RBridges: Appointed Forwarders
draft-perlman-trill-rbridge-af-00

Document Type Replaced Internet-Draft (individual)
Last updated 2011-05-20 (latest revision 2011-03-29)
Replaced by draft-ietf-trill-rbridge-af
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-trill-rbridge-af
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-perlman-trill-rbridge-af-00.txt

Abstract

The IETF TRILL protocol provides optimal pair-wise data forwarding without configuration, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using IS-IS link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called RBridges. TRILL supports multi-access LAN links that can have multiple end stations and RBridges attached. Where multiple RBridges are attached to a link, native traffic to and from end stations on that link is handled by a subset of those RBridges called Appointed Forwarders, with the intent that native traffic in each VLAN be handled by at most one RBridge. The purpose of this document is to improve the documentation of the Appointed Forwarder mechanism.

Authors

Radia Perlman (radia@alum.mit.edu)
Donald Eastlake (d3e3e3@gmail.com)
Ayan Banerjee (ayabaner@cisco.com)
fangwei hu (hu.fangwei@zte.com.cn)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)