[Idr] Fw: draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG adoption call (7/22/2024 to 8/9/2024)
"zehua.hu@foxmail.com" <zehua.hu@foxmail.com> Wed, 24 July 2024 06:34 UTC
Return-Path: <zehua.hu@foxmail.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 7AAF0C18DBB3 for <idr@ietfa.amsl.com>; Tue, 23 Jul 2024 23:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.162
X-Spam-Level:
X-Spam-Status: No, score=-4.162 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 Q0p8g62WlUhb for <idr@ietfa.amsl.com>; Tue, 23 Jul 2024 23:34:18 -0700 (PDT)
Received: from out203-205-221-192.mail.qq.com (out203-205-221-192.mail.qq.com [203.205.221.192]) (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 2E9B0C18DB9D for <idr@ietf.org>; Tue, 23 Jul 2024 23:34:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1721802849; bh=i8GX1OEYr+lGFekoRqlwrZIfRxT0hX9MYCbxZ5NVclg=; h=Date:From:To:Subject; b=poU5s24MyNVLrhUBJFB7SHrulkV+zDZglJvsAIWFxQRW+KcB98vamKPWHDAAxzdMG pHCz0RaWl1PSy4SYlwphG6OwKs8vZjnxKnepS4E0/C5QcDV9O1cqTnye/H2bCS4MJd rlHmbs97SAyqIGEoMoAy3S1hOZBbDCoQpuU9aBVw=
Received: from DESKTOP-AKI7PBC ([14.26.226.102]) by newxmesmtplogicsvrszc19-0.qq.com (NewEsmtp) with SMTP id 887A34FD; Wed, 24 Jul 2024 14:34:07 +0800
X-QQ-mid: xmsmtpt1721802847t8q5b0nx4
Message-ID: <tencent_FBD29A30B2CCEE531E62FA7CDB44ED2A0906@qq.com>
X-QQ-XMAILINFO: MmuCfgcSBfHx+3f5rfhKpaidMU5nzYEyLKwHePciRrWrmv46tZCzy1LeFmJ49D m7PLVEALkdVp4+pbtnCmJ3YibvtXAqc898hBTFMN7OizIy6lcZmbzE5FYaw2Ba0mNE3Us2O1QTh6 /GwhQTC8fiH21ZfpKOpBqZdjxWGOIF2XAxG/VDZWDByjv+gI7o0TrmNo0D/bjWQPzdvoCxU+qpME mna4EcHWev/nixRaqxpelQaJLwsKcRpsQPxAdA0aO6tEMjjV9qV3FWlFcE2W+37HNzSyqETDw07c vbqpmcUwdTb6aAAgfFUSiF84MmM2GlJ8lhhHtZs1oPOcV9buBNcKasndvIo6N9gbyG4Wst6q7hPG NMN4Em4a2ASanx8Mdie8nxYBtyiBviXWZzEDlN0P3u5HJ0OV+C5EObQFkz7n/LL/tPEMpQ9LgNKj zbNH5GeAHQAYIVTZ/2ctjpIZ7cHMfkZlKe3YxN9ANUQraIp8LobACc6nYPw7sG92t6//f8J4cysK Z0lCl3H9U6CjDIRI9EiPjTZwqzhhFxVHhfDwFuXstzIRU1y/rV85uGegXobzw7kQwTADye679erT cLkaW6nNVyc43gJhKQgHFrYaWef5RzNqqv6avYqkzyZLkzBgcXCC8NZ2DwnSJgH8j+scgXPgfgdV dfAaJLj/AvEPGHChNvQDoR8eyEjkH/kZwmKJleiUuVShLr8XpYcJ4qHWHZAA/HIYNbW8JSLCVEc7 9O7BJ1mV78mfiO1qa1erZfeOyKfrlMHuPefUi81TupnH1mUtjyeHu0cS41GEaeumnZOy+JhcjnWS 50vdZeEKT1eLiTA6Fl8uOwYN2syit7nuAb+ZQ75iO2UjGaxH8wvJny/9Z6kP0c7LvdImZRrMudPm +pQf92ph2VAO/BM+xxYf11EBqPjgt7oZXGzLcoMXmE8rNVO7CH8wNagQSq7c93TJXxtcR/uVn3PK rXymLIMkRHtdqutyJphZ7vkU6Giua2Ry4EUh1R9aY2f/NNyjX8aHVSxQSyOFsibkYECbGRtu+Wf6 RumGgINIKQgg1Ygcz3ckkL11T4e4Y=
X-QQ-XMRINFO: OD9hHCdaPRBwq3WW+NvGbIU=
Date: Wed, 24 Jul 2024 14:34:07 +0800
From: "zehua.hu@foxmail.com" <zehua.hu@foxmail.com>
To: Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
X-Priority: 3
X-GUID: 53160402-16FB-45F3-9261-C709DC2C454F
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.245[cn]
Mime-Version: 1.0
X-OQ-MSGID: <2024072414340643105424@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart686287212387_=----"
Message-ID-Hash: 7IPDLFQ3UK5OIM73N7WOP4C22AHDQU53
X-Message-ID-Hash: 7IPDLFQ3UK5OIM73N7WOP4C22AHDQU53
X-MailFrom: zehua.hu@foxmail.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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Fw: draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG adoption call (7/22/2024 to 8/9/2024)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/CG0y9bCFAlkyAFKTAYI2m5BAGc4>
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 and WG,
I support the adoption of this draft and my replies about the questions are:
1. Yes. It is very useful.
2. Yes. The draft is clear.
3. I don't see any other security concerns.
4. Yes. It is ready to move on.
B.R.
Zehua Hu
China Telecom
From: Susan Hares
Date: 2024-07-23 09:41
To: idr@ietf.org
Subject: [Idr] draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG adoption call (7/22/2024 to 8/9/2024)
This begins a 2+ week WG adoption call (7/22 to 8/9/2024)for
draft-chen-bgp-ls-sr-policy-nrp-09.txt.
(https://datatracker.ietf.org/doc/draft-chen-idr-bgp-ls-sr-policy-nrp/)
The authors should respond to this WG adoption call with an email with the IPR statement.
Document focus:
This document defines a new TLV in BGP-LS to report the NRP-ID
associated with an SR Candidate Policy Path (CP).
Links to Spring: During the 5/20/2024 interim, the following question was raised:
What is the relationship between the information in this draft and the information in draft-ietf-spring-resource-aware-segments?
Ran answered the following:
Due to the resource SID mechanism defined in the draft-ietf-spring-resource-aware-segments
(https://datatracker.ietf.org/doc/draft-ietf-spring-resource-aware-segments/)
the headend node does not have information about the relationship between
Candidate Path (CP) and NRP IDs, so it currently does not consider reporting the
relationship between CP and NRP ID. The current draft is only for the scenario
where data packets carry NRP ID. The NRP ID is used with the normal SR SID as
the resource used will be indicated by the NRP-ID. An SR Policy candidate path(CP)
may be instantiated with a specific NRP on the headend node via a local configuration,
PCEP, or BGP SR Policy signaling. Then the state and attributes of the NRP associated
with the candidate path of SR policy can be distributed to the controller.
In your discussion, please consider:
Is the addition of NRP-ID information to SR BGP-LS information valuable to networks?
Does the draft clearly specify the TLV?
Are there any security concerns about reporting NRP-ID?
Is this document ready to adopt?
Cheerily, Sue
- [Idr] 答复: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … zhao.detao
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … 岳胜男
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … Adrian Farrel
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … Susan Hares
- [Idr] draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG… Susan Hares
- [Idr] Fw: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … zehua.hu@foxmail.com
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … Fan Zhang
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … zhuyq-ietf2024@foxmail.com
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … linchangwang
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … Dongjie (Jimmy)
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … liu.yao71
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … zhuyq-ietf2024@foxmail.com
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … chen.ran
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … Gyan Mishra
- [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 … Susan Hares
- [Idr] Re: [Teas] Re: draft-chen-idr-bgp-ls-sr-pol… chen.ran