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

janaiyengar <notifications@github.com> Thu, 16 November 2017 06:51 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 ED0421294E8 for <quic-issues@ietfa.amsl.com>; Wed, 15 Nov 2017 22:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.182
X-Spam-Level:
X-Spam-Status: No, score=-3.182 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_24=1.618, 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 aotxa11OeUyI for <quic-issues@ietfa.amsl.com>; Wed, 15 Nov 2017 22:51:06 -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 483F21293E0 for <quic-issues@ietf.org>; Wed, 15 Nov 2017 22:51:06 -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=bn2BVkInNvLnCiv7kWS6IUP/kIk=; b=fknXpwN+j84k8Hrn x+eF205AZY93TICSJm64n/BeoDLoPbWZC+VAcJOwwbGxt1qRzRhifaoBEX2pJztW DrjjP6vjLPAnWzRylYdcypqQlR6rvH942E6HH9eKTAIIusn4CSZZ3uOiPRdw9ljr s3KKrqdUocqZI1flOp/+UTxxlw8=
Received: by filter0498p1iad2.sendgrid.net with SMTP id filter0498p1iad2-5358-5A0D3559-8 2017-11-16 06:51:05.292499446 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1iad2.sendgrid.net (SG) with ESMTP id 5keguHsyRRCxlAyiL2ee7w for <quic-issues@ietf.org>; Thu, 16 Nov 2017 06:51:05.219 +0000 (UTC)
Date: Thu, 16 Nov 2017 06:51:05 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abdf16f7038514767c4a7faf3d93f2f0a1bb3dbe5992cf000000011624f75992a169ce0fa74d75@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/344832127@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_5a0d355934332_339f3fbc6278af389110f2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0iwzqDJNo4y63oknP3Prd212sTrl3A4hjkhV jIMY7vsnsvKgPOdiLFLtvz60JitSMv72HlJP626IT5CG3Th9eOkWGUTLeiqBFMZXF2/5W5ac7MYAtj QcE+tKR1zvLtVQPk1KJIX0n6RuChcwcWxQQSYnW24z1LQHWI1unPYErOy1ckDlR01CKujLIF2OZFAn o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/28Vgm6r4HgXRMM6KOwS4SIrJWdU>
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 06:51:09 -0000

Thinking about this a bit more and chatting with @ianswett, not randomizing will risk ossification of the initial packet number.  I'm wondering if it's valuable to randomize anyways, just to avoid issues, and in the interest of making more fields unpredictable. Thoughts?

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