RFC 8302
Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) Optimization, January 2018
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- Y. Li
D. Eastlake 3rd
L. Dunbar
R. Perlman
M. Umair - Stream:
- IETF
- Source:
- trill (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8302
Discuss this RFC: Send questions or comments to the mailing list trill@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8302
Abstract
This document describes mechanisms to optimize the Address Resolution Protocol (ARP) and Neighbor Discovery (ND) traffic in a Transparent Interconnection of Lots of Links (TRILL) campus. TRILL switches maintain a cache of IP / Media Access Control (MAC) address / Data Label bindings that are learned from ARP/ND requests and responses that pass through them. In many cases, this cache allows an edge Routing Bridge (RBridge) to avoid flooding an ARP/ND request by either responding to it directly or encapsulating it and unicasting it. Such optimization reduces packet flooding over a TRILL campus.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.