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

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

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

Abstract

   A major issue in multilevel TRILL is how to manage RBridge nicknames.
   In this document, the area border RBridge uses 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 to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   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

Copyright and License Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
 

Mingui Zhang, et al     Expires January 4, 2020                 [Page 1]
INTERNET-DRAFT      Single Nickname Multiple Levels         July 3, 2019

   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.

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. Acronyms and Terminology  . . . . . . . . . . . . . . . . . . .  3
   3. Nickname Handling on Border RBridges  . . . . . . . . . . . . .  3
     3.1. Actions on Unicast Packets  . . . . . . . . . . . . . . . .  4
     3.2. Actions on Multi-Destination Packets  . . . . . . . . . . .  5
   4. Per-flow Load Balancing . . . . . . . . . . . . . . . . . . . .  6
     4.1. Ingress Nickname Replacement  . . . . . . . . . . . . . . .  7
     4.2. Egress Nickname Replacement . . . . . . . . . . . . . . . .  7
   5. Protocol Extensions for Discovery . . . . . . . . . . . . . . .  7
     5.1. Discovery of Border RBridges in L1  . . . . . . . . . . . .  7
     5.2. Discovery of Border RBridge Sets in L2  . . . . . . . . . .  8
   6. One Border RBridge Connects Multiple Areas  . . . . . . . . . .  8
   7. E-L1FS/E-L2FS Backwards Compatibility . . . . . . . . . . . . .  9
   8. Security Considerations . . . . . . . . . . . . . . . . . . . .  9
   9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 10
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
     10.2. Informative References . . . . . . . . . . . . . . . . . . 11
   Appendix A. Clarifications . . . . . . . . . . . . . . . . . . . . 11
     A.1. Level Transition  . . . . . . . . . . . . . . . . . . . . . 11
   Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

1. Introduction

   TRILL (Transparent Interconnection of Lots of Links [RFC6325]
   [RFC7780]) multilevel techniques are designed to improve TRILL
   scalability issues. 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-
Show full document text