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

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2014-12-08
Replaces draft-eastlake-trill-channel-tunnel
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
Stream WG state WG Document
Document shepherd Susan Hares
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Susan Hares" <shares@ndzh.com>
INTERNET-DRAFT                                           Donald Eastlake
Updates: 7178                                                  Yizhou Li
Intended status: Proposed Standard                                Huawei
Expires: June 7, 2015                                   December 8, 2014

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

Abstract

   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol includes an optional mechanism, called RBridge Channel and
   specified in RFC 7178, 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 two optional
   extensions to the RBridge Channel protcol: (1) A standard method to
   tunnel a variety of payload types by encapsulating them in an RBridge
   Channel message; and (2) A method to support security facilities for
   RBridge Channel messages. This document updates RFC 7178.

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.1  Terminology and Acronyms..............................3

      2. Channel Tunnel Packet Format............................4

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

      4. Security, Keying, and Algorithms.......................12
      4.1 Authentication Coverage...............................12
      4.2 SType None............................................13
      4.3 RFC 5310 Based Authentication.........................13
      4.4 xxx Based Security....................................13

      5. Channel Tunnel Errors..................................14
      5.1 SubERRs under ERR 6...................................14
      5.2 Nested RBridge Channel Errors.........................14

      6. IANA Considerations....................................15
      7. Security Considerations................................16

      Normative References......................................17
      Informative References....................................18

      Appenxid Z: Change History................................19

      Acknowledgements..........................................20
      Authors' Addresses........................................21

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

1. Introduction

   The IETF TRILL base protocol [RFC6325] has been extended with an
   optional RBridge Channel [RFC7178] facility to support transmission
   of typed messages (for example BFD [RFC7175]) between two TRILL
   switches (RBridges) in the same campus and between RBridges and end
   stations on the same link. When sent between RBridges in the same
   campus, a TRILL Data packet with a TRILL header is used and the
   destination RBridge is indicated by nickname. When sent between a
   RBridge and an end station on the same link in either direction a
   native RBridge Channel messages [RFC7178] is used with no TRILL
   header and the destination port or ports is indicated by a MAC
   address. (There is no mechanism to stop end stations on the same
   link, from sending native RBridge Channel messages to each other;
   however, such use is outside the scope of this document.)

   This document updates [RFC7178] and specifies extensions to RBridge
   Channel that provides two additional facilities as listed below.
Show full document text