Re: [quicwg/base-drafts] Wrongly hinting of issues not existing for packet number size increase (#605)
MikkelFJ <notifications@github.com> Tue, 20 June 2017 12:45 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 42E9E12EAC6 for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 05:45:35 -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 lGKYchZ2V6gn for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 05:45:33 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BC3612EAAB for <quic-issues@ietf.org>; Tue, 20 Jun 2017 05:45:33 -0700 (PDT)
Date: Tue, 20 Jun 2017 05:45:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497962732; bh=eLWSO2wBzztV8TDkojJDc01YGHbMKR3E7eHdhC8oZs0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iYFfYC/TcyEmPuLj6xazg2MhmNV/RW3TTP/eaZUAE2hbakPdxiRaGxvZZYp1udk9u dOmsBJcH2QiPF/xOND4BlrjajBUGGKYphVVK9NaYeZqXVwCmyGbYRrJ/b0dPyYeUah AIh1gm8hlaszDE7ArZT4y07I1YyPqIIpmiGkZXA4=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe9472041f1c78603b73e0617c8ab21fe04d16e4f92cf000000011560daec92a169ce0df59194@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/605/309741686@github.com>
In-Reply-To: <quicwg/base-drafts/issues/605@github.com>
References: <quicwg/base-drafts/issues/605@github.com>
Subject: Re: [quicwg/base-drafts] Wrongly hinting of issues not existing for packet number size increase (#605)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_594918ec991eb_61953fc8da5b7c2c58212"; 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/b3en-b1ulVy5WjgYkmy7P-VRSXw>
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, 20 Jun 2017 12:45:35 -0000
> Maybe I'm misunderstanding you. Or may be the opposite - I thought you would introduce a gap in the packet number space while advancing the larger range, but that no longer makes sense to me. Either way, I'm not sure there is a problem: If you send 100 packets in 8-bit encoding, then decide to send 100000 packets more, you encode 8 bit until packet 127, use 16 bit until packet 32767, and 32 bit after that. Regardless of delivery order, there shouldn't be any ambiguity about the packer number. But this isn't exactly how things are specified currently - it uses a diff against largest received or something like that. If the spec would state that only half the representable range must be used for any given encoding, except for 64 bit, then I think it should be working. Simpler yet, use varlen. -- 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/605#issuecomment-309741686
- Re: [quicwg/base-drafts] Transport: Wrongly hinti… MikkelFJ
- [quicwg/base-drafts] Transport: Wrongly hinting o… Magnus Westerlund
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Martin Thomson
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Patrick McManus
- Re: [quicwg/base-drafts] Wrongly hinting of issue… MikkelFJ
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Patrick McManus
- Re: [quicwg/base-drafts] Wrongly hinting of issue… MikkelFJ
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Magnus Westerlund
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Magnus Westerlund
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Magnus Westerlund
- Re: [quicwg/base-drafts] Wrongly hinting of issue… ianswett
- Re: [quicwg/base-drafts] Wrongly hinting of issue… ianswett
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Magnus Westerlund
- Re: [quicwg/base-drafts] Wrongly hinting of issue… ianswett
- Re: [quicwg/base-drafts] Wrongly hinting of issue… Martin Thomson