Document: draft-ietf-idr-sr-policy-nrp-03
Title: BGP SR Policy Extensions for Network Resource Partition
Reviewer: Menachem Dodge
Review result: Has Nits

I have reviewed this document as part of the Ops area directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
Ops area directors.
Document editors and WG chairs should treat these comments just like
any other last-call comments.

NITS
====

Introduction paragraph 2:
-------------------------
"RFC 9543 network slice" is mentioned four times in the paragraph. The paragraph begins with [RFC 9543] so could this just be written as 
"network slice"? Is there a reason/need to put an emphasis on "RFC 9543 network slice" ? 

In Section 3, second last paragraph
-----------------------------------
"For SR Policy with MPLS data plane, one approach to encapsulate the NRP Selector ID to the packet is based on the mechanism defined in [I-D.ietf-mpls-mna-fwk]"

Are there other approaches for MPLS data plane? Should these be mentioned or considered?

In Section 3, last paragraph
----------------------------
"...it is considered that the association between an SR Policy
   and NRP is consistent, in such case all candidate paths of one SR
   policy SHOULD be associated with the same NRP."

How should reception of candidate paths of one SR policy that are associated with different NRPs be handled ?

==================================================================

Other than this, the document is well written and understandable.

Thank you kindly,

Yours Sincerely,
Menachem Dodge