Re: [quicwg/base-drafts] Largest Reference algorithm can produce invalid values (#2112)
Bence Béky <notifications@github.com> Fri, 21 December 2018 15:48 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 0933E130E2A for <quic-issues@ietfa.amsl.com>; Fri, 21 Dec 2018 07:48:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.085
X-Spam-Level:
X-Spam-Status: No, score=-7.085 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, FROM_EXCESS_BASE64=0.979, HTML_IMAGE_ONLY_32=0.001, 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 cDH1prebczap for <quic-issues@ietfa.amsl.com>; Fri, 21 Dec 2018 07:48:23 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E458E130E3B for <quic-issues@ietf.org>; Fri, 21 Dec 2018 07:48:22 -0800 (PST)
Date: Fri, 21 Dec 2018 07:48:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545407301; bh=oVVh6BS863uoQN1lKTNsxmQ+cOLoMzgTGmsI7wBodAc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LFzNK/ibJtpW4qYxH3iLYLg/qaOXiJ9W9Wwm3q2pc0l2i/l66F9H72xut7N/kBa6y gaP+ggr4TlpzgsVaRRm6c0rrw+ZHOsd7eDaMdBc4farBDGiGzWi5z8hd2UbvL9H/i7 cY6QsoY6tdC1YpwiIWSKdaRFdm3IdMWlHb+8nW+k=
From: Bence Béky <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab78e3662f03a1598d0e3a8cb82400079dc041535c92cf000000011834cd4592a169ce17393bf8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2112/449423152@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2112@github.com>
References: <quicwg/base-drafts/issues/2112@github.com>
Subject: Re: [quicwg/base-drafts] Largest Reference algorithm can produce invalid values (#2112)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1d0b45967ed_56fc3f92144d45b4114143"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: bencebeky
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/ZJeCZSD3gqjTY8QJIz-oOXbXMew>
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: Fri, 21 Dec 2018 15:48:37 -0000
To address Martin's original concern about 0 or negative outputs, my point is that the decoding algorithm outputs a LargestReference that is the same modulo (2 * MaxEntries) as the original, and is in the same 2 * MaxEntries wide range as the original (as long as the original was valid), therefore must be the same as the original. That is, in agreement with afrind@ above, I believe that the decoding algorithm will produce valid (positive) decoded LargestReference values as long as it is fed an input wire-LargestReference that was obtained by encoding a valid LargestReference value given TotalNumberOfInserts and MaxEntries. -- 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/2112#issuecomment-449423152
- [quicwg/base-drafts] Largest Reference algorithm … Martin Thomson
- Re: [quicwg/base-drafts] Largest Reference algori… afrind
- Re: [quicwg/base-drafts] Largest Reference algori… Martin Thomson
- Re: [quicwg/base-drafts] Largest Reference algori… afrind
- Re: [quicwg/base-drafts] Largest Reference algori… Martin Thomson
- Re: [quicwg/base-drafts] Largest Reference algori… afrind
- Re: [quicwg/base-drafts] Largest Reference algori… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Largest Reference algori… afrind
- Re: [quicwg/base-drafts] Largest Reference algori… Martin Thomson
- Re: [quicwg/base-drafts] Largest Reference algori… afrind
- Re: [quicwg/base-drafts] Largest Reference algori… Martin Thomson
- Re: [quicwg/base-drafts] Largest Reference algori… Bence Béky
- Re: [quicwg/base-drafts] Largest Reference algori… Bence Béky
- Re: [quicwg/base-drafts] Largest Reference algori… Bence Béky
- Re: [quicwg/base-drafts] Largest Reference algori… afrind
- Re: [quicwg/base-drafts] Largest Reference algori… afrind