Draft: draft-ietf-taps-arch

Commentary: Addresses 
 The architecture draft uses UDP checksums as an example of a protocol - specific property in Section 3.2 and 4.1.2 . I find this a bit confusing because in the Interface draft , checksum coverage is a Generic Connection Property ( Section 11.1.2 ) . Should we maybe use a different example of a protocol - specific property , such as the TCP User Timeout we have in the Interface draft ? 
 Sure , we can switch the example around 
 Thanks , LGTM!Thanks – works
Paragraph (version A):
A specialized feature could be required by an application only when
using a specific protocol, and not when using others.  For example,
if an application is using UDP, it could require control over the
checksum or fragmentation behavior for UDP; if it used a protocol to
frame its data over a byte stream like TCP, it would not need these
options.  In such cases, the API ought to expose the features in such
a way that they take effect when a particular protocol is selected,
but do not imply that only that protocol could be used.  For example,
if the API allows an application to specify a preference to use a
partial checksum, communication would not fail when a protocol such
as TCP is selected, which uses a checksum covering the entire
payload.
Paragraph (version B):
A specialized feature could be required by an application only when
using a specific protocol, and not when using others.  For example,
if an application is using TCP, it could require control over the
User Timeout Option for TCP; these options would not take effect for
other transport protocols.  In such cases, the API ought to expose
the features in such a way that they take effect when a particular
protocol is selected, but do not imply that only that protocol could
be used.  For example, if the API allows an application to specify a
preference to use the User Timeout Option, communication would not
fail when a protocol such as QUIC is selected.
Paragraph (version A):
Connection Properties: The Connection Properties are used to
configure protocol-specific options and control per-connection
behavior of the Transport Services system; for example, a
protocol-specific Connection Property can express that if UDP is
used, the implementation ought to use checksums.  Note that the
presence of such a property does not require that a specific
protocol will be used.  In general, these properties do not
explicitly determine the selection of paths or protocols, but can
be used in this way by an implementation during connection
establishment.  Connection Properties are specified on a
Preconnection prior to Connection establishment, and can be
modified on the Connection later.  Changes made to Connection
Properties after Connection establishment take effect on a best-
effort basis.
Paragraph (version B):
Connection Properties: The Connection Properties are used to
configure protocol-specific options and control per-connection
behavior of the Transport Services system; for example, a
protocol-specific Connection Property can express that if TCP is
used, the implementation ought to use the User Timeout Option.
Note that the presence of such a property does not require that a
specific protocol will be used.  In general, these properties do
not explicitly determine the selection of paths or protocols, but
can be used in this way by an implementation during connection
establishment.  Connection Properties are specified on a
Preconnection prior to Connection establishment, and can be
modified on the Connection later.  Changes made to Connection
Properties after Connection establishment take effect on a best-
effort basis.