%% You should probably cite draft-ietf-lsr-isis-invalid-tlv instead of this I-D. @techreport{ginsberg-lsr-isis-invalid-tlv-03, number = {draft-ginsberg-lsr-isis-invalid-tlv-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ginsberg-lsr-isis-invalid-tlv/03/}, author = {Les Ginsberg and Paul Wells and Tony Li and Tony Przygienda and Shraddha Hegde}, title = {{Invalid TLV Handling in IS-IS}}, pagetotal = 8, year = 2019, month = apr, day = 3, abstract = {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 which 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 insure that interoperability is maximized. This document when approved updates RFC3563, RFC5305, RFC6232, and RFC6233.}, }