News for hackers. Stuff that matters.
Re:The Sheer Size of IPV6 by wmf on Monday March 09, 2009 @08:13PM (#509297)
The cost of migrating from IPv4 to IPvAndys is more or less equally huge as the cost of migrating from IPv4 to IPv6. If you're going to pay a huge migration cost, you might as well do a thorough job of it.
Re:The Sheer Size of IPV6 by derefr on Monday March 09, 2009 @08:59PM (#509348)
There is a really easy way to do it right now, that just involves recoding some drivers (no hardware needs to be changed): steal the port bytes from TCP and UDP and use them as two additional bytes of host address. No server is using all of its ports; turning them into addresses (and requiring a server to have as many addresses as it has connections open) would flatten the two spaces together, which seems almost elegant to me.
Re:The Sheer Size of IPV6 by tptacek on Monday March 09, 2009 @09:29PM (#509372)
You realize that if you did this, your computer could only ever open 256 concurrent outbound connections to a single host, right?

If you really were going to upgrade every router and switch on the Internet and port every single program that used the BSD sockets interface or the Win32 WSA Socket interface, and for some perverse reason you felt you needed a backwards-compatible frame format, you wouldn't break TCP or UDP to do it. You'd add a pair of IP options, called "source address extension" and "destination address extension".

But of course, you wouldn't do this, because if you're going to go through that much pain, you might as well get the full IPv6 address space.

Re:The Sheer Size of IPV6 by Andys on Monday March 09, 2009 @11:23PM (#509457)
I'm just not sure thats the case. IPv6 has too much of a 'design by committee' feel to it, which usually means it falls over as a standard in Internet land.
Re:The Sheer Size of IPV6 by tptacek on Monday March 09, 2009 @11:42PM (#509477)
What feels "design-by-committee" about IPv6 to you?