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

"Aijun Wang" <wangaijun@tsinghua.org.cn> Mon, 06 January 2020 02:04 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
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 76E2E12002E; Sun, 5 Jan 2020 18:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 WtxUqdrA50SC; Sun, 5 Jan 2020 18:04:28 -0800 (PST)
Received: from m176115.mail.qiye.163.com (m176115.mail.qiye.163.com [59.111.176.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FD19120045; Sun, 5 Jan 2020 18:04:27 -0800 (PST)
Received: from WangajPC (unknown [219.142.69.77]) by m176115.mail.qiye.163.com (Hmail) with ESMTPA id 3F4EF66305A; Mon, 6 Jan 2020 10:04:20 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
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>
References: <4CBA5DF1-E8E2-4370-9602-871FADAB1F9A@chopps.org> <004901d5c1dd$d2fda8b0$78f8fa10$@org.cn> <DM6PR11MB2842EA4E3D169511C7B4CE72C1230@DM6PR11MB2842.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB2842EA4E3D169511C7B4CE72C1230@DM6PR11MB2842.namprd11.prod.outlook.com>
Date: Mon, 06 Jan 2020 10:04:18 +0800
Message-ID: <00dc01d5c435$9bd0c980$d3725c80$@org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DD_01D5C478.A9F40980"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHVwd3rlkDRleqSsEC/0E5m/IjAE6fYZZcggAR6m/A=
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUtXWQgYFAkeWUFZVkpVTU9CS0tKT0xCSk9DQ01ZV1koWU FKTEtLSjdXWS1ZQUlXWQkOFx4IWUFZNTQpNjo3JCkuNz5ZBg++
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6NSI6Kyo5UTgrAyE#NDkLPikc FkkwCzJVSlVKTkxDSUxNSU1OTE1LVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxMWVdZCAFZQUlKQk9NNwY+
X-HM-Tid: 0a6f78988a3e9373kuws3f4ef66305a
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/aOO6rqF1UYPleEYDDnLB1JXoYdI>
Subject: [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 02:04:31 -0000

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
抄送: 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> On Behalf Of Aijun Wang

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

> To: '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

> 

> 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

> 

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

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

> Hopps

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

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

> 抄送:  <mailto:lsr-ads@ietf.org> 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/> 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

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

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

> 

> _______________________________________________

> Lsr mailing list

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

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