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 00:32 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 A4121C1D8777 for <idr@ietfa.amsl.com>; Tue, 23 Jul 2024 17:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.09
X-Spam-Level: *
X-Spam-Status: No, score=1.09 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_BLOCKED=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=no 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 hNabZNoyQG9W for <idr@ietfa.amsl.com>; Tue, 23 Jul 2024 17:32:08 -0700 (PDT)
Received: from out203-205-221-205.mail.qq.com (out203-205-221-205.mail.qq.com [203.205.221.205]) (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 B6E84C1519AA for <idr@ietf.org>; Tue, 23 Jul 2024 17:32:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1721781119; bh=I6O0RBAvFx8VlGjGYSDfDQFleOrHHFXLIMcHdx/2VEs=; h=Date:From:To:Subject; b=mXiTeS3YuZfwr2EkgJSP7AN+YlVTa232jXEVO3IkwbtogageQp6ceS/2W5+U8jVBM kxb1pFY9Hw/tpxwe1I8b7IWFbnApY7/g2XrTv5rW5J/ku5qaHnX9LQvzSGE+ci0uEi 8PqKaDytKGORY+lcjGfT9GAaoH170Ny5kYYTRYXI=
Received: from LAPTOP-62COFCP0 ([61.144.66.67]) by newxmesmtplogicsvrszb9-1.qq.com (NewEsmtp) with SMTP id 7F9B78C8; Wed, 24 Jul 2024 08:31:57 +0800
X-QQ-mid: xmsmtpt1721781117t1dzz3bhz
Message-ID: <tencent_BE87832CA13698341C3DCD2F823BF6E65609@qq.com>
X-QQ-XMAILINFO: Md1mxnKJDwB6caFw5qSjxR0/9ZIWQKEpNiSg95xYh7UUczfA8mTMqfmupDdi0+ Pp4pXuEeNslZPGZUrwaRROJlUlJO1GuTlj/ATo7Tbmhvfmkel7PQg/BOFutbPrROwbfH6Xu7NIEQ 3pKzCUJ6yrUifq15SH+lsd8BRoXZy2ZfJEIAJ0+9dLl9sz1SXIZc/ALDapRM/hwJJsZ5ps5DasTr 0lsWAKf5baM0/I+XVN5zcYQl7FtWccO6JMy70Ml3E6ySAkMN9TSXvQBL0e9B1xs+kG3rlf/hG7FN pE25dYY9olQH05QHkImXHqHjYbonSLnGkYNRPlxw2teRBpg2dzYLw8rBJLieb7EBErJwVikZ3eYI KMLifOzl1IglyG5mLLfa9Gt5at0C8DW2NgdOeYwk8EEmC7BUFw0ikOxhRW2mKlFUegTfl+1oQMzt Dz92hOdZAw1O07onoPBwnxRZW2w7SUQTGA8yqeitGVm4fKGSMMbvbKsK/s/avQOVSC2eisrVfgq/ 4HEM6Zm0KtKJSMvSoaKLVM+rmQV4JPlsyFf0ou8j+qbNKDu/3KuxJlMSDOROivUnLCSrUxwRPWnK n4yNhZQJ175El+kTPYvdT/WIFP8hVCx6khmap/X/EXrfWqkaqxUFJlALLXXpnTXgT4gzVvNfWMnw pV4ym5kqfHYT4N3rYorXRbL/DVy3rJtSFcPrx+SpH7fX2zTHc5aoxGD6/EVi+ufxmAmnBSpMans5 OrSOFXpEcP+IQQNNSSFXgQ8J6XrE9sSztjqymalJxamXLWTojpSXv8aM3+wfoKcu2uEoXm0WlI4x gAVUKbQPCRUvGcux3Q2GswMRTw96cdRByxrifDitedL8IpjMpg6ovLQscftwlWwUEyjWfaUv9hEV b/MK1kPH9R/8pZqALCRStank9GwAFBvjM5nMGZE87lWxsNrPzsgk+mESONPTYkBbtve5ln9crcjV bGg3teY9d5wVz0OZBfZgEUdkIjuT1FyISGVWsJeKr/VnSr2krmfezYocM7V+cu
X-QQ-XMRINFO: M/715EihBoGSf6IYSX1iLFg=
From: "zhuyq-ietf2024@foxmail.com" <zhuyq-ietf2024@foxmail.com>
To: "shares@ndzh.com" <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
X-Priority: 3
X-GUID: 39D074EC-CFE1-4A49-8A9B-B799D1FC90AA
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.259[cn]
Mime-Version: 1.0
X-OQ-MSGID: <2024072408315116396763@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart002243866138_=----"
X-MailFrom: zhuyq-ietf2024@foxmail.com
X-Mailman-Rule-Hits: nonmember-moderation
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0
Message-ID-Hash: T4PMZAO5SP66N4CLZJTAG7V6VOFY5WKV
X-Message-ID-Hash: T4PMZAO5SP66N4CLZJTAG7V6VOFY5WKV
X-Mailman-Approved-At: Thu, 25 Jul 2024 07:38:44 -0700
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/E_GtvnvLfgshRyOeByRaqBw-3Nw>
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>
Date: Wed, 24 Jul 2024 00:32:12 -0000
X-Original-Date: Wed, 24 Jul 2024 08:31:52 +0800

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.26.15 | Report a Bug | By Email | System Status