RFC 9638: Network Virtualization over Layer 3 (NVO3) Encapsulation Considerations
In plain English — editorial summary, not part of the RFC
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 by the NVO3 Working Group starting from the output of the 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, Operations, Administration, and Maintenance (OAM) functions such as path MTU discovery become challenging with multiple encapsulations along the data path. Based on these considerations, the NVO3 Working Group determined that Generic Network Virtualization Encapsulation (Geneve) with a few modifications is the common encapsulation. This document provides more details, particularly in Section 7.
Document record
- Document ID
- RFC9638
- Published
- September 2024
- Authors
- S. Boutros; D. Eastlake 3rd
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9521Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve)Current
January 2024
- RFC 8293A Framework for Multicast in Network Virtualization over Layer 3Current
January 2018
- RFC 7978Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header ExtensionCurrent
September 2016
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 9599Guidelines for Adding Congestion Notification to Protocols that Encapsulate IPCurrent
August 2024
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 6935IPv6 and UDP Checksums for Tunneled PacketsCurrent
April 2013
- RFC 6324Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed MitigationsCurrent
August 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?