[arin-ppml] Draft Policy ARIN-2019-1: Clarify Section 4 IPv4 Request Requirements (ARIN)

Wed Apr 17 14:45:18 EDT 2019

Having reviewed the previous language and the revised bit and can say that
is seems concise and any contract/clause writer would be proud.

On Wed, 17 Apr 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
> ******************************************
>
-- 

*r. LeVere harpervisual evangelist/c.l.g.mondo media.rlh*
*1+246+695-2375*

**CONSULTING HOURS:*
Monday - Thursday  by appointment.
[10 am-6pm]*

**Friday, Saturday and Sunday CLOSED**

This email message (including attachments, if any) is intended for the use
of the individual or entity to whom or which it is addressed and may
contain information that is privileged, proprietary, confidential, and
exempt from
disclosure If you are not the intended recipient, you are notified that any
dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify the sender and
erase this email message immediately.

The sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of email
transmission.
Thank You.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190417/62f45168/attachment.htm>