Oops, sorry the RIPE proposal number is 2023-01. On Wed, Jun 21, 2023 at 08:15 David Farmer <far...@umn.edu> 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 presentation at RIPE 86 > last fall and a discussion on their address-policy-wg mailing late last > year. The conversation started with a reduction to /29, and a reasonable > compromise of /26 that was written in to a formal proposal earlier this > year. That proposal is progressing through their process and just finished > their Discussion Phase last week, and has entered their Review Phase, and > at least seems to be heading towards being policy in the RIPE community. > > While I do not support this proposal, especially as written, it is > nevertheless an important and timely conversation for the ARIN community to > have and I for one appreciate it being brought forward to our community as > a proposal. > > Thanks. > > On Wed, Jun 21, 2023 at 03:19 Matt Peterson <m...@peterson.org> 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 >> <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 <i...@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@arin.net). >> Unsubscribe or manage your mailing list subscription at: >> https://lists.arin.net/mailman/listinfo/arin-ppml >> Please contact i...@arin.net if you experience any issues. > > >> -- > =============================================== > David Farmer Email:far...@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > -- =============================================== David Farmer Email:far...@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
_______________________________________________ ARIN-PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML@arin.net). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact i...@arin.net if you experience any issues.
