Tag Cloud:

Are Service Providers Ready for IPv6?

President and CEO of Incognito, Stephane Bourque, is looking find out what strategies communication service providers are using to transition to IPv6 and needs your help to answer a few questions about your IPv6-readiness.  

Guest blog post by Stephane Bourque, President and CEO of Incognito Software Systems

Worldwide, the transition to IPv6 has begun — but just how ready are communication service providers for this change?

ARIN is expected to join regional Internet registries in Latin America, Europe, and Asia Pacific in exhausting public IPv4 addresses soon. Globally, this means that the number of remaining public IPv4 pools available to service providers to hand out to customers is running out, and most providers will need to consider strategies for IPv6 to enable future growth.

What are these strategies? That’s what we want to find out. For the second year, Incognito is running a global survey of communication service providers to find out IPv6 plans and strategies. The 5-10 minute survey is open to telecommunications, cable, mobile, satellite, and converged service providers of all sizes.  All participants will receive a copy of the final report compiled from survey results.

Last year’s report found that most service providers are slowly moving towards IPv6. At that stage, although more than three quarters of respondents had started preparing for IPv6, only 14% had deployed IPv6 on their networks and 4% had begun offering IPv6 addresses to end users.

Infographic 2014 Incognito Survey

The transition to IPv6 is essential for all businesses. At Incognito, we have embraced IPv6 on our internal networks and our website to prepare for an IPv6 future. When we made our website IPv6 ready in 2011, only a fraction of websites could be reached over IPv6, but we knew content was going to be a significant driver in the transition. So we enabled IPv6-support at the World IPv6 Launch Day in 2011. Our solutions already supported IPv6, so we knew we had to practice what we preach. It hasn’t been a quick process, but we look forward to being part of an IPv6 world.

Whether you are IPv6 ready or not, all communication service providers are invited to share your experiences and plans in the IPv6 Readiness in the Communication Service Provider Industry survey.


sbourqueStephane Bourque is the technological inspiration behind Incognito’s provisioning solutions. As CEO, Stephane has championed the development of high performance, multi-platform solutions that help service providers increase margins and reduce network upkeep.

Originally from Montreal, Canada, and educated at Concordia University, Stephane applied his computer engineering background at Banyan Systems to design enterprise network management systems for Fortune 1000 companies like Bell Canada.




Help ARIN Choose the Next Meeting Location

By Melissa Goodwin, Meeting Planner, ARIN

In your everyday life, you pick the music you want to listen to, choose which specialty coffee you want to drink, but what you may not realize, is that you can also help determine ARIN’s future meeting locations.

Recently, while sitting at my desk looking for a network connectivity sponsor for ARIN 39 (2-5 April 2017), I started receiving gentle nudges from two potential host cities asking us to make a decision. And as much as I would like to, I can’t do it without a little help from you. I thought it might be a good idea to tell you a little bit about how we determine the locations for the biannual Public Policy and Members Meetings, and maybe you and your organization will be inspired to get involved. So here it goes…

Sponsor an ARIN Meeting

Long before a sponsor logo is stamped on a meeting giveaway – there is a team who puts in long hours establishing which cities to solicit offers from based on past history and geographical service area (no, we don’t just throw darts at a map), poring over proposals, reviewing our requirements against hotel offers, and making sure that all of the good stuff you want to see and do in a particular city can be accommodated. Once we have identified a short list of hotels that can fulfill our meeting requirements, we work with our operations folks to make sure the hotel(s) understand and can handle our wireless network requirements – one of which is IPv6 capability. Then, we reach out to our community to secure a wireless network sponsor.

In a nutshell – Without a network sponsor, we can’t contract with a venue. So we need your help to decide which city and hotel to move forward with (if you are already in a particular venue – it’s a bonus). Sponsoring an ARIN meeting is truly your chance to “see and be seen” – have your colleagues using your network, see your logo on the mobile app and on conference signage, deliver a welcome address, etc.

If you feel like you or your company would like to be a wireless network sponsor, check out our ARIN Sponsorship Opportunities page for additional information.  At the moment we are looking for potential network sponsors in New Orleans or Nashville. In the future it could be in your backyard.

And if you aren’t sure that sponsoring is your thing and want more details or just want to say “hi”—stop by and see me in Montreal, Quebec at ARIN 36. Maybe we can get coffee – and I’ll let you choose your own beverage.



Top 6 Reddit AMA Questions with ARIN CEO

By Jennifer Bly, Public Relations and Social Media Coordinator, ARIN

With opening his computer, removing his watch, and stretching his fingers, ARIN’s President and CEO John Curran prepared to type. And type he did! Last Wednesday, John hosted a Reddit Ask Me Anything (AMA) session to raise awareness of the need for IPv6 deployment as we rapidly approach IPv4 address runout. He answered questions on topics ranging from the effects of IPv4 depletion on various Internet stakeholders, to IPv6 migration tools, and let’s not forget coffee! In case you missed the AMA, here are the top six questions (as voted on by those who participated) and his speedily typed answers –

Reddit AMA with John Curran

Q: Would you rather fight an IPv4-quantity of horse-sized ducks or an IPv6-quantity of duck-size horses?

A: An IPv6 quantity of anything is lethal… gimme the 4.b billion horde of huge ducks, and perhaps something sharp to wield!

Q: IPv6 is clearly the direction we want to be heading, but the allocation and assignment policies people are deploying will probably mean we’ll end up with a HUGE table size which will even further constrain resources in ASIC driven routers. What is ARIN (and the other RIRs) doing to try and prevent needless deaggregation of prefixes into the DFZ?

A: It’s a real problem – in the short term, we need to accommodate both the IPv4 and IPv6 tables in parallel, and things are going to get tight. I’m not actually worried about the IPv6 routing table (even though each entry can be larger in size) because the number of issued IPv6 blocks is still likely to be quite small compared to the decades of IPv4 address issuance.

However, IPv4 is going to be a big problem in the interim, as parties start valuing unique public addresses and don’t really care about the minimize size… i.e. if you can acquire a /28 and have a unique presence on the Internet, why pay more to get a /24? In the end, it’s going to be up to the ISPs to decide what is the minimum size “customer Bring-Your-Own-Address (BYOA)” that they’re willing to route…

Q: What is your favorite drink, and why is it coffee?

A: In the morning, coffee. Lot’s of coffee – I prefer fresh latte or expresso, but will drink nearly anything caffeinated at 5 AM. In the middle of the day, more coffee. At night, more coffee, and an occasional gin and tonic or expresso martini (see a pattern here?)

Q: Is there any sort of plan for reclaiming the unused portions of the /8s and such that big companies bought up in the beginning?

A: We’ve actually been reclaiming unused IPv4 space for a while, with some very good results. We would have run out years sooner, if it were not for organizations such as BBN, the US DoD, Stanford, Interop, and others who returned unneeded address space as a result of these efforts. You can read more about that here – https://www.icann.org/news/blog/recovering-ipv4-address-space

Two important things to keep in mind – 1) we were issuing IPv4 space in 2010 and more than 10 /8’s per year, so recovering another handful doesn’t change IPv4’s outlook in the least, 2) this is further shown by IPv4’s 4.3 billion total address space compared with 7+ billion people on the planet… we literally can’t provide for one always-on device for everyone here via IPv4 (let alone their home, work, cloud, etc. demands)

Q: What do you see happening once the “official” source of IPv4 addresses run dry? I’ve heard speculation about black markets and prices for IPv4 addresses skyrocketing etc, what’s your take? As for IPv6, are there currently any big hurdles standing in the way of rapid, worldwide adoption? Any technical challenges? Or perhaps security related?

A: While black market transfers are possible, the reality is that we already have today an IP transfer market which is working well, and completely legitimate. Folks that wish to transfer addresses can do so, both within the ARIN region, and to/from other regions in accordance with policy. Given that, there’s not a lot of reasons to try and work around the legitimate transfer process, unless you are trying to bypass the policies, and the risk one takes is that nearly anyone can sell repeatedly to multiple buyers if they’re not going to update the registry… not a reasonable risk that most businesses will take.

Q: As someone who was not even aware that we are running out of IPv4 addresses how will this affect me and what will be different with IPv6 compared to IPv4?

A: I do hope you are not an Internet Service Provider and just hearing about this now. If that’s the case, my advice is to change professions quickly. 😉 Otherwise, if you’re just a typical organization, it’s good to know that many of the folks accessing your website today are coming over mobile devices that actually connected to the Internet via a slightly different protocol (i.e. IPv6) Your website is likely connected only via IPv4. This should remedied as it will provide for more direct connections with better performance, and really is not much work. Talk to your IT department (or if you are the IT department, then go online to teamarin.net/get6 and then talk to your hosting company or ISP).

Thanks to all of you Redditors who submitted questions. To view the entire exchange, check out the whole conversation over on the IAmA subreddit. There were lots of interested questions and answers you won’t want to miss. Best of all? We can sigh a breath of relief that we dodged that lethal IPv6-quantity of duck-size horses.


Tag This: IPv4 Runout

By Jennifer Bly, Public Relations and Social Media Coordinator, ARIN

With less than 45K IPv4 addresses remaining in the ARIN inventory, IPv4 depletion here at ARIN is only weeks away.  We thought it’d be fun to get your ideas about the tag line we should use when ARIN hits IPv4 runout.  Maybe we’ll even take you up on a few of these.  Here’s what you came up with so far:


Thanks for sharing your ideas! If you want to add to this growing list, leave your ideas in the comments below or on Twitter or Facebook.


Engaging the Caribbean ICT Community

By Jennifer Bly, Public Relations and Social Media Coordinator, ARIN

Last week I had the opportunity to connect with attendees at the Caribbean Association of National Telecommunication Organizations (CANTO) 31st Annual Conference and Trade Exhibition in Miami, FL. I found the Caribbean ICT community to be most welcoming and interested in bettering the Internet in their local communities to promote economic and social development. ARIN has been pleased to take part in this CANTO event for the many years as we encourage the Caribbean Internet community to get involved in everything from requesting number resources to public policy discussions.

CANTO 2015 ARIN & LACNIC booth

ARIN shared a booth in the exhibit hall with our friends from LACNIC, the other RIR that also serves the Caribbean region. I joined both Cathy Handley, ARIN’s Executive Director of Government Affairs and Public Policy and Richard Jimmerson, ARIN’s Chief Information Officer to speak with many stakeholders and answer questions about our IPv4 waiting list, getting an ASN, steps needed to prepare for IPv6 and more. Jointly with LACNIC we also hosted a couple of Ministerial events to drive home the importance of governmental participation in the Internet governance process and the need for all levels of support for IPv6 adoption.

I was delighted by how appreciative many were that ARIN is making a continued effort to engage and support the Caribbean. And it was great to be able to explain in-person the many ways they could become engaged in the ARIN community. For example, ARIN offers a fellowship program to send up to five people per region to each Public Policy and Members Meeting held in the spring and fall of each year. In addition to fellowships, we also offer full remote participation options in case attending in person is not possible. This fall we will be headed to Montreal in Canada in the spring of 2016 we will take to Montego Bay in Jamaica. Also, we hosted our most recent Caribbean ARIN on the Road educational event in Dominica in June of this year and are always open to suggestions on where to go next.

CANTO Cathy Speaking

CANTO Richard Speaking

On Wednesday afternoon, representatives from ARIN, LACNIC, ICANN, and the Internet Society took part in a joint session to discuss the ever-changing ICT ecosystem. The panel covered topics like the impending IPv4 depletion in our region, the example of the RIRs as successful multistakeholder model, IP address transfers, IPv6, the status of the IANA stewardship transition, and more.

Along with CANTO, here at ARIN we share the common interest of Internet growth and stability in the Caribbean. We depend on the participation of all of our members to make sure we’re able to meet the needs of our entire region. No matter where you reside, if you are looking to get more involved in ARIN here are a few places you can start:

Get the latest news from ARIN

Subscribe to arin-announce

Follow and contribute to policy discussions

Subscribe to ARIN’s public policy mailing list (ppml)

Request resources from ARIN

Request IPv4, IPv6, or ASNs

Come to an ARIN event

ARIN biannual meetings and one-day ARIN on the Road events provide a chance to network with colleagues and discuss important matters.

Get resources on IPv6

IPv6 Wiki




IPv6 at the Dutch ccTLD registry SIDN

Where there’s a will, there’s a way. Senior Research Engineer at SIDN, Marco Davids, explains how Dutch ccTLD registry SIDN committed to IPv6 deployment.

Guest blog post by Marco Davids

.nl, the IPv6-enabled registry

SIDN is the registry for the Dutch country-code top-level domain. In terms of domain names per capita, we are one of the largest TLDs in the world. And even in absolute numbers, we are still among the five largest country-code TLDs. I guess that makes us kind of special. We may be a small country, but, as in so many countries, the Internet is immensely popular and has been for quite some time. In that regard, we are far from exceptional.

SIDN photoAt SIDN, we firmly believe in IPv6 as a long-term solution for the exponential growth of the Internet and the problems that arise from that. In fact, with IPv4 space running out, and prices on the secondary market rising, the need for a new addressing scheme on the internet is perhaps more acute than ever.

We are pleased to see that many organisations recognise the need for change and are acting accordingly. On the other hand, surprisingly, a considerable number of organisations haven’t even bothered to look into IPv6 at all. That is a concern. Large ISPs in the Netherlands (with a few exceptions) are moving, but they tend to take things slowly. This is one of the reasons why we are keen to promote awareness and adoption of IPv6. It goes without saying that we practise what we preach: IPv6 has been enabled on our own services for quite some time. More on that later.

The Dutch ‘comply-or-explain’ policy

The Dutch government is very much aware of the urgency of IPv6. In the Netherlands, the government maintains a so-called ‘comply-or-explain’ list, containing various Internet standards, including IPv6. Standards on the list should be used by government organisations and, for example, be part of the requirements in a procurement process. As I said, IPv6 has been on the list for quite some time, and an increasing number of government services are now reachable via IPv6. A broadly similar European list also exists, and naturally IPv6 is on that list as well.

Although we are not required to, because we are not a government agency, SIDN has decided to adhere to the comply-or-explain list. The authoritative name servers for the .nl domain have been fully IPv6-compliant for quite a number of years, but we felt we needed to go a few steps further and enable all of our services on IPv6. Naturally, we ran into a few issues. The vendor of our email appliances, for example, promised IPv6 support ‘soon’. But it turned out they needed ‘a little more time’. Quite frustrating, but also a lesson learned: be firm and serious with your vendor and make clear agreements beforehand about mutual expectations. There are still vendors out there, trying to make their customers believe that ‘no one really needs IPv6’ or claiming that IPv6 support ‘is in the next version of the firmware, scheduled for release any time soon’. My advice: show them the door.

Sometimes being pragmatic is the solution. We came to the conclusion that modifying the entire back-end infrastructure of our registry system for IPv6 was not feasible in the short term. As an interim solution, we are using load balancers to disclose our registry system via IPv6 on the Internet side, while it is still running on (RFC1918) IPv4 space internally. We also made our Whois service accessible via IPv6 in a similar fashion. So, where there’s a will, there’s often a way.


The Dutch Internet Standards Platform is a private-public initiative by several organisations with the goal of promoting new standards, including IPv6. On a simple website, https://internet.nl/, anyone can easily check the quality of their connection, or a domain name for that matter, in relation to these new standards. The test is strict; some people say it’s too strict. But if you manage to achieve a 100% score, you can at least be sure that your setup is very future proof. So try it out.

Summarising, I would say that IPv6 is here and now. It’s a mature standard that is being deployed at a rapid pace. The amount of IPv6 traffic is increasing by 100% a year.  And in the interest of an ever expanding internet, everyone should join in.


Marco DavidsMarco Davids is a Senior Technical Policy Advisor and Senior Research Engineer at SIDN, the ccTLD for the Netherlands (.nl). He has been with SIDN since 2007 and a member of the SIDN Labs R&D-team. In this capacity he is involved in various projects, primarily with a focus on the DNS. Marco is also an active participant in the RIPE and IETF communities and has contributed to several RFCs and draft documents.




Waiting List for Unmet IPv4 Requests

By Richard Jimmerson, Chief Information Officer, ARIN

As described in an announcement on 1 July 2015, ARIN has activated the Unmet Requests Policy. Organizations are currently electing to accept block sizes smaller than those for which they qualified or are electing to be placed on the Waiting List for Unmet Requests. So far, 21 organizations have elected to be placed on the waiting list and ARIN expects there to be over 100 soon.

ARIN Waiting List Activated No Reason to Wait for IPv6

At the time of this post, ARIN holds only /24 blocks in the ARIN IPv4 free pool inventory. We expect the ARIN IPv4 free pool inventory to deplete in full sometime around the late August timeframe. Options for obtaining IPv4 address space other than through the ARIN IPv4 free pool, including transfers, are described on our IPv4 inventory page.

Starting in late August, we will publish the Waiting List for Unmet Requests on the ARIN public website. The information will be displayed on a dedicated page for the waiting list and will include the full waiting list order based on date/timestamp placement, qualified block sizes, and minimum acceptable block sizes. We will also include summary totals for all information displayed. ARIN is unable to publicly disclose the names of the organizations on the waiting list, so that information will not be included.

I want to note that the community will continue to see IPv4 blocks larger than what remains in the inventory issued from ARIN over the next 60 days. The reason for this is that when an organization is approved for IPv4 address space, they are granted an approval that is valid for 60 days. At the time of approval, the approved block size is placed on a 60-day temporary hold for the organization. Inside this 60-day period, the organization pays any applicable registration fees due and signs a Registration Services Agreement (RSA), if an updated one is not already on file. After this has all been done, the organization is issued the block that was held for them.

If you see a block being issued by ARIN that is larger than what remains in the IPv4 inventory, it is for approvals that were granted up to two months ago.



Get your apps ready for IPv6

By Andy Newton, Chief Engineer, ARIN

With IPv4 depletion at critical levels, the pressure to transition to IPv6 has never been higher. For years, network engineers and planners have been upgrading routers and configuring networks to prepare for the new protocol, but many remain unsure whether or not their custom-built applications and commercial-off-the-shelf software packages are IPv6-ready. Applications are a crucial component of any organization’s network health, but can still be overlooked when preparing a large network for IPv6 adoption. With that in mind, ARIN proudly presents “Preparing Applications for IPv6,” a software developers guide to writing and migrating networked applications for use on IPv6 networks. This guide focuses on software application needs when making the migration to IPv6, and covers some common assumptions made when developing software for an IPv4-only Internet.

Preparing Apps for IPv6


Custom application developers will find this guide useful as a checklist of areas to investigate in your software’s code. You know your codebase better than anybody else, so we encourage you to take a look at each section of this guide and determine if it applies to your software. If your software acts as a Representational State Transfer (REST) client, you should be aware of the issues involved with placing IPv6 addresses in URLs. If your software takes IP address information from user, you will need to look at input validation and forms. This guide should spare you hours of exploratory testing, allowing you to fix the code you know will break before entering into an expensive QA cycle.

If you are the user of custom or off-the-shelf software, you can use this guide as a roadmap covering potential issues that software may encounter with an IPv6 deployment. For example, if your software stores IP addresses in a database, you may wish to ask your software vendor if the database is capable of storing IPv6 addresses as well as IPv4 addresses. You may also wish to forward this guide to your software vendor for their use in determining if the software they have created is suitable for the coming IPv6 world.

The overwhelming majority of the books available on IPv6 migration are aimed at helping network engineers migrate their network infrastructure to IPv6. With the lack of IPv6 transition information for software developers, we feel a guide with a software focus was long overdue. This guide is geared specifically toward software architects, software developers, software engineers, and computer programmers. We hope it will help you gain a more thorough understanding of the changes needed for your software to make a smooth transition to IPv6, and arm you with the knowledge you need to confront software vendors about their preparedness for IPv6.

If you have any questions after reading this guide, just contact us at info@arin.net.


On the Horizon: Unmet Requests Policy Activation

By Richard Jimmerson, Chief Information Officer, ARIN

On the Horizon

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.

When an organization qualifies for a block size that no longer remains in the ARIN IPv4 inventory, they are given the option to either accept a smaller block that is available to fully satisfy their request, or to be placed on the waiting list for unmet requests. As we do with all IPv4 tickets, we take action on customer responses in the date/time stamp order that they were received. We are able to look ahead in our IPv4 response queue and see that we will take the registration actions described above during this business week.

Once we take the registration action of issuing a smaller block than what was qualified for, or place an organization on the waiting list for unmet requests, we will issue an announcement to the community and a press release.

At the time of this post, there is less than 1% of a /8 equivalent remaining in the ARIN IPv4 free pool. The only prefix sizes remaining are /23s and /24s.


Registry Data Access Protocol (RDAP): A Common Whois System

By Andy Newton, Chief Engineer, ARIN

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.

In March, the Internet Engineering Task Force (IETF) published a set of Requests for Comment (RFCs) for a protocol intended to be a replacement for the Whois systems of RIRs and Domain Name Registries (DNRs). This protocol is called the Registry Data Access Protocol (RDAP), and it is based on the common approach of delivering results in JavaScript Object Notation (JSON) format over HTTP (also know as a Representational State Transfer, or RESTful web service). Both LACNIC and APNIC have already fielded servers speaking this new protocol. On 20 June 2015, ARIN officially deployed its RDAP services. The other RIRs and many DNRs are expected to do so very soon as well.

ARIN’s RDAP services are composed of an RDAP version of its WHOIS system, essentially returning ARIN registration data in RDAP format, and an RDAP bootstrap service.

In RDAP, the method to find the proper server for which to send queries is called bootstrapping. It is a set of processes that involve downloading JSON files from IANA and indexing them appropriately. For some types of clients, such as Javascript programs running in web browsers or simple Bash scripts using curl or wget, bootstrapping can be onerous. But ARIN’s bootstrapping service makes this trivial. Clients that do not wish to conduct bootstrapping simply send their RDAP queries to the bootstrap service, and an HTTP(S) redirect will be returned instructing the client where next to send the query.

ARIN’s bootstrap service is located at https://rdap.arin.net/bootstrap. A query for IP address would look like this: https://rdap.arin.net/bootstrap/ip/ That query results in a redirect to APNIC, whereas http://rdap.arin.net/bootstrap/ip/ results in a redirect to ARIN’s RDAP registry service (located at https://rdap.arin.net/registry). Incidentally, the code for ARIN’s RDAP bootstrap service is open source and available on GitHub.

ARIN has also made available an RDAP command-line client called NicInfo. This is an open source, Ruby program, and most recent versions of Linux and Mac OS can be simply installed with ‘gem install nicinfo’. More information on NicInfo can be found on its GitHub pages.



A Closer Look at The Internet of Things

Nick Rojas explores the Internet of Things and how some will appreciate the fundamental changes to the Internet that will allow it to come to fruition, while others will simply take it for granted.

Guest blog post by Nick Rojas

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.

While considering the benefits of having smart refrigerators and other fun gadgets, many forget the significant potential applications that the Internet of Things could change, such as water conservation due to “smart” sensors, reducing city traffic congestion, and a radical change in health care practices.


The Main Challenge: Infrastructure

Smartphones alone command a staggering share of smart devices in use today, with more than 143 million of them in use. When phones, refrigerators, bathroom scales, football stadiums, and even entire cities collectively need to connect to the Internet, we may find that we simply don’t have the infrastructure to support this yet. When IP protocols were first designed, futurists couldn’t have envisioned all the devices that would one day connect to the Internet. The concept of connecting virtually everything to the Internet goes well beyond the original framework.

Every device connected to the Internet must be given a unique identifier to function properly, so IP address exhaustion is certainly a thing that could hinder the ability to provide for the “Internet of Everything”. This is where we can enjoy a bit of good news.

IPv4 provided approximately 4.3 billion addresses, and has lasted for about 25 years. IPv6 has been available since 1999 and vastly expands the number of addresses to about 340 trillion, trillion, trillion addresses. Simply put, we’re good to go, for a very long time.

As progress is made, some of us will appreciate the fundamental change to the Internet while others will simply take it for granted.

“There will be so many IP addresses … so many devices, sensors, things that you are wearing, things that you are interacting with that you won’t even sense it. It will be part of your presence all the time.”  – Eric Schmidt, Google’s chairman and former CEO

With Increased Connectivity comes Improved Analysis

In addition to infrastructure and the increasing number of devices, the Internet of Things will prompt the continued development of analytics. Advanced statistics and predictive algorithms will play an ever larger role in decision making.   As an example, smart devices can be used by medical researchers to track the relationship between medicines consumed and heart rate.

As the volume of people using such devices increases, and the amount of data reaches statistical significance, analyzing the data can help researchers glean valuable information about the impact of certain foods on heart rate.

According to M.V. Greene, “”The “Internet of Things,” where objects in the physical world are connected to electronic virtual networks, is poised to turn retail on its head. Not since the introduction of online shopping – and before that credit and debit cards for purchasing – has something in retail had the potential to be so transformative.”

As the applications of these smart devices are dreamed of and manufactured, the opportunities for scientists and researchers are endless. Dreaming up ways of connecting human activities with data can lead to major advances in how we lead our lives. With the recent launch of Apple’s Smart Watch, which signifies the first massive step into mass adoption of wearable technology, the potential of the Internet of Things has just begun.


Nick RojasNick Rojas is a business consultant and writer who lives in Los Angeles. He has consulted small and medium-sized enterprises for over twenty years. He has contributed articles to Visual.ly, Entrepreneur, and TechCrunch. You can follow him on Twitter @NickARojas, or you can reach him at NickAndrewRojas@gmail.com.







Breaking down ARIN’s remaining IPv4 Pool

By Richard Jimmerson, Chief Information Officer, ARIN

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. Given the limited amount of address space remaining in the ARIN IPv4 inventory, a common question has been about the concept of “breaking blocks”, so let me explain why and how it works.

IPv4 Review Team

When an organization qualifies for a block size that is not available in the ARIN IPv4 inventory, but there is a larger block size available, we split the closest available larger block to create the newly qualified/approved block size for that organization. For instance, if an organization qualifies for a /14, but it is not available in the inventory, ARIN will split the next available, larger block to create the block that is needed to fulfill that request. In this case, for example, the next larger block is a /11, which would be split to fulfill that approved /14 request. The blocks remaining after that split, a /12, /13, and a /14, would remain in the ARIN IPv4 free pool inventory and be displayed accordingly.

We have hundreds of open IPv4 requests at ARIN today. We are very carefully reviewing and responding to tickets in the order they were received and in accordance with Phase 4 of our IPv4 Countdown Plan. We are aware that this has created delays in our response times, as the request volume and customer questions we are receiving have significantly increased our workload. Rest assured that we are working diligently, and that our number one priority is ensuring Phase 4 procedures are followed during this unique time in the IPv4 history.

The number of days remaining before depletion are dwindling. It is very likely that we are already processing a request that we will be unable to fulfill. We will manage the distribution of the remaining IPv4 in accordance with policy and by following the procedures we outlined in 2011 as part of the IPv4 Countdown Plan.

As a community, we have been preparing for this milestone for years, and now that it is here the Registration Services team is fully committed to making sure that we exercise full diligence with each IPv4 request. As anticipated, this has slowed our request processing pace, and we appreciate the patience of all our customers at this time.



Turning Bits into Bites

I can has IPv6? Mathew Newton knows how to make IPv6 fun – by involving cats of course. Here’s how he connected a DIY device to the Internet of Things to solve a problem and make his feline friends extra happy on World IPv6 Day.

Guest blog post by Mathew Newton

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

Back in 2009 I was looking for a solution to ensure our two cats didn’t go hungry if my wife and I had to work late or go out for the evening straight from work. I couldn’t help but feel that I already had half the solution by virtue of my home-grown security solution based around the use of IP cameras. We could see the cats via the Internet wherever we were, so why not feed them this way on an occasional basis also? Cutting a long story short (the full details of which can be found on my website with the obligatory cat video on YouTube) I built the first version (the ‘Mark 1’) of my cat feeder:

Cat Feeder

Aesthetics didn’t feature on the requirements list (well, not mine anyway – it turns out they did on my wife’s!) but function and reliability definitely did. It seemed to tick both of these boxes completely with little room for improvement.

That’s not to say my work was done however – I had to do something about the Cisco Catalyst switch (I know, pun intended; it was clearly meant to be!) which I’d used to interface the feeder to the network through some hacked-together RJ45 loopback adapters and piggybacking on the port status LED driver ICs. Not only was the switch noisy but also bulky and had to be tethered to a nearby network port. After rummaging through piles of kits that ‘may come in handy one day’ I found a Cisco-Linksys WRT54GL broadband router and used it to make the improved ‘Mark 2’ version:

Cat Feeder 2

Cat Feeder Schematic

Not only was the feeder now a self-contained device, but it was also wireless (well, apart from the main power) and, by reflashing the firmware, could also support IPv6! The immediate benefit of this was, of course, being able to assign an appropriate ‘vanity’ address involving ::f00d and ::feed and no doubt others! Once that novelty wore off, the other benefits became obvious – there was no messing about with port forwarding and dynamic DNS update scripts. It just worked. Out of the box. This could of course be a double-edged sword where network security relies solely on the stateful property of a NAT and so my first IoT lesson to learn was making sure that my firewall was configured to protect the feeder accordingly.

The second lesson was also security-themed, and I’ve only got myself to blame for this one. On World IPv6 Day in June 2011, I decided to open up the feeder for 24 hours for anyone to access. For those connecting over IPv4 they could only view the feeder-mounted webcams, but for those with IPv6 they could also take control of the feeder and feed the cats. You can probably imagine how it went – food pretty much everywhere and two very full cats! The real problem, however, was that some users had spotted that I was passing control parameters through the URL to a PHP script (e.g. /catfeedercontrol.php?action=feed&time=5) and so were trying to abuse this by manipulating the feed durations, fishing for other commands and goodness knows what else. I quickly added some sanity checking to the scripts to mitigate this (I didn’t do this previously because access was usually password controlled). A key point to note here is that this attack vector was not directly related to the use of IPv6 as such – the vulnerability was at the application layer after all – however the ease with which IPv6 allows devices to be reachable from the Internet highlights the importance of ensuring that security is properly considered at all layers of the stack.

Even with sanity checking I would have benefited from being able to rate limit access but didn’t have time to work out how to do this. Instead, I opted to filter the source address of repeat offenders using the firewall and this became my third security lesson. The IPv6 double-edge sword was back – the offender was either hopping between addresses (whether that be manually or using short-term privacy addresses) or an entire organisation was seemingly in on the act because the addresses were all over the place within a very large prefix! I assumed the former but given the futility of playing cat and mouse with the offender (pun not intended!) I gave up blocking individual addresses and filtered the entire prefix instead. In a ‘real world’ application this could of course have significant unintended consequences, and so it did make me realise that our approach to filter-by-address strategies in IPv4 might need further thought when it comes to IPv6.

All in all, the cat feeder has been a great success and has never let us down in the six years we’ve been using it (I should point out that we only use it on occasion and not as a substitute for in-person contact with our pets!). Indeed, the cats seem to love it although it has to be said they’d love anything that feeds them! I suspect though that they might be particularly keen on the IPv6 aspect as normally they are fed twice a day but on World IPv6 Day they were fed a total of 168 meals. So from their perspective, this answers the question as to how much better IPv6 is than IPv4… 84 times of course!


Mathew NewtonMathew has nearly 20 years of network-related experience with a particular focus on all aspects relating to the design and deployment of IP (v4 and v6) and DNS.

His interest in computing, electronics and ‘how things work’ arguably stems from a childhood of taking things apart. He is now at the level where hardly any screws are left over when putting them back together again.





3 Reasons Not to Delay your IPv6 Deployment

By John Curran, President and CEO, ARIN

Lately there has been some remarkably bad advice circulating that suggests companies would be better off delaying their IPv6 deployment ­– effectively deferring their IPv6 efforts until there’s no other option. Deferring the roll out of IPv6 while the Internet is moving ahead with IPv6 is a flawed strategy with serious impacts to your business. Let’s take a look at three reasons why companies should make their IPv6 websites reachable now versus waiting until later.

Don't Delay

1. The public Internet is moving to IPv6 whether you’re ready for it or not

First, it’s important to remember that it is the public Internet that now is migrating to IPv6, so for most organizations it is not your whole enterprise that is impacted at this point. Unless you’re an Internet service provider, the migration to IPv6 only impacts the public-facing servers (e.g. web servers) that you use to communicate with your customers and business partners. No one is saying that the printer in the copy room needs to find IPv6, or that every desktop needs it – it is the public Internet is moving to IPv6, and this means whether you like it or not, your public servers are going to be reached increasingly via the IPv6 protocol.  This ongoing migration of the public Internet to IPv6 is easy to confirm – just look at deployment of mobile devices in the US, where nearly every leading carrier is using IPv6 to expand their networks. Google indicates that more than 15% of search queries in the US are now coming over IPv6, and this is increasing each week.


2. The costs of moving to IPv6 aren’t as high as you think

The costs of IPv6-enabling your public facing servers are actually are quite modest, and consist primarily of confirming that your external connectivity/ISP has enabled IPv6, and then configuring your existing firewalls, load balancing, and web servers with the additional IPv6 addresses. For many who have third-party hosting of their website, it’s quite possible that the much of work has already been done. The return on investment is quite real, since an increasing number of mobile users have IPv6-based connectivity and see faster performance from IPv6-enabled websites than IPv4-only websites (which must be accessed via dynamic translation.)


3. The longer you wait, the longer your competitors are gaining valuable experience working with IPv6 that you aren’t

Finally, when deciding whether putting off your IPv6 efforts make sense, it’s probably best to think about what happens at the end of that process. By deferring your experience with IPv6, you’re effectively putting your enterprise behind the technology curve compared to the marketplace and your competitors. At some point you will need to expend more resources at a faster rate to build the skills and competency needed to catch up. This is poor situation to put your technology team in, and may even surprise your financial folks with the sudden need to invest in new, more capable technology that your competition has been using for years. But there might be some good news – dealing with these consequences of delaying your IPv6 efforts is more likely going to be your successor’s problem, once the deferment and resulting impacts to the company become evident.


For more information on IPv6, go to Get6.


IPv4 Request Pipeline

By Richard Jimmerson, Chief Information Officer, ARIN

IPv4 pipeline

Today we have .20 of a /8 remaining in the ARIN IPv4 free pool. At the same time, we have over 200 open tickets from organizations requesting IPv4 address space from that free pool. These requests are for sizes ranging from a /23 to larger than a /16. This does not count the many open tickets we have for /24s.

IPv4 inventory 5.7.2015It is possible in the coming weeks we will have enough IPv4 address space requests in the pipeline to account for all the remaining IPv4 address space in the ARIN IPv4 free pool. Because of this, the first organization to elect to be placed on the waiting list for unmet resources may already have an open request for IPv4 address space today.

We are working hard to reduce the response times for IPv4 requests, but are at the same time being very precise about the order in which we review and respond to tickets. Strict adherence to our Phase 4 countdown procedures is more important than ever as we near the end of our IPv4 free pool. It is imperative that we review and respond to all tickets in the order they were received according to their timestamp.

When the first organization elects to be placed on the Waiting List for Unmet Requests, we will let you know. We will send an announcement out via our arin-announce mailing list, update you with another blog in this series, share it on social media, and issue a press release to notify the media about this milestone. We can’t predict exactly when this will happen, but we expect it to be soon. This will be a signal that full depletion of the ARIN IPv4 free pool is imminent.

Of course, organizations have options to obtain IPv4 address space through the transfer process and to request IPv6 address space from ARIN. We will share more information about the status of the ARIN IPv4 inventory in the coming weeks.