<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta content="text/html; charset=utf-8">
</head>
<body>
<div style="font-size:10pt">
<div dir="auto"><i><span style="background-color:rgb(255,255,255); color:rgb(51,51,51); font-size:16.1px">I also support the updated language in this proposal and the issues it addresses.</span></i></div>
<div dir="auto"><i><br>
</i></div>
<div>
<div dir="auto" style="font-size:9pt"><i>Mike Arbrouet</i></div>
<div dir="auto" style="font-size:9pt"><br>
</div>
</div>
</div>
<div style="font-size:10pt">
<div dir="auto"><br>
</div>
<div dir="auto">------ Original message------</div>
<div dir="auto"><b>From: </b>Rudolph Daniel</div>
<div dir="auto"><b>Date: </b>Thu, Apr 18, 2019 6:23 AM</div>
<div dir="auto"><b>To: </b>arin-ppml@arin.net;</div>
<div dir="auto"><b>Cc: </b></div>
<div dir="auto"><b>Subject:</b>Re: [arin-ppml] ARIN-PPML Draft 2019-1</div>
<div dir="auto"><br>
</div>
</div>
<div>
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-family:times new roman,serif; font-size:large; color:#000000">
<br clear="all">
</div>
<div>
<div dir="ltr" class="gmail_signature">
<div dir="ltr"></div>
</div>
</div>
<span class="gmail_default" style="">I support this draft proposal..</span></div>
<div><span class="gmail_default" style="">RD</span></div>
<div dir="ltr"><span class="gmail_default" style="font-family:"times new roman",serif; font-size:large; color:rgb(0,0,0)"></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">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" 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" 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" 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" 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" target="_blank">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net" 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" 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" 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" 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" 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" target="_blank">ARIN-PPML@arin.net</a><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>
<br>
<br>
------------------------------<br>
<br>
End of ARIN-PPML Digest, Vol 166, Issue 24<br>
******************************************<br>
</blockquote>
</div>
</div>
</div>
</body>
</html>