IETF Logo Mail Archive

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

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 19 October 2018 19:43 UTC

Return-Path: <jefftant.ietf@gmail.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 BBA97130DFB; Fri, 19 Oct 2018 12:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 F5htMmwMoAov; Fri, 19 Oct 2018 12:43:38 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9099A130F88; Fri, 19 Oct 2018 12:43:32 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id p24-v6so16915924pff.10; Fri, 19 Oct 2018 12:43:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=BQ4ULZNx0DZuZc/jA1hCVMiIJYNOTbid0muLTqmfskU=; b=i024eZ3ffQHeDsh/o9mirtH25KBBw2YzCvmanQ/Tg6U9IVK3qYepAK7ZaFVj2j4OQ6 IQdKrwjCDwpyzVYKLkj8UO0da201UrPS/kfoBHpUeyGtvfi1TArV+g9YV6R74spkkBqk hyAvSkhhCYbwqDdYIdlP++8vRb1eZ9r1SeJbdjodQJYoo1/p8a59Pp2DHDbUVLspaj72 2mrFfPoYhbs1irvysCke12MgPOGekHH3DIAt3bSqJ4Aw1RxGibXzjEkq7nTgsufJ/LNM JAIm2DFqu8hQe2xyL1f9cfJkMKBFtZqmTEk4lODfzmgu/oJr69nJ/9It3D63/6Z+J6jK DbjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=BQ4ULZNx0DZuZc/jA1hCVMiIJYNOTbid0muLTqmfskU=; b=SqlyTzfo3oVIvMtrCGVVUw++X50ExKxJ9VFuYCINU5rgC9/U5qvgYDjPnslp73V6vJ 2F04oiXa2Or+P89DXcagWQWtBErwfcPqLoHlPXH3teSdtXHzKylXMv9lztnSdDhDIKdH kh7v0/jEwXCJUM6ewWT6C7kTuVob9FJ8sGdu4ETXtWBRQKwo3K06+PDd6yBVVqr+3BSm 1N7XyHlJBvint2q/dDUCR7Z1wfuq28icpFpIqWVf08xuemvz3obFJIDRCbGouTsWunaS xTgWZ7LggB8+AJG+loNGUKHjX/Dd8rfUfRuit/Iv5H1jVIXAdLQn58etDHbsZDEXJQmy BC3A==
X-Gm-Message-State: ABuFfojawKDjqTwZZ+/NUmU5lPnfI6ehxN4MOX89pQjTJPaIImw+2+bH Zjx29h/pYGNUzmJR01/v/jdeqInZ
X-Google-Smtp-Source: ACcGV633cuSePU/7XN4cfxzf8BpUy0YXq99F4J4GaNkfse4+rPdUS0L3Xdb1/DdwogEi5HNSzclOeQ==
X-Received: by 2002:a63:ca0c:: with SMTP id n12-v6mr33852821pgi.109.1539978211679; Fri, 19 Oct 2018 12:43:31 -0700 (PDT)
Received: from [10.5.5.194] ([12.12.156.34]) by smtp.gmail.com with ESMTPSA id o2-v6sm24785036pgp.82.2018.10.19.12.43.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Oct 2018 12:43:30 -0700 (PDT)
Date: Fri, 19 Oct 2018 12:43:24 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "lsr@ietf.org" <lsr@ietf.org>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Cc: "draft-ginsberg-lsr-isis-invalid-tlv@ietf.org" <draft-ginsberg-lsr-isis-invalid-tlv@ietf.org>
Message-ID: <645b4d8f-ef54-4a0e-87e4-b848711a49b8@Spark>
In-Reply-To: <e2be977ac6944cf8a4ec9a55252cd538@XCH-ALN-001.cisco.com>
References: <153997473895.6517.13956388612295275485.idtracker@ietfa.amsl.com> <e2be977ac6944cf8a4ec9a55252cd538@XCH-ALN-001.cisco.com>
X-Readdle-Message-ID: 645b4d8f-ef54-4a0e-87e4-b848711a49b8@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5bca33e1_737b8ddc_12a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/KSISIeKFJqFi20GD5S6haDIThNI>
Subject: Re: [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:43:41 -0000

Great stuff, long time due!

Cheers,
Jeff
On Oct 19, 2018, 12:23 PM -0700, Les Ginsberg (ginsberg) <ginsberg@cisco.com>, wrote:
> 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
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr

v2.23.0 | Report a Bug | By Email