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

Document Type Active Internet-Draft (individual)
Last updated 2019-04-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
LSR Working Group                                            L. Ginsberg
Internet-Draft                                                  P. Wells
Updates: 3563 5305 6232 6233 (if                           Cisco Systems
         approved)                                                 T. Li
Intended status: Standards Track                         Arista Networks
Expires: October 5, 2019                                   T. Przygienda
                                                                S. Hegde
                                                  Juniper Networks, Inc.
                                                           April 3, 2019

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

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.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

Ginsberg, et al.         Expires October 5, 2019                [Page 1]
Internet-Draft     draft-ginsberg-lsr-isis-invalid-tlv        April 2019

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 5, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  TLV Codepoints Registry . . . . . . . . . . . . . . . . . . .   3
   3.  TLV Acceptance in PDUs  . . . . . . . . . . . . . . . . . . .   4
     3.1.  Handling of Disallowed TLVs in Received PDUs other than
           LSP Purges  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Special Handling of  Disallowed TLVs in Received LSP
           Purges  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Applicability to sub-TLVs . . . . . . . . . . . . . . . .   5
     3.4.  Correction to POI TLV Registry Entry  . . . . . . . . . .   5
   4.  TLV Validation and LSP Acceptance . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The Intermediate System to Intermediate System (IS-IS) protocol
   utilizes Type/Length/Value (TLV) encoding for all content in the body
   of Protocol Data Units (PDUs).  New extensions to the protocol are
   supported by defining new TLVs.  In order to allow protocol

Ginsberg, et al.         Expires October 5, 2019                [Page 2]
Internet-Draft     draft-ginsberg-lsr-isis-invalid-tlv        April 2019
Show full document text