Re: [quicwg/base-drafts] Be more conservative about migration? (#2143)

Eric Kinnear <notifications@github.com> Wed, 22 May 2019 11:45 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 2FDF012011C for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 04:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 Vd53W-8Zw8g8 for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 04:44:59 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9BB1120033 for <quic-issues@ietf.org>; Wed, 22 May 2019 04:44:58 -0700 (PDT)
Date: Wed, 22 May 2019 04:44:57 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558525497; bh=HsfUPHzD05aDtAFKM5HIOIFDWQwVC8Hfw0muxa5MILo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LdQO/QvEFae/GgG0OzT5ijv9RyHbaDwTizN/GPLnK5j5uSq5xT+O5DzArnVwGXBl2 n4EvZHZ1Pp6CZ0A/4S5xL1dA2v4Sh9dkwt5o2rD7hBxMT37/NihIQ3Fr+g3CLVqTdB wKCkOOD5ios5ear01xvCyIX0UJ+fGh7Zp4yDCBYA=
From: Eric Kinnear <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2HFKNIOXZTULON4XN26JULTEVBNHHBOSK35E@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2143/494767874@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2143@github.com>
References: <quicwg/base-drafts/issues/2143@github.com>
Subject: Re: [quicwg/base-drafts] Be more conservative about migration? (#2143)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce53639a171c_2103fd9ff4cd95c19369c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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/43CKS6DT9F_BpJvUf88DCjOXKqQ>
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: Wed, 22 May 2019 11:45:00 -0000

We've gone through a bunch of different issues in this conversation, many of them have since been addressed. 

In general, we've come up with some requirements, like having both old and new paths be validated, removing many of the concerns around quiescence. There's also now a mention about heuristics, and it might be worth some editorial text describing possible heuristics to use (happy to put some of that together, will pretty much align with @martinduke's and @janaiyengar's comments above).

Much of @martinthomson's comment above with the Tokyo proposal still applies, some of the last bits of the text outlined there are changing in #2637. 

We can try to summarize the current state of things (also happy to do that), but I'm not sure that there's a lot left to do in this issue specifically.

-- 
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/2143#issuecomment-494767874