Draft: draft-ietf-taps-interface

Commentary: Applied requested changes 
 In 3.2 it is clear that you can set Message Properties on Connections and Preconnections , but the rest of the document is not very clear about this . In 4.2 for instance the text only talks about setting Selection Properties and Connection Properties on PreConnections . In 7.1.3 the text says " Connection Properties describe the default behavior for all Messages on a Connection " . But I think that Message Properties set on a Connection or PreConnection may also describe the default behavior so this relationship should be clarified . Also , the Message Property defaults given for Properties that do not depend on other Properties sets the defaults for all Messages in a Connection I assume ? I also assume that a Message Property set on a Message Context overrides a Message Property set on a PreConnection or Connection , but this is also not specified . In 5.4 .   , I assume that setting Message Properties on a Connection applies to all Connections in the Connection Group ? This is not clear . 
 In general , I agree . If you set a message property dynamically on a connection , though , I do n't think it would affect the group — I could have one stream in a multiplexed protocol have separate behavior , such as priority . 
 +1 to tfpauly . But this is already written in 5.4 , maybe you missed it (  ) ? " Message Properties are also not entangled . For example , changing  ( see Section 7.1.3.1 ) of a Message will only affect a single Message on a single Connection . " 
 I am fine with an update of a Message Property to a connection applying only to that connection . Priority is not a good example as it is already a special case , but my main issue was that we need to be more clear about the behavior in the specification . the issue is about setting a Message Property on a Connection . The text you refer to talk about setting Message Properties on a message . You could interpret the first part as a general statement , but the way the text is structured it is easy to think it refers to setting Message Properties on a message so I think we should be explicit also about setting Message Properties on a Connection . Could be a second example . 
 So after looking at the text again , I think the example talking about setting Message Properties on a message should be removed , see comment in the pull request . 
 Thanks ! !
Paragraph (version A):
A Preconnection Object holds properties reflecting the application's
requirements and preferences for the transport.  These include
Selection Properties for selecting protocol stacks and paths, as well
as Connection Properties for configuration of the detailed operation
of the selected Protocol Stacks.
Paragraph (version B):
A Preconnection Object holds properties reflecting the application's
requirements and preferences for the transport.  These include
Selection Properties for selecting protocol stacks and paths, as well
as Connection Properties and Message Properties for configuration of
the detailed operation of the selected Protocol Stacks on a per-
Connection and Message level.
Paragraph (version A):
Message Properties are also not entangled.  For example, changing
"Lifetime" (see msg-lifetime) of a Message will only affect a single
Message on a single Connection.
Paragraph (version B):
Message Properties set on a Connection also apply only to that
Connection.
Paragraph (version A):
Connection Properties describe the default behavior for all Messages
on a Connection.  If a Message Property contradicts a Connection
Property, and if this per-Message behavior can be supported, it
overrides the Connection Property for the specific Message.  For
example, if "Reliable Data Transfer (Connection)" is set to "Require"
and a protocol with configurable per-Message reliability is used,
setting "Reliable Data Transfer (Message)" to "false" for a
particular Message will allow this Message to be sent without any
reliability guarantees.  Changing the Reliable Data Transfer property
on Messages is only possible for Connections that were established
enabling the Selection Property "Configure Per-Message Reliability".
Paragraph (version B):
If a Message Property contradicts a Connection Property, and if this
per-Message behavior can be supported, it overrides the Connection
Property for the specific Message.  For example, if "Reliable Data
Transfer (Connection)" is set to "Require" and a protocol with
configurable per-Message reliability is used, setting "Reliable Data
Transfer (Message)" to "false" for a particular Message will allow
this Message to be sent without any reliability guarantees.  Changing
the Reliable Data Transfer property on Messages is only possible for
Connections that were established enabling the Selection Property
"Configure Per-Message Reliability".