Rbridges: Base Protocol Specification
draft-perlman-trill-rbridge-protocol-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Radia Perlman , Dr. Joseph D. Touch | ||
| Last updated | 2008-04-16 (Latest revision 2006-02-15) | ||
| Replaced by | draft-ietf-trill-rbridge-protocol | ||
| 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-ietf-trill-rbridge-protocol | |
| 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 provide the ability to have an entire campus, with multiple physical links, look to IP like a single subnet. The design allows for zero configuration of switches within a campus, optimal pair-wise routing, safe forwarding even during periods of temporary loops, and the ability to cut down on ARP/ND traffic. The design also supports VLANs, and allows forwarding tables to be based on RBridge destinations (rather than endnode destinations), which allows internal routing tables to be substantially smaller than in conventional bridge systems.
Authors
Radia Perlman
Dr. Joseph D. Touch
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)