Re: [quicwg/base-drafts] Describe a new version negotiation mechanism which allows for (#1755)

Mike Bishop <notifications@github.com> Fri, 28 September 2018 16:30 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 44986130E63 for <quic-issues@ietfa.amsl.com>; Fri, 28 Sep 2018 09:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 3t5PPmxaNwPn for <quic-issues@ietfa.amsl.com>; Fri, 28 Sep 2018 09:30:40 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 456F3128D0C for <quic-issues@ietf.org>; Fri, 28 Sep 2018 09:30:40 -0700 (PDT)
Date: Fri, 28 Sep 2018 09:30:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538152239; bh=Vb3R+Osdrzl+nuq8pAmpt3lnnm9z1KuzqG8wbEYxL3s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=xJVuuCJvUM5PJbK7H08EukkkANb3JU72GthdMhIEudsOglVUz8ZjZf6AkubsBzSqq QkOz/1nyhJNSaAY+0Hv1IgfpatTsOQtBmmeex4gkgJ0X72YF7tY5SFVvfh/B527M96 cWhbydyPy87frmEy+ngnuLXxeEx547hVRbZE01sU=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab270407019d612ee3644c9bfeecb86a32514d56e792cf0000000117c6192f92a169ce1583704e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1755/c425492193@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1755@github.com>
References: <quicwg/base-drafts/pull/1755@github.com>
Subject: Re: [quicwg/base-drafts] Describe a new version negotiation mechanism which allows for (#1755)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bae572f34ffb_49d73fa944ed45b83701b5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/wTLCWPdsjjdPtZ1qSJC-xnnb87s>
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: Fri, 28 Sep 2018 16:30:42 -0000

I think we don't want to remove the client's initially-offered version or the server's list of other supported versions -- they're there for valid reasons and are still needed.  The client's original version is used for the server to ensure that the VN wasn't spurious.  The server's other supported versions are useful for the client to remember and pick a more-preferred version next time.

This optimization should strictly add to the VN information in the handshake, with a list of compatible version the server could switch to in its response.

(The suggestion that such compatible versions would include near-final draft versions and the final RFC is definitely intriguing from a deployment standpoint, incidentally.)

-- 
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/pull/1755#issuecomment-425492193