Date: Wed, 22 Jul 2020 04:19:59 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK2VDD6DEJ3GHH4ZV2V5EQA57EVBNHHCPCRAZE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3932/662396977@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3932@github.com>
References: <quicwg/base-drafts/issues/3932@github.com>
Subject: Re: [quicwg/base-drafts] Servers are not expected to validate
 multiple paths simultaneously (#3932)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5f1820df7282c_3a743ff138ccd968101811";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/rpDtmpqLJoekXt0cgKVk8PSXa7M>


----==_mimepart_5f1820df7282c_3a743ff138ccd968101811
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@marten-seemann So the scenario is that a client is using one path and has 2 or more new ones available?  I've heard future hardware could make that possible, though I've never seen that case myself.

The short of this is now that we're trying to move to IETF QUIC style connection migration and path validation, and I'm finding it fairly confusing.

-- 
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/3932#issuecomment-662396977
----==_mimepart_5f1820df7282c_3a743ff138ccd968101811
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/marten-seemann/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/marten-seemann">@marten-seemann</a> So the scenario is that a client is using one path and has 2 or more new ones available?  I've heard future hardware could make that possible, though I've never seen that case myself.</p>
<p>The short of this is now that we're trying to move to IETF QUIC style connection migration and path validation, and I'm finding it fairly confusing.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/issues/3932#issuecomment-662396977">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK3VNRG25CAMZ5JGBK3R43DN7ANCNFSM4PEEGI2A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK5LYAOTAL4UNO52CG3R43DN7A5CNFSM4PEEGI2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE55WAMI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/3932#issuecomment-662396977",
"url": "https://github.com/quicwg/base-drafts/issues/3932#issuecomment-662396977",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5f1820df7282c_3a743ff138ccd968101811--