Re: [quicwg/base-drafts] Clients can send GOAWAY too (#3129)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



> -stream is reset individually, or the connection terminates.  Servers MAY reject
-individual requests on streams below the indicated ID if these requests were not
-processed.
+connection and initiate a graceful connection close.  Endpoints initiate the
+graceful shutdown of a connection by sending a GOAWAY frame ({{frame-goaway}}).
+The GOAWAY frame contains an identifier that indicates to the receiver the range
+of requests or pushes that were or might be processed in this connection.  The
+server sends a client-initiated bidirectional Stream ID; the client sends a Push
+ID.  Requests or pushes with the indicated identifier or greater are rejected by
+the sender of the GOAWAY.  This identifier MAY be zero if no requests or pushes
+were processed.
+
+The information in the GOAWAY enables a client and server to agree on which
+requests or pushes were accepted prior to the connection shutdown.  Endpoints
+SHOULD abruptly terminate any requests or pushes that have identifiers greater
+than or equal to the smallest identifier sent in a GOAWAY frame.

I think we can remove this sentence, as we talk more specifically in the sentence starting from line 708 (i.e. "It is RECOMMENDED that the receiving endpoint explicitly reject such requests (see {{request-cancellation}}) or pushes (see {{frame-cancel-push}}) in order to clean up transport state for the affected streams."), and because the abstract is already given in the sentence starting from line 690 (i.e. "Requests or pushes with the indicated identifier or greater are rejected by the sender of the GOAWAY.").

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3129#pullrequestreview-342537325