Directory Assistance Problem and High-Level Design Proposal
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 15
- Abstract
- Edge TRILL (Transparent Interconnection of Lots of Links) switches currently learn the mapping between MAC (Media Access Control) addresses and their egress TRILL switch by observing the data packets they ingress or egress or by the TRILL ESADI (End-Station Address Distribution Information) protocol. When an ingress TRILL switch receives a data frame for a destination address (MAC&Label) that the switch does not know, the data frame is flooded within the frame's Data Label across the TRILL campus. This document describes the framework for using directory services to assist edge TRILL switches in reducing multi-destination frames, particularly unknown unicast frames flooding, and ARP/ND (Address Resolution Protocol / Neighbor Discovery), thus improving TRILL network scalability and security.
- Publication Date
- 2013-11-01
- Status Note
- Informational
- DOI
10.17487/RFC7067- Link
- https://doi.org/10.17487/RFC7067
- Author(s)
- Linda DunbarDonald E. Eastlake 3rdRadia PerlmanIgor Gashinsky
- Keyword(s)
- TRILL, Orchestration, Directory Services, ARP
Latest version of IETF RFC 7067
Document Versions — IETF RFC 7067
-
▶ IETF RFC 7067 (2013-11-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IEEE.STD802.1Q.2011 — 802.1Q EXTERNAL
- ISO.10589.2002 — 1 EXTERNAL
- Zhai, H., Hu, F., Perlman, R., Eastlake 3rd, D., and O. Stokes, "TRILL (Transparent Interconnection of Lots of Links): ESADI (End Station Address Distribution Information) Protocol", Work in Progress, July 2013. EXTERNAL
- Eastlake 3rd, D., Zhang, M., Agarwal, P., Perlman, R., and D. Dutt, "TRILL (Transparent Interconnection of Lots of Links): Fine-Grained Labeling", Work in Progress, May 2013. EXTERNAL
- IETF RFC 826 [Active*]
- IETF RFC 3971 [Active*]
- IETF RFC 4861 [Active*]
- IETF RFC 6325 [Active*]
- IETF RFC 6326 [Superseded*]
- IETF RFC 6439 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7067.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7067, Directory Assistance Problem and High-Level Design Proposal. Available at https://doi.org/10.17487/RFC7067
Snippet:
IETF RFC 7067, Directory Assistance Problem and High-Level Design Proposal. Available at https://doi.org/10.17487/RFC7067
HTML (ISO 690 compliant)
Preview:
IETF RFC 7067, Directory Assistance Problem and High-Level Design Proposal. Available at https://doi.org/10.17487/RFC7067
Snippet:
<span class="citation"><cite>IETF RFC 7067</cite>, Directory Assistance Problem and High-Level Design Proposal. Available at <a href="https://doi.org/10.17487/RFC7067" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7067</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7067, Directory Assistance Problem and High-Level Design Proposal
doi: 10.17487/RFC7067
url: https://doi.org/10.17487/RFC7067
doi: 10.17487/RFC7067
url: https://doi.org/10.17487/RFC7067
Snippet:
<li> <cite id="bib-rfc7067">IETF RFC 7067</cite>, Directory Assistance Problem and High-Level Design Proposal <span class="doi">10.17487/RFC7067</span> </li>
Referenced By
- IETF RFC 7780 [Active*]
- IETF RFC 7938 [Active*]
- IETF RFC 7961 [Active*]
- IETF RFC 7978 [Active*]