Skip to main content

TRILL Multilevel Using Unique Nicknames
draft-zhang-trill-multilevel-unique-nickname-00

Document Type Replaced Internet-Draft (trill WG)
Expired & archived
Authors Mingui Zhang , Donald E. Eastlake 3rd , Radia Perlman , Margaret Cullen , Hongjun Zhai
Last updated 2016-05-24 (Latest revision 2016-03-18)
Replaced by RFC 8397
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-trill-multilevel-unique-nickname
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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 the unique nickname approach. This approach gives unique nicknames to all TRILL switches across the multilevel TRILL campus.

Authors

Mingui Zhang
Donald E. Eastlake 3rd
Radia Perlman
Margaret Cullen
Hongjun Zhai

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)