Split Network Virtualization Edge Control-Plane Requirements
RFC 8394, “Split Network Virtualization Edge Control-Plane Requirements”, is an Informational document published in May 2018 by Y. Li, D. Eastlake 3rd, L. Kreeger, T. Narten, D. Black. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8394 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8393 Operating the Network Service Header with Next Protocol "None"
- RFC 8395 Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
- RFC 8392 CBOR Web Token
- RFC 8396 Managing, Ordering, Distributing, Exposing, and Registering Telephone Numbers : Problem Statement, Use Cases, and Framework
- RFC 8391 XMSS: eXtended Merkle Signature Scheme
- RFC 8397 Transparent Interconnection of Lots of Links Multilevel Using Unique Nicknames
- RFC 8390 RSVP-TE Path Diversity Using Exclude Route
- RFC 8398 Internationalized Email Addresses in X.509 Certificates