Draft: draft-ietf-taps-interface

Commentary: Message Context Parameters / Properties are now Message Properties , and associated terminology cleanup . Addresses part of the resolution to . 
 Looks good , thanks for the cleanup!LGTM
Paragraph (version A):
Each application using the Transport Services Interface declares its
preferences for how the transport service should operate using
properties at each stage of the lifetime of a connection.  During
pre-establishment, Selection Properties selection-props are used to
specify which paths and protocol stacks can be used and are preferred
by the application, and Connection Properties connection-props can be
used to fine-tune the eventually established connection.  These
Connection Properties can also be used to monitor and fine-tune
established connections.  The behavior of the selected protocol
stack(s) when sending Messages is controlled by Message Context
Properties message-props.
Paragraph (version B):
Each application using the Transport Services Interface declares its
preferences for how the transport service should operate using
properties at each stage of the lifetime of a connection.  During
pre-establishment, Selection Properties selection-props are used to
specify which paths and protocol stacks can be used and are preferred
by the application, and Connection Properties connection-props can be
used to fine-tune the eventually established connection.  These
Connection Properties can also be used to monitor and fine-tune
established connections.  The behavior of the selected protocol
stack(s) when sending Messages is controlled by Message Properties
message-props.
Paragraph (version A):
An InitiateError occurs either when the set of transport properties
and cryptographic parameters cannot be fulfilled on a Connection for
initiation (e.g. the set of available Paths and/or Protocol Stacks
meeting the constraints is empty) or reconciled with the local and/or
remote endpoints; when the remote specifier cannot be resolved; or
when no transport-layer connection can be established to the remote
endpoint (e.g. because the remote endpoint is not accepting
connections, or the application is prohibited from opening a
Connection by the operating system).
Paragraph (version B):
An InitiateError occurs either when the set of transport properties
and security parameters cannot be fulfilled on a Connection for
initiation (e.g. the set of available Paths and/or Protocol Stacks
meeting the constraints is empty) or reconciled with the local and/or
remote endpoints; when the remote specifier cannot be resolved; or
when no transport-layer connection can be established to the remote
endpoint (e.g. because the remote endpoint is not accepting
connections, or the application is prohibited from opening a
Connection by the operating system).
Paragraph (version A):
Applications may need to annotate the Messages they send with extra
information to control how data is scheduled and processed by the
transport protocols in the Connection.  A messageContext object
contains parameters for sending Messages, and can be passed to the
Send Action.  Note that these properties are per-Message, not per-
Send if partial Messages are sent (send-partial).  All data blocks
associated with a single Message share properties.  For example, it
would not make sense to have the beginning of a Message expire, but
allow the end of a Message to still be sent.
Paragraph (version B):
Applications may need to annotate the Messages they send with extra
information to control how data is scheduled and processed by the
transport protocols in the Connection.  A MessageContext object
contains properties for sending Messages, and can be passed to the
Send Action.  Note that these properties are per-Message, not per-
Send if partial Messages are sent (send-partial).  All data blocks
associated with a single Message share properties.  For example, it
would not make sense to have the beginning of a Message expire, but
allow the end of a Message to still be sent.
Paragraph (version A):
Parameters may be added to a messageContext object only before the
context is used for sending.  Once a messageContext has been used
with a Send call, modifying any of its parameters is invalid.
Paragraph (version B):
Properties may be added to a MessageContext object only before the
context is used for sending.  Once a messageContext has been used
with a Send call, modifying any of its properties is invalid.
Paragraph (version A):
All messageData sent with the same messageContext object will be
treated as belonging to the same Message, and will constitute an in-
order series until the endOfMessage is marked.  Once the end of the
Message is marked, the messageContext object may be re-used as a new
Message with identical parameters.
Paragraph (version B):
All data sent with the same MessageContext object will be treated as
belonging to the same Message, and will constitute an in-order series
until the endOfMessage is marked.  Once the end of the Message is
marked, the MessageContext object may be re-used as a new Message
with identical parameters.
Paragraph (version A):
The Capacity Profile for a selected protocol stack may be modified on
a per-Message basis using the Transmission Profile Message Context
Property; see send-profile.
Paragraph (version B):
The Capacity Profile for a selected protocol stack may be modified on
a per-Message basis using the Transmission Profile Message Property;
see send-profile.