Skip to main content

Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames
draft-ietf-trill-multilevel-unique-nickname-07

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, Susan Hares <shares@ndzh.com>, akatlas@gmail.com, trill-chairs@ietf.org, trill@ietf.org, rfc-editor@rfc-editor.org, shares@ndzh.com, draft-ietf-trill-multilevel-unique-nickname@ietf.org
Subject: Protocol Action: 'TRILL Multilevel Using Unique Nicknames' to Proposed Standard (draft-ietf-trill-multilevel-unique-nickname-07.txt)

The IESG has approved the following document:
- 'TRILL Multilevel Using Unique Nicknames'
  (draft-ietf-trill-multilevel-unique-nickname-07.txt) as Proposed Standard

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

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-trill-multilevel-unique-nickname/


Ballot Text

Technical Summary

   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.

Working Group Summary

Consensus strong on this methodology. 

A word on TRILL WG: 
TRILL working worked on the multi-level, multiple topology work 
item together over the last 3+ years.  The WG operates with 
high discussion level at IETFs for these new features, and 
individuals working hard on drafts between time. 
During the last 12 months, early drafts in the 
multi-level,  multiple topology (E.g. RFC8243) 
have been approved. 

Document Quality

Huawei and IPInfusion have TRILL implementations, 
Scaling work was engaged in to aid long-term growth. 
No implementations of this draft have been done. 

On responses about known IPR by authors, Honjun Zhai did reply
on Feb 9 and Donald forwarded Dongxin Liu's email reply to the
trill mailing list on Feb 20.

Personnel

Document Shepherd: Susan Hares
AD: Alia Atlas 

RFC Editor Note