<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-lsr-isis-invalid-tlv" target="https://datatracker.ietf.org/doc/html/draft-ietf-lsr-isis-invalid-tlv-03">
   <front>
      <title>Invalid TLV Handling in IS-IS</title>
      <author initials="L." surname="Ginsberg" fullname="Les Ginsberg">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Wells" fullname="Paul Wells">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="T." surname="Li" fullname="Tony Li">
         <organization>Arista Networks</organization>
      </author>
      <author initials="T." surname="Przygienda" fullname="Tony Przygienda">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="S." surname="Hegde" fullname="Shraddha Hegde">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <date month="July" day="26" year="2020" />
      <abstract>
	 <t>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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-lsr-isis-invalid-tlv-03" />
   
</reference>
