Читайте блоги ICANN, чтобы получать новости о деятельности в области формирования политики, региональных мероприятиях и других событиях.

IPv4 squatting: awareness raising and research

23 марта 2010
Автор Leo Vegoda

Контент доступен только на следующих языках

  • English

As has been noted again in recent days, some ISPs, vendors and end users have been using previously unallocated IPv4  blocks to address their own networks and devices. When these address blocks become officially allocated or assigned, the prior use can lead to routing problems both for the new holder of the addresses and the person who used them without authorization. This is an unfortunate problem that we have been trying to raise awareness of over the last few years.

In September 2007 I wrote an article about the issue for Cisco’s IP Journal. Over the next few months we conducted some preliminary research into the extent of this usage and presented the preliminary findings at a few network operator meetings.

Once we had a workable method for researching the problem we commissioned Duane Wessels to do a thorough analysis using the DITL data collected by DNS OARC. His research was then presented at the Brooklyn DNS OARC meeting in mid 2008. Obviously, we also shared this research with you on this blog.

At the start of this year, APNIC received, a block which many network operators have improperly been using for years. Often this use predates the creation of ICANN and is very entrenched. Rather than rushing this address space into use, APNIC staff has been working with other RIRs and network operators to look at the scale of traffic sent to various parts of this /8 and where else it is used on the Internet.

People who have numbered networks using this address block and others that are yet to be allocated will find that they experience connectivity problems and hard to resolve helpdesk calls as a result of this use. Similar problems occur for the legitimate users of the address space. This is the whole point of a single, authoritative allocation registry for IP addresses and other unique identifiers. When resources are simply taken, not assigned, uniqueness is challenged and any protocol that relies on uniqueness can fail.

Of course, the story doesn’t end there. These problems just make it even more clear why it is important for us all to provide services and connect to them over IPv6. IPv6 is so big that there is no justification for using address space that has not been allocated or that has been allocated to someone else. And if you want unique, private addresses then they are available too.


Leo Vegoda