All things related to multicast

[David Farmer <>]

We are at the beginning of a major equipment replacement/upgrade cycle for campus.  As part of that I have been thinking about what the appropriate support of interdomain multicast should be.  While I haven't come to a final conclusions yet, here is my current thinking.

1. Primary goal of deprecating MSDP, and therefore interdomain IPv4 ASM multicast. MSDP is fragile and honestly it's a hack.

2. Keep IPv4 ASM multicast locally, on campus, maybe between campuses in the University system, through use of a common RP, no MSDP.  

3. Keep IPv4 SSM interdomain multicast 

4. Focus efforts on supporting IPv6 interdomain multicast, SSM and embedded-RP

5. Keep IPv4 and IPv6 BGP multicast NLRIs

6. Primarily PIM sparse mode, maybe using PIM-bidir for better scaling

What do others think?

Thanks

On Wed, Aug 10, 2016 at 11:00 AM, Michael H Lambert <> wrote:

The following was sent by John Kristoff (cc'ed) to the Multicast WG mailing list (yes, the list still exists):

> Begin forwarded message:
>
> From: John Kristoff <>
> Subject: AS 20130 has turned off interdomain IP multicast
> Date: 9 August 2016 at 18:09:37 EDT
> To: "" <>
> Reply-To:
>
>> show msdp
> MSDP instance is not running
>
>> show route table ?
> Possible completions:
>  <table>              Name of routing table
>  inet.0
>  inet.1
>  inet6.0
>  inet6.1
>>
>
> It was a fun ride for a time, but it now joins the dustbin of dead
> technologies in the back of my brain.  Token Ring, ISDN, NetWare, ...,
> welcome you to the club, may you rest in peace.
>
> John

Does anyone else think it might be time to reflect on the future of interdomain multicast in the backbone?

Michael

--

===============================================
David Farmer              
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota  
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================