<div>I believe using host names will work. However the issue comes in some cases where you can't use hostnames for streaming (ex: connecting directly to an IP camera) and must instead pass an IPv4 literal. Here is what Apple specifies you must do. I tried this with udpsink and I'm having issues connecting.</div><div><span style="font-family:'Lucida Grande','Lucida Sans Unicode',Helvetica,Arial,Verdana,sans-serif;font-size:23.200000762939453px"><br></span></div><div><span style="font-family:'Lucida Grande','Lucida Sans Unicode',Helvetica,Arial,Verdana,sans-serif;font-size:23.200000762939453px">Use System APIs to Synthesize IPv6 Addresses</span><br></div><div><p style="margin-top:0px;margin-bottom:0.833em;line-height:normal;font-family:'Lucida Grande','Lucida Sans Unicode',Helvetica,Arial,Verdana,sans-serif">If your app needs to connect to an IPv4-only server without a DNS hostname, use <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">getaddrinfo</code> to resolve the IPv4 address literal. If the current network interface doesn’t support IPv4, but supports IPv6, NAT64, and DNS64, performing this task will result in a synthesized IPv6 address.</p><p style="margin-top:0px;margin-bottom:0.833em;line-height:normal;font-family:'Lucida Grande','Lucida Sans Unicode',Helvetica,Arial,Verdana,sans-serif"><span class="content_text" style="margin-top:0px;line-height:normal;margin-bottom:0.833em;padding-bottom:0.833em">Listing 10-1</span> shows how to resolve an IPv4 literal using <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">getaddrinfo</code>. Assuming you have an IPv4 address stored in memory as four bytes (such as <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">{192, 0, 2, 1}</code>), this example code converts it to a string (such as <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">"192.0.2.1"</code>), uses <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">getaddrinfo</code> to synthesize an IPv6 address (such as a <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">struct sockaddr_in6</code> containing the IPv6 address <code style="font-size:16.479999542236328px;font-family:Courier,Consolas,monospace;color:rgb(102,102,102);word-break:break-all">"64:ff9b::192.0.2.1"</code>) and tries to connect to that IPv6 address.</p><div class="gmail_quote"><div>On Tue, Dec 20, 2016 at 5:35 AM Sebastian Dröge <<a href="mailto:sebastian@centricular.com">sebastian@centricular.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 2016-12-19 at 18:38 -0800, jml5qh wrote:<br class="gmail_msg"><br>> Is there any native support for dealing with NAT64 translation? Apple<br class="gmail_msg"><br>> is<br class="gmail_msg"><br>> requiring this support in apps:  Apple documentation<br class="gmail_msg"><br>> <<a href="https://developer.apple.com/library/content/documentation/Networking" rel="noreferrer" class="gmail_msg" target="_blank">https://developer.apple.com/library/content/documentation/Networking</a><br class="gmail_msg"><br>> InternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfo<br class="gmail_msg"><br>> rtheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html<br class="gmail_msg"><br>> #//apple_ref/doc/uid/TP40010220-CH213-SW23>  <br class="gmail_msg"><br><br class="gmail_msg"><br>What exactly does this require from the application? Just not using any<br class="gmail_msg"><br>IPv4 addresses directly, but instead using hostnames and IPv6<br class="gmail_msg"><br>addresses? What exactly does Apple require?<br class="gmail_msg"><br><br class="gmail_msg"><br>Generally this should all work fine already, but there might be usage<br class="gmail_msg"><br>of (or references to) now "forbidden" APIs nonetheless. Do you know<br class="gmail_msg"><br>what exactly is a problem?<br class="gmail_msg"><br><br class="gmail_msg"><br>--<br class="gmail_msg"><br>Sebastian Dröge, Centricular Ltd · <a href="http://www.centricular.com" rel="noreferrer" class="gmail_msg" target="_blank">http://www.centricular.com</a>_______________________________________________<br class="gmail_msg"><br>gstreamer-devel mailing list<br class="gmail_msg"><br><a href="mailto:gstreamer-devel@lists.freedesktop.org" class="gmail_msg" target="_blank">gstreamer-devel@lists.freedesktop.org</a><br class="gmail_msg"><br><a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br class="gmail_msg"><br></blockquote></div></div>