IETF Logo Mail Archive

Re: [quicwg/base-drafts] Packet numbers and sequence numbers are too easily confused (#3725)

ekr <notifications@github.com> Fri, 05 June 2020 00:25 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 4941A3A10C2 for <quic-issues@ietfa.amsl.com>; Thu, 4 Jun 2020 17:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 suvrq8aRYqVI for <quic-issues@ietfa.amsl.com>; Thu, 4 Jun 2020 17:25:31 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F30D33A10C1 for <quic-issues@ietf.org>; Thu, 4 Jun 2020 17:25:30 -0700 (PDT)
Received: from github-lowworker-5fb2734.va3-iad.github.net (github-lowworker-5fb2734.va3-iad.github.net [10.48.19.27]) by smtp.github.com (Postfix) with ESMTP id 4A5C026163E for <quic-issues@ietf.org>; Thu, 4 Jun 2020 17:25:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1591316730; bh=xUVZmHT73c9BeUwGkrPH5vfqMZEWVvR9/+lstkWMSag=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oiljliwBeM3uUTYm5EbumK/8OaqysVDWMvXVSpUp5xNiFzFroHcfl87jNnriisCQF vuk+MvZUwcXk9ueL1B6ZCmqibZFdpKUJT6LHu/ns3pfxMr50yZH/dlkctufDKkPPH5 mJ+NSYYNlO8+VxJmGw6WswEU4X0DnL9GZo+NTM4o=
Date: Thu, 04 Jun 2020 17:25:30 -0700
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZVT4OOFO5KHNGDRTF44VY7VEVBNHHCLHJD4M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3725/639188142@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3725@github.com>
References: <quicwg/base-drafts/issues/3725@github.com>
Subject: Re: [quicwg/base-drafts] Packet numbers and sequence numbers are too easily confused (#3725)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ed990fa3b86_3f33f95f42cd96c11387c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/Qn3s6l9H_F3T9n411Yy1iG-rbGE>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 05 Jun 2020 00:25:33 -0000

On Thu, Jun 4, 2020 at 4:31 PM Martin Thomson <notifications@github.com>
wrote:

> So there are three things here:
>
>    1.
>
>    The mention of sequence number in relation to CRYPTO frames is a
>    mistake. This should be "offset".
>
>
Agreed. This is just wrong.



>    1.
>
>    Packet numbers are just packet numbers. Yes, it is a sequence number,
>    but we don't use "sequence" here anywhere else, so that one instance is
>    just a mistake.
>
> Agreed. I think it's quite likely this is the result of my simultaneously
trying to submit edits to (D)TLS and QUIC.


>    1.
>
>    Sequence numbers for connection IDs. I'm not inclined to change these.
>    Using index/indices would be fine, but the risk involved in making a change
>    isn't worth it in my opinion. As this is sufficiently distinct from the TCP
>    usage, I see no real risk of confusion either.
>
> +1


-- 
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/3725#issuecomment-639188142

v2.23.0 | Report a Bug | By Email