[quicwg/base-drafts] DUPLICATE_PUSH push ID validation (#2681)

Lucas Pardue <notifications@github.com> Thu, 09 May 2019 16:16 UTC

Date: Thu, 09 May 2019 09:16:46 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4ERYGQTKEPO57QX4F24GCO5EVBNHHBUXKDQA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2681@github.com>
Subject: [quicwg/base-drafts] DUPLICATE_PUSH push ID validation (#2681)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd4526ea4a5d_31313fb3cd0cd96847848"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8PXevMbUNtmsjfG20lPISbsHrnY>

Two questions: 
1. Should DUPLICATE_PUSH respect max push ID limit?
  PUSH_PROMISE says the following:

 > A server MUST NOT use a Push ID that is larger than the client has
   provided in a MAX_PUSH_ID frame (Section 4.2.8) and MUST NOT use the
   same Push ID in multiple PUSH_PROMISE frames

2. What should a client do if it sees a DUPLICATE_PUSH for an ID of a PUSH_PROMISE that it never received?

This could be caused by a race condition, so it seems sensible to allow this to clients to support this without error. We should probably document that like we did for other racy things.
It 

-- 
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/2681

[quicwg/base-drafts] DUPLICATE_PUSH push ID valid… Lucas Pardue
Re: [quicwg/base-drafts] DUPLICATE_PUSH push ID v… Mike Bishop
Re: [quicwg/base-drafts] DUPLICATE_PUSH push ID v… Lucas Pardue
Re: [quicwg/base-drafts] DUPLICATE_PUSH push ID v… Mike Bishop