RFC 4813: OSPF Link-Local Signaling
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5613.
Current version: RFC 5613 — OSPF Link-Local Signaling
In plain English — editorial summary, not part of the RFC
OSPF is a link-state intra-domain routing protocol used in IP networks. OSPF routers exchange information on a link using packets that follow a well-defined format. The format of OSPF packets is not flexible enough to enable applications to exchange arbitrary data, which may be necessary in certain situations. This memo describes a vendor-specific, backward-compatible technique to perform link-local signaling, i.e., exchange arbitrary data on a link. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4813
- Published
- March 2007
- Authors
- B. Friedman; L. Nguyen; A. Roy; D. Yeung; A. Zinin
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 5613
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4812OSPF Restart SignalingCurrent
March 2007
- RFC 4811OSPF Out-of-Band Link State Database (LSDB) ResynchronizationUpdated
March 2007
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
- RFC 4915Multi-Topology (MT) Routing in OSPFCurrent
June 2007
- RFC 4940IANA Considerations for OSPFCurrent
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 4577OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 4552Authentication/Confidentiality for OSPFv3Current
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?