A new Request for Comments is now available in online RFC libraries.


        RFC 1765:

        Title:      OSPF Database Overflow
        Author:     J. Moy
        Date:       March 1995
        Mailbox:    jmoy@casc.com
        Pages:      9
        Characters: 21,613
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1765.txt


Proper operation of the OSPF protocol requires that all OSPF routers
maintain an identical copy of the OSPF link-state database.  However,
when the size of the link-state database becomes very large, some
routers may be unable to keep the entire database due to resource
shortages; we term this "database overflow". When database overflow is
anticipated, the routers with limited resources can be accommodated by
configuring OSPF stub areas and NSSAs. This memo details a way of
gracefully handling unanticipated database overflows.  This memo is a
product of the Open Shortest Path First Working Group of the IETF

This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited..

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute