Summary

  • Goodson says enterprises, school districts, local governments and hospitals in her customer conversations are affected by ARIN policy but rarely take part in its development.
  • ARIN’s process is open to the Internet community. The question is whether operational examples from those organizations reach the Section 6 proposals now under discussion.

A rulebook needs the people who use it

A network policy can be open to everyone and still hear from only a narrow slice of the people who have to live with it. Elizabeth Goodson’s argument starts with that gap. In her ARIN candidate questionnaire, she names enterprises, school districts, local governments and hospitals among the customers she talks with about network design and routing. She says these organizations are affected by policy but rarely join ARIN’s policy process.

Goodson knows the distance between a rule and its implementation from both sides of the cable. Her first telecom job after college was in a DSL technical-support call center. She moved through operations and engineering into network architecture and planning. She now leads Lightpath Fiber’s Data Network Planning team, which she says handles network design, strategic planning, product engineering, equipment and software certification, and standards. The team also codifies IP allocation and routing policy for its own network. She has guided the organization through ARIN resource transfers and RPKI ROAs.

That path gives her a specific reason to want a closer look at Section 6 of ARIN’s Number Resource Policy Manual, the IPv6 section. Goodson describes it as material first written for global coordination, inserted into the manual with limited updates over roughly two decades. Her first term on ARIN’s Advisory Council has included work with the Policy Experience Report Working Group, which turns ambiguities and operating problems into policy proposals. She says the group’s Section 6 work should prompt more proposals and engagement from the community.

ARIN’s own meeting record shows the topic has an operational edge. At ARIN 57, the official transcript of ARIN 57 identifies Goodson as a PERWG member and lists a Section 6 IPv6 allocations table topic with her, Gus Reese and Alison Wood. Minutes from the following Advisory Council meeting describe feedback about the complexity of the initial-allocation formula; one Fellow’s reaction was that users should not have to solve a math problem to understand it.

The live policy docket makes the question concrete. Draft Policy ARIN-2026-2, still listed as Under Discussion, proposes replacing formula- and utilization-based allocation mechanisms with a planning-based approach. Its draft text asks for a network plan, hierarchy, operational needs and growth projections. The policy page says what the proposal would change; it does not show that Goodson authored it. Her stated contribution is the wider one: bring more of the community’s operating experience into the debate.

ARIN’s Policy Development Process is open to the Internet community. Membership or customer status is not required to participate or submit a proposal; ARIN staff and Board members cannot file proposals. Goodson’s question is whether the organizations she names use that process. Her questionnaire gives no count of these organizations and no reason they stay away. That missing detail matters because a quiet constituency leaves fewer real network plans on the record when a rule is rewritten.

A policy manual is not a design review, but its criteria shape the evidence an applicant has to assemble. If a school district’s network plan, a hospital’s internal addressing needs or a local government’s growth horizon never enters policy discussion, the text is tested against fewer operating contexts. Goodson’s request is simple to state: let the people who translate allocation rules into networks help supply the examples before Section 6 changes again.

Primary records