Hi, Linda and Anoop - (I’ve changed the message Subject to more accurately describe this topic.)
On Aug 29, 2014, at 6:06 PM, Anoop Ghanwani <[email protected]> wrote: > > [Linda] The entire charter didn't even mention application initiated > multicast. It is wrong. NVA can eliminate (or reduce) ARP/ND related > broadcast/multicast, but not application initiated multicast. > > The current proposed MILESTONES have separate deliverables for WG adoption > and FOR IESG review, and very detailed categories being explicitly spelled > out. Therefore, at minimum, should have one line on the protocols to handle > hosts/applications initiated multicast. > > [ag] I agree with Linda here. While it sounds like there is agreement that > the problem needs to be addressed by the working group, it would be useful to > at least have an explicit mention of multicast somewhere in the charter. > Perhaps we could change the following line from: > "The NVO3 WG will develop solutions for network virtualization based on the > following architectural tenets:" > to: > "The NVO3 WG will develop solutions for network virtualization covering both > unicast and multicast traffic handling based on the > following architectural tenets:” I’m not opposed to mentioning multicast in the charter, but t wouldn’t be my preferred choice. The way that I think about it, multicast support is an appropriate topic for the requirements drafts. And it should be discussed in the architecture draft, as well as any solutions drafts where it might be applicable. But it would be sub-optimal to load the charter with a discussion of the various types of traffic that might be found in the overlay: broadcast, known and unknown unicast, multicast supporting network protocols (such as address resolution etc), multicast on behalf of applications (“application specific multicast”), etc. The current charter text does not exclude work on multicast, which is good. And I don’t see any reason to explicitly call it out as a unique topic separate from the architecture, control plane, data plane, and use cases. If I’m missing something please help me understand. Otherwise I’d prefer to leave the proposed charter text as-is. Cheers, -Benson
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
