RFC 7623 on Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
rfc-editor@rfc-editor.org Tue, 22 September 2015 00:01 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747D91A92FC for <ietf-announce@ietfa.amsl.com>; Mon, 21 Sep 2015 17:01:31 -0700 (PDT)
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 6_rkOhnlFfVV for <ietf-announce@ietfa.amsl.com>; Mon, 21 Sep 2015 17:01:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id B9E8B1A92B4 for <ietf-announce@ietf.org>; Mon, 21 Sep 2015 17:01:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B29C2182534; Mon, 21 Sep 2015 17:00:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7623 on Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150922000041.B29C2182534@rfc-editor.org>
Date: Mon, 21 Sep 2015 17:00:41 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/ASM3NXDwwO6fRFIiSiup505cyJg>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 22 Sep 2015 00:01:31 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7623
Title: Provider Backbone Bridging Combined with
Ethernet VPN (PBB-EVPN)
Author: A. Sajassi, Ed.,
S. Salam,
N. Bitar,
A. Isaac,
W. Henderickx
Status: Standards Track
Stream: IETF
Date: September 2015
Mailbox: sajassi@cisco.com,
ssalam@cisco.com,
nabil.n.bitar@verizon.com,
aisaac@juniper.net,
wim.henderickx@alcatel-lucent.com
Pages: 23
Characters: 52595
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-l2vpn-pbb-evpn-10.txt
URL: https://www.rfc-editor.org/info/rfc7623
DOI: http://dx.doi.org/10.17487/RFC7623
This document discusses how Ethernet Provider Backbone Bridging (PBB)
can be combined with Ethernet VPN (EVPN) in order to reduce the
number of BGP MAC Advertisement routes by aggregating Customer/Client
MAC (C-MAC) addresses via Provider Backbone MAC (B-MAC) address,
provide client MAC address mobility using C-MAC aggregation, confine
the scope of C-MAC learning to only active flows, offer per-site
policies, and avoid C-MAC address flushing on topology changes. The
combined solution is referred to as PBB-EVPN.
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