IETF Logo Mail Archive

Re: [quicwg/base-drafts] Consider making long header payload length 16bits (#1577)

Nick Banks <notifications@github.com> Wed, 18 July 2018 21:35 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 24DF0130E13 for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 14:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 UZ9zV51hh5bU for <quic-issues@ietfa.amsl.com>; Wed, 18 Jul 2018 14:35:12 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41918131066 for <quic-issues@ietf.org>; Wed, 18 Jul 2018 14:35:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=3cTF7GCrldBvd4TbGZD0/zFYGeE=; b=EiaIg12vyRsfZW+R k25l60Q+1cApnTtj4aGe1MZt8UatnJrZM3PKC7A+dGMY3YTDLsv8n7gi0uIJ0sbQ 7Ai41f9NGtOmY4MftOdjHmI18RmhNLGCHiHKn1uzi1HX5pM5wFe0Mpo43lr09YK7 d4Io+VSbyUtoq85U7saw5zuOg3Q=
Received: by filter0348p1iad2.sendgrid.net with SMTP id filter0348p1iad2-28288-5B4FB28E-C 2018-07-18 21:35:10.834971946 +0000 UTC m=+80975.965673226
Received: from github-lowworker-4f62d42.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id lHf0SJU8SASRo-gGtzPisg for <quic-issues@ietf.org>; Wed, 18 Jul 2018 21:35:10.765 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-4f62d42.cp1-iad.github.net (Postfix) with ESMTP id B8203C0EAE for <quic-issues@ietf.org>; Wed, 18 Jul 2018 14:35:10 -0700 (PDT)
Date: Wed, 18 Jul 2018 21:35:11 +0000
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4cf77ae5f0d1540ecc05020e46505fd4bc8aefda92cf000000011767748e92a169ce146220ed@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1577/406081808@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1577@github.com>
References: <quicwg/base-drafts/issues/1577@github.com>
Subject: Re: [quicwg/base-drafts] Consider making long header payload length 16bits (#1577)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b4fb28eb5df1_69373fda07cccf60532314"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2KIULJ5qtKLBPgQHRJL7o2f4Od+E/xE1HO2+ 7q3C6IAmvGaHBrxoi/JtPNVbmg57lDRHaWwpv1vSlxKQYdqTktWA69MzLYLPzeBNdPTXVcmgGyWA9z d3xlJvR/SLsvnAACnNF4h4HBtBaUeVAJ/5Rx1KM1EaIY+J4OBZZAC0kClUHbndX7YJBNewmqtsSV5f U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hrEcabFYpPRMv7dRaJd6Qt5muYo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 18 Jul 2018 21:35:15 -0000

Actually, @dtikhonov I think the expressible range maybe the biggest non-bikeshed reason to use a 2-byte field. Everyone is always using 2 bytes because they build up the contents first (because they don't know the final length upfront) and then go back and fill in those two bytes they preallocated essentially. But if a complete solution wants to support maximum 64K UDP payload sizes, that logic gets a lot more complicated. Either they always preallocate 4 bytes or they have to precalculate the size, which is hard enough that nearly all implementations don't do that already.

-- 
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/1577#issuecomment-406081808

v2.43.4 | Report a Bug | By Email | System Status