[quicwg/base-drafts] Should receipt of multiple promises really be an error? (#2232)

ekr <notifications@github.com> Thu, 20 December 2018 23:13 UTC

Date: Thu, 20 Dec 2018 23:12:53 +0000
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf47278cf3f615e063724437a20e6e7eb22d5cec792cf000000011833e3f492a169ce177076e8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2232@github.com>
Subject: [quicwg/base-drafts] Should receipt of multiple promises really be an error? (#2232)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c21f4e1a2f_402c3f84990d45b45611bf"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/c1UgyUSbFoyIGGvw_nqLeWP01q0>

S 4.2.6.

```
A server MUST NOT use a Push ID that is larger than the client has provided in a
MAX_PUSH_ID frame ({{frame-max-push-id}}) and MUST NOT use the same Push ID in
multiple PUSH_PROMISE frames.  A client MUST treat receipt of a PUSH_PROMISE
that contains a larger Push ID than the client has advertised or a Push ID which
has already been promised as a connection error of type HTTP_MALFORMED_FRAME.
```

Note that this doesn't match the convention we are using in QUIC transport
that things are idempotent and duplicates are fine.


-- 
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/issues/2232

[quicwg/base-drafts] Should receipt of multiple p… ekr
Re: [quicwg/base-drafts] Should receipt of multip… Martin Thomson
Re: [quicwg/base-drafts] Should receipt of multip… ianswett
Re: [quicwg/base-drafts] Should receipt of multip… Lucas Pardue
Re: [quicwg/base-drafts] Should receipt of multip… Mike Bishop
Re: [quicwg/base-drafts] Should receipt of multip… Mike Bishop