TRILL Campus Extension
draft-aldrin-trill-campus-extension-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sam Aldrin , Donald E. Eastlake 3rd , Tissa Senevirathne , Ayan Banerjee , Santiago Alvarez , XiaoLan Wan | ||
| Last updated | 2013-01-10 (Latest revision 2012-07-09) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
This document presents a solution suite for TRILL campuses to be connected over WAN networks. TRILL protocol is primarily designed to work within intra-data centers. Connecting different sites over WAN using overlay tunnel protocols is the primary method employed at present. Though this presents a simple mechanisms to extend TRILL campuses over WAN networks, it also brings in the problem of scalability for TRILL nicknames exchanged between sites, latency, duplication of traffic etc. This draft proposes a way to extend the TRILL sites without having the WAN network aware of TRILL campus network and its topology. This document details on how to extend TRILL campus sites and to establish connections between various sites without having to exchange entire TRILL campus information, thus reducing the information flow to the required sites only. This document do not add or define datacenter interconnect protocol.
Authors
Sam Aldrin
Donald E. Eastlake 3rd
Tissa Senevirathne
Ayan Banerjee
Santiago Alvarez
XiaoLan Wan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)