PBB E-VPN
draft-ietf-l2vpn-pbb-evpn-00

The information below is for an old version of the document
Document Type Active Internet-Draft (l2vpn WG)
Last updated 2012-02-27
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Working Group                                 Ali Sajassi 
   Internet Draft                                         Samer Salam 
   Category: Standards Track                             Sami Boutros 
                                                                Cisco 
   Florin Balus 
   Wim Henderickx                                         Nabil Bitar 
   Alcatel-Lucent                                             Verizon 
                                                                      
   Clarence Filsfils                                     Aldrin Issac 
   Dennis Cai                                               Bloomberg 
   Cisco                                                              
                                                           Lizhong Jin 
                                                                   ZTE 
                                                                      
   Expires: August 27, 2012                         February 27, 2012 
                                                                         
    
                                 PBB E-VPN 
                     draft-ietf-l2vpn-pbb-evpn-00.txt 
    
   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/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 April 28, 2012. 
    
   Copyright Notice 
    
   Copyright (c) 2011 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 
    
     
   Sajassi, et. al.                                           [Page 1] 
    

    
                     draft-ietf-l2vpn-pbb-evpn-00.txt 
    
   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. 
    
    
   Abstract 
   This document discusses how Ethernet Provider Backbone Bridging 
   [802.1ah] can be combined with E-VPN in order to reduce the number 
   of BGP MAC advertisement routes by aggregating Customer/Client MAC 
   (C-MAC) addresses via Provider Backbone MAC address (B-MAC), provide 
   client MAC address mobility using C-MAC aggregation and B-MAC sub-
   netting, confine the scope of C-MAC learning to only active flows, 
   offer per site policies and avoid C-MAC address flushing on topology 
   changes. The combined solution is referred to as PBB-EVPN.  
    
    
    
    
    
   Conventions 
    
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
   document are to be interpreted as described in RFC 2119 
    
    
   Table of Contents 
    
   1. Introduction.................................................... 3 
   2. Contributors.................................................... 4 
   3. Terminology..................................................... 4 
   4. Requirements.................................................... 4 
   4.1. MAC Advertisement Route Scalability........................... 4 
   4.2. C-MAC Mobility with MAC Sub-netting........................... 5 
   4.3. C-MAC Address Learning and Confinement........................ 5 
   4.4. Interworking with TRILL and 802.1aq Access Networks with C-MAC 
   Address Transparency............................................... 5 
   4.5. Per Site Policy Support....................................... 6 
   4.6. Avoiding C-MAC Address Flushing............................... 6 
   5. Solution Overview............................................... 6 
   6. BGP Encoding.................................................... 7 
   6.1. BGP MAC Advertisement Route................................... 7 
Show full document text