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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Sun, 02 December 2018 17:54 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 103971241F6 for <lsr@ietfa.amsl.com>; Sun, 2 Dec 2018 09:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.959
X-Spam-Level:
X-Spam-Status: No, score=-15.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, 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 Ii8U8zou_bph for <lsr@ietfa.amsl.com>; Sun, 2 Dec 2018 09:54:14 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC1841200B3 for <lsr@ietf.org>; Sun, 2 Dec 2018 09:54:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2964; q=dns/txt; s=iport; t=1543773254; x=1544982854; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=jIDBd/s4ZjiCdj6uGFN4DuT4zgrDY/nErWWU+xe7TNQ=; b=NFoxPDXUHbxhazH1LPSBBUG75e6kuS9ECACDBspKOLK3Wl+h/KS5JfhN cu6imSH4i6pC8E63ry8UZJT4XozYUpyNLYvhijoJLMyU39bhxrf0DhL+h DeWGtgb5aR+J8rDd1EWUqHp4ulPdemx+uoaBNptYVea5GNWbWC0rFFRrz 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAA4GwRc/5RdJa1iGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmgQInCoNviBiMCIINg0WUA4F6CwEBJYRHAheDHSI0CQ0BAwEBAgEBAm0cAQuFPAEBAQEDIxFDDgQCAQgRBAEBAwImAgICMBUGAQEFAwIEEwiDGoIBD6F8gS+EMQIOQIUcgQuLEReBQD+BEIMTgx4BAQIBARaBbYJeglcCjy6REgkChn6DMocCIIFbTYREijqJBIRlil0CERSBJx84gVVwFRqDDQmJRYFOhT9BMQGNDIEfAQE
X-IronPort-AV: E=Sophos;i="5.56,307,1539648000"; d="scan'208";a="207768835"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Dec 2018 17:54:12 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id wB2HsCV8016554 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <lsr@ietf.org>; Sun, 2 Dec 2018 17:54:12 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 2 Dec 2018 11:54:11 -0600
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; Sun, 2 Dec 2018 11:54:12 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-01.txt
Thread-Index: AQHUimDceFQKhDAVhEKytBGy7PR8zaVrurMA
Date: Sun, 02 Dec 2018 17:54:11 +0000
Message-ID: <9026873aaee74bdfa40f75e3fbf7bf8f@XCH-ALN-001.cisco.com>
References: <154377016944.7337.2693246421316486750.idtracker@ietfa.amsl.com>
In-Reply-To: <154377016944.7337.2693246421316486750.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.67.88]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/MQxT-LGR9LsFe-BgAtHLamR70Lc>
Subject: [Lsr] FW: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-01.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: Sun, 02 Dec 2018 17:54:17 -0000

FYI -

This new version includes some new co-authors, adds some clarifying text, and corrects an error found in RFC 6232.

   Les


-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: Sunday, December 02, 2018 9:03 AM
To: Shraddha Hegde <shraddha@juniper.net>; Tony Przygienda <prz@juniper.net>; Paul Wells (pauwells) <pauwells@cisco.com>; Tony Li <tony.li@tony.li>; Les Ginsberg (ginsberg) <ginsberg@cisco.com>
Subject: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-01.txt


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

Name:		draft-ginsberg-lsr-isis-invalid-tlv
Revision:	01
Title:		Invalid TLV Handling in IS-IS
Document date:	2018-12-02
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/internet-drafts/draft-ginsberg-lsr-isis-invalid-tlv-01.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-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ginsberg-lsr-isis-invalid-tlv
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ginsberg-lsr-isis-invalid-tlv-01

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, RFC6232, 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