TRILL Multilevel Using Unique Nicknames
draft-ietf-trill-multilevel-unique-nickname-02

Document Type Active Internet-Draft (trill WG)
Last updated 2017-05-23
Replaces draft-zhang-trill-multilevel-unique-nickname
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd Susan Hares
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Susan Hares <shares@ndzh.com>
TRILL Working Group                                             M. Zhang
Internet Draft                                           D. Eastlake 3rd
Intended Category: Proposed Standard                              Huawei
                                                              R. Perlman
                                                                     EMC
                                                               M. Cullen
                                                       Painless Security
                                                                 H. Zhai
                                                                     JIT
                                                                  D. Liu
                                                   China Telcom Co., Ltd
Expires: November 25, 2017                                  May 24, 2017

                TRILL Multilevel Using Unique Nicknames
           draft-ietf-trill-multilevel-unique-nickname-02.txt

Abstract

   TRILL routing can be extended to support multiple levels by building
   on the multilevel feature of IS-IS routing. Depending on how
   nicknames are managed, there are two primary alternatives to realize
   TRILL multilevel: the unique nickname approach and the aggregated
   nickname approach as discussed in [MultiL]. This document specifies a
   unique nickname approach. This approach gives unique nicknames to all
   TRILL switches across the multilevel TRILL campus.

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

 

Mingui Zhang, et al    Expires November 25, 2017                [Page 1]
INTERNET-DRAFT      TRILL Multilevel Unique Nickname        May 24, 2017

Copyright and License Notice

   Copyright (c) 2017 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.

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. Acronyms and Terminology  . . . . . . . . . . . . . . . . . . .  3
   3. Data Routing  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1. Unicast Routing . . . . . . . . . . . . . . . . . . . . . .  4
     3.2. Multicast Routing . . . . . . . . . . . . . . . . . . . . .  5
       3.2.1. Local Distribution Trees  . . . . . . . . . . . . . . .  5
       3.2.2. Global Distribution Trees . . . . . . . . . . . . . . .  5
   4. Protocol Basics and Extensions  . . . . . . . . . . . . . . . .  8
     4.1. Multilevel TRILL Basics . . . . . . . . . . . . . . . . . .  8
     4.2. Nickname Allocation . . . . . . . . . . . . . . . . . . . .  8
     4.3. Nickname Announcements  . . . . . . . . . . . . . . . . . .  9
     4.4. Capability Indication . . . . . . . . . . . . . . . . . . . 11
   5. Mix with Aggregated nickname Areas  . . . . . . . . . . . . . . 11
   6. Security Considerations . . . . . . . . . . . . . . . . . . . . 12
   7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 12
   8. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     8.1. Normative References  . . . . . . . . . . . . . . . . . . . 13
     8.2. Informative References  . . . . . . . . . . . . . . . . . . 14
   Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

1. Introduction

   The multiple level feature of [IS-IS] can increase the scalability of
   TRILL as discussed in [MultiL]. However, multilevel IS-IS needs some
   extensions to support the TRILL multilevel feature. The two most
   significant extensions are how TRILL switch nicknames are managed and
Show full document text