Draft: draft-ietf-taps-arch

Commentary: Addresses 
 In the architecture document , I noticed that we sometimes say " Transport Services system " and sometimes " Transport System " . Are these the same ? Are " Transport Services implementation " and " Transport System implementation " the same , too ? 
 I prefer " Transport Services system " and " Transport Services implementation " 
 I find it long and clumsy :( Side note : we 'll have to rename it everywhere in the API draft too if we go with this . 
 was this fixed by ? 
 Yes it was . We already used Transport Services most places so it 's not all that different . 
 Looks good , thanks !
Paragraph (version A):
The Transport Services architecture evolves this general model of
interaction, aiming to both modernize the API surface presented to
applications by the transport layer and enrich the capabilities of
the Transport System implementation.  It combines interfaces for
multiple interaction patterns into a unified whole.  By combining
name resolution with connection establishment and data transfer in a
single API, it allows for more flexible implementations to provide
path and transport protocol agility on the application's behalf.
Paragraph (version B):
The Transport Services architecture evolves this general model of
interaction, aiming to both modernize the API surface presented to
applications by the transport layer and enrich the capabilities of
the Transport Services implementation.  It combines interfaces for
multiple interaction patterns into a unified whole.  By combining
name resolution with connection establishment and data transfer in a
single API, it allows for more flexible implementations to provide
path and transport protocol agility on the application's behalf.
Paragraph (version A):
the ability to manage dependencies between messages, when the
Transport System could decide to not deliver a message, either
following packet loss or because it has missed a deadline.  In
particular, this can avoid (re-)sending data that relies on a
previous transmission that was never received.
Paragraph (version B):
the ability to manage dependencies between messages, when the
Transport Services system could decide to not deliver a message,
either following packet loss or because it has missed a deadline.
In particular, this can avoid (re-)sending data that relies on a
previous transmission that was never received.
Paragraph (version A):
Connection Properties: The Connection Properties are used to
configure protocol-specific options and control per-connection
behavior of the Transport 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 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 A):
Abort: The action the application takes on a Connection to
indicate a Close and also indicate that the Transport System
SHOULD NOT attempt to deliver any outstanding data.  This is
intended for immediate termination of a connection, without
cleaning up state.
Paragraph (version B):
Abort: The action the application takes on a Connection to
indicate a Close and also indicate that the Transport Services
system SHOULD NOT attempt to deliver any outstanding data.  This
is intended for immediate termination of a connection, without
cleaning up state.
Paragraph (version A):
Specifically, a Transport System would consider protocols
identical only if they are of the same type and version.  For
example, the same version of TLS running over two different
transport Protocol Stacks are considered equivalent, whereas TLS
Transport Services systems MAY allow applications to indicate that
they consider two different transport protocols equivalent, e.g.,
to allow fallback to TLS 1.2 if TLS 1.3 is not available.
Paragraph (version B):
Specifically, a Transport Services system would consider protocols
identical only if they are of the same type and version.  For
example, the same version of TLS running over two different
transport Protocol Stacks are considered equivalent, whereas TLS
Transport Services systems MAY allow applications to indicate that
they consider two different transport protocols equivalent, e.g.,
to allow fallback to TLS 1.2 if TLS 1.3 is not available.
Paragraph (version A):
By default, stored properties of the implementation, such as cached
protocol state, cached path state, and heuristics, may be shared
(e.g. across multiple connections in an application).  This provides
efficiency and convenience for the application, since the Transport
System implementation can automatically optimize behavior.
Paragraph (version B):
By default, stored properties of the implementation, such as cached
protocol state, cached path state, and heuristics, may be shared
(e.g. across multiple connections in an application).  This provides
efficiency and convenience for the application, since the Transport
Services implementation can automatically optimize behavior.