Split-NVE Control Plane Requirements
draft-ietf-nvo3-hpvr2nve-cp-req-10

Document Type Active Internet-Draft (nvo3 WG)
Last updated 2017-10-26
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Matthew Bocci
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Matthew Bocci <matthew.bocci@nokia.com>
NVO3 Working Group                                                 Y. Li
INTERNET-DRAFT                                               D. Eastlake
Intended Status: Informational                       Huawei Technologies
                                                              L. Kreeger
                                                             Arrcus, Inc
                                                               T. Narten
                                                                     IBM
                                                                D. Black
                                                                     EMC
Expires: April 30, 2018                                 October 27, 2017

                  Split-NVE Control Plane Requirements
                   draft-ietf-nvo3-hpvr2nve-cp-req-10

Abstract

   In a Split-NVE architecture, the functions of the NVE (Network
   Virtualization Edge) are split across a server and an external
   network equipment which is called an external NVE.  The server-
   resident control plane functionality resides in control software,
   which may be part of a hypervisor or container management software;
   for simplicity, this draft refers to the hypervisor as the location
   of this software.

   Control plane protocol(s) between a hypervisor and its associated
   external NVE(s) are used by the hypervisor to distribute its virtual
   machine networking state to the external NVE(s) for further handling.
   This document illustrates the functionality required by this type of
   control plane signaling protocol and outlines the high level
   requirements. Virtual machine states as well as state transitioning
   are summarized to help clarify the needed protocol requirements.

Status of this Memo

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

   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
 

Li, et al                                                       [Page 1]
INTERNET DRAFT         Hypervisor to NVE CP Reqs            October 2017

   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.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2  Target Scenarios  . . . . . . . . . . . . . . . . . . . . .  6
   2. VM Lifecycle  . . . . . . . . . . . . . . . . . . . . . . . . .  8
     2.1 VM Creation Event  . . . . . . . . . . . . . . . . . . . . .  8
     2.2 VM Live Migration Event  . . . . . . . . . . . . . . . . . .  9
     2.3 VM Termination Event . . . . . . . . . . . . . . . . . . . . 10
     2.4 VM Pause, Suspension and Resumption Events . . . . . . . . . 10
   3. Hypervisor-to-NVE Control Plane Protocol Functionality  . . . . 10
     3.1 VN Connect and Disconnect  . . . . . . . . . . . . . . . . . 11
     3.2 TSI Associate and Activate . . . . . . . . . . . . . . . . . 12
     3.3 TSI Disassociate and Deactivate  . . . . . . . . . . . . . . 15
   4. Hypervisor-to-NVE Control Plane Protocol Requirements . . . . . 16
   5. VDP Applicability and Enhancement Needs . . . . . . . . . . . . 17
   6. Security Considerations . . . . . . . . . . . . . . . . . . . . 19
   7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 19
   8. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 19
   8. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     8.1  Normative References  . . . . . . . . . . . . . . . . . . . 20
Show full document text