Protect Your Pre-1997 IP Address

CWmike writes "With IPv4 space running out any day now, is your legacy IP address space safe? Marc Lindsey writes that if your company obtained its IP address space before 1997, you have probably received several letters from the American Registry for Internet Numbers encouraging you to enter into a contractual agreement to protect the IP address. But should you sign it? Be careful — there are several issues you should consider before signing up for this, writes Lindsey, who offers a deeper look at the issue."

Comments

Why?

[froggymana]

Why would it matter if you have the same IP address you've had for several years? Whats wrong with switching to a different one?

I got one

[bbn]

I just checked. My 1994 class C is still allocated to me. I have no idea how to regain control over it though as every single contact detail, except my name, is outdated by 15 years.

It was never used on the public internet. But back then they said you should get one for your local lan. This was before everyone started doing 192.168.x.y. So I applied for a class C and got it.

Even if I did manage to get RIPE to correct the contact details, I do not know any ISP who would advertize it for me. So this class C is part of the dead IPv4 space that will probably never get used.

Re:I got one

[Spazmania]

IANAL, but here's some perspective from someone who has been in the thick of the ARIN policy process for the last few years:

First, you're talking about RIPE (european IP addresses) while the article is about the registration services process at ARIN (north american IP addresses).

Had you been talking about ARIN, this is frankly the kind of thing where you'll want to sign the LRSA and soon. ARIN will work with you to nail down the details and confirm the registration but they'll want to normalize their relationship with you via a signed contract first. I think they'll still update if you come to them with ironclad documentation, but if you had ironclad documentation you'd have been the kind of person who kept the registration up to date to begin with.

For those who are still contactable via at least the email address published on the registration, now is not the time to sign the LRSA. ARIN claims you have more rights under the LRSA than under the regular RSA but on close examination the claim doesn't really hold up. It's a standard adhesion contract in which the powerful party has reserved the rights to themselves.

That having been said, keep tabs on proposed ARIN policy every 6 months or so. ARIN probably won't seek the legal liability from trying to seize legacy registrations that are obviously in use, but the situation could change.

If you are in the situation where your contact details are dead, I personally think you SHOULD sign the LRSA and normalize things with ARIN. A /24 is going to be worth at least $1000 within 12 months, and probably a lot more. IPv6 won't deploy fast enough, the IPv4 free pool will be gone by mid year and the only source of new IPv4 addresses will be folks who are willing to sell.

On the other side, the unrouted dead registrations without valid contacts are very likely to evaporate in the next 24 months. The ARIN policies for this sort of reclamation aren't in place yet, but mark my words: they will be.

Re:Seriously?

[TheCarp]

Which is fine. If I cared (I have been debating it) I could probably get my home internal network doing internal IPv6 and connected out via a tunnel this weekend (if I didn't already have some other things to do, like clean out the room that is to become the new office).

Might be able to do it at a small business, in a few days to weeks, if things were otherwise slow.

Try it on a large multi-site network that runs continuously. Coordinating changes between multiple groups, with varying level of skill and network clue, and varying responsibilities, all while everyone is doing their normal day job.

Shit, its going to take you two years of meetings just to explain to mid level managers why they need to get the high level managers on board so they can make all the little fiefdoms work together on something that isn't directly of interest to any of them, but yours.

Of course, its only two years because I figure its about that long before the high level manager hears some BS about someone else who did IpV6 and then asks the mid level managers that you have been battering for years about why they aren't doing it when these other people are.