Home / Blogs

IPv4 Historical Imbalances and the Threat to IPv6

It is an open secret that the current state of IPv4 allocation contains many accidental historical imbalances and in particular developing countries who wish to use IPv4 are disadvantaged by the lack of addresses available through ordinary allocation and are forced into purchasing addresses on the open market. As most of the addresses for sale are held by organisations based in the developed world, this amounts to a transfer of wealth from the developing world to the developed world, on terms set by the developed world.

It has long been argued that this problem will be short-lived or would be avoided altogether by the switch to IPv6 which does not have any problem of scarcity. The same argument continues that this imminent switch to IPv6 removes any need to address the historical imbalances of IPv4 allocation as IPv4 will cease to be of any importance quite soon.

This argument never felt sound and seemed to me to ignore the perception issue that it creates, which is that those responsible for IP allocation policies, largely based in the developed world, don’t care about imbalances that are disadvantageous to the developing world and so can’t be trusted to stop this happening again.

Of course anyone who understands IPv6 allocation policies knows that these have learnt a lot from the accidents of history that created the current imbalances in IPv4 and are very different policies. So when challenged on the perception issue, those who argue against correcting the historical imbalances point to the IPv6 allocation policies and politely explain that those imbalances won’t happen again.

But there is now strong evidence out there that this perception that the IPv6 allocation policies will not be fair, is strongly held and will not be shifted by any amount of polite explanation of how the IPv6 policies differ from the IPv4 policies that led to the imbalances. Top of this list to my mind is proposition 100 (prop-100), a policy proposal in the APNIC RIR that requests the reservation of a /16 block of IPv6 addresses for India and similar reservations for all other countries in the region, from which any allocations to an LIR from that country will be provisioned.

The explicit reason given for prop-100 is:

“The main objective of this proposal is to ensure that all economies (and the different present and future organizations in those economies) can ensure they will get a suitable share of the IPv6 address space, in one or more large contiguous blocks, whether they need it now or at a later date.”

It might look like the focus here is on contiguous blocks, but discussions with the author have made it quite clear that it isn’t about this, the real concern is:

“planned usage of the IPv6 address space with assurance that every economy will have some address space reserved for it whether it needs now or in the future.”

No amount of reasoned explanation that the IPv6 allocation policies will not lead to scarcity that disadvantages some economies, is affecting the views of the authors, nor is any amount of simple mathematics showing just how vast the IPv6 space is and just how small a percentage has been allocated so far. Nor is any amount of rational argument ever going to work so long as the accidental historical imbalances of IPv4 are ignored. Note, I didn’t say “corrected”, I said “ignored” as this is about perception and trust more than anything else.

So here we are, approaching the worst possible position where our well considered IPv6 allocation policies are untrusted and undermined because of the complete disregard for the historical imbalances of IPv4, when that has nothing to do with IPv6. Rather the IPv6 taking away the problems of those imbalances, those imbalances are now close to seriously disrupting IPv6.

If this proposal for contiguous national blocks sounds familiar then that’s because it is telephone numbering all over again. The ITU-T, that dying anachronism, is struggling to reinvent itself in the Internet age and has latched onto IPv6 allocations as a lifeline. The ITU-T IPv6 Group has stated aims almost identical to that of prop-100:

“To draft a global policy proposal for the reservation of a large IPv6 block, taking into consideration the future needs of developing countries ...”

“To further study possible methodologies and related implementation mechanisms to ensure ‘equitable access’ to IPv6 resource by countries.”

The ITU has been touting this nonsense around developing countries and gaining traction using, yes you guessed it, the historical IPv4 imbalances as evidence that they need to step in to ensure fairness in IPv6.

It should be clear by now that the accidental historical imbalances of IPv4 cannot continue to be ignored as this is actually making the situation worse. A very public global policy process needs to begin to tackle these imbalances. In particular, since the biggest issues are with pre-RIR allocations made directly by IANA, it needs to be the Address Supporting Organisation (ASO) of ICANN that initiates this policy process. Those companies that hold large allocations, such as the /8s out there, should be required to demonstrate need as determined by an RIR policy and receive an appropriate number of addresses for that need.

The question I most often get asked is how do we bring the address holders to the table since they are under no obligation to do so? My answer has been the same for years—if they don’t follow this policy process then they don’t get RPKI and they get shut out of the global routing tables.

I’ve heard it said that this won’t work because RPKI will never be that authoritative, but I’m convinced the push to secure the Internet will make it authoritative fairly quickly. The other argument I’ve heard against this solution is that RIRs should not be regulators and deny RPKI for policy infringements. Well, if the RIRs don’t regulate then either governments or their proxy of the ITU-T will and that is going to be far more damaging to the Internet than the bruises caused by the RIRs stepping up and taking responsibility.

Even if this is not the solution, something still has to be done. This is no longer an historical issue, this is now a struggle for the future that IPv6 represents.

By Jay Daley, Posting here in a personal capacity

Filed Under

Comments

I am not sure about the open secret Suresh Ramasubramanian  –  Nov 7, 2011 1:48 AM

The popular example of that was the “MIT has more IP space than China does” meme, that continued for long, long after China had more than a /8 allocated to it.

The “contiguous IP space” idea is going to turn up some interesting monopolies in economies where the incumbent government owned telco is a steady lossmaker and the regulator is known to take a series of actions over the years that try to tilt the playing field in the incumbent’s favor .. giving a monopoly on IP space allocation in the country to a government agency would have interesting consequences to private industry players - even those who currently support this proposition.

a lot to chew on here... McTim  –  Nov 7, 2011 4:51 AM

While I certainly agree that allocating v6 to economies instead of to folk who will route those addresses is a bad idea whose time I hope will never come, I also think that a Global Policy to recover some of those addresses will not make the folk who want to do this stop their efforts.

At this point, I think it is more about sovereignty (control) and about generating revenue for regulators than it is about historical imbalance, although the proponents of this idea won’t admit that.

BTW, I don’t think that the ASO themselves (as a body) can initiate a global policy proposal (although individual members of the ASO could).  You can read 6.4 of the procedures of the ASO or Attachment A of the MoU  to see what I mean.

IPv4 Address Pool Expanded Abraham Chen  –  Aug 19, 2018 1:09 PM

There is practically no need to go to IPv6 based on our recent research result, called EzIP (phonetic for Easy IPv4) that we have submitted a draft to IETF:

https://tools.ietf.org/html/draft-chen-ati-adaptive-ipv4-address-space-03

EzIP can multiply each public IPv4 address by 256M (Million) fold without affecting current equipment. This enables over 75% of nations to serve their respective countries starting from just one of the IPv4 addresses that are already assigned to that nation. This is in addition to the existing Internet setup.

Essentially, the CIR (Country-based Internet Registry) model proposed by ITU-T utilizing IPv6 a few years ago can now be stealthily implemented under IPv4, even without forming the sixth RIR at all.

The two simultaneous sets of services will enable consumers to evaluate their meirts in parallel and then make informed choice.

These possibilities would lead us to a new phase of address allocation related discussions.

Thoughts and comments would be much appreciated.

Abe (2018-08-19 09:04)

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

VINTON CERF
Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Related

Topics

New TLDs

Sponsored byRadix

IPv4 Markets

Sponsored byIPv4.Global

DNS

Sponsored byDNIB.com

Domain Names

Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

Brand Protection

Sponsored byCSC

Cybersecurity

Sponsored byVerisign