[trill] Last Call: <draft-ietf-trill-vendor-channel-00.txt> (TRILL: Vendor Specific TRILL Channel Protocol) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 21 February 2018 02:01 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: trill@ietf.org
Delivered-To: trill@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F26A91200F1; Tue, 20 Feb 2018 18:01:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-trill-vendor-channel@ietf.org, Susan Hares <shares@ndzh.com>, akatlas@gmail.com, trill-chairs@ietf.org, trill@ietf.org, shares@ndzh.com
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <151917849494.9803.606889875156182384.idtracker@ietfa.amsl.com>
Date: Tue, 20 Feb 2018 18:01:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/1sfJzGgLo3WX-HpTnNv5ax-dK1M>
Subject: [trill] Last Call: <draft-ietf-trill-vendor-channel-00.txt> (TRILL: Vendor Specific TRILL Channel Protocol) to Proposed Standard
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Feb 2018 02:01:35 -0000
The IESG has received a request from the Transparent Interconnection of Lots of Links WG (trill) to consider the following document: - 'TRILL: Vendor Specific TRILL Channel Protocol' <draft-ietf-trill-vendor-channel-00.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2018-03-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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 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. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-trill-vendor-channel/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-trill-vendor-channel/ballot/ No IPR declarations have been submitted directly on this I-D.