Invalid TLV Handling in IS-IS
draft-ginsberg-lsr-isis-invalid-tlv-03

Document Type Replaced Internet-Draft (lsr WG)
Last updated 2019-07-22 (latest revision 2019-04-03)
Replaced by draft-ietf-lsr-isis-invalid-tlv
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-lsr-isis-invalid-tlv
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ginsberg-lsr-isis-invalid-tlv-03.txt

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.

Authors

Les Ginsberg (ginsberg@cisco.com)
Paul Wells (pauwells@cisco.com)
Tony Li (tony.li@tony.li)
Tony Przygienda (prz@juniper.net)
Shraddha Hegde (shraddha@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)