1. Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 MPLS Upstream Label Assignment for RSVP- TE and LDP draft-raggarwa-mpls-rsvp-ldp-upstream- 00.txt Rahul Aggarwal (rahul@juniper.net)rahul@juniper.net J. L. Le Roux (jeanlouis.leroux@francetelecom.com)

2. 2 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Scope  Upstream label assignment capability  Distributing upstream assigned labels for RSVP-TE RSVP-TE P2MP Hierarchy  Distributing upstream assigned labels for LDP  Tunnel identifier exchange  Avoiding branch LSR traffic replication on a LAN for RSVP-TE and LDP P2MP LSPs

3. 3 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Upstream Label Assignment Capability  Upstream assigned labels must not be distributed unless its known that the downstream LSR supports them draft-raggarwa-mpls-upstream-label  Signaled in CAPABILITY object in RSVP-TE Hello messages Implies that a LSR may exchange Hello messages with another LSR before exchanging any other messages  Upstream label assignment capability TLV is introduced in LDP Initialization messages

4. 4 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Distributing Upstream Assigned Labels for RSVP-TE  A new UPSTREAM_ASSIGNED_LABEL object Included in RSVP-TE Path messages  A LSR that receives an UPSTREAM_ASSIGNED_LABEL object in a Path messages must not include the LABEL object in the RESV message LSRs Ru and Rd for a LSP that is bound to FEC F, MUST use either downstream-assigned label distribution or upstream-assigned label distribution,for FEC F, but NOT both, for packets that are to be transmitted on the LSP from Ru to Rd.

5. 5 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Distributing Upstream Assigned Labels for LDP  Upstream-Assigned Label Request TLV Included in Label Request Messages  Upstream-Assigned Label TLV Included in Label advertise, release and withdraw messages

6. 6 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Tunnel Identifier Exchange  Mechanism for Ru to inform Rd that a particular tunnel will be used by Ru to transmit MPLS packets with upstream assigned labels to Rd  RSVP-TE IF_ID_HOP object RSVP-TE P2MP LSP TLV Extends RSVP-TE P2P Hierarchy to P2MP LSPs. Signals the binding of an “inner P2MP LSP” to an “outer P2MP LSP” IP Multicast Tunnel TLV  LDP Interface ID TLV

7. 7 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Avoiding Branch LSR Replication on a LAN for P2MP LSPs  P2MP RSVP-TE and LDP LSPs rely on branch LSR replication on a LAN For bandwidth optimization it is desirable for a branch LSR to transmit a single copy of a packet on a LAN  Upstream label assignment allows a branch LSR, Ru, to transmit a single copy of a MPLS packet to on a P2MP LSP on a LAN  Ru assigns an upstream assigned label and distributes it to each of  Only a subset of may support upstream label assignment and the other LSRs will continue to use downstream label assignment – packets will be replicated for these LSRs

8. 8 Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net Conclusion  Other applications of upstream assigned labels are possible. Should be specified in separate documents  Comments are welcome  We would like this to be a WG document