Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop <notifications@github.com> Tue, 10 July 2018 23:27 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 342BB130E67 for <quic-issues@ietfa.amsl.com>; Tue, 10 Jul 2018 16:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 j91FfSvKbadZ for <quic-issues@ietfa.amsl.com>; Tue, 10 Jul 2018 16:27:41 -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 8A3F412426A for <quic-issues@ietf.org>; Tue, 10 Jul 2018 16:27:41 -0700 (PDT)
Date: Tue, 10 Jul 2018 16:27:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531265260; bh=rq8JQOjvD2wbE7SNwuy4Pvgqu2yDP2zYnSFmdrrN9cw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hQsZnDMlUTFdGRHiVrVbH8gHpsgVaE0yNpTNXTfRZvmt5w7hwzwUV102YscEF1/RF 64sjbdygxTqmV5r+wMTdHgQLLC34S0m9NHjMxJOApJXLNiISLPdPQBbikUxRPR1ZWJ QyJOzwfLKq2dk/1YC+BQL0mTem6BKKD/ZCOfzmzI=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2fc58ab7aa866e9f308ec02a00a990a98d27e47392cf00000001175d02ec92a169ce0c118d76@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/203/403997182@github.com>
In-Reply-To: <quicwg/base-drafts/issues/203@github.com>
References: <quicwg/base-drafts/issues/203@github.com>
Subject: Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b4540ecd57be_78a83fcebe7acf841254482"; 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/2QyQM8_eS8IoJ-dyLsBkYqWKmBY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 10 Jul 2018 23:27:46 -0000
This proposes a change to the invariants. By definition, then, it can't be v2. My feeling is that we've sufficiently stabilized our choices in the invariants and we should close this with no action. -- 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/203#issuecomment-403997182
- [quicwg/base-drafts] Connection migration should … Lucas Clemente
- Re: [quicwg/base-drafts] Connection migration sho… ianswett
- Re: [quicwg/base-drafts] Connection migration sho… mirjak
- Re: [quicwg/base-drafts] Connection migration sho… Marten Seemann
- Re: [quicwg/base-drafts] Connection migration sho… Igor Lubashev
- Re: [quicwg/base-drafts] Connection migration sho… Lucas Clemente
- Re: [quicwg/base-drafts] Connection migration sho… Mike Bishop
- Re: [quicwg/base-drafts] Connection migration sho… Mike Bishop
- Re: [quicwg/base-drafts] Connection migration sho… Mike Bishop
- Re: [quicwg/base-drafts] Connection migration sho… Mike Bishop
- Re: [quicwg/base-drafts] Connection migration sho… Martin Thomson
- Re: [quicwg/base-drafts] Connection migration sho… ianswett
- Re: [quicwg/base-drafts] Connection migration sho… MikkelFJ
- Re: [quicwg/base-drafts] Connection migration sho… mirjak
- Re: [quicwg/base-drafts] Connection migration sho… Christian Huitema
- Re: [quicwg/base-drafts] Connection migration sho… Lars Eggert
- Re: [quicwg/base-drafts] Connection migration sho… Kazuho Oku
- Re: [quicwg/base-drafts] Connection migration sho… MikkelFJ
- Re: [quicwg/base-drafts] Connection migration sho… Kazuho Oku
- Re: [quicwg/base-drafts] Connection migration sho… MikkelFJ
- Re: [quicwg/base-drafts] Connection migration sho… Mike Bishop
- Re: [quicwg/base-drafts] Connection migration sho… Kazuho Oku
- Re: [quicwg/base-drafts] Connection migration sho… Mike Bishop
- Re: [quicwg/base-drafts] Connection migration sho… Kazuho Oku
- Re: [quicwg/base-drafts] Connection migration sho… Martin Thomson
- Re: [quicwg/base-drafts] Connection migration sho… Martin Thomson
- Re: [quicwg/base-drafts] Connection migration sho… Martin Thomson