Directory Assisted RBridge Edge
draft-dunbar-trill-directory-assisted-edge-05
Document | Type |
Replaced Internet-Draft
(trill WG)
Expired & archived
|
|
---|---|---|---|
Authors | Linda Dunbar , Donald E. Eastlake 3rd , Radia Perlman , Igor Gashinsky | ||
Last updated | 2012-07-12 (Latest revision 2012-03-11) | ||
Replaced by | draft-ietf-trill-directory-framework | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-trill-directory-framework | |
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:
Abstract
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.
Authors
Linda Dunbar
Donald E. Eastlake 3rd
Radia Perlman
Igor Gashinsky
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)