Hi all，

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

- Document: [draft-ietf-tvr-schedule-yang-05]

- Reviewer: [Chongfeng Xie]

- Review Date: [December 03, 2025]

- Intended Status: [Standards Track] 

---

## Summary 

- Has Issues: I have some minor concerns about this document that I think should be resolved before publication.
 

## Major Issues 

- For a document that will become a standard in the future, a section of "Operational considerations" following RFC5706bis can be added, it will help operators to understand on how to use the three modules.
 
---

## Minor Issues 

- Three modules (ietf-tvr-schedule.yang, ietf-tvr-topology.yang, ietf-tvr-node.yang) have been defined in this document, it is recommended to introduce the relationship between these three modules in section 1 or or other places.

- Section 3.1 mainly introduces TVR Schedule, so I suggest that the title of section 3.1 can be changed to "TVR Schedule Definitions",  since schedule has been illustrated in other documents, such as draft-ietf-netmod-schedule-yang.

- In section 3.3, there is "Delay is the link propagation time and does not include any queuing delays. ", I wonder how to get the value of delay, does it depend on calculating the length of the underlying physical link?

- This draft has three appendixes (Appendix A, Appendix B, Appendix C). It is recommended to cite these appendixes in the relevant sections of the body, so as to show the relationship between the appendixes and the relevant content in the body.

- The following sentence in section 5 looks redundent，it can be removed,  
       "The following RFCs are not referenced in the document text but are referenced in the ... modules: [RFC6991]." 
    
---

## Nits 

- No nits found. 

---

Best regards
Chongfeng