Hello, As someone building a small, IPv6-first hosting network, I think we should consider requiring demonstrable progress toward IPv6 deployment as a condition of receiving IPv4 space from the waitlist.
I understand why small and new networks still need IPv4. Even when a network is designed around IPv6, it needs a way to communicate with users and services that only support IPv4. Access to limited IPv4 space can help those networks get started. At the same time, I think allocating scarce recovered space should come with a reasonable expectation that the recipient is actively deploying IPv6. For an operating network, that could mean demonstrating working IPv6 connectivity and making relevant services or customer connectivity available over IPv6. Simply obtaining an IPv6 allocation would not demonstrate much progress by itself. Provider-assigned IPv6 should count too. The requirement would need to account for new networks that need IPv4 compatibility to launch. How could we define meaningful, verifiable deployment milestones without creating a circular requirement or an expensive compliance process? I also wouldn’t tie eligibility to a particular percentage of IPv6 traffic, since that depends partly on the networks users are connecting from. I’d appreciate hearing everyone’s thoughts, particularly what evidence would demonstrate genuine progress while remaining practical for small operators. Thanks, Charlie Fish rrainn LLC AS403070 > On Oct 27, 2026, at 6:09 AM, Jones, Brian <[email protected]> wrote: > > > At ARIN 58 the NRPM Working Group introduced this table topic and garnered a > bit of discussion about the community’s thoughts concerning the Waitlist. > Posting here for broader exposure and to solicit more community feedback. > > _________________________________________________________________________________ > Table Topic - If the Waitlist didn’t exist, what would? > > Discussions about how ARIN would handle the return of IP address space became > a central topic. > > There was much discussion around auctioning off IPv4 addresses after that > topic was brought up. It was pointed out that there are legal and ethical > issues to consider for what ARIN would do with and resources from this. There > was discussion about how the money would be used if such a decision was made > to auction off IPv4 address space. > > It was expressed that no new policy would have to replace the Waitlist, that > by default ARIN would continue allocate IPv4 address space out of section 4.4 > and 4.10 of the NRPM and that IPv4 resources would be replenished with any > returned or reclaimed resources to the reserved pools as is indicated by the > NRPM. > > There were also discussions about combining sections 4.4 and 4.10 of the NRPM > and removing the Waitlist while also relaxing the requirement for acquiring > these resources concerning transitioning to IPv6. Relaxing the requirement > from you must have an IPv6 transition plan to acquire any resources from this > space to something like “with preference given for those transitions to > IPv6”. The hard requirement for transitioning to IPv6 was brought up as an > impediment for those who may not have the money for purchasing newer network > equipment to support IPv6 and at least in some Caribbean regions it may take > the local government involvement before network operators can even consider > moving toward IPv6. This was expressed at a previous table topic discussion > at ARIN 56 I believe. > > At least one participant asked if it was possible for ARIN to provide a > report on where waitlist allocations go after they are fulfilled. > Specifically, do they go to small ISPs, wind up in the market for leasing, or > elsewhere? > > It was also mentioned that if an entity has a viable business plan that > requires IPv4 then they should have included the cost for purchasing or > leasing those resources because the Waitlist has no guarantees for available > IPv4 resources, so does there remain any reason to maintain a Waitlist > becomes the question. > _________________________________________________________________________________ > > _ > Brian Jones > ARIN Advisory Council > NRPM WG Chair > _______________________________________________ > ARIN-PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. _______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
