[quicwg/base-drafts] Unnecessary packet number expectations in ACK frame description (#3310)

Dmitri Tikhonov <notifications@github.com> Fri, 27 December 2019 15:44 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 0CA9A120026 for <quic-issues@ietfa.amsl.com>; Fri, 27 Dec 2019 07:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 FhaI1kLOZTdv for <quic-issues@ietfa.amsl.com>; Fri, 27 Dec 2019 07:44:30 -0800 (PST)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CBCA12004A for <quic-issues@ietf.org>; Fri, 27 Dec 2019 07:44:30 -0800 (PST)
Received: from github-lowworker-39ac79b.ac4-iad.github.net (github-lowworker-39ac79b.ac4-iad.github.net [10.52.18.15]) by smtp.github.com (Postfix) with ESMTP id AEBD36A03B5 for <quic-issues@ietf.org>; Fri, 27 Dec 2019 07:44:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1577461469; bh=ngkdvAP0+6MPEWNfcTaHhSutOoBJ3HTkkerkXhIRnLk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XQ63Dr9ETER05p4F9fhpeUugVrBvecmORjXfDrSAokUbK1BOwIgUT8wep1+7eKlyS 3DzCaNbeJiusPqeehxTvzqXdkVSmR8bu1UMYf+1geB7UDp6cjpQk8L4vjIYqu9q3Gc wCJ5ElA86Il5KmVSx5puXBXznDAN0a9w3Ry3WSBU=
Date: Fri, 27 Dec 2019 07:44:29 -0800
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK44SDIL5MDFJEHA6YN4CNMV3EVBNHHCAXBUGE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3310@github.com>
Subject: [quicwg/base-drafts] Unnecessary packet number expectations in ACK frame description (#3310)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e0626dd9fbf8_7d813f9b11ccd96861053e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
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/gFOK0NkGnh807a4B-nf5hwoLTtc>
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, 27 Dec 2019 15:44:32 -0000

The [Transport Draft](https://tools.ietf.org/html/draft-ietf-quic-transport-24#section-19.3) contains the following paragraph:

```
   It is expected that a sender will reuse the same packet number across
   different packet number spaces.  ACK frames only acknowledge the
   packet numbers that were transmitted by the sender in the same packet
   number space of the packet that the ACK was received in.
```

I see a few problems with the first sentence:
1. As written, it does not make sense.
1. There is no mention of packet number reuse expectations across packet number spaces in [Section 12.3](https://tools.ietf.org/html/draft-ietf-quic-transport-24#section-12.3).
1. The connection between it and the sentence that follows is not clear.

I propose that the first sentence simply be dropped.

-- 
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/3310