+1. Support. Linda
From: Lucy yong Sent: Friday, August 29, 2014 5:28 PM To: Anoop Ghanwani; Linda Dunbar Cc: Benson Schliesser; [email protected] Subject: RE: [nvo3] Third Draft Charter Update for Discussion "The NVO3 WG will develop solutions for network virtualization covering both unicast and multicast traffic handling based on the following architectural tenets:" Support this suggestion. Lucy From: nvo3 [mailto:[email protected]] On Behalf Of Anoop Ghanwani Sent: Friday, August 29, 2014 5:07 PM To: Linda Dunbar Cc: Benson Schliesser; [email protected]<mailto:[email protected]> Subject: Re: [nvo3] Third Draft Charter Update for Discussion Benson, Please see in line prefixed with [ag]. Anoop On Fri, Aug 29, 2014 at 8:51 AM, Linda Dunbar <[email protected]<mailto:[email protected]>> wrote: Benson, Thanks for the reply. Comments inserted below: -----Original Message----- From: Benson Schliesser [mailto:[email protected]<mailto:[email protected]>] > Some suggestions on the MILESTONES: > > I think application specific multicast is an important area, especially for > data centers whose underlay IP network don't support PIM or traditional L3 > multicast schemes. Many data centers fall into this category. I don't particularly like the phrase "application specific multicast", [Linda] It is about the non ARP/ND related multicast (or the multicast initiated by clients). [ag] Perhaps we can refer to this as "multicast applications other than ARP/ND." but I think I understand what you mean by it. And I agree with your statement that it's an important area for the WG to address. I also think that multicast traffic can be taken into account when documenting the data and control plane protocols already enumerated in the milestones. It isn't clear to me that there is any reason to call it out specifically, nor what such a milestone would look like. [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:" Anoop
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
