Hacker News Reader

Comment by 51Cards | Hacker News Reader

I always thought that when we ran out of IP4, that some of the companies holding on to Class A blocks would release parts of those for use. I'm not a master of how blocks are assigned or if addressing wise it would be feasible but really, does Ford fully use its Class A block? Prudential Insurance? Eli Lilly? GE?

View on HN

They could be playing the long view and realizing how much that address space is worth. If I were in charge of IT at those companies, I'd renumber out of the block and start thinking about selling the space, once it gets tight.

I've noticed that the perceived view in the netops community -- backed up by mailing list messages today, even -- is that such an IPv4 broker market is an inevitability no matter what the RIRs do. There are policies about it, but some regions (i.e., APNIC) have a model that encourages reselling space without their involvement.

Many people don't realize how non-trivial renumbering a network is. I transitioned the resnet at a public university from a /19 to a new /18, and it took several months of planning to pull off.

90% of the space was assigned via DHCP, but that remaining 10% which was statically assigned was a lot of work. Imagine tracking down every device assigned an IP address, scattered across a college campus.

Our routing configuration was trivial (single super-net, single site, &c), compacting an enterprise /8 would be an insane amount of work.

The long view isn't making a quick buck off v4, it's moving to v6 as quickly as possible.

Spot on. It took Stanford roughly two years to move off their /8.

OTOH, legacy /8s may contain whole /16s that have never been used and thus can be sold off without renumbering.

Looks like Stanford already did this with their block:

http://en.wikipedia.org/wiki/List_of_assigned_/8_IP_address_...

Its a pretty interesting list of companies that still hold onto these blocks.

I have to wonder what the DoD's Network Information Centre needs with 151 million IP addresses. Surely they could spare a few.

Especially when you consider none of the good stuff is allowed on the internet anyway.

Random point about this (my current employer is a national lab):

In 2006, the OMB issued a requirement that new DoD/DoE/USG/etc IT spend ("to the maximum extent practicable") be IPv6-capable, and tasked NIST with developing a testing framework for determining compliance:

http://www.whitehouse.gov/sites/default/files/omb/assets/omb... http://management.energy.gov/documents/AttachmentFlash2010-4...

Mind you, we were also supposed to be running at least dual-stack by 2008. ;-) Anyway, as of the middle of last year, this came along:

http://www.cio.gov/Documents/IPv6MemoFINAL.pdf

Basically, we have to be IPv6-capable on external services by 2012, and be ready for it enterprise-wide (for anything that touches the Internet; offline farms, etc. are exempt) by 2014. I don't suspect many organizations are going to hit that, but that's the target, and we're taking it pretty seriously here.

Also, here's a random resource: a totally unofficial IPv6 survey:

http://www.mrp.net/IPv6_Survey.html

Reply on news.ycombinator.com