[Lsr] RFC 8918 on Invalid TLV Handling in IS-IS

rfc-editor@rfc-editor.org Thu, 24 September 2020 22:19 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9953A08E5; Thu, 24 Sep 2020 15:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35VSo26LoK-x; Thu, 24 Sep 2020 15:19:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 320ED3A08E3; Thu, 24 Sep 2020 15:19:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 44822F40776; Thu, 24 Sep 2020 15:19:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lsr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200924221916.44822F40776@rfc-editor.org>
Date: Thu, 24 Sep 2020 15:19:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/iB0UWJeXL5I53e4px8dTDbj9qI4>
Subject: [Lsr] RFC 8918 on Invalid TLV Handling in IS-IS
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2020 22:19:28 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8918

        Title:      Invalid TLV Handling in IS-IS 
        Author:     L. Ginsberg,
                    P. Wells,
                    T. Li,
                    T. Przygienda,
                    S. Hegde
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2020
        Mailbox:    ginsberg@cisco.com, 
                    pauwells@cisco.com, 
                    tony.li@tony.li,
                    prz@juniper.net, 
                    shraddha@juniper.net
        Pages:      8
        Updates:    RFC 5305, RFC 6232

        I-D Tag:    draft-ietf-lsr-isis-invalid-tlv-03.txt

        URL:        https://www.rfc-editor.org/info/rfc8918

        DOI:        10.17487/RFC8918

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.

This document is a product of the Link State Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC