Draft: draft-ietf-taps-interface

Commentary: Done 
 Thanks ! Looks good to me now . Thank you - makes it clearer and shorter
Paragraph (version A):
The application makes no representation about its expected
capacity profile.  No special optimizations of the tradeoff
between delay, delay variation, and bandwidth efficiency should be
made when selecting and configuring transport protocol stacks.
Transport system implementations that map the requested capacity
profile onto per-connection DSCP signaling without multiplexing
SHOULD assign the DSCP Default Forwarding RFC2474 PHB; when the
Connection is multiplexed, the guidelines in Section 6 of RFC7657
apply.
Paragraph (version A):
The application is not interactive.  It expects to send and/or
receive data without any urgency.  This can, for example, be used
to select protocol stacks with scavenger transmission control and/
or to assign the traffic to a lower-effort service.  Transport
system implementations that map the requested capacity profile
onto per-connection DSCP signaling without multiplexing SHOULD
assign the DSCP Less than Best Effort LE-PHB PHB; when the
Connection is multiplexed, the guidelines in Section 6 of RFC7657
apply.
Paragraph (version B):
This property specifies the desired network treatment for traffic
sent by the application and the tradeoffs the application is prepared
to make in path and protocol selection to receive that desired
treatment.  When the capacity profile is set to a value other than
Default, the transport system SHOULD select paths and configure
protocols to optimize the tradeoff between delay, delay variation,
and bandwidth efficiency based on the capacity profile specified.
How this is realized is implementation-specific.  The Capacity
Profile MAY also be used to set priorities on the wire for Protocol
Stacks supporting prioritization.  Recommendations for use with DSCP
are provided below for each profile; note that when a Connection is
multiplexed, the guidelines in Section 6 of RFC7657 apply.
Paragraph (version B):
The application provides no information about its expected
capacity profile.  Transport system implementations that map the
requested capacity profile onto per-connection DSCP signaling
SHOULD assign the DSCP Default Forwarding RFC2474 PHB.
Paragraph (version B):
The application is not interactive.  It expects to send and/or
receive data without any urgency.  This can, for example, be used
to select protocol stacks with scavenger transmission control and/
or to assign the traffic to a lower-effort service.  Transport
system implementations that map the requested capacity profile
onto per-connection DSCP signaling SHOULD assign the DSCP Less
than Best Effort LE-PHB PHB.
Paragraph (version A):
The application is interactive, and prefers loss to latency.
Response time should be optimized at the expense of bandwidth
efficiency and delay variation when sending on this connection.
This can be used by the system to disable the coalescing of
multiple small Messages into larger packets (Nagle's algorithm);
to prefer immediate acknowledgment from the peer endpoint when
supported by the underlying transport; and so on.  Transport
system implementations that map the requested capacity profile
onto per-connection DSCP signaling without multiplexing SHOULD
assign the DSCP Expedited Forwarding RFC3246 PHB; when the
Connection is multiplexed, the guidelines in Section 6 of RFC7657
apply.
Paragraph (version B):
The application is interactive, and prefers loss to latency.
Response time should be optimized at the expense of bandwidth
efficiency and delay variation when sending on this connection.
This can be used by the system to disable the coalescing of
multiple small Messages into larger packets (Nagle's algorithm);
to prefer immediate acknowledgment from the peer endpoint when
supported by the underlying transport; and so on.  Transport
system implementations that map the requested capacity profile
onto per-connection DSCP signaling without multiplexing SHOULD
assign the DSCP Expedited Forwarding RFC3246 PHB.
Paragraph (version A):
The application prefers loss to latency but is not interactive.
Response time should be optimized at the expense of bandwidth
efficiency and delay variation when sending on this connection.
Transport system implementations that map the requested capacity
profile onto per-connection DSCP signaling without multiplexing
SHOULD assign a DSCP Assured Forwarding (AF21,AF22,AF23,AF24)
RFC2597 PHB; when the Connection is multiplexed, the guidelines in
Section 6 of RFC7657 apply.
Paragraph (version B):
The application prefers loss to latency but is not interactive.
Response time should be optimized at the expense of bandwidth
efficiency and delay variation when sending on this connection.
Transport system implementations that map the requested capacity
profile onto per-connection DSCP signaling without multiplexing
SHOULD assign a DSCP Assured Forwarding (AF21,AF22,AF23,AF24)
RFC2597 PHB.
Paragraph (version A):
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 bandwidth efficiency.  This implies
that the Connection may fail if the desired rate cannot be
maintained across the Path.  A transport may 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; when
the Connection is multiplexed, the guidelines in Section 6 of
RFC7657 apply.
Paragraph (version B):
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 bandwidth efficiency.  This implies
that the Connection may fail if the desired rate cannot be
maintained across the Path.  A transport may 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.
Paragraph (version A):
The application expects to send/receive data at the maximum rate
allowed by its congestion controller over a relatively long period
of time.  Transport system implementations that map the requested
capacity profile onto per-connection DSCP signaling without
multiplexing SHOULD assign a DSCP Assured Forwarding
(AF11,AF12,AF13,AF14) RFC2597 PHB per Section 4.8 of RFC4594.
When the Connection is multiplexed, the guidelines in Section 6 of
RFC7657 apply.
Paragraph (version B):
The application expects to send/receive data at the maximum rate
allowed by its congestion controller over a relatively long period
of time.  Transport system implementations that map the requested
capacity profile onto per-connection DSCP signaling without
multiplexing SHOULD assign a DSCP Assured Forwarding
(AF11,AF12,AF13,AF14) RFC2597 PHB per Section 4.8 of RFC4594.