[trill] RFC 8243 on Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)

rfc-editor@rfc-editor.org Mon, 11 September 2017 03:02 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 165A2132CE9; Sun, 10 Sep 2017 20:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPH3GSQYA2kO; Sun, 10 Sep 2017 20:02:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AE00128D0F; Sun, 10 Sep 2017 20:02:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 91C10B80118; Sun, 10 Sep 2017 20:02:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, trill@ietf.org
Message-Id: <20170911030236.91C10B80118@rfc-editor.org>
Date: Sun, 10 Sep 2017 20:02:36 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/4f3WRV-IIwrUJr2iIZWKuqNMuFU>
Subject: [trill] RFC 8243 on Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 03:02:58 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8243

        Title:      Alternatives for Multilevel Transparent Interconnection 
                    of Lots of Links (TRILL) 
        Author:     R. Perlman, 
                    D. Eastlake 3rd,
                    M. Zhang,
                    A. Ghanwani,
                    H. Zhai
        Status:     Informational
        Stream:     IETF
        Date:       September 2017
        Mailbox:    radia@alum.mit.edu, 
                    d3e3e3@gmail.com, 
                    zhangmingui@huawei.com,
                    anoop@alumni.duke.edu, 
                    honjun.zhai@tom.com
        Pages:      29
        Characters: 66920
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-rbridge-multilevel-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8243

        DOI:        10.17487/RFC8243

Although TRILL is based on IS-IS, which supports multilevel unicast
routing, extending TRILL to multiple levels has challenges that are
not addressed by the already-existing capabilities of IS-IS.  One
issue is with the handling of multi-destination packet distribution
trees.  Other issues are with TRILL switch nicknames.  How are such
nicknames allocated across a multilevel TRILL network?  Do nicknames
need to be unique across an entire multilevel TRILL network?  Or can
they merely be unique within each multilevel area?

This informational document enumerates and examines alternatives
based on a number of factors including backward compatibility,
simplicity, and scalability; it makes recommendations in some cases.

This document is a product of the Transparent Interconnection of Lots of Links Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC