<div dir="ltr">On Wed, Feb 13, 2013 at 3:27 AM, Doug Barton <span dir="ltr"><<a href="mailto:dougb@dougbarton.us" target="_blank">dougb@dougbarton.us</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
An example I have direct experience of is the code that does connection<br>
establishment libjingle, used by Google video chat. Being able to rely<br>
on the fact that the IPv6 address assigned to your interface is, in<br>
fact, your IPv6 address greatly simplifies the code. By comparison,<br>
firewall traversal is trivial.<br>
</div></blockquote>
<br>
Fair enough, but I live in a world where that issue has already been addressed, with multiple different solutions available.</blockquote><div><br></div><div>Even if there is code available, you're still talking about development and testing cost (and decreased reliability in corner cases), in all non client-server applications, forever. It doesn't have to be that way.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Would life be easier if such solutions were not necessary? Sure! Are we ever again going to live in a world where they are not? Nope.</blockquote>
<div><br></div><div>I disagree. Here's an alternative scenario: enough of the userbase of these applications has non-NPTed IPv6. There is insufficient incentive for the developers to support NPT. Thus, NPT is not supported by the majority of apps.</div>
<div><br></div><div>Since you use today's NATed IPv4 world as an example, here's an example from that world of apps that don't bend over backwards to work everywhere: AFAIK Skype (arguably the app with the best workaround) doesn't work behind networks that don't allow TCP or UDP connections to the outside world but only use HTTP proxies. Technically, it could probably be made to work behind an HTTP proxy by implementing tunneling over HTTP, but it doesn't.</div>
</div></div></div>