Draft: draft-ietf-taps-interface

Commentary: An alternative would be to remove negative values from the definition of Integer and Numeric , because I think we have no single negative usage anywhere . Still ... to me , this PR seems cleaner ( more forward - looking , as we might want to support negative values in some future update ? ) 
 LGMT
Paragraph (version A):
A Transport Services API can request a protocol that supports sending
keep alive packets keep-alive.  If this property is an Integer, it
specifies the maximum length of time an idle connection (one for
which no transport packets have been sent) should wait before the
Local Endpoint sends a keep-alive packet to the Remote Endpoint.
Adjusting this Property will only take effect when the underlying
stack supports sending keep-alive packets.  Guidance on setting this
value for datagram transports is provided in RFC8085.  A value
greater than the connection timeout (conn-timeout) or the enumerated
value "Disabled" will disable the sending of keep-alive packets.
Paragraph (version B):
A Transport Services API can request a protocol that supports sending
keep alive packets keep-alive.  If this property is Numeric, it
specifies the maximum length of time an idle connection (one for
which no transport packets have been sent) should wait before the
Local Endpoint sends a keep-alive packet to the Remote Endpoint.
Adjusting this Property will only take effect when the underlying
stack supports sending keep-alive packets.  Guidance on setting this
value for datagram transports is provided in RFC8085.  A value
greater than the connection timeout (conn-timeout) or the enumerated
value "Disabled" will disable the sending of keep-alive packets.
Paragraph (version A):
Integer values of this property specify an upper-bound rate that a
transfer is not expected to exceed (even if flow control and
congestion control allow higher rates), and/or a lower-bound rate
below which the application does not deem it will be useful.  These
are specified in bits per second.  The enumerated value "Unlimited"
indicates that no bound is specified.
Paragraph (version B):
Numeric values of this property specify an upper-bound rate that a
transfer is not expected to exceed (even if flow control and
congestion control allow higher rates), and/or a lower-bound rate
below which the application does not deem it will be useful.  These
are specified in bits per second.  The enumerated value "Unlimited"
indicates that no bound is specified.
Paragraph (version A):
If this property is an Integer, it controls the number of Connections
that can be accepted from a peer as new members of the Connection's
group.  Similar to SetNewConnectionLimit(), this limits the number of
ConnectionReceived Events that will occur, but constrained to the
group of the Connection associated with this property.  For a multi-
streaming transport, this limits the number of allowed streams.
Paragraph (version B):
If this property is Numeric, it controls the number of Connections
that can be accepted from a peer as new members of the Connection's
group.  Similar to SetNewConnectionLimit(), this limits the number of
ConnectionReceived Events that will occur, but constrained to the
group of the Connection associated with this property.  For a multi-
streaming transport, this limits the number of allowed streams.
Paragraph (version A):
This property represents the maximum Message size that an application
can send.  It is specified as the nummber of bytes.
Paragraph (version A):
This numeric property represents the maximum Message size that an
application can receive.  It specified as the number of bytes.
Paragraph (version B):
This property represents the maximum Message size that an application
can send.  It is specified as the number of bytes.
Paragraph (version B):
This property represents the maximum Message size that an application
can receive.  It specified as the number of bytes.