RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2
In plain English — editorial summary, not part of the RFC
This document describes extensions to the OSPF protocol version 2 to support intra-area Traffic Engineering (TE), using Opaque Link State Advertisements.
Document record
- Document ID
- RFC3630
- Published
- October 2003
- Authors
- D. Katz; K. Kompella; D. Yeung
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Updates:
- RFC 2370
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3623Graceful OSPF RestartCurrent
November 2003
- RFC 2844OSPF over ATM and Proxy-PARCurrent
May 2000
- RFC 2740OSPF for IPv6Obsoleted
December 1999
- RFC 4576Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 2676QoS Routing Mechanisms and OSPF ExtensionsCurrent
August 1999
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 1252OSPF Version 2 Management Information BaseObsoleted
August 1991
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?