RFC 1765: OSPF Database Overflow
In plain English — editorial summary, not part of the RFC
This memo details a way of gracefully handling unanticipated database overflows. This memo defines an Experimental Protocol for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1765
- Published
- March 1995
- Authors
- J. Moy
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1772Application of the Border Gateway Protocol in the InternetCurrent
March 1995
- RFC 1773Experience with the BGP-4 protocolCurrent
March 1995
- RFC 1774BGP-4 Protocol AnalysisCurrent
March 1995
- RFC 1747Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2Current
January 1995
- RFC 1745BGP4/IDRP for IP---OSPF InteractionCurrent
December 1994
- RFC 1793Extending OSPF to Support Demand CircuitsUpdated
April 1995
- RFC 1735NBMA Address Resolution Protocol (NARP)Current
December 1994
- RFC 1724RIP Version 2 MIB ExtensionCurrent
November 1994
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?