IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Fri, 26 October 2018 00:55 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 C9AF0130DD1 for <quic-issues@ietfa.amsl.com>; Thu, 25 Oct 2018 17:55:23 -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 t9u1urtrpSaU for <quic-issues@ietfa.amsl.com>; Thu, 25 Oct 2018 17:55:22 -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 072D31286E7 for <quic-issues@ietf.org>; Thu, 25 Oct 2018 17:55:22 -0700 (PDT)
Date: Thu, 25 Oct 2018 17:55:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1540515320; bh=l7A/WGahkcoYUerdQMDk7qOsgEWGjZoAzu6D84HE+iA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0E5zaiAkOo7iWjnemrSJtOhNDEUsIGYPBWShjy7fveZAnmCXTh2/aHAl4pnal97zc e0a+styQDrqn1Z+AMF8riw5eSuZMVI7soCAO0W9oyhmWkdkOix/2YbNo6DRtbNHczA FjulVcZm7DRrtN5l2+jwt9yds/1D/Feqiy6wqNaU=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab331bfe39f7ac3d3579261f11a2f0105b037540f692cf0000000117ea27f892a169ce1640b1a8@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/c433251999@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_5bd265f8cf466_45903fc041ad45bc26055d4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/A8pC3NSevuzJLYo8KgBmsDcb4Ps>
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 00:55:24 -0000

@marten-seemann, I assume that the server would upgrade to support v2 in stages similar to what @kazuho suggests in [this comment](https://github.com/quicwg/base-drafts/pull/1901#discussion_r228354726):

That is, the server first starts accepting v2, but not advertising support for it.  In the revised design I proposed, it would also not object if v2 were to appear in unsupported versions during this phase of rollout.

Once all server instances have started accepting v2, then the server can start sending it in Version Negotiation packets.

With the proposed design there is a third phase - once there are no Version Negotiation packets in flight that don't advertise v2, the server can generate errors if unsupported_versions contains v2.

-- 
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-433251999

v2.23.0 | Report a Bug | By Email