RFC 8918

Invalid TLV Handling in IS-IS, September 2020

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Status:
PROPOSED STANDARD
Updates:
RFC 5305, RFC 6232
Authors:
L. Ginsberg
P. Wells
T. Li
T. Przygienda
S. Hegde
Stream:
IETF
Source:
lsr (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC8918

Discuss this RFC: Send questions or comments to lsr@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

The key to the extensibility of the Intermediate System to Intermediate System (IS-IS) protocol has been the handling of unsupported and/or invalid Type-Length-Value (TLV) tuples. Although there are explicit statements in existing specifications, deployment experience has shown that there are inconsistencies in the behavior when a TLV that is disallowed in a particular Protocol Data Unit (PDU) is received.

This document discusses such cases and makes the correct behavior explicit in order to ensure that interoperability is maximized.

This document updates RFCs 5305 and 6232.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader