RFC 6845: OSPF Hybrid Broadcast and Point-to-Multipoint Interface Type
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to model a broadcast network as a hybrid of broadcast and point-to-multipoint networks for purposes of OSPF operation. Neighbor discovery and maintenance as well as Link State Advertisement (LSA) database synchronization are performed using the broadcast model, but the network is represented using the point-to-multipoint model in the router-LSAs of the routers connected to it. This allows an accurate representation of the cost of communication between different routers on the network, while maintaining the network efficiency of broadcast operation. This approach is relatively simple and requires minimal changes to OSPF. This document updates both OSPFv2 (RFC 2328) and OSPFv3 (RFC 5340). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6845
- Published
- January 2013
- Authors
- N. Sheth; L. Wang; J. Zhang
- Status
- PROPOSED STANDARD
- 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 8042OSPF Two-Part MetricCurrent
December 2016
- RFC 6992Routing for IPv4-Embedded IPv6 PacketsCurrent
July 2013
- RFC 7096Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)Current
January 2014
- RFC 6571Loop-Free Alternate (LFA) Applicability in Service Provider (SP) NetworksCurrent
June 2012
- RFC 7138Traffic Engineering Extensions to OSPF for GMPLS Control of Evolving G.709 Optical Transport NetworksCurrent
March 2014
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6425Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP PingCurrent
November 2011
- RFC 6348Requirements for Point-to-Multipoint Extensions to the Label Distribution ProtocolCurrent
September 2011
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?