Re: Query about upstrean assigned label from draft-ietf-l3vpn-2547bis-mcast-07.txt

[Eric Rosen <[e-mail]>]

Subinoy> Section Point 5 in 7.4.1.1. Advertising C-flow Binding to P-Tunnel
Subinoy> in draft-ietf-l3vpn-2547bis-mcast-07.txt says

        "If at least some of the S-PMSIs aggregated onto the same
        P-tunnel belong to different MVPNs, then all these routes MUST
        carry an MPLS upstream assigned label [MPLS-UPSTREAM-LABEL,
        section 6.3.4]. If all these aggregated S-PMSIs belong to the
        same MVPN, then the routes MAY carry an MPLS upstream assigned
        label [MPLS-UPSTREAM-LABEL]. The labels MUST be distinct on a
        per MVPN basis, and MAY be distinct on a per route basis."

Subinoy> I do not understand where 1 label per MVPN solves everything then
Subinoy> what is the need to use 1 label per route. What is the need to keep
Subinoy> multiple label for a single MVPN per PE router?

The text you've  quoted does not require that a label  be assigned for every
route.  

If you're  asking why that's even allowed  as an option, the  reason is that
some implementers may prefer to assign  a different label to each c-flow, so
as to avoid the need to do an <S,G> lookup.

Subinoy> Suppose Customer is running PIM as multicast protocol, Provider
Subinoy> network support l3vpn with BGP, RSVP P2MP.  Then how customer
Subinoy> Register packet destined to C-RP is forwarded through provider
Subinoy> network?

Register packets are unicast packets.

Subinoy> From draft-ietf-l3vpn-2547bis-mcast-07.txt I could not understand
Subinoy> exactly when Source Active A-D route is sent and when send Source
Subinoy> Active A-D route?  Ingress PE or Egress PE?  To whom Source Active
Subinoy> A-D route is sent?

Did you look at section 9.2?  Also section 13 of draft-ietf-l3vpn-2547bis-
mcast-bgp-05.txt.  Could you  say more about which bit  of text is confusing
you?