[quicwg/base-drafts] QPACK should require handling of integers up to of 62 bits long (#1727)

Kazuho Oku <notifications@github.com> Sat, 08 September 2018 04:21 UTC

Date: Fri, 07 Sep 2018 21:21:26 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd71c522f65ef3b5009fc68bda89f4cc7bc63ea2192cf0000000117ab104692a169ce155aa80d@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1727@github.com>
Subject: [quicwg/base-drafts] QPACK should require handling of integers up to of 62 bits long (#1727)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b934e4680ebe_60053fc8c14d45bc4315b4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/spSoz-vfwYlAxFCxfqrLIm6tSoM>

QPACK uses the integer encoding defined in [RFC 7541 section 5.1](https://httpwg.org/specs/rfc7541.html#integer.representation), which states:
> Integer encodings that exceed implementation limits — in value or octet length — MUST be treated as decoding errors. Different limits can be set for each of the different uses of integers, based on implementation constraints.

This was fine for HPACK because the maximum integer being transmitted was capped by the header table size.

OTOH, we use the encoding to transfer stream IDs. That means that QPACK implementations need to support decoding integers of up to 62 bits long.

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

[quicwg/base-drafts] QPACK should require handlin… Kazuho Oku
Re: [quicwg/base-drafts] QPACK should require han… Dmitri Tikhonov
Re: [quicwg/base-drafts] QPACK should require han… Mike Bishop
Re: [quicwg/base-drafts] QPACK should require han… afrind