So, when everything's on IPv6, and you want to play an IPv4-only game, you'll first have to establish an IPv4 VPN between the players? I suppose that sounds feasible, but someone will have to write the software to make it easy.
It's difficult to manipulate binary digits in hexadecimal, too. I don't see any advantage to this.
Every hex digit represents exactly 4 binary digits. If you flip a bit in a hexadecimal number, then exactly one hex digit will change. To know how it will change, you only need to remember the binary values of 0-F.
With decimal, you could flip a bit and change every digit in the number.
Hexadecimal is used because a network is designated by an N-bit prefix, and it's *much* harder to manipulate bits in decimal, especially when each number is 16 or 32 bits long.
And using the colon for address separation is equally as stupid since that is how we designate port numbers.
Once you've gone to hexadecimal, using dots to separate the address leads to ambiguity. Is a.b.c.d.e.f.beef.de an IP address or a hostname?
it is pretty much unrememberable
With IPv6, your network will have its own 48 to 64-bit prefix. Once you remember that prefix, you can choose your suffixes to be as simple as you'd like.
you omit parts of the address... but ONLY once!
You can only omit one run of zeros, because otherwise the length of each run would be ambiguous.
When IPv4 was first developed, subnets were only allocated on 8-bit boundaries. Since CIDR rolled out in the 90's, the subnet length is now arbitrary, and working with subnets requires doing tedious decimal-binary conversions in your head. It's a mess.
IPv6 uses hexadecimal, because a hex digit represents exactly 4 bits. This makes the CIDR math really simple.
Now, what if we used hex with dots? Is a.b.c.d.e.f.beef.de an IP address or a hostname? Hell if I know. That's why we use colons now.
And the second approach (a reverse SSH tunnel) only works if you have that server at work with a public IP. What happens when you want to connect to your friend's computer, which happens to be behind a different ISP's NAT, or even an overlapping RFC1918 space within the same ISP?
You basically have to lease a public IP on a server somewhere, to accomplish things that should be trivial.
This method would actually have worked if the people who made IPv6 hadn't decided to make the standard backwards incompatible.
How would you propose to make IPv6 backwards compatible? How can a device that only understands 32-bit addresses send a packet to a 128-bit address, and what problem would it solve that NAT64 doesn't?
As it is, IPv6 must be run in dual-stack mode, which means that even if you've got an IPv6 address, you must also have an IPv4 address.
The raw 2**128 number sounds impressive, but it's mostly meaningless, since each customer is assigned somewhere between 2**64 and 2**80 addresses. In practice, IPv6 supports maybe 64K times as many users, but each user can now have an ~unlimited number of devices.
Slashdot Mirror
AT&T has more IPv6 users than any other ISP in the world:
http://www.worldipv6launch.org/measurements/
Granted, it's all based on 6rd, but you can't say they're not trying.
I'll rent you a solar system for only $1,000/day, but you'll need to find your own transportation.
Weld the cables? Are you insane? Those things must cost thousands of dollars.
Brilliant, then you need to deal with half hours every time you convert to/from UTC.
If all you need is a backup set of optics, just make the pilots wear an eyepatch.
You forgot "mother". Incidentally, I'm telling her you said a bad word.
So, when everything's on IPv6, and you want to play an IPv4-only game, you'll first have to establish an IPv4 VPN between the players? I suppose that sounds feasible, but someone will have to write the software to make it easy.
You do realize that the ISPs would be the ones doing the prioritizing, right?
Most people are probably going to be happy using browsers that have both codecs
Which browsers would those be? I thought Chrome was the only one with both WebM and H.264.
It's difficult to manipulate binary digits in hexadecimal, too. I don't see any advantage to this.
Every hex digit represents exactly 4 binary digits. If you flip a bit in a hexadecimal number, then exactly one hex digit will change. To know how it will change, you only need to remember the binary values of 0-F.
With decimal, you could flip a bit and change every digit in the number.
You listed 17 /8 blocks in your post. If you managed to reclaim every single one of those, you'd almost make up for IANA's 19 allocations in 2010.
And let us know how it goes when you try to take those addresses from the US military.
Using a hexadecimal address was pure stupidity.
Hexadecimal is used because a network is designated by an N-bit prefix, and it's *much* harder to manipulate bits in decimal, especially when each number is 16 or 32 bits long.
And using the colon for address separation is equally as stupid since that is how we designate port numbers.
Once you've gone to hexadecimal, using dots to separate the address leads to ambiguity. Is a.b.c.d.e.f.beef.de an IP address or a hostname?
it is pretty much unrememberable
With IPv6, your network will have its own 48 to 64-bit prefix. Once you remember that prefix, you can choose your suffixes to be as simple as you'd like.
you omit parts of the address ... but ONLY once!
You can only omit one run of zeros, because otherwise the length of each run would be ambiguous.
But small children will naturally become taller over time. Why are we mandating a technical solution for a problem that solves itself in 10 years?
When IPv4 was first developed, subnets were only allocated on 8-bit boundaries. Since CIDR rolled out in the 90's, the subnet length is now arbitrary, and working with subnets requires doing tedious decimal-binary conversions in your head. It's a mess.
IPv6 uses hexadecimal, because a hex digit represents exactly 4 bits. This makes the CIDR math really simple.
Now, what if we used hex with dots? Is a.b.c.d.e.f.beef.de an IP address or a hostname? Hell if I know. That's why we use colons now.
Precisely. Now whose side are you on?
And the second approach (a reverse SSH tunnel) only works if you have that server at work with a public IP. What happens when you want to connect to your friend's computer, which happens to be behind a different ISP's NAT, or even an overlapping RFC1918 space within the same ISP?
You basically have to lease a public IP on a server somewhere, to accomplish things that should be trivial.
Manufactoria - http://pleasingfungus.com/
Best programming-related Flash game ever.
This method would actually have worked if the people who made IPv6 hadn't decided to make the standard backwards incompatible.
How would you propose to make IPv6 backwards compatible? How can a device that only understands 32-bit addresses send a packet to a 128-bit address, and what problem would it solve that NAT64 doesn't?
As it is, IPv6 must be run in dual-stack mode, which means that even if you've got an IPv6 address, you must also have an IPv4 address.
T-Mobile disagrees. They're deploying an IPv6-only NAT64 network as we speak:
http://groups.google.com/group/tmoipv6beta/web/t-mobiles-technical-architecture
The actual number of addresses is a red herring, since every user will be assigned between 2^64 and 2^80 addresses.
For all practical purposes, IPv6 supports about 64K times as many users, but each user can have an unlimited number of devices.
So does anyone have an actual link to an example of the player? That seems like a rather blatant omission from the article.
The raw 2**128 number sounds impressive, but it's mostly meaningless, since each customer is assigned somewhere between 2**64 and 2**80 addresses. In practice, IPv6 supports maybe 64K times as many users, but each user can now have an ~unlimited number of devices.
and we've run out of ipv4 addresses "in about a year" for the last decade or so.
[citation needed]
You're technically correct, but the mob has spoken. Just call your 3D "holographic" and get on with your life.
You can deploy an IPv6-only network where the clients can still connect to IPv4-only servers.
It's called NAT64:
http://tools.ietf.org/html/draft-ietf-behave-v6v4-xlate-stateful
Isn't a carbon nanotube just a rolled-up strip of graphene?