Protocol Extension for Support of Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching (MPLS) Traffic Engineering
RFC 3496

Document Type RFC - Informational (March 2003; No errata)
Last updated 2015-10-14
Stream Legacy
Formats plain text pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3496 (Informational)
Telechat date
Responsible AD Scott Bradner
Send notices to (None)
Network Working Group                                        A. G. Malis
Request for Comments: 3496                                      T. Hsiao
Category: Informational                                  Vivace Networks
                                                              March 2003

  Protocol Extension for Support of Asynchronous Transfer Mode (ATM)
        Service Class-aware Multiprotocol Label Switching (MPLS)
                          Traffic Engineering

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

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

Abstract

   This document specifies a Resource ReSerVation Protocol-Traffic
   Engineering (RSVP-TE) signaling extension for support of Asynchronous
   Transfer Mode (ATM) Service Class-aware Multiprotocol Label Switching
   (MPLS) Traffic Engineering.

Table of Contents

   1.  Overview......................................................2
   2.  Extended RSVP-TE Path Message Format..........................2
       2.1 PATH Message Format.......................................3
   3.  ATM_SERVICECLASS Object.......................................3
   4.  Handling the ATM_SERVICECLASS Object..........................4
   5.  Non-support of the ATM_SERVICECLASS Object....................4
   6.  Security Considerations.......................................4
   7.  IANA Considerations...........................................5
   8.  References....................................................5
   9.  Authors' Addresses............................................5
   10. Full Copyright Statement......................................6

Malis & Hsiao                Informational                      [Page 1]
RFC 3496    ATM Service Class-aware MPLS Traffic Engineering  March 2003

1. Overview

   This document defines a Resource ReSerVation Protocol-Traffic
   Engineering (RSVP-TE) protocol addition to support ATM (Asynchronous
   Transfer Mode) Service Class-aware MPLS (MultiProtocol Label
   Switching) Traffic Engineering.

   This protocol addition is used with all MPLS Label Switched Routers
   (LSRs) and link types (including, but not restricted to, Packet over
   SONET, Ethernet, and ATM links) to signal traffic engineered paths
   that can support the ATM service classes as defined by the ATM Forum
   [TM].  This document does not specify HOW to actually implement the
   functionality in the MPLS LSRs to emulate the ATM Forum service
   classes (such as necessary queuing and scheduling mechanisms), only
   how to signal that the TE path must support the ATM Forum service
   classes.  A useful application for such paths is the carriage of ATM
   cells encapsulated in IP or MPLS packets in order to use MPLS
   networks as functional replacements for ATM networks.

2. Extended RSVP-TE Path Message Format

   One new RSVP-TE Object is defined in this document: the
   ATM_SERVICECLASS Object.  Detailed description of this Object is
   provided below.  This new Object is applicable to PATH messages.
   This specification only defines the use of the ATM_SERVICECLASS
   Object in PATH messages used to establish LSP (Label Switched Path)
   Tunnels in accordance with [RSVP-TE].  Such PATH messages contain a
   Session Object with a C-Type equal to LSP_TUNNEL_IPv4 and a
   LABEL_REQUEST object.

   Restrictions defined in [RSVP-TE] for support of establishment of LSP
   Tunnels via RSVP-TE are also applicable to the establishment of LSP
   Tunnels supporting ATM Service Class-aware traffic engineering.  For
   instance, only unicast LSPs are supported and Multicast LSPs are for
   further study.

   This new ATM_SERVICECLASS object is optional with respect to RSVP-TE
   so that general RSVP-TE implementations not concerned with ATM
   Service Class-aware traffic engineering MPLS LSP setup do not have to
   support this object.

Malis & Hsiao                Informational                      [Page 2]
RFC 3496    ATM Service Class-aware MPLS Traffic Engineering  March 2003

2.1 PATH Message Format

   The format of the extended PATH message is as follows:

   <PATH Message> ::=      <Common Header> [ <INTEGRITY> ]
                                <SESSION> <RSVP_HOP>
                            <TIME_VALUES>
                            [ <EXPLICIT_ROUTE> ]
                            <LABEL_REQUEST>
                            [ <SESSION_ATTRIBUTE> ]
                            [ <DIFFSERV> ]
                            [ <ATM_SERVICECLASS> ]
                            [ <POLICY_DATA> ... ]
                            [ <sender descriptor> ]

   <sender descriptor> ::=  <SENDER_TEMPLATE> [ <SENDER_TSPEC> ]
                            [ <ADSPEC> ]
                            [ <RECORD_ROUTE> ]

3. ATM_SERVICECLASS Object

   The ATM_SERVICECLASS object format is as follows:
Show full document text