Re: [quicwg/base-drafts] Remove DUPLICATE_PUSH and allow duplicate PUSH_PROMISE (#3309)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



> @@ -1238,9 +1233,10 @@ MAX_PUSH_ID frame ({{frame-max-push-id}}). A client MUST treat receipt of a
 PUSH_PROMISE frame that contains a larger Push ID than the client has advertised
 as a connection error of H3_ID_ERROR.
 
-A server MUST NOT use the same Push ID in multiple PUSH_PROMISE frames. A client
-MUST treat receipt of a Push ID which has already been promised as a connection
-error of type H3_ID_ERROR.
+A server MAY use the same Push ID in multiple PUSH_PROMISE frames. If so, the
+decompressed request headers MUST be idential.  A client MUST treat receipt of a
+Push ID which has already been promised with different headers than the previous
+promise as a connection error of type H3_ID_ERROR.

> MUST-error requires that the client keep the request headers for the lifetime of the connection in case it ever sees that Push ID again.

As stated in https://github.com/quicwg/base-drafts/issues/3275#issuecomment-566379821, it is my understanding that an endpoint can determine if the PUSH_PROMISE refers to a new Push ID or a Push ID it already has received, and therefore my preference goes to stating "MUST error if there is a mismatch, or ignore the PUSH_PROMISE frame."

-- 
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/3309#discussion_r362355382