Transparent Interconnection of Lots of Links (TRILL) Single Area Border RBridge Nickname for Multilevel
draft-ietf-trill-multilevel-single-nickname-12

Document Type Active Internet-Draft (individual in rtg area)
Last updated 2020-07-09
Replaces draft-zhang-trill-multilevel-single-nickname
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Susan Hares
IESG IESG state Waiting for Writeup
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Vigoureux
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
INTERNET-DRAFT                                                  M. Zhang
Intended Status: Proposed Standard                                Huawei
                                                             D. Eastlake
                                                               Futurewei
                                                              R. Perlman
                                                                     EMC
                                                               M. Cullen
                                                       Painless Security
                                                                 H. Zhai
                                                                     JIT
Expires: January 6, 2021                                    July 7, 2020

           Transparent Interconnection of Lots of Links (TRILL)
            Single Area Border RBridge Nickname for Multilevel
            draft-ietf-trill-multilevel-single-nickname-12.txt

Abstract
   A major issue in multilevel TRILL is how to manage RBridge nicknames.
   In this document, area border RBridges use a single nickname in both
   Level 1 and Level 2. RBridges in Level 2 must obtain unique nicknames
   but RBridges in different Level 1 areas may have the same nicknames.

Status of This Memo

   This Internet-Draft is submitted 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 IDR Working Group mailing list <idr@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.

M. Zhang, et al                                                 [Page 1]
INTERNET-DRAFT                                Multilevel Single Nickname

Table of Contents

      1. Introduction............................................3
      2. Acronyms and Terminology................................4

      3. Nickname Handling on Border RBridges....................5
      3.1. Actions on Unicast Packets............................5
      3.2. Actions on Multi-Destination Packets..................6

      4. Per-flow Load Balancing.................................9
      4.1. Ingress Nickname Replacement..........................9
      4.2. Egress Nickname Replacement...........................9

      5. Protocol Extensions for Discovery......................10
      5.1. Discovery of Border RBridges in L1...................10
      5.2. Discovery of Border RBridge Sets in L2...............10

      6. One Border RBridge Connects Multiple Areas.............12
      7. E-L1FS/E-L2FS Backwards Compatibility..................13

      8. Manageability Considerations...........................13
      9. Security Considerations................................15
      10. IANA Considerations...................................15

      11. References............................................16
      11.1. Normative References................................16
      11.2. Informative References..............................17

      Appendix A. Level Transition Clarification................18

      Authors' Addresses........................................19

M. Zhang, et al                                                 [Page 2]
INTERNET-DRAFT                                Multilevel Single Nickname

1. Introduction

   TRILL (Transparent Interconnection of Lots of Links [RFC6325]
   [RFC7780]) multilevel techniques are designed to improve TRILL
   scalability issues.

   Informational [RFC8243] is an educational document to explain
   multilevel TRILL and list possible concerns. It does not specify a
   protocol. As described in [RFC8243], there have been two proposed
   approaches. One approach, which is referred to as the "unique
   nickname" approach, gives unique nicknames to all the TRILL switches
   in the multilevel campus, either by having the Level 1/Level 2 border
   TRILL switches advertise which nicknames are not available for
   assignment in the area, or by partitioning the 16-bit nickname into
   an "area" field and a "nickname inside the area" field. [RFC8397] is
   the standards track document specifying a "unique nickname" flavor of
   TRILL multilevel. The other approach, which is referred to in
   [RFC8243] as the "aggregated nickname" approach, involves assigning
Show full document text