[trill] RFC 7782 on Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC Attachments
rfc-editor@rfc-editor.org Thu, 25 February 2016 23:55 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4B61B3827; Thu, 25 Feb 2016 15:55:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.908
X-Spam-Level:
X-Spam-Status: No, score=-106.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 oRJnNLqdC5ty; Thu, 25 Feb 2016 15:55:24 -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 A3E8C1B3842; Thu, 25 Feb 2016 15:54:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E0CD118019D; Thu, 25 Feb 2016 15:53:36 -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
Message-Id: <20160225235336.E0CD118019D@rfc-editor.org>
Date: Thu, 25 Feb 2016 15:53:36 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/rYzMn-3fdf8qKaO6pA66KTWc-Fc>
Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org
Subject: [trill] RFC 7782 on Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC Attachments
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Feb 2016 23:55:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7782
Title: Transparent Interconnection of Lots of
Links (TRILL) Active-Active Edge Using Multiple
MAC Attachments
Author: M. Zhang, R. Perlman,
H. Zhai, M. Durrani,
S. Gupta
Status: Standards Track
Stream: IETF
Date: February 2016
Mailbox: zhangmingui@huawei.com,
radia@alum.mit.edu,
honjun.zhai@tom.com,
mdurrani@cisco.com,
sujay.gupta@ipinfusion.com
Pages: 22
Characters: 47989
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-trill-aa-multi-attach-06.txt
URL: https://www.rfc-editor.org/info/rfc7782
DOI: http://dx.doi.org/10.17487/RFC7782
TRILL (Transparent Interconnection of Lots of Links) active-active
service provides end stations with flow-level load balance and
resilience against link failures at the edge of TRILL campuses, as
described in RFC 7379.
This document specifies a method by which member RBridges (also
referred to as Routing Bridges or TRILL switches) in an active-active
edge RBridge group use their own nicknames as ingress RBridge
nicknames to encapsulate frames from attached end systems. Thus,
remote edge RBridges (who are not in the group) will see one host
Media Access Control (MAC) address being associated with the multiple
RBridges in the group. Such remote edge RBridges are required to
maintain all those associations (i.e., MAC attachments) and to not
flip-flop among them (as would occur prior to the implementation of
this specification). The design goals of this specification are
discussed herein.
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