TRILL: RBridge Channel Tunnel Protocol
draft-ietf-trill-channel-tunnel-00

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2013-12-05
Replaces draft-eastlake-trill-channel-tunnel
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                           Donald Eastlake
Updates: RFCchannel                                            Yizhou Li
Intended status: Proposed Standard                                Huawei
Expires: June 4, 2014                                   December 5, 2013

                 TRILL: RBridge Channel Tunnel Protocol
                <draft-ietf-trill-channel-tunnel-00.txt>

Abstract

   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol includes an optional mechanism, called RBridge Channel, for
   the transmission of typed messages between TRILL switches in the same
   campus and between TRILL switches and end stations on the same link.
   This document specifies optional extensions to RBridge Channel that
   provides three facilities: (1) A mechanism to send such messages
   between a TRILL switch and an end station in either direction, or
   between two end stations, when the two devices are in the same campus
   but not on the same link; (2) A method to support security facilities
   for RBridge Channel messages; and (3) A method to tunnel a variety of
   payload types by encapsulating them in an RBridge Channel message.

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 authors or the TRILL working group mailing list:
   trill@ietf.org

   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 & Y. Li                                             [Page 1]
INTERNET-DRAFT                             TRILL: RBridge Channel Tunnel

Table of Contents

      1. Introduction............................................3
      1.2.  Terminology and Acronyms.............................3

      2. Channel Tunnel Packet Format............................5

      3. Tunnel Payload Types....................................8
      3.1 Null Payload...........................................8
      3.2 RBridge Channel Message Payload........................8
      3.3 TRILL Data Packet......................................9
      3.4 TRILL IS-IS Packet....................................10
      3.5 Ethernet Frame........................................11

      4. Channel Tunnel Scopes..................................13
      4.1 End Station to RBridge(s).............................14
      4.2 RBridge to End Station................................15
      4.3 End Station to End Station............................16

      5. Security, Keying, and Algorithms.......................18
      5.1 Authentication Coverage...............................18
      5.2 SType None............................................19
      5.3 RFC 5310 Based Authentication.........................19
      5.4 DTLS Based Security...................................20

      6. Channel Tunnel Errors..................................21
      6.1 SubERRs under ERR 6...................................21
      6.2 Nested RBridge Channel Errors.........................21

      7. IANA Considerations....................................22
      8. Security Considerations................................22

      Normative References......................................23
      Informative References....................................23
      Acknowledgements..........................................25
      Authors' Addresses........................................26

D. Eastlake & Y. Li                                             [Page 2]
INTERNET-DRAFT                             TRILL: RBridge Channel Tunnel

1. Introduction

   The IETF TRILL protocol [RFC6325] includes an optional RBridge
   Channel [RFCchannel] facility to support transmission of typed
   messages (for example BFD [RFCbfd]) between two RBridges in the same
   campus and between RBridges and end stations on the same link.  This
   document specifies optional extensions to RBridge Channel that
   provides three facilities:

      (1) A mechanism to send RBridge Channel messages between a TRILL
          switch (RBridge) and an end station in either direction, or
          between two end stations, when the two devices are in the same
          campus but not on the same link. This mechanism requires the
Show full document text