Re: [nvo3] Fwd: DRAFT Charter Update for Discussion

[Lucy yong <[e-mail]>]

Benson,
Please fine the proposed additional text in the charter text.

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, the solutions for a DCVPN spanning over multiple DCs, and the solutions for a DCVPN interconnecting to another DCVPN in DC(s) and an external network. 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.
 Lucy