[arin-ppml] ARIN-2024-5 community feedback needed re: IXP additional allocations

[Martin Hannigan]

On Wed, May 14, 2025 at 12:28 PM Chris Woodfield <cwoodfield at gmail.com>
wrote:

> Hello all,
>
> While presenting Draft Policy ARIN-2024-5 at ARIN 55, it was noted in the
> room that the new Section 4.4 should include in the “Additional
> Allocations” subsection an accommodation for IXPs requesting an additional
> block where ARIN is unable to provide a sparse allocation, making the
> next-contiguous prefix unavailable. It was noted that IXPs should be able
> to receive a new allocation at the larger size, and be given sufficient
> time to renumber IXP infrastructure, along with their members’ peerings, to
> the new prefix and then return the original one once the renumbering is
> complete.
>

All facets of renumbering should fall well within the justification
process. I can't see a valid reason to expand language or to pile on
sections.


> One critical question that comes from this: The policy must specify a
> deadline for which the original prefix must be returned to ARIN, and I’m
> interested in the community’s take on what that deadline should be. In my
> experience, IXP participants are given a fairly limited amount of time
> (typically 30-60 days) to renumber, but I believe that ARIN policy should
> be more generous here, because there are always corner cases and
> stragglers. On the other hand, IXPs might prefer to have a tighter window
> codified in policy, as that might give them additional context when
> engaging with IXP participants who don’t prioritize renumbering.
>

The existing policy and draft proposal don't require the return of 4.4
resources. But that too might be accomplished during the justification
process to balance utilization requirements.

To scale this the scenario is the largest network peering at the largest
IX. In that scenario renumbering is complex and will take a long time. 24
months is not unreasonable operationally.

HTH,

-M<
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20250514/0b293553/attachment.htm>