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
tsv-art@ietf.org if you reply to or forward this review.

Summary: Ready with Nits.

This document is well-written as an informational RFC. I don't see any technical issues related to transport, but it might be better to clarify the following minor point.

The draft allows DetNet data plane to carry flow ID and sequence number as metadata. 
But, aren't there any potential risks for the conflict of the flow ID or wrap-around of the sequence number? (especially for explicit case)
It might be better to state which module should care if it's out of scope for the draft or to clarify there is no risk against them.

Thanks,
--
Yoshi