datatracker.ietf.org
Sign in
Version 5.6.3.p2, 2014-09-29
Report a bug

Resource Reservation Protocol (RSVP) Message Formats for Label Switched Path (LSP) Attributes Objects
RFC 6510

Internet Engineering Task Force (IETF)                         L. Berger
Request for Comments: 6510                                          LabN
Updates: 4875, 5420                                           G. Swallow
Category: Standards Track                                          Cisco
ISSN: 2070-1721                                            February 2012

        Resource Reservation Protocol (RSVP) Message Formats for
              Label Switched Path (LSP) Attributes Objects

Abstract

   Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs)
   established using the Resource Reservation Protocol Traffic
   Engineering (RSVP-TE) extensions may be signaled with a set of LSP-
   specific attributes.  These attributes may be carried in both Path
   and Resv messages.  This document specifies how LSP attributes are to
   be carried in RSVP Path and Resv messages using the Routing Backus-
   Naur Form and clarifies related Resv message formats.  This document
   updates RFC 4875 and RFC 5420.

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/rfc6510.

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
   to this document.  Code Components extracted from this document must

Berger & Swallow             Standards Track                    [Page 1]
RFC 6510         RSVP Message Formats for LSP Attributes   February 2012

   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.

Table of Contents

   1. Introduction ....................................................2
      1.1. Conventions Used in This Document ..........................3
   2. Path Messages ...................................................3
      2.1. Path Message Format ........................................3
   3. Resv Messages ...................................................4
      3.1. Resv Message Format -- Per LSP Operational Status ..........5
      3.2. Resv Message Format -- Per S2L Operational Status ..........6
           3.2.1. Compatibility .......................................6
   4. Security Considerations .........................................6
   5. Acknowledgments .................................................7
   6. References ......................................................7
      6.1. Normative References .......................................7
      6.2. Informative References .....................................7

1.  Introduction

   Signaling in support of Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) point-to-point Label Switched Paths (LSPs)
   is defined in [RFC3209] and [RFC3473]. [RFC4875] defines signaling
   support for point-to-multipoint (P2MP) Traffic Engineering (TE) LSPs.

   Two LSP Attributes objects are defined in [RFC5420].  These objects
   may be used to provide additional information related to how an LSP
   should be set up when carried in a Path message and, when carried in
   a Resv message, how an LSP has been established.  The definition of
   the objects includes a narrative description of related message
   formats (see Section 9 of [RFC5420]).  This definition does not
   provide the related Routing Backus-Naur Form (BNF) [RFC5511] that is
   typically used to define how messages are to be constructed using
   RSVP objects.  The current message format description has led to the
   open question of how the LSP Attributes objects are to be processed
   in Resv messages of P2MP LSPs (which are defined in [RFC4875]).

   This document provides the BNF for Path and Resv messages carrying
   the LSP Attributes object.  The definition clarifies how the objects
   are to be carried for all LSP types.  Both Path and Resv message BNF
   is provided for completeness.

Berger & Swallow             Standards Track                    [Page 2]

[include full document text]