Draft: draft-ietf-taps-arch

Commentary: From the email : 
 Thank you for addressing this – Looks good !
Paragraph (version A):
The diagram below provides a high-level view of the actions and
events during the lifetime of a connection.  Note that some actions
are alternatives (e.g., whether to initiate a connection or to listen
for incoming connections), while others are optional (e.g., setting
Connection and Message Properties in Pre-Establishment) or have been
omitted for brevity.
Paragraph (version B):
The diagram below provides a high-level view of the actions and
events during the lifetime of a Connection object.  Note that some
actions are alternatives (e.g., whether to initiate a connection or
to listen for incoming connections), while others are optional (e.g.,
setting Connection and Message Properties in Pre-Establishment) or
have been omitted for brevity.
Paragraph (version A):
Selection Properties: The Selection Properties consist of the
options that an application can set to influence the selection of
paths between the local and remote systems, to influence the
selection of transport protocols, or to configure the behavior of
generic transport protocol features.  These options can take the
form of requirements, prohibitions, or preferences.  Examples of
options that influence path selection include the interface type
(such as a Wi-Fi connection, or a Cellular LTE connection),
requirements around the Maximum Transmission Unit (MTU) or path
MTU (PMTU), or preferences for throughput and latency properties.
Examples of options that influence protocol selection and
configuration of transport protocol features include reliability,
service class, multipath support, and fast open support.
Paragraph (version B):
Selection Properties: The Selection Properties consist of the
options that an application can set to influence the selection of
paths between the local and remote systems, to influence the
selection of transport protocols, or to configure the behavior of
generic transport protocol features.  These options can take the
form of requirements, prohibitions, or preferences.  Examples of
options that influence path selection include the interface type
(such as a Wi-Fi connection, or a Cellular LTE connection),
requirements around the largest Message that can be sent, or
preferences for throughput and latency properties.  Examples of
options that influence protocol selection and configuration of
transport protocol features include reliability, service class,
multipath support, and fast open support.
Paragraph (version A):
Protocol Stack: A set of Protocol Instances (including relevant
application, security, transport, or Internet protocols) that are
used together to establish connectivity or send and receive
Messages.  A single stack can be simple (a single transport
protocol instance over IP), or complex (multiple application
protocol streams going through a single security and transport
protocol, over IP; or, a multi-path transport protocol over
multiple transport sub-flows).
Paragraph (version A):
Candidate Path: One path that is available to an application and
conforms to the Selection Properties and System Policy.  Candidate
Paths are identified during the gathering phase (gathering) and
can be used during the racing phase (racing).
Paragraph (version B):
Protocol Stack: A set of Protocol Instances (including relevant
application, security, transport, or Internet protocols) that are
used together to establish connectivity or send and receive
Messages.  A single stack can be simple (a single transport
protocol instance over IP), or it can be complex (multiple
application protocol streams going through a single security and
transport protocol, over IP; or, a multi-path transport protocol
over multiple transport sub-flows).
Paragraph (version B):
Candidate Path: One path that is available to an application and
conforms to the Selection Properties and System Policy, of which
there can be several.  Candidate Paths are identified during the
gathering phase (gathering) and can be used during the racing
phase (racing).
Paragraph (version A):
Remote Endpoint Racing: Remote Endpoint Racing is the act of
attempting to establish, or scheduling attempts to establish,
multiple Protocol Stacks that differ based on the specific
representation of the Remote Endpoint, such as IP addresses
resolved from a DNS hostname.
Paragraph (version B):
Remote Endpoint Racing: Remote Endpoint Racing is the act of
attempting to establish, or scheduling attempts to establish,
multiple Protocol Stacks that differ based on the specific
representation of the Remote Endpoint, such as a particular IP
address that was resolved from a DNS hostname.
Paragraph (version A):
The interface to specify these groups MAY expose fine-grained tuning
for which properties and cached state is allowed to be shared with
other Connections.  For example, an application might want to allow
sharing TCP Fast Open cookies across groups, but not TLS session
state.
Paragraph (version B):
The interface to specify a Connection Group MAY expose fine-grained
tuning for which properties and cached state is allowed to be shared
with other Connections.  For example, an application might want to
allow sharing TCP Fast Open cookies across groups, but not TLS
session state.