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

Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
RFC 7180

Internet Engineering Task Force (IETF)                   D. Eastlake 3rd
Request for Comments: 7180                                      M. Zhang
Updates: 6325, 6327, 6439                                         Huawei
Category: Standards Track                                    A. Ghanwani
ISSN: 2070-1721                                                     Dell
                                                               V. Manral
                                                             Ionos Corp.
                                                             A. Banerjee
                                                        Cumulus Networks
                                                                May 2014

         Transparent Interconnection of Lots of Links (TRILL):
                Clarifications, Corrections, and Updates

Abstract

   The IETF Transparent Interconnection of Lots of Links (TRILL)
   protocol provides least-cost pair-wise data forwarding without
   configuration in multi-hop networks with arbitrary topology and link
   technology, safe forwarding even during periods of temporary loops,
   and support for multipathing of both unicast and multicast traffic.
   TRILL accomplishes this by using Intermediate System to Intermediate
   System (IS-IS) link-state routing and by encapsulating traffic using
   a header that includes a hop count.  Since publication of the TRILL
   base protocol in July 2011, active development of TRILL has revealed
   errata in  RFC 6325 and some cases that could use clarifications or
   updates.

   RFCs 6327 and 6439 provide clarifications and updates with respect to
   adjacency and Appointed Forwarders.  This document provides other
   known clarifications, corrections, and updates to RFCs 6325, 6327,
   and 6439.

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/rfc7180.

Eastlake, et al.             Standards Track                    [Page 1]
RFC 7180     TRILL: Clarifications, Corrections, and Updates    May 2014

Copyright Notice

   Copyright (c) 2014 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Eastlake, et al.             Standards Track                    [Page 2]
RFC 7180     TRILL: Clarifications, Corrections, and Updates    May 2014

Table of Contents

   1. Introduction ....................................................4
      1.1. Precedence .................................................4
      1.2. Changes That Are Not Backward Compatible ...................4
      1.3. Terminology and Acronyms ...................................5
   2. Overloaded and/or Unreachable RBridges ..........................5
      2.1. Reachability ...............................................6
      2.2. Distribution Trees .........................................6
      2.3. Overloaded Receipt of TRILL Data Frames ....................7
           2.3.1. Known Unicast Receipt ...............................7
           2.3.2. Multi-Destination Receipt ...........................7
      2.4. Overloaded Origination of TRILL Data Frames ................7
           2.4.1. Known Unicast Origination ...........................7
           2.4.2. Multi-Destination Origination .......................8
                  2.4.2.1. An Example Network .........................8
                  2.4.2.2. Indicating OOMF Support ....................9
                  2.4.2.3. Using OOMF Service .........................9
   3. Distribution Trees .............................................10
      3.1. Number of Distribution Trees ..............................10
      3.2. Clarification of Distribution Tree Updates ................10
      3.3. Multicast Pruning Based on IP Address .....................10

[include full document text]