## Summary Choose one: - Has Issues: I have some minor concerns about this document that I think should be resolved before publication. ## General Operational Comments Alignment with RFC 5706bis The mechanism is operationally feasible and the core design is deployable, but the Operational Considerations content should be expanded as described below to fully align with RFC 5706bis. ## Major Issues > No major issues found. --- ## Minor Issues 1. Dentification of Abnormal States Section 3.5, Step 3 specifies that when an SR Policy cannot be resolved or transitions to Down, the FlowSpec route MUST be retained in the Loc-RIB and continue to be advertised downstream, but the forwarding plane must not activate it or must mark it inactive. However, the draft does not state how this state should be identified by operations, or how this state should be handled, for example, the alarm escalation and clearing conditions for this state. 2.Installation Ordering Considerations FlowSpec rules may be installed before the corresponding SR Policy is ready, causing transient traffic misclassification or blackholing. Section 3.8.2 of this draft classifies this case as “Drop-on-Failure” handling. Suggestion: Add installation ordering considerations to Section 5, Operational Considerations, recommending that controllers ensure, during orchestration, that the SR Policy is ready before the FlowSpec steering route that references it; otherwise, traffic may be misclassified or dropped. 3.Verification Procedure Considerations The current draft does not explain how to verify whether a steering route works as expected; it is suggested to add a verification procedure. 4.MTU Considerations Section 3.3.3 discusses data-plane encapsulation but not the resulting increase in packet length. Steering into an SR Policy adds SR-MPLS label stack or SRv6 outer IPv6 header (and SRH) overhead, reducing the effective path MTU,and operators should ensure that the path MTU/PMTUD configuration can accommodate it. ---