draft-ietf-mpls-ldp-upstream-01.txt   draft-ietf-mpls-ldp-upstream-02.txt 
Network Working Group R. Aggarwal Network Working Group R. Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: September 2007 Expiration Date: May 21, 2008
J. L. Le Roux J. L. Le Roux
France Telecom France Telecom
November 18, 2007
MPLS Upstream Label Assignment for LDP MPLS Upstream Label Assignment for LDP
draft-ietf-mpls-ldp-upstream-01.txt draft-ietf-mpls-ldp-upstream-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of 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 Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 10 skipping to change at page 2, line 10
This document describes procedures for distributing upstream-assigned This document describes procedures for distributing upstream-assigned
labels for Label Distribution Protocol (LDP). It also describes how labels for Label Distribution Protocol (LDP). It also describes how
these procedures can be used for avoiding branch LSR traffic these procedures can be used for avoiding branch LSR traffic
replication on a LAN for LDP point-to-multipoint (P2MP)LSPs. replication on a LAN for LDP point-to-multipoint (P2MP)LSPs.
Table of Contents Table of Contents
1 Specification of requirements ......................... 2 1 Specification of requirements ......................... 2
2 Introduction .......................................... 2 2 Introduction .......................................... 2
3 LDP Upstream Label Assignment Capability .............. 3 3 LDP Upstream Label Assignment Capability .............. 3
4 Distributing Upstream-Assigned Labels in LDP .......... 3 4 Distributing Upstream-Assigned Labels in LDP .......... 4
4.1 Procedures ............................................ 4 4.1 Procedures ............................................ 4
5 LDP Tunnel Identifier Exchange ........................ 5 5 LDP Tunnel Identifier Exchange ........................ 5
6 LDP Point-to-Multipoint LSPs on a LAN ................. 6 6 LDP Point-to-Multipoint LSPs on a LAN ................. 6
7 Acknowledgements ...................................... 8 7 IANA Considerations ................................... 8
8 References ............................................ 8 8 Acknowledgements ...................................... 8
8.1 Normative References .................................. 8 9 References ............................................ 9
8.2 Informative References ................................ 9 9.1 Normative References .................................. 9
9 Author Information .................................... 9 9.2 Informative References ................................ 9
10 Intellectual Property Statement ....................... 9 10 Author's Address ...................................... 10
11 Full Copyright Statement .............................. 10 11 Intellectual Property Statement ....................... 10
12 Full Copyright Statement .............................. 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
skipping to change at page 3, line 27 skipping to change at page 3, line 29
peers, its support of upstream label assignment. This parameter peers, its support of upstream label assignment. This parameter
follows the format and procedures for exchanging Capability follows the format and procedures for exchanging Capability
Parameters defined in [LDP-CAP]. Parameters defined in [LDP-CAP].
Following is the format of the LDP Upstream Label Assignment Following is the format of the LDP Upstream Label Assignment
Capability Parameter: Capability Parameter:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1|0| Upstream Lbl Ass Cap(IANA)| Length (= 5) | |1|0| Upstream Lbl Ass Cap(IANA)| Length (= 1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1| Reserved | |1| Reserved |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
If a LSR includes the Upstream Label Assignment Capability in LDP If a LSR includes the Upstream Label Assignment Capability in LDP
Initialization Messages it implies that the LSR is capable of both Initialization Messages it implies that the LSR is capable of both
distributing upstream-assigned label bindings and receiving upstream- distributing upstream-assigned label bindings and receiving upstream-
assigned label bindings. The reserved bits MUST be set to zero on assigned label bindings. The reserved bits MUST be set to zero on
transmission and ignored on receipt. The Upstream Label Assignment transmission and ignored on receipt. The Upstream Label Assignment
Capability Parameter can be exchanged only in LDP initialization Capability Parameter can be exchanged only in LDP initialization
skipping to change at page 8, line 7 skipping to change at page 8, line 15
3. The selected upstream LSR U is the LSR that has the number H. 3. The selected upstream LSR U is the LSR that has the number H.
This allows for load balancing of a set of LSPs among a set of This allows for load balancing of a set of LSPs among a set of
candidate upstream LSRs, while ensuring that on a LAN interface a candidate upstream LSRs, while ensuring that on a LAN interface a
single upstream LSR is selected. It is also to be noted that the single upstream LSR is selected. It is also to be noted that the
procedures in this section can still be used by Rd and Ru if other procedures in this section can still be used by Rd and Ru if other
LSRs on the LAN do not support upstream label assignment. Ingress LSRs on the LAN do not support upstream label assignment. Ingress
replication and downstream label assignment will continue to be used replication and downstream label assignment will continue to be used
for LSRs that do not support upstream label assignment. for LSRs that do not support upstream label assignment.
7. Acknowledgements 7. IANA Considerations
This document defines a new LDP Upstream Label Assignment Capability
Parameter. IANA is requested to assign the value 0x0507 to this
Parameter.
This document defines a new LDP Upstream-Assigned Label Request TLV,
IANA is requested to assign the type value of this TLV.
This document defines a new LDP Upstream-Assigned Label TLV, IANA is
requested to assign the type value of this TLV.
This document defines three new Interface ID TLVs:
- RSVP-TE P2MP LSP TLV
- IP Multicast Tunnel TLV
- MPLS Context Label TLV
IANA is requested to assign the type values of these TLVs.
8. Acknowledgements
Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei and Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei and
Thomas Morin for their comments. The hashing algorithm used on LAN Thomas Morin for their comments. The hashing algorithm used on LAN
interfaces is taken from [MLDP]. interfaces is taken from [MLDP].
8. References 9. References
8.1. Normative References 9.1. Normative References
[RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon, [RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon,
RFC 3031. RFC 3031.
[MPLS-UPSTREAM] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream [MPLS-UPSTREAM] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream
Label Assignment and Context Specific Label Space", draft-ietf-mpls- Label Assignment and Context Specific Label Space", draft-ietf-mpls-
upstream-label-02.txt upstream-label-03.txt
[MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter, [MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter,
draft-ietf-mpls-codepoint-01.txt draft-ietf-mpls-codepoint-07.txt
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
[RFC3472] Ashwood-Smith, P. and L. Berger, Editors, " Generalized [RFC3472] Ashwood-Smith, P. and L. Berger, Editors, " Generalized
Multi-Protocol Label Switching (GMPLS) Signaling - Constraint-based Multi-Protocol Label Switching (GMPLS) Signaling - Constraint-based
Routed Label Distribution Protocol (CR-LDP) Extensions", RFC 3472, Routed Label Distribution Protocol (CR-LDP) Extensions", RFC 3472,
January 2003. January 2003.
[RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label [RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", RFC 3471 January Switching (GMPLS) Signaling Functional Description", RFC 3471 January
2003. 2003.
[RFC3036] L. Andersson, et. al., "LDP Specification", January 2001. [RFC3036] L. Andersson, et. al., "LDP Specification", January 2001.
8.2. Informative References 9.2. Informative References
[MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs", [MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs",
draft-ietf-l3vpn-2547bis-mcast-02.txt draft-ietf-l3vpn-2547bis-mcast-02.txt
[RSVP-TE-P2MP] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors], [RSVP-TE-P2MP] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors],
"Extensions to RSVP-TE for Point to Multipoint TE LSPs", draft-ietf- "Extensions to RSVP-TE for Point to Multipoint TE LSPs", draft-ietf-
mpls-rsvp-te-p2mp-07.txt mpls-rsvp-te-p2mp-07.txt
[MLDP] I. Minei et. al, "Label Distribution Protocol Extensions for [MLDP] I. Minei et. al, "Label Distribution Protocol Extensions for
Point-to-Multipoint Label Switched Paths", draft-etf-mpls-ldp- Point-to-Multipoint Label Switched Paths", draft-etf-mpls-ldp-
p2mp-02.txt p2mp-02.txt
[LDP-CAP] B. Thomas, et. al., "LDP Capabilities", draft-thomas-mpls- [LDP-CAP] B. Thomas, et. al., "LDP Capabilities", draft-thomas-mpls-
ldp-capabilities-02.txt ldp-capabilities-02.txt
9. Author Information 10. Author's Address
Rahul Aggarwal Rahul Aggarwal
Juniper Networks Juniper Networks
1194 North Mathilda Ave. 1194 North Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Phone: +1-408-936-2720
Email: rahul@juniper.net Email: rahul@juniper.net
Jean-Louis Le Roux Jean-Louis Le Roux
France Telecom France Telecom
2, avenue Pierre-Marzin 2, avenue Pierre-Marzin
22307 Lannion Cedex 22307 Lannion Cedex
France France
E-mail: jeanlouis.leroux@orange-ftgroup.com E-mail: jeanlouis.leroux@orange-ftgroup.com
10. Intellectual Property Statement 11. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 10, line 14 skipping to change at page 11, line 5
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
11. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to the Copyright (C) The IETF Trust (2007). This document is subject to the
rights, licenses and restrictions contained in BCP 78, and except as rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights. set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 16 change blocks. 
20 lines changed or deleted 47 lines changed or added

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