IETF Logo Mail Archive

Re: [quicwg/base-drafts] Servers can't migrate. Period. (#2031)

Martin Thomson <notifications@github.com> Wed, 21 November 2018 04:52 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 AD84B127333 for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 20:52:58 -0800 (PST)
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 uSI5SsGP87fp for <quic-issues@ietfa.amsl.com>; Tue, 20 Nov 2018 20:52:57 -0800 (PST)
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 CA3A41276D0 for <quic-issues@ietf.org>; Tue, 20 Nov 2018 20:52:56 -0800 (PST)
Date: Tue, 20 Nov 2018 20:52:55 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542775975; bh=R0BlSOzC916aD4LBkblsqB0AIUYkhllG0xD4FDLWPR8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sAjHEwqxllrTXtP0bLLYO98rMHeLKsoep3PoGNzVdWNEamGeIa0WrPhqYoE5teEnw 8bGxO1MtO/7QQZAQgk+5SQCU8fywx4RR+h+dLb0hELeLtRB/dP9hyDSYrx/pq5yHss p3Vt7BaMozpV63bHVorvhHG5RroQRC3L+pOWoS3c=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab3ca2ba818baefe6e205f3dd85360306ad4d2ab8592cf00000001180ca6a792a169ce16d36b25@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2031/c440530402@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2031@github.com>
References: <quicwg/base-drafts/pull/2031@github.com>
Subject: Re: [quicwg/base-drafts] Servers can't migrate. Period. (#2031)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf4e4a7dfe70_59683f9be52d45b896035"; 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/8ltCqpyhRpU4u7h_S-1pyaHxZNs>
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, 21 Nov 2018 04:52:59 -0000

Yes.  I am similarly unhappy, but the task to properly define migration for both clients and servers ultimately ends up with something as complex as ICE.  We don't want to repeat that mistake.  ICE started small, then turned into an RFC that was so large and complex people were scared of it.

-- 
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/2031#issuecomment-440530402

v2.23.0 | Report a Bug | By Email