RFC 7432 on BGP MPLS-Based Ethernet VPN

rfc-editor@rfc-editor.org Wed, 18 February 2015 23:01 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFC61A1B59; Wed, 18 Feb 2015 15:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cX0AXYKejv6h; Wed, 18 Feb 2015 15:01:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 22F551A1B96; Wed, 18 Feb 2015 15:01:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2ACF4181D1F; Wed, 18 Feb 2015 15:01:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7432 on BGP MPLS-Based Ethernet VPN
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150218230141.2ACF4181D1F@rfc-editor.org>
Date: Wed, 18 Feb 2015 15:01:41 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/l2vpn/wQu7oHk77BkGkZ1044mGOdkfV4I>
Cc: l2vpn@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Feb 2015 23:01:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7432

        Title:      BGP MPLS-Based Ethernet VPN 
        Author:     A. Sajassi, Ed.,
                    R. Aggarwal, N. Bitar,
                    A. Isaac, J. Uttaro,
                    J. Drake, W. Henderickx
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2015
        Mailbox:    sajassi@cisco.com, 
                    raggarwa_1@yahoo.com, 
                    nabil.n.bitar@verizon.com,
                    aisaac71@bloomberg.net, 
                    uttaro@att.com, 
                    jdrake@juniper.net, 
                    wim.henderickx@alcatel-lucent.com
        Pages:      56
        Characters: 134119
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-evpn-11.txt

        URL:        https://www.rfc-editor.org/info/rfc7432

This document describes procedures for BGP MPLS-based Ethernet VPNs
(EVPN).  The procedures described here meet the requirements specified
in RFC 7209 -- "Requirements for Ethernet VPN (EVPN)".

This document is a product of the Layer 2 Virtual Private Networks Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC