Usage and applicability of BGP MPLS based Ethernet VPN
draft-ietf-bess-evpn-usage-04

Document Type Active Internet-Draft (bess WG)
Last updated 2017-06-21 (latest revision 2017-03-13)
Replaces draft-rp-l2vpn-evpn-usage
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Martin Vigoureux
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
BESS Workgroup                                           J. Rabadan, Ed.
Internet Draft                                           S. Palislamovic
                                                           W. Henderickx
Intended status: Informational                                     Nokia

J. Uttaro                                                     A. Sajassi
AT&T                                                               Cisco

                                                                K. Patel
                                                                  Arrcus

T. Boyes                                                        A. Isaac
Bloomberg                                                        Juniper

Expires: September 14, 2017                               March 13, 2017

         Usage and applicability of BGP MPLS based Ethernet VPN
                     draft-ietf-bess-evpn-usage-04

Abstract

   This document discusses the usage and applicability of BGP MPLS based
   Ethernet VPN (EVPN) in a simple and fairly common deployment
   scenario. The different EVPN procedures will be explained on the
   example scenario, analyzing the benefits and trade-offs of each
   option. Along with [RFC7432], this document is intended to provide a
   simplified guide for the deployment of EVPN in Service Provider
   networks.

Status of this Memo

   This Internet-Draft is submitted 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."

 

Rabadan-Palislamovic et al.Expires September 14, 2017           [Page 1]
Internet-Draft                 EVPN Usage                 March 13, 2017

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

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

   This Internet-Draft will expire on September 20, 2016.

Copyright 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
   2. Use-case scenario description . . . . . . . . . . . . . . . . .  4
   3. Provisioning Model  . . . . . . . . . . . . . . . . . . . . . .  6
     3.1. Common provisioning tasks . . . . . . . . . . . . . . . . .  6
       3.1.1. Non-service specific parameters . . . . . . . . . . . .  7
       3.1.2. Service specific parameters . . . . . . . . . . . . . .  7
     3.2. Service interface dependent provisioning tasks  . . . . . .  8
       3.2.1. VLAN-based service interface EVI  . . . . . . . . . . .  8
       3.2.2. VLAN-bundle service interface EVI . . . . . . . . . . .  9
       3.2.3. VLAN-aware bundling service interface EVI . . . . . . .  9
   4. BGP EVPN NLRI usage . . . . . . . . . . . . . . . . . . . . . .  9
   5. MAC-based forwarding model use-case . . . . . . . . . . . . . . 10
     5.1. EVPN Network Startup procedures . . . . . . . . . . . . . . 10
     5.2. VLAN-based service procedures . . . . . . . . . . . . . . . 11
       5.2.1. Service startup procedures  . . . . . . . . . . . . . . 11
       5.2.2. Packet walkthrough  . . . . . . . . . . . . . . . . . . 12
     5.3. VLAN-bundle service procedures  . . . . . . . . . . . . . . 15
       5.3.1. Service startup procedures  . . . . . . . . . . . . . . 15
       5.3.2. Packet Walkthrough  . . . . . . . . . . . . . . . . . . 16
     5.4. VLAN-aware bundling service procedures  . . . . . . . . . . 16
       5.4.1. Service startup procedures  . . . . . . . . . . . . . . 16
       5.4.2. Packet Walkthrough  . . . . . . . . . . . . . . . . . . 17
   6. MPLS-based forwarding model use-case  . . . . . . . . . . . . . 18
 

Rabadan-Palislamovic et al.Expires September 14, 2017           [Page 2]
Show full document text