[quicwg/base-drafts] Don't use bitmap frames to describe varint structures (#3115)

"Roy T. Fielding" <notifications@github.com> Thu, 17 October 2019 19:56 UTC

Date: Thu, 17 Oct 2019 12:56:39 -0700
From: "Roy T. Fielding" <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYXW6AGAZBMXIAA2Y53WYEAPEVBNHHB4UPZEI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3115@github.com>
Subject: [quicwg/base-drafts] Don't use bitmap frames to describe varint structures (#3115)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da8c7779bd27_57c83fcee82cd96c160962"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Xzm8iBjyG7UEju23qz9yPzoRPqQ>

Many of the QUIC drafts use fixed 32bit maps to "illustrate" the layout of various parts of a message. In some cases, that is useful up to the point where the frame bits end. In other cases, the illustration consists of a list of arbitrary varint values, for which the 32bit illustration is both horribly misleading and a waste of space (and reader's time). Please stop.

I prefer C-style data structures for descriptive ordering, but YMMV. The simplest alternative is to just list the variable names (and types) in order. The only place where I would like to see a bitmap presentation would be an actual example, which shows the variable ints in the actual positions that the example values would cause them to be placed.

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

[quicwg/base-drafts] Don't use bitmap frames to d… Roy T. Fielding
Re: [quicwg/base-drafts] Don't use bitmap frames … David Schinazi
Re: [quicwg/base-drafts] Don't use bitmap frames … ianswett
Re: [quicwg/base-drafts] Don't use bitmap frames … Mike Bishop
Re: [quicwg/base-drafts] Don't use bitmap frames … Roy T. Fielding
Re: [quicwg/base-drafts] Don't use bitmap frames … ekr
Re: [quicwg/base-drafts] Don't use bitmap frames … Lucas Pardue
Re: [quicwg/base-drafts] Don't use bitmap frames … Kazuho Oku
Re: [quicwg/base-drafts] Don't use bitmap frames … Nick Harper
Re: [quicwg/base-drafts] Don't use bitmap frames … Lucas Pardue
Re: [quicwg/base-drafts] Don't use bitmap frames … Nick Harper
Re: [quicwg/base-drafts] Don't use bitmap frames … Lucas Pardue
Re: [quicwg/base-drafts] Don't use bitmap frames … Martin Thomson
Re: [quicwg/base-drafts] Don't use bitmap frames … Kazuho Oku
Re: [quicwg/base-drafts] Don't use bitmap frames … Marten Seemann
Re: [quicwg/base-drafts] Don't use bitmap frames … Robin Marx
Re: [quicwg/base-drafts] Don't use bitmap frames … Lucas Pardue
Re: [quicwg/base-drafts] Don't use bitmap frames … Martin Thomson