[Tvr] Re: [Tsv-art] draft-ietf-tvr-requirements-07 ietf last call Tsvart review

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

Hi Mirja,

Many thanks for your TSV-ART review of our document. We have addressed your comments in the forthcoming -09 revision as follows:

1. Signal load of frequent schedule updates

Section 2.1.4 (Execution Locality) discusses the increased volume of data that distributing schedules imposes on the network, and how this can be mitigated by limiting the time horizon distributed to each device within a sliding window.

In addition, we have added text to Section 2.2.8 (Time-Overlap and Priority) highlighting solutions need to account for technology-specific constraints, including admission control, queue depth, sender pacing and loss.

Indeed, we believe a more detailed treatment of signalling load belongs in solution documents, but the considerations are now flagged for solution designers.

2. Abstract clarity

We have adopted your suggested rewording, many thanks! The Abstract now reads: "This document introduces requirements for the design and implementation of systems which perform TVR computations."

3. Section organisation

Agree, and have moved the TVR definition to the beginning of Section 2 (Overview of Time-Variant Networks), so the reader encounters the definition before the architectural discussion. We have also added a roadmap paragraph at the start of Section 2 explaining how its subsections fit together.

4. Various NITS

- Squashed Nit, "managed data proper"
- Corrected to "managed data model" in Section 2.1.2.
- Manager/manager capitalisation

Thank you again for the careful review.

BR, Dan. 

-----Original Message-----
From: Mirja Kühlewind via Datatracker <[e-mail]> 
Sent: 06 February 2026 18:12
To: [e-mail]
Cc: [e-mail]; [e-mail]; [e-mail]
Subject: [Tsv-art] draft-ietf-tvr-requirements-07 ietf last call Tsvart review

Document: draft-ietf-tvr-requirements
Title: TVR (Time-Variant Routing) Requirements
Reviewer: Mirja Kühlewind
Review result: Ready

This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information.

When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC [e-mail] if you reply to or forward this review.

There are no direct transport issues identified in this document. One point, that might be missing or is only briefly mentioned in section 3.1 point 3 that notes change frequency and costs, is the signal load on the network/system that frequency schedule updates might cause. However, maybe such a discussion is not in scope for this document?

Otherwise I have some minor, editorial comments/nits that you may or may not want to address:

1) In the abstract, this sentence is not clear to me:

“This document introduces requirements where TVR computations could
   improve message exchange in a network.”

MAYBE

“This document introduces requirements for the design and implementation of systems which perform TVR computations in order to improve message exchange in a network.”

?

2) As section 2.4 basically also contains the definition of TVR, I think it would have been easier for me to read the document if section 2.4. would be at the start of section 2. But I guess that a matter of taste.

Nits

1) In Section 2.1.2
OLD
Extrinsic Schedule:  In this situation, the schedule is not part of
      the managed data proper

NEW
Extrinsic Schedule:  In this situation, the schedule is not part of
      the managed data model

2) Section 2.1.4 (and 4.1)
While you always use Agent with an upper A; you write manager with a lower m (which it used with an upper M in the definitions). Is that intentional?