IETF Logo Mail Archive

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

pravb <notifications@github.com> Thu, 16 November 2017 06:39 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 0D02A129471 for <quic-issues@ietfa.amsl.com>; Wed, 15 Nov 2017 22:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.616
X-Spam-Level:
X-Spam-Status: No, score=-0.616 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 RpZLjKSzvhyC for <quic-issues@ietfa.amsl.com>; Wed, 15 Nov 2017 22:39:17 -0800 (PST)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 BD0D51293E0 for <quic-issues@ietf.org>; Wed, 15 Nov 2017 22:39:17 -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=v5AFbGxOPK513oBfgtlxI0f9dmg=; b=rN2J8gPdSMyX54fc VpN2XI5DUeW/g12wEN1BCt+Ld/79tI6fKDBuQNQ6hvGMfYVQUQMgUanfbaa9Qn+g P9EfcYfWEC2+uhK4wKwzxhfTTU7/06BRuj5BS8CQ6rOKJHxfLkYcyOLmVHUyWXlS SsK8rHLfnn+7M420+X8kLC4UfsE=
Received: by filter0147p1iad2.sendgrid.net with SMTP id filter0147p1iad2-30168-5A0D3294-8 2017-11-16 06:39:16.292587747 +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 ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id cuZW2540T3eaMKbOPmgtvw for <quic-issues@ietf.org>; Thu, 16 Nov 2017 06:39:16.167 +0000 (UTC)
Date: Thu, 16 Nov 2017 06:39:16 +0000
From: pravb <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6fd376e0cb343cebe8bc267ad29b676eb19221a592cf000000011624f49492a169ce0fa74d75@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/344830311@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_5a0d3294145e5_2fe3fdf53214f2c5384f7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1ww1T44HvfiRMX5C29dES36pLU3aMZPy22kh EJwBg29H4JyYrSlMwZaGOKEeY0cRXfZ0hqyImEk4RoDQtngThKuMyzHUdyNeBTMMvE+P8dLR6mt3t1 Fkv6D+U0CbqzHge9X9/Jg5ft3jrBRSY2R8eCd/BpAcqrUD+bhB+DM3+Qdw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/QH6ZQWu5hBQtYrWz0eMbskSYjJ4>
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:39:19 -0000

Let's explicitly disallow wraparound then with the recognition that we then put a limit on the amount of data a QUIC connection can transfer whereas there is no such limit in TCP. I think if a received packet causes a change in the connection state machine then we don't need a Boolean or stats counter to detect this and we do not need any sentinel values. Also I can't think of any other use cases for sentinel values so if anyone else has any ideas please speak out soon.

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

v2.46.0 | Report a Bug | By Email | System Status