Slashdot Mirror
U.S. Government to Adopt IPv6 in 2008
IO ERROR writes "The U.S. Government is set to transition to IPv6 in June 2008, according to Government Computer News: 'In the newest additions to the IPv6 Transition Guidance, the CIO Council's Architecture and Infrastructure Committee has provided a list of best practices and transition elements that agencies should use as they work to meet the deadline. The latest additions, (MS Word) released in May, are a compilation of existing recommendations and best practices gathered from the Defense Department, which has been testing and preparing for the transition for years, the private sector, and the Internet research and development community.'"
That word document has 37 pages, 12,946 words, 74,666 characters, and 564 paragraphs. I think there's enough detail.
Wouldn't IPv6 basicly be deployed when 51%> adopt it? If the commercial world doesn't accept it then the goverment will be on it's own and that won't fly too well.
There's no place like ::1
hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
I'm curious as to whether there are any reliable stats out there about the availability of IPv4 address space and how it has changed over time. The widespread adoption of hide-mode NAT has allowed companies, universities and the like to move thousands of computers out of the public address space, freeing up large blocks of public address goodness. Cripes when I think about what I got away with in university, hooking my desktop up to the local LAN, getting a public and ........
CommentBot 0.7a running with args "-module irritate,disagree -target random"
As the CIO Council and Office of Management and Budget help map out the June 2008 transition to IP Version 6, perhaps the biggest challenge is that they're entering unfamiliar territory.
In the newest additions to the IPv6 Transition Guidance, the council's Architecture and Infrastructure Committee has provided a list of best practices and transition elements that agencies should use as they work to meet the deadline.
So the government has a year-and-a-half to meet this deadline? Forgive the cynicism, but given that they have a loose set of guidelines and so many systems that would need conversion, I think they're being a tad optimistic. Kudos for trying this, but I won't be surprised when it takes until 2010.
GetOuttaMySpace - The Anti-Social Network
I haven't had the time yet to read over the specs and try to figure out what the downsides and hassles for the rest of us will be with IPv6, but I'm sure there are slashdotters out there who have taken the time to figure out where the problems and issues are.
If those of you out there who understand those issues could make a few posts here I would greatly appreciate it.
Thank you.
This is a big step forward for IPv6 adoption, but I think the next major step will be by the cable companies. They want every set-top-box or cable TV to have two way communication and be fully addressable. Where else would they get the address space needed for that? IPv6 solves a lot of the problems they have with addressing that may devices. That will probably be the first way IPv6 gets into most of our homes.
Digitac
Anyone not having access to an IPv6 network, say because you are behind a NAT, and are wanting to try out IPv6, because it is in your blood to do so, I recommend giving Miredo a go. If I suggest this one over other solutions, is because of the number of platforms supported (including, Linux, Windows, MacOS X, BSD). There is Freenet6, but it won't work from behind my NAT with MacOS X.
Jumpstart the tartan drive.
If this transition goes anywhere near as well as that time the US Government resolved to convert the US to the metric system in the 1970s, then... well, we'll all have a lot more time to play solitaire.
Slashdot Burying Stories About Slashdot Media Owned
I don't know what IPv6 is but I'm assuming because it is on Slashdot and it involves the government I should be against it.
Now if only someone would slap around ComCast and get them using IPv6 natively.. or all USA ISPs for that matter.. There is zero choice for native IPv6 where I live unless I want to colo @ Hurricane Electric :(
-=[ place
The good news: long term, I think IPv6 is desirable. Thus, I like seeing a large organization pave the way. Let them get the kinks out. Let them find out what all goes wrong. Let them blaze the trail so we can ride on their coattails. Let them incur the big expense.
The bad news: Wait a minute. "Them?" Oh shit, it's the US government. I'm a US citizen. Argh, that's my expense. D'oh!
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
It's the new, boosted, PATRIOT Act: Intellectual Property version 6
Swedish plasma phys. PhD student; MSc EE; knows maths, programming, electronics; finance interest; seeks opportunities
You think that's bad. This article mentions getting info to transition to it from the US DoD....and this /. article is the first time I've heard anything about the DoD pushing to transition to IPv6!!!!
Heck...we're rebuilding systems from scratch in some cases post Katrina, and yet nothing is mentioned to us about trying to do anything with IPv6.
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
I hope it goes more efficiently than our switch to the metric system.
I remember when the government mandated the switchover from TCP/IP to ISO protocols. The acronym for that was GOSIP.
Computer industry vendors spent serious money preparing for the August 1990 adoption deadline.
They had to implement the ISO protocols or risk not being able to sell their systems to the government (always a major customer).
The revised date for adoption is never.
The worst part about doing government contracts was dealing with all the folks that say:
"We can't design this around TCP/IP, the government is mandating ISO."
"We can't solve problems by using the same kind of thinking we used when we created them." -- Albert Einstein
yes, the US Gov't has lots of IPv4 addresses, but the number available to everyone else is shrinking rapidly. By switching to IPv6, every man, woman, child, dog, piece of field ammunition, toast, individually wrapped piece of butter, and toy car will have an IP address. Sometimes, rarely, but sometimes, the Government works for the people. :P
Non impediti ratione cogitationus.
Which firewalls can currently be used to filter, log, and block ipv6 traffic?
IPV6 definitely has been around for many years now, but none of the windows firewalls I've downloaded seemed to have any kind of configurations for logging or filtering ipv6. Sure that's 2 years away, but unless I overlooked a firewall (there are so many for windows) or they use some kind of open source package that probabbly has ipv6 firewall capability already. i have to wonder how they're going to keep secure.
https://www.gnu.org/philosophy/free-sw.html
I suspect this will be about as successful as the DOD's old policy of only doing development in Ada. Let the waiver requests begin!
The Army reading list
Not to mention they'd piss off a bunch of home users who would have to replace all their equipment (routers and such) with IPV6 hardware. There's probably a lot of people still running OSes that don't support IPV6.
Where did DavyGrvy mention turning off IPv4? They work together, you know. Do even Slashdotters not understand that adding IPv6 to a network does nothing to reduce IPv4 connectivity? It's win-win.
IPv6 tunnels over IPv4. IPv4 tunnels over IPv6. Machines running IPv4 can talk to machines running IPv6. Machines running IPv6 can talk to machines running IPv4.
IPv6 still has issues, to be sure, but interoperability with IPv4 isn't one of them.
Socialism: a lie told by totalitarians and believed by fools.
Interest in IpV6 has stagnated since 2001.
y =ipv6_meme_flatlined_for_five
If the U.S. Government is about to push a major IpV6 initiative, there could be some money to be made here.
http://www.realmeme.com/roller/page/realmeme?entr
Of course this is all theoretical because large chunks of the address space are "wasted" - no, scratch that, read "used" - to prevent fragmentation, i.e. end users always get a /48 network. The smallest subnet is /64 etc.
/29 net or a /24. Two /29 users could be adjacent and have their first 3 octets of the address match. This complicates routing, because this simple example already doubles the routing table at the upstream router.
/104 networks in IPv6 and still have plenty of addresses. But it's specifically not done for the above reasons.
With IPv4 there are users who could have a
With IPv6 you take the first 48 bits and those always point to a unique end user. Any smaller subnet is going to be handled by this user's router, so routing tables just became a lot smaller, even if the addresses are four times as large.
This "anti-fragmentation" of course consumes chunks of address space without using every one of those addresses. Of course users could do with, for example,
Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
Given how many problems with IPv4 this new revision solves and that a thorough look was taken at the protocol in its entirety, of all things, I'm surprised *geeks* usually just try to find reasons to not like it. Sure, admins may need to retrain, and there'll be infrastructure costs, but since when did geeks stop looking at positive evolution as being bigger than these things?
There's also always a lot of FUD spread around this matter, and one can find it even in this topic, for example IPv6 increasing routing complexity. IPv6 uses hierarchical address ranges *and* is modularized so there's not just less complexity, but even less *traffic* to route unless using more advanced features of IPv6. After the transition, IPv6 is better for your routers.
NAT's also seem to be a common enough argument against IPv6 that someone should have written a damn "Why NAT's won't solve address space issues" FAQ to uninformed people already. There is something similar enough for that though.
Anyway, instead of just ranting, here's a document about some of the changes IPv6 makes. Maybe especially this part is educative to some.
Beware: In C++, your friends can see your privates!
My favorite part is when I heard about IPv6 in college, they had calculated that there would be enough addresses for 10 IPv6 devices for every square foot of the planet!
:) You'll forgive me for not carrying more significant digits around.
Oh, goodness me, are you ever off. Earth's area is 5.1e14 square meters. 2**128 ~= 3.4e38. 3.4e38 / 5.1e14 = 6.7e23 IPv6 addresses per square meter. For square feet, call it 6e22 addresses per square foot. (1 square meter's pretty close to 10 square feet.)
So, you're off by a about 21 and a half orders of magnitude. That's not even close by astronomical standards.
See this mailing list message, which points to this PDF presentation.
I could do that for www.sixxs.net, www.kame.net and every host that already has IPv6 connectivity. So "we" are not getting anywhere with IPv6 because it doesn't work because the big sites don't bother because IPv6 isn't anywhere yet. Nice way to get nothing done ever.
If I send my buddies e-mail, most of the time everything is IPv6 only, including DNS lookups, although DNS transport over IPv6 isn't really common yet.
Some people are indeed sitting on IPv6 and wondering when the rest will follow.
Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6