Re: [quicwg/base-drafts] don't allow 0 as a packet number (#832)
Ryan Hamilton <notifications@github.com> Wed, 04 October 2017 15:19 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 C4943132C2A for <quic-issues@ietfa.amsl.com>; Wed, 4 Oct 2017 08:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.799
X-Spam-Level:
X-Spam-Status: No, score=-9.799 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 K3csZMzOTUK7 for <quic-issues@ietfa.amsl.com>; Wed, 4 Oct 2017 08:19:26 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CD65133211 for <quic-issues@ietf.org>; Wed, 4 Oct 2017 08:19:25 -0700 (PDT)
Date: Wed, 04 Oct 2017 08:19:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1507130365; bh=6NXKVqyDT79WqTs/sYcIKid9A2FLX4SpFDYOqqEbcGQ=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sAFZDJ5SSBLK8kwvOHW0c9cHG0m1fXDOebaB7z5OEEPAu8mG34XhE95e1tfIjw8+f Chc984abdlheFH93YrARIXfbbuKE7CiMJbm9vHh8tm3ROkcRC0TizBN1bbN/tCVoj/ K6g4McBbTS+XvrmiMg1ArBxdWviJtjFTcXOStqhs=
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe40a32faeb12bbd15fe7818ba2780b9d74c9e9ab92cf0000000115ecbdfd92a169ce0fa74d75@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/334191017@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_59d4fbfd359ec_41f43fbd9d3a0f30643aa"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
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/kPto_uzHjFAtaMi5K1jewYpzVwY>
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: Wed, 04 Oct 2017 15:19:29 -0000
I also completely agree with the idea that 0 is an invalid packet number to simplify tracking. On Wed, Oct 4, 2017 at 7:31 AM, ekr <notifications@github.com> wrote: > I agree with @nibanks, but it's worth noting that it's also easy to produce > a value that is nonzero: > > 33s | <30 random bits> | 1 > > > > On Wed, Oct 4, 2017 at 7:09 AM, Nick Banks <notifications@github.com> > wrote: > > > If we really must have an invalid packet number I would also prefer > > 2^64-1, as that would never be initialized to, since we use 32 random > bits, > > and we would essentially limit the maximum number allowed by 1. Really, > no > > additional logic required. > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > <https://github.com/quicwg/base-drafts/issues/832#issuecomment-334167698 > >, > > or mute the thread > > <https://github.com/notifications/unsubscribe- > auth/ABD1oSeL0dqALA_JqDmJwi_ENpQVdeCSks5so5GwgaJpZM4Ps6XH> > > > . > > > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/quicwg/base-drafts/issues/832#issuecomment-334174957>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ASp6yqdPSz1aDBWc_ubmNZSfdeexSA7Jks5so5bVgaJpZM4Ps6XH> > . > -- 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-334191017
- [quicwg/base-drafts] don't allow 0 as a packet nu… Marten Seemann
- Re: [quicwg/base-drafts] don't allow 0 as a packe… MikkelFJ
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Nick Banks
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Marten Seemann
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Nick Banks
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Marten Seemann
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Nick Banks
- Re: [quicwg/base-drafts] don't allow 0 as a packe… ianswett
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Nick Banks
- Re: [quicwg/base-drafts] don't allow 0 as a packe… ekr
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Ryan Hamilton
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar
- Re: [quicwg/base-drafts] don't allow 0 as a packe… pravb
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Ryan Hamilton
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Martin Thomson
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Patrick McManus
- Re: [quicwg/base-drafts] don't allow 0 as a packe… MikkelFJ
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Lars Eggert
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Martin Thomson
- Re: [quicwg/base-drafts] don't allow 0 as a packe… MikkelFJ
- Re: [quicwg/base-drafts] don't allow 0 as a packe… MikkelFJ
- Re: [quicwg/base-drafts] don't allow 0 as a packe… ekr
- Re: [quicwg/base-drafts] don't allow 0 as a packe… MikkelFJ
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Lars Eggert
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar
- Re: [quicwg/base-drafts] don't allow 0 as a packe… pravb
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar
- Re: [quicwg/base-drafts] don't allow 0 as a packe… MikkelFJ
- Re: [quicwg/base-drafts] don't allow 0 as a packe… Martin Thomson
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar
- Re: [quicwg/base-drafts] don't allow 0 as a packe… janaiyengar