Deterministic Networking Problem Statement
draft-ietf-detnet-problem-statement-09

I'm balloting Yes (and not NoObj) because I specifically *do* see archival value in this document (and use-case / problem-statement documents in general); when someone has to implement / deploy the technology, having them understand what problem it is supposed to solve (or what the use case is) is valuable...

I did have a few nits - they are purely editorial, and I'm only mentioning them because I noticed them, feel free to address or not.

1: Section 1.  Introduction
"While the initial user base has focused almost entirely on Ethernet
   physical media and Ethernet-based bridging protocol (from several
   Standards Development Organizations), the need for Layer-3 expressed
   above, must not be confined to Ethernet and Ethernet-like media, and
   while such media must be encompassed by any useful Deterministic
   Networking (DetNet) Architecture, cooperation between IETF and other
   SDOs must not be limited to IEEE or IEEE 802."
I found this sentence to be hard to parse / a run on -- the comma between above and must didn't help, but splitting it up into multiple sentences would sure make it easier to read. 

2: "As a result of this work, it will be possible to establish a multi-hop path over the IP or MPLS network,"
The "will" in the above made me twitch -- I understand that that is the expected outcome / desire, but wording it as "will" seems like hubris.

3: "In other words, a Deterministic Network is
   backwards compatible with - capable of transporting - statistically
   multiplexed traffic while preserving the properties of the accepted
   deterministic flows."
The hyphens around "capable of transporting" confused me. Perhaps it was intended to be a parenthetical?