[trill] I-D Action: draft-ietf-trill-rbridge-multilevel-02.txt

internet-drafts@ietf.org Wed, 20 April 2016 01:14 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160420011452.31513.65430.idtracker@ietfa.amsl.com>
Date: Tue, 19 Apr 2016 18:14:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/BdHfdyDsWpUxlGrxVnzVHqr4iZ8>
Cc: trill@ietf.org
Subject: [trill] I-D Action: draft-ietf-trill-rbridge-multilevel-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transparent Interconnection of Lots of Links of the IETF.

        Title           : Alternatives for Multilevel TRILL (Transparent Interconnection of Lots of Links)
        Authors         : Radia Perlman
                          Donald Eastlake
                          Mingui Zhang
                          Anoop Ghanwani
                          Hongjun Zhai
	Filename        : draft-ietf-trill-rbridge-multilevel-02.txt
	Pages           : 30
	Date            : 2016-04-19

Abstract:
   Extending TRILL to multiple levels has challenges that are not
   addressed by the already-existing capability of IS-IS to have
   multiple levels.  One issue is with the handling of multi-destination
   packet distribution trees. Another issue is with TRILL switch
   nicknames.  There have been two proposed approaches.  One approach,
   which we refer 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.  The other approach, which we refer to as the
   "aggregated nickname" approach, involves hiding the nicknames within
   areas, allowing nicknames to be reused in different areas, by having
   the border TRILL switches rewrite the nickname fields when entering
   or leaving an area. Each of those approaches has advantages and
   disadvantages. This informational document suggests allowing a choice
   of approach in each area. This allows the simplicity of the unique
   nickname approach in installations in which there is no danger of
   running out of nicknames and allows the complexity of hiding the
   nicknames in an area to be phased into larger installations on a per-
   area basis.




The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-trill-rbridge-multilevel/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-trill-rbridge-multilevel-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-trill-rbridge-multilevel-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[trill] I-D Action: draft-ietf-trill-rbridge-mult… internet-drafts