IETF Logo Mail Archive

Re: [quicwg/base-drafts] Simultaneous connection migration (#490)

janaiyengar <notifications@github.com> Thu, 04 May 2017 23:46 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 20CFD129789 for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 16:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.183
X-Spam-Level:
X-Spam-Status: No, score=-3.183 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, 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 p02w2F2JVXXM for <quic-issues@ietfa.amsl.com>; Thu, 4 May 2017 16:46:06 -0700 (PDT)
Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 98F8912956B for <quic-issues@ietf.org>; Thu, 4 May 2017 16:46:06 -0700 (PDT)
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=IkvJo5rKySAuL0qMQxDbozAMci4=; b=K4NoZOyOvzONG51d Rolh7C2jETK2StzOyXyZ07LYPYHmO/tkN/9u7qjEfRy6QPvL1xmuDJYeLEhYjVT2 seEr1nV+3D4DnpbF3zcQUdMZEL0CS0AnpLKM9b1q/TgyCAVAIhta0A+cA3K+lnme 00e2KThD9zIkwRM2Kx9Sbj3Ve5Q=
Received: by filter0500p1mdw1.sendgrid.net with SMTP id filter0500p1mdw1-12655-590BBD3C-18 2017-05-04 23:46:04.429518017 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id cHo4rkl6TPqVg4DDY8AdwA for <quic-issues@ietf.org>; Thu, 04 May 2017 23:46:04.388 +0000 (UTC)
Date: Thu, 04 May 2017 16:46:04 -0700
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab79af7975253149b3b190bc36cb16160b313f430592cf0000000115237f3c92a169ce0d7229b3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/490/299339092@github.com>
In-Reply-To: <quicwg/base-drafts/issues/490@github.com>
References: <quicwg/base-drafts/issues/490@github.com>
Subject: Re: [quicwg/base-drafts] Simultaneous connection migration (#490)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_590bbd3c4a17c_68ac3f90e267dc2c33757"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0BMcgbYLT6KWz3yurL08CooWZe3dFqNXrCy0 XTo1MctN2Qiff3q1F5Kbv+vrB18+xxugqfkcJ418n61mFnFkv5h0L3Qq2e//qMawWm83Te7wf02s+U bCHWszfJ9qsX50bcKI2oUtrO5bx1EI5slJz0JhAbBgT7QGGQlFZCEKy8RpUmcCELO/8wKtk01JI1LD c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/2ExtDZSlpOxq7pq1qPuYZWo0o20>
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, 04 May 2017 23:46:08 -0000

Ah -- so you're assuming that the peer has stopped listening on the previous port. Sure, that case won't work at all. But the case where both endpoints choose to use a new port while being able to "drain" the old one is possible to do simultaneous migration with.

-- 
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/490#issuecomment-299339092

v2.23.0 | Report a Bug | By Email