[trill] RFC 8381 on Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol
rfc-editor@rfc-editor.org Tue, 22 May 2018 05:39 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 A914B12DA22; Mon, 21 May 2018 22:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 cMCvXPGegB0Y; Mon, 21 May 2018 22:39:46 -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 C65B2124B18; Mon, 21 May 2018 22:39:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 735F8B828BD; Mon, 21 May 2018 22:39:36 -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, trill@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180522053936.735F8B828BD@rfc-editor.org>
Date: Mon, 21 May 2018 22:39:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/HTvjMp3HkaceWeZRDq1FA8HPAhU>
Subject: [trill] RFC 8381 on Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 22 May 2018 05:39:49 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8381 Title: Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol Author: D. Eastlake 3rd, Y. Li, W. Hao, A. Banerjee Status: Standards Track Stream: IETF Date: May 2018 Mailbox: d3e3e3@gmail.com, liyizhou@huawei.com, haoweiguo@huawei.com, ayabaner@cisco.com Pages: 11 Characters: 22410 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trill-vendor-channel-01.txt URL: https://www.rfc-editor.org/info/rfc8381 DOI: 10.17487/RFC8381 The IETF TRILL (Transparent Interconnection of Lots of Links) protocol is implemented by devices called TRILL switches or RBridges (Routing Bridges). TRILL includes a general mechanism, called an RBridge Channel, for the transmission of typed messages between RBridges in the same campus and between RBridges and end stations on the same link. This document specifies a method to send vendor-specific messages over the RBridge Channel facility. 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