Search RFCs
RFC 7067
Directory Assistance Problem and High-Level Design Proposal,November 2013
- File formats:
- Status:
- INFORMATIONAL
- Authors:
- L. Dunbar
D. Eastlake 3rd
R. Perlman
I. Gashinsky - Stream:
- IETF
- Source:
- trill (int)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7067
Discuss this RFC: Send questions or comments to the mailing listtrill@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7067
Abstract
Edge TRILL (Transparent Interconnection of Lots of Links) switchescurrently learn the mapping between MAC (Media Access Control)addresses and their egress TRILL switch by observing the data packetsthey ingress or egress or by the TRILL ESADI (End-Station AddressDistribution Information) protocol. When an ingress TRILL switchreceives a data frame for a destination address (MAC&Label) that theswitch does not know, the data frame is flooded within the frame'sData Label across the TRILL campus.
This document describes the framework for using directory services toassist edge TRILL switches in reducing multi-destination frames,particularly unknown unicast frames flooding, and ARP/ND (AddressResolution Protocol / Neighbor Discovery), thus improving TRILLnetwork scalability and security.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.