Re: [arin-ppml] Draft Policy ARIN-2023-3: Amendment of the waitlist

h may have 3 unique ASN's *(say a route server, route collector, and management network) *- but are all operated by the same organization. That does not seem like a legitimate definition of an exchange point, especially when that operator is the only participant over several years. --Matt On

Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs

Oops, sorry the RIPE proposal number is 2023-01. On Wed, Jun 21, 2023 at 08:15 David Farmer wrote: > Actually, I expect the genesis of this proposal was the very similar > proposal in the RIPE community RIPE-2023-02 Reducing IXP IPv4 assignment > default size to a /26. That proposal followed a p

Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs

Actually, I expect the genesis of this proposal was the very similar proposal in the RIPE community RIPE-2023-02 Reducing IXP IPv4 assignment default size to a /26. That proposal followed a presentation at RIPE 86 last fall and a discussion on their address-policy-wg mailing late last year. The con

Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs

> On Jun 21, 2023, at 10:18 AM, Matt Peterson wrote: > It's clear this proposal did not receive feedback from those of us who > operate IXP's (or those who lived through the ep.net era). Renumbering events > are often multi-year efforts for an IXP, this "savings" is not worth the > operationa

Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs

It's clear this proposal did not receive feedback from those of us who operate IXP's *(or those who lived through the ep.net era).* Renumbering events are often multi-year efforts for an IXP, this "savings" is not worth the operational overhead. I'm not in support of this proposal.