Date: Wed, 12 Dec 2018 14:56:36 +0000 (UTC)
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab08438e2a2668b9795531801a1b42fba2e45b930492cf000000011828e3a392a169ce1742d117@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/446616025@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_5c1121a3e2595_325d3f9f33ad45b41656f0";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/PI54aU4Mhxc9mXbmJ0N19qFSemE>

----==_mimepart_5c1121a3e2595_325d3f9f33ad45b41656f0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Although not strictly related to this problem, there are also concerns about DNS query privacy and host name exposure in TLS handshake. So a version x might look into the broader DNS / cert auth problem along with multiple server paths.

-- 
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-446616025
----==_mimepart_5c1121a3e2595_325d3f9f33ad45b41656f0
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Although not strictly related to this problem, there are also concerns about DNS query privacy and host name exposure in TLS handshake. So a version x might look into the broader DNS / cert auth problem along with multiple server paths.</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/2122#issuecomment-446616025">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AWbkq_s7Sv95m6BcsYioonkMgionBu57ks5u4RkjgaJpZM4ZPkXE">mute the thread</a>.<img src="https://github.com/notifications/beacon/AWbkq0D-N90wsWrJuG9FOng5BcFRh16Lks5u4RkjgaJpZM4ZPkXE.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"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":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mikkelfj in #2122: Although not strictly related to this problem, there are also concerns about DNS query privacy and host name exposure in TLS handshake. So a version x might look into the broader DNS / cert auth problem along with multiple server paths."}],"action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/2122#issuecomment-446616025"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2122#issuecomment-446616025",
"url": "https://github.com/quicwg/base-drafts/issues/2122#issuecomment-446616025",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5c1121a3e2595_325d3f9f33ad45b41656f0--