--- 1/draft-ietf-mpls-nodeid-subobject-04.txt 2006-02-05 00:42:00.000000000 +0100 +++ 2/draft-ietf-mpls-nodeid-subobject-05.txt 2006-02-05 00:42:00.000000000 +0100 @@ -1,21 +1,21 @@ Jean Philippe Vasseur (Editor) Zafar Ali Siva Sivabalan Cisco Systems, Inc. IETF Internet Draft Expires: July, 2005 January, 2005 - draft-ietf-mpls-nodeid-subobject-04.txt + draft-ietf-mpls-nodeid-subobject-05.txt Definition of an RRO node-id subobject Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Working documents of the Internet Engineering Task Force (IETF), its @@ -208,22 +208,22 @@ with existing mechanisms. In this document, we define extensions to and describe the use of RSVP [RSVP, RSVP-TE] to solve the above-mentioned problem. 3. Signaling node-ids in RROs As mentioned above, the limitation that we need to address is the generality of the contents of the RRO IPv4 and IPv6 subobjects, as defined in [RSVP-TE].[RSVP-TE] defines the IPv4 and IPv6 RRO subobjects -along with two flags (namely the ôLocal Protection Availableö and -ôLocal protection in useö bits). Moreover, other bits have been +along with two flags (namely the "Local Protection Available" and +"Local protection in use" bits). Moreover, other bits have been specified in [FAST-REROUTE] and [SOFT-PREEMPTION]. In this document, we define the following new flag: Node-id: 0x20 When set, this indicates that the address specified in the RRO's IPv4 or IPv6 subobject is a node-id address, which refers to the "Router Address" as defined in [OSPF-TE], or "Traffic Engineering Router ID" as defined in [ISIS-TE]. A node MUST use @@ -338,47 +338,47 @@ [RSVP-TE] Awduche, et al, "Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. Informative references [FAST-REROUTE] Ping Pan, et al, "Fast Reroute Extensions to RSVP-TE for LSP Tunnels", draft-ietf-mpls-rsvp-lsp-fastreroute-07.txt. Work in progress. -[OSPF-TE] Katz et al., ôTraffic Engineering (TE) Extensions to OSPF -Version 2ö, RFC3630. +[OSPF-TE] Katz et al., "Traffic Engineering (TE) Extensions to OSPF +Version 2", RFC3630. -[ISIS-TE] Smit et al., ôIntermediate System to Intermediate System (IS- +[ISIS-TE] Smit et al., "Intermediate System to Intermediate System (IS- IS) - Extensions for Traffic Engineering (TE)IS-IS extensions for -Traffic Engineeringö, RFC3784. +Traffic Engineering", RFC3784. Vasseur, Ali and Sivabalan 7 -[INTER-AREA-TE-REQS] Le Roux, Vasseur, Boyle et al., ôRequirements for -Inter-Area MPLS Traffic Engineeringö, draft-ietf-tewg-interarea-mpls-te- +[INTER-AREA-TE-REQS] Le Roux, Vasseur, Boyle et al., "Requirements for +Inter-Area MPLS Traffic Engineering", draft-ietf-tewg-interarea-mpls-te- req-03.txt. Work in progress. [INTER-AS-TE-REQS] Zhang, Vasseur et al, "MPLS Inter-AS Traffic Engineering requirements", draft-tewg-interas-te-req-09.txt. Work in progress. [INTER-DOMAIN-SIG] Ayyangar and Vasseur, "Inter domain GMPLS Traffic -Engineering - RSVP-TE extensionsö, draft-ayyangar-ccamp-inter-domain- +Engineering - RSVP-TE extensions", draft-ayyangar-ccamp-inter-domain- rsvp-te-01.txt. Work in progress. [LOOSE-PATH-REOPT] Vasseur et al. "Reoptimization of MPLS Traffic Engineering loosely routed LSP", . Work in progress. -[SOFT-PREEMPTION] Meyer, Maddux, Vasseur, Villamizar and Birjandi. ôMPLS -Traffic Engineering Soft preemptionö, draft-ietf-mpls-soft-preemption- +[SOFT-PREEMPTION] Meyer, Maddux, Vasseur, Villamizar and Birjandi. "MPLS +Traffic Engineering Soft preemption", draft-ietf-mpls-soft-preemption- 03.txt. Work in progress. Authors' Addresses: Jean Philippe Vasseur Cisco Systems, Inc. 300 Beaver Brook Road Boxborough , MA - 01719 USA Email: jpv@cisco.com