Invalid TLV Handling in IS-IS
draft-ginsberg-lsr-isis-invalid-tlv-03
| Document | Type |
Replaced Internet-Draft
(lsr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Les Ginsberg , Paul Wells , Tony Li , Tony Przygienda , Shraddha Hegde | ||
| Last updated | 2019-07-22 (Latest revision 2019-04-03) | ||
| Replaced by | RFC 8918 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-lsr-isis-invalid-tlv | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Paul Wells
Tony Li
Tony Przygienda
Shraddha Hegde
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)