An NVO3 solution is a set of protocols and/or protocol extensions that
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
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.
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
(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