TRILL: RBridge Channel Header Extension
draft-ietf-trill-channel-tunnel-09

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2016-07-05 (latest revision 2016-06-12)
Replaces draft-eastlake-trill-channel-tunnel
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2016-02-08)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs one more YES or NO OBJECTION position to pass.
Responsible AD Alia Atlas
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state None
INTERNET-DRAFT                                           Donald Eastlake
Updates: 7178                                                     Huawei
Intended status: Proposed Standard                        Mohammed Umair
                                                              IPinfusion
                                                               Yizhou Li
                                                                  Huawei
Expires: December 11, 2016                                 June 12, 2016

                TRILL: RBridge Channel Header Extension
                <draft-ietf-trill-channel-tunnel-09.txt>

Abstract

   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol includes an optional mechanism (specified in RFC 7178)
   called RBridge Channel for the transmission of typed messages between
   TRILL switches in the same campus and the transmission of such
   messages between TRILL switches and end stations on the same link.
   This document specifies extensions to the RBridge Channel protocol
   header to support two features as follows: (1) a standard method to
   tunnel payloads whose type can be indicated by Ethertype through
   encapsulation in RBridge Channel messages; 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, M. Umair, & Y. Li                                  [Page 1]
INTERNET-DRAFT                          TRILL: RBridge Channel Extension

Table of Contents

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

      2. RBridge Channel Header Extension Format.................5

      3. Extended RBridge Channel Payload Types..................8
      3.1 Null Payload...........................................8
      3.2 Ethertyped Payload.....................................8
      3.2.1 RBridge Channel Message as the Payload...............9
      3.2.2 TRILL Data Packet as the Payload.....................9
      3.2.3 TRILL IS-IS Packet as the Payload...................10
      3.3 Ethernet Frame........................................11

      4. Extended RBridge Channel Security......................14
      4.1 Derived Keying Material...............................14
      4.2 SType None............................................15
      4.3 RFC 5310 Based Authentication.........................15
      4.4 DTLS Pairwise Security................................17
      4.5 Composite Security....................................18

      5. Extended RBridge Channel Errors........................19
      5.1 SubERRs under ERR 6...................................19
      5.2 Secure Nested RBridge Channel Errors..................19

      6. IANA Considerations....................................20
      6.1 Extended RBridge Channel Protocol Number..............20
      6.2 RBridge Channel Error Codes Subregistry...............20

      7. Security Considerations................................21

      Normative References......................................22
      Informative References....................................23

      Appendix Z: Change History................................24

      Acknowledgements..........................................26
      Authors' Addresses........................................27

D. Eastlake, M. Umair, & Y. Li                                  [Page 2]
INTERNET-DRAFT                          TRILL: RBridge Channel Extension

1. Introduction

   The IETF TRILL base protocol [RFC6325] [RFC7780] has been extended
   with the RBridge Channel [RFC7178] facility to support transmission
   of typed messages (for example BFD (Bidirectional Forwarding
   Detection) [RFC7175]) between two TRILL switches (RBridges) in the
   same campus and the transmission of such messages 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
Show full document text