Default Nickname Based Approach for Multilevel TRILL
draft-tissa-trill-multilevel-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Tissa Senevirathne , Les Ginsberg , Sam Aldrin , Ayan Banerjee | ||
| Last updated | 2013-05-17 (Latest revision 2012-11-13) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Multilevel TRILL allows the interconnection of multiple TRILL networks to form a larger TRILL network without proportionally increasing the size of the IS-IS LSP DB. In this document, an approach based on default route concept is presented. Also, presented in the document is a novel method of constructing multi- destination trees using partial nickname space. Methods presented in this document are compatible with the RFC6325 specified data plane operations.
Authors
Tissa Senevirathne
Les Ginsberg
Sam Aldrin
Ayan Banerjee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)