Hi Brenson,
This statement An NVO3 solution, also known as a Data Center Virtual Private Network (DCVPN), does not seem to imply your response The term "NVO3" refers to a working group. The term "DCVPN" refers to the category of solutions for providing multi-tenancy, etc in a DC environment. To me it looks like NVO3 and DCVPN are the same thing. Can we instead use your response in the opening line? Regards, Osama From: nvo3 [mailto:[email protected]] On Behalf Of Benson Schliesser Sent: Thursday, August 14, 2014 10:57 AM To: Linda Dunbar Cc: [email protected] Subject: Re: [nvo3] Fwd: DRAFT Charter Update for Discussion Hi, Linda. On Wed, Aug 13, 2014 at 4:39 PM, Linda Dunbar <[email protected] <mailto:[email protected]> > wrote: The proposed charter is so general that there is not much to pick on. Yes, you have done a great job drafting it. I'm not sure if you're serious, or teasing me / being sarcastic, but either way I guess it puts a smile on my face. ;) So the NVO3 is now DCVPN? Since the underlay is IP, will it become another L3VPN? Somebody else asked me a similar question privately, so I want to make sure it's clear... The term "NVO3" refers to a working group. The term "DCVPN" refers to the category of solutions for providing multi-tenancy, etc in a DC environment. There are possibly many technical approaches to designing a DCVPN. Some of those approaches might be based on protocols like BGP, MPLS, etc, which are developed in other WGs. As proposed in the new charter, NVO3 does not own the scope / charter for all work on DCVPNs. Rather, the proposed NVO3 charter is meant to narrow our focus to a specific type of DCVPN: overlay-based with a logically centralized control plane. That being said, is that not clear from the text that we proposed? Is there some specific way that it could be improved? Cheers, -Benson
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
