Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this Internet-Draft. 

The Operational Directorate reviews all operational and management-related Internet-Drafts to ensure alignment with operational best practices and that adequate operational considerations are covered.

A complete set of _"Guidelines for Considering Operations and Management in IETF Specifications"_ can be found at https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/.

While these comments are primarily for the Operations and Management Area Directors (Ops ADs), the authors should consider them alongside other feedback received.


- Document: draft-ietf-netconf-adaptive-subscription-14

- Reviewer: Dhruv Dhody

- Review Date: 2026-01-16

- Intended Status: Experimental

 
---

## Summary 

- 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 

In line with RFC 5706bis, the Operational Considerations section (Section 5) would benefit from expansion to explain how operators are expected to use adaptive subscriptions in practice, including examples of potential failure or instability scenarios (e.g., frequent adaptation due to poorly chosen evaluation expressions) and what operational signals (such as adaptive-period update notifications or subscription state) operators should monitor to detect and troubleshoot such conditions.
  
## Major Issues 

No major issues found. 

---

## Minor Issues 

- Section 1.2: It is unclear whether an open-ended experiment is appropriate in this case. Additionally, the rationale for selecting a 20% telemetry reduction as a success criterion is unclear; it would be unfortunate if the experiment were considered unsuccessful at, for example, a 19% reduction. Finally, the phrase “leak out” is unclear in this context.

 
---

## Nits 

- s/Two types of subscription are introduced/Two types of subscriptions are introduced/
- s/allows update to be triggered/allows updates to be triggered/
- s/can be capture at the same time/can be captured at the same time/
- s/wherever changes to the targeted data node occur/whenever changes to the targeted data node occur/
- s/which add complexity/which adds complexity/
- s/may be returned as supplemental information/may be returned as supplementary information/

---

Thanks! 
Dhruv