[Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-08 - updates needed prior to WG adoption call - Still need version -09

[[e-mail]]

Hi Sue,
Thanks!

Best Regards,
Ran





Original


From: SusanHares <[e-mail]>
To: 陈然00080434;
Cc: [e-mail] <[e-mail]>;
Date: 2024年07月23日 05:52
Subject: RE: [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-08 - updates needed prior to WG adoption call - Still need version -09




Ran:
 
Thank you for the submission.  I will start the WG adoption call by 8pm PT today. 
 
Sue 
 


From: [e-mail] <[e-mail]> 
 Sent: Sunday, July 21, 2024 10:05 PM
 To: Susan Hares <[e-mail]>
 Cc: [e-mail]
 Subject: Re: [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-08 - updates needed prior to WG adoption call - Still need version -09



 





 


Hi Sue and WG,
 
We just submitted version 09 and resolved all comments. The link is: https://datatracker.ietf.org/doc/draft-chen-idr-bgp-ls-sr-policy-nrp/. Thanks.
 
Best Regards,
Ran

Original

From: SusanHares <[e-mail]>



To: [e-mail] <[e-mail]>;



Date: 2024年07月12日 17:58



Subject: [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-08 - updates needed prior to WG adoption call - Still need version -09




_______________________________________________
 Idr mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]

Chen: 
 
Thank you for the updates in draft-chen-idr-bgp-ls-sr-policy-nrp-08 and your email:
 
https://mailarchive.ietf.org/arch/msg/idr/LI_J2mPQhnaF1VS_TSGXA3V2qDo/
 
I’ve responded to your comments below. 
 
 
You also responded to Adrian also reviewed the document at: 
https://mailarchive.ietf.org/arch/msg/idr/SoQMt47xFHvJzO3CnJkfVaXolu4/
https://mailarchive.ietf.org/arch/msg/idr/qWLt2z9KI-9sPfdrCm-UKp0m7sU/
 
 
If you submit -09 by Monday of IETF week, I’ll start a WG adoption call for this draft. 
 
Cheerily, Sue  
 
 
================
Short form of what needs to be changed: 
 
As a reminder, these are the things:
Please provide the updates 
 
The following things do not seem to be resolved in draft-chen-idr-bgp-ls-sr-policy-nrp-08.txt: 
 
: What is the relationship between the information in this draft and the information in draft-ietf-spring-resource-aware-segments?
 
Ran-1:  Due to the resource SID mechanism defined in the draft-ietf-spring-resource-aware-segments, the headend node does not have information about the relationship between 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.
 
Sue-2 (response): Thank you for this feedback. Here’s a few suggestion for -09. 
 
Please indicate where the IPv6 packet carries the NRP-ID in next hop header. Expanding he following paragraph in section 1 might be helpful:
 
   [I-D.ietf-teas-nrp-scalability] introduces a scalable data plane    approach to support Network Slice is to carry a dedicated NRP ID in    the data packet to identify the NRP the packet belongs to, so that    the packet can be processed and forwarded using the subset of network    resources allocated to the NRP. 
 
 
Also refer to draft that specifies this. 
 
On CP, please expand CP the first time it is used in section 2, paragraph 3.
 
Old text:/
   This TLV is optional and only one this TLV is advertised for a given
   CP. / New text:/ 
   This TLV is optional and only one this TLV is advertised for a given
   Candidate Path (CP). / 
 
 
2. Discussion of how what state the NRP-ID specifically links to and helps align.
 
Ran-1:  A Network Resource Partition (NRP) is a collection of allocated network resources in a network. The SR policy the forwarding path of the data packet, and the NRP ID indicates the reserved resources along the path specified by the SR policy. By associating the SR policy with a specific NRP, the forwarding path and resource reservation along the path are ensured.  BGP-LS reports the association between CP and NRP-ID, which is used to synchronize the association information between CP and NRP-ID.
 
Sue-2: Review your text in sections 1 and 2. Can you include this wonderful explanation in either section.  
 
R    Discussion of whether this draft applies to SR-MPLS
Ran: Yes, this draft applies to SR-MPLS and will be clarified in the draft.
Sue-2: Thanks for including this in section -09 
 
Cheerily, Sue Hares