TRILL: Vendor Specific TRILL Channel Protocol
draft-ietf-trill-vendor-channel-01

Document Type Active Internet-Draft (trill WG)
Last updated 2018-04-24 (latest revision 2018-03-09)
Replaces draft-eastlake-trill-vendor-channel
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2018-02-20)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to Susan Hares <shares@ndzh.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state AUTH48
TRILL Working Group                                      Donald Eastlake
INTERNET-DRAFT                                                 Yizhou Li
Intended status: Proposed Standard                            Weiguo Hao
                                                                  Huawei
                                                           Ayan Banerjee
                                                                   Cisco
Expires: September 7, 2018                                 March 8, 2018

             TRILL: Vendor Specific TRILL Channel Protocol
                <draft-ietf-trill-vendor-channel-01.txt>

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.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Distribution of this document is unlimited. Comments should be sent
   to the TRILL working group mailing list.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
   Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

D. Eastlake, et al                                              [Page 1]
INTERNET-DRAFT                                     TRILL: Vendor Channel

Table of Contents

      1. Introduction............................................3
      1.1 Terminology and Acronyms...............................3

      2. Vendor Channel Packet Format............................4

      3. Vendor Channel Errors...................................7
      3.1 Sending an Error Response..............................8

      4. IANA Considerations....................................10

      5. Security Considerations................................11

      Normative References......................................12
      Informative References....................................12

      Authors' Addresses........................................13

D. Eastlake, et al                                              [Page 2]
INTERNET-DRAFT                                     TRILL: Vendor Channel

1. Introduction

   The IETF TRILL (TRansparent Interconnection of Lots of Links)
   protocol [RFC6325] [RFC7780] is implemented by devices called TRILL
   switches or RBridges (Routing Bridges). It provides efficient least
   cost transparent routing in multi-hop networks with arbitrary
   topologies and link technologies, using link-state routing and a hop
   count.

   The TRILL protocol includes an RBridge Channel facility [RFC7178] to
   support typed message transmission between RBridges in the same
   campus and between RBridges and end stations on the same link. This
   document specifies a method of sending messages specified by a
   particular organization, indicated by OUI (Organizationally Unique
   Identifier) [RFC7042] or CID (Company Identifier) [802], over the
   RBridge Channel facility.  Such organization specific messages could,
   for example, be used for vendor specific diagnotic or control
   messages.

   However, note that a range of RBridge Channel protocol numbers are
   available based on RFC publication. Those intending to use the
   RBridge Channel facility are encouraged to document their use in a
   RFC and to use RBridge Channel protocol numbers based on such RFC
   publication.

1.1 Terminology and Acronyms

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   This document uses the acronyms defined in [RFC6325] supplemented by
   the following additional acronym:

   CID - Company Identifier [802]

   OUI - Organizationally Unique Identifier [RFC7042]

   TRILL switch - An alternative term for an RBridge

D. Eastlake, et al                                              [Page 3]
INTERNET-DRAFT                                     TRILL: Vendor Channel

2. Vendor Channel Packet Format
Show full document text