File formats:

Status:

PROPOSED STANDARD

Obsoleted by:

RFC 7780

Updates:

RFC 6325, RFC 6327, RFC 6439

Authors:

D. Eastlake 3rd
M. Zhang
A. Ghanwani
V. Manral
A. Banerjee

Stream:

IETF

Source:

trill (int)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7180

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 7180

Abstract

The IETF Transparent Interconnection of Lots of Links (TRILL) protocol provides least-cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topology and link technology, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using Intermediate System to Intermediate System (IS-IS) link-state routing and by encapsulating traffic using a header that includes a hop count. Since publication of the TRILL base protocol in July 2011, active development of TRILL has revealed errata in RFC 6325 and some cases that could use clarifications or updates.

RFCs 6327 and 6439 provide clarifications and updates with respect to adjacency and Appointed Forwarders. This document provides other known clarifications, corrections, and updates to RFCs 6325, 6327, and 6439.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.