Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
RFC 7623
Document | Type |
RFC - Proposed Standard
(September 2015; No errata)
Was draft-ietf-l2vpn-pbb-evpn (individual in rtg area)
|
|
---|---|---|---|
Authors | Ali Sajassi , Samer Salam , Nabil Bitar , Aldrin Isaac , Wim Henderickx | ||
Last updated | 2015-10-14 | ||
Replaces | draft-sajassi-l2vpn-pbb-evpn | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Giles Heron | ||
Shepherd write-up | Show (last changed 2014-12-01) | ||
IESG | IESG state | RFC 7623 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alvaro Retana | ||
IESG note | This document passed WG last call in the L2VPN working group and is being advanced as AD sponsored because that WG has now been closed. | ||
Send notices to | lizho.jin@gmail.com | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) A. Sajassi, Ed. Request for Comments: 7623 S. Salam Category: Standards Track Cisco ISSN: 2070-1721 N. Bitar Verizon A. Isaac Juniper W. Henderickx Alcatel-Lucent September 2015 Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN) Abstract This document discusses how Ethernet Provider Backbone Bridging (PBB) can be combined with Ethernet VPN (EVPN) in order to reduce the number of BGP MAC Advertisement routes by aggregating Customer/Client MAC (C-MAC) addresses via Provider Backbone MAC (B-MAC) address, provide client MAC address mobility using C-MAC aggregation, 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. Status of This Memo This is an Internet Standards Track document. 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). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7623. Sajassi, et al. Standards Track [Page 1] RFC 7623 PBB-EVPN September 2015 Copyright Notice Copyright (c) 2015 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 2. Terminology .....................................................4 3. Requirements ....................................................4 3.1. MAC Advertisement Route Scalability ........................5 3.2. C-MAC Mobility Independent of B-MAC Advertisements .........5 3.3. C-MAC Address Learning and Confinement .....................5 3.4. Per-Site Policy Support ....................................6 3.5. No C-MAC Address Flushing for All-Active Multihoming .......6 4. Solution Overview ...............................................6 5. BGP Encoding ....................................................7 5.1. Ethernet Auto-Discovery Route ..............................7 5.2. MAC/IP Advertisement Route .................................7 5.3. Inclusive Multicast Ethernet Tag Route .....................8 5.4. Ethernet Segment Route .....................................8 5.5. ESI Label Extended Community ...............................8 5.6. ES-Import Route Target .....................................9 5.7. MAC Mobility Extended Community ............................9 5.8. Default Gateway Extended Community .........................9 6. Operation .......................................................9 6.1. MAC Address Distribution over Core .........................9 6.2. Device Multihoming .........................................9 6.2.1. Flow-Based Load-Balancing ...........................9 6.2.1.1. PE B-MAC Address Assignment ...............10 6.2.1.2. Automating B-MAC Address Assignment .......11 6.2.1.3. Split Horizon and Designated Forwarder Election ........................12 6.2.2. Load-Balancing based on I-SID ......................12 6.2.2.1. PE B-MAC Address Assignment ...............12 6.2.2.2. Split Horizon and Designated Forwarder Election ........................13 6.2.2.3. Handling Failure Scenarios ................13Show full document text