NVO3 Encapsulation Considerations

Document Type Expired Internet-Draft (individual)
Authors Sami Boutros  , Sam Aldrin  , Uri Elzur  , Ilango Ganga  , Rajeev Manur  , David Mozes  , Michael Smith 
Last updated 2017-09-14 (latest revision 2017-03-13)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

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)
Sam Aldrin (aldrin.ietf@gmail.com)
Uri Elzur (uri.elzur@intel.com)
Ilango Ganga (ilango.s.ganga@intel.com)
Rajeev Manur (rajeev.manur@broadcom.com)
David Mozes (davidm@mellanox.com)
Michael Smith (michsmit@cisco.com)

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