EVPN auto provisioning using a controller
draft-boutros-bess-evpn-auto-provisoning-02

Document Type Active Internet-Draft (individual)
Last updated 2016-10-21
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
Intended Status: Standard Track                                   VMware
                                                            Rex Fernando
                                                             Ali Sajassi
                                                           Cisco Systems

                                                              Kitty Pang
                                                                 Alibaba

                                                            Tapraj Singh
                                                                 Juniper

Expires: April 24, 2017                                 October 21, 2016

               EVPN auto provisioning using a controller 
              draft-boutros-bess-evpn-auto-provisoning-02

Abstract

   In some datacenter use cases, priori knowledge of what PE/NVE to be
   configured for a given L2 or L3 service may not be available. This
   document describes how EVPN can be extended to discover what L2 or L3
   services to be enabled on a given PE/NVE, based on first sign of life
   FSOL packets received on the PE/NVE ports. An EVPN route based on the
   FSOL packets will be sent to a controller to trigger a push of the
   related L2/L3 or subscriber service configuration to be provisioned
   on the PE/NVE and on the switch ports.

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
   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

 

Boutros                  Expires April 24, 2017                 [Page 1]
INTERNET DRAFT           EVPN Auto provisioning         October 21, 2016

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

Copyright and License Notice

   Copyright (c) 2016 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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2. Requirements  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1 Auto-Provisioning  . . . . . . . . . . . . . . . . . . . . .  3
     2.2 Scalability  . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.3 Redundancy . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.4 Multi-homing . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.5 Fast Convergence . . . . . . . . . . . . . . . . . . . . . .  4
   3. Benefits  . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . .  4
   5 Ethernet Segment identifier encoding . . . . . . . . . . . . . .  6
   6 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . .  6
   7 Security Considerations  . . . . . . . . . . . . . . . . . . . .  6
   8  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  6
   9  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     9.1  Normative References  . . . . . . . . . . . . . . . . . . .  7
     9.2  Informative References  . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

 

Boutros                  Expires April 24, 2017                 [Page 2]
INTERNET DRAFT           EVPN Auto provisioning         October 21, 2016

1  Introduction

   This document describes how EVPN can be extended by access PE/NVE
   nodes and a controller in a data center to auto provision the L2 or
   L3 services needed to be enabled on the PE/NVE nodes.
Show full document text