Re: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 06 January 2020 04:59 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 942EA1200C3; Sun, 5 Jan 2020 20:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.489
X-Spam-Level:
X-Spam-Status: No, score=-14.489 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 header.b=JYaQcliW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=bbNkgfNV
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 mOtr71U4JkUl; Sun, 5 Jan 2020 20:59:44 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A22E1200B1; Sun, 5 Jan 2020 20:59:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41304; q=dns/txt; s=iport; t=1578286784; x=1579496384; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1SxP3L+T7AFri2v2I/vYKbBSXu6PoJYvXh1XRskACEM=; b=JYaQcliWT3OvEY18p9YzDEDytjJlIEk58f1hhThtlvWIbaNtTVd5gTIS uLhGkJ92X/VyM1vTBu4yXVdfM3Inm5YO54pD7hiM4GFD5aWe5kvhNkgJH 5ly8Rarzlc/lTSVpEV/tLY/hzsGTyhjcNBVgBrJ37+9YTGD3Q+CJZH3TM A=;
IronPort-PHdr: 9a23:x0GJERG0e8y6IQTsVV5ix51GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efHraTcwEd5NfFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C+BQAXvhJe/4UNJK1mHAEBAQEBBwEBEQEEBAEBgXyBJS9QBWxYIAQLKoQJg0YDin+CX5gNglIDUAQJAQEBDAEBGAEKCgIBAYRAAheBUiQ4EwIDDQEBBAEBAQIBBQRthTcMhV4BAQEBAgEBARARChMBASwLAQQHBAIBBgIRBAEBHgMBBgMCAgIlCxQGAwgCBAENBQgTB4MBgXlNAw4gAQIMkQSQZAKBOIhhdYEygn4BAQWBSUGCdRiCDAMGgTaMGRqBQT+BWIJMPoJkAQEDAYFSDysJgloygiyNLoMQhVeJY48lCoI2hzSFO4ZmgmCCRod9hEGLV4NHiwyIU5IGAgQCBAUCDgEBBYFpIoFYcBU7gmxQGA2NElODIIUUhT90gSiLE4JBAQE
X-IronPort-AV: E=Sophos;i="5.69,401,1571702400"; d="scan'208,217";a="417828540"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Jan 2020 04:59:43 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 0064xhnC021117 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 6 Jan 2020 04:59:43 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 5 Jan 2020 22:59:42 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 5 Jan 2020 23:59:41 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sun, 5 Jan 2020 23:59:41 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OUDFzhXMJyp6k5vnzU6cL2vnnynLJUPK1wclJ4Cf+OHC8upK0yexCNELsEdn0EohkmhLOJHEqSwzrRGuHvlhBR4HytjTFfcJOluYHXivg7fw4jx+X1UdnvfUTpSJPyovAjxaeQlE1mzbxApvmlu3HKVQrdJAoYtA+bVPaZUQr9U+nr4zVC1d+5GfZ1QJV6OSf12jzmj5iesttVCOMRchwuFsXqjR6DG1Heey5dzPGOmWIxrXKUSWz3h54R5caHfeXoAjGALDX2ULehzwQw3EGe6VqvRx1WL8M/keXj4BzV7OsmNfXNi0rl9FoIkdsAY7aoXKI6xii9HxfE7LSYrhCA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1SxP3L+T7AFri2v2I/vYKbBSXu6PoJYvXh1XRskACEM=; b=XwqfNsUMItgqXUx+Xrz6zqWf7GaqXioRZ7vSnm0pWgmNYFeGdg+purFo8nOV+ersGc4ZDcXon8re8qw7NtqfUkM6MWogMQ8mTFnaBWMlZUEgT4zSKyJTCjXq/WhbzicX2JAyhmJHngJ9fQ/YciFp8p4vV/yIOi4RD1ZVXCSSOkbv0WAPQ5TKuV2Pb4cYK7xTbu5gH55AgbjeXtkuYIn1itinK/de7i7CKEc/TFkm+sFsn71DQUs1WlDJGdCmaYPVXHBgE6vRaqmPweV0Edy4UXOwT1t9f7kCvUy1cRL6B1gJ7G44+hGhxpjDTNtI+Fgk4uqYxmPJ8BkQpp67l3fXMw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1SxP3L+T7AFri2v2I/vYKbBSXu6PoJYvXh1XRskACEM=; b=bbNkgfNVQ10FwgrvE/ph9r6JwFf1QRm6d7OsHIooCo5wsCVgDAS9b0BUWq0spXPd8zJmw3t7ilbrFeoFg7Ud4AGrDvQrg91DGco2akwbFKnTn/M6z8VHIbxTkHjWMg6au0h/3Y3MMwouqzahqZn0+odSBVhivDD1vNZzkruytB0=
Received: from DM6PR11MB2842.namprd11.prod.outlook.com (20.176.98.140) by DM6PR11MB4250.namprd11.prod.outlook.com (52.132.250.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.11; Mon, 6 Jan 2020 04:59:41 +0000
Received: from DM6PR11MB2842.namprd11.prod.outlook.com ([fe80::f888:dab1:b205:ed9c]) by DM6PR11MB2842.namprd11.prod.outlook.com ([fe80::f888:dab1:b205:ed9c%7]) with mapi id 15.20.2602.015; Mon, 6 Jan 2020 04:59:40 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, 'Christian Hopps' <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
CC: "lsr-ads@ietf.org" <lsr-ads@ietf.org>, 'Antoni Przygienda' <prz@juniper.net>
Thread-Topic: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv
Thread-Index: AQHVwd3rlkDRleqSsEC/0E5m/IjAE6fYZZcggAR6m/CAABFu0IAAB8iQgAAdTMA=
Date: Mon, 06 Jan 2020 04:59:40 +0000
Message-ID: <DM6PR11MB28425BC07AC58E3001A40D9CC13C0@DM6PR11MB2842.namprd11.prod.outlook.com>
References: <4CBA5DF1-E8E2-4370-9602-871FADAB1F9A@chopps.org> <004901d5c1dd$d2fda8b0$78f8fa10$@org.cn> <DM6PR11MB2842EA4E3D169511C7B4CE72C1230@DM6PR11MB2842.namprd11.prod.outlook.com> <00dc01d5c435$9bd0c980$d3725c80$@org.cn> <DM6PR11MB2842BA9A055D7EBB10EA781DC13C0@DM6PR11MB2842.namprd11.prod.outlook.com> <00f701d5c440$34a2e760$9de8b620$@org.cn>
In-Reply-To: <00f701d5c440$34a2e760$9de8b620$@org.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ginsberg@cisco.com;
x-originating-ip: [2001:420:c0c8:1003::51f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: dafd1326-6b97-410b-8c1c-08d792653d0c
x-ms-traffictypediagnostic: DM6PR11MB4250:
x-microsoft-antispam-prvs: <DM6PR11MB4250CEFEB5850E5D44E3D857C13C0@DM6PR11MB4250.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(136003)(39860400002)(346002)(376002)(13464003)(199004)(189003)(52314003)(81156014)(52536014)(55016002)(9686003)(33656002)(81166006)(8936002)(7696005)(6506007)(53546011)(71200400001)(478600001)(54906003)(5660300002)(966005)(76116006)(186003)(316002)(66446008)(86362001)(64756008)(4326008)(2906002)(224303003)(66946007)(66556008)(110136005)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB4250; H:DM6PR11MB2842.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Hiuxn3aocmxQVZR5gwPzNysuKT0XYaS3hZTgfwdKhU18VUlKS0l8R9r9esZW50b/NDppAtT0ot1ZC1VJ1/xNcnDqNK08xS37q5rCa0QA8zzChsG2uLtjJq4iWefy8HG2mcw4FrUzJ2IlgPdnFiFsxICK/QdzX8T+Qlszr+b8ol69aD65wSl1uMaa604kZNUkRPth00u4qZnrOjQ/RzUNe1IyEiEIlIpx6u7fP6ohOa1cZj7PMdXGOq61+fItDujQczjgCIbITzHojDXeyWGkuFy9Gi9ibPEeqvPdEq5jO3LddmaLPTLiKROaf7fIBR8iCK5zKAqf1hBLpcNieSC5j0tRe/QPKDdrtYv9NbQYGo3en5YlnN3hguHJRYxifjirnTO4SSoEtMo2QgLpd37pON7PSLDfMBb9GiUJUI1FNBzwrp2zQYwM6AchT6iSGN3NgbCGlzp9zGLxvKfMY7Gw7cVTGMOuCdf3/EPH8gw+SwVYIjXHjy3H62Nud/n+Awt9KAA/mdPLrNeQjh9FANDrzW7I7vVP35ZblAk6ifDrIhu5EcsmngJZ4qN8bzCkeoud
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR11MB28425BC07AC58E3001A40D9CC13C0DM6PR11MB2842namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: dafd1326-6b97-410b-8c1c-08d792653d0c
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Jan 2020 04:59:40.7970 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: y9SPDorkvj2shx3CfRyn//QMSNUNxK0QJtEGsWH5WyitbMkJgKtqjVr3+cHFAOR41u1NOAeJQnH7R1wV/yoHRQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4250
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.16, xch-aln-006.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/qi7yg9ppKzzDZL3WMx8aCzF3iMw>
Subject: Re: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv
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: Mon, 06 Jan 2020 04:59:47 -0000

Aijun –

When an authentication variant is not supported by all nodes in the area/domain it can’t be used safely. This isn’t a problem we are trying to solve and it was never the reason for writing  the invalid TLV draft.
Please reread the Abstract and Introduction in order to understand the intent of this draft.

Thanx.

   Les


From: Aijun Wang <wangaijun@tsinghua.org.cn>
Sent: Sunday, January 05, 2020 7:20 PM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>; 'Christian Hopps' <chopps@chopps.org>; lsr@ietf.org
Cc: lsr-ads@ietf.org; 'Antoni Przygienda' <prz@juniper.net>
Subject: 答复: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

Hi, Les:

The questions is raised actually by the current description in section 3.2.
It describes the incompatible issues among different RFCs, but no promising solution (maybe there is none), also not emphasizing the consequence for the incompatible deployments (may exist in other document).
Anyway, I knew the answers. Put it into the document may be more helpful for others.

Best Regards.

Aijun Wang
China Telecom

发件人: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
发送时间: 2020年1月6日 10:42
收件人: Aijun Wang; 'Christian Hopps'; lsr@ietf.org<mailto:lsr@ietf.org>
抄送: lsr-ads@ietf.org<mailto:lsr-ads@ietf.org>; 'Antoni Przygienda'
主题: RE: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

Aijun –

Please read Section 3.2 of the draft which discusses these issues.
Thanx.

   Les

From: Aijun Wang <wangaijun@tsinghua.org.cn<mailto:wangaijun@tsinghua.org.cn>>
Sent: Sunday, January 05, 2020 6:04 PM
To: Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>>; 'Christian Hopps' <chopps@chopps.org<mailto:chopps@chopps.org>>; lsr@ietf.org<mailto:lsr@ietf.org>
Cc: lsr-ads@ietf.org<mailto:lsr-ads@ietf.org>; 'Antoni Przygienda' <prz@juniper.net<mailto:prz@juniper.net>>
Subject: 答复: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

Hi, Les:

Since this draft is the main entry for the management of invalid tlv in isis, will it be more useful to include the description that you provide for its completeness?  Knowing the possible consequences may drive the operators to consider more carefully for their updating deployment.

Anyway, I support this draft.

Best Regards.

Aijun Wang
China Telecom

发件人: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
发送时间: 2020年1月3日 13:29
收件人: Aijun Wang; 'Christian Hopps'; lsr@ietf.org<mailto:lsr@ietf.org>
抄送: lsr-ads@ietf.org<mailto:lsr-ads@ietf.org>; 'Antoni Przygienda'
主题: RE: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv


Aijun -



Since advertising some sort of capability would also be unusable until all routers were upgraded to understand the new capability advertisement this does not help. 😊



The consequences of enabling a form of authentication which is not supported by all nodes is an inconsistent LSPDB - which means protocol function is broken.



I would also point out that the incompatibilities are discussed in the original specifications (RFC 5304 and RFC 6232) - both of which have been published for a number of years. The points being made in this regard in this draft aren't new.



   Les



> -----Original Message-----

> From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> On Behalf Of Aijun Wang

> Sent: Thursday, January 02, 2020 6:31 PM

> To: 'Christian Hopps' <chopps@chopps.org<mailto:chopps@chopps.org>>; lsr@ietf.org<mailto:lsr@ietf.org>

> Cc: lsr-ads@ietf.org<mailto:lsr-ads@ietf.org>; 'Antoni Przygienda' <prz@juniper.net<mailto:prz@juniper.net>>

> Subject: [Lsr] 答复: WG Last Call draft-ietf-lsr-isis-invalid-tlv

>

> Is there any method to indicate or negotiate the support of

> ISO10589/RFC5304/RFC6233 because they are not back compatible?

> What will be the consequence when not all of the routers within the IGP

> domain support the same RFC?

> Will it valuable to add more clarification for the above incompatible

> scenario, instead of saying "... ... therefore can only be safely enabled

> when all nodes support the extensions"?

>

>

> Best Regards.

>

> Aijun Wang

> China Telecom

>

> -----邮件原件-----

> 发件人: lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org> [mailto:lsr-bounces@ietf.org] 代表 Christian

> Hopps

> 发送时间: 2020年1月3日 3:07

> 收件人: lsr@ietf.org<mailto:lsr@ietf.org>

> 抄送: lsr-ads@ietf.org<mailto:lsr-ads@ietf.org>; Christian Hopps; Antoni Przygienda

> 主题: [Lsr] WG Last Call draft-ietf-lsr-isis-invalid-tlv

>

> This begins a 2 week WG Last Call, ending after Jan 16th, 2020, for

> draft-ietf-lsr-isis-invalid-tlv.

>

>   https://datatracker.ietf.org/doc/draft-ietf-lsr-isis-invalid-tlv/

>

> Tony P (other authors already responded during the adoption poll), please

> indicate your knowledge of any IPR related to this work to the list as well.

>

> Thanks,

> Chris & Acee.

>

> _______________________________________________

> Lsr mailing list

> Lsr@ietf.org<mailto:Lsr@ietf.org>

> https://www.ietf.org/mailman/listinfo/lsr

>

> _______________________________________________

> Lsr mailing list

> Lsr@ietf.org<mailto:Lsr@ietf.org>

> https://www.ietf.org/mailman/listinfo/lsr