IETF Logo Mail Archive

[Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG adoption call (7/22/2024 to 8/9/2024)

"zhuyq-ietf2024@foxmail.com" <zhuyq-ietf2024@foxmail.com> Wed, 24 July 2024 05:58 UTC

Return-Path: <zhuyq-ietf2024@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 A28DAC1840F6 for <idr@ietfa.amsl.com>; Tue, 23 Jul 2024 22:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.912
X-Spam-Level:
X-Spam-Status: No, score=-3.912 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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_BLOCKED=0.001, 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 Zud4v2GAk5u9 for <idr@ietfa.amsl.com>; Tue, 23 Jul 2024 22:58:29 -0700 (PDT)
Received: from out203-205-221-231.mail.qq.com (out203-205-221-231.mail.qq.com [203.205.221.231]) (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 CE743C1840EF for <idr@ietf.org>; Tue, 23 Jul 2024 22:58:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1721800699; bh=OT0oXhR19gED4hZplHv3mMJ4Cpw7+94XKwIRMqkcb7I=; h=Date:From:To:Subject:References; b=KyHyTL/5r2uxVDjti2Vb/CJMpSUhMoDp6P8Nxi1iA4qBqaVZYhdG0/tYWxUAS1xiz 2d3KcTU54wfNHlEw13HWxTy7RmKuuBYBWy8hjbQUGMK0kCnc3azuGH3gfPT6HDN0AF JUaEwEysirMUI9AQ/0xa+n9gQN0qb491nJKyGbIY=
Received: from LAPTOP-62COFCP0 ([61.144.66.67]) by newxmesmtplogicsvrszb9-0.qq.com (NewEsmtp) with SMTP id E9220405; Wed, 24 Jul 2024 13:58:18 +0800
X-QQ-mid: xmsmtpt1721800698tjxawy300
Message-ID: <tencent_B30E1A439E1B17DA1D2073CBC3EB96621B08@qq.com>
X-QQ-XMAILINFO: OLnGMPzD2sDVI8/4FCmAO2Kyc+Goraz9prFyyyLcPQgzYAbmXlNj5VLxDKjKOk FQeIll9zWQz9F+eu/DiK691kaABU3MzbYUzo5PxWaebenBwcT/jnXWIMfyra1noSg75cpxjy9tXW Tng1QYoXt/TBB15Z3v6ilQAmRCcxcJ5Eqm8BNl9tUlNY9s3Z4JxG30JGd4BhDKj6naJLqdyr27+w 7boy5Ef3VAswkMbroEZ6ghQkw4EUxbo+X0/BxSmAzgiYyanqBU4cxkoIvxWJ9cRrXS31Bkj2O3ba sHQchjdFozXmG8Rn4r5xSjEehvVE/58r1RBXmVRbVVvxdKJ+fLI7ENZqAI1EBxKF/js0iLZTIUEg 43iQMG14HQVCQWs1qtbXIEurkK21q+uUjEHmnfrVpcoQWz2V/V/h8MIPDo1FP43XK3RfPtHeiPPw y7Y0KbkBU45aBAYrlzDz2t7Ur1ha0PZDTmTRKDNWPE/fK0sgtg7NVpxGDAARsNKmPG9HgAXyu8/J Mb2v2j3IrZTIjAr5bqrTXhGtsKVljep3BSBwywwdU7lXHWUmreejSCjx02WpZyx/707Rm75PdtY7 pBx5zrYajFijPM5fgVe9jCKqUIqoMt8nzOCpSH4maJr+yQ73e5FgsULTSWjFlxR7acWwoVGJsnHF LRoJLQ1yjF/XwbeeQ/hE4+lOIzaL3L8nDEJ3Inzgd+sYG4rfr+TB1HUsnaaijlL4QFkBsDTdSAwr o9BXnm+zf6ugsTd7d3I15EyWgZKH0RIC9C+/5CcBbsRnK8+BIC0GpHNAe1PO6aG5+/riA6ZfYyVv ZhACFF8nvnD8LpyS2f1/Yup15DUqQT0Gwt9LG4NaBxy/JMfYKLahsYT1YSfq3ZQPCp5YdbrY+q4D zH8oS0clBg03kIWjy4u5ud0ggrZZXftNVIg3i25RrxcsXkHWG0cO9C+7vUdF7msbC0Cs1/q5sDQ/ s1yKQ1Z0JTJKYDZsr9nmh4LOdz7xKCvC9fbwst/9wtEeqDGL/KUQ2UyIq4bYU+cPFdnh6y7Mwjdr 5/dChHUvnH3rLvzBXWDsCnyY4yBXE0hp71j5t14Q==
X-QQ-XMRINFO: OWPUhxQsoeAVDbp3OJHYyFg=
Date: Wed, 24 Jul 2024 13:58:17 +0800
From: "zhuyq-ietf2024@foxmail.com" <zhuyq-ietf2024@foxmail.com>
To: shares <shares@ndzh.com>, idr <idr@ietf.org>
References: <2024072408315116396763@foxmail.com>
X-Priority: 3
X-GUID: 0D0A94B4-B372-42DD-9E87-5639825413C1
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.259[cn]
Mime-Version: 1.0
X-OQ-MSGID: <2024072413581738530212@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart175343127761_=----"
Message-ID-Hash: TRY3CZ5QHLF6AVTON3MXH65BGEUSAZA4
X-Message-ID-Hash: TRY3CZ5QHLF6AVTON3MXH65BGEUSAZA4
X-MailFrom: zhuyq-ietf2024@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] Re: 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/ZKYWziDo6yCx4bdPehUusm3wqjc>
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 as a co-author.  Pls. see inline. Thanks. 
B.R.
Yongqing Zhu
China Telecom



zhuyq-ietf2024@foxmail.com

Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org
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? // Yes. The NRP-ID information is  used to synchronize the association information between the SR Policy CP and the NRP-ID.
Does the draft clearly specify the TLV? //Yes. I think so.
Are there any security concerns about reporting NRP-ID?//AFAIK, there' no  other security concerns.
Is this document ready to adopt?// Yes. It's ready.
 
Cheerily, Sue

v2.35.0 | Report a Bug | By Email | System Status