Summary

  • At ARIN 58 on 23 October 2026, Lee Howard introduced the Board's IPv6 Task Force and asked the community to identify, record and prioritize practical deployment obstacles.
  • The group is considering an ARIN IPv6 program, a peer-support tool and measures of success. Howard chairs a three-voting-member task force whose Board-approved term runs through 2027 unless extended.

There is a shelf somewhere full of presentations explaining that IPv6 is important. Lee Howard did not ask ARIN 58 for another shelf. According to ARIN's account of the meeting, he said adoption is no longer mainly an awareness problem. The task force he chairs wants to hear which part of a deployment becomes a nuisance, a cost or a dead end, then decide what ARIN can help operators do about it.

His proposed work has three parts: recommend the structure of an ARIN IPv6 program, explore a way for the community to help peers with specific IPv6 problems, and define how success would be measured. Howard invited operators to tell him, Rob Seastrom and Tina Morris how to identify, record and prioritize the obstacles. A list may sound less grand than a launch slogan. It is much harder to hide an unresolved item on a list.

The Board's August draft minutes give the assignment a boundary. The Board adopted an amended charter for three voting members, with the work scheduled to end in 2027 unless the Board later extends it. Howard volunteered and was named chair. The minutes establish a task force, not a finished IPv6 program; the October meeting was its public invitation to bring the stubborn details into view.

Howard knows the language of incentives too. In a 2024 article he wrote for ARIN, he argued that organizations with underused IPv4 addresses could release some of that value to fund IPv6 work. In the same essay, he drew a less convenient distinction: phones and computers generally handled IPv6 well, while many other consumer and IoT devices did not as of mid-2024. Money can authorize a migration; an incompatible device can still ruin a Tuesday afternoon. The 2026 task force's obstacle-first approach starts where that sales pitch ends.

Howard's ARIN biography runs through IETF IPv6 working groups, the Internet Architecture Board and network operations. That background gives him a reason to ask for named failure modes rather than one more confidence graph. The task force cannot configure a company's routers for it. It can make recurring problems visible, connect people who solved them to people still stuck, and show whether the advice changed any deployment outcome. Those are the claims the proposed program will have to earn.

An IPv6 campaign can fill a room. An obstacle register can reveal what everyone in the room has been stepping around. Howard has asked for the latter; now operators have to bring the bruises and the task force has to keep count.