Hi Benson, Overall, I think this is much better. I have a few nits inline below.
Thanks, Larry On 8/23/14 9:49 AM, "Benson Schliesser" <[email protected]> wrote: >Dear NVO3 Contributors - > >Over the past couple weeks, as you¹ve reviewed the proposed charter >update, Matthew and I have received a great deal of feedback both on- and >off-list. Based on all of this input we have developed a revision that we >hope is more clear and accurate. Please review the text below and provide >any feedback that you may have within the next week. > >Thanks, >-Benson & Matthew > >http://svn.tools.ietf.org/svn/wg/nvo3/charter-ietf-nvo3-01-rev-20140823.tx >t > >An NVO3 solution is a set of protocols and/or protocol extensions that >enable >network virtualization within a data center (DC) environment using an >IP-based >overlay approach. It provides layer 2 and layer 3 services LK> I would say "layer 2 and/or layer 3", saying only and implies both services are always present in an NVO3 solution. >for virtual networks >enabling multi-tenancy, workload mobility, optimization, management, and >security, addressing the issues described in the problem statement and >consistent with the framework previously produced by the NVO3 WG. > >The NVO3 WG will develop solutions for network virtualization based on the >following architectural tenets: > - Support for an IP-based underlay data plane > - A logically centralized control plane for network virtualization >Network virtualization approaches that do not adhere to these tenets are >explicitly outside of the scope of the NVO3 WG. > >In pursuit of the solutions described above, the NVO3 WG will document an >architecture for network virtualization within a data center environment. > >The NVO3 WG may produce requirements for a network virtualization control >plane, and will select, extend, and/or develop one or more control plane >protocols to support the architecture. Such protocols are expected to >fulfill >the communication requirements between a Tenant System (TS) and Network >Virtualization Edge (NVE), LK> I think when you say TS above, you really mean the Hypervisor or an End Device such as a Network Service Appliance where the NVE is split with the encap/decap happening in another device, such as a TOR switch. We have been steering clear of having the untrusted Tenant Systems signaling what networks they want to connect to. >and between an NVE and the Network Virtualization >Authority (NVA). The internal mechanisms and protocols of a logically >centralized NVA are explicitly out of scope of the NVO3 WG. Architectural >issues raised by coexistence of multiple logically centralized control >planes >in the same data center may be considered by the WG. Inter-DC mechanisms >are >not in scope of the NVO3 WG at this time. > >The NVO3 WG may produce requirements for network virtualization data >planes >based on encapsulation of virtual network traffic over an IP-based >underlay >data plane. Such requirements should consider OAM and security. Based on >these >requirements the WG will select, extend, and/or develop one or more data >plane >encapsulation format(s). > >Additionally, the WG may document common use-cases for NVO3 solutions. > >The working group may choose to adopt a protocol or data encapsulation >that was >previously worked on outside the IETF as the basis for the WG's work. If >the >NVO3 WG anticipates the adoption of the technologies of another SDO as >part of >the selected protocols or data encapsulation, the NVO3 WG will first >liaise >with that SDO. > >BGP-based solutions to network virtualization within a data center >environment >will be developed in the BGP-Enabled Services (BESS) WG. > >MILESTONES > >Done - Problem Statement submitted for IESG review >Done - Framework document submitted for IESG review >TBD - Architecture submitted for IESG review >TBD - TS to NVE Control Plane Protocol Adopted by WG >TBD - NVE to NVA Control Plane Protocol Adopted by WG >TBD - NVE Data Plane Protocol Adopted by WG >TBD - TS to NVE Control Plane Protocol Submitted for IESG review >TBD - NVA to NVA Control Plane Protocol Submitted for IESG review >TBD - NVE Data Plane Protocol Submitted for IESG review >TBD - Recharter or close WG > >OPTIONAL DOCUMENTS >(we intend to produce these if they're helpful to the WG, but are not >obliged >to do so) > >Control Plane Requirements >Data Plane Requirements >Use-cases > > > >_______________________________________________ >nvo3 mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
