EVPN Virtual Ethernet Segment
draft-ietf-bess-evpn-virtual-eth-segment-19

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: =?utf-8?q?Luc_Andr=C3=A9_Burdet?= <lburdet@cisco.com>, Matthew Bocci <matthew.bocci@nokia.com>, The IESG <iesg@ietf.org>, bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-evpn-virtual-eth-segment@ietf.org, gunter@vandevelde.cc, laburdet.ietf@gmail.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'EVPN Virtual Ethernet Segment' to Proposed Standard (draft-ietf-bess-evpn-virtual-eth-segment-19.txt)

The IESG has approved the following document:
- 'EVPN Virtual Ethernet Segment'
  (draft-ietf-bess-evpn-virtual-eth-segment-19.txt) as Proposed Standard

This document is the product of the BGP Enabled ServiceS Working Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/

Ballot Text

Technical Summary

   Ethernet VPN (EVPN) and Provider Backbone EVPN (PBB-EVPN) introduce a
   comprehensive suite of solutions for delivering Ethernet services
   over MPLS/IP networks.  These solutions offer advanced features,
   including multi-homing capabilities.  Specifically, they support
   Single-Active and All-Active redundancy modes for an Ethernet Segment
   (ES), which is defined as a collection of physical links connecting a
   multi-homed device or network to a set of Provider Edge (PE) devices.
   This document extends the concept of an Ethernet Segment by allowing
   an ES to be associated with a set of Ethernet Virtual Circuits (EVCs,
   such as VLANs) or other entities, including MPLS Label Switched Paths
   (LSPs) or Pseudowires (PWs).  This extended concept is referred to as
   Virtual Ethernet Segments (vES).  This draft outlines the
   requirements and necessary extensions to support vES in both EVPN and
   PBB-EVPN.

Working Group Summary

   There is broad consensus in the working group for this to progress

Document Quality

  There are 3 known vendor implementations of this draft.
  Other outstanding comments from the earlier reviews have been addressed.

Consensus achieved- even though most reviews/comments occurred at WGLC (i.e.
late in process)

(Update from WG Co-Chair Matthew Bocci) Note that this document was sent back
to the WG for a second WG last call following an original publication request
on v07 of the draft. This was the result of a number of significant comments in
AD and IESG review and there was a desire to confirm WG consensus on the new
text to resolve these comments. There was working group consensus on this and
v14 of the draft reflects this together with a number of editorial corrections.
The response to an INTdir review was subsequently discussed on the BESS list
but the consensus was that the draft should progress as-is.

Personnel

   The Document Shepherd for this document is Luc André Burdet. The
   Responsible Area Director is Gunter Van de Velde.

RFC Editor Note