Date: Tue, 17 Oct 2017 05:00:53 +0000 (UTC)
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abec412e46bb37df2c8b63486aae62a7636f3df0bb92cf0000000115fd508492a169ce0ee9dd49@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/732/c337118214@github.com>
In-Reply-To: <quicwg/base-drafts/pull/732@github.com>
References: <quicwg/base-drafts/pull/732@github.com>
Subject: Re: [quicwg/base-drafts] Address validation for connection migration
 (#732)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_59e58e84d5934_76e13fb5fd268f3492060";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/K73MLr9Z3K4xqxicnGlloA4rYNc>

----==_mimepart_59e58e84d5934_76e13fb5fd268f3492060
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Hm, yes, you're right. So, I do have articulated rules about when to switch, but it'll take a lot more to explain, and it is the "more detailed model" of switching. So, IIUC, in this simple case, client swithces and sends packet from new IP/port, server sees packet from new address and starts validation, during and after validation completes continues sending data to new IP/port. Is this correct? This is fine with me. (FWIW, this is exactly what GQUIC used to do/does right now, and we're working through its inadequacies.)

-- 
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/pull/732#issuecomment-337118214
----==_mimepart_59e58e84d5934_76e13fb5fd268f3492060
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Hm, yes, you're right. So, I do have articulated rules about when to swi=
tch, but it'll take a lot more to explain, and it is the "more detailed mod=
el" of switching. So, IIUC, in this simple case, client swithces and sends =
packet from new IP/port, server sees packet from new address and starts val=
idation, during and after validation completes continues sending data to ne=
w IP/port. Is this correct? This is fine with me. (FWIW, this is exactly wh=
at GQUIC used to do/does right now, and we're working through its inadequac=
ies.)</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&mda=
sh;<br />You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, <a href=3D"https://github.com/quicwg/bas=
e-drafts/pull/732#issuecomment-337118214">view it on GitHub</a>, or <a href=
=3D"https://github.com/notifications/unsubscribe-auth/AWbkq2qtpEGVE8SvEEisS=
s5f7PRXqoaMks5stDSEgaJpZM4O3IIJ">mute the thread</a>.<img alt=3D"" height=
=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq6jcTGscPaVUspDRm=
2TBGzijO0hOks5stDSEgaJpZM4O3IIJ.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewAction=
">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/pull=
/732#issuecomment-337118214"></link>
  <meta itemprop=3D"name" content=3D"View Pull Request"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Pull Request on GitHub"=
></meta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_version"=
:"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"Gi=
tHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"quicwg=
/base-drafts","subtitle":"GitHub repository","main_image_url":"https://clou=
d.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290=
892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/asset=
s/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name=
":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates=
":{"snippets":[{"icon":"PERSON","message":"@janaiyengar in #732: Hm, yes, y=
ou're right. So, I do have articulated rules about when to switch, but it'l=
l take a lot more to explain, and it is the \"more detailed model\" of swit=
ching. So, IIUC, in this simple case, client swithces and sends packet from=
 new IP/port, server sees packet from new address and starts validation, du=
ring and after validation completes continues sending data to new IP/port. =
Is this correct? This is fine with me. (FWIW, this is exactly what GQUIC us=
ed to do/does right now, and we're working through its inadequacies.)"}],"a=
ction":{"name":"View Pull Request","url":"https://github.com/quicwg/base-dr=
afts/pull/732#issuecomment-337118214"}}}</script>=

----==_mimepart_59e58e84d5934_76e13fb5fd268f3492060--