[bess] RFC 8317 on Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)
rfc-editor@rfc-editor.org Thu, 01 February 2018 00:44 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 6634912D835; Wed, 31 Jan 2018 16:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 ZW2PQvv5cMpZ; Wed, 31 Jan 2018 16:44:53 -0800 (PST)
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 E193A12EAE7; Wed, 31 Jan 2018 16:44:53 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CE7EFB8171B; Wed, 31 Jan 2018 16:44:29 -0800 (PST)
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: <20180201004429.CE7EFB8171B@rfc-editor.org>
Date: Wed, 31 Jan 2018 16:44:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Ybu1VMDnVOjdTWf1fnGhT0ACFxI>
Subject: [bess] RFC 8317 on Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)
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: Thu, 01 Feb 2018 00:44:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8317
Title: Ethernet-Tree (E-Tree) Support in Ethernet
VPN (EVPN) and Provider Backbone Bridging
EVPN (PBB-EVPN)
Author: A. Sajassi, Ed.,
S. Salam,
J. Drake,
J. Uttaro,
S. Boutros,
J. Rabadan
Status: Standards Track
Stream: IETF
Date: January 2018
Mailbox: sajassi@cisco.com,
ssalam@cisco.com,
jdrake@juniper.net,
ju1738@att.com,
sboutros@vmware.com,
jorge.rabadan@nokia.com
Pages: 23
Characters: 53519
Updates: RFC 7385
I-D Tag: draft-ietf-bess-evpn-etree-14.txt
URL: https://www.rfc-editor.org/info/rfc8317
DOI: 10.17487/RFC8317
The MEF Forum (MEF) has defined a rooted-multipoint Ethernet service
known as Ethernet-Tree (E-Tree). A solution framework for supporting
this service in MPLS networks is described in RFC 7387, "A Framework
for Ethernet-Tree (E-Tree) Service over a Multiprotocol Label
Switching (MPLS) Network". This document discusses how those
functional requirements can be met with a solution based on RFC 7432,
"BGP MPLS Based Ethernet VPN (EVPN)", with some extensions and a
description of how such a solution can offer a more efficient
implementation of these functions than that of RFC 7796,
"Ethernet-Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)".
This document makes use of the most significant bit of the Tunnel Type
field (in the P-Multicast Service Interface (PMSI) Tunnel attribute)
governed by the IANA registry created by RFC 7385; hence, it updates
RFC 7385 accordingly.
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