[bess] RFC 8560 on Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents
rfc-editor@rfc-editor.org Thu, 09 May 2019 17:13 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 BCB6B12011E; Thu, 9 May 2019 10:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 A0Pxj2Jabu9M; Thu, 9 May 2019 10:13:14 -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 E8A4612012D; Thu, 9 May 2019 10:13:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2ADC9B82A93; Thu, 9 May 2019 10:13:08 -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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190509171308.2ADC9B82A93@rfc-editor.org>
Date: Thu, 09 May 2019 10:13:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/IZpLvi1Xy_nBHnGIJIZWLHGCzyY>
Subject: [bess] RFC 8560 on Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 09 May 2019 17:13:16 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8560
Title: Seamless Integration of Ethernet VPN (EVPN)
with Virtual Private LAN Service (VPLS)
and Their Provider Backbone Bridge (PBB)
Equivalents
Author: A. Sajassi, Ed.,
S. Salam,
N. Del Regno,
J. Rabadan
Status: Standards Track
Stream: IETF
Date: May 2019
Mailbox: sajassi@cisco.com,
ssalam@cisco.com,
nick.delregno@verizon.com,
jorge.rabadan@nokia.com
Pages: 16
Characters: 34654
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-evpn-vpls-seamless-integ-07.txt
URL: https://www.rfc-editor.org/info/rfc8560
DOI: 10.17487/RFC8560
This document specifies mechanisms for backward compatibility of
Ethernet VPN (EVPN) and Provider Backbone Bridge Ethernet VPN
(PBB-EVPN) solutions with Virtual Private LAN Service (VPLS) and Provider
Backbone Bridge VPLS (PBB-VPLS) solutions. It also provides
mechanisms for the seamless integration of these two technologies in
the same MPLS/IP network on a per-VPN-instance basis. Implementation
of this document enables service providers to introduce EVPN/PBB-EVPN
Provider Edges (PEs) in their brownfield deployments of VPLS/PBB-VPLS
networks. This document specifies the control-plane and forwarding
behavior needed for the auto-discovery of the following: 1) a VPN
instance, 2) multicast and unicast operation, and 3) a Media Access
Control (MAC) mobility operation. This enables seamless integration
between EVPN and VPLS PEs as well as between PBB-VPLS and PBB-EVPN
PEs.
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