[arin-ppml] ARIN-PPML Draft 2019-1

Mon Jul 15 12:58:50 EDT 2019

Carlton- thank you for your comment.
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

Kat Hunter

On Mon, Jul 8, 2019 at 6:49 PM Carlton Samuels <carlton.samuels at gmail.com>
wrote:

> I support the change of language for this draft policy.
>
> Carlton Samuels
>
> On Mon, 8 Jul 2019, 3:16 pm Kat Hunter, <takokat81 at gmail.com> wrote:
>
>> Good afternoon,
>>
>> 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:
>>
>> Current language found in NRPM Section 4.1.8 - Unmet Requests:
>>
>> Repeated requests, in a manner that would circumvent 4.1.6, are not
>> allowed: an organization may only receive one allocation, assignment, or
>> transfer every 3 months, but ARIN, at its sole discretion, may waive
>> this requirement if the requester can document a change in circumstances
>> since their last request that could not have been reasonably foreseen at
>> the time of the original request, and which now justifies additional
>> space.
>>
>> Proposed new language:
>>
>> Repeated requests, in a manner that would circumvent 4.1.6 are not
>> allowed: an organization may not apply for IPv4 address resources under
>> this section if they have received an allocation, assignment, or
>> transfer of IPv4 resources less than three months prior, or if the
>> organization has transferred space to another party under Section 8 less
>> than 36 months prior. ARIN, at its sole discretion, may waive this
>> restriction if the requester can document a change in circumstances
>> since their last request that could not have been reasonably foreseen at
>> the time of the original request, and which now justifies additional
>> space.
>>
>>
>> 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.
>>
>> -Thanks
>> Kat Hunter
>>
>> On Thu, Apr 18, 2019 at 8:27 AM Brian Jones <bjones at vt.edu> wrote:
>>
>>> I support Draft Policy 2019-1 with the new proposed language.
>>>
>>> --
>>> Brian E Jones, CSP-SM, CSP-PO
>>> NI&S Virginia Tech
>>> bjones at vt.edu
>>>
>>> On Apr 18, 2019, at 7:20 AM, Rudolph Daniel <rudi.daniel at gmail.com>
>>> wrote:
>>>
>>>
>>> I support this draft proposal..
>>> RD
>>>
>>> On Wed, Apr 17, 2019 at 12:00 PM <arin-ppml-request at arin.net> wrote:
>>>
>>>> Send ARIN-PPML mailing list submissions to
>>>>         arin-ppml at arin.net
>>>>
>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>>         https://lists.arin.net/mailman/listinfo/arin-ppml
>>>> or, via email, send a message with subject or body 'help' to
>>>>         arin-ppml-request at arin.net
>>>>
>>>> You can reach the person managing the list at
>>>>         arin-ppml-owner at arin.net
>>>>
>>>> When replying, please edit your Subject line so it is more specific
>>>> than "Re: Contents of ARIN-PPML digest..."
>>>>
>>>>
>>>> Today's Topics:
>>>>
>>>>    1. Revised - Draft Policy ARIN-2019-1: Clarify Section 4 IPv4
>>>>       Request Requirements (ARIN)
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>>
>>>> Message: 1
>>>> Date: Tue, 16 Apr 2019 14:26:07 -0400
>>>> From: ARIN <info at arin.net>
>>>> To: arin-ppml at arin.net
>>>> Subject: [arin-ppml] Revised - Draft Policy ARIN-2019-1: Clarify
>>>>         Section 4 IPv4 Request Requirements
>>>> Message-ID: <6a411169-0e13-2087-d6f2-5176a56bfe28 at arin.net>
>>>> Content-Type: text/plain; charset=utf-8; format=flowed
>>>>
>>>> The following has been revised:
>>>>
>>>> * Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements
>>>>
>>>> Revised text is below and can be found at:
>>>> https://www.arin.net/participate/policy/drafts/2019_1/
>>>>
>>>> You are encouraged to discuss all Draft Policies on PPML. The AC will
>>>> evaluate the discussion in order to assess the conformance of this
>>>> draft
>>>> policy with ARIN's Principles of Internet number resource policy as
>>>> stated in the Policy Development Process (PDP). Specifically, these
>>>> principles are:
>>>>
>>>> * Enabling Fair and Impartial Number Resource Administration
>>>> * Technically Sound
>>>> * Supported by the Community
>>>>
>>>> The PDP can be found at:
>>>> https://www.arin.net/participate/policy/pdp/
>>>>
>>>> Draft Policies and Proposals under discussion can be found at:
>>>> https://www.arin.net/participate/policy/drafts/
>>>>
>>>> Regards,
>>>>
>>>> Sean Hopkins
>>>> Policy Analyst
>>>> American Registry for Internet Numbers (ARIN)
>>>>
>>>>
>>>>
>>>> Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements
>>>>
>>>> Problem Statement:
>>>>
>>>> Per a recent ARIN Policy Experience Report and resulting AC discussion,
>>>> it was noted that the language of Section 4.1.8 is imprecise in that it
>>>> can be interpreted as specifying a waiting period for any allocation
>>>> activity, as opposed to being intended to limit only the frequency of
>>>> IPv4 allocations under Section 4.
>>>>
>>>> The same Policy Experience Report also noted that ARIN staff has
>>>> observed a pattern where an organization transfers space under NRPM
>>>> Section 8.2 to a specified recipient, and then immediately applies for
>>>> space under Section 4. This activity appears to be speculative in
>>>> nature
>>>> and not consistent with sound address management policy.
>>>>
>>>> The updated language in this proposal addresses the two issues above,
>>>> as
>>>> both concerns can be addressed via modifications to the same section
>>>> and
>>>> sentence thereof of the NRPM:
>>>>
>>>> * Clarifies the waiting period to only prohibit requests for IPv4
>>>> allocations under Section 4 of the NRPM
>>>>
>>>> * Disallows organizations that have transferred space to other parties
>>>> within the past 36 months from applying for additional IPv4 space under
>>>> NRPM Section 4.
>>>>
>>>> Policy Statement:
>>>>
>>>> Current language found in NRPM Section 4.1.8 - Unmet Requests:
>>>>
>>>> Repeated requests, in a manner that would circumvent 4.1.6, are not
>>>> allowed: an organization may only receive one allocation, assignment,
>>>> or
>>>> transfer every 3 months, but ARIN, at its sole discretion, may waive
>>>> this requirement if the requester can document a change in
>>>> circumstances
>>>> since their last request that could not have been reasonably foreseen
>>>> at
>>>> the time of the original request, and which now justifies additional
>>>> space.
>>>>
>>>> Proposed new language:
>>>>
>>>> Repeated requests, in a manner that would circumvent 4.1.6 are not
>>>> allowed: an organization may not apply for IPv4 address resources under
>>>> this section if they have received an allocation, assignment, or
>>>> transfer of IPv4 resources less than three months prior, or if the
>>>> organization has transferred space to another party under Section 8
>>>> less
>>>> than 36 months prior. ARIN, at its sole discretion, may waive this
>>>> restriction if the requester can document a change in circumstances
>>>> since their last request that could not have been reasonably foreseen
>>>> at
>>>> the time of the original request, and which now justifies additional
>>>> space.
>>>>
>>>> Comments:
>>>>
>>>> This proposal incorporates two related policy goals, combined for
>>>> convenience in one proposal as both can addressed via modification of
>>>> the same section and sentence of the NRPM. During ARIN 43 it was
>>>> proposed to the community that the two policy statements were
>>>> severalble, however, there was sufficient community support behind
>>>> keeping both.
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> Subject: Digest Footer
>>>>
>>>> _______________________________________________
>>>> ARIN-PPML mailing list
>>>> ARIN-PPML at arin.net
>>>> https://lists.arin.net/mailman/listinfo/arin-ppml
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> End of ARIN-PPML Digest, Vol 166, Issue 24
>>>> ******************************************
>>>>
>>> _______________________________________________
>>> ARIN-PPML
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> https://lists.arin.net/mailman/listinfo/arin-ppml
>>> Please contact 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 (ARIN-PPML at arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> https://lists.arin.net/mailman/listinfo/arin-ppml
>>> Please contact 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 (ARIN-PPML at arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact 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/20190715/cbf01305/attachment.htm>