IETF Logo Mail Archive

Re: [quicwg/base-drafts] Compatible version upgrade (#1901)

MikkelFJ <notifications@github.com> Fri, 26 October 2018 09:46 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 449C61293FB for <quic-issues@ietfa.amsl.com>; Fri, 26 Oct 2018 02:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 rq_BQdWqERtQ for <quic-issues@ietfa.amsl.com>; Fri, 26 Oct 2018 02:46:29 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF2A31252B7 for <quic-issues@ietf.org>; Fri, 26 Oct 2018 02:46:29 -0700 (PDT)
Date: Fri, 26 Oct 2018 02:46:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540547187; bh=qp1XOrbn7gzi0qkmwLi8VtMAZmq+rQvdL2HoYqH8iMU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cjtx5drb2iIX4BBJNqBBXCyjJiQS4mhywscfnRzK18eSYUjQXo5sxk1pMxm54B6lA QkJVfS14GWiGqfAEFpRwIm+p3KHZ4i/4VA6/g+W4FjHmDgHE8/jmgcYkyHZYwtzyGC DmoJh4kPsBkI2nialzbdkfiJmrvmKqYA+vsc/XSY=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb1c753a72e9fb5a6e144b39e680b9b40a55c78ac92cf0000000117eaa47392a169ce1640b1a8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1901/c433352263@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1901@github.com>
References: <quicwg/base-drafts/pull/1901@github.com>
Subject: Re: [quicwg/base-drafts] Compatible version upgrade (#1901)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bd2e273a9b72_7b903fb7b5ad45c4456169"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/P-uJT-KmQOi2yukHOk12e0pQsSM>
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, 26 Oct 2018 09:46:32 -0000

I can't get my head around this sence

> A server MUST NOT send a Version Negotiation packet if it prefers a version that
 is not compatible with the version the client initially chose; a server has to
 allow the client to choose between versions that are not compatible.

It is a bit unclear when a client populates other compatible versions: in the first connection attempt, or only as a response to a VN packet. In the latter case the client already has made a choice and the server should not send VN.

On the hande in the first connection attempt the client might want to try v1 with the option of v1.1 and v1.2 as compatible upgrades. It might also want to support v2 but since v2 is not compatible, it cannot say that. But it could hope for v2 in a VN packet. Except, the server is not allowed to do that.

-- 
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/1901#issuecomment-433352263

v2.23.0 | Report a Bug | By Email