Thanks, Lucy. Personally, I agree that this would be a valuable part of a NVO3 solution. As a WG chair, I think we may need to focus our work in multiple phases... Can you suggest specific text that might help with this goal in the charter?
Cheers, -Benson On Thu, Aug 14, 2014 at 9:45 AM, Lucy yong <[email protected]> wrote: > Hi Benson and Matthew, > > > > The charter text is in general and good. > > > > I suggest that the charter also includes the solutions for a virtual > network, i.e. DCVPN, spanning multiple DCs and a virtual network > interconnecting to another virtual network in DC(s) and an external network. > > > > Thanks, > > Lucy > > > > *From:* nvo3 [mailto:[email protected]] *On Behalf Of *Benson > Schliesser > > *Sent:* Wednesday, August 13, 2014 2:42 PM > *To:* [email protected] > *Subject:* [nvo3] Fwd: DRAFT Charter Update for Discussion > > > > Just a reminder that Matthew and I are looking for feedback on the draft > text of a new NVO3 charter. Can it be that we wrote a charter so perfect > there are no comments..? > > > > The draft charter text is quoted in my email below. For reference it can > also be found at > http://svn.tools.ietf.org/svn/wg/nvo3/charter-ietf-nvo3-01-rev-20140808.txt > > > > Cheers, > > -Benson & Matthew > > > > > > ---------- Forwarded message ---------- > From: *Benson Schliesser* <[email protected]> > Date: Fri, Aug 8, 2014 at 4:53 PM > Subject: DRAFT Charter Update for Discussion > To: [email protected] > > > Dear NVO3 Contributors - > > As discussed during the NVO3 meeting at IETF-90 in Toronto, the chairs > have been drafting a new / revised charter for the WG. The latest draft > charter text is below for your review. > > Frankly, we suspect that some of the wording could be further improved to > be more clear and/or precise. With that in mind we ask for your help - > please let us know if something seems unclear or if you have suggestions > for better wording. > > If you have feedback please post it to the list for discussion within the > next 2 weeks. > > Thanks, > -Benson & Matthew > > An NVO3 solution, also known as a Data Center Virtual Private Network > (DCVPN), > is a set of protocols and/or protocol extensions that address the issues > described by draft-ietf-nvo3-overlay-problem-statement consistent with the > approach described by draft-ietf-nvo3-framework. > > NVO3 will document DCVPN requirements for both control plane protocol(s) > and > data plane encapsulation format(s), as well as management, operational, > maintenance, troubleshooting, security and OAM protocol requirements. > Additionally, NVO3 will document common use-cases for DCVPN solutions. > > Consistent with the documents described above, the NVO3 WG will document an > architecture for DCVPNs within a data center environment based on the > following > architectural design points: > - A logically centralized NVA control plane > - Support for an underlay IP data plane between NVEs > > Based on this architecture the NVO3 WG will develop one or more NVO3 > solutions. > This may include documenting applicability of existing protocols, > contributing > to the development of protocol extensions by other WGs and/or SDOs, and/or > developing new protocols as appropriate. > > Solutions and/or protocols that were developed outside of the IETF, but not > developed by another SDO, and that have multiple interoperable > implementations > may be adopted by the NVO3 WG for further development, based on WG > consensus, > if requested by the authors . > > If the NVO3 WG anticipates the adoption of the technologies of another SDO, > such as the IEEE, as part of any DCVPN solution, it will liaise with that > SDO > to ensure the compatibility of the approach. > > >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
