IPV6 Conference June 24-27
John Sokol writes "IPv6 is the 'next-generation' protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 ('IPv4'). This years big conference on it will be in San Diego from June 24-27. See the North American Global IPV6 Summit site. I hear rumor DARPA will be making a big announcement there."
What did you hear they would announce?
That there is no need for IPv6? That the so-called IP shortage was mostly fabricated?
I've had enough abrasive sigs. Kittens are cute and fuzzy.
As a coincidence, the year 2427 is also when IPV6 will be finally implemented.
Does anyone know of any good books that cover IPv6 as well as Stevens' cover IPv4?
The only thing holding me back from a wider deployment is the need to tunnel ipv6 through my ISP, who doesn't route it. Due the braindead pricing of broadband services in Australia, where we get byte-charged heavily, there are local free-traffic "internet exchanges" (http://www.waia.asn.au/) to get around the problem.
If I have to make a tunnel outside my ISP, I get bytecharged even for traffic between work & home, for example, despite both being on WAIX.
As a result, the practical utility of ipv6 for me is quite limited until the ISPs here grow brains.
Craig Ringer
You should be using a comercial, not a private connection.
I beleive that comercial traffic make up most of the day time load of ISP's and puts more strain on the network than P2P traffic.
Wander why your being bytecharged?
thank God the internet isn't a human right.
Why is everybody so god damned negative when it comes to IPv6? It's a good thing! IPv4 = One IP for every American IPv6 = One IP for every atom ..
Unless you want the entire world to start NAT'ing (I for one prefer having my own IP addy ..) you might as well embrace IPv6 because more and more dumbasses will be connecting to the net.
Hopefully someone will raise the question how an end-site with is supposed to take /48 assignments from its IP transit providers is supposed to work w.r.t. multihoming.
/32 assignments because they can't commit to allocating 200 /48 assignments in 2 years.
If a domain has 1 IP address for each IP transit provider then we rely on DNS round-robin. If one IP transit provider goes down, then we lost 33% of our connections.
End-sites can't get
Until this RIPE policy is sorted, I don't see much worth in deploying IPv6.