Draft: draft-ietf-taps-interface

Commentary: Rather than saying " this can only be queried " everywhere , I split this into setting and querying now , and I also moved SoftErrors in there . It 's not precisely " querying " for a Property , but it 's the closest match - better than " Connection Termination " , I think ( this is where SoftErrors were before ) . 
 what about " Connection Maintenance : Setting Properties and Obtaining Information " ? 
 Maintenance sounds a bit strange to me , " Managing Connections : Setting Properties and Obtaining Information " ? 
 I like it ( and I agree about " maintenance " being slightly strange ) 
 Managing sounds good to me too . 
  , done 
 lgtm , thanks !
Paragraph (version A):
At any point, the application can query Connection Properties.  It
can also set per-connection Protocol Properties.
Paragraph (version A):
For Connections that are Establishing: Transport Properties that
the application specified on the Preconnection, see connection-
props.  Selection Properties of a Connection can only be queried,
not set.
Paragraph (version B):
For Connections that are Establishing: Transport Properties that
the application specified on the Preconnection, see connection-
props.
Paragraph (version A):
Selection Properties indicate whether or not the Connection has
or offers a certain Selection Property.  Note that the actually
instantiated protocol stack may not match all Protocol
Selection Properties that the application specified on the
Preconnection.  For example, a certain Protocol Selection
Property that an application specified as Preferred may not
actually be present in the chosen protocol stack because none
of the currently available transport protocols had this
feature.  Selection Properties of a Connection can only be
queried.
Paragraph (version A):
Protocol Properties of the protocol stack in use (see protocol-
props below).  These can be queried and set.  Certain specific
Procotol Properties may be read-only, on a protocol- and
property-specific basis.
Paragraph (version A):
For Connections that are Established, properties of the path(s) in
use.  These properties can be derived from the local provisioning
domain RFC7556, measurements by the Protocol Stack, or other
sources.  They can only be queried.
Paragraph (version B):
Selection Properties indicate whether or not the Connection has
or offers a certain Selection Property.  Note that the actually
instantiated protocol stack may not match all Protocol
Selection Properties that the application specified on the
Preconnection.  For example, a certain Protocol Selection
Property that an application specified as Preferred may not
actually be present in the chosen protocol stack because none
of the currently available transport protocols had this
feature.
Paragraph (version B):
Protocol Properties of the protocol stack in use (see protocol-
props).
Paragraph (version B):
For Connections that are Established, properties of the path(s) in
use.  These properties can be derived from the local provisioning
domain RFC7556, measurements by the Protocol Stack, or other
sources.
Paragraph (version B):
Slightly different from "querying", a SoftError Event can also occur,
informing the application about the receipt of an ICMP error message
related to the Connection.  This will only happen if the underlying
protocol stack supports access to soft errors; however, even if the
underlying stack supports it, there is no guarantee that a soft error
will be signaled.
Paragraph (version A):
A SoftError can inform the application about the receipt of an ICMP
error message that does not force termination of the connection, if
the underlying protocol stack supports access to soft errors;
however, even if the underlying stack supports it, there is no
guarantee that a soft error will be signaled.