[bess] RFC 8214 on Virtual Private Wire Service Support in Ethernet VPN

rfc-editor@rfc-editor.org Wed, 23 August 2017 20:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E471321C0; Wed, 23 Aug 2017 13:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 xxSbOcV7smzh; Wed, 23 Aug 2017 13:29:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46556132441; Wed, 23 Aug 2017 13:29:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 28D17B80D37; Wed, 23 Aug 2017 13:29:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bess@ietf.org
Message-Id: <20170823202927.28D17B80D37@rfc-editor.org>
Date: Wed, 23 Aug 2017 13:29:27 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/zl51TfnTLNC0L2DEMx0EGPVI0KE>
Subject: [bess] RFC 8214 on Virtual Private Wire Service Support in Ethernet VPN
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Aug 2017 20:29:58 -0000

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

        
        RFC 8214

        Title:      Virtual Private Wire Service Support 
                    in Ethernet VPN 
        Author:     S. Boutros, 
                    A. Sajassi,
                    S. Salam,
                    J. Drake,
                    J. Rabadan
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2017
        Mailbox:    sboutros@vmware.com, 
                    sajassi@cisco.com, 
                    ssalam@cisco.com,
                    jdrake@juniper.net, 
                    jorge.rabadan@nokia.com
        Pages:      17
        Characters: 34563
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-evpn-vpws-14.txt

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

        DOI:        10.17487/RFC8214

This document describes how Ethernet VPN (EVPN) can be used to
support the Virtual Private Wire Service (VPWS) in MPLS/IP networks.
EVPN accomplishes the following for VPWS: provides Single-Active as
well as All-Active multihoming with flow-based load-balancing,
eliminates the need for Pseudowire (PW) signaling, and provides fast
protection convergence upon node or link failure.

This document is a product of the BGP Enabled Services 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/retrieve/bulk

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