Re: [quicwg/base-drafts] token-based greasing / initial packet protection (#3166)

Kazuho Oku <> Thu, 31 October 2019 09:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7D46F120887 for <>; Thu, 31 Oct 2019 02:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sdox1YMj-zG8 for <>; Thu, 31 Oct 2019 02:07:54 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E3A3012021C for <>; Thu, 31 Oct 2019 02:07:53 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 418E2C60615 for <>; Thu, 31 Oct 2019 02:07:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572512873; bh=0GaKimTS29zMmb/TKK53/k1HXKsI17I2ek0FVA0BY38=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YmFyeVcTQRpoFtwYNiS3DeDI9T4D2GfYppF4D/BSixEjxuYBjT8alBonWLANODik4 QM85hRT8bnLmA8qUyH6hQWpIycw0soIGYXHLggkIxeDJjJaK6R+okeG8SkWKkpZa4/ KJKj7+XDcw46bfw6AW0GOpKMQILA7nqeerebYKlI=
Date: Thu, 31 Oct 2019 02:07:53 -0700
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3166/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] token-based greasing / initial packet protection (#3166)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dbaa469335de_11623f8aa98cd96c1756547"; 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: Thu, 31 Oct 2019 09:07:56 -0000

kazuho commented on this pull request.

> +values as their seeds.
+## Server Behavior
+Typically, a server that advertises the alternative seeds would act in the
+following steps:
+* The server pre-allocates a set of unused version numbers as the alternative
+  version numbers, associating each of those version numbers with a packet type
+  modifier chosen at random.
+* When issuing a NEW_TOKEN token, the server generates the alternative initial
+  salt by calling a pseudo-random function.  Then it builds a token that
+  embeds the alternative seeds including the initial salt being generated.  The
+  token will be encrypted using a key known only to the server, thereby

Thank you for the suggestions. All the proposed editorial changes made sense except this one, I've applied them.

Regarding this suggestion, I think we do not need to be general here, as this is about how a "typical server" would behave.

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