Skip to Content.
Sympa Menu

wg-multicast - Re: [NTAC] [MBONED] BCP 229, RFC 8815 on Deprecating Any-Source Multicast (ASM) for Interdomain Multicast

Subject: All things related to multicast

List archive

Re: [NTAC] [MBONED] BCP 229, RFC 8815 on Deprecating Any-Source Multicast (ASM) for Interdomain Multicast


Chronological Thread 
  • From: David Farmer <>
  • To: Michael Lambert <>
  • Cc: NTAC <>, wg-multicast <>
  • Subject: Re: [NTAC] [MBONED] BCP 229, RFC 8815 on Deprecating Any-Source Multicast (ASM) for Interdomain Multicast
  • Date: Fri, 28 Aug 2020 09:58:22 -0500
  • Dkim-filter: OpenDKIM Filter v2.11.0 mta-p8.oit.umn.edu 4BdN5Y3JRLz9vcdZ
  • Dmarc-filter: OpenDMARC Filter v1.3.2 mta-p8.oit.umn.edu 4BdN5Y3JRLz9vcdZ

Michael,

I had thought of that suggestion as well, and I would be happy to lead such an effort. 

However, why I suggested it as an NTAC item first is, the possibility that there is already a community consensus for #4. If there is already a community consensus for #4 then resurrecting the multicast working group is probably a waste of time and effort. 

On the other hand, if there is community support to at least look at the other possibilities, I'd support that and would be happy to lead such an effort and I think that resurrecting the multicast working group is probably the way to move it forward.

Thanks

On Fri, Aug 28, 2020 at 9:31 AM Michael Lambert <> wrote:
What I would suggest is to resurrect the mulitcast working group with
the specific charge of producing a recommendation for one of David's
possibilities (or perhaps failing to reach a consensus and falling back
on apathy and attrition).

I can't argue with David's sense that we'll head for option 4, but I'd
like to at least see us try to work towards one of the other options.

Frank?  Dale?

Michael

David Farmer (via wg-multicast Mailing List) wrote on 2020/08/28 10:14:20:
> I'd like to suggest we create an NTAC work item on multicast, that
> being what is our current community recommendations for interdomain
> multicast.
>
> I see 4 possibilities;
>
> 1. Native SSM, with support on the Internet2 backbone as well.
> 2. AMT SSM, with no support for native SSM multicast on the Internet2
> backbone, but coordination of the effort.
> 3. Some Combination of 1 & 2, we will need to define what this means for
> the Internet2 backbone.
> 4. Completely Deprecate Interdomain Multicast Coordination within our
> community
>
> Note #4 still allows individual entities to do AMT if they wish, there
> is just no community coordination of the effort or explicit support by
> the Interent2 or the backbone.
>
> Honestly, I see us heading toward #4, and if that is where we want to go
> as a community, I'm ok with that. However, I would rather we decide that
> intentionally, than get there by attrition and apathy.
>
> What do others think?
>
> Thanks


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



Archive powered by MHonArc 2.6.19.

Top of Page