Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol
RFC 8381

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: draft-ietf-trill-vendor-channel@ietf.org, Susan Hares <shares@ndzh.com>, akatlas@gmail.com, trill-chairs@ietf.org, trill@ietf.org, The IESG <iesg@ietf.org>, shares@ndzh.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'TRILL: Vendor Specific TRILL Channel Protocol' to Proposed Standard (draft-ietf-trill-vendor-channel-01.txt)

The IESG has approved the following document:
- 'TRILL: Vendor Specific TRILL Channel Protocol'
  (draft-ietf-trill-vendor-channel-01.txt) as Proposed Standard

This document is the product of the Transparent Interconnection of Lots of
Links Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-trill-vendor-channel/


Technical Summary

  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.

Working Group Summary

  Working group pushed for this draft even though
  it came at the end of work.  It provides a way for 
  TRILL vendors to send vendor specific messages. 
  This feature will allow the vendors to innovate 
  and then come back to IETF with "baked"
  features for standardizing.

Document Quality

No protocol implementations, but it is important for future vendor-dependent
innovation - and the document is straightforward.

Personnel

   Document Shepherd: Sue Hares 
   Responsible Area Director: Alia Atlas