Domain Subobjects for Resource ReserVation Protocol - Traffic Engineering (RSVP-TE)Huawei Technologies India Pvt LtdLeela PalaceBangaloreKarnataka560008INDIAdhruv.dhody@huawei.comHuawei Technologies India Pvt LtdLeela PalaceBangaloreKarnataka560008INDIAudayasree.palle@huawei.comHuawei Technologies India Pvt LtdLeela PalaceBangaloreKarnataka560008INDIAvenugopalreddyk@huawei.comCTTC - Centre Tecnologic de Telecomunicacions de CatalunyaAv. Carl Friedrich Gauss n7CastelldefelsBarcelona 08860SPAINramon.casellas@cttc.es
Routing
CCAMP Working GroupThe RSVP-TE specification and the GMPLS extensions to RSVP-TE allow abstract nodes and resources to be explicitly included in a path setup. Further Exclude Routes extensions allow abstract nodes and resources to be explicitly excluded in a path setup. This document specifies new subobjects to include or exclude domains during path setup where domain is a collection of network elements within a common sphere of address management or path computational responsibility (such as an IGP area or an AS (4-Byte)). Note that the use of Autonomous Number (AS) (2-Byte) as an abstract node representing domain is already defined in and .The RSVP-TE specification and the GMPLS extensions to RSVP-TE allow abstract nodes and resources to be explicitly included in a path setup using the Explicit Route Object (ERO). Further Exclude Routes extensions allow abstract nodes or resources to be excluded from the whole path using the Exclude Route object (XRO). To exclude certain abstract nodes or resources between a specific pair of abstract nodes present in an ERO, a subobject Explicit Exclusion Route Subobject (EXRS) is used. already describes the notion of abstract nodes, where an abstract node is a group of nodes whose internal topology is opaque to the ingress node of the LSP. It further defines a subobject for Autonomous Systems (AS) (2-Byte). This document extends the notion of abstract nodes by adding new subobjects for IGP Areas and 4-byte AS numbers. These subobjects MAY be included in Explicit Route Object (ERO), Exclude Route object (XRO) or Explicit Exclusion Route Subobject (EXRS).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 .The following terminology is used in this document.Autonomous System.As per , any collection of network elements within a common sphere of address management or path computational responsibility. Examples of domains include Interior Gateway Protocol (IGP) areas and Autonomous Systems (ASs).Explicit Route ObjectExplicit Exclusion Route SubobjectInterior Gateway Protocol. Either of the two routing protocols, Open Shortest Path First (OSPF) or Intermediate System to Intermediate System (IS-IS).Intermediate System to Intermediate System.Open Shortest Path First.Path Computation Element. An entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints.Path Computation Element Protocol.Resource Reservation ProtocolTraffic Engineering Label Switched Path.Exclude Route Object and define domain as a separate administrative or geographic environment within the network. A domain may be further defined as a zone of routing or computational ability. Under these definitions a domain might be categorized as an Autonomous System (AS) or an Interior Gateway Protocol (IGP) area.As per , an abstract node is a group of nodes whose internal topology is opaque to the ingress node of the LSP. Using this concept of abstraction, an explicitly routed LSP can be specified as a sequence of IP prefixes or a sequence of Autonomous Systems. In this document we extend the notion to include IGP area and 4-Byte AS number.The sub-objects MAY appear in RSVP-TE, notably in - Explicit Route Object (ERO): As per , an explicit route is a particular path in the network topology including abstract nodes (domains). Exclude Route Object (XRO): As per , the exclude route identifies a list of abstract nodes (domains) that should not be traversed along the path of the LSP being established. Explicit Exclusion Route Subobject (EXRS): As per , used to specify exclusion of certain abstract nodes between a specific pair of nodes. EXRS are a subobject inside the ERO. These subobjects are used to specify the domains that must be excluded between two abstract nodes.As stated in , an explicit route is a particular path in the network topology. In addition to the ability to identify specific nodes along the path, an explicit route can identify a group of nodes (abstract nodes) that must be traversed along the path. Some subobjects are defined in , , , and but new subobjects related to domains are needed.The following subobject types are used in ERO.This document extends the above list to support 4-Byte AS numbers and IGP Areas. already defines 2-Byte AS number.To support 4-Byte AS numbers as per , the following subobject is defined: L: The L bit is an attribute of the subobject as defined in . Type: (TBA by IANA) indicating a 4-Byte AS Number. Length: 8 (Total length of the subobject in bytes). Reserved: Zero at transmission, ignored at receipt. AS-ID: The 4-Byte AS Number. Note that if 2-Byte AS numbers are in use, the low order bits (16 through 31) should be used and the high order bits (0 through 15) should be set to zero. Since the length and format of Area-id is different for OSPF and ISIS, the following two subobjects are defined: For OSPF, the area-id is a 32 bit number. The subobject is encoded as follows: L: The L bit is an attribute of the subobject as define in . Type: (TBA by IANA) indicating 4-Byte OSPF Area ID. Length: 8 (Total length of the subobject in bytes). Reserved: Zero at transmission, ignored at receipt. OSPF Area Id: The 4-Byte OSPF Area ID. For IS-IS, the area-id is of variable length and thus the length of the subobject is variable. The Area-id is as described in IS-IS by ISO standard . The subobject is encoded as follows:L: The L bit is an attribute of the subobject as define in . Type: (TBA by IANA) indicating IS-IS Area ID. Length: Variable. As per , the total length of the subobject in bytes, including the L, Type and Length fields. The Length MUST be at least 4, and MUST be a multiple of 4.Area-Len: Variable (Length of the actual (non-padded) IS-IS Area Identifier in bytes; Valid values are from 2 to 11 inclusive). Reserved: Zero at transmission, ignored at receipt. IS-IS Area Id: The variable-length IS-IS area identifier. Padded with trailing zeroes to a four-byte boundary. The new subobjects to support 4-Byte AS and IGP (OSPF / ISIS) Area MAY also be used in the ERO to specify an abstract node (a group of nodes whose internal topology is opaque to the ingress node of the LSP). All the rules of processing (for example Next Hop Selection, L bit processing, unrecognized subobjects etc) are as per the . As stated in , the exclude route identifies a list of abstract nodes that should not be traversed along the path of the LSP being established. Some subobjects are defined in , , and but new subobjects related to domains are needed.The following subobject types are used in XRO.This document extends the above list to support 4-Byte AS numbers and IGP Areas. and already define a 2-Byte AS number.To support 4-Byte AS numbers as per , the following subobject is defined: The meaning of the L bit, similar to , is as follows: 0 indicates that the abstract node (AS) specified MUST be excluded. 1 indicates that the abstract node (AS) specified SHOULD be avoided.The meaning of all the other elements (Type, Length, Reserved and 4-Byte AS Id) is same as explained above in .Since the length and format of Area-id is different for OSPF and ISIS, the following two subobjects are defined: For OSPF, the area-id is a 32 bit number. The subobject is encoded as follows: The meaning of the L bit, similar to , is as follows: 0 indicates that the abstract node (OSPF Area) specified MUST be excluded. 1 indicates that the abstract node (OSPF Area) specified SHOULD be avoided.The meaning of all the other elements (Type, Length, Reserved and OSPF Area Id) is same as explained above in .For IS-IS, the area-id is of variable length and thus the length of the subobject is variable. The Area-id is as described in IS-IS by ISO standard . The subobject is encoded as follows:The meaning of the L bit, similar to , is as follows: 0 indicates that the abstract node (IS-IS Area) specified MUST be excluded. 1 indicates that the abstract node (IS-IS Area) specified SHOULD be avoided.The meaning of all the other elements (Type, Length, Area-Len, Reserved and IS-IS Area Id) is same as explained above in .The new subobjects to support 4-Byte AS and IGP (OSPF / ISIS) Area MAY also be used in the XRO to specify exclusion of an abstract node (a group of nodes whose internal topology is opaque to the ingress node of the LSP). All the rules of processing are as per the . As per , the Explicit Exclusion Route defines abstract nodes or resources that must not or should not be used on the path between two inclusive abstract nodes or resources in the explicit route. EXRS is an ERO subobject that contains one or more subobjects of its own, called EXRS subobjects.The EXRS subobject may carry any of the subobjects defined for XRO, thus the new subobjects to support 4-Byte AS and IGP (OSPF / ISIS) Area MAY also be used in the EXRS. The meanings of the fields of the new XRO subobjects are unchanged when the subobjects are included in an EXRS, except that scope of the exclusion is limited to the single hop between the previous and subsequent elements in the ERO.All the rules of processing are as per the . The domain subobjects to be used in Path Computation Element Protocol (PCEP) are referred to in . Note that the new domain subobjects follow the principle that subobjects used in PCEP are identical to the subobjects used in RSVP-TE. In an inter-area LSP path setup where the ingress and the egress belong to different IGP areas within the same AS, the domain subobjects MAY be represented using an ordered list of IGP area subobjects in an ERO. The AS number MAY be skipped, as area information is enough to uniquely identify a domain.As shown in , AS subobject is optional. So the signaling at Ingress MAY be - ERO:(A1, ABF1, Area B, Area C, Egress); or ERO:(A1, ABF1, AS 100, Area B, AS 100, Area C, Egress). The AS subobject is optional and it MAY be skipped. An RSVP-TE implementation should be able to understand both notations and there is no change in the processing rules as mentioned in . In an inter-AS LSP path setup where the ingress and the egress belong to different AS, the domain subobjects MAY be represented using an ordered list of AS subobjects in an ERO. As shown in , where each AS has a single IGP area (area 0), the area subobject MAY be skipped as AS is enough to uniquely identify a domain. So the signaling at Ingress - ERO:(A1, A2, AS B, AS C, Egress); or ERO:(A1, A2, AS B, Area 0, AS C, Area 0, Egress). Area subobject is optional and it MAY be skipped. An RSVP-TE implementation should be able to understand both notations and there is no change in the processing rules as mentioned in .Note that to get a domain disjoint path, the ingress may also signal the backup path with -XRO:(AS B)As shown in , where AS 200 is made up of multiple areas, the signaling MAY include both AS and Area subobject to uniquely identify a domain.As shown in the signaling at Ingress - ERO:(X1, AS 200, Area D, Area B, Area C, Egress). The combination of both an AS and an Area uniquely identifies a domain, note that an Area domain identifier always belongs to the previous AS that appears before it or, if no AS subobjects are present, it is assumed to be the current AS. Also note that there are no changes in the processing rules as mentioned in with respect to subobjects. IANA registry: RSVP PARAMETERSSubsection: Class Names, Class Numbers, and Class TypesIANA is requested to add further subobjects to the existing entry for:Security considerations for MPLS-TE and GMPLS signaling are covered in and . This document does not introduce any new messages or any substantive new processing, and so those security considerations continue to apply. The route exclusion security consideration are covered in and continue to apply. We would like to thank Lou Berger, George Swallow, Chirag Shah, Reeja Paul and Sandeep Boina for their useful comments and suggestions.Standard Representation Of Domain Sequence. (draft-ietf-pce-pcep-domain-sequence-02)
Intermediate system to Intermediate system routeing information
exchange protocol for use in conjunction with the Protocol for
providing the Connectionless-mode Network Service (ISO
8473)
ISO