Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
RFC 3564, “Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering”, is an Informational document published in July 2003 by F. Le Faucheur, W. Lai. It has since been updated by RFC 5462. The canonical text is published by the RFC Editor.
Abstract
This document presents Service Provider requirements for support of Differentiated Services (Diff-Serv)-aware MPLS Traffic Engineering (DS- TE). Its objective is to provide guidance for the definition, selection and specification of a technical solution addressing these requirements. Specification for this solution itself is outside the scope of this document. A problem statement is first provided. Then, the document describes example applications scenarios identified by Service Providers where existing MPLS Traffic Engineering mechanisms fall short and Diff-Serv-aware Traffic Engineering can address the needs. The detailed requirements that need to be addressed by the technical solution are also reviewed. Finally, the document identifies the evaluation criteria that should be considered for selection and definition of the technical solution. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3564 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3563 Cooperative Agreement Between the ISOC/IETF and ISO/IEC Joint Technical Committee 1/Sub Committee 6 on IS-IS Routing Protocol Development
- RFC 3565 Use of the Advanced Encryption Standard Encryption Algorithm in Cryptographic Message Syntax
- RFC 3562 Key Management Considerations for the TCP MD5 Signature Option
- RFC 3566 The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec
- RFC 3561 Ad hoc On-Demand Distance Vector Routing
- RFC 3567 Intermediate System to Intermediate System Cryptographic Authentication
- RFC 3560 Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax
- RFC 3568 Known Content Network Request-Routing Mechanisms