2702: Requirements for Traffic Engineering Over

HTML TXT PS PDF

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. These capabilities can be used to optimize the utilization of network resources and to enhance traffic oriented performance characteristics.

Status INFORMATIONAL
Format TXT=68386 bytes
Authors J. McManus M. O'Dell J. Agogbua J. Malcolm MPLS.
Date September 1999
Keyphrases traffic trunk traffic trunks MPLS

References

RFC2105: Cisco Systems' Tag Switching Architecture Overview.
RFC2119: Key words for use in RFCs to Indicate Requirement Levels.
RFC2386: A Framework for QoS-based Routing in the Internet.
RFC2430: A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE).
RFC2676: QoS Routing Mechanisms and OSPF Extensions.

Referenced by

RFC3031: Multiprotocol Label Switching Architecture.
RFC3036: LDP Specification.
RFC3168: The Addition of Explicit Congestion Notification (ECN) to
RFC3198: Terminology for Policy-Based Management.
RFC3209: RSVP-TE: Extensions to RSVP for LSP Tunnels.
RFC3210: Applicability Statement for Extensions to RSVP for LSP-Tunnels.
RFC3212: Constraint-Based LSP Setup using
RFC3213: Applicability Statement for CR-LDP.
RFC3214: LSP Modification Using CR-LDP.
RFC3272: Overview and Principles of Internet Traffic Engineering.
RFC3299: Request for Comments Summary RFC Numbers 3200-3299.
RFC3346: Applicability Statement for Traffic Engineering with
RFC3386: Network Hierarchy and Multilayer Survivability.
RFC3469: Framework for Multi-Protocol Label Switching (MPLS)-based Recovery.
RFC3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering.
RFC3630: Traffic Engineering (TE) Extensions to OSPF Version 2.
RFC3784: Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE).
RFC3785: Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) Metric.
RFC3812: Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB).
RFC3906: Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels.
RFC3917: Requirements for IP Flow Information Export (IPFIX).
RFC3945: Generalized Multi-Protocol Label Switching (GMPLS) Architecture.
RFC3970: A Traffic Engineering (TE)
RFC4105: Requirements for Inter-Area MPLS Traffic Engineering. J.-L. Le Roux, Ed., J.-P. Vasseur,
RFC4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering.
RFC4128: Bandwidth Constraints Models for Differentiated Services (Diffserv)-aware MPLS Traffic Engineering: Performance Evaluation.
RFC4190: Framework for Supporting Emergency Telecommunications Service (ETS) in IP Telephony.
RFC4216: MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements. R. Zhang, Ed., J.-P. Vasseur,
RFC4461: Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs).
RFC4655: A Path Computation Element (PCE)-Based Architecture. A. Farrel, J.-P. Vasseur,