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

2023-08-22 Thread Martin Hannigan
On Sun, Aug 20, 2023 at 4:04 AM Owen DeLong via ARIN-PPML < arin-ppml@arin.net> wrote: > > > On Aug 15, 2023, at 19:33, Reese, Gus wrote: > > Greetings, > > The ARIN AC is hearing some initial opposition on the draft policy but we > are also sensing that some changes to the policy might change

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

2023-08-20 Thread Owen DeLong via ARIN-PPML
Kevin Blumberg > > From: ARIN-PPML > <mailto:arin-ppml-boun...@arin.net> On Behalf Of Matt Peterson > Sent: Wednesday, June 21, 2023 4:19 AM > To: arin-ppml@arin.net <mailto:arin-ppml@arin.net> > Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 init

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

2023-08-18 Thread William Herrin
On Thu, Aug 17, 2023 at 6:06 PM Martin Hannigan wrote: > I'm a little lost on your fraud concern. In fairness, so am I. I guess what I'm trying to say is that where generic assignments can be later repurposed by the registrants to uses other than the ones which justified their assignment, should

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

2023-08-17 Thread Martin Hannigan
From: ARIN-PPML on behalf of William Herrin < b...@herrin.us> Date: Wednesday, August 16, 2023 at 5:17 AM To: Reese, Gus Cc: arin-ppml@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 wrote:

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

2023-08-17 Thread Martin Hannigan
day, August 15, 2023 at 10:33 PM To: arin-ppml@arin.net Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs Greetings, The ARIN AC is hearing some initial opposition on the draft policy but we are also sensing that some changes to the policy might change some mi

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

2023-08-16 Thread William Herrin
On Tue, Aug 15, 2023 at 7:33 PM Reese, Gus wrote: > a. Permit larger assignment if the organization demonstrates an expected > utilization of 50% of the requested block within 24 months. (similar to > transfer requirements) No. > b. Permit a range of sizes (from as low as possibly /27 up to

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

2023-08-15 Thread Reese, Gus
, Kevin Blumberg From: ARIN-PPML <mailto:arin-ppml-boun...@arin.net> On Behalf Of Matt Peterson Sent: Wednesday, June 21, 2023 4:19 AM To: arin-ppml@arin.net<mailto:arin-ppml@arin.net> Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs It's clear this

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

2023-06-29 Thread Andrew Dul
:*ARIN-PPML *On Behalf Of *Matt Peterson *Sent:* Wednesday, June 21, 2023 4:19 AM *To:* arin-ppml@arin.net *Subject:* 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

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

2023-06-29 Thread Kevin Blumberg
From: ARIN-PPML On Behalf Of Matt Peterson Sent: Wednesday, June 21, 2023 4:19 AM To: arin-ppml@arin.net Subject: 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

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

2023-06-21 Thread David Farmer via ARIN-PPML
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

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

2023-06-21 Thread David Farmer via ARIN-PPML
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

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

2023-06-21 Thread Bill Woodcock
> 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 >

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

2023-06-21 Thread Matt Peterson
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.

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

2023-06-20 Thread David Farmer via ARIN-PPML
t; > > > Jason Byrne > > Senior Customer Success Analyst > > ARIN > > > > *From: *ARIN-PPML on behalf of David Farmer > via ARIN-PPML > *Reply-To: *David Farmer > *Date: *Tuesday, June 20, 2023 at 1:53 PM > *To: *Chris Woodfield > *Cc: *&quo

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

2023-06-20 Thread Scott Leibrand
As an IXP participant, +1 to continuing to allocate IXPs /24s upon request whenever doing so will mean IXP participants don’t have to subsequently renumber. But for IXPs with no credible plans to need a /24, no objections to allocating a smaller block by default. Scott > On Jun 20, 2023, at

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

2023-06-20 Thread William Herrin
On Tue, Jun 20, 2023 at 8:54 AM ARIN wrote: > ARIN will make IPv4 micro-allocations to critical infrastructure providers of > the Internet, including public internet exchange points (IXPs), core DNS > service providers (e.g. ICANN-sanctioned root and ccTLD operators) as well as > the RIRs and

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

2023-06-20 Thread Jason Byrne
; Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs Before making a judgment on this policy, I would like to know how Micro-Allocations for IXPs have been made by ARIN in each of the last 6 years. Why 6 years? It’s twice the 3-years window of the replenishm

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

2023-06-20 Thread Martin Hannigan
PM To: Martin Hannigan Cc: andrew@quark.net , Chris Woodfield , arin-ppml@arin.net Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs Regardless of whether this will break anything or not, IMHO, it is yet another (futile) effort at rearranging the IPv4 deck cha

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

2023-06-20 Thread Delong.com via ARIN-PPML
PML on behalf of Andrew Dul > > Date: Tuesday, June 20, 2023 at 2:04 PM > To: Chris Woodfield > Cc: arin-ppml@arin.net > Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 > allocation for IXPs > > Indeed, we therefore have to define priorities of

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

2023-06-20 Thread Martin Hannigan
ate: Tuesday, June 20, 2023 at 2:04 PM To: Chris Woodfield Cc: arin-ppml@arin.net Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs Indeed, we therefore have to define priorities of allocations for the depleted IPv4 pool. I wanted to point out that if the commun

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

2023-06-20 Thread Martin Hannigan
PML on behalf of Andrew Dul Date: Tuesday, June 20, 2023 at 1:43 PM To: arin-ppml@arin.net Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs I'd also like to point out that we already have a method for refilling the IXP pool as needed. The current policy sta

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

2023-06-20 Thread Andrew Dul
Indeed, we therefore have to define priorities of allocations for the depleted IPv4 pool. I wanted to point out that if the community believed that sticking with the /24 allocations is best for IXPs then it appears we have sufficient resources to do so into the future.  At the present time

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

2023-06-20 Thread Chris Woodfield
Andrew - You are correct that the micro-allocation pool can be replenished as needed from returned allocations. That said, it should be noted that IPv4 allocations used for this purpose would be resources that, under current policy, would have presumably been allocated to organizations via the

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

2023-06-20 Thread David Farmer via ARIN-PPML
Before making a judgment on this policy, I would like to know how Micro-Allocations for IXPs have been made by ARIN in each of the last 6 years. Why 6 years? It’s twice the 3-years window of the replenishment policy. How much of the pool that is left is helpful to know. However, without also

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

2023-06-20 Thread Andrew Dul
I'd also like to point out that we already have a method for refilling the IXP pool as needed.  The current policy states that ARIN should maintain at least a 3 year supply for these reserved pools and so far it would also seem that the returns to ARIN appear to be sufficient to add to the

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

2023-06-20 Thread Ron Grant
The policy properly differentiates between allocations for IXPs which do NOT need global reachability and allocations which do - however it places a too-onerous restriction on the initial allocation: 4.4.1 Micro-allocations for Internet Exchange Points (IXPs) An IXP requesting an initial

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

2023-06-20 Thread Chris Woodfield
Speaking as the proposal author: It appears that a URL included in the draft language has been inadvertently eaten by formatting. The Statistics & Reporting link is here: https://www.arin.net/reference/research/statistics/#ipv4-reserved-pool-status-nrpm-4-10-ipv6-deployments I’ll also note

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

2023-06-20 Thread Matthew Wilder via ARIN-PPML
Hi Owen, It sounds as though your opposition to this draft policy includes a concern that it is not technically sound. In what ways do you believe that this change would break the Internet or contort it? Thanks, Matthew On Tue, Jun 20, 2023 at 9:45 AM Owen DeLong via ARIN-PPML <

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

2023-06-20 Thread Owen DeLong via ARIN-PPML
We’re 12 years past IANA runout and only 50% of this reservation has been depleted. Seems to me that things are working as intended. There is no plan or expectation that n IPv4 free pool will last indefinitely into the future, nor should we be making attempts to do so on any level. I oppose

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

2023-06-20 Thread ARIN
On 15 June 2023, the ARIN Advisory Council (AC) accepted “ARIN-prop-320: /26 initial IPv4 allocation for IXPs” as a Draft Policy.   Draft Policy ARIN-2023-2 is below and can be found at:   https://www.arin.net/participate/policy/drafts/2023_2   You are encouraged to discuss all Draft Policies on