Re: [quicwg/base-drafts] don't allow 0 as a packet number (#832)

MikkelFJ <notifications@github.com> Thu, 16 November 2017 08:07 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 080C6129571 for <quic-issues@ietfa.amsl.com>; Thu, 16 Nov 2017 00:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level:
X-Spam-Status: No, score=-3.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_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 gqQ44ymBA7ZT for <quic-issues@ietfa.amsl.com>; Thu, 16 Nov 2017 00:07:44 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 323EC120724 for <quic-issues@ietf.org>; Thu, 16 Nov 2017 00:07:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=WylrGA8pLzIuhYfFtsucIN8fkpo=; b=sjwPARdoF4eseKYP dEX7tIe3c7s1H7jdccoTy7Zzv+egeciVIlRVpgedmYYh7BnUQhyssmBDFP+NL6b0 DFnkV9lqoHV+JePXqUlOCL5hm0Oj8xvDZwaxEYVdBmba4wvid6UWz21LlRPL0Z7z kFeoc5b4xE83Tk+xjXpYt5kVbUY=
Received: by filter0470p1iad2.sendgrid.net with SMTP id filter0470p1iad2-26932-5A0D474F-6 2017-11-16 08:07:43.227808171 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id pikWpcZIT0iyOESD7uIrKw for <quic-issues@ietf.org>; Thu, 16 Nov 2017 08:07:42.897 +0000 (UTC)
Date: Thu, 16 Nov 2017 08:07:43 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab059fa9780ef9e4622247367810edf8d4de858f3a92cf000000011625094e92a169ce0fa74d75@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/832/344845807@github.com>
In-Reply-To: <quicwg/base-drafts/issues/832@github.com>
References: <quicwg/base-drafts/issues/832@github.com>
Subject: Re: [quicwg/base-drafts] don't allow 0 as a packet number (#832)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a0d474eb8072_1425b3ffcde508f281435159"; 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
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1E3wQyiH9Y2IS1aOo3F9io/SHYui28xTgPNV aVEq0Dg2Et/3WdRenaxBNPYpmFgHEb51FDll5r1aZYLljZbPVq/lf+i+B4IvQvDQbULKSc3JAHuIbQ I89DzuAZYHUH38DTJvl2ppa3a2j/99R3oR3KipLcqt/0APR4iq15BLLS+aPw87elHnuzJXKt9A8U4w 8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/z8xRmKsP5B1SmPjsryaEqfy8vfU>
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: Thu, 16 Nov 2017 08:07:46 -0000

In the context of connection migration I just sent a mail to the QUIC WG list suggesting to avoid gaps such that the packer numbers cannot effectively be exhausted. One option is to encode/encrypt packet numbers, the other was to reset packet numbers during migration. Encoding would deal with ossification issues. Randomizing early would work against keeping the packet number space large, though not as much as for migrations since it is a one off.

-- 
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/832#issuecomment-344845807