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

Robin Marx <> Tue, 29 October 2019 13:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 425CA12080C for <>; Tue, 29 Oct 2019 06:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wrszuH7N-Q3F for <>; Tue, 29 Oct 2019 06:17:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BDB97120801 for <>; Tue, 29 Oct 2019 06:17:07 -0700 (PDT)
Date: Tue, 29 Oct 2019 06:17:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572355026; bh=kJuMslyNx6nluZlBMaiGg664qeiTyOWFnSTqSokSaUU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OlpYXSve8CKC3EqJmCxsNqzYyrrcOuGG/B714+wss6yxtcVJAL0I1se25lzLJDcJd OpngpWECIWaVXwbz4fMpQKHv0hAnd0k5pK5UkqLPNMihculWwUEBACRlyFQQpzVcIf MhFMq/DVS0mQ6H1pvp97AX+RdI2vXtHgre1snS3w=
From: Robin Marx <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3115/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Don't use bitmap frames to describe varint structures (#3115)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db83bd293e26_7d593fb4b40cd96c55336"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rmarx
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Oct 2019 13:17:09 -0000

> Yeah sorry I should have recognised you were providing a simple example not the whole shebang. I will point out that this format begins to resemble @rmarx qlog definition in TypeScript notation. If we really did want to change things, he'd probably be interested in aligning them if possible.

For what it's worth, @nharper's example would look a bit like this in TypeScript notation:

class StreamFrame implements Frame {
 data:Array<byte> = new Array<byte>(length);

interface GenericFrame {

interface Packet {

I've been using this in qlog mainly for convenience but am willing to move to another format down the line if qlog actually gets adopted and this type of flexible format is used in other QUIC drafts. 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: