Merge remote-tracking branch 'origin/master' into goaway

Author: MikeBishop

draft-ietf-quic-transport.md

@@ -1440,13 +1440,13 @@ period of time.  A QUIC connection, once established, can be terminated in one
 of three ways:
 
 1. Explicit Shutdown: An endpoint sends a CONNECTION_CLOSE frame to
-   initiate a connection termination.  An endpoint MAY use application-layer
-   mechanisms to gracefully close activity on the connection. On termination of
-   the active streams, a CONNECTION_CLOSE may be sent.  If an endpoint sends a
-   CONNECTION_CLOSE frame while unterminated streams are active (no FIN bit or
-   RST_STREAM frames have been sent or received for one or more streams), then
-   the peer must assume that the streams were incomplete and were abnormally
-   terminated.
+   terminate the connection.  An endpoint MAY use application-layer mechanisms
+   prior to a CONNECTION_CLOSE to indicate that the connection will soon be
+   terminated.  On termination of the active streams, a CONNECTION_CLOSE may be
+   sent.  If an endpoint sends a CONNECTION_CLOSE frame while unterminated
+   streams are active (no FIN bit or RST_STREAM frames have been sent or
+   received for one or more streams), then the peer must assume that the streams
+   were incomplete and were abnormally terminated.
 
 2. Implicit Shutdown: The default idle timeout is a required parameter in
    connection negotiation.  The maximum is 10 minutes.  If there is no network
@@ -1465,9 +1465,18 @@ of three ways:
    should send a Public Reset packet in return.  (TODO: articulate rules around
    when a public reset should be sent.)
 
-TODO: Connections that are terminated are added to a TIME_WAIT list at the
-server, so as to absorb any straggler packets in the network.  Discuss TIME_WAIT
-list.
+After receiving either a CONNECTION_CLOSE frame or a Public Reset, an
+endpoint MUST NOT send additional packets on that connection. After
+sending either a CONNECTION_CLOSE frame or a Public Reset packet,
+implementations MUST NOT send any non-closing packets on that
+connection. If additional packets are received after this time and
+before idle_timeout seconds has passed, implementations SHOULD respond
+to them by sending a CONNECTION_CLOSE (which MAY just be a duplicate
+of the previous CONNECTION_CLOSE packet) but MAY also send a Public
+Reset packet.  Implementations SHOULD throttle these responses, for
+instance by exponentially backing off the number of packets which are
+received before sending a response.  After this time, implementations
+SHOULD respond to unexpected packets with a Public Reset packet.
 
 # Frame Types and Formats