NVO3 Encapsulation Considerations
draft-dt-nvo3-encap-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| 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) | ||
| Replaced by | draft-ietf-nvo3-encap | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-nvo3-encap | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Sami Boutros
Sam Aldrin
Uri Elzur
Ilango Ganga
Rajeev Manur
David Mozes
Michael Smith
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)