[trill] RFC 7968 on Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination Data
rfc-editor@rfc-editor.org Thu, 01 September 2016 01:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A733612D944; Wed, 31 Aug 2016 18:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level:
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 uIr_A54Ejb5z; Wed, 31 Aug 2016 18:40:49 -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 667E912D7E1; Wed, 31 Aug 2016 18:39:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5D70BB80D47; Wed, 31 Aug 2016 18:39:23 -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
Message-Id: <20160901013923.5D70BB80D47@rfc-editor.org>
Date: Wed, 31 Aug 2016 18:39:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/IEoE_wA_eicbOH3irDDfeMkHnis>
Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org
Subject: [trill] RFC 7968 on Transparent Interconnection of Lots of Links (TRILL): Using Data Labels for Tree Selection for Multi-Destination Data
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2016 01:40:59 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7968
Title: Transparent Interconnection of Lots of
Links (TRILL): Using Data Labels for
Tree Selection for Multi-Destination Data
Author: Y. Li, D. Eastlake 3rd,
W. Hao, H. Chen,
S. Chatterjee
Status: Standards Track
Stream: IETF
Date: August 2016
Mailbox: liyizhou@huawei.com,
d3e3e3@gmail.com,
haoweiguo@huawei.com,
philips.chenhao@huawei.com,
somnath.chatterjee01@gmail.com
Pages: 22
Characters: 47260
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-trill-tree-selection-05.txt
URL: https://www.rfc-editor.org/info/rfc7968
DOI: http://dx.doi.org/10.17487/RFC7968
TRILL (Transparent Interconnection of Lots of Links) uses
distribution trees to deliver multi-destination frames. Multiple
trees can be used by an ingress Routing Bridge (RBridge) for flows,
regardless of the VLAN, Fine-Grained Label (FGL), and/or multicast
group of the flow. Different ingress RBridges may choose different
distribution trees for TRILL Data packets in the same VLAN, FGL,
and/or multicast group. To avoid unnecessary link utilization,
distribution trees should be pruned based on one or more of the
following: VLAN, FGL, or multicast destination address. If any
VLAN, FGL, or multicast group can be sent on any tree, for typical
fast-path hardware, the amount of pruning information is multiplied
by the number of trees, but there is limited hardware capacity for
such pruning information.
This document specifies an optional facility to restrict the TRILL
Data packets sent on particular distribution trees by VLAN, FGL,
and/or multicast groups, thus reducing the total amount of pruning
information so that it can more easily be accommodated by fast-path
hardware.
This document is a product of the Transparent Interconnection of Lots of Links 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