datatracker.ietf.org
Sign in
Version 5.6.3, 2014-09-19
Report a bug

Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
RFC 6326

Internet Engineering Task Force (IETF)                       D. Eastlake
Request for Comments: 6326                                        Huawei
Category: Standards Track                                    A. Banerjee
ISSN: 2070-1721                                                  D. Dutt
                                                                   Cisco
                                                              R. Perlman
                                                                   Intel
                                                             A. Ghanwani
                                                                 Brocade
                                                               July 2011

   Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS

Abstract

   The IETF has standardized the Transparent Interconnection of Lots of
   Links (TRILL) protocol, which provides transparent Layer 2 forwarding
   using encapsulation with a hop count and IS-IS link state routing.
   This document specifies the data formats and code points for the
   IS-IS extensions to support TRILL.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6326.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Eastlake, et al.             Standards Track                    [Page 1]
RFC 6326                   TRILL Use of IS-IS                  July 2011

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3
      1.1. Conventions Used in This Document ..........................3
   2. TLV and Sub-TLV Extensions to IS-IS for TRILL ...................3
      2.1. The Group Address TLV ......................................3
           2.1.1. The Group MAC Address Sub-TLV .......................4
      2.2. Multi-Topology-Aware Port Capability Sub-TLVs ..............5
           2.2.1. The Special VLANs and Flags Sub-TLV .................6
           2.2.2. Enabled-VLANs Sub-TLV ...............................7
           2.2.3. Appointed Forwarders Sub-TLV ........................8
      2.3. Sub-TLVs for the Router Capability TLV .....................9
           2.3.1. The TRILL Version Sub-TLV ...........................9
           2.3.2. The Nickname Sub-TLV ...............................10
           2.3.3. The Trees Sub-TLV ..................................11
           2.3.4. The Tree Identifiers Sub-TLV .......................11
           2.3.5. The Trees Used Identifiers Sub-TLV .................12
           2.3.6. Interested VLANs and Spanning Tree Roots Sub-TLV ...12
           2.3.7. The VLAN Group Sub-TLV .............................15
      2.4. MTU Sub-TLV of the Extended Reachability TLV ..............15
      2.5. TRILL Neighbor TLV ........................................16
   3. The MTU PDUs ...................................................18
   4. Use of Existing PDUs and TLVs ..................................19
      4.1. TRILL IIH PDUs ............................................19
      4.2. Area Address ..............................................19
      4.3. Protocols Supported .......................................19
   5. IANA Considerations ............................................20
      5.1. Allocations from Existing Registries ......................20
      5.2. New Sub-Registries Created ................................21
   6. Security Considerations ........................................22
   7. References .....................................................22
      7.1. Normative References ......................................22
      7.2. Informative References ....................................23
   8. Acknowledgements ...............................................23

[include full document text]