Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)
RFC 7570

Document Type RFC - Proposed Standard (July 2015; No errata)
Last updated 2015-10-14
Replaces draft-ietf-ccamp-lsp-attribute-ro
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication Jan 2015
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2014-12-31)
IESG IESG state RFC 7570 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                  C. Margaria, Ed.
Request for Comments: 7570                                       Juniper
Category: Standards Track                                  G. Martinelli
ISSN: 2070-1721                                                    Cisco
                                                                S. Balls
                                                               B. Wright
                                                              Metaswitch
                                                               July 2015

 Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)

Abstract

   RFC 5420 extends RSVP-TE to specify or record generic attributes that
   apply to the whole of the path of a Label Switched Path (LSP).  This
   document defines an extension to the RSVP Explicit Route Object (ERO)
   and Record Route Object (RRO) to allow them to specify or record
   generic attributes that apply to a given hop.

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

Copyright Notice

   Copyright (c) 2015 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
   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.

Margaria, et al.             Standards Track                    [Page 1]
RFC 7570               General ERO LSP Parameters              July 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  ERO Hop Attributes Subobject  . . . . . . . . . . . . . . . .   3
     2.1.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Hop Attributes TLVs . . . . . . . . . . . . . . . . . . .   4
     2.3.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  RRO Hop Attributes Subobject  . . . . . . . . . . . . . . . .   6
     3.1.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  Subobject Presence Rule . . . . . . . . . . . . . . .   6
       3.2.2.  Reporting Compliance with ERO Hop Attributes  . . . .   7
       3.2.3.  Compatibility with RRO Attributes Subobject . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  ERO Hop Attributes Subobject  . . . . . . . . . . . . . .   8
     4.2.  RRO Hop Attributes Subobject  . . . . . . . . . . . . . .   8
     4.3.  Existing Attribute Flags  . . . . . . . . . . . . . . . .   8
     4.4.  Existing LSP Attribute TLVs . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched
   Paths (LSPs) can be route constrained by making use of the Explicit
   Route Object (ERO) and related subobjects as defined in [RFC3209],
   [RFC3473], [RFC3477], [RFC4873], [RFC4874], [RFC5520], and [RFC5553].
   Several documents have identified the need for attributes that can be
   targeted at specific hops in the path of an LSP, including [RFC6163],
   [WSON-SIG], [RFC7571], or [OBJ-FUN].  This document provides a
   generic mechanism for use by these other documents.

   RSVP already supports generic extension of LSP attributes in
   [RFC5420].  In order to support current and future ERO constraint
Show full document text