datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

TRILL: Clarifications, Corrections, and Updates
draft-ietf-trill-clear-correct-06

TRILL Working Group                                      Donald Eastlake
INTERNET-DRAFT                                              Mingui Zhang
Intended status: Proposed Standard                                Huawei
Updates: 6325, 6327, 6439                                 Anoop Ghanwani
                                                                    Dell
                                                          Vishwas Manral
                                                         Hewlett-Packard
                                                           Ayan Banerjee
                                                        Cumulus Networks
Expires: January 29, 2013                                  July 30, 2012

            TRILL: Clarifications, Corrections, and Updates
                <draft-ietf-trill-clear-correct-06.txt>

Abstract

   The IETF TRILL (TRansparent Interconnection of Lots of Links)
   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 IS-IS (Intermediate System to
   Intermediate System) link state routing and by encapsulating traffic
   using a header that includes a hop count. Since the TRILL base
   protocol was approved in March 2010, active development of TRILL has
   revealed errata in the original RFC 6325 and some cases that could
   use clarifications or updates.

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

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 TRILL working group
   mailing list <rbridge@postel.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."

D. Eastlake, et al                                              [Page 1]
INTERNET-DRAFT                     TRILL: Clarifications and Corrections

   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, et al                                              [Page 2]
INTERNET-DRAFT                     TRILL: Clarifications and Corrections

Table of Contents

      1. Introduction............................................4
      1.1 Precedence.............................................4
      1.2 Changes That Are Not Backwards Compatible..............4
      1.3 Terminology and Acronyms...............................5

      2. Overloaded and/or Unreachable RBridges..................6
      2.1 Reachability...........................................6
      2.2 Distribution Trees.....................................7
      2.3 Overloaded Receipt of TRILL Data Frames................7
      2.3.1 Known Unicast Receipt................................7
      2.3.2 Multi-Destination Receipt............................8
      2.4 Overloaded Origination of TRILL Data Frames............8
      2.4.1 Known Unicast Origination............................8
      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................................10

      3. Distribution Trees.....................................11
      3.1 Number of Distribution Trees..........................11
      3.2 Clarification of Distribution Tree Updates............11
      3.3 IP Address Based Multicast Pruning....................11
      3.4 Numbering of Distribution Trees.......................12

      4. Nickname Selection.....................................13

      5. MTU (Maximum Transmission Unit)........................15
      5.1 MTU Related Errata in RFC 6325........................15
      5.1.1 MTU PDU Addressing..................................15
      5.1.2 MTU PDU Processing..................................16

[include full document text]