IETF Logo Mail Archive

[quicwg/base-drafts] Allow server to enforce port-Retry packet numbering (#3989)

Dmitri Tikhonov <notifications@github.com> Mon, 10 August 2020 12:29 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 62E163A1529 for <quic-issues@ietfa.amsl.com>; Mon, 10 Aug 2020 05:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level:
X-Spam-Status: No, score=-1.554 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 H7J138WDeWaw for <quic-issues@ietfa.amsl.com>; Mon, 10 Aug 2020 05:29:56 -0700 (PDT)
Received: from out-27.smtp.github.com (out-27.smtp.github.com [192.30.252.210]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B7D33A0DD8 for <quic-issues@ietf.org>; Mon, 10 Aug 2020 05:29:55 -0700 (PDT)
Received: from github-lowworker-d31a065.va3-iad.github.net (github-lowworker-d31a065.va3-iad.github.net [10.48.17.70]) by smtp.github.com (Postfix) with ESMTP id C2FEB900051 for <quic-issues@ietf.org>; Mon, 10 Aug 2020 05:29:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1597062594; bh=AJ3OmD7KiBZmWRECYIA7Tx2PvcSRVbzdqP/HysJ8QZM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=xxfNplBrBhq7PP7kXTmOBddDms/a99dmBlQml/G6dg2BHjwyCML98cIDt4bpczVfp 4YAomUqZQtW4MyA/MrNyvs0u7dGn0uA+LdGjhD2EJseY3tETeMxlBJx8CL8AtLs61x yPjC35HbvHlvIafCxshAKASZb0WEjNcDv4VSyXrw=
Date: Mon, 10 Aug 2020 05:29:54 -0700
From: Dmitri Tikhonov <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7KMJ7R7AVLEM633G55HUPMFEVBNHHCQTDTBE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3989@github.com>
Subject: [quicwg/base-drafts] Allow server to enforce port-Retry packet numbering (#3989)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f313dc2b2078_694416f85869"; 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/StbGso-BifQT4jEND3fLdPvb_Ks>
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: Mon, 10 Aug 2020 12:29:57 -0000

_(I first raised this issue on the [mailing list](https://mailarchive.ietf.org/arch/msg/quic/D59v8K4Zem5Kb2zjQWyKsA_v1eI/).)_

There is the following `MUST NOT` in the transport draft:

```
   A client MUST NOT reset the packet number for any packet number space
   after processing a Retry packet; Section 17.2.3 contains more
   information on this.
```

We should allow the server to abort the connection the the client violates this `MUST NOT`.  The server can do so by including the packet number into the Retry token and comparing against it when the client sends packets that carry the token.

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

v2.23.0 | Report a Bug | By Email