Last Call: <draft-ietf-l2vpn-evpn-req-05.txt> (Requirements for Ethernet VPN (EVPN)) to Informational RFC
The IESG <iesg-secretary@ietf.org> Wed, 30 October 2013 15:10 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0781221E811D; Wed, 30 Oct 2013 08:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.388
X-Spam-Level:
X-Spam-Status: No, score=-102.388 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gh96keKZzWnr; Wed, 30 Oct 2013 08:10:56 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C80DF11E8245; Wed, 30 Oct 2013 08:09:53 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-l2vpn-evpn-req-05.txt> (Requirements for Ethernet VPN (EVPN)) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.81
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20131030150953.6969.95127.idtracker@ietfa.amsl.com>
Date: Wed, 30 Oct 2013 08:09:53 -0700
Cc: l2vpn@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 15:10:57 -0000
The IESG has received a request from the Layer 2 Virtual Private Networks WG (l2vpn) to consider the following document: - 'Requirements for Ethernet VPN (EVPN)' <draft-ietf-l2vpn-evpn-req-05.txt> as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-11-27. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract The widespread adoption of Ethernet L2VPN services and the advent of new applications for the technology (e.g., data center interconnect) have culminated in a new set of requirements that are not readily addressable by the current Virtual Private LAN Service (VPLS) solution. In particular, multi-homing with all-active forwarding is not supported and there's no existing solution to leverage Multipoint-to-Multipoint (MP2MP) LSPs for optimizing the delivery of multi-destination frames. Furthermore, the provisioning of VPLS, even in the context of BGP-based auto-discovery, requires network operators to specify various network parameters on top of the access configuration. This document specifies the requirements for an Ethernet VPN (EVPN) solution which addresses the above issues. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-l2vpn-evpn-req/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-l2vpn-evpn-req/ballot/ No IPR declarations have been submitted directly on this I-D.