Comments on: IPv6 – Blocks, Slashes and Big Numbers http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/ A Behind the Scenes Look at the Best Hosting Provider in the World Fri, 24 May 2013 11:59:58 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: michael http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-45753 michael Mon, 07 Jan 2013 07:14:26 +0000 http://blog.softlayer.com/2011/#comment-45753 why is ipv6 so slow to adoption? because 4 octets of numerals is way easier to remember. even tech people that can remember a lot dont want to go through that. were all dragging tooth and nail until its eventual. however, they said the world would blow up years ago because of ipv4 running out of addresses. why is ipv6 so slow to adoption? because 4 octets of numerals is way easier to remember. even tech people that can remember a lot dont want to go through that. were all dragging tooth and nail until its eventual. however, they said the world would blow up years ago because of ipv4 running out of addresses.

]]> By: Mike http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-45722 Mike Fri, 04 Jan 2013 19:57:08 +0000 http://blog.softlayer.com/2011/#comment-45722 Wow, thanks for this very cool video on IPv6. I just got a VPS that gave me /64 IPv6 addresses and didn't quite understand what it meant. I found you guys through a google search for this and am so glad you spelled it out for me! Within even SoftLayer, how would one utilize even a few of these addresses? The only scenario I can think of is assigning a large number of IPv6 addresses to just one machine. But this wouldn't necessarily provide any sort of performance boost. It would just allow that one machine to be accessed via several different IPv6 addresses. Wow, thanks for this very cool video on IPv6. I just got a VPS that gave me /64 IPv6 addresses and didn’t quite understand what it meant. I found you guys through a google search for this and am so glad you spelled it out for me!

Within even SoftLayer, how would one utilize even a few of these addresses? The only scenario I can think of is assigning a large number of IPv6 addresses to just one machine. But this wouldn’t necessarily provide any sort of performance boost. It would just allow that one machine to be accessed via several different IPv6 addresses.

]]> By: IPv4 v. IPv6 – What’s the Difference? – SoftLayer Blog http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-42010 IPv4 v. IPv6 – What’s the Difference? – SoftLayer Blog Mon, 27 Aug 2012 19:30:16 +0000 http://blog.softlayer.com/2011/#comment-42010 [...] ago, Phil Jackson and I recorded a podcast-esque click-through of a presentation that explained the difference between IPv4 and IPv6 address space, and as a testament to the long-tail nature of blog posts, Internet Society’s Deploy360 Blog [...] [...] ago, Phil Jackson and I recorded a podcast-esque click-through of a presentation that explained the difference between IPv4 and IPv6 address space, and as a testament to the long-tail nature of blog posts, Internet Society’s Deploy360 Blog [...]

]]> By: Kevin Hazard http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-42007 Kevin Hazard Mon, 27 Aug 2012 15:42:01 +0000 http://blog.softlayer.com/2011/#comment-42007 Lennie, Thanks for sharing your thoughts! The HTML/CSS reference in the video was more of an "off-the-cuff" realization than a declarative statement, and I think you're right about that. We should have given an example of CIDR notation when we started explaining it, and now that you mention it, that omission is pretty glaring. It's been about a year since we made the video, so it's about time to refresh the content to make it even smoother ... We'll probably script it out a little more as well. I'm not sure whether Internet-enabled appliances like televisions and refrigerators use a standardized network configuration, but I'd certainly hope they're using NAT or self-assigned IPs behind a router ... With IPv4, providing a public IP address to each would be problematic, but with IPv6, it'd be less so. Lennie, Thanks for sharing your thoughts!

The HTML/CSS reference in the video was more of an “off-the-cuff” realization than a declarative statement, and I think you’re right about that.

We should have given an example of CIDR notation when we started explaining it, and now that you mention it, that omission is pretty glaring. It’s been about a year since we made the video, so it’s about time to refresh the content to make it even smoother … We’ll probably script it out a little more as well.

I’m not sure whether Internet-enabled appliances like televisions and refrigerators use a standardized network configuration, but I’d certainly hope they’re using NAT or self-assigned IPs behind a router … With IPv4, providing a public IP address to each would be problematic, but with IPv6, it’d be less so.

]]> By: Video: IPv6 addressing and why ISPs give out such huge blocks of IPv6 addresses | Deploy360 Programme http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-42004 Video: IPv6 addressing and why ISPs give out such huge blocks of IPv6 addresses | Deploy360 Programme Mon, 27 Aug 2012 14:18:18 +0000 http://blog.softlayer.com/2011/#comment-42004 [...] exactly how big IPv6 addresses really are, how they are structured and how they are given out. In their companion blog post, they explain the motivation for the video and a bit more [...] [...] exactly how big IPv6 addresses really are, how they are structured and how they are given out. In their companion blog post, they explain the motivation for the video and a bit more [...]

]]> By: Lennie http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-41955 Lennie Fri, 24 Aug 2012 20:54:05 +0000 http://blog.softlayer.com/2011/#comment-41955 I have some comments about this video: 1. In HTML/CSS #ffff is ignored, because the long notation is 6 characters (#ffffff) and the short nation is 3 characters (#fff). 2. When explaining CIDR notation, I would suggest next time to first show what it looks like to people. 3. How many Internet enabled TV use a publicly routable address ? They are probably behind a NAT or using 10.0.0.0/8 or so. So I doubt it would matter much for IPv4 depletion. I have some comments about this video:

1. In HTML/CSS #ffff is ignored, because the long notation is 6 characters (#ffffff) and the short nation is 3 characters (#fff).

2. When explaining CIDR notation, I would suggest next time to first show what it looks like to people.

3. How many Internet enabled TV use a publicly routable address ? They are probably behind a NAT or using 10.0.0.0/8 or so. So I doubt it would matter much for IPv4 depletion.

]]> By: boethius http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-39964 boethius Wed, 06 Jun 2012 05:56:22 +0000 http://blog.softlayer.com/2011/#comment-39964 Full adoption of IPv6 will almost certainly take many years but I think in the next 3-5 years we'll probably see logarithmic adoption as it will simply be a necessity if the Internet is to expand, as it surely will. There's also a huge amount of unused IPv4 space going out for sale on the open market. Many many providers and big corporations got massive IPv4 space allocations in the early days of the Internet and are only using a small fraction of it so even though IPv4 space is "exhausted" and IANA and other registries cannot allocate new IPv4 space there is still a ton that is not in use. There are many millions of legacy IPv4 devices - i.e. the millions of home wireless routers out here. That said many even basic home wireless routers released in the last year or two are IPv6 capable and corporate Cisco, Juniper, Huawei, Brocade, etc. routers have been IPv6-capable for several years now . Comcast is transitioning to IPv6 right down to the home cable modem and will tunnel IPv4 into IPv6. All or nearly all major backbone ISPs are fully IPv6 capable and probably running dual-stack IPv4/IPv6. Many enterprises are migrating their core networks to IPv6 and running dual-stack on their servers. Percentage-wise it's relatively small but it's happening. Full adoption of IPv6 will almost certainly take many years but I think in the next 3-5 years we’ll probably see logarithmic adoption as it will simply be a necessity if the Internet is to expand, as it surely will. There’s also a huge amount of unused IPv4 space going out for sale on the open market. Many many providers and big corporations got massive IPv4 space allocations in the early days of the Internet and are only using a small fraction of it so even though IPv4 space is “exhausted” and IANA and other registries cannot allocate new IPv4 space there is still a ton that is not in use. There are many millions of legacy IPv4 devices – i.e. the millions of home wireless routers out here. That said many even basic home wireless routers released in the last year or two are IPv6 capable and corporate Cisco, Juniper, Huawei, Brocade, etc. routers have been IPv6-capable for several years now . Comcast is transitioning to IPv6 right down to the home cable modem and will tunnel IPv4 into IPv6. All or nearly all major backbone ISPs are fully IPv6 capable and probably running dual-stack IPv4/IPv6. Many enterprises are migrating their core networks to IPv6 and running dual-stack on their servers. Percentage-wise it’s relatively small but it’s happening.

]]> By: Hriday Biyani http://blog.softlayer.com/2011/ipv6-blocks-slashes-and-big-numbers/comment-page-1/#comment-27272 Hriday Biyani Tue, 02 Aug 2011 19:28:08 +0000 http://blog.softlayer.com/2011/#comment-27272 Love the presentation and the geeky but lucid way the IPV6 concept has been explained to the uninitiated like me :) Can you also let me know why IPV6 adoption is slow. Are all ISPs and networking equipment not supporting IPV6 addresses yet? Hriday @diademtech Love the presentation and the geeky but lucid way the IPV6 concept has been explained to the uninitiated like me :) Can you also let me know why IPV6 adoption is slow. Are all ISPs and networking equipment not supporting IPV6 addresses yet?

Hriday
@diademtech

]]>