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

Igor Lubashev <notifications@github.com> Wed, 25 January 2017 00:05 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 02E8C1295BA for <quic-issues@ietfa.amsl.com>; Tue, 24 Jan 2017 16:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.218
X-Spam-Level:
X-Spam-Status: No, score=-5.218 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_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, 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 xcc4ai51-pHC for <quic-issues@ietfa.amsl.com>; Tue, 24 Jan 2017 16:05:46 -0800 (PST)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 D59561295B9 for <quic-issues@ietf.org>; Tue, 24 Jan 2017 16:05:45 -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=s2fLBazQA7gsBnaL+gc6ULzEhE0=; b=fhMJQRHd8myz2Y5E MRWweLlTvh7p+PCKF+dKEQx+VJks6V2G2vZDGGW1RHNwFriWrSWZlLAHJZWzMboq veU8AdR0aAvx7ogXy8NCrvK5QM9d/JIecnywdT4Wxd1X+0RZjpc6TzT1BOsnsC+q g24+VHrPzHRfe9fK7MSRrBZAYAo=
Received: by filter0443p1mdw1.sendgrid.net with SMTP id filter0443p1mdw1-25415-5887EBD2-49 2017-01-25 00:05:38.567024704 +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 ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id MYWswVIxTqimqWri1JxOeA for <quic-issues@ietf.org>; Wed, 25 Jan 2017 00:05:38.309 +0000 (UTC)
Date: Tue, 24 Jan 2017 16:05:38 -0800
From: Igor Lubashev <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/203/274979665@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_5887ebd23584a_6c2a3fc5556d513c615c2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0NV5AEZh4JeSNAuxitMJU0ikfmRhGEe64VQ9 hG5uN94QVKfQFDBGUmZHDLRFFS8QWWOuG04Ewi9Xvf+VKqD8CLqjgZRUMLGtkw03IhttEQneSaxWUJ ctry1VC6ctJwfhUeQyBkGvuzZvkFdKDu6zHk4tRIs64OR9WVB4d1Nk9FtogYOWO1sMUXep5z+9xMbQ o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/1GZlbJ7A_EwnvOYV1olePsXIX8s>
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: Wed, 25 Jan 2017 00:05:48 -0000

@marten-seemann But @mirjak makes a valid point. The sender may be unaware. It could be a case of a NAT rebinding (new outgoing UDP port) or you are on a WiFi spot provided by a cell-connected router that just migrated to a different operator.

Trying to confuse the network, you are confusing the server as well (unless your server is a single lonely box on a rack somewhere). CDNs are complex networks with multiple machines coordinating to present you with a nice "server" abstraction. If you are successful in confusing the network, you will confuse CDNs and as a result end users will get suboptimal performance and reliability for their connections.

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