Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 5340,RFC 5838

Authors:

A. Lindem
A. Roy
D. Goethals
V. Reddy Vallem
F. Baker

Stream:

IETF

Source:

ospf (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8362

Discuss this RFC: Send questions or comments to the mailing listlsr@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8362

Abstract

OSPFv3 requires functional extension beyond what can readily be donewith the fixed-format Link State Advertisement (LSA) as described inRFC 5340. Without LSA extension, attributes associated with OSPFv3links and advertised IPv6 prefixes must be advertised in separateLSAs and correlated to the fixed-format LSAs. This document extendsthe LSA format by encoding the existing OSPFv3 LSA information inType-Length-Value (TLV) tuples and allowing advertisement ofadditional information with additional TLVs. Backward-compatibilitymechanisms are also described.

This document updates RFC 5340, "OSPF for IPv6", and RFC 5838,"Support of Address Families in OSPFv3", by providing TLV-basedencodings for the base OSPFv3 unicast support and OSPFv3 addressfamily support.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.