Re: [quicwg/base-drafts] [Version Ossification] Alternative version and Initial Salt should be part of NEW_TOKEN (#3111)

Kazuho Oku <> Tue, 22 October 2019 02:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8DDC7120AEA for <>; Mon, 21 Oct 2019 19:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_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 MtujRXN4Dsvw for <>; Mon, 21 Oct 2019 19:20:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B983C120AE7 for <>; Mon, 21 Oct 2019 19:20:41 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F2758C605FD for <>; Mon, 21 Oct 2019 19:20:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571710840; bh=aIcjHWAmk/pkIyOX7YHie7lX5I3158mmsIxsWAJm6IE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qUrFWTPElm95605FMCVOp643HoY9C0wTLr+I6F1umxpc+A+kKgE6V4IyAU1r/daGn xVOrmLHf7HoBKiGabxrQDuOpb5c9cmL8E4XPKZCQaOc5d5cjvL1gDMPDxHsBwUVUcv 1MvuxQlUlfFRNNQAcge4htdPysWAggCg+7Xyt0kU=
Date: Mon, 21 Oct 2019 19:20:40 -0700
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3111/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] [Version Ossification] Alternative version and Initial Salt should be part of NEW_TOKEN (#3111)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dae6778e31c7_2b1c3fc7d12cd96c281b8"; 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: Tue, 22 Oct 2019 02:20:43 -0000

> Aren't clients required to store transport parameters when doing resumption already, so this is moving it from one place they store to another?

That's a good point. I admit that the only one benefit of bundling the alternative version-salt is that the server can store and recover that from the token. That said, please let me reiterate that that is a huge benefit, as it provides the servers the capability of protecting the Initial packets from on-path intermediary in a cryptographically secure way.

Regarding if the alternative fields should be a mandatory field of a NEW_TOKEN frame, I think it's just about a matter of encoding. As I have stated in, a server that is not willing to do greasing (or Initial protection) can advertise version 1 and the Initial salt of version 1 in those fields.

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