--- 1/draft-ietf-mpls-ldp-upstream-04.txt 2010-01-30 01:10:44.000000000 +0100 +++ 2/draft-ietf-mpls-ldp-upstream-05.txt 2010-01-30 01:10:44.000000000 +0100 @@ -1,22 +1,22 @@ Network Working Group R. Aggarwal Internet Draft Juniper Networks -Expiration Date: January 2010 +Expiration Date: July 2010 J. L. Le Roux France Telecom - July 12, 2009 + January 29, 2010 MPLS Upstream Label Assignment for LDP - draft-ietf-mpls-ldp-upstream-04.txt + draft-ietf-mpls-ldp-upstream-05.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. @@ -26,28 +26,32 @@ material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright and License Notice - Copyright (c) 2009 IETF Trust and the persons identified as the + Copyright (c) 2010 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 in effect on the date of - publication of this document (http://trustee.ietf.org/license-info). - Please review these documents carefully, as they describe your rights - and restrictions with respect to this document. + 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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format @@ -65,24 +69,24 @@ 1 Specification of requirements ......................... 3 2 Introduction .......................................... 3 3 LDP Upstream Label Assignment Capability .............. 3 4 Distributing Upstream-Assigned Labels in LDP .......... 4 4.1 Procedures ............................................ 5 5 LDP Tunnel Identifier Exchange ........................ 6 6 LDP Point-to-Multipoint LSPs on a LAN ................. 7 7 IANA Considerations ................................... 9 8 Acknowledgements ...................................... 9 - 9 References ............................................ 9 - 9.1 Normative References .................................. 9 + 9 References ............................................ 10 + 9.1 Normative References .................................. 10 9.2 Informative References ................................ 10 -10 Author's Address ...................................... 10 +10 Author's Address ...................................... 11 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 This document describes procedures for distributing upstream-assigned labels [RFC5331] for Label Distribution Protocol (LDP). These @@ -214,34 +218,39 @@ this case the fact that L is upstream-assigned is determined by Rd by the tunnel on which the packet is received. There must be a mechanism for Ru to inform Rd that a particular tunnel from Ru to Rd will be used by Ru for transmitting MPLS packets with upstream-assigned MPLS labels. When LDP is used for upstream label assignment, the Interface ID TLV [RFC3472] is used for signaling the Tunnel Identifier. If Ru uses an IP or MPLS tunnel to transmit MPLS packets with upstream assigned labels to Rd, Ru MUST include the Interface ID TLV in the Label - Mapping messages along with the Upstream Assigned Label TLV. Four - new Interface ID TLVs are introduced to support RSVP-TE P2MP LSPs, - LDP P2MP LSPs, IP Multicast Tunnels and context labels. The TLV value - acts as the tunnel identifier. + Mapping messages along with the Upstream Assigned Label TLV. The + IPv4 Next/Previous Hop Address and the Logical Interface ID fields in + the Interface ID TLV SHOULD be set to 0 by the sender and ignored by + the receiver. - 1. RSVP-TE P2MP LSP TLV. Type = TBD. Value of he TLV is the RSVP-TE - P2MP Session Object and optionally the P2MP Sender Template Object - [RFC4875]. The TLV value identifies the RSVP-TE P2MP LSP. It allows - Ru to tunnel an "inner" LDP P2MP LSP, the label for which is upstream - assigned, over an "outer" RSVP-TE P2MP LSP that has leaves - . The P2MP LSP IF_ID TLV allows Ru to signal to - the binding of the inner LDP P2MP LSP to the outer RSVP- - TE P2MP LSP. The control plane signaling between Ru and - for the inner P2MP LSP uses targeted LDP signaling messages + Four new Interface ID TLVs are introduced to support RSVP-TE P2MP + LSPs, LDP 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 + as carried in the + RSVP-TE P2MP LSP SESSION Object [RFC4875]. The TLV value identifies + the RSVP-TE P2MP LSP. It allows Ru to tunnel an "inner" LDP P2MP LSP, + the label for which is upstream assigned, over an "outer" RSVP-TE + P2MP LSP that has leaves . The P2MP LSP IF_ID TLV allows + Ru to signal to the binding of the inner LDP P2MP LSP to + the outer RSVP-TE P2MP LSP. The control plane signaling between Ru + and for the inner P2MP LSP uses targeted LDP signaling + messages 2. LDP P2MP LSP TLV. Type = TBD. Value of the TLV is the LDP P2MP FEC as defined in [MLDP]. The TLV value identifies the LDP P2MP LSP. It allows Ru to tunnel an "inner" LDP P2MP LSP, the label for which is upstream assigned, over an "outer" LDP P2MP LSP that has leaves . The P2MP LSP IF_ID TLV allows Ru to signal to the binding of the inner LDP P2MP LSP to the outer LDP- P2MP LSP. The control plane signaling between Ru and for the inner P2MP LSP uses targeted LDP signaling messages