Re: [Idr] Request comments on draft-chen-idr-bgp-ls-sr-policy-nrp-05
linchangwang <linchangwang.04414@h3c.com> Tue, 05 March 2024 13:09 UTC
Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297A1C14F6B3 for <idr@ietfa.amsl.com>; Tue, 5 Mar 2024 05:09:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRoktByxaTFz for <idr@ietfa.amsl.com>; Tue, 5 Mar 2024 05:09:29 -0800 (PST)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29AC2C14F680 for <idr@ietf.org>; Tue, 5 Mar 2024 05:09:26 -0800 (PST)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 425D9580047589; Tue, 5 Mar 2024 21:09:05 +0800 (GMT-8) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX06-IMDC.srv.huawei-3com.com (unknown [10.62.14.15]) by mail.maildlp.com (Postfix) with ESMTP id 909512004BAA; Tue, 5 Mar 2024 21:10:24 +0800 (CST)
Received: from DAG6EX01-IMDC.srv.huawei-3com.com (10.62.14.10) by DAG6EX06-IMDC.srv.huawei-3com.com (10.62.14.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Tue, 5 Mar 2024 21:09:07 +0800
Received: from DAG6EX01-IMDC.srv.huawei-3com.com ([fe80::1d4d:847c:a7e3:1f10]) by DAG6EX01-IMDC.srv.huawei-3com.com ([fe80::1d4d:847c:a7e3:1f10%20]) with mapi id 15.02.1258.027; Tue, 5 Mar 2024 21:09:07 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: "chen.ran@zte.com.cn" <chen.ran@zte.com.cn>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Request comments on draft-chen-idr-bgp-ls-sr-policy-nrp-05
Thread-Index: Adpu/P/A6feTQ/FaTu6gLfZFBoInlA==
Date: Tue, 05 Mar 2024 13:09:06 +0000
Message-ID: <862ef02234a144ccb7e7fe99c154fe57@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.76.156]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_862ef02234a144ccb7e7fe99c154fe57h3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 425D9580047589
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LxQJhRB8ugjauipSFtIStlOAG9g>
Subject: Re: [Idr] Request comments on draft-chen-idr-bgp-ls-sr-policy-nrp-05
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2024 13:09:32 -0000
Hi Ran I have reviewed this draft and have the following comments: 1. The definition of NRP TLV is incorrect. As defined in RFC9552, the type and length of the TLV should be two bytes, not one byte. It is necessary to redefine the entire NRP TLV. 2. [RFC7752] has been deprecated, please update the reference to RFC9552. 3. Regarding the "Scalability Considerations" section: It differs from the description in draft-ietf-idr-sr-policy-nrp-00. In draft-ietf-idr-sr-policy-nrp-00, it states that as the number of NRP increases, the number of SR Policies would also increase accordingly. Therefore, the number of SR Policies reported on BGP-LS would also increase. It is suggested that the description be consistent with this. Thanks, Changwang 发件人: Idr <idr-bounces@ietf.org> 代表 chen.ran@zte.com.cn 发送时间: 2024年3月5日 9:20 收件人: idr@ietf.org 主题: [Idr] Request comments on draft-chen-idr-bgp-ls-sr-policy-nrp-05 Hi WG, We have updated this draft, the link is https://datatracker.ietf.org/doc/draft-chen-idr-bgp-ls-sr-policy-nrp/, which defines a new TLV which enable the headend to report the configuration and the states of SR policies carrying NRP information by using BGP-LS. In this version, we add the Security Considerations. Any comments are welcomed. Thank you! Best Regards, Ran ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!