IETF Logo Mail Archive

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

ianswett <notifications@github.com> Tue, 22 October 2019 02:12 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 C75A3120AE6 for <quic-issues@ietfa.amsl.com>; Mon, 21 Oct 2019 19:12:20 -0700 (PDT)
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 6Itm-Hi56LoE for <quic-issues@ietfa.amsl.com>; Mon, 21 Oct 2019 19:12:19 -0700 (PDT)
Received: from out-10.smtp.github.com (out-10.smtp.github.com [192.30.254.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82973120AE2 for <quic-issues@ietf.org>; Mon, 21 Oct 2019 19:12:19 -0700 (PDT)
Received: from github-lowworker-f045d1f.ac4-iad.github.net (github-lowworker-f045d1f.ac4-iad.github.net [10.52.19.54]) by smtp.github.com (Postfix) with ESMTP id 025F61210F0 for <quic-issues@ietf.org>; Mon, 21 Oct 2019 19:12:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571710339; bh=3nMlM1DsQ61wACPNiJqTxla0fnCC+XyGZ4cUhU8GBV0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M0k7ZS9X3cZiw6tPACAY0Bp0IxDMRfxmsWQxXs3pYarFt5bU8sEbegJ6Hp8TUWitM VTXuDmKE+tvcZW3jhtyHz87rnPgMpQAJrwoHnUYTFLsf20+kb5wjeM9hJf8Xv3rtYh oTA0r6WDoFeDOn/ZS0kDDRMegrRb1n+BlPQKtwCQ=
Date: Mon, 21 Oct 2019 19:12:18 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZGW5JCKEQRY4CL3CN3XOTBFEVBNHHB4UHVOQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3111/544779814@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3111@github.com>
References: <quicwg/base-drafts/issues/3111@github.com>
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_5dae6582b1bea_22a13f95aeccd96c11268e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/57huA8sAxk1fWHTgKAy2Meb144g>
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: Tue, 22 Oct 2019 02:12:21 -0000

One nit on your first point:
> We are creating another set of resumption information that needs to be retained by the client (we already have NEW_TOKEN token, TLS session ticket, and optionally H3 SETTINGS).

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

There are servers that will want to use NEW_TOKEN and not do version greasing, so I believe this really should be optional if you put it into NEW_TOKEN, just like it would be in transport params.

-- 
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/3111#issuecomment-544779814

v2.23.0 | Report a Bug | By Email