[j-nsp] NG-MVPN RPT-SPT mode no receiver CE limitation?
Mark Tinka
mark.tinka at seacom.mu
Wed May 28 02:27:33 EDT 2014
On Wednesday, May 28, 2014 08:21:52 AM Krasimir Avramski
wrote:
> Well with the caveat that in RPT-SPT after the first
> Receiver PE travels the RPT, the (S,G) state is already
> known to remaining Receiver PEs due to bgp inherent
> protocol optimization - type-5 SA generated by source
> PE, so we are effectively in the SPT-only operation
> after the first subscriber behind the "first Receiver
> PE".
We'd just rather do without the extra step.
It's not typical of (traditional) Multicast design, but from
my side, it's a welcome optimization that I would wish upon
anyone. The extra control plane state is minimal, even at
scale.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20140528/64aec6cd/attachment.sig>
More information about the juniper-nsp
mailing list