[arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs
Martin Hannigan
hannigan at gmail.com
Thu Aug 17 21:05:37 EDT 2023
From: ARIN-PPML <arin-ppml-bounces at arin.net> on behalf of William Herrin <
bill at herrin.us>
Date: Wednesday, August 16, 2023 at 5:17 AM
To: Reese, Gus <gReese at cogentco.com>
Cc: arin-ppml at arin.net <arin-ppml at arin.net>
Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4
allocation for IXPs
On Tue, Aug 15, 2023 at 7:33 PM Reese, Gus <gReese at cogentco.com> wrote:
[ clip ]
>> b. Permit a range of sizes (from as low as possibly /27 up to /24) upon
request, with no documentation needed.
>Sort of. If an IXP would qualify for a /27, they should be able to
>receive up to a /24 upon request with no -additional- documentation.
>They still have to qualify as an IXP for the /27 and it should still
>be understood as fraud if the addresses are used for a purpose other
t>han an IXP.
Which the current definition of three participants should be adequate for
this use case in the NRPM.
I'm a little lost on your fraud concern. If the addresses are used for the
peering LAN and other IXP related purposes like, usually through no fault
of their own, wedging some cache hosts in the space, are you concerned? If
they are used for a FTTH application? Sure. Pretty clear in that respect.
Thanks Bill.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20230817/8d81a36a/attachment.htm>
More information about the ARIN-PPML
mailing list