{"draft":"draft-ietf-lsr-isis-invalid-tlv-03","doc_id":"RFC8918","title":"Invalid TLV Handling in IS-IS","authors":["L. Ginsberg","P. Wells","T. Li","T. Przygienda","S. Hegde"],"format":["HTML","TEXT","PDF","XML"],"page_count":"8","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Link State Routing","abstract":"The key to the extensibility of the Intermediate System to\r\nIntermediate System (IS-IS) protocol has been the handling of\r\nunsupported and\/or invalid Type-Length-Value (TLV) tuples. Although\r\nthere are explicit statements in existing specifications, deployment\r\nexperience has shown that there are inconsistencies in the behavior\r\nwhen a TLV that is disallowed in a particular Protocol Data Unit\r\n(PDU) is received.\r\n\r\nThis document discusses such cases and makes the correct behavior\r\nexplicit in order to ensure that interoperability is maximized.\r\n\r\nThis document updates RFCs 5305 and 6232.","pub_date":"September 2020","keywords":["TLV","IS-IS"],"obsoletes":[],"obsoleted_by":[],"updates":["RFC5305","RFC6232"],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC8918","errata_url":null}