RFC 4105: Requirements for Inter-Area MPLS Traffic Engineering
In plain English — editorial summary, not part of the RFC
This document lists a detailed set of functional requirements for the support of inter-area MPLS Traffic Engineering (inter-area MPLS TE). It is intended that solutions that specify procedures and protocol extensions for inter-area MPLS TE satisfy these requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4105
- Published
- June 2005
- Authors
- J.-L. Le Roux; J.-P. Vasseur; J. Boyle
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sub
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 5151Inter-Domain MPLS and GMPLS Traffic Engineering -- Resource Reservation Protocol-Traffic Engineering (RSVP-TE) ExtensionsCurrent
February 2008
- RFC 5316ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringObsoleted
December 2008
- RFC 5392OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic EngineeringCurrent
January 2009
- RFC 5712MPLS Traffic Engineering Soft PreemptionCurrent
January 2010
- RFC 4216MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) RequirementsCurrent
November 2005
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 3346Applicability Statement for Traffic Engineering with MPLSCurrent
August 2002
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?