Re: [quicwg/base-drafts] Mandate the use of short header for stateless reset (#2600)

Kazuho Oku <> Wed, 10 April 2019 05:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8390212025E for <>; Tue, 9 Apr 2019 22:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mEkzby49RMlz for <>; Tue, 9 Apr 2019 22:08:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E2D6A12015B for <>; Tue, 9 Apr 2019 22:08:14 -0700 (PDT)
Date: Tue, 09 Apr 2019 22:08:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1554872893; bh=5eYXu0TAuaQ0ZOiqAXczLwEglEaYKO0GTV1MQzp+VmE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=C6dTuy28vvTWiKpwLx1VKJe9ordNF3aLf+uRjuKUlKpbNFwC8ndl/KU4rGwX+T4dG GElTTwLPWntd/4t+FvuifDu+iSYwTlXGl+Ki0eYGjISv1tL+kMXgisPu61VlGR5tN3 nZOZyigCvNM1enZwGApvlCqHYrUgnt73EGHLBS2Y=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2600/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Mandate the use of short header for stateless reset (#2600)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cad7a3d998c5_66b83f88bced45c01091d4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Apr 2019 05:08:16 -0000

kazuho commented on this pull request.

> @@ -2391,13 +2391,17 @@ the packet other than the last 16 bytes for carrying data.
 ### Detecting a Stateless Reset
-An endpoint detects a potential stateless reset when a incoming packet
-with a short header either cannot be associated with a connection,
-cannot be decrypted, or is marked as a duplicate packet.  The endpoint
-then compares the last 16 bytes of the packet with the Stateless Reset
-Token provided by its peer, either in a NEW_CONNECTION_ID frame or
-the server's transport parameters.  If these values are identical,
-the endpoint MUST enter the draining period and not send any further
+An endpoint detects a potential stateless reset when an incoming packet either
+cannot be associated with a connection, cannot be decrypted, or is marked as a
+duplicate packet.  The endpoint MUST then compare the last 16 bytes of the

I think that this can be a MUST, based on the understanding that processing of stateless resets sent by the peer is an option. Or are we requiring every endpoint to detect and handle stateless resets?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: