RFC 3270 - Multi-Protocol Label Switching (MPLS) Support of Differentiated Services

• Status: Standards Track
• Published: May 2002
• Stream: IETF
• Updated by: RFC 5462
• Errata: RFC 3270 Errata

---

Document Information

• RFC Number: 3270
• Title: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
• Authors: F. Le Faucheur, Editor (Cisco Systems), L. Wu (Cisco Systems), B. Davie (Cisco Systems), S. Davari (PMC-Sierra Inc.), P. Vaananen (Nokia), R. Krishnan (Axiowave Networks), P. Cheval (Alcatel), J. Heinanen (Song Networks)
• Date: May 2002
• Category: Standards Track
• Updated by: RFC 5462
• ISSN: 2070-1721

Abstract

This document defines a flexible solution for support of Differentiated Services (Diff-Serv) over Multi-Protocol Label Switching (MPLS) networks.

This solution allows the MPLS network administrator to select how Diff-Serv Behavior Aggregates (BAs) are mapped onto Label Switched Paths (LSPs) so that he/she can best match the Diff-Serv, Traffic Engineering and protection objectives within his/her particular network. For instance, this solution allows the network administrator to decide whether different sets of BAs are to be mapped onto the same LSP or mapped onto separate LSPs.

Status of This Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2002). All Rights Reserved.

Table of Contents

• 1. Introduction
  • 1.1. Terminology
  • 1.2. EXP-Inferred-PSC LSPs (E-LSP)
  • 1.3. Label-Only-Inferred-PSC LSPs (L-LSP)
  • 1.4. Overall Operations
  • 1.5. Relationship between Label and FEC
  • 1.6. Bandwidth Reservation for E-LSPs and L-LSPs
• 2. Label Forwarding Model for Diff-Serv LSRs and Tunneling Models
  • 2.1. Label Forwarding Model for Diff-Serv LSRs
  • 2.2. Incoming PHB Determination
  • 2.2.1. Incoming PHB Determination Considering a Label Stack Entry
  • 2.2.2. Incoming PHB Determination Considering IP Header
  • 2.3. Outgoing PHB Determination With Optional Traffic Conditioning
  • 2.4. Label Forwarding
  • 2.5. Encoding Diff-Serv Information Into Encapsulation Layer
  • 2.5.1. Encoding Diff-Serv Information Into Transmitted Label Entry
  • 2.5.2. Encoding Diff-Serv Information Into Transmitted IP Header
  • 2.6. Diff-Serv Tunneling Models over MPLS
  • 2.6.1. Diff-Serv Tunneling Models
  • 2.6.2. Pipe Model
  • 2.6.2.1. Short Pipe Model
  • 2.6.3. Uniform Model
  • 2.6.4. Hierarchy
• 3. Detailed Operations of E-LSPs
  • 3.1. E-LSP Definition
  • 3.2. Populating the `Encaps-->PHB mapping' for an incoming E-LSP
  • 3.2.1. Preconfigured `EXP<-->PHB mapping'
  • 3.3. Incoming PHB Determination On Incoming E-LSP
  • 3.4. Populating the `Set of PHB-->Encaps mappings' for an outgoing E-LSP
  • 3.4.1. `PHB-->EXP mapping'
  • 3.4.2. `PHB-->CLP mapping'
  • 3.4.2.1. Default `PHB-->CLP mapping'
  • 3.4.3. `PHB-->DE mapping'
  • 3.4.3.1. `Default PHB-->DE mapping'
  • 3.4.4. `PHB-->802.1 mapping'
  • 3.4.4.1. Preconfigured `PHB-->802.1 Mapping'
  • 3.5. Encoding Diff-Serv information into Encapsulation Layer On Outgoing E-LSP
  • 3.5.1. `PHB-->EXP mapping'
  • 3.5.2. `PHB-->CLP mapping'
  • 3.5.3. `PHB-->DE mapping'
  • 3.5.4. `PHB-->802.1 mapping'
  • 3.6. E-LSP Merging
• 4. Detailed Operation of L-LSPs
  • 4.1. L-LSP Definition
  • 4.2. Populating the `Encaps-->PHB mapping' for an incoming L-LSP
  • 4.2.1. `EXP-->PHB mapping'
  • 4.2.1.1. Mandatory `EXP/PSC --> PHB mapping'
  • 4.2.2. `CLP-->PHB mapping'
  • 4.2.2.1. Default `CLP/PSC --> PHB mapping'
  • 4.2.3. `DE-->PHB mapping'
  • 4.2.3.1. Default `DE/PSC --> PHB mapping'
  • 4.3. Incoming PHB Determination On Incoming L-LSP
  • 4.3.1. `EXP-->PHB mapping'
  • 4.3.2. `CLP-->PHB mapping'
  • 4.3.3. `DE-->PHB mapping'
  • 4.4. Populating the `Set of PHB-->Encaps mappings' for an outgoing L-LSP
  • 4.4.1. `PHB-->EXP mapping'
  • 4.4.1.1. Mandatory `PHB-->EXP mapping'
  • 4.4.2. `PHB-->CLP mapping'
  • 4.4.3. `PHB-->DE mapping'
  • 4.4.4. `PHB-->802.1 mapping'
  • 4.5. Encoding Diff-Serv Information into Encapsulation Layer on Outgoing L-LSP
  • 4.6. L-LSP Merging
• 5. RSVP Extension for Diff-Serv Support
  • 5.1. Diff-Serv related RSVP Messages Format
  • 5.1.1. Path Message Format
  • 5.2. DIFFSERV Object
  • 5.2.1. DIFFSERV object for an E-LSP:
  • 5.2.2. DIFFSERV object for an L-LSP:
  • 5.3. Handling DIFFSERV Object
  • 5.4. Non-support of the DIFFSERV Object
  • 5.5. Error Codes For Diff-Serv
  • 5.6. Intserv Service Type
• 6. LDP Extensions for Diff-Serv Support
  • 6.1. Diff-Serv TLV
  • 6.2. Diff-Serv Status Code Values
  • 6.3. Diff-Serv Related LDP Messages
  • 6.3.1. Label Request Message
  • 6.3.2. Label Mapping Message
  • 6.3.3. Label Release Message
  • 6.3.4. Notification Message
  • 6.4. Handling of the Diff-Serv TLV
  • 6.4.1. Handling of the Diff-Serv TLV in Downstream Unsolicited Mode
  • 6.4.2. Handling of the Diff-Serv TLV in Downstream on Demand Mode
  • 6.5. Non-Handling of the Diff-Serv TLV
  • 6.6. Bandwidth Information
• 7. MPLS Support of Diff-Serv over PPP, LAN, Non-LC-ATM and Non-LC-FR Interfaces
• 8. MPLS Support of Diff-Serv over LC-ATM Interfaces
  • 8.1. Use of ATM Traffic Classes and Traffic Management mechanisms
  • 8.2. LSR Implementation With LC-ATM Interfaces
• 9. MPLS Support of Diff-Serv over LC-FR Interfaces
  • 9.1. Use of Frame Relay Traffic parameters and Traffic Management mechanisms
  • 9.2. LSR Implementation With LC-FR Interfaces
• 10. IANA Considerations
• 11. Security Considerations
• 12. Acknowledgments
• References
• Authors' Addresses
• Full Copyright Statement

Appendices

• Appendix A. Example Deployment Scenarios
  • A.1. Scenario 1: 8 (or fewer) BAs, no Traffic Engineering, no MPLS Protection
  • A.2. Scenario 2: More than 8 BAs, no Traffic Engineering, no MPLS Protection
  • A.3. Scenario 3: 8 (or fewer) BAs, Aggregate Traffic Engineering, Aggregate MPLS Protection
  • A.4. Scenario 4: per-OA Traffic Engineering/MPLS Protection
  • A.5. Scenario 5: 8 (or fewer) BAs, per-OA Traffic Engineering/MPLS Protection
  • A.6. Scenario 6: no Traffic Engineering/MPLS Protection on 8 BAs, per-OA Traffic Engineering/MPLS Protection on other BAs.
  • A.7. Scenario 7: More than 8 BAs, no Traffic Engineering, no MPLS Protection
• Appendix B. Example Bandwidth Reservation Scenarios
  • B.1. Scenario 1: No Bandwidth Reservation
  • B.2. Scenario 2: Bandwidth Reservation for per-PSC Admission Control
  • B.3. Scenario 3: Bandwidth Reservation for per-PSC Admission Control and per-PSC Resource Adjustment

---

Related Resources

• Official RFC: RFC 3270
• DataTracker: RFC 3270
• Errata: RFC Editor Errata