Re: [mpls] MPLS-RT review of draft-rekhter-mpls-pim-sm-over-mldp

[Yakov Rekhter <[e-mail]>]

Ice,

> Yakov,
> 
> > Let me just point out that draft-wijnands-mpls-mldp-in-band-wildcard-encodi
ng
> > itself said the following:
> > 
> >                                                                     In
> >   scenarios where it does not make sense to apply "threshold infinity"
> >   to a given ASM group, a more complex set of procedures are needed, as
> >   per [I-D.rekhter-pim-sm-over-mldp].
> > 
> >   ....
> > 
> >   [I-D.rekhter-pim-sm-over-mldp]
> >              Rekhter, Y. and R. Aggarwal, "Carrying PIM-SM in ASM mode
> >              Trees over P2MP mLDP LSPs",
> >              draft-rekhter-pim-sm-over-mldp-04 (work in progress),
> >              August 2011.
> > 
> > So, even draft-wijnands-mpls-mldp-in-band-wildcard-encoding acknowledges
> > that there are scenarios where it is insufficient. Moreover, this
> > draft suggest to use draft-rekhter-pim-sm-over-mldp, *not*
> > draft-ietf-mpls-seamless-mcast.
> 
> Just because its referenced, it does mean the authors support the
> idea. The i ntention was to point out that rekhter-pim-sm-over-mldp
> uses complex procedures to support PIM-SM. To avoid any confusion,
> I'll update the next revision to suggest draft-ietf-mpls-seamless-mcast
> to be used to support PIM-SM. Good point.

Would you also update rfc6826 ? As it said the following:

   LSR D is attached to a network that is capable of MPLS multicast and
   IP multicast (see figure 1), and D is required to create a IP
   multicast tree due to a certain IP multicast event, like a PIM Join,
   MSDP Source Announcement (SA) [RFC3618], BGP Source Active auto-
   discovery route [SM-MLDP], or Rendezvous Point (RP) discovery.

   ....

   [SM-MLDP]  Rekhter, Y., Aggarwal, R., and N. Leymann, "Carrying PIM-
              SM in ASM mode Trees over P2MP mLDP LSPs", Work in
              Progress, August 2011.

Yakov.