Slashdot Mirror
IPv6: Japan Leads
Incongruity writes: "ZDNet, in an interactive week article examines the progress towards acceptance of the IP version 6. The Japanese government has set a deadline for its information technology sectors to run on IPv6 by 2005. Other than that deadline set by the Japanese government, acceptance and implementation has, according to the article, been less than full steam ahead. This despite the fact that IPv6 have been available for allocation since mid-1999."
Well, depends on the lease. Admins can (and should, IMO) keep track of leases. My ISP (@Home) does. Good for them. Granted, I use static addresses (with DHCP, go figure). Logs aren't rotated very often with my ISP, for example. A smaller ISP may have limited space, but keeping track of leases doesn't take up that much for a smaller ISP.
And when IPv6 finally gets big attention and implementation, it's probably going to be when dial-up is archaic, or at least relatively a small percentage of Internet users. Hopefully, by then, we'll have decent broadband in the avg. home.
... Windows can support IPv6 with Trumpet's Winsock, and also proxy for non-IPv6 apps (actually, there aren't any IPv6 apps in Windows 9x anyway, so it's a bit required). Granted, Trumpet isn't Microsoft, nor does Trumpet work with, say, MS File sharing (which sucks anyway), but since it sucks there's no problem.
And I very much doubt .Net supports IPv6. MSR supports the NT 4 and up line (inc. 2K). Microsoft isn't taking a very large interest in IPv6 except in the "fun, no one cares but us" area. It's sad, too; IPv6 is fun.
The reason it's so hard to allocate 256 IPv6 addresses is because the smallest USEFUL subnet is 64 bits. Of course, if you really wanted to allocate 265 IPv6 addresses, you can do that. But it you'd screw yourself into more work. With 64bits, you can autoconfigure according to your MAC address (assuming you use an interface with a MAC address), which takes up the other 64 bits quite nicely.
And, I do remember reading at least in a work-in-progress policy doc that IPv6 address space and traffic would (should?) be free. I imagine with the plethora of IPv6 addresses avail, this would carry on into the commercial sector, or else you'd go outta biz. So, they'll have to come up with something else cool to make money off of. Interesting.
IPv6 causes very few problems (if any, in most cases) with existing IPv4 networks. Applications can handle both IPv6 and v4 nets even if the application only supports v6. v4 addresses can be mapped to v6 using the 0:0:0:0:0:ffff::/96 prefix. Many IPv6 clients take this into account when doing a DNS lookup and only a v4 address is returned.
You can also go the other way (map v6 into v4 space). Trumpet Winsock does this in Windows. You can use any v4 app in Windows (with *very* few exceptions; even IE works:)) on a completely v6 network, if you wanted to. You can use both v4 and v6 very nicely.
The most basic factors you need to consider are operating systems, and their implementations. Applications are lower on the chain. Although, the firewall would be a very high priority too; if it doesn't allow protocol 41, IPv6 is dead.
Hm. Forgive me, but which IPv6 policy is this from? There are plenty. Most of them are still being worked upon. Haven't heard of this one. Although, I can say that it'd be quite simple to change someone's IPv6 prefix; in ISP-ville, they just send a message to the router, and it does everything necessary without human intervention (gotta love machines taking all our jobs and performing them better than us, eh?). Now, I don't quite think this'd work very fast over all of Japan, nor do I think anyone would reassign Japan's entire IPv6 prefixes...
Anyway, in all my rambling, I still wanna know which spec this is from.
Makes me think it's a customer-driven world we live in.
OS vendors and network hardware vendors are treating IPv6 as experimential, which is why people are not deploying it. People like the network to work with as little work as possible. You are more likely to be pitched about Voice over IP than IPv6 from a vendor salesperson.
Another major concern is hardware compatiblity, people don't want to scrap older routers. IT departments have to watch their budgets these days. Most routers do support IPv6 or can be updated to do so.
IPv6 uses 128 bit (16 byte) addressing.
The minimum allocation is still 1 address of course. /64.
that's 2^64 addresses, or 281474976710656 class B address blocks. In theory, no ISP should ever have less, but clearly there's a market segment that has been ignored - ISP customers, and it will be serviced. I'm guessing that most home networks will get a /96 (4 billion address) but that's just a guess. Every ISP is probably going to do it differently.
The minimum network allocation is a
IPv6 packets have a standard for encryption, which arguably means they will be easier to encrypt than IPv4 packets, but they aren't all encrypted by default. Also, encrypted IPv6 packets can encrypt the source address, making traffic analysis more difficult. However, packets encrypted using the standard encryption are easy to identify as encrypted packets. This would make traffic analysis of encrypted traffic easier.
Although technically no one owns IPv6 address space, it's extremely unlikely that anyone will ever be asked to return address space until we are close to running out. According to the IPv6 specs., renumbering should be a simple task, and it also shouldn't be necessary. I'm not sure I believe either of those statements, but that is what is claimed. The real reason for this clause is to remind ISPs to tell their customers that they can't take their address space with them when they switch ISPs. (I do think it's reasonable to assume this could happen again if it wasn't prevented.)
Some Windows IPv6 support already exists. (I'm using it right now.) the website hs247.com/ has a lot of information, go slashdot them. ;)
FreeBSD and Linux already support IPv6. There are bugs, but then there are bugs in IPv4 too.
Maybe we can do both switches at the same time.
Since I found your posting rather confusing, I will just add a little info (I too have an ADSL from a danish provider (Worldonline, since you didn't ask)). And while my router was delivered with NAT configured with 192.168.1.x on the local side, the external IP is fully routable, and fully accessable from the "real" internet. But it is certainly an anoying little caveat, since you need to either let some machine get all packages, or configure EVERY port you need to use. Lets all hope the powers that be (or if the US won't play ball, the powers that WILL be) get in gear and implements IPv6...
You mean J2EE, don't you? Which is a balatant rip-off of MTS? Micrososft Transaction Server?
--
Two witches watched two watches.
Which witch watched which watch?
I remember in 1996 NTT announced it would have ISDN data connections available at every location in Japan within 12 months. Didn't happen, did it? They can't even deliver land lines at every location in Japan, thus the amazing statistics that more Japanese people have portable phones than home phones.
I'm don't on my 'domain' here but : I'm sure as hell gonna try to give my IP packets high data priopority. Making them packets from isochronic applications should also do the trick but they will trash iso-packets that remain in a queue too long... soo resend those , no ??? This means fast, very fast communication for those that can actually write something (and scriptkiddy's ... )
It's an idea, ... geeky but still just an idea...
Don't mind this dude, half of the time he goes half naked, and that's not the same as full time quarter naked, is it ??
Apparently software has been in beta test for months, with the full release scheduled for the end of May.
Also see http://www.cisco.com/ipv6
Japan leads in IPv6....
;)
I'm sure many of us have seen 'Serial Experiments: Lain', and therefore know that it takes place about when we're upgrading from IPv6 to IPv7, are they trying to 'Fulfill the Prophecy'? Oh, brb, god is trying to ICQ-chat me...
(This bit of nonsense brought to you by: caffeine, sleep dep, and the watching of copious amounts of anime. Please don't mod me down too far for attempting humor in this state... ^_^;;)
---------
"Look. Endsville is burning." -Mamimi, FLCL
Friend: "The NIC is misconfigured..." Me: "No prob, I'll just telnet in and fix it." *Silence*