BGP MPLS-Based Ethernet VPN
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, l2vpn mailing list <email@example.com>, l2vpn chair <firstname.lastname@example.org> Subject: Protocol Action: 'BGP MPLS Based Ethernet VPN' to Proposed Standard (draft-ietf-l2vpn-evpn-11.txt) The IESG has approved the following document: - 'BGP MPLS Based Ethernet VPN' (draft-ietf-l2vpn-evpn-11.txt) as Proposed Standard This document is the product of the Layer 2 Virtual Private Networks Working Group. The IESG contact persons are Adrian Farrel and Alia Atlas. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-l2vpn-evpn/
Technical Summary: This document describes procedures for BGP MPLS based Ethernet VPNs (EVPN). The procedures described here are intended to meet the requirements specified in RFC7209 - Requirements for Ethernet VPN. EVPN requires extensions to existing IP/MPLS protocols as described in this document, but also uses several building blocks from existing MPLS technologies. Working Group Summary: This document is an L2VPN Working Group document, and has been reviewed in the working group through multiple iterations of the draft. Document Quality: The document is long (50 pages) and detailed, however this is due to the inherent complexity of the problem which EVPN solves - namely the provision of scalable E-LAN services with support for active/active attachment (i.e. the ability for CE devices to load balance across multiple PEs). The document has been through multiple revisions and is now sufficiently stable to progress to RFC, and more importantly to be used as a reference for creating interoperable implementations. Personnel: Document Shepherd: Giles Heron (email@example.com) Area Director: Adrian Farrel (firstname.lastname@example.org) RFC Editor Note There are seven front page authors listed on this document. This is a considered position reflecting the politics of this work. The RFC Editor is asked to make an exception for this document.