[Tvr] Re: Call for adoption and IPR: draft-zdm-tvr-applicability-05 (Ends 2026-05-09)

[Adrian Farrel <[e-mail]>]

Hi Tony, all,

I think this is a useful piece of work. That is, I believe it is useful to have a "cookbook" to guide implementers and operators.

Nice Operational Considerations and Security Considerations sections - thank you.

Editorially, I'd ask he authors to carefully check the references: I think there are a few that should be made normative
7589
7951
8342
tvr-requirements

Would be good if the Appendix subsections had section numbers (such as A.1, etc.)

Check the IP addresses in all the examples. I think they need to come from the documentation ranges.

At some point, someone is going to ask why you haven't got an example using IPv6 addresses. Presumably it would be easy to switch one or two over from IPv4.

You have a few line length problems in the YANG and in particular Figure 7.

Cheers,
Adrian


-----Original Message-----
From: Tony Li via Datatracker <[e-mail]> 
Sent: 25 April 2026 17:37
To: [e-mail]; [e-mail]; [e-mail]
Subject: [Tvr] Call for adoption and IPR: draft-zdm-tvr-applicability-05 (Ends 2026-05-09)

This message starts a tvr WG Call for Adoption and IPR of:
draft-zdm-tvr-applicability-05

This Working Group Call for Adoption and IPR ends on 2026-05-09

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.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the tvr WG. Comments to explain your preference are
greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Authors and contributors MUST reply to this message with either:

"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the above by responding to this email regardless of 
whether or not you are aware of any relevant IPR. This document will not 
advance to the next stage until a response has been received from each 
author.

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-zdm-tvr-applicability/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-zdm-tvr-applicability-05.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-zdm-tvr-applicability-05

-- 
Tvr mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]