Skip to main content

NVO3 Encapsulation Considerations
draft-ietf-nvo3-encap-07

The information below is for an old version of the document.
Document Type Expired Internet-Draft (nvo3 WG)
Authors Sami Boutros , Donald E. Eastlake 3rd
Last updated 2022-01-30 (Latest revision 2021-07-29)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Reviews
Stream WG state WG Document
Document shepherd Matthew Bocci
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
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:
https://www.ietf.org/archive/id/draft-ietf-nvo3-encap-07.txt

Abstract

As communicated by the 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 recommends Geneve with a few modifications as the common encapsulation. This document provides more details, particularly in Section 7.

Authors

Sami Boutros
Donald E. Eastlake 3rd

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