--- 1/draft-ietf-mpls-rsvp-upstream-02.txt 2008-07-09 02:12:35.000000000 +0200 +++ 2/draft-ietf-mpls-rsvp-upstream-03.txt 2008-07-09 02:12:35.000000000 +0200 @@ -1,22 +1,22 @@ Network Working Group R. Aggarwal Internet Draft Juniper Networks -Expiration Date: May 20, 2008 +Expiration Date: January 2009 J. L. Le Roux France Telecom - November 17, 2007 + July 8, 2008 MPLS Upstream Label Assignment for RSVP-TE - draft-ietf-mpls-rsvp-upstream-02.txt + draft-ietf-mpls-rsvp-upstream-03.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -48,21 +48,21 @@ 2 Introduction .......................................... 2 3 RSVP-TE Upstream Label Assignment Capability .......... 3 4 Distributing Upstream-Assigned Labels in RSVP-TE ...... 4 4.1 Procedures ............................................ 4 5 RSVP-TE Tunnel Identifier Exchange .................... 5 6 RSVP-TE Point-to-Multipoint LSPs on a LAN ............. 6 7 Acknowledgements ...................................... 7 8 References ............................................ 7 8.1 Normative References .................................. 7 8.2 Informative References ................................ 8 - 9 Author Information .................................... 8 + 9 Author's Address ...................................... 8 10 Intellectual Property Statement ....................... 8 11 Full Copyright Statement .............................. 9 1. Specification of requirements 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 [RFC2119]. 2. Introduction @@ -74,21 +74,21 @@ This document describes extensions to RSVP-TE that a LSR can use to advertise to its neighboring LSRs whether the LSR supports upstream label assignment. This document also describes extensions to RSVP-TE to distribute upstream-assigned labels. The usage of MPLS upstream label assignment using RSVP-TE for avoiding branch LSR [RSVP-P2MP] traffic replication on a LAN for - RSVP-TE P2MP TE LSPs [RSVP-TE-P2MP] is also described. + RSVP-TE P2MP TE LSPs [RFC4875] is also described. 3. RSVP-TE Upstream Label Assignment Capability According to [MPLS-UPSTREAM], upstream-assigned label bindings MUST NOT be used unless it is known that a downstream LSR supports them. This implies that there MUST be a mechanism to enable a LSR to advertise to its RSVP-TE neighbor LSR(s) its support of upstream- assigned labels. [RSVP-RESTART] defines a CAPABILITY object to be carried within Hello @@ -186,21 +186,21 @@ assigned labels to Rd, Ru MUST include the IF_ID RSVP_HOP object [RFC3473] in Path messages along with the UPSTREAM_ASSIGNED_LABEL Object. Three new TLVs are introduced in the IF_ID RSVP_HOP object [RFC3471] to support RSVP-TE P2MP LSPs, IP Multicast Tunnels and context labels. The TLV value acts as the tunnel identifier. 1. RSVP-TE P2MP LSP TLV. Type = TBD. Value of the TLV is the RSVP-TE P2MP Session Object and optionally the P2MP Sender Template Object - [RSVP-TE-P2MP]. The TLV value identifies the RSVP-TE P2MP LSP. This + [RFC4875]. The TLV value identifies the RSVP-TE P2MP LSP. This mechanism extends RSVP-TE P2P Hierarchy [LSP-HIER] to RSVP-TE P2MP Hierarchy. It allows Ru to tunnel an "inner" P2MP LSP, the label for which is upstream assigned, over an "outer" P2MP LSP that has leaves . The P2MP LSP IF_ID TLV allows Ru to signal to the binding of the inner P2MP LSP to the outer P2MP LSP. The control plane signaling between Ru and for the inner P2MP LSP uses directed RSVP-TE signaling messages as in [LSP-HIER]. 2. IP Multicast Tunnel TLV. Type = TBD. In this case the TLV value is a tuple. Source Address is @@ -226,26 +226,26 @@ Currently the usage of the context label TLV is limited only to RSVP- TE P2MP LSPs on a LAN as specified in the next section. The context label TLV MUST NOT be used for any other purposes. 6. RSVP-TE Point-to-Multipoint LSPs on a LAN This section describes one application of upstream label assignment using RSVP-TE. Further applications are to be described in separate documents. - [RSVP-TE-P2MP] describes how to setup RSVP-TE P2MP LSPs. On a LAN the - solution described in [RSVP-TE-P2MP] relies on "ingress replication". - A LSR on a LAN (say Il), that is a branch LSR for a P2MP LSP, (say - Ru) sends a separate copy of a packet that it receives on the P2MP - LSP to each of the downstream LSRs on the LAN (say that - are adjacent to it in the P2MP LSP. + [RFC4875] describes how to setup RSVP-TE P2MP LSPs. On a LAN the + solution described in [RFC4875] relies on "ingress replication". A + LSR on a LAN (say Il), that is a branch LSR for a P2MP LSP, (say Ru) + sends a separate copy of a packet that it receives on the P2MP LSP to + each of the downstream LSRs on the LAN (say that are + adjacent to it in the P2MP LSP. In order to increase efficiency of bandwidth utilization, it is desirable for Ru to send a single copy of the packet for the P2MP LSP on the LAN, when there are multiple downstream routers on the LAN that are adjacent in that P2MP LSP. This requires that each of must be able to associate the label L, used by Ru to transmit packets for the P2MP LSP on the LAN, with that P2MP LSP. It is possible to achieve this using RSVP-TE upstream-assigned labels with the following procedures. Assume that Ru and support upstream label assignment. @@ -283,48 +283,47 @@ 8. References 8.1. Normative References [RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon, RFC 3031. [MPLS-UPSTREAM] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream Label Assignment and Context Specific Label Space", draft-ietf-mpls- - upstream-label-03.txt + upstream-label-05.txt [MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter, - draft-ietf-mpls-codepoint-07.txt + draft-ietf-mpls-codepoint-08.txt [RFC3209] Awduche et. al." "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. [RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC3473] Berger, L., Editor, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling - Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. [RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471 January 2003. [RSVP-RESTART] A. Satyanarayana et. al., "Extensions to GMPLS RSVP Graceful Restart", draft-ietf-ccamp-rsvp-restart-ext-02.txt 8.2. Informative References [MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs", - draft-ietf-l3vpn-2547bis-mcast-02.txt + draft-ietf-l3vpn-2547bis-mcast-06.txt - [RSVP-TE-P2MP] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors], - "Extensions to RSVP-TE for Point to Multipoint TE LSPs", draft-ietf- - mpls-rsvp-te-p2mp-07.txt + [RFC4875] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors], + "Extensions to RSVP-TE for Point to Multipoint TE LSPs", RFC 4875 9. Author's Address Rahul Aggarwal Juniper Networks 1194 North Mathilda Ave. Sunnyvale, CA 94089 Phone: +1-408-936-2720 Email: rahul@juniper.net @@ -354,21 +353,21 @@ http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. 11. Full Copyright Statement - Copyright (C) The IETF Trust (2007). This document is subject to the + Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.