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 52A67128DF3
 for <quic-issues@ietfa.amsl.com>; Tue, 20 Jun 2017 00:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.396
X-Spam-Level: 
X-Spam-Status: No, score=-8.396 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.8, 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 H7ATKfTpYtBl for <quic-issues@ietfa.amsl.com>;
 Tue, 20 Jun 2017 00:17:35 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net
 (github-smtp2-ext2.iad.github.net [192.30.252.193])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 9C69C1287A3
 for <quic-issues@ietf.org>; Tue, 20 Jun 2017 00:17:35 -0700 (PDT)
Date: Tue, 20 Jun 2017 00:17:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1497943054;
 bh=ugVxxkEW4MnPv/e6I8lE7mqjj+X5twgL5UAkhIf6tIA=;
 h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=j5N1dDl2ImssmQQvZuaV0Rh2Ht2XC494pNQqFTdynvtYcTRnbm832PNgxRzZX0WtW
 74gNXYLFq+jv/Ut/0T1Su+XvXg3uGeuSlxnoy1RiP96crD+1tdpCYEIYty9uGlEzyJ
 tK4YfwHdMZIBLnIeySAmZhIIVHQq23gAbF8AANtM=
From: Patrick McManus <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab89a38ee4b902a535db5f16c1d1e47f36d9fe238492cf0000000115608e0e92a169ce0df59194@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/309666359@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_5948cc0eb9abf_2c8e3f7ee1c7fc3c9737b";
 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/bfpAHhzjJq-yZAqjFZKSIegprFg>
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 07:17:37 -0000


----==_mimepart_5948cc0eb9abf_2c8e3f7ee1c7fc3c9737b
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

yes; you can be semi-blocked from sending by the range of the lowest unacked packet you have outstanding.

I say semi-blocked (as opposed to say, deadlocked) because you can just move to the bigger packet number space and essentially declare the older uacked ones presumed-lost. They'll fail decryption at the receiver when given the 'wrong' packet number.

8 bit numbers  aren't especially useful.. perhaps banning them as footguns would be a practical step to help quality of implementations.


-- 
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-309666359
----==_mimepart_5948cc0eb9abf_2c8e3f7ee1c7fc3c9737b
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>yes; you can be semi-blocked from sending by the range of the lowest u=
nacked packet you have outstanding.</p>
<p>I say semi-blocked (as opposed to say, deadlocked) because you can jus=
t move to the bigger packet number space and essentially declare the olde=
r uacked ones presumed-lost. They'll fail decryption at the receiver when=
 given the 'wrong' packet number.</p>
<p>8 bit numbers  aren't especially useful.. perhaps banning them as foot=
guns would be a practical step to help quality of implementations.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/605#issuecomment-309666359">view it on GitHub</a>, =
or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq8Lf9=
XyUeVPFheZPHlckv4kgqqFCks5sF3IOgaJpZM4Nypwu">mute the thread</a>.<img alt=
=3D"" height=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq-p=
GnGswF4_rjn7exd2bN2RVfAOAks5sF3IOgaJpZM4Nypwu.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewActi=
on">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/is=
sues/605#issuecomment-309666359"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></me=
ta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6=
-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubuserconte=
nt.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","=
action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dr=
afts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mcmanus in #6=
05: yes; you can be semi-blocked from sending by the range of the lowest =
unacked packet you have outstanding.\r\n\r\nI say semi-blocked (as oppose=
d to say, deadlocked) because you can just move to the bigger packet numb=
er space and essentially declare the older uacked ones presumed-lost. The=
y'll fail decryption at the receiver when given the 'wrong' packet number=
.\r\n\r\n8 bit numbers  aren't especially useful.. perhaps banning them a=
s footguns would be a practical step to help quality of implementations.\=
r\n"}],"action":{"name":"View Issue","url":"https://github.com/quicwg/bas=
e-drafts/issues/605#issuecomment-309666359"}}}</script>=

----==_mimepart_5948cc0eb9abf_2c8e3f7ee1c7fc3c9737b--

