Network Virtualization Overlays (nvo3) Internet Drafts

      
 Generic Protocol Extension for VXLAN (VXLAN-GPE)
 
 draft-ietf-nvo3-vxlan-gpe-13.txt
 Date: 04/11/2023
 Authors: Fabio Maino, Larry Kreeger, Uri Elzur
 Working Group: Network Virtualization Overlays (nvo3)
 This document describes extending Virtual eXtensible Local Area Network (VXLAN), via changes to the VXLAN header, with four new capabilities: support for multi-protocol encapsulation, support for operations, administration and maintenance (OAM) signaling, support for ingress-replicated BUM Traffic (i.e. Broadcast, Unknown unicast, or Multicast), and explicit versioning. New protocol capabilities can be introduced via shim headers.
 Network Virtualization Overlays (NVO3) Encapsulation Considerations
 
 draft-ietf-nvo3-encap-12.txt
 Date: 19/02/2024
 Authors: Sami Boutros, Donald Eastlake
 Working Group: Network Virtualization Overlays (nvo3)
 The IETF Network Virtualization Overlays (NVO3) Working Group developed considerations for a common encapsulation that addresses various network virtualization overlay technical concerns. This document provides a record, for the benefit of the IETF community, of the considerations arrived at starting from the output of an NVO3 encapsulation design team. These considerations may be helpful with future deliberations by working groups over the choice of encapsulation formats. There are implications of having different encapsulations in real environments consisting of both software and hardware implementations and within and spanning multiple data centers. For example, OAM functions such as path MTU discovery become challenging with multiple encapsulations along the data path. Based on these considerations, the Working Group determined that Geneve with a few modifications as the common encapsulation. This document provides more details, particularly in Section 7.
 OAM for use in GENEVE
 
 draft-ietf-nvo3-geneve-oam-10.txt
 Date: 19/04/2024
 Authors: Greg Mirsky, Sami Boutros, David Black, Santosh Pallagatti
 Working Group: Network Virtualization Overlays (nvo3)
 This document lists a set of general requirements for active OAM protocols in the Geneve overlay network. Based on the requirements, IP encapsulation for active Operations, Administration, and Maintenance protocols in Geneve protocol is defined. Considerations for using ICMP and UDP-based protocols are discussed.

data-group-menu-data-url="/group/groupmenu.json">

Network Virtualization Overlays (nvo3)

WG Name Network Virtualization Overlays
Acronym nvo3
Area Routing Area (rtg)
State Active
Charter charter-ietf-nvo3-02 Approved
Document dependencies
Additional resources Issue tracker, Wiki, Zulip stream
Personnel Chairs Matthew Bocci, Sam Aldrin
Area Director Gunter Van de Velde
Tech Advisor Ron Bonica
Secretary Yizhou Li
Liaison Contacts Benson Schliesser, Matthew Bocci
Mailing list Address nvo3@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/nvo3
Archive https://mailarchive.ietf.org/arch/browse/nvo3/
Chat Room address https://zulip.ietf.org/#narrow/stream/nvo3

Charter for Working Group

The purpose of the NVO3 WG is to develop a set of protocols and/or
protocol extensions that enable network virtualization within a data
center (DC) environment that assumes an IP-based underlay. An NVO3
solution provides layer 2 and/or layer 3 services for virtual networks
enabling multi-tenancy and workload mobility, addressing the issues
described in the problem statement (including management and security),
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 authority 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 protocol
for each of the functional interfaces identified to support the
architecture. Such protocols are expected to fulfill the communication
requirements between an End Device and a Network Virtualization Edge
(NVE) in cases where the NVE is not co-resident with the End Device,
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 to ensure the compatibility of
the approach.

The NVO3 WG will not consider solutions to network virtualization
within a data center environment based on extensions to BGP or LISP
protocols.

Milestones

Date Milestone Associated documents
Aug 2020 OAM Solution submitted for IESG Review
Aug 2020 Recharter or close working group
Mar 2020 Security Solutions Submitted to IESG
Mar 2020 Security Requirements Submitted to IESG
Dec 2019 Data Plane Requirements submitted for IESG review

Done milestones

Date Milestone Associated documents
Done Data Plane Solution submitted for IESG review
Done End Device - NVE Control Plane Solution submitted for IESG review
Done Architecture submitted for IESG review
Done Use Cases submitted for IESG review
Done Framework document submitted for IESG review
Done Problem Statement submitted for IESG review