<div dir="ltr">Carlton- thank you for your comment. <div>All- Our Advisory Council meeting is this Thursday and I'd like to see if we can get any additional comments for moving this forward. If there are no comments, I will be moving this to a vote on the AC to get this in recommended status. Thanks</div><div><br></div><div>Kat Hunter</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 8, 2019 at 6:49 PM Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com">carlton.samuels@gmail.com</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="auto">I support the change of language for this draft policy.<div dir="auto"><br></div><div dir="auto">Carlton Samuels</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 8 Jul 2019, 3:16 pm Kat Hunter, <<a href="mailto:takokat81@gmail.com" target="_blank">takokat81@gmail.com</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">Good afternoon,<br><br>With the ARIN board recently adopting the AC's recommendation to re-instate the wait-list policy, we should now reconsider Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements draft policy in light of those changes. In the AC's recommendation, the specific part of this section remains unchanged. Would everyone like to proceed with the following changes:<br><br>Current language found in NRPM Section 4.1.8 - Unmet Requests:<br><br>Repeated requests, in a manner that would circumvent 4.1.6, are not <br>allowed: an organization may only receive one allocation, assignment, or <br>transfer every 3 months, but ARIN, at its sole discretion, may waive <br>this requirement if the requester can document a change in circumstances <br>since their last request that could not have been reasonably foreseen at <br>the time of the original request, and which now justifies additional space.<br><br>Proposed new language:<br><br>Repeated requests, in a manner that would circumvent 4.1.6 are not <br>allowed: an organization may not apply for IPv4 address resources under <br>this section if they have received an allocation, assignment, or <br>transfer of IPv4 resources less than three months prior, or if the <br>organization has transferred space to another party under Section 8 less <br>than 36 months prior. ARIN, at its sole discretion, may waive this <br>restriction if the requester can document a change in circumstances <br>since their last request that could not have been reasonably foreseen at <br>the time of the original request, and which now justifies additional space.<br><br><br>Would you like this to proceed to recommended draft as proposed? Feedback before the reinstatement of the wait list was very positive for this and we would appreciate any additional comments or verification on moving this to recommended draft.<br><div><br></div><div>-Thanks</div><div>Kat Hunter</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 18, 2019 at 8:27 AM Brian Jones <<a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.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>I support Draft Policy 2019-1 with the new proposed language.<div><br><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><div>--</div><div>Brian E Jones, CSP-SM, CSP-PO</div><div>NI&S Virginia Tech</div><div><a href="mailto:bjones@vt.edu" rel="noreferrer" target="_blank">bjones@vt.edu</a></div></div></div></div>
</div>
<div><br><blockquote type="cite"><div>On Apr 18, 2019, at 7:20 AM, Rudolph Daniel <<a href="mailto:rudi.daniel@gmail.com" rel="noreferrer" target="_blank">rudi.daniel@gmail.com</a>> wrote:</div><br class="gmail-m_2141087680939354790m_4181712567428658003gmail-m_4084140876737055924Apple-interchange-newline"><div><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:"times new roman",serif;font-size:large"><br clear="all"></div><div><div dir="ltr" class="gmail-m_2141087680939354790m_4181712567428658003gmail-m_4084140876737055924gmail_signature"><div dir="ltr"></div></div></div><span class="gmail_default">I support this draft proposal..</span></div><div><span class="gmail_default">RD</span></div><div dir="ltr"><span class="gmail_default" style="font-family:"times new roman",serif;font-size:large"></span></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 17, 2019 at 12:00 PM <<a href="mailto:arin-ppml-request@arin.net" rel="noreferrer" target="_blank">arin-ppml-request@arin.net</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">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arin-ppml-request@arin.net" rel="noreferrer" target="_blank">arin-ppml-request@arin.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arin-ppml-owner@arin.net" rel="noreferrer" target="_blank">arin-ppml-owner@arin.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ARIN-PPML digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Revised - Draft Policy ARIN-2019-1: Clarify Section 4 IPv4<br>
Request Requirements (ARIN)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 16 Apr 2019 14:26:07 -0400<br>
From: ARIN <<a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net" rel="noreferrer" target="_blank">arin-ppml@arin.net</a><br>
Subject: [arin-ppml] Revised - Draft Policy ARIN-2019-1: Clarify<br>
Section 4 IPv4 Request Requirements<br>
Message-ID: <<a href="mailto:6a411169-0e13-2087-d6f2-5176a56bfe28@arin.net" rel="noreferrer" target="_blank">6a411169-0e13-2087-d6f2-5176a56bfe28@arin.net</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
The following has been revised:<br>
<br>
* Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements<br>
<br>
Revised text is below and can be found at:<br>
<a href="https://www.arin.net/participate/policy/drafts/2019_1/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_1/</a><br>
<br>
You are encouraged to discuss all Draft Policies on PPML. The AC will <br>
evaluate the discussion in order to assess the conformance of this draft <br>
policy with ARIN's Principles of Internet number resource policy as <br>
stated in the Policy Development Process (PDP). Specifically, these <br>
principles are:<br>
<br>
* Enabling Fair and Impartial Number Resource Administration<br>
* Technically Sound<br>
* Supported by the Community<br>
<br>
The PDP can be found at:<br>
<a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br>
<br>
Draft Policies and Proposals under discussion can be found at:<br>
<a href="https://www.arin.net/participate/policy/drafts/" rel="noreferrer noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/</a><br>
<br>
Regards,<br>
<br>
Sean Hopkins<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements<br>
<br>
Problem Statement:<br>
<br>
Per a recent ARIN Policy Experience Report and resulting AC discussion, <br>
it was noted that the language of Section 4.1.8 is imprecise in that it <br>
can be interpreted as specifying a waiting period for any allocation <br>
activity, as opposed to being intended to limit only the frequency of <br>
IPv4 allocations under Section 4.<br>
<br>
The same Policy Experience Report also noted that ARIN staff has <br>
observed a pattern where an organization transfers space under NRPM <br>
Section 8.2 to a specified recipient, and then immediately applies for <br>
space under Section 4. This activity appears to be speculative in nature <br>
and not consistent with sound address management policy.<br>
<br>
The updated language in this proposal addresses the two issues above, as <br>
both concerns can be addressed via modifications to the same section and <br>
sentence thereof of the NRPM:<br>
<br>
* Clarifies the waiting period to only prohibit requests for IPv4 <br>
allocations under Section 4 of the NRPM<br>
<br>
* Disallows organizations that have transferred space to other parties <br>
within the past 36 months from applying for additional IPv4 space under <br>
NRPM Section 4.<br>
<br>
Policy Statement:<br>
<br>
Current language found in NRPM Section 4.1.8 - Unmet Requests:<br>
<br>
Repeated requests, in a manner that would circumvent 4.1.6, are not <br>
allowed: an organization may only receive one allocation, assignment, or <br>
transfer every 3 months, but ARIN, at its sole discretion, may waive <br>
this requirement if the requester can document a change in circumstances <br>
since their last request that could not have been reasonably foreseen at <br>
the time of the original request, and which now justifies additional space.<br>
<br>
Proposed new language:<br>
<br>
Repeated requests, in a manner that would circumvent 4.1.6 are not <br>
allowed: an organization may not apply for IPv4 address resources under <br>
this section if they have received an allocation, assignment, or <br>
transfer of IPv4 resources less than three months prior, or if the <br>
organization has transferred space to another party under Section 8 less <br>
than 36 months prior. ARIN, at its sole discretion, may waive this <br>
restriction if the requester can document a change in circumstances <br>
since their last request that could not have been reasonably foreseen at <br>
the time of the original request, and which now justifies additional space.<br>
<br>
Comments:<br>
<br>
This proposal incorporates two related policy goals, combined for <br>
convenience in one proposal as both can addressed via modification of <br>
the same section and sentence of the NRPM. During ARIN 43 it was <br>
proposed to the community that the two policy statements were <br>
severalble, however, there was sufficient community support behind <br>
keeping both.<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net" rel="noreferrer" target="_blank">ARIN-PPML@arin.net</a><br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
<br>
------------------------------<br>
<br>
End of ARIN-PPML Digest, Vol 166, Issue 24<br>
******************************************<br>
</blockquote></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" rel="noreferrer" 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" rel="noreferrer" target="_blank">info@arin.net</a> if you experience any issues.<br></div></blockquote></div><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" rel="noreferrer" 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 noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" rel="noreferrer" 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" rel="noreferrer" 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 noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" rel="noreferrer" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div>
</blockquote></div>