IETF Logo Mail Archive

Re: [quicwg/base-drafts] Largest Reference isn't the right concept (#2110)

csillagasz <notifications@github.com> Wed, 26 December 2018 19:39 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 00ACE13126E for <quic-issues@ietfa.amsl.com>; Wed, 26 Dec 2018 11:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-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 PEnpUJBV9Yi3 for <quic-issues@ietfa.amsl.com>; Wed, 26 Dec 2018 11:39:39 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C692113126D for <quic-issues@ietf.org>; Wed, 26 Dec 2018 11:39:38 -0800 (PST)
Date: Wed, 26 Dec 2018 11:39:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545853177; bh=K4vcl7N3C0Ve7+oZx3KMraZ7uPZ5/4lRSC4UiPMeZyo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FDU3fu4kpx6l+TzFL/g+HTfWbkJ9HWhAAQ/C36DhKVY2OSgddoObhqfVyjc3Y2BKR mL90pFdMGeUXGl+RdSeXWmCgcu8g+RLubIiIkfVTghxGGmK3vG8nJtKB/cszPr2i+4 R3aP/SXA8P7gOMv6GuruySdDcW+0gsMRhWTg8cYU=
From: csillagasz <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab04791e5738626e9e2e19041d3d0fcf740428eeb992cf00000001183b9af992a169ce17392e66@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2110/450014755@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2110@github.com>
References: <quicwg/base-drafts/issues/2110@github.com>
Subject: Re: [quicwg/base-drafts] Largest Reference isn't the right concept (#2110)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c23d8f9a50bc_4bf93fa1fead45b46485ed"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: csillagasz
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/5xAQQb2Rx1Nz8ClfhdbqJT1dXTI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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, 26 Dec 2018 19:39:41 -0000

> @bencebeky writes:
> 
> > I enthusiastically support [...] changing absolute indexing to zero-based.
> 
> This had been discussed before. The consensus was to leave it one-based.

My impression is that this consensus was driven by the artifical constraint of Largest Reference having to be able to match the absolute index while also having a dedicated value (of zero) for no dynamic reference.  Martin's proposed change from Largest Reference to Required Insert Count removes this rather contrived constraint and allows the more natural indexing scheme of zero based indexing that matches static table indexing, the majority of developers' mental model, and the majority of implementations' innards.

-- 
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/2110#issuecomment-450014755

v2.23.0 | Report a Bug | By Email