Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
RFC 6511

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 09

Internet Engineering Task Force (IETF)                            Z. Ali
Request for Comments: 6511                                    G. Swallow
Category: Standards Track                                  Cisco Systems
ISSN: 2070-1721                                              R. Aggarwal
                                                        Juniper Networks
                                                           February 2012

    Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for
                      RSVP-TE Label Switched Paths

Abstract

   There are many deployment scenarios that require an egress Label
   Switching Router (LSR) to receive binding of the Resource Reservation
   Protocol - Traffic Engineering (RSVP-TE) Label Switched Path (LSP) to
   an application and a payload identifier using some "out-of-band"
   (OOB) mechanism.  This document defines protocol mechanisms to
   address this requirement.  The procedures described in this document
   are equally applicable for point-to-point (P2P) and point-to-
   multipoint (P2MP) LSPs.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6511.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Ali, et al.                  Standards Track                    [Page 1]
RFC 6511        Non-PHP and OOB Mapping for RSVP-TE LSPs   February 2012

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

 Table of Contents

   1. Introduction ....................................................2
      1.1. Conventions Used in This Document ..........................3
   2. RSVP-TE Signaling Extensions ....................................3
      2.1. Signaling Non-PHP Behavior .................................3
      2.2. Signaling OOB Mapping Indication ...........................5
      2.3. Relationship between OOB and Non-PHP Flags .................6
      2.4. Egress Procedure for Label Binding .........................6
   3. Security Considerations .........................................7
   4. IANA Considerations .............................................7
      4.1. Attribute Flags for LSP Attributes Object ..................7
      4.2. New RSVP Error Sub-Code ....................................8
   5. Acknowledgements ................................................8
   6. References ......................................................8
      6.1. Normative References .......................................8
      6.2. Informative References .....................................9

1.  Introduction

   When Resource Reservation Protocol - Traffic Engineering (RSVP-TE) is
   used for applications like Multicast Virtual Private Network (MVPN)
   [RFC6513] and Virtual Private LAN Service (VPLS) [RFC4761], an egress
   Label Switching Router (LSR) receives the binding of the RSVP-TE
   Label Switched Path (LSP) to an application and a payload identifier
   using an "out-of-band" (OOB) mechanism (e.g., Border Gateway Protocol
   (BGP)).  In such cases, the egress LSR cannot make correct forwarding
   decisions until such OOB mapping information is received.
   Furthermore, in order to apply the binding information, the egress