NVO3 Encapsulation Considerations

The information below is for an old version of the document
Document Type Expired Internet-Draft (nvo3 WG)
Last updated 2019-03-25 (latest revision 2018-09-14)
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd Matthew Bocci
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Matthew Bocci <matthew.bocci@nokia.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


As communicated by WG Chairs, the IETF NVO3 chairs and Routing Area director have chartered a design team to take forward the encapsulation discussion and see if there is potential to design a common encapsulation that addresses the various technical concerns. There are implications of different encapsulations in real environments consisting of both software and hardware implementations and spanning multiple data centers. For example, OAM functions such as path MTU discovery become challenging with multiple encapsulations along the data path. The design team recommend Geneve with few modifications as the common encapsulation, more details are described in section 7.


Sami Boutros (sboutros@vmware.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)