RFC 2702: Requirements for Traffic Engineering Over MPLS
In plain English — editorial summary, not part of the RFC
This document presents a set of requirements for Traffic Engineering over Multiprotocol Label Switching (MPLS). It identifies the functional capabilities required to implement policies that facilitate efficient and reliable network operations in an MPLS domain. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2702
- Published
- September 1999
- Authors
- D. Awduche; J. Malcolm; J. Agogbua; M. O'Dell; J. McManus
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 2547BGP/MPLS VPNsObsoleted
March 1999
- RFC 2430A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)Current
October 1998
- RFC 3036LDP SpecificationObsoleted
January 2001
- RFC 3037LDP ApplicabilityCurrent
January 2001
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 3213Applicability Statement for CR-LDPCurrent
January 2002
- RFC 3215LDP State MachineCurrent
January 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?