-----BEGIN PGP SIGNED MESSAGE----- At 07:30 PM 3/27/2001 -0500, Martin, Christian wrote:

One of the things that appears to be a major impediment to large-scale deployment is the lack of SA transitivity, which is limited by MSDP's RPF rules. Therefore, the Internet needs a dense mesh of MSDP peerings to allow any-to-any connectivity. As of now, this is not the case. SSM will fix this.

regards, chris

Two responses, not mutually exclusive: - The Internet already has a "dense mesh" of BGP peerings. All the pieces are in place from the major router vendors to turn on MSDP and PIM-SM at the same places; it seems to me that it's just a matter of doing it. - Come on over to the IETF MSDP working group. In Minneapolis I presented an I-D that would avoid the RPF rules. However, in the MSDP working group there is very strong resistance to dropping the RPF rules, because then you can't build an "MSDP traceroute". My personal response to that is something along the lines of 'there is no "DNS traceroute" but DNS works just fine anyway, and you just use other mechanisms to debug it.' It was agreed in Minneapolis that building an RPF-free MSDP would be deferred until the current MSDP reaches standard status, and then we would build MSDPv2 without RPF rules if we thought it was needed. === Bill Nickless http://www.mcs.anl.gov/people/nickless +1 630 252 7390 PGP:0E 0F 16 80 C5 B1 69 52 E1 44 1A A5 0E 1B 74 F7 nickless@mcs.anl.gov -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQCVAwUBOsJkF6wgm7ipJDXBAQGIWwP/ZjtGv/fA1I17v2GQD/jeW2zWzBgj9z30 ZsgOi6xUBfKFHvzaB+NMSP+CYAiv9jXhusR1MHeH/+vSDEP5Z5wSYNF39/uEC1zd kLA0WGyIF/+zm7VXMsxdx4iwb+iSVhaTbIA+TYcgsQzigNnWbfWpnB43EvNDp6Xb x7tjGssZkAY= =nsmd -----END PGP SIGNATURE-----