What's Your Timeline for IPv6 Migration?

SgtChaireBourne asks: "IPv4 has, over the last 20 years, seen unexpectedly wide adoption. During this time it's proven to be both flexible and robust, but also several problems, though once small, have grown. IPv6 looks to solve some scalability problems, add needed privacy and authentication mechanisms, address quality of service, and provide better routing and addressing capabilities. What kind of timeline does your site/institution/business have for rolling out IPv6 and how?" Those interested in IPv6 migration may also be interested in this article, from a year ago.

Comments

Re:My Timeline

[b0r1s]

Besides, we almost HAVE to use NAT to prevent p2p apps from completely swamping our tiny college connection, so we have unlimited IP addresses anyway.

A competant network administer would have killed p2p apps long ago with firewalls and packet filtering.

Re:What IP shortage ?

[unclejon]

I agree, I think that for the vast majority of organizations, NAT takes care of the address space problem. Given that a single IP can have 64k ports, that's 64k mappings to internal machines. So a company with 640 machines can have 100 simultaneous connections per machine.

Does anyone else see problems by ipv6?

[Anonymous Coward]

I mean, look at the big attacks in 2000 with the DDoS trinoo daemon running on all those machines, with IPv6 being implemented wouldn't that allow more machines connected to the internet and someone being able to generated a even larger DDoS attack??