[arin-ppml] Transferring Waiting List Space - Feedback Requested
Mike Burns
mike at iptrading.com
Mon Nov 14 18:48:09 EST 2022
Hi David,
To prevent a recurrence of the RIPE new-entrants-pool fiasco, I think a demonstration of need will suffice to prevent gaming.
And changing from a /22 to a /24 reduces the incentive to game by 75%.
But it would be interesting to hear other ideas.
Regards,
Mike
---- On Mon, 14 Nov 2022 18:35:27 -0500 David Farmer via ARIN-PPML <arin-ppml at arin.net> wrote ---
Conceptually, as an abstract idea, I have no problem with restricting the waiting list to newcomers only. However, the implementation of such a restriction could prove problematic; What is a true newcomer? How do we prevent gaming of this restriction?
The current 60-month restriction on transfers is already functionally indefinite, at least in my option.
Finally, the waiting list was never intended as a viable option to meet a network's need for resources; its purpose in policy is to ensure ARIN has a mechanism to distribute any IPv4 resources that are reclaimed or otherwise become available to ARIN.
Thanks.
On Mon, Nov 14, 2022 at 5:09 PM Fernando Frediani <mailto:fhfrediani at gmail.com> wrote:
Then need to detail and analyze what sound unreasonable in
changing 5 years period to indefinite.
Reducing the request size to anything smaller than an /22 is
giving a such small and useless space that will probably make no
difference to whoever receives it. A /22 is already a very small
amount (almost symbolic) but at least gives the ability to a newer
organizations to work with something, get into the market,
innovate, reach some proper size and then invest in different
technologies to make better usage of few IPv4 and deploy IPv6
properly in order to keep existing in the market. Plus giving out
/24-only to organizations in the waiting list would contribute
even more to increase the size of the routing table with very
little gain.
A change in the waiting-list rules that would be certainly be
welcome is restrict it only to newcomers that have no IPv4 space
at all. Those who already have had already enough time to learn
live with what they have and organize themselves to either do IPv4
transfers and deploy IPv6 in order to reduce its dependency
whenever possible.
Fernando
On 14/11/2022 19:53, David Farmer via
ARIN-PPML wrote:
I reviewed the Policy Implementation and
Experience Report presented at ARIN 50;
https://www.arin.net/participate/meetings/ARIN50/materials/1020_policyimplementation.pdf
https://www.youtube.com/watch?v=RruDSG32D0M&list=PL726kQ53RX6i-x05T2JLckh59gWtLs1TR&t=5569s
https://www.arin.net/participate/meetings/ARIN50/day1_transcript/#policy-implementation-and-experience-report
I don't support any changes to the transfer provisions of
the waiting list. The current transfer provisions seem
reasonable to me.
However, if I were going to support any changes to the
waiting list, I would support reducing the request size from
/22 to /24.
Thanks.
On Mon, Nov 14, 2022 at 3:42
PM WOOD Alison * DAS <mailto:Alison.WOOD at das.oregon.gov>
wrote:
Hello!
The Policy Experience Report
Working Group has been working on the Policy
Experience Report from ARIN 50. I would appreciate
your feedback on the following issue regarding
transferring waitlist space.
The current wait list criteria
is:
Must have a /20 or less in total IPv4 holdings.
May request up to a /22.
Removed from list if IPv4 received via 8.3/8.4
transfer.
Received ip space is eligible for needs-based
transfer after five years.
The Policy Experience Working
Group would like your feedback on a potential policy
that would restrict the transfer of IP space that
has been obtained from the waiting list. In other
words, any IP address space received from the
waiting list would be ineligible for transfer
indefinitely and encouraged to be returned to ARIN
if not in use. This policy would be specific to
transfers and not M & A’s.
The working group appreciates
your feedback.
Thank you!
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed
to
the ARIN Public Policy Mailing List (mailto:ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact mailto:info at arin.net if you
experience any issues.
--
===============================================
David Farmer mailto:Email%3Afarmer at 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 (mailto:ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact 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 (mailto:ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact mailto:info at arin.net if you experience any issues.
--
===============================================
David Farmer mailto:Email%3Afarmer at 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 (mailto:ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact mailto: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/20221114/af1995d3/attachment.htm>
More information about the ARIN-PPML
mailing list