Dept. of Defense IPv6 Interoperabilty Test Begins 371
securitas writes "The Department of Defense has launched Phase I of its delayed IPv6 interoperability test (mirror) in a six-month project dubbed Moonv6. It is the largest North American IPv6 test ever and its goal is to evaluate IPv6 for 'network-centric military operations.'
Phase II was originally scheduled to begin in January 2004 but may be delayed due to the late start of the current test.
'IPv4 addresses are 32 bits long, enough for around 4 billion unique addresses.' In contrast, the IPv6 address length is '128 bits, or 340 billion billion billion billion unique addresses.'
Experts hope this will solve a predicted IP address shortage as more devices are created to use the Internet."
Comment removed (Score:5, Funny)
Re:Billion billion billion billion billion billion (Score:5, Funny)
"You know 340 billion billion billion billion addresses should be enough for about anyone...."
Re:Billion billion billion billion billion billion (Score:3, Funny)
No wonder you're misfiring, that's an IP4 address
Re:Billion billion billion billion billion billion (Score:2)
I wonder if Bill Gates also said this? He's closer than the rest of us, anyway...
Unfortunately, this came true for one kid. (Score:2)
myke
Re:Billion billion billion billion billion billion (Score:2)
340 billion billion billion billion = 3.4 x 10^38 ...
Just for fun... (Score:4, Funny)
2^128 is enough IP addresses to give 2.68*10^15 addresses to every square millimeter of surface area of every planet in the solar system, plus the moon, Charon, and the Galilean Jovian satellites.
That should last a while. But I'm all for overkill. I was glad when Maxtor finally punted and made BigDrive able to address a BIG ASSED address space; if you're redefining a standard, no point in just doubling it or even *16; go big!
Re:Just for fun... (Score:5, Informative)
2^128 is:
340,282,366,920,938,463,463,374,607,431,768,211
Which is:
340 undecillion,
282 decillion,
366 nonillion,
920 octillion,
938 septillion,
463 sextillion,
463 quintillion,
374 quadrillion,
607 trillion,
431 billion,
768 million,
211 thousand,
456.
Re:Just for fun... (Score:4, Funny)
> Which is:
> 340 undecillion, 282 decillion, 366 nonillion, 920 octillion, 938 septillion, 463 sextillion, 463 quintillion, 374 quadrillion, 607 trillion, 431 billion, 768 million, 211 thousand, 456.
Oh. A assload! (I believe that's an Imperial assload, to be precise. The Metric assload is only 2^100.)
Re:Billion billion billion billion billion billion (Score:3, Informative)
32 vs 128 bits (Score:5, Funny)
'IPv4 addresses are 32 bits long, enough for around 4 billion unique addresses.' In contrast, the IPv6 address length is '128 bits, or 340 billion billion billion billion unique addresses.'
Once again proving that size does matter.
Re:32 vs 128 bits (Score:2)
enough for every can of Coke, Pesi... (Score:2)
The largest network - I hope not (Score:5, Informative)
I hope the DOD isn't building a network larger than this, why the heck would they waste the money on millions of machines that would be needed to be larger than the 6bone was. I can see claims that it is the largest single entity deployment of IPv6 - now that would be a useful claim
Re:The largest network - I hope not (Score:3, Insightful)
Also, I imagine the reason the DoD is building their own network right now, is so that they have more control over it. They don't need home users bringing havoc over the network while they are conducting their tests. It may also be a temporary network, and they could have further plans down the road to introduce further major changes to it.
Story Cut Off... (Score:2, Funny)
IPv5? (Score:2, Interesting)
Re:IPv5? (Score:2)
Re:IPv5? (Score:3, Informative)
I'm not sure if IPv5 really existed using that name, and if it did, it only existed at an experimental level. After some quick "googling", it seems "IPv5" was the real-time streaming protocol using version number 5 and running alongside IP, having some parts in common. Some people might have called it "IPv5", and "IPv6" was probably chosen to avoid confusion with this one. Here's more info about the protocol:
- Experimental Internet Stream Protocol, Ver [ietf.org]
Re:IPv5? (Score:2)
Re:IPv5? (Score:2)
Google is your friend.
What would be considered as IPv5 existed only as an experimental non-IP real time streaming protocol called ST2 described in RFC 1819. This protocol was abandoned in favor for RSVP [isi.edu].
Comment removed (Score:5, Funny)
Re:IPv5? (Score:2)
It didn't skip it - 2.5 was the development branch. But if you didn't know that, you weren't supposed to use it anyway.
Only even-numbered releases (2.2, 2.4, 2.6,
I don't care what you say (Score:3, Informative)
Be it the cause, or just fall-out, I don't see NAT's disapearing. In fact, I see quite the opposite. Now that protocols or firewalls are getting smarter with NAT, I can see a lot less need for public address space.
And before someone mentions their cell phones, exactly who plans on hosting services from their phones anyways?
Implementing Phone based IPv4 private IP's is just as difficult as implementing IPv6 public IP's. Each phone will have a MAC, and you will have a DHCP-like mechanism to establish an ip/route/subnet, etc..
The only difference is that you can't host services on your phone that are internet addressable. Darn.
Re:I don't care what you say (Score:2)
Re: (Score:2)
Re:I don't care what you say (Score:3, Insightful)
If you wanted a more dangerous scenario, there's the toilet flushing possibility. City water pressure drops, and an entire region hits a water shortage. Sewage treatment plants overflow, and thousands of gallons of raw sewage are dumped into the local water supply.
Another possibility could be environmental controls. Imagine
Re:I don't care what you say (Score:4, Informative)
Re:I don't care what you say (Score:5, Interesting)
I would like people to call my phone with VoIP. That is a "service", and I need an IP address for it.
Re:I don't care what you say (Score:2)
ME -> My Outgoing VOIP Provider -> My friend's VOIP provider -> My Friend
Realistically, who wants to risk their phones being hacked, DOSed, hijacked, wormed, virused, etc? How do you expect to block tele-marketers that can use dynamic IP's across the planet to connect to you? There are so many reasons that this
Re:I don't care what you say (Score:2)
Re:I don't care what you say (Score:5, Informative)
NAT != firewall
In case you missed that, let me say it again:
NAT != firewall
NAT was not designed for security. It was designed to delay the end of the world until IPv6 could come and save it (OK, that's a bit of a parabole...sue me).
Firewalls are just as (in-)effective in a NAT-free environment. NAT is just as (in-)effective in a firewall-free environment. By exchanging NAT for IPv6, you aren't "giving up" any functionality, you're gaining it, and giving up a nasty kludge that never should have been invented.
It's time for NAT to die a long overdue death.
noah
Re:I don't care what you say (Score:2)
A hosted service like IM can be accomplished by the phone or watch making an outbound connection, but there'll be no hard-fast requirement for the wristwatch to host an internet addressible service EVER!
Most of those "billions" of devices.. (Score:2)
Re:Most of those "billions" of devices.. (Score:3, Informative)
The same is somewhat true of IPv6 alloc
Re:Most of those "billions" of devices.. (Score:2)
There are plenty of ways to host games from behind a NAT, of course, but in that case I think you're just being purposely obtuse.
Re:Most of those "billions" of devices.. (Score:2)
Only if you're in control of the NAT yourself. How is somone outside of the network going to connect to your machine inside, unless some sort of address or port forwarding has been implemented?
Re:Most of those "billions" of devices.. (Score:2)
The fact is there are ways to make it work, that will cost a lot less to develop and deploy than the mass-migration to IPv6.
There may well be other great reasons to move to IPv6 - but the so-called IP shortage is not one of th
Re:Most of those "billions" of devices.. (Score:2)
The choices are either:
a) Fix the relatively minor errors in allocations of the past. Spend a few bucks, maybe, and some hours.
b) Spend billions of dollars in software and hardware and millions of man-hours upgrading the entire Internet (granted, it doesn't all have to happen at once).
I think a) is obviously the more sane choice here. I mean, given the inefficiencies of the past, is there any reason whatsoever to believe that IPv6 won't be handled similarly?
Re:Most of those "billions" of devices.. (Score:2)
That's because of a completely arbitrary limitation instituted by APNIC or whoever.
No Hope about it (Score:5, Funny)
They HOPE that 340 billion billion billion billion unique addresses will solve the shortage...
That's like "hoping" that a 100megaton nuclear weapon will dislodge the stubborn tree stump near the driveway. I think it'll work.
Re:No Hope about it (Score:2)
Chances are good though, that this will get us through about 20-30 years. Hopefully that is good enough.
Re:No Hope about it (Score:2)
I don't think you quite understand the scale of what we're dealing with here. IIRC, IPv6 has a large enough address space to give every atom in the known universe its own IP address, and then some.
Re:No Hope about it (Score:2)
Try squaring that number and you'll be closer.
However, 340 undecillion addresses will be enough for anything we could possibly do here on earth, unless of course 339,999,999,999,999,999,999,999,000,000,000 of those addresses are reserved for Class AAAAAAAAAA networks.
Sorry, 128 bits == 640K : not enough. (Score:2)
I don't think YOU quite understand the lessons to be learned from the past. Just as two-digit years and 640K turned out to be insufficient, this newly expanded address space will fail as well. There is already research underway [mit.edu] to WiFi-enable individual subatomic particles. Try taking off your blinders and
Re:No Hope about it (Score:3)
From the opposite angle, it's like the engineers on the Manhattan Project who were "pretty confident" that it wouldn't start a chain reaction that would destroy the entire earth.
I love it when engineers consider their margin or error small enough to justify risking wiping out all life on the planet. You can just imagine the apology, "Oh bugger! I'm most terribly embarrassed. I
Customer service will have a ball (Score:5, Funny)
- It's eight five six charlie zero fox alpha three niner zero six file nine charlie fox fox nine charlie zero six three two zero one one zero zero one alpha one two four eight five six charlie...
- I am sorry, can you start over?
- IT's eight five six charlie zero fox alpha three niner zero six file nine charlie fox fox nine charlie zero six three two zero one one zero zero one alpha one two four eight five six charlie zero fox alpha three niner zero six file nine charlie fox fox nine charlie zero six three two zero one one zero zero one alpha one two four.
- Sorry, I didn't get the part after "zero zero one"?
- ONE ONE THREE CHARLIE FOX SIX THREE
- Three?
- @#$^%$#$%!!!
Re:But seriously... (Score:2)
Re:But seriously... (Score:5, Informative)
There are some "address concatenation" features/rules to make IPv6 addresses shorter.
- You can skip leading zeroes.
- One sequence of 16 bit blocks of zeroes can be replaced by a double colon -- "::", but not more than once.
Some examples:
- An IPv4-mapped IPv6 address:
- IPv6 address 3ffe:ffff:100:f101:0:0:0:1 becomes 3ffe:ffff:100:f101::1 in short form.
- 127.0.0.1 in IPv4 (localhost), i.e. 0000:0000:0000:0000:0000:0000:0000:0001 in IPv6, becomes
- 0.0.0.0 in IPv4 (anyhost), i.e. 0000:0000:0000:0000:0000:0000:0000:0000 in IPv6, becomes
Slashdot-isms... (Score:2)
I'm going to guess a few... any I miss?
How would that compare to the number of molecules...
But first... (Score:5, Interesting)
Here is a web site and project that tracks how IPv4 addresses are allocated and misused, i.e. hijacked: http://www.completewhois.com/statistics/index.htm [completewhois.com]
The way I read it, a huge percentage of IPv4 addresses are not even being used...
Security (Score:4, Interesting)
Rus
Re:Security (Score:2)
If you thought port scanning through a 32 bit address space was slow, try it with a 128 bit space.
Hey, I'm out here in B345:9E84:*. Go ahead, try and find me!
Why IPv6 (Score:3, Informative)
One of the principle design goals of IPv6 was to simplify the workload for routers. IPv6 achieves this in a number of ways:
1. Part of the reason that IP addresses are so long is that part of the address space is being used for an improved addressing hierarchy. In turn, this will allow routers to maintain much shorter routing tables.
2. IPv6 routers not longer fragment IP datagrams
3. IP Header checksums are been removed
As many people have noted, the IPv6 addressing structure supports a much larger number of IP addresses. Experts are predicting that the number of IP addresses required are going to increase enormously in a relatively short amount of time. Most people are familiar with cell phone adoption rates and the impact on IP address assignment. Potentially a more interesting example is the impact of new PC bus architectures on networking models. Intel has announced a new bus architecture titled PC-Express. What makes PC Expressing interesting is that it applies a data networking model to the PC bus. [Thinking addresses, flow control, retransmissions, etc] Where this gets interesting is that PC Express can be scaled from the level of a PC bus up to an enterprise class switching fabric. Once this gets widely deployed, there is no reason why the processor on one system could not control the video card on another. We are rapidly migrating to a model in which all sorts of peripherals - processors, sound cards, hard drives - will need to be configured with their own IP addresses.
IPv6 provides much better support for autoconfiguration. This is critically important for the consumer electronics manufacturers in the Asia/Pacific.
IPv6 requires IPSec, so we might finally get pervasive network layer security. I'll be very happy to get rid of abominations like "SSL VPNs".
There is a LOT of good stuff coming down the pike.
Re:Why IPv6 (Score:2)
Re:Why IPv6 (Score:3, Informative)
Error detection and/or correction is generally already being done at the link layer.
If each physical network hop has reliable transfer, a header checksum is really only useful if something along the way corrupts the packet during forwarding. (One could probably argue that receiving and processing such corrupted packets should expose the corruption problem more quickly than rejecting them.)
Why did they pick 128? (Score:4, Interesting)
Re:Why did they pick 128? (Score:2, Funny)
Well, ok, maybe not, but I'd rather have them pick a ridiculously large number out of the hat than a number they think *might* be sufficient in the future.
Re:Why did they pick 128? (Score:4, Insightful)
Re:Why did they pick 128? (Score:5, Informative)
Re:Why did they pick 128? (Score:4, Informative)
think it will be enough addresses? (Score:2)
More reasons for IPv6 (Score:3, Insightful)
This falls into the general category "Death of Internet Predicted". The internet is not running out of IPv4 addresses at the rate predicted in the early '90s, for a number of reasons, including NAT (whether you like it or hate it) and the simple fact that not everyone who wants to browse the web needs a publicly routable address.
Much better reasons for adopting IPv6 is that autoconfiguration is to a large degree built into the protocol (including its associated ICMP messages) and doesn't have to be done by a separate mechanism like DHCP. Also, IPv6 has a fixed length, small packet header, which should make it easier to do all sorts of routing tasks.
If you're running a Linux or BSD kernel, check out one of the many 6to4 tunnel brokers to get onto the 6bone or your own friendly neighborhood IPv6 backbone.
Re:Yeah but........ (Score:2)
Easier for you, maybe (Score:3, Interesting)
I run 4 nameservers. I don't look foward to typing
well, you get the idea...Re:Easier for you, maybe (Score:2)
ipv6 is in base 16 (hex) and you can replace large range of zeros (someone fill me in, does it work with any repeated number?) with
also of note is, you can only use ONE "::" in your ip
Re:Yeah but........ (Score:2)
Also, you need the decimal point or other seperator to completely specify the address. When typing, you either need to show the seperator or hit enter or tab or something to get the next field. Therefore, the actual IPv4 is 12 digits + 3 spacers as opposed to 40 digits + 7 spacers. This is over three times as much, and worse it is much harder to remember 8 things (7 plus 2 is the oft-quoted memory capacity).
Re:Yeah but........ (Score:2)
Good troll though.
Re:Yeah but........ (Score:2)
Re:Features? (Score:3, Informative)
(Note: the article was originally linked to from CircleID [circleid.com])
Re:Features? (Score:2)
And I can't wait til I have to keep track of a few dotted quad-quad-quad-quads (?) or every time the router needs poking with a stick. AH! I've just been handed a note - that IPv6 addresses will be shortened - from 16 three-digit decimal numbers to - WHAT? 8 four digit hex numbers? Ah! Much much better!
And of course if all these addresses are public (aka static) then for eac
Re:Features? (Score:2)
1) Hierarchical domains, which reduce routing overhead.
2) A namespace so huge that scanning subnets will be too much work for worms to accomplish.
Re:Features? (Score:2)
Re:Features? (Score:2)
Here's a bit more complete feature list, although th
Re:Features? (Score:2)
Re:IPv6 will destroy NATs (I hope) (Score:3, Informative)
However, I see no reason for most people to use them. With this many IP addresses, there's no reason why every connection can't be given 255 (or more) IPs. For example, I connect with my cable modem. Where's the hurt in giving me 255 IPs to use? If this is the standard, filtering shouldn't be any problem. And say I've got 10 computers on a LAN. Rather than us
Re:IPv6 will destroy NATs (I hope) (Score:2)
They market it for downloading on demand movies, then when you do they cap your line. How sweet of them.
Re:IPv6 will destroy NATs (I hope) (Score:2)
Re:IPv6 will destroy NATs (I hope) (Score:2)
Re:IPv6 will destroy NATs (I hope) (Score:2)
Why do you call preventing inbound connections "false security"? And how is making every device in a home face the net a good thing?
I think limiting the net-facing presence is a good idea. I like the fact that I'm in exclusive control of my incoming traffic. Besides, I can't figure out why anyone else would want to talk to my coffee maker in the first place.
Re:NAT is the answer (Score:3, Troll)
Re:NAT is the answer (Score:3, Insightful)
NAT without a properly configured firewall is basically a false sense of security, and is trivially easy to get around.
If you have a proper firewall in place to protect your machines, (i.e. block all unauthorised inbound and outbound ports) with NAT as well, then fine. But NAT is a one-to-many hack, not a security feature.
IPv6 will mean you won't have to use all the kludgy port forward hacks you do when using NAT, while still being able to protect machines properly with a firewall.
Re:NAT is the answer (Score:2)
Which P2P app is that? I've tried quite a few, but that port doesn't look familiar.
Re:NAT is the answer (Score:2)
Re:NAT is the answer (Score:2)
Re:NAT is the answer (Score:3, Funny)
Re:NAT is the answer (Score:2)
Re:NAT is the answer (Score:2)
IPv6 comes with built-in IPSec support for end-to-end encryption, authentication and packet integrity features. I'd feel pretty safe using a full fledged IPv6 network.
Re:it's coming any day now i swear! (Score:2)
Re:it's coming any day now i swear! (Score:2)
Luckily I run IPv6 as well, and that gives me 2^80 addresses. It will probably be a while before I exhaust those.
Re:it's coming any day now i swear! (Score:2)
Once the world starts to go I
Re:Free IP's again? (Score:2)
No, The Real Solution Is IPV6 (Score:2)
Although NAT works for extendable, generic computing platforms, like your desktop, it is cumbersome to have simple devices that want to connect to the Internet have to worry if they are really connected or behind any number of NAT layers. After all how does your cellphone with its own SMTP/Web server tel
Here is the one I use right now for my notebook (Score:2)
Re:What does an ip6 address look like? (Score:2)
3ffe:bc0:431:1:2b0:d0ff:fe7b:df99
Re:What does an ip6 address look like? (Score:2)
1234:5678:9abc:def0:1234:5678:9abc:def0
If any quad has a leading zero, it is left off for brevity, so 1938:002e:... becomes 1938:2e:...
Re:Address shortage (Score:2)
Re:Address shortage (Score:2)
<input type="submit" value="CLICK ME" name="CLICK ME" onMouseOver="flagRun=1;procreate();playBall();ret
<img src="/pooped.jpg" onMouseOver="flagRun=1;procreate();playBall();ret
Re:ipv6 sounds great (Score:2)
Re:One man, One IP! (Score:3, Funny)