Draft: draft-ietf-quic-transport

Commentary: Minor nits and changes .
Paragraph (version A):
For connections that are no longer needed or desired, there are
several ways for a client and server to terminate a connection
(termination).
Paragraph (version B):
For connections that are no longer needed or desired, there are
several ways for a client and server to terminate a connection, as
described in termination.
Paragraph (version B):
An endpoint verifies support for Explicit Congestion Notification
(ECN) by observing whether the ACK frames acknowledging the first
packets it sends carry ECN counts, as described in ecn-validation.
Paragraph (version A):
Unlike the token that is created for a Retry packet, which is used
immediately, the token sent in the NEW_TOKEN frame might be used
after some period of time has passed.  Thus, a token SHOULD have an
expiration time, which could be either an explicit expiration time or
an issued timestamp that can be used to dynamically calculate the
expiration time.  A server can store the expiration time or include
it in an encrypted form in the token.
Paragraph (version B):
Unlike the token that is created for a Retry packet, which is used
immediately, the token sent in the NEW_TOKEN frame can be used after
some period of time has passed.  Thus, a token SHOULD have an
expiration time, which could be either an explicit expiration time or
an issued timestamp that can be used to dynamically calculate the
expiration time.  A server can store the expiration time or include
it in an encrypted form in the token.
Paragraph (version A):
An endpoint MAY include other frames with the PATH_CHALLENGE and
PATH_RESPONSE frames used for path validation.  In particular, an
endpoint can include PADDING frames with a PATH_CHALLENGE frame for
Path Maximum Transfer Unit (PMTU) discovery (see pmtud); it can also
include its own PATH_CHALLENGE frame with a PATH_RESPONSE frame.
Paragraph (version B):
An endpoint MAY include other frames with the PATH_CHALLENGE and
PATH_RESPONSE frames used for path validation.  In particular, an
endpoint can include PADDING frames with a PATH_CHALLENGE frame for
Path Maximum Transmission Unit Discovery (PMTUD; see pmtud); it can
also include its own PATH_CHALLENGE frame with a PATH_RESPONSE frame.
Paragraph (version A):
If the peer sent the disable_active_migration transport parameter, an
endpoint also MUST NOT send packets (including probing packets; see
probing) from a different local address to the address the peer used
during the handshake.  An endpoint that has sent this transport
parameter, but detects that a peer has nonetheless migrated to a
different remote address MUST either drop the incoming packets on
that path without generating a stateless reset or proceed with path
validation and allow the peer to migrate.  Generating a stateless
reset or closing the connection would allow third parties in the
network to cause connections to close by spoofing or otherwise
manipulating observed traffic.
Paragraph (version B):
If the peer sent the disable_active_migration transport parameter, an
endpoint also MUST NOT send packets (including probing packets; see
probing) from a different local address to the address the peer used
during the handshake, unless the endpoint has acted on a
preferred_address transport parameter from the peer.  If the peer
violates this requirement, the endpoint MUST either drop the incoming
packets on that path without generating a stateless reset or proceed
with path validation and allow the peer to migrate.  Generating a
stateless reset or closing the connection would allow third parties
in the network to cause connections to close by spoofing or otherwise
manipulating observed traffic.
Paragraph (version A):
After changing the address to which it sends non-probing packets, an
endpoint could abandon any path validation for other addresses.
Paragraph (version A):
Receiving a packet from a new peer address might be the result of a
NAT rebinding at the peer.
Paragraph (version B):
After changing the address to which it sends non-probing packets, an
endpoint can abandon any path validation for other addresses.
Paragraph (version B):
Receiving a packet from a new peer address could be the result of a
NAT rebinding at the peer.