We expect to take registration actions this week that will activate ARIN’s policy for unmet requests. For the first time, it is expected an organization will receive a block size smaller than they qualified for, and/or an organization will be placed on the waiting list for unmet requests.
For decades the only common method for accessing data in all the Regional Internet Registries (RIRs) has been Whois. Unfortunately, as a protocol, Whois does not specify any queries or responses making true interoperability between RIRs very difficult. This situation is even worse for domain registries.
The so-called “Internet of Things” (IoT), is not just about the seemingly endless benefits of connecting everything to the internet, or as some say, making things “smart”. It’s also about infrastructure, intellectual property, education, and increasingly growing business interests. It’s how devices are tied to the cloud for commerce, research, and an endless array of applications.
At the time of this post, there is only .15 of a /8 remaining in the ARIN IPv4 free pool. The largest prefix that remains available is a /11. Within days, that /11 will either be issued to a qualifying organization, or broken down to make smaller prefixes available for organizations who have qualified for a block size that falls between a /11 and the next available block size in inventory.
If we are to believe the figures being banded around, the Internet looks set to be dominated by the number of devices connecting under the ‘Internet of Things’ banner at some point over the coming years. If there’s any domination of the Internet before then it is arguably by cats – cat photos, cat videos, pretty much cat anything. I actually think there’s room for both though in the form of Internet-enabled cat feeders…
Webpass’ network is 100% dual-stacked and running on a Brocade CER and MLXe platform so setting up the IP circuit was as simple as: 1. Adding an IPv4 /30 and an IPv6 /64 for connectivity between networks. 2. Statically routing ARIN’s netblocks with the next-hop being the Webpass WAN IPs. 3. Redistributing the static routes into our OSPF and OSPFv3 tables
From the Twitterverse
- ICYMI based on our IPv4 response queue @JimmRich predicts we will activate our unmet requests policy very soon: http://t.co/cchPFxlz0z
- Today's IPv4 inventory is at 0.00887 /8s remaining in the ARIN free pool https://t.co/pbhjacdmxs
- Very cool tool to help you plan your IPv6 address framework! https://t.co/xKmzrFfBuZ
- Share your comments on draft Internet Number Community Review Committee Charter: https://t.co/PMONBfTERT on the @theNRO ianaxfer list
- We expect to take actions this week that will activate ARIN’s policy for unmet requests http://t.co/cchPFxlz0z #IPv4 http://t.co/ZeKEyzF6TU
- Cisco Live San Diego 2015 – IPv6 “the wrap” http://t.co/1A9zoHtVo7 via @GetYourBuildOn
- [New Blog] On the Horizon: Unmet Requests Policy Activation - By Richard Jimmerson, Chief Information Officer, ARI... http://t.co/IUDmSO6Xpb
- Apply for a fellowship to attend the next ARIN meeting for FREE: https://t.co/BbgTqaokSl
- Curious which RIR allocated/assigned a particular resource? Find out with this new data call on #RIPEstat: https://t.co/qQT0LGMVCJ
- http://t.co/kr4KENLqFe now shows 20% of USA Internet users connecting via #IPv6 - quite timely, as IPv4 is at runout! http://t.co/W8yvDROeAU
- @FrantechCA Yes, you can read up on it at: https://t.co/1hyrLUfMD9
- @FrantechCA Thank you for your inquiry. We will be making an announcement about the waiting list next week.
- The #IANA Stewardship Transition: A major milestone passed on the path towards globalizing the Internet - https://t.co/tGau978pZl #ICANN53
- Subscribe to PPML http://t.co/R9zHx20Wke to discuss Internet number resource policies in the ARIN region
- Great post from @ehorley on why #IPv6 is indispensable at @LinkedIn https://t.co/IG2ZRq4Zu0
- ARIN's remaining IPv4 inventory only includes 101 /23s and 439 /24s at this point: https://t.co/pbhjacdmxs #get6
- How low can it go? Less than 1% of a /8 remaining in our IPv4 inventory http://t.co/V6s6aQyOz3
- Registry Data Access Protocol (RDAP) is based on the common approach of delivering results in JSON format over HTTP: http://t.co/u9iWcLpuY9
- Phases of the #IANAstewardship transition graphic from @ICANN #ICANN53 http://t.co/gy5rxjTijp
- Policy implemented: https://t.co/20JeZmTR6X ARIN-2014-17: Change Utilization Requirements from last-allocation to total-aggregate