Slashdot Mirror

← Back to Stories (view on slashdot.org)

IPv6 Achieves 50% Reach On Major US Carriers (worldipv6launch.org)

Posted by EditorDavid on from the following-protocol dept.

Long-time Slashdot reader dyork brings new from The Internet Society: IPv6 deployment hit a milestone this month related to the four major US providers (Verizon Wireless, T-Mobile USA, Sprint, AT&T): "IPv6 is the dominant protocol for traffic from those mobile networks to major IPv6-capable content providers."
A graph on their "World IPv6 Launch" site shows those carriers are now delivering close to 55% of their traffic over IPv6 to major IPv6-capable content providers -- up from just 37.59% in December. "This is really remarkable progress in the four years since World IPv6 Launch in 2012, and the growth of IPv6 deployment in 2016 is showing no signs of abating." In fact, the NTIA is now requesting feedback from organizations that have already implemented IPv6, noting that while we've used up all the 4.3 billion IPv4 addresses, IPv6 offers 340 undecillion IP addresses -- that is, 340 followed by 36 digits.

9 of 150 comments (clear)

  1. In before... by Just+Some+Guy · · Score: 4, Funny

    Here, let's get the resistance out of the way:

    "But, but, if we can't have NAT then we'll be h4xx0r3d! And I can't remember all those hex digits LOL."

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:In before... by unixisc · · Score: 3, Informative

      No. PAT involves using port numbers to supplement IPv4 addresses, so that a hybrid static-dynamic NAT in IPv4 can get a 1:1 mapping b/w the local IP addresses and the external IP address coupled w/ the port number. That's one of the things that IPv6 eliminates, but it also removes things like load balancing or address isolation.

      NPT - Network Prefix Translation - is different. It keeps the Interface ID unchanged - the part of the address that's not part of the network address - is not touched. Instead, a public unicast address is converted into a site local address, w/o touching port numbers. What you have is a 1:1 relationship b/w local and routable addresses. In PAT, what you have is a 1:1 relationship b/w a routable address coupled w/ one of 65536 port numbers to a local address. Which is a mess, b'cos if one needs ports for anything else (like map segments in a mapping application), one has to keep tabs on the ports used for PAT vs the ones used for the applications that need them

  2. Re:is that math correct? by Lord+Crc · · Score: 4, Informative

    IPv6 = 256^6 = ... 340x10^36 ???

    Not sure if bad attempt at joke or not, but in case it isn't: the 6 in IPv6 isn't the number of octets used in the addresses, it's a version number. IPv6 uses 128 bit addresses, and 2^128 = 3.4 * 10^38.

  3. There are 5 trillion /56 blocks by raymorris · · Score: 5, Interesting

    IPv6 has five TRILLION /56 blocks.

    There are enough /64 to give every person on earth 2,635,249,153 of them.

    128 bits allows for HUGE numbers.

    Long ago, when we were developing IPv6, I was part of the group who argued for 128 bit addresses rather than 64 bit. I've decided I was wrong. 64 bits would have been more than enough, and could be processed on 64-bit processors, in standard databases, without hassle. Since my side won the argument, we have 128-bit addresses, which are so big they are a pain in the ass in Microsoft SQL Server and elsewhere.

    1. Re:There are 5 trillion /56 blocks by flargleblarg · · Score: 5, Insightful

      The woes of MicroSoft SQL Server should not be dictating the future. I, for one, am very glad that you argued in favor of 128-bit addresses.

  4. Re:Grey Goo Limit by Anonymous Coward · · Score: 3, Informative

    You recall xkcd 865.

  5. In the meantime Canada ISPs are behind by Midnight+Thunder · · Score: 3, Interesting

    Still frustrated that the ISPs in Canada are still lagging on getting IPv6. The biggest failing ISP is Bell, with no publicly announced plans.

    There has been the "Call Your ISP for IPv6" campaign by the guys over at Sixxs:

    https://www.sixxs.net/wiki/Cal...

    --
    Jumpstart the tartan drive.
  6. Internet royalty walks among us by destinyland · · Score: 4, Interesting

    I just think it's cool that the Internet Society's Dan York is posting to Slashdot (and has a six-digit UID).

  7. Re:is that math correct? by unixisc · · Score: 3, Informative

    While I do think IPv6 addresses are wasted, I don't think the wastage happens in the global prefix. Rather, it happens in the Interface ID area. 64 bits is way overkill for an interface ID, since no subnet will have anywhere close to even 4 billion nodes, much less 2^64. In the meantime, in the global prefix side, things are squished w/o getting into a hierarchical routing, which would have been a real godsend, had it been implemented.

    Yeah, my example probably shifted things, due to my use of documentation's 2001:db8::/32, and your scenario would be the more likely one. Still, I believe that the upper 4 words should have been strictly global prefixes, not including subneting: it should have been used to hierarchically route from IANA to RIR to country to ISP to organization/families/individuals. At a gateway, allow for either a /64 or a /96 (w/ 4 billion subnets), depending on the need. So if a home router needs 2 network addresses for 2 SSIDs, either get 2 /64s or subnet 1 /64 into /96s.

    The reason that is given for the 64 bit interface ID is auto-configuration, but that's a lame excuse. First of all, even w/ 64 bits, it's unlikely, but not guaranteed that there won't be an address conflict, and at any rate, there is DAD to resolve that in IPv6. Then, using things like MAC addresses or IMEA numbers to obtain these addresses creates a potential for spoofing agents to deduce a target address, assuming that a network wants those things either hidden, or difficult to find w/o initiating from the user's end. 32 bits would easily have been enough for any subnet - even in the most crowded spot in Guangzhou, I doubt that there would be anything close to 4 billion devices that would be under a subnet, and even if there was, that network would grind to a halt w/o redundant APs, repeaters and other signal enhancing agents. So the IETF could have designed IPv6 to have the first 64 bits strictly the global prefix, then either have a 16:48 or 32:32 split b/w subnets and nodes.