[Idr] Re: draft-ietf-idr-bgp-ls-sr-policy-nrp-01

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 05 September 2024 01:12 UTC

Return-Path: <jie.dong@huawei.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 9EDF9C18DBBB for <idr@ietfa.amsl.com>; Wed, 4 Sep 2024 18:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 TlRjLYPDuDgE for <idr@ietfa.amsl.com>; Wed, 4 Sep 2024 18:12:51 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5EFFC18DB83 for <idr@ietf.org>; Wed, 4 Sep 2024 18:12:50 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Wzh8c56Bzz6J7y8 for <idr@ietf.org>; Thu, 5 Sep 2024 09:09:20 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (unknown [7.191.160.241]) by mail.maildlp.com (Postfix) with ESMTPS id F1E4B1400D9 for <idr@ietf.org>; Thu, 5 Sep 2024 09:12:47 +0800 (CST)
Received: from kwepemg100001.china.huawei.com (7.202.181.18) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 5 Sep 2024 02:12:46 +0100
Received: from kwepemf100006.china.huawei.com (7.202.181.220) by kwepemg100001.china.huawei.com (7.202.181.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 5 Sep 2024 09:12:45 +0800
Received: from kwepemf100006.china.huawei.com ([7.202.181.220]) by kwepemf100006.china.huawei.com ([7.202.181.220]) with mapi id 15.02.1544.011; Thu, 5 Sep 2024 09:12:45 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-ietf-idr-bgp-ls-sr-policy-nrp-01
Thread-Index: Adr8lEjpNbYtZwp5RxScdRQk6yPtcgBOiNSgAEDdBpAAF3IwoA==
Date: Thu, 05 Sep 2024 01:12:45 +0000
Message-ID: <828be78fa775490eae72ba0538e35413@huawei.com>
References: <CO1PR08MB661109925C71EDF82B77C0F2B3912@CO1PR08MB6611.namprd08.prod.outlook.com> <44cbbfb2f1484fad975aeccbf8088864@huawei.com> <CO1PR08MB661190E278C2635D647B188EB39C2@CO1PR08MB6611.namprd08.prod.outlook.com>
In-Reply-To: <CO1PR08MB661190E278C2635D647B188EB39C2@CO1PR08MB6611.namprd08.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.66]
Content-Type: multipart/alternative; boundary="_000_828be78fa775490eae72ba0538e35413huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: 6CJI2PR7EM3DH7FNZP4AR7FC6JEKL673
X-Message-ID-Hash: 6CJI2PR7EM3DH7FNZP4AR7FC6JEKL673
X-MailFrom: jie.dong@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "庞冉(联通集团中国联通研究院-本 部)" <pangran@chinaunicom.cn>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: draft-ietf-idr-bgp-ls-sr-policy-nrp-01
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/yUiFWFx0OEjxDTAwEF_2mrJKNwY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi Sue,

I guess you mean draft-ietf-idr-sr-policy-nrp?

Yes we can give an update of this draft at the interim.

Best regards,
Jie

From: Susan Hares [mailto:shares@ndzh.com]
Sent: Wednesday, September 4, 2024 10:06 PM
To: Dongjie (Jimmy) <jie.dong@huawei.com>; idr@ietf.org
Cc: Huzhibo <huzhibo@huawei.com>; 庞冉(联通集团中国联通研究院-本部) <pangran@chinaunicom.cn>
Subject: RE: draft-ietf-idr-bgp-ls-sr-policy-nrp-01

Jie:

Would you present an update on draft-ietf-idr-bgp-ls-sr-policy-nrp  at the IDR Interim meeting on 9/9/2024?

This will help people prepare for WG LC for this draft.

Cheerily, Sue Hares



From: Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>
Sent: Tuesday, September 3, 2024 3:22 AM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; idr@ietf.org<mailto:idr@ietf.org>
Cc: Huzhibo <huzhibo@huawei.com<mailto:huzhibo@huawei.com>>; 庞冉(联通集团中国联通研究院-本部) <pangran@chinaunicom.cn<mailto:pangran@chinaunicom.cn>>
Subject: RE: draft-ietf-idr-bgp-ls-sr-policy-nrp-01


Hi Sue,

Thanks a lot for the review. Please see replies inline:

From: Susan Hares [mailto:shares@ndzh.com<mailto:shares@ndzh.com>]
Sent: Monday, September 2, 2024 1:31 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Cc: Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; Huzhibo <huzhibo@huawei.com<mailto:huzhibo@huawei.com>>; 庞冉(联通集团中国联通研究院-本部) <pangran@chinaunicom.cn<mailto:pangran@chinaunicom.cn>>
Subject: draft-ietf-idr-bgp-ls-sr-policy-nrp-01

Jie, Zhibo, and Ran:

Thank you for your hard work on draft-ietf-idr-sr-policy-nrp-01.

Would you let me know:


  1.  Do you plan technical additions to this draft?

[Jie] No. The major content of this document is stable.


  1.  Do you need an early allocations from the Tunnel Encapsulation sub-TLV registry?

[Jie ] The sub-TLV code point requested in this document has been assigned by IANA.


  1.  Are there two implementations of this draft?

[Jie] We are aware of multiple implementations. Will put them into an implementation report.


  1.  Do you wish to go to WG LC in the next 3 months (Sept-November)?

[Jie] Yes, after a new revision to address the editorial changes, we hope to move this document to WG LC in next 3 months. Thanks.

Best regards,
Jie

Cheerily, Sue Hares


Shepherd report for draft-ietf-idr-sr-policy-nrp-01

Status: WG draft, recently adopted (6/2024 upload)
Prior to WG LC: needs 2 implementations.
Shepherd Summary: Editorial changes needed
allocation status: Need allocations

Editorial changes:
1. Section 2, NRP-ID

old text: /NRP ID is planned by network operator/
new text: /NRP ID is allocated and administered by network operator./

2. Section 3, Scalability, last sentence, need clarity on what "this" refers to

old text: On the other hand this will only cause an increase
          in the status reporting information of the head node,
             the impacts to the BGP control plane are considered acceptable./

Suggested
new text:/ On the other hand, the increase in state when NRP increases will
           cause an increase in the state reported on the head node.
           Due to this fact, the impact to the BGP control plan is considered
           acceptable./

Issue-2: Security Section, Please enhance the security section
Security section should refer to security section in
[draft-ietf-idr-sr-policy-safi]. It is important to reference:

a) operates in trusted environment (as draft-ietf-idr-sr-policy-safi)
b) Operators must a NRP-ID for one or more SR Policy is a critical piece of
information about critical infrastructure.  Care must be take
with distribution of information.

Editorial changes: None