Hi, Tina. Speaking broadly about requirements drafts: The proposed charter allows the WG to publish requirements. They are described as items the WG "may produce" because they're not blocking further work. (I.e. requirements are non-gating, and the work on solutions is not serialized.) The purpose of working on requirements is to assist the WG in developing solutions.
The current OAM requirements draft is (by its own description) high level and broad. The WG could choose to publish it in this form, to simply set high level expectations as we continue our work on solutions. And/or the WG could choose to integrate it into control plane and/or data plane requirements drafts, elaborating on the general text in ways that are more specific to each draft's topic. And/or the WG could choose to abandon it. But we would need to show WG consensus for doing any of these things. And I don't think that consensus is yet clear in this case. In my personal opinion, I'd like to see the text evolve to be more specific as a stand-alone document *and* have the OAM requirement ideas integrated more tightly into the various data plane and control plane drafts. I have not heard (nor imagined) any compelling reasons to abandon it. But I also do not think it's quite "done" at this point. Cheers, -Benson On Sun, Aug 24, 2014 at 6:00 PM, Tina TSOU <[email protected]> wrote: > Dear Benson, > > How are we going to deal with draft like > http://datatracker.ietf.org/doc/draft-ashwood-nvo3-oam-requirements/ > ? > > > Thank you, > Tina > > On Aug 24, 2014, at 12: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.txt > > 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 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), 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
