Date: Wed, 12 Dec 2018 07:11:01 -0800
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abe65d3342a8d02d4329170cbfaeb6e133098983e992cf000000011828e70592a169ce1742d117@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2122/446621471@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2122@github.com>
References: <quicwg/base-drafts/issues/2122@github.com>
Subject: Re: [quicwg/base-drafts] QUIC connection migration and IPv6 only
 NAT64/DNS64 Networks (#2122)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c11250567057_13653fccc52d45c022011e";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/PxLZUIkLRxAvsyWH_EDTVmyaz6w>


----==_mimepart_5c11250567057_13653fccc52d45c022011e
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

> I was implying these frames to be sent post handshake, encrypted and protected and not exposing anything in the TLS handshake itself.

Not arguing on that, just suggesting that address lookup can have a much broader scope and when a single QUIC endpoint starts acting a bit like a DNS perhaps that scope should be taken into account. But certainly not for v1.

-- 
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/2122#issuecomment-446621471
----==_mimepart_5c11250567057_13653fccc52d45c022011e
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<blockquote>
<p>I was implying these frames to be sent post handshake, encrypted and p=
rotected and not exposing anything in the TLS handshake itself.</p>
</blockquote>
<p>Not arguing on that, just suggesting that address lookup can have a mu=
ch broader scope and when a single QUIC endpoint starts acting a bit like=
 a DNS perhaps that scope should be taken into account. But certainly not=
 for v1.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2122#issuecomment-446621471">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq-Yg=
NAEgnpGJVqG4SWlU4LQjtl6Aks5u4RyFgaJpZM4ZPkXE">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq42dl5oyA88GF8HZdL62dWCU=
AVXbks5u4RyFgaJpZM4ZPkXE.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://assets-cdn.github.com/images/email/message_cards/header.png","avatar_=
image_url":"https://assets-cdn.github.com/images/email/message_cards/avat=
ar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicw=
g/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mikk=
elfj in #2122: \u003e I was implying these frames to be sent post handsha=
ke, encrypted and protected and not exposing anything in the TLS handshak=
e itself.\r\n\r\nNot arguing on that, just suggesting that address lookup=
 can have a much broader scope and when a single QUIC endpoint starts act=
ing a bit like a DNS perhaps that scope should be taken into account. But=
 certainly not for v1."}],"action":{"name":"View Issue","url":"https://gi=
thub.com/quicwg/base-drafts/issues/2122#issuecomment-446621471"}}}</scrip=
t>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2122#issuecomment=
-446621471",
"url": "https://github.com/quicwg/base-drafts/issues/2122#issuecomment-44=
6621471",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c11250567057_13653fccc52d45c022011e--