(Meta: One of my friends asked in class today, how I expect to find a topic to blog about daily. Well, right after that, we were discussing the IPv4 exhaustion thing. So I thought I’ll write on that topic itself, as direct proof of the fact that there are infinitely many topics to blog about, all around us. We just need to see them that way. Or rather, the way Jerry Seinfeld would!)
Think of that movie scene where people in a desert are desperately digging and all. You know, surviving on the last droplets in the water bottle. The camel and the dog gets none, obviously. And then, they dig and hit a spring or a water pipe(no idea how a water pipe landed up there, though), and there’s more than enough for everybody. Heck, even the camel and the dog gets some!
Well, that is how going from IPv4 to IPv6 will be, I think. (With the exception of the camels, hopefully.. I don’t think people would want to locate pet animals using nslookup)
The last IPv4 address block has been given out to the regional organizations who shall, in turn, allocate them to somebody down the recursive tree. I’d like that last IP to be a part of a guess-that-ip-and-take-it-for-free contest. It would attract enthusiasm. And then, of course, there has to be some real genius with a one-liner way to crack it:
fping -gu 0.0.0.0/32
(fping, for those who don’t know, is a program that can spray an entire subnet with ping requests. And since the entire IPv4 space is but a single “subnet”, if I may call it, this one’s pretty evil, I think)
And on some day in June I think, many big websites are going to officially test their sites using IPv6 for the first time or so. Test? What can go wrong? Of course, other than something like Google calling Microsoft: “Bill, that you? I think I got one of your bits wrong.. can you repeat yours again from the third octet? I hope you don’t want my address; you can always Google it! (Invisible Wink Here)”. Hangs up.
On a more serious note, the IPv6 scenario inside IIT is very bad. I happened to notice that all the latest routers are not responding to IPv6 requests that I was sending back then. I wrote to CC. All they did was assigned my complaint to some particular guy. Besides that, no reply. I hope that changes fast.
And then, in future, I long for the day when I might be able to say: “My website’s IPv6 address is also the 128-bit md5 hash of my password!”
Totally awesome. Building the future, one “bit” at a time.