RFC 3883: Detecting Inactive Neighbors over OSPF Demand Circuits (DC)
In plain English — editorial summary, not part of the RFC
OSPF is a link-state intra-domain routing protocol used in IP networks. OSPF behavior over demand circuits (DC) is optimized in RFC 1793 to minimize the amount of overhead traffic. A part of the OSPF demand circuit extensions is the Hello suppression mechanism. This technique allows a demand circuit to go down when no interesting traffic is going through the link. However, it also introduces a problem, where it becomes impossible to detect an OSPF-inactive neighbor over such a link. This memo introduces a new mechanism called "neighbor probing" to address the above problem. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3883
- Published
- October 2004
- Authors
- S. Rao; A. Zinin; A. Roy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
- Updates:
- RFC 1793
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4136OSPF Refresh and Flooding Reduction in Stable TopologiesCurrent
July 2005
- RFC 3623Graceful OSPF RestartCurrent
November 2003
- RFC 4167Graceful OSPF Restart Implementation ReportCurrent
October 2005
- RFC 4202Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4203OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4222Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion AvoidanceUpdated
October 2005
- RFC 4552Authentication/Confidentiality for OSPFv3Current
June 2006
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
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?