[Lsr] FW: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-00.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 19 October 2018 19:22 UTC

Return-Path: <ginsberg@cisco.com>
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 062E313120E; Fri, 19 Oct 2018 12:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 RaLZSWE4p4ck; Fri, 19 Oct 2018 12:22:20 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D70E131240; Fri, 19 Oct 2018 12:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3022; q=dns/txt; s=iport; t=1539976930; x=1541186530; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=40mr7n4kI00EkKBSY0Vay0wZ2NuzK/W92I+9QCpywu4=; b=KVWa8aeelo/uhkSU/oxao1WDRCtod7qm/u8j3ZArTlZT8Li8g5ptjolV IuGSMUYogffIenbrIbGQggKbYcGGpriEBeuC5vw9V+PkmELt7SBC/m+3Z tL9lHxnrlqby2WO875rQE97Da5m06ihYWERMcSDMFxxHczXchxbUajC2Y c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AeAACfLcpb/5JdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUgMBAQEBAQsBggRmfygKg2uUMYINgz+TUIF6CwEBJYR?= =?us-ascii?q?HAheEcSE1DA0BAwEBAgEBAm0cAQuFOQEBAQQjEUMCDAQCAQgRBAEBAwImAgI?= =?us-ascii?q?CMBUGAQEFAwIEDgUIgxqCAQ+nJ4EuhDACDECFGIELikQXgUE/gRCDE4MbAQE?= =?us-ascii?q?CAQGBdA+CXYJXAo5HhXuJfwkChlyDHIZqH4FPTIQniWeMVIlXAhEUgSYeATa?= =?us-ascii?q?BVXAVGoMNCYsQhT5vAYp2gR8BAQ?=
X-IronPort-AV: E=Sophos;i="5.54,401,1534809600"; d="scan'208";a="188221128"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2018 19:22:09 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id w9JJM9JG016812 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Oct 2018 19:22:09 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 19 Oct 2018 14:22:08 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1395.000; Fri, 19 Oct 2018 14:22:08 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "lsr@ietf.org" <lsr@ietf.org>
CC: "draft-ginsberg-lsr-isis-invalid-tlv@ietf.org" <draft-ginsberg-lsr-isis-invalid-tlv@ietf.org>
Thread-Topic: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-00.txt
Thread-Index: AQHUZ9vx9BWaZA3ksECZWouSwadLQ6Um8NSA
Date: Fri, 19 Oct 2018 19:22:08 +0000
Message-ID: <e2be977ac6944cf8a4ec9a55252cd538@XCH-ALN-001.cisco.com>
References: <153997473895.6517.13956388612295275485.idtracker@ietfa.amsl.com>
In-Reply-To: <153997473895.6517.13956388612295275485.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.113.215]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/mXonR9s_M5en0gmcXej5_hkhpA8>
Subject: [Lsr] FW: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-00.txt
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: Fri, 19 Oct 2018 19:22:28 -0000

Folks -

This new draft discusses IS-IS protocol behaviors related to handling TLVs that are either:

  o Not recognized/supported by an implementation
  o Present in a PDU where they are disallowed
  o The TLV encoding is invalid in some ways

Inconsistent handling of these cases has been known to cause interoperability issues.

Comments are most welcome.

   Les


-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org>; 
Sent: Friday, October 19, 2018 11:46 AM
To: Paul Wells (pauwells) <pauwells@cisco.com>;; Les Ginsberg (ginsberg) <ginsberg@cisco.com>;
Subject: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-00.txt


A new version of I-D, draft-ginsberg-lsr-isis-invalid-tlv-00.txt
has been successfully submitted by Les Ginsberg and posted to the IETF repository.

Name:		draft-ginsberg-lsr-isis-invalid-tlv
Revision:	00
Title:		Invalid TLV Handling in IS-IS
Document date:	2018-10-19
Group:		Individual Submission
Pages:		7
URL:            https://www.ietf.org/internet-drafts/draft-ginsberg-lsr-isis-invalid-tlv-00.txt
Status:         https://datatracker.ietf.org/doc/draft-ginsberg-lsr-isis-invalid-tlv/
Htmlized:       https://tools.ietf.org/html/draft-ginsberg-lsr-isis-invalid-tlv-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ginsberg-lsr-isis-invalid-tlv


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, in some cases the expected
   behavior is "well known" but not explicitly stated.

   This document discusses the "well known behaviors" and makes them
   explicit in order to insure that interoperability is maximized.

   This document when approved updates RFC3563, RFC5305, and RFC6233.


                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat