RFC 5329: Traffic Engineering Extensions to OSPF Version 3
In plain English — editorial summary, not part of the RFC
This document describes extensions to OSPFv3 to support intra-area Traffic Engineering (TE). This document extends OSPFv2 TE to handle IPv6 networks. A new TLV and several new sub-TLVs are defined to support IPv6 networks. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5329
- Published
- September 2008
- Authors
- K. Ishiguro; V. Manral; A. Davey; A. Lindem
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5340OSPF for IPv6Updated
July 2008
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 7770Extensions to OSPF for Advertising Optional Router CapabilitiesCurrent
February 2016
- RFC 5330A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a LinkCurrent
October 2008
- RFC 5305IS-IS Extensions for Traffic EngineeringUpdated
October 2008
- RFC 5392OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringCurrent
January 2009
- RFC 5252OSPF-Based Layer 1 VPN Auto-DiscoveryCurrent
July 2008
- RFC 5250The OSPF Opaque LSA OptionCurrent
July 2008
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?