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

This html diff was produced by rfcdiff 1.37c. The latest version is available from http://tools.ietf.org/tools/rfcdiff/