Multicast Link State For Rbidges
draft-hares-trill-multicast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Susan Hares | ||
| Last updated | 2005-10-20 | ||
| 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
Rbridges are transparent Layer 2 bridges that provide the ability to have an entire campus, with multiple physical links look like a single subnet. The Rbridge technology utilizes Rbridges to link together Layer 2 areas using spanning trees to calculate paths. The Rbridges run a link state protocol to determine the least cost paths Rbridges and exchange information about the location of MAC addresses. The Rbridges will run a level 1 or a single area routing protocol. To forward multicast packets, the Rbirdges may treat these as broadcast (sending the packets to all Rbridges) or use methods to snoop the Multicast MAC addresses (GARP, MAC learning) or IP/MAC address packets (IGMP/PIM snooping). Multicast Link State Rbridge connections suggest a Hybrid Multicast Link state extensions to ISIS and OSPF for Rbridges.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)