RBridges: Use of IS-IS
draft-eastlake-trill-rbridge-isis-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Donald E. Eastlake 3rd , Dinesh G. Dutt, Radia Perlman | ||
Last updated | 2011-05-20 (Latest revision 2008-11-03) | ||
Replaced by | draft-eastlake-isis-trill | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-eastlake-isis-trill | |
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
RBridges implement the TRILL protocol, which in turn makes use of an extended version of the IS-IS (Intermediate System to Intermediate System) routing protocol to determine topology and frame forwarding and for the distribution and synchronization of data. RBridges provide optimal pair-wise forwarding with zero configuration, safe forwarding even during periods of temporary loops, and multipathing for both unicast and multicast traffic. Rbridges also support VLANs. This document specifies some details of IS-IS PDUs used in TRILL.
Authors
Donald E. Eastlake 3rd
Dinesh G. Dutt
Radia Perlman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)