<div dir="ltr"><div>Hi all -</div><div>Alyssa and I are shepherding this on behalf of the AC. Given the varying, thoughtful opinions, I'd like to prod to see if anyone else has thoughts one way or the other on this draft.</div><div><br></div><div>Anita<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 19, 2020 at 6:26 PM Alyssa Moore <<a href="mailto:alyssa@alyssamoore.ca">alyssa@alyssamoore.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi folks, <br><br>There was some great discussion of this policy proposal at ARIN45. We hear a wide range of views including:<br><ol><li>Don't grandfather organizations. The new waitlist policy is sound. </li><li>Organizations that were on the waitlist before 2019-16 should be eligible for their original request size (even if it exceeds the new limit of a /22). </li><li>Organizations that were on the waitlist before 2019-16 should remain eligible if their holdings exceed a /20 OR a /18. The draft policy under discussion specifies a /18 total holdings for grandfathered orgs, while the current waitlist policy (2019-16) specifies a /20.</li><li>Organizations that were on the waitlist before 2019-16 should be eligible regardless of their total holdings because that was not a restriction of the policy under which they originally qualified for the waitlist. <br></li></ol><div> There was general support to continue finessing this draft. If you have views on the above noted parameters, please make them known here.</div><div><br></div><div>For reference: <br><br><b>Old waitlist policy</b></div><div><ol><li>Requester specifies smallest block they'd be willing to accept, equal to or larger than the applicable minimum size specified elsewhere in ARIN policy.<br></li><li>Did not place a limit on the total existing IP address holdings of a party eligible for the waitlist.<br></li><li>Made resources issued from the waitlist ineligible for transfer until after a period of 12 months. </li></ol><b>New Waitlist Policy</b><br><ol><li>Limits the size of block ARIN can issue on the waitlist to a /22.<br></li><li>Places a limit on the total existing IP address holdings of a party eligible for the waitlist at a /20 or less.<br></li><li>Makes resources issued from the
waitlist ineligible for transfer until after a period of 60 months. <br></li></ol><div><br>Best, <br>Alyssa</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 26, 2020 at 3:35 PM David Farmer <<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">I support this policy and believe the policy development process is the proper place to handle this issue. However, this policy seems to be implementable as a one-time policy directive to ARIN Staff. Once implemented, by putting the effected organizations back on the waiting list, it seems unnecessary to memorialized the text in the NRPM, it would immediately become extraneous and potentially confusing to future readers of the NRPM.<div><br></div><div>Therefore, I would like to recommend the Policy Statement not be added to the NRPM upon its implementation. I believe this to be consistent with the intent of the policy. Otherwise, does ARIN Staff have procedural advice on how best to handle what seems like a one-time directive?</div><div><br></div><div>Thanks</div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Tue, Mar 24, 2020 at 12:21 PM ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>> wrote:</div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
Draft Policy ARIN-2020-2: Grandfathering of Organizations Removed from <br>
Waitlist by Implementation of ARIN-2019-16<br>
<br>
Problem Statement:<br>
<br>
The implementation of the ARIN-2019-16 Advisory Council Recommendation <br>
Regarding NRPM 4.1.8: Unmet Requests caused some organizations to be <br>
removed from the waiting list that were approved under the old policy’s <br>
eligibility criteria. These organizations should have been grandfathered <br>
when the waitlist was reopened to allow them to receive an allocation of <br>
IPv4 up to the new policy’s maximum size constraint of a /22.<br>
<br>
Policy Statement: Update NRPM Section 4.1.8 as follows:<br>
<br>
Add section 4.1.8.3 (temporary language in the NRPM to remain until the <br>
policy objective is achieved)<br>
<br>
Restoring organizations to the waitlist<br>
<br>
ARIN will restore organizations that were removed from the waitlist at <br>
the adoption of ARIN-2019-16 to their previous position if their total <br>
holdings of IPv4 address space amounts to a /18 or less. The maximum <br>
size aggregate that a reinstated organization may qualify for is a /22.<br>
<br>
All restored organizations extend their 2 year approval by [number of <br>
months between July 2019 and implementation of new policy]. Any requests <br>
met through a transfer will be considered fulfilled and removed from the <br>
waiting list.<br>
<br>
Comments:<br>
<br>
Timetable for implementation: Immediate<br>
<br>
Anything Else: While attending ARIN 44 and discussing this with other <br>
community members the vast majority indicated that they agreed that some <br>
organizations were treated unfairly. This proposal is a remedy.<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a rel="noreferrer" href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div></div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div></div>