draft-ietf-mpls-ldp-upstream-02.txt   draft-ietf-mpls-ldp-upstream-03.txt 
Network Working Group R. Aggarwal Network Working Group R. Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: May 21, 2008 Expiration Date: January 2009
J. L. Le Roux J. L. Le Roux
France Telecom France Telecom
November 18, 2007 July 8, 2008
MPLS Upstream Label Assignment for LDP MPLS Upstream Label Assignment for LDP
draft-ietf-mpls-ldp-upstream-02.txt draft-ietf-mpls-ldp-upstream-03.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 6, line 7 skipping to change at page 6, line 7
[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. Three Mapping messages along with the Upstream Assigned Label TLV. Three
new Interface ID TLVs are introduced to support RSVP-TE P2MP LSPs, IP new Interface ID TLVs are introduced to support RSVP-TE P2MP LSPs, IP
Multicast Tunnels and context labels. The TLV value acts as the Multicast Tunnels and context labels. The TLV value acts as the
tunnel identifier. tunnel identifier.
1. RSVP-TE P2MP LSP TLV. Type = TBD. Value of the TLV is the RSVP-TE 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 P2MP Session Object and optionally the P2MP Sender Template Object
[RSVP-TE-P2MP]. The TLV value identifies the RSVP-TE P2MP LSP. It [RFC4875]. The TLV value identifies the RSVP-TE P2MP LSP. It allows
allows Ru to tunnel an "inner" LDP P2MP LSP, the label for which is Ru to tunnel an "inner" LDP P2MP LSP, the label for which is upstream
upstream assigned, over an "outer" RSVP-TE P2MP LSP that has leaves 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 P2MP LSP IF_ID TLV allows Ru to signal to
<Rd1...Rdn> the binding of the inner LDP P2MP LSP to the outer RSVP- <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> TE P2MP LSP. The control plane signaling between Ru and <Rd1...Rdn>
for the inner P2MP LSP uses targeted LDP signaling messages for the inner P2MP LSP uses targeted LDP signaling messages
2. IP Multicast Tunnel TLV. Type = TBD. In this case the TLV value is 2. IP Multicast Tunnel TLV. Type = TBD. In this case the TLV value is
a <Source Address, Multicast Group Address> tuple. Source Address is a <Source Address, Multicast Group Address> tuple. Source Address is
the IP address of the root of the tunnel i.e. Ru, and Multicast Group the IP address of the root of the tunnel i.e. Ru, and Multicast Group
Address is the Multicast Group Address used by the tunnel. Address is the Multicast Group Address used by the tunnel.
skipping to change at page 9, line 14 skipping to change at page 9, line 14
9. References 9. References
9.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-03.txt upstream-label-06.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-07.txt draft-ietf-mpls-codepoint-10.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.
9.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-06.txt
[RSVP-TE-P2MP] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors], [RFC4875] 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", RFC 4875
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-05.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
10. Author's Address 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
 End of changes. 9 change blocks. 
13 lines changed or deleted 12 lines changed or added

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