Juniper

200 Somerset Corporate Boulevard, Suite 4001 Bridgewater NJ 08807 United States cmargaria@juniper.net

Cisco

via Philips 12 20900 Monza Italy +39 039 209 2044 giomarti@cisco.com

Metaswitch

100 Church Street EN2 6BQ Enfield United Kingdom +44 208 366 1177 steve.balls@metaswitch.com

Metaswitch

100 Church Street EN2 6BQ Enfield United Kingdom +44 208 366 1177 Ben.Wright@metaswitch.com

Routing TEAS RSVP-TE GMPLS 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.

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 , , , , , , and . Several documents have identified the need for attributes that can be targeted at specific hops in the path of an LSP, including , , , or . This document provides a generic mechanism for use by these other documents. RSVP already supports generic extension of LSP attributes in . In order to support current and future ERO constraint extensions, this document provides a mechanism to define per-hop attributes. The document describes a generic mechanism for carrying information related to specific nodes when signaling an LSP. This document does not restrict what that information can be used for. The defined approach builds on LSP attributes defined in and enables attributes to be expressed in ERO and Secondary Explicit Route Objects (SEROs). A new ERO subobject is defined, containing a list of generic per-hop attributes.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

The ERO Hop Attributes subobject is OPTIONAL. If used, it is carried in the ERO or SERO. The subobject uses the standard format of an ERO subobject.

The length is variable and content is a list of Hop Attributes TLVs defined in . The size of the ERO subobject limits the size of the Hop Attributes TLV to 250 bytes. The typical size of currently defined and forthcoming LSP_ATTRIBUTE TLVs applicable to a specific hop (WSON_SIGNALING, Objective Function (OF), and Metric) is not foreseen to exceed this limit. The ERO Hop Attributes subobject is defined as follows:

The L, Type, and Length parameters are as defined in , Section 4.3.3. The L bit MUST be set to 0. The Type for the ERO Hop Attributes subobject is 35. The Hop Attributes TLVs are encoded as defined in . Reserved MUST be set to 0 when the subobject is inserted in the ERO, MUST NOT be changed when a node processes the ERO, and MUST be ignored on the node addressed by the preceding ERO subobjects. This bit reflects the LSP_REQUIRED_ATTRIBUTE and LSP_ATTRIBUTE semantic defined in . When set, it indicates required hop attributes to be processed by the node. When cleared, it indicates that the hop attributes are not required as described in . The TLVs as defined in .

ERO attributes carried by the new objects defined in this document are encoded within TLVs. Each object MAY contain one or more TLVs. There are no ordering rules for TLVs, and interpretation SHOULD NOT be placed on the order in which TLVs are received. The TLV format is defined in , Section 3. The Attribute Flags TLV defined in is carried in an ERO Hop Attributes subobject. Flags set in the Attribute Flags TLV carried in an ERO Hop Attributes subobject SHALL be interpreted in the context of the received ERO. Only a subset of defined flags are defined as valid for use in Attribute Flags TLV carried in an ERO Hop Attributes subobject. Invalid flags SHALL be silently ignored. Unknown flags SHOULD trigger the generation of a PathErr with Error Code "Unknown Attributes Bit" as defined in , Section 5.2. The set of valid flags are defined in . The presence and ordering rule of the Attribute Flags TLV in an ERO Hop Attributes subobject is defined by each Flag. A document defining a flag to be used in an Attribute Flags TLV carried in the ERO Hop Attributes subobject has to describe: after which kinds of ERO subobject the flag is valid, if ordering of the flag and other ERO subobjects associated with the same hop (e.g., Label subobjects) is significant, if ordering is significant, how the flag is interpreted in association with the preceding subobjects, and any flag modification rules that might apply.

As described in , the ERO is managed as a list of subobjects each identifying a specific entity, an abstract node, or a link that defines a waypoint in the network path. Identifying subobjects of various types are defined in , , , , , and . modified the ERO list by allowing one or two Label subobjects to be interposed in the list after a subobject identifying a link. One or more ERO Hop Attributes subobjects applicable to a particular hop MAY be inserted directly after any of the existing identifying subobjects defined in, , , , , and . If any Label subobjects are present for a hop, the ERO Hop Attributes subobject(s) MAY also be inserted after the Label subobjects. The attributes specified in an ERO Hop Attributes subobject apply to the immediately preceding subobject(s) in the ERO subobject list. A document defining a specific Hop Attributes TLV has to describe: after which kinds of ERO subobject they are valid, if ordering of the Hop Attributes subobject and other ERO subobjects associated with the same hop (e.g., Label subobjects) is significant, if ordering is significant, how the attribute is interpreted in association with the preceding ERO subobjects, and any TLV modification rules that might apply. For instance, subobject presence rules can be defined by describing rules similar to , Section 6.1. If a node is processing an ERO Hop Attributes subobject and does not support the handling of the subobject, it will behave as described in when an unrecognized ERO subobject is encountered. This node will return a PathErr with Error Code "Routing Error" and Error Value "Bad EXPLICIT_ROUTE object" with the EXPLICIT_ROUTE object included, truncated (on the left) to the offending unrecognized subobject. When the R bit is set, a node MUST examine the attributes TLV present in the subobject following the rules described in , Section 5.2. When the R bit is not set, a node MUST examine the attributes TLV present in the subobject following the rules described in , Section 4.2. A node processing an ERO Hop Attributes subobject with a Hop Attributes TLV longer than the ERO subobject SHOULD return a PathErr with Error Code "Routing Error" and Error Value "Bad EXPLICIT_ROUTE object" with the EXPLICIT_ROUTE object included, truncated (on the left) to the offending malformed subobject. A processing node MUST NOT originate a Hop Attributes TLV longer than the ERO Hop Attributes subobject. The processing of the Hop Attributes TLVs SHOULD be described in the documents defining them.

In some cases, it is important to determine if an OPTIONAL hop attribute has been processed by a node.

The RRO Hop Attributes subobject is OPTIONAL. If used, it is carried in the RECORD_ROUTE object. The subobject uses the standard format of an RRO subobject. The RRO Hop Attributes subobject is defined as follows:

The Type and Length parameters are as defined in , Section 4.4.1. The Type for the RRO Hop Attributes subobject is 35. The Hop Attributes TLVs are encoded as defined in . Reserved MUST be set to 0 when the subobject is inserted in the RRO, MUST NOT be changed when a node processes the RRO, and MUST be ignored on the node addressed by the preceding RRO subobjects. The processed or additional Hop Attributes TLVs, using the format defined in .

The RRO rules defined in are not changed. The RRO Hop Attributes subobject MUST be pushed after the RRO Attributes subobject (if present) as defined in . The RRO Hop Attributes subobject MAY be present between a pair of subobjects identifying the Label Switching Router (LSR) or links. Unless local policy applies, all such subobjects SHOULD be forwarded unmodified by transit LSRs. It is noted that a node (e.g., a domain edge node) MAY edit the RRO to prune/modify the RRO, including the RRO Hop Attributes subobject before forwarding due to confidentiality policy or other reasons (for instance, RRO size reduction).

To report that an ERO hop attribute has been considered, or to report an additional attribute, an LSR can add a RRO Hop Attributes subobject with the Hop Attributes TLV, which describes the attribute to be reported. The requirement to report compliance MUST be specified in the document that defines the usage of a hop attribute.

The RRO Hop Attributes subobject extends the capability of the RRO Attributes subobject defined in , Section 7.2 by allowing the node to report the attribute value. The mechanism defined in this document is compatible with the RRO Attributes subobject using the following procedures. For LSP attributes signaled in the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES objects, a node SHOULD use the RRO Attributes subobject to report processing of those attributes. For LSP attributes signaled in the ERO Hop Attributes subobject and not in the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES objects, if a node desires to report the attributes, it SHOULD use the RRO Hop Attributes subobject and SHOULD NOT use the RRO Attributes subobject. Ingress nodes not supporting the RRO Hop Attributes subobject will drop the information, as described in , Section 4.4.5. A node can use the RRO Hop Attributes subobject to report an LSP attribute signaled in LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES only if the following conditions are met: The attribute and its corresponding flag is allowed on both the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES and LSP Hop Attributes subobject. The reporting of an LSP attribute signaled in LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES in the RRO Hop Attribute is specified in the document defining that LSP attribute.

IANA manages the "Resource Reservation Protocol (RSVP) Parameters" registry located at <http://www.iana.org/assignments/rsvp&nbhy;parameters>. Per this document, IANA has made an allocation in the Sub-object type 20 EXPLICIT_ROUTE - Type 1 Explicit Route registry. This document introduces a new ERO subobject: Value Description Reference ----------------------------------------------- 35 Hop AttributesThis document,

IANA manages the "Resource Reservation Protocol (RSVP) Parameters" registry located at <http://www.iana.org/assignments/rsvp-parameters>. Per this document, IANA has made an allocation in the Sub-object type 21 ROUTE_RECORD - Type 1 Route Record registry. This value is the same as that in . This document introduces a new RRO subobject: Value Description Reference ----------------------------------------------- 35 Hop AttributesThis document,

IANA manages the "Attribute Flags" registry as part of the "Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters" registry located at <http://www.iana.org/assignments/rsvp-te-parameters>. A new column in the registry is introduced by this document. This column indicates if the flag is permitted to be used in an Attribute Flags TLV carried in the ERO Hop Attributes subobject. The column uses the heading "ERO" and the registry has been updated as follows: BitName AttributeAttributeRROEROReference No. FlagsPathFlagsResv 0End-to-end re-routing Yes No No No This Document 1Boundary re-routing Yes No No No This Document 2Segment-based re-routing Yes No No No This Document 3LSP Integrity Required Yes No No No This Document 4Contiguous LSP Yes No YesNo This Document 5LSP stitching desired Yes No YesNo This Document 6Pre-Planned LSP Flag Yes No No No This Document 7Non-PHP behavior flag Yes No YesNo This Document 8OOB mapping flag Yes No YesNo This Document 9Entropy Label Capability Yes Yes No No This Document 10OAM MEP entities desiredYes Yes YesNo This Document 11OAM MIP entities desiredYes Yes YesNo This Document 12SRLG collection Flag Yes Yes YesNo (TEMPORARY - registered This Document 2014-09-11, expires 2015-09-11) New allocation requests to this registry SHALL indicate the value to be used in the ERO column.

IANA manages the "Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters" registry located at <http://www.iana.org/assignments/rsvp-te-parameters>. The "Attributes TLV Space" registry manages the following attributes, as defined in : TLV Type (T-field value) TLV Name Whether allowed on LSP_ATTRIBUTES object Whether allowed on LSP_REQUIRED_ATTRIBUTES object Per this document, IANA has added the following information for each TLV in the RSVP TLV type identifier registry. Whether allowed on LSP Hop Attributes ERO subobject The existing registry has been modified for existing TLVs as follows. The following abbreviations are used below: Whether allowed on LSP_ATTRIBUTES object. Whether allowed on LSP_REQUIRED_ATTRIBUTES object. Whether allowed on LSP Hop Attributes subobject. TName LSP_ALSP_RAHOP_ARef. ---------------------------------------------------- 1Attribute Flags Yes Yes Yes This Document 2Service ID TLV Yes No No This Document 3OAM Configuration TLVYes Yes No This Document

This document adds a new subobject in the EXPLICIT_ROUTE and the ROUTE_RECORD objects carried in RSVP messages used in MPLS and GMPLS signaling. It builds on mechanisms defined in and and does not introduce any new security. The existing security considerations described in , , , and do apply. As with any RSVP-TE signaling request, the procedures defined in this document permit the transfer and reporting of functional preferences on a specific node. The mechanism added in this document does allow more control of LSP attributes at a given node. A node SHOULD check the hop attributes against its policies and admission procedures as it does with other inputs. A node MAY reject the message using existing RSVP Error Codes like "Policy Control Failure" or "Admission Control Failure". The node MAY also, depending on the specific TLV procedures, modify the requested attribute. This can reveal information about the LSP request and status to anyone with unauthorized access. The mechanism described in this document does not contribute to this issue, which can be only resolved by encrypting the content of the whole signaling message. In addition, the reporting of attributes using the RRO can reveal details about the node that the operator wishes to remain confidential. The same strategy and policies that apply to other RRO subobjects also apply to this new mechanism. It is RECOMMENDED that domain boundary policies take the releasing of RRO hop attributes into consideration.

The authors would like to thank Lou Berger for his directions and Attila Takacs for inspiring . The authors also thank Dirk Schroetter for his contribution to the initial draft versions of this document.