All things related to multicast

[David Farmer <>]

On Wed, Aug 10, 2016 at 4:12 PM, Grimes, Greg <> wrote:

This thread has my attention as I am currently watching a live
multicasted stream from the bottom of the Pacific Ocean.  Before the
NOAA network changes that resulted in them doing a VPN from their
location at the Stennis Space Center we had to provide interdomain
multicast for the Stennis Exploration Command Center so they could
monitor the Okeanos Explorer's underwater exploration.  If it's decided
to kill msdp, how would I continue getting this stream out of Rhode
Island?

SSM (Source Specific Multicast) would be an option, specifying a remote RP for the specific multicast group could work too, or special purpose connectivity over AL2S would be another option. 

 

 I would also love to do IPv6 interdomain multicast, but I have
an issue with my ISP and getting IPv6 support.  We have unicast
support, but I'm scared to even ask for IPv6 multicast support.  What
does I2 support?

I2 does unicast and multicast IPv6.

 

--
Greg T. Grimes
Senior Network Analyst
Information Technology Services
Mississippi State University

662-325-9311

On Wed, 2016-08-10 at 14:13 -0500, David Farmer wrote:
> 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
> ===============================================

--

===============================================
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
===============================================