NVO3 Encapsulation Considerations
draft-dt-nvo3-encap-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                         Sami Boutros(Ed.)
Intended Status: Informational                                    VMware

Ignas Bagdonas                                                Sam Aldrin
Equinix                                                           Google

Matthew Bocci                                                  Uri Elzur
Nokia                                                       Ilango Ganga
                                                                   Intel

Pankaj Garg                                                 Rajeev Manur
Microsoft                                                       Broadcom

Tal Mizrahi                                                  David Mozes
Marvell                                                         Mellanox

Erik Nordmark                                              Michael Smith
Arista Networks                                                    Cisco

Expires: September 13, 2017                               March 12, 2017

                   NVO3 Encapsulation Considerations 
                         draft-dt-nvo3-encap-01

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.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

 

nvo3-dt-encap          Expires September 13, 2017               [Page 1]
INTERNET DRAFT     NVO3 Encapsulation Considerations      March 12, 2017

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Problem Statement . . . . . . . . . . . . . . . . . . . . . . .  4
   2. Design Team Goals . . . . . . . . . . . . . . . . . . . . . . .  4
   3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . .  4
   5. Issues with current Encapsulations  . . . . . . . . . . . . . .  5
     5.1 Geneve . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     5.2 GUE  . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     5.3 VXLAN-GPE  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   6. Common Encapsulation Considerations . . . . . . . . . . . . . .  6
     6.1 Current Encapsulations . . . . . . . . . . . . . . . . . . .  6
     6.2 Useful Extensions Use cases  . . . . . . . . . . . . . . . .  6
       6.2.1. Telemetry extensions. . . . . . . . . . . . . . . . . .  6
 

nvo3-dt-encap          Expires September 13, 2017               [Page 2]
INTERNET DRAFT     NVO3 Encapsulation Considerations      March 12, 2017

       6.2.2. Security/Integrity extensions . . . . . . . . . . . . .  7
       6.2.3. Group Base Policy . . . . . . . . . . . . . . . . . . .  7
     6.3 Hardware Considerations  . . . . . . . . . . . . . . . . . .  8
Show full document text