Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9638
Discuss this RFC: Send questions or comments to the mailing listnvo3@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9638
The IETF Network Virtualization Overlays (NVO3) Working Groupdeveloped considerations for a common encapsulation that addressesvarious network virtualization overlay technical concerns. Thisdocument provides a record, for the benefit of the IETF community, ofthe considerations arrived at by the NVO3 Working Group starting fromthe output of the NVO3 encapsulation Design Team. Theseconsiderations may be helpful with future deliberations by workinggroups over the choice of encapsulation formats.
There are implications of having different encapsulations in realenvironments consisting of both software and hardware implementationsand within and spanning multiple data centers. For example,Operations, Administration, and Maintenance (OAM) functions such aspath MTU discovery become challenging with multiple encapsulationsalong the data path.
Based on these considerations, the NVO3 Working Group determined thatGeneric Network Virtualization Encapsulation (Geneve) with a fewmodifications is the common encapsulation. This document providesmore details, particularly in Section 7.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.