Re: [quicwg/base-drafts] Wrongly hinting of issues not existing for packet number size increase (#605)

Patrick McManus <notifications@github.com> Tue, 20 June 2017 12:24 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 2B28C12E059 for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 05:24:42 -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 CIt728weHMJR for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 05:24:40 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3020A12E056 for <quic-issues@ietf.org>; Tue, 20 Jun 2017 05:24:40 -0700 (PDT)
Date: Tue, 20 Jun 2017 05:24:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1497961479; bh=Ydu1welMy3A1qjsaJgcSnFTFgM+cwxGEK9RsTA5X+Bg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=adh/s5RpdAY7ubY5GBVqSeGuUdJJuQD9o/OkN1Z9jqloiHB8m+bUuijyEZyl3gpC/ jmiaYENGQvSrMgkXW6gEvR7Ie/NE6aJehcnHP+xcgxO0V5qODNVcPZGxB0DJWz4Rf8 gwbIsAgLjz4PHd5uR2tnmNsF5dZpx/dqHequikG4=
From: Patrick McManus <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab49a2ec4b4d119eafcfd56d0bc2b86d84a9720b0992cf000000011560d60792a169ce0df59194@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/309736878@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_594914075f64b_54853f8afddb1c2c594bb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mcmanus
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/kpNkteKC_0CCRu4bXMB4aBy6ubM>
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:24:42 -0000

I don't think gapless creates a problem with the existing spec (though I also support #595). Maybe I'm misunderstanding you.

Gap is a property of the sender, and there would be no gap just by virtue of moving to a bigger encoding - that's obvious to the receiver if the packets are delivered in order but its true whether the receiver realizes it or not.  So out of order delivery would basically just be a form of loss/corruption (the misinterpreted number would cause a decrypt fail) fixed in the usual way (retransmit of data). 

To me, the most important part of this issue is that the current design is prone to this self-induced loss and while not a critical fail, it should be improved.

-- 
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-309736878