[Tvr] Re: [External] FW: New Version Notification for draft-zdm-tvr-applicability-05.txt

["King, Daniel" <[e-mail]>]

Thanks, Li, and other I-D authors.

I appreciate the time you took to publish a new version of the I-D, and thanks for addressing my comments and assorted updates. Good job.

Re: JSON examples

Although I appreciate the multiple examples in the document, I wonder whether we should focus on a single example and go into more detail. This might depend on what the WG considers a suitable example of the TVR schedule being applied. The document has five examples; would two or three be enough, and then focus effort on providing a more detailed analysis and over-the-wire example code via a repository in an appendix.

Thinking aloud, why not combine with a network controller such as TeraFlowSDN (https://tfs.etsi.org/) and work with partners to prototype some TVR capabilities and consider operational aspects? This could also be supported via an IETF Hackathon. I'd be willing to volunteer and contribute code to achieve this if other people are also interested.

Re: Next Steps

Obviously up to the Chairs and WG, but I'd support adopting the I-D. I think it provides a necessary step towards achieving the WG's final chartered goals/milestones:

https://datatracker.ietf.org/group/tvr/about/

Nov 2025        Applicability Statement
Mar 2026        Implementation and Operational Considerations

BR, Dan.

-----Original Message-----
From: zhangli (CE) <[e-mail]>
Sent: 09 February 2026 12:17
To: tvr <[e-mail]>
Cc: [e-mail]; King, Daniel <[e-mail]>
Subject: [External] FW: New Version Notification for draft-zdm-tvr-applicability-05.txt

This email originated outside the University. Check before clicking links or attachments.

Dear TVR WG,

As you see, a new version of draft-zdm-tvr-applicability. This version addresses multiple comments from Dan King and also includes additional improvements to the document for clarity and explanation, including:

- Editorial/Readability Improvements
- Explaining TVR definitions
- Clarification for protocol usage and data stores related to TVR usage
- Further narrowing the scope of use cases and examples
- More details on handling schedule conflicts
- Recommendations for Security Considerations
- Practical Operator Considerations
- Cleaning up code and NITS related to JSON
- Additional References

Thanks a lot for Dan King's valuable comments and suggestions.

So, dear chairs and all, does the working group want to adopt the document?

If so, I think there is a need to make sure we have the right examples. A suggestion from Dan King is that maybe we can extend the detail of the use case JSON examples. Maybe Dan King can expand on what he means by this?

Best regards
Li

-----邮件原件-----
发件人: [e-mail] <[e-mail]>
发送时间: 2026年2月9日 19:39
收件人: Dongjie (Jimmy) <[e-mail]>; zhangli (CE) <[e-mail]>; Mohamed Boucadair <[e-mail]>
主题: New Version Notification for draft-zdm-tvr-applicability-05.txt

A new version of Internet-Draft draft-zdm-tvr-applicability-05.txt has been successfully submitted by Li Zhang and posted to the IETF repository.

Name:     draft-zdm-tvr-applicability
Revision: 05
Title:    Applicability of TVR YANG Data Models
Date:     2026-02-09
Group:    Individual Submission
Pages:    39
URL:      https://www.ietf.org/archive/id/draft-zdm-tvr-applicability-05.txt
Status:   https://datatracker.ietf.org/doc/draft-zdm-tvr-applicability/
HTML:     https://www.ietf.org/archive/id/draft-zdm-tvr-applicability-05.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-zdm-tvr-applicability
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-zdm-tvr-applicability-05

Abstract:

   Time-Variant Routing (TVR) is a routing system that can accommodate
   predicted topology changes caused by internal or external factors.
   Typical use cases include resource preservation networks, operating
   efficiency networks and dynamic reachability networks.  This document
   provides examples of how to implement the TVR scheduling capabilities
   for key use cases.  It describes which part of the TVR data model is
   used and why, and it outlines operational and security considerations
   when deploying TVR-based technologies.



The IETF Secretariat