Skip to main content

TRILL: The ESADI Protocol

Document Type Replaced Internet-Draft (trill WG)
Expired & archived
Authors Hongjun Zhai , fangwei hu , Radia Perlman , Donald E. Eastlake 3rd
Last updated 2012-06-26 (Latest revision 2012-04-11)
Replaced by RFC 7357
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-trill-esadi
Consensus boilerplate Unknown
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:


The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides least cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topologies and link technologies. TRILL supports the multi-pathing of both unicast and multicast traffic. Devices that implement the TRILL protocol are called RBridges (Routing Bridges) or TRILL Switches. The ESADI (End System Address Distribution Information) protocol is a VLAN (Virtual Local Area Network) scoped way that TRILL switches can communicate end station addresses to each other. An RBridge announcing VLAN-x connectivity (normally a VLAN-x appointed forwarder) and running the TRILL ESADI protocol can receive remote address information and/or transmit local address information for VLAN-x to other such RBridges. This document updates RFC 6325, specifically the documentation of the ESADI protocol.


Hongjun Zhai
fangwei hu
Radia Perlman
Donald E. Eastlake 3rd

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