Date: Wed, 12 Dec 2018 07:19:46 -0800
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab677cd0d82c3a84e86d6dd4b632592c1ad4887b6d92cf000000011828e91292a169ce1742d117@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/446624696@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_5c1127121e197_46ab3fbc0fcd45b43765d3";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/dpyfu0B4VcugXaxflwky2_8vR30>


----==_mimepart_5c1127121e197_46ab3fbc0fcd45b43765d3
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Note that generally an endpoint does not know its own public address because it can sit behind load balancers and multiple layers of NAT devices. So having the endpoint publish alternative addresses will not the solve the problem in general.

In fact the scenario could be reformulated to load balancer on multiple stacks instead of the server endpoint. You end up needing some DNS service that can deal with it.

-- 
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-446624696
----==_mimepart_5c1127121e197_46ab3fbc0fcd45b43765d3
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Note that generally an endpoint does not know its own public address b=
ecause it can sit behind load balancers and multiple layers of NAT device=
s. So having the endpoint publish alternative addresses will not the solv=
e the problem in general.</p>
<p>In fact the scenario could be reformulated to load balancer on multipl=
e stacks instead of the server endpoint. You end up needing some DNS serv=
ice that can deal with it.</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-446624696">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkqw-M=
9vBxq-9wMU8fNuzcpOCUyk4eks5u4R6SgaJpZM4ZPkXE">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq1kiwrz_57RyocZK1rCtG3ZR=
1y6Pks5u4R6SgaJpZM4ZPkXE.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: Note that generally an endpoint does not know its own publ=
ic address because it can sit behind load balancers and multiple layers o=
f NAT devices. So having the endpoint publish alternative addresses will =
not the solve the problem in general.\r\n\r\nIn fact the scenario could b=
e reformulated to load balancer on multiple stacks instead of the server =
endpoint. You end up needing some DNS service that can deal with it."}],"=
action":{"name":"View Issue","url":"https://github.com/quicwg/base-drafts=
/issues/2122#issuecomment-446624696"}}}</script>
<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=
-446624696",
"url": "https://github.com/quicwg/base-drafts/issues/2122#issuecomment-44=
6624696",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c1127121e197_46ab3fbc0fcd45b43765d3--