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

[[e-mail]]

Hi Yao,

Thank you for your comments and support. Will be updated in the next version.

Best Regards,
Ran

Original


From: 刘尧
To: [e-mail] <[e-mail]>;
Cc: [e-mail] <[e-mail]>;
Date: 2024年07月29日 15:20
Subject: [Idr] Re: draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG adoption call (7/22/2024 to 8/9/2024)

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

Hi,
I support the adoption of this document.

1.  Is the addition of NRP-ID information to SR BGP-LS information valuable to networks?
Yes. 

2.  Does the draft clearly specify the TLV?
1) About the NRP ID field
The suggestion is to add a reference to the NRP ID field definition in draft-ietf-idr-sr-policy-nrp since delivering via BGP SR Policy is one of the origin from which the headend gets the NRP ID of the SR Policy CP from. 
2) The Length is a  2-octet field and the value is 8.

3.  Are there any security concerns about reporting NRP-ID?
No.

4.  Is this document ready to adopt?
Yes.

Regards，
Yao







From: SusanHares <[e-mail]>
To: [e-mail] <[e-mail]>;
Date: 2024年07月23日 09:43
Subject: [Idr] draft-chen-idr-bgp-ls-sr-policy-nrp-09 - WG adoption call (7/22/2024 to 8/9/2024)

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

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