Gyan- most of these interop questions for MSDP-MVPN are covered in
RFC6514. This doc makes no changes to those procedures. This doc simply
addresses a fundamental gap that was missed in RFC6514- specifically that
MSDP SAs contain 3 pieces of info (source, group, originating RP) and MVPN
SAs
On Thu, 9 Jan 2020, Gyan Mishra wrote:
|
| Actually, Embedded RP provides interdomain ASM for IPv6 and is the
reason
| there is no need for MSDP in IPv6.
|
|
| Gyan> With embedded RP how is the “source” SA propagated as is done by MSDP
with IPv4 accomplished with IPv6. The
On Wed, 8 Jan 2020, Gyan Mishra wrote:
| Gyan> Source discovery is only necessary with ASM not SSM. With SSM the
receiver is "source" aware so does not require any discovery mechanism.
| So with SSM which requires IGMPv3 enabled on the receiver last hop router
subnets and on the
I am not aware of any IPR related to this draft.
-Lenny
On Mon, 6 Jan 2020, slitkows.i...@gmail.com wrote:
|
| Hello,
|
|
|
| This email begins a two-weeks WG adoption poll for and
draft-zzhang-bess-bgp-multicast-03 [1] .
|
| For information, it’s companion document
I support adoption of this draft.
On Mon, 6 Jan 2020, slitkows.i...@gmail.com wrote:
|
| Hello,
|
|
|
| This email begins a two-weeks WG adoption poll for and
draft-zzhang-bess-bgp-multicast-controller-02 [1] ..
|
| For information, it’s companion document
Support as coauthor bc it addresses a practical deployment problem that is
currently seen with MSDP interacting with MVPN.
I am not aware of any relevant undisclosed IPR.
On Mon, 26 Feb 2018, stephane.litkow...@orange.com wrote:
|
| Hello working group,
|
|
|
| This email starts a
Toerless,
Thanks for the comments. After thinking about your feedback on RFC4610 a
bit, I'm not sure that case is applicable here. Consider the 2 directions
of interworking:
1) MSDP SA/AnycastRP_PIM_Register -> MVPN SA
2) MVPN SA -> MSDP SA/AnycastRP_PIM_Register
As I understand, #1 is
