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

Owen DeLong owen at delong.com
Sun Aug 20 04:02:52 EDT 2023 


> On Aug 15, 2023, at 19:33, Reese, Gus <gReese at Cogentco.com> 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 some minds.  There is a potential scenario in which a large number of IXPs will arise based on relatively recent news item targeting underserved markets.  
>  
> The study cited in the original email to the PPML shows that more than 2 out of 3 IXPs globally have fewer than 32 members registered, for which a /26 is more than sufficient.
>  

What is true today may not be true tomorrow. Regardless of the number of new exchanges coming on board, I still believe that a /24 is a reasonable minimum assignment.

IPv4 should have been over quite some time ago. It’s relatively trivial to exchange dual-stack NLRI over multi-protocol BGP over IPv6.

On Juniper, this looks like this:

protocols { bgp { group <name> {
  neighbor <peer-v6-address> {
    local-address <local-v6-address>;
    family inet {
        unicast;
    }
    family inet6 {
        unicast;
    }
  }
} } }

There’s a similar construct available for FRR, Cisco, Arista, and many others as well.


> We want to gauge whether the community might support some combination of the following options to make this draft more balanced:
>  
> a. Permit larger assignment if the organization demonstrates an expected utilization of 50% of the requested block within 24 months. (similar to transfer requirements)

I strongly oppose this for the reasons stated above.

> b. Permit a range of sizes (from as low as possibly /27 up to /24) upon request, with no documentation needed.

I am slightly less opposed to this so long as it comes with additional instructions to ARIN staff to:

	1.	Reserve the remainder of the corresponding /24 for each longer prefix issued until such time as there
		are no available /24s to issue.

	2.	Expand the prefix to /24 upon request from the IX without any additional justification required.

Owen

>  
> We welcome the opinions of all community members.
>  
> Regards,
>  
> Gus
>  
> --
> Gus Reese
> ARIN Advisory Council
> greese at cogentco.com <mailto:greese at cogentco.com>
>  
> From: ARIN-PPML <arin-ppml-bounces at arin.net> On Behalf Of Andrew Dul
> Sent: Thursday, June 29, 2023 11:51 AM
> To: Kevin Blumberg <kevinb at thewire.ca>; arin-ppml at arin.net
> Subject: Re: [arin-ppml] Draft Policy ARIN-2023-2: /26 initial IPv4 allocation for IXPs
>  
> In 4.4 it does say “ARIN will make a list of these blocks publicly available.” Is that information available with the IXP name etc?
> I believe this is the list that ARIN is currently publishing.
>  
> https://www.arin.net/reference/research/statistics/microallocations/#micro-allocations-for-exchange-points
>  
> I was going to say it probably would be helpful if there was a machine readable format for this...but looks like someone already thought of that...
>  
> https://www.arin.net/participate/community/acsp/suggestions/2019/2019-24/
>  
> Andrew
>  
> On 6/29/2023 8:42 AM, Kevin Blumberg wrote:
> I don’t support this policy. 
>  
> I’ll echo what other operators have said, renumbering is non-trivial at an IXP.
>  
> Is ARIN even able to provide reverse DNS delegation for a /26 at this point?
>  
> The CI pool is in my mind working as intended, the drawn down from the pool as shown earlier has been reasonable.
>  
> If the definition of who is an IXP for the purposes of getting space, that is an entirely different proposal and problem statement. In 4.4 it does say “ARIN will make a list of these blocks publicly available.” Is that information available with the IXP name etc? 
>  
> Thanks,
>  
> Kevin Blumberg
>  
> From: ARIN-PPML <arin-ppml-bounces at arin.net> <mailto:arin-ppml-bounces at arin.net> On Behalf Of Matt Peterson
> Sent: Wednesday, June 21, 2023 4:19 AM
> To: arin-ppml at arin.net <mailto:arin-ppml at 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 lived through the ep.net <http://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. This is a solution looking for a problem, we have both the appropriate pool size and a method to refill.
>  
> If anything, the 4.4 requirement language around "other participants (minimum of three total)" could use some attention. ARIN's service region has many "shadow IXP's", which 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 Tue, Jun 20, 2023 at 8:54 AM ARIN <info at arin.net <mailto:info at arin.net>> wrote:
> 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
> 
> 
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net <mailto:ARIN-PPML at arin.net>).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net <mailto:info at arin.net> if you experience any issues.
>  
> 
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20230820/cdef8fab/attachment.htm>

More information about the ARIN-PPML mailing list