Hi Aijun, 

Thanks for your review and support. 

Regarding your question about the NRP identification, the 32-bit NRP ID in this 
document is an identifier in the control plane, while the resource-aware SR 
SIDs or the NRP Selector ID are carried in the data packets. There is mapping 
between them, while they don't have to be exact the same in size and encoding. 

Hope this addresses your question.

Best regards,
Jie

> -----Original Message-----
> From: Aijun Wang <[email protected]>
> Sent: Thursday, September 25, 2025 10:49 AM
> To: [email protected]; [email protected]
> Subject: [Pce] Re: Adoption Poll for draft-dong-pce-pcep-nrp
> 
> Hi, All:
> 
> I review this document and support its adoption.
> 
> One question for the contents of the document, in the introduction part this
> document, it says there are several methods to identify on NRP, for example,
> the SR/SRv6 SID, or VPN-VTN-ID etc.
> So, can the 32 bit NRP ID encompass all these situations? For example, the
> SRv6 SID is 16 bytes length, how to encapsulate it into the newly defined NRP
> TLV?
> 
> 
> Best Regards
> 
> Aijun Wang
> China Telecom
> 
> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of [email protected]
> Sent: Friday, September 19, 2025 8:14 PM
> To: [email protected]
> Subject: [Pce] Adoption Poll for draft-dong-pce-pcep-nrp
> 
> Hi all,
> 
> This message starts an adoption poll for draft-dong-pce-pcep-nrp-04 [1].
> @WG members: do you think this document is a correct foundation to
> become a PCE WG work item?
> Please respond using the PCE mailing list, including rationale if you believe 
> it
> isn't ready.
> 
> Thank you,
> 
> Dhruv & Julien
> 
> --
> [1] https://datatracker.ietf.org/doc/draft-dong-pce-pcep-nrp/
> 
> _______________________________________________
> Pce mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
Pce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to