RFC 8249: Transparent Interconnection of Lots of Links (TRILL): MTU Negotiation
In plain English — editorial summary, not part of the RFC
The base IETF TRILL (Transparent Interconnection of Lots of Links) protocol has a TRILL campus-wide MTU feature, specified in RFCs 6325 and 7177, that assures that link-state changes can be successfully flooded throughout the campus while being able to take advantage of a campus-wide capability to support jumbo packets. This document specifies recommended updates to that MTU feature to take advantage, for appropriate link-local packets, of link-local MTUs that exceed the TRILL campus MTU. In addition, it specifies an efficient algorithm for local MTU testing. This document updates RFCs 6325, 7177, and 7780.
Document record
- Document ID
- RFC8249
- Published
- September 2017
- Authors
- M. Zhang; X. Zhang; D. Eastlake 3rd; R. Perlman; S. Chatterjee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8245Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444Current
October 2017
- RFC 8253PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)Updated
October 2017
- RFC 8243Alternatives for Multilevel Transparent Interconnection of Lots of Links (TRILL)Current
September 2017
- RFC 8256Requirements for Hitless MPLS Path Segment MonitoringCurrent
October 2017
- RFC 8242Interface to the Routing System (I2RS) Ephemeral State RequirementsCurrent
September 2017
- RFC 8241Interface to the Routing System (I2RS) Security-Related RequirementsCurrent
September 2017
- RFC 8258Generalized SCSI: A Generic Structure for Interface Switching Capability Descriptor (ISCD) Switching Capability Specific Information (SCSI)Current
October 2017
- RFC 8237MPLS Label Switched Path (LSP) Pseudowire (PW) Status Refresh Reduction for Static PWsCurrent
October 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?