IETF Logo Mail Archive

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

mirjak <notifications@github.com> Thu, 18 January 2018 09:39 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 557B612EB21 for <quic-issues@ietfa.amsl.com>; Thu, 18 Jan 2018 01:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.029
X-Spam-Level:
X-Spam-Status: No, score=-2.029 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 ewrDwaDwpmMO for <quic-issues@ietfa.amsl.com>; Thu, 18 Jan 2018 01:39:52 -0800 (PST)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FA5912EB1E for <quic-issues@ietf.org>; Thu, 18 Jan 2018 01:39:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=EmU9u81Dn0N40QWxk9WAI+8EHcs=; b=IaFmwzoICeJlqHKb yaxo9tokm8vUU/0HluDqEHvikxl0fj8uZiEhwyTndIwzrIYNOLhxQVvVp/5TdNkz IA7G4mRTf0PiF4GvnmWT1QQ5Wx4FQLDBeJA5qdLcA4XaC6JbsaywPjIrnklZeH3X 1yWMQ9a8jiAbuoJ0NbFgi02WGTM=
Received: by filter0049p1iad2.sendgrid.net with SMTP id filter0049p1iad2-1926-5A606B67-4 2018-01-18 09:39:51.231102189 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id eZ3HcgqAQoC47MRLd6nk9w for <quic-issues@ietf.org>; Thu, 18 Jan 2018 09:39:51.228 +0000 (UTC)
Date: Thu, 18 Jan 2018 09:39:51 +0000
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abee4ef50845adfa30db342c1f9bb8ee42f3ef3fad92cf0000000116782d6792a169ce0c118d76@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/358591264@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_5a606b6729c92_39312b005501aed45078d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1rKjIc8z3kBqITt15t7fP1d1f9Nt33HoRI9s dujFe4c823zlE1trOhL1HPtz6NLSV/PiQri9IB+gsWv2cghwh+TyPvpbr9bPR76Ng3RKT6nL9Olthm V+TXJ4j58ZA4TqcHfpCZdeogIdtPMYEmCabpEnIVTRkuIVD8BBsNblP57w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ssST542Gq7PQuTgIi6_6-MDitVE>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 18 Jan 2018 09:39:54 -0000

So I think for a some middleboxes it would actually be beneficial if a migration would look like a new flow/handshake because, as the path may have changed, you might end up at a new middlebox that does not have state yet, and it would be easier to set up new state if you can identify a QUIC flow by its handshake pattern.

However, I agree that this might be hard as you not only would need to send long headers but actually run a whole TLS handshake. Or could it even be beneficial in some cases to re-do the TLS handshake if you are on a new path?

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

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