RFC 8362: OSPFv3 Link State Advertisement (LSA) Extensibility
In plain English — editorial summary, not part of the RFC
OSPFv3 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisement (LSA) as described in RFC 5340. Without LSA extension, attributes associated with OSPFv3 links and advertised IPv6 prefixes must be advertised in separate LSAs and correlated to the fixed-format LSAs. This document extends the LSA format by encoding the existing OSPFv3 LSA information in Type-Length-Value (TLV) tuples and allowing advertisement of additional information with additional TLVs. Backward-compatibility mechanisms are also described. This document updates RFC 5340, "OSPF for IPv6", and RFC 5838, "Support of Address Families in OSPFv3", by providing TLV-based encodings for the base OSPFv3 unicast support and OSPFv3 address family support.
Document record
- Document ID
- RFC8362
- Published
- April 2018
- Authors
- A. Lindem; A. Roy; D. Goethals; V. Reddy Vallem; F. Baker
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8361Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) TrafficCurrent
April 2018
- RFC 8363GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
May 2018
- RFC 8360Resource Public Key Infrastructure (RPKI) Validation ReconsideredCurrent
April 2018
- RFC 8364PIM Flooding Mechanism (PFM) and Source Discovery (SD)Updated
March 2018
- RFC 8359Network-Assigned Upstream LabelCurrent
March 2018
- RFC 8365A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)Updated
March 2018
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 8355Resiliency Use Cases in Source Packet Routing in Networking (SPRING) NetworksCurrent
March 2018
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?