Draft: draft-ietf-quic-transport

Commentary: transport : fix typos and add internal reference
Paragraph (version A):
In a stateless design, a server can use encrypted and authenticated
tokens to pass information to clients that the server can later
recover and use to validate a client address.  Tokens are not
integrated into the cryptographic handshake and so they are not
authenticated.  For instance, a client might be able to reuse a
token.  To avoid attacks that exploit this property, a server can
limit its use of tokens to only the information needed validate
client addresses.
Paragraph (version B):
In a stateless design, a server can use encrypted and authenticated
tokens to pass information to clients that the server can later
recover and use to validate a client address.  Tokens are not
integrated into the cryptographic handshake and so they are not
authenticated.  For instance, a client might be able to reuse a
token.  To avoid attacks that exploit this property, a server can
limit its use of tokens to only the information needed to validate
client addresses.
Paragraph (version A):
This eliminates the use of the connection ID for linking activity
from the same connection on different networks.  Protection of packet
numbers ensures that packet numbers cannot be used to correlate
activity.  This does not prevent other properties of packets, such as
timing and size, from being used to correlate activity.
Paragraph (version B):
This eliminates the use of the connection ID for linking activity
from the same connection on different networks.  Header protection
ensures that packet numbers cannot be used to correlate activity.
This does not prevent other properties of packets, such as timing and
size, from being used to correlate activity.
Paragraph (version A):
Blocked signals are carried in DATA_BLOCKED, STREAM_DATA_BLOCKED,
and STREAMS_BLOCKED frames.  DATA_BLOCKED streams have connection
scope, STREAM_DATA_BLOCKED frames have stream scope, and
STREAMS_BLOCKED frames are scoped to a specific stream type.  New
frames are sent if packets containing the most recent frame for a
scope is lost, but only while the endpoint is blocked on the
corresponding limit.  These frames always include the limit that
is causing blocking at the time that they are transmitted.
Paragraph (version B):
Blocked signals are carried in DATA_BLOCKED, STREAM_DATA_BLOCKED,
and STREAMS_BLOCKED frames.  DATA_BLOCKED frames have connection
scope, STREAM_DATA_BLOCKED frames have stream scope, and
STREAMS_BLOCKED frames are scoped to a specific stream type.  New
frames are sent if packets containing the most recent frame for a
scope is lost, but only while the endpoint is blocked on the
corresponding limit.  These frames always include the limit that
is causing blocking at the time that they are transmitted.
Paragraph (version A):
Clients MUST ensure they send the first Initial packet in single IP
packet.  Similarly, the first Initial packet sent after receiving a
Retry packet MUST be sent in a single IP packet.
Paragraph (version B):
Clients MUST ensure they send the first Initial packet in a single IP
packet.  Similarly, the first Initial packet sent after receiving a
Retry packet MUST be sent in a single IP packet.
Paragraph (version A):
The idle timeout is a value in seconds that is encoded as an
integer.  If this parameter is absent or zero then the idle
timeout is disabled.
Paragraph (version B):
The idle timeout is a value in seconds that is encoded as an
integer, see (idle-timeout).  If this parameter is absent or zero
then the idle timeout is disabled.