Search RFCs

RFC Editor

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 listtrill@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) protocolprovides least-cost pair-wise data forwarding without configuration inmulti-hop networks with arbitrary topology and link technology, safeforwarding even during periods of temporary loops, and support formultipathing of both unicast and multicast traffic. TRILL accomplishes thisby using Intermediate System to Intermediate System (IS-IS) link-state routingand by encapsulating traffic using a header that includes a hop count. Sincepublication of the TRILL base protocol in July 2011, active development ofTRILL has revealed errata in RFC 6325 and some cases that could useclarifications or updates.

RFCs 6327 and 6439 provide clarifications and updates with respectto adjacency and Appointed Forwarders. This document provides otherknown clarifications, corrections, and updates to RFCs 6325, 6327,and 6439.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.