Summary

  • E. Marie Brierley’s ARIN Community Grant project joined ARIN address records, NIST service observations and BGP data to study the stages of enterprise IPv6 adoption. In its 2022 report, 727 of 1,000 tracked entities matched an ARIN Org ID; 551 of those had no IPv6 allocation from ARIN and 176 did.
  • The report counted 231 IPv6-enabled services, not 231 distinct organizations. In a later ARIN essay, Brierley argued that the evidence needed a new audience: marketing chiefs who could make and sponsor a business case for IPv6.

An address block can sit in a registry while a company’s website still speaks only IPv4. E. Marie Brierley wanted to know how often that journey stalled and where. Her ARIN Community Grant report described a database joining address acquisition to publicly observable web, DNS and email services. Counting IPv6 traffic was the easy, late-stage answer. She wanted to see the earlier decisions.

The first obstacle was wonderfully unglamorous: names. An organization in ARIN’s records did not always appear under the same label in NIST’s domain observations. Brierley’s team combined automated matching with manual review and found the join more difficult than expected. Their preliminary model of address acquisition could describe who requested space; it could not, by itself, say who had completed a deployment. Before making a grand claim about enterprise migration, they had to decide whether two database rows even represented the same enterprise.

The next project report gave the spreadsheet some teeth. Of 1,000 entities tracked by NIST, 727 could be matched to an ARIN Org ID. Among those 727, 551 had no IPv6 allocation from ARIN, while 176 did. The project found 231 enabled services across BGP, DNS, email and web observations. Its footnote mattered as much as the headline number: 231 counted services, so one organization could contribute more than one. Some dates even ran backwards, with service enablement apparently preceding address acquisition. Mergers and changing domains made the historical join harder. This was a 2022 research snapshot of linked records, with its seams visible.

Then Brierley changed rooms. In her 2023 ARIN essay, she argued that enterprise CIOs faced crowded budgets while their current addressing still appeared to function. Another technical case alone would struggle for a place on the calendar. She proposed speaking to chief marketing officers, whose teams already buy technology to improve customer journeys and measure commercial results. Her own example was a Reno user repeatedly placed by IP geolocation in other cities. It was an anecdote about a misplaced audience, and a way to ask who inside a company might care enough to fund the repair.

Her proposal was to translate an infrastructure upgrade into questions marketing could carry to finance: where does slow delivery affect a purchase, where does a wrong location spoil a campaign, and which applications are ready for IPv6? The ARIN grant data identified stages of adoption; it did not measure a revenue lift from the proposed pitch. Brierley’s point was organizational. A technical team can show that the network has work to do. A budget holder decides whether that work joins the company’s plans.