WWDC 2015 VIDEO HOW TO
WWDC 2015 VIDEO MAC

Now, a typical test bed will look like this. What that really means is now it's hosting a Wi-Fi hotspot, and you can connect your other client devices and start testing your applications. That means now the Wi-Fi interface is in access point mode. So when I start it, I see that the Wi-Fi icon has grayed out and it has an arrow pointing up. Now, for the example here, I have my IPv4 connectivity on the Internet and I'm sharing this as an IPv6-only access network with NAT64/DNS64 on my Wi-Fi interface. Now, this feature is meant to be used by the developers, so it's somewhat hidden, and to make it visible, all you have to do is to Option-click on Sharing, then Option-click on Internet Sharing, and now you will see everything looks just the same.īut there's a new checkbox here that says 'Create NAT64 Network.' So you check that, you choose your interfaces for Internet sharing, and now you can host this NAT64 network and start testing your applications.

WWDC 2015 VIDEO MAC

Starting today, with just your Mac devices on top of IPv4 connectivity, you can create your very own NAT64 networks and start testing your applications. So great, we have a new app submission requirement, right? And you must be wondering how do I test my application for this network? Where will I find this NAT64 type of network? I have a great news for all of you. Now the transition to this type of network will happen very soon, and when it happens, we want it to be an absolutely seamless experience for our consumers.Īnd that is the reason your app has to be IPv6 compliant, and this will be an app submission requirement. Now, the important thing to note here is that to the applications running on the client device, your IPv4-only server looks like an IPv6-only server.Īnd this is important because till now, some of you in the room may have been thinking that my server is only configured for IPv4, so I do not need to test for a client accessing it over an IPv6 network. The network itself is configured in a way that search packets get shorted to the NAT64 engine, which then translates IPv6 traffic to IPv4 and vice versa on the way back. Now that the client device has this IPv6 address to work with, it can start writing traffic to the network. So now they have deployed DNS64 and NAT64 in their network, and the way it works is when the application on the client device makes a hostname query to get the IPv6 address for an IPv4-only server, DNS64 and the network synthesizes an IPv6 address and gives it back to the client device. Now, when you do that, you lose connectivity to the IPv4-only part of the Internet, which is still in majority. So what they really want to do is to drop IPv4 from their access network. So that's great, right? Turns out it's actually worse for cellular carriers than it was before.Īnd the reason is now they are having to support both IPv4 as well as IPv6 in their network. And second, more than half of the subscribers are now connecting to cellular data networks over IPv6. I will now show you how IPv6 deployment looks for three major cellular carriers in the USA. Now, with this, they again have end-to-end network connectivity and there's no translation needed in the data path.

So carriers are now deploying IPv6 in their network. Now, this works, but the larger scale NAT device is both expensive and fragile. However, we soon realized that we were running out of IPv4 addresses way too fast.

Now, a long, long time ago, client devices had real and unique IPv4 addresses these were the good olden days and you had end-to-end network connectivity. Now, we will talk more about that and what it means to you as developers, but before we do that, let's begin with a bit of history. That is the reason we will also be mandating your applications to be IPv6 compliant. So you must be wondering, why are we talking about IPv6 now? We are seeing more and more of IPv6 deployment in enterprise and cellular networks.Īnd you want to make sure that your applications work in those networks. Now, what's new in IPv6? IPv6 RFC was published almost 17 years back.

WWDC 2015 VIDEO HOW TO

For the first topic I will talk about IPv6, and for the second topic Stuart will talk about how to make your applications run faster. I am Prabhakar Lakhera and with me I have my colleague Stuart Cheshire.Īnd this session is in two parts. Welcome to Your App and Next Generation Network session. PRABHAKAR LAKHERA: Thank you and good morning.

Wwdc 2015 video