Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements
RFC 8394

Document Type RFC - Informational (May 2018; No errata)
Last updated 2018-05-31
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Matthew Bocci
Shepherd write-up Show (last changed 2018-01-24)
IESG IESG state RFC 8394 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to Matthew Bocci <matthew.bocci@nokia.com>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
Internet Engineering Task Force (IETF)                             Y. Li
Request for Comments: 8394                               D. Eastlake 3rd
Category: Informational                              Huawei Technologies
ISSN: 2070-1721                                               L. Kreeger
                                                            Arrcus, Inc.
                                                               T. Narten
                                                                     IBM
                                                                D. Black
                                                                Dell EMC
                                                                May 2018

Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements

Abstract

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

   One or more control-plane protocols 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 protocol
   requirements.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8394.

Li, et al.                    Informational                     [Page 1]
RFC 8394          Split-NVE Control-Plane Requirements          May 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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 ....................................................3
      1.1. Terminology ................................................4
      1.2. Target Scenarios ...........................................6
   2. VM Lifecycle ....................................................7
      2.1. VM Creation Event ..........................................8
      2.2. VM Live Migration Event ....................................8
      2.3. VM Termination Event .......................................9
      2.4. VM Pause, Suspension, and Resumption Events ...............10
   3. Hypervisor-to-NVE Control-Plane Protocol Functionality .........10
      3.1. VN_Connect and VN_Disconnect ..............................10
      3.2. TSI Associate and Activate ................................12
      3.3. TSI De-Associate 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 ............................................20
   8. References .....................................................21
      8.1. Normative References ......................................21
      8.2. Informative References ....................................22
   Appendix A. VDP Illustrations (per IEEE 802.1Q) (for Information
               Only) .................................................23
   Acknowledgements ..................................................25
   Authors' Addresses ................................................26

Show full document text