EVPN Virtual Ethernet Segment
draft-ietf-bess-evpn-virtual-eth-segment-04
|
| Document |
Type |
|
Active Internet-Draft (bess WG)
|
|
Last updated |
|
2019-01-22
(latest revision 2019-01-18)
|
|
Replaces |
|
draft-sajassi-bess-evpn-virtual-eth-segment
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
|
|
Document shepherd |
|
LucAndré Burdet
|
|
Shepherd write-up |
|
Show
(last changed 2019-02-20)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Luc André Burdet <lburdet@cisco.com>
|
Internet Working Group A. Sajassi
Internet Draft P. Brissette
Category: Standards Track Cisco
R. Schell
Verizon
J. Drake
Juniper
J. Rabadan
Nokia
Expires: July 18, 2019 January 18, 2019
EVPN Virtual Ethernet Segment
draft-ietf-bess-evpn-virtual-eth-segment-04
Abstract
EVPN and PBB-EVPN introduce a family of solutions for multipoint
Ethernet services over MPLS/IP network with many advanced features
among which their multi-homing capabilities. These solutions define
two types of multi-homing for an Ethernet Segment (ES): 1) Single-
Active and 2) All-Active, where an Ethernet Segment is defined as a
set of links between the multi-homed device/network and a set of PE
devices that they are connected to.
Some Service Providers want to extend the concept of the physical
links in an ES to Ethernet Virtual Circuits (EVCs) where many of such
EVCs can be aggregated on a single physical External Network-to-
Network Interface (ENNI). An ES that consists of a set of EVCs
instead of physical links is referred to as a virtual ES (vES). This
draft describes the requirements and the extensions needed to support
vES in EVPN and PBB-EVPN.
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."
Sajassi et al. Expires July 18, 2019 [Page 1]
INTERNET DRAFT Virtual Ethernet Segment January 18, 2019
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2014 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.
Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Virtual Ethernet Segments in Access Ethernet Networks . . . 4
1.2 Virtual Ethernet Segments in Access MPLS Networks . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1. Single-Homed & Multi-Homed Virtual Ethernet Segments . . . 8
3.2. Scalability . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3. Local Switching . . . . . . . . . . . . . . . . . . . . . . 9
3.4. EVC Service Types . . . . . . . . . . . . . . . . . . . . . 9
3.5. Designated Forwarder (DF) Election . . . . . . . . . . . . 10
3.6. OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.7. Failure & Recovery . . . . . . . . . . . . . . . . . . . . 11
3.8. Fast Convergence . . . . . . . . . . . . . . . . . . . . . 11
Sajassi et al. Expires July 18, 2019 [Page 2]
Show full document text