IETF Logo Mail Archive

Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)

ianswett <notifications@github.com> Mon, 23 January 2017 10:07 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 C7D97129AE4 for <quic-issues@ietfa.amsl.com>; Mon, 23 Jan 2017 02:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.752
X-Spam-Level:
X-Spam-Status: No, score=-6.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-1.156, 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 UBuJW9z8CgWO for <quic-issues@ietfa.amsl.com>; Mon, 23 Jan 2017 02:07:39 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [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 637F9129405 for <quic-issues@ietf.org>; Mon, 23 Jan 2017 02:07:39 -0800 (PST)
Date: Mon, 23 Jan 2017 02:07:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1485166058; bh=pyacAbibebNTorr8wFxNrHz90ijXVgg8MioS+XKFay4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pJ0CwmDK/U2xRd9leuJHIoGAUxdgElZDxCBcKEhPa3BBDvpeXeFmWX7OZlIa7+YT4 iMvWE3mByP687Gggq8FHfrtYUROzVJOQrSmN5Cnc8M+eA435ZKyIhsPqikzvo93tIl 2dvla5khoiCM4sdNyNGlgLRLnrT9XLA8Fz7NKRdQ=
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/203/274446488@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_5885d5ea5bac1_6a993fcf2997113831473"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/nbF-uCedS7tTM6tqTXjXbDiqN0w>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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: Mon, 23 Jan 2017 10:07:41 -0000

Agreed that it should look as much like a new connection as possible.

I've heard middleboxes had to add explicit support for MPTCP, so at the very least, we don't want to be in a situation where middleboxes need to change their behavior to accommodate QUIC connection migration or multipath.

The question becomes how much does it need to look like a new handshake?  ie: Is it sufficient to send a fake CHLO followed by forward secure data, or do we need to wait an RTT?  How realistic does the CHLO need to be?

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

v2.37.1 | Report a Bug | By Email | System Status