Original text:
The application expects to send/receive data at a constant rate after Connection establishment.  Delay and delay variation should be minimized at the expense of efficient use of the available <del> capacity.  This implies that the Connection might fail if the desired rate cannot be maintained across the Path.  A transport can interpret this capacity profile as preferring a circuit breaker RFC8084 to a rate-adaptive congestion controller. Transport system implementations that map the requested capacity profile onto per-connection DSCP signaling without multiplexing SHOULD assign a DSCP Assured Forwarding (AF31,AF32,AF33,AF34) RFC2597 PHB. </del>  The application expects to send/receive data at the maximum rate allowed by its congestion controller over a relatively long period

Reviewer comments:
To address NiTs
I-D.ietf-tsvwg-datagram-plpmtud is now a RFC.
See PR
Resolved in PR
The current text says: Constant-Rate Streaming: The application expects to send/receive data at a constant rate after Connection establishment. Delay and delay variation should be minimized at the expense of efficient use of the available capacity. This implies that the Connection might fail if the desired rate cannot be maintained across the Path. this last sentence sounds a little like the app needs to maintain the rate, rather than the path is expected to offer the rate. Could we change the last sentence to: /This implies that the Connection might fail if the Path is unable to maintain the desired rate. /
See PR
This was fixed in PR
Editorial: This text at the end of the intro reads odd to me: ‘This specific transport stack choice is discouraged for general use, because it can reduce the portability.’ I think it should read more like: ‘This choice, which only permits using a specific transport stack is discouraged for general use, because it can reduce the portability.’ —— Editorial; Is a Connection an instance of the stack? The current text says: ‘A Connection represents a transport Protocol Stack on which data can be sent to and/or received from a Remote Endpoint’ This may be better as?: ‘A Connection represents an instance if a transport Protocol Stack on which data can be sent to and/or received from a Remote Endpoint’ —— ‘Editorial ‘through a Message Framer which finds message’ Should this be: ‘through a Message Framer that finds message’
See PR
Resolved in PR
This LGTM, thanks!

Revised text:
The application expects to send/receive data at a constant rate after Connection establishment.  Delay and delay variation should be minimized at the expense of efficient use of the available  <ins> capacity.  This implies that the Connection might fail if the Path is unable to maintain the desired rate.  A transport can interpret this capacity profile as preferring a circuit breaker RFC8084 to a rate-adaptive congestion controller.  Transport system implementations that map the requested capacity profile onto per- connection DSCP signaling without multiplexing SHOULD assign a DSCP Assured Forwarding (AF31,AF32,AF33,AF34) RFC2597 PHB. </ins> The application expects to send/receive data at the maximum rate allowed by its congestion controller over a relatively long period