Sign in
Version 5.12.0.p1, 2015-03-01
Report a bug

Directory Assisted RBridge Edge

Document type: Replaced Internet-Draft (trill WG)
Document stream: IETF
Last updated: 2012-07-12 (latest revision 2012-03-11)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: Adopted by a WG
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-trill-directory-framework
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


RBridge edge nodes currently learn the mapping between MAC addresses and their corresponding RBridge edge nodes by observing the data packets traversed through. When ingress RBridge receives a data packet with its destination address (MAC&VLAN) unknown, the data packet is flooded across RBridge domain. When there are more than one RBridge ports connected to one bridged LAN, only one of them can be designated as AF port for forwarding/receiving traffic for each LAN, the rest have to be blocked for that LAN. This draft describes the framework of using directory assisted RBridge edge to improve TRILL network scalability in data center environment.


Linda Dunbar <>
Donald Eastlake <>
Radia Perlman <>
Igor Gashinsky <>

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