Re: [quicwg/base-drafts] Variable-length integers (#595)
MikkelFJ <notifications@github.com> Tue, 17 October 2017 01:30 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5267313295C for <quic-issues@ietfa.amsl.com>; Mon, 16 Oct 2017 18:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zobmsArq8Z6L for <quic-issues@ietfa.amsl.com>; Mon, 16 Oct 2017 18:30:07 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0960C133018 for <quic-issues@ietf.org>; Mon, 16 Oct 2017 18:30:07 -0700 (PDT)
Date: Mon, 16 Oct 2017 18:30:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1508203806; bh=CSysxWzv6Qj39lqNoi+qVfJiqZABug8XmzuTcL/j6Bk=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oCZ9EnFHMqEQ1eeqqkaJG3UyAbAPyuURLpieAff5tamFjdijHtawMjKG3LCBWbNy3 reJT9L6e86vTLmWL3zZ2aCjHDMh4BfdwotTIiTDP8SA8gQtkhC4LQ4gbp7sIAWnKTJ pEu5x568oMGVKo2JsuFqx7/Jg8UfgSjhtaiY+P/4=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba99e70d903a732575e66343cdde3832eb4b7f00692cf0000000115fd1f1e92a169ce0df0ef15@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/595/337090566@github.com>
In-Reply-To: <quicwg/base-drafts/issues/595@github.com>
References: <quicwg/base-drafts/issues/595@github.com>
Subject: Re: [quicwg/base-drafts] Variable-length integers (#595)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59e55d1e3d927_58433fe675702f38196f4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pb-RgqWNhCCnCEhe295z3lSbgK4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Oct 2017 01:30:08 -0000
I agree with Ian - there are complexities with going with a length based solution when dealing with optional sub-frames so as is, I prefer any solution that is not length based. But it is not unhead of to have a length based solution where each subframe exists if the length is longer than most recently parsed subframe, but obviously that necessitates a termination of that subframe. Thus, each subframe typically has its own length. One of the IoT protocols do this, perhaps it is MQTT. However, it is likely to consume more space. In isolation, it is also not a good idea to add a length based solution. If it is done, all other frames ought to be revisited, which would be some additional work to ensure the length can be understood without understanding the full frame. I would generally like to see a solution where a frame could be skipped by just reading its header as opposed to requiring a full stream parser. It forces implementations to separate parsing from actions which may be architecturally nice, but introduces temporary data structures to handle the parse output. But, it will likely consume more space overall. -- 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/595#issuecomment-337090566
- [quicwg/base-drafts] Replace variable length fiel… ekr
- Re: [quicwg/base-drafts] Replace variable length … MikkelFJ
- Re: [quicwg/base-drafts] Variable-length integers… ianswett
- Re: [quicwg/base-drafts] Variable-length integers… Martin Thomson
- Re: [quicwg/base-drafts] Variable-length integers… MikkelFJ
- Re: [quicwg/base-drafts] Variable-length integers… Mike Bishop