[arin-ppml] Revised - Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6 Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests

[Kat Hunter]

All - We haven't received a lot of comments on 2019-9. If you have time
today, could you please comment for or against moving forward with this
policy?  Do you feel this proposal would remove the potential for duplicate
requests under these sections? Thank you in advance for any comments

Kat Hunter

On Thu, May 23, 2019 at 12:44 PM ARIN <info at arin.net> wrote:

> The following has been revised:
>
> * Draft Policy ARIN-2019-9: Clarify Interactions Between NRPM 4.10 IPv6
> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests
>
> Revised text is below and can be found at:
> https://www.arin.net/participate/policy/drafts/2019_9/
>
> 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-9: Clarify Interactions Between NRPM 4.10 IPv6
> Transition Space Requests and NRPM 4.1.8.2 Unmet Needs Requests
>
> Problem Statement:
>
> It has been observed that an organization requesting IPv4 resources
> under NRPM Section 4.10, Dedicated IPv4 Block To Facilitate IPv6
> Deployment, can also request similar or the same resources under Section
> 4.2.1.8, Unmet Needs. This proposal aims to remove this potential for
> duplicate requests under these sections.
>
> Policy Statement:
>
> Section 4.1.8.2, Unmet Needs:
>
> Current language: Any requests met through a transfer will be considered
> fulfilled and removed from the waiting list.
>
> Proposed language:
>
> Any requests met through a transfer or an allocation request fulfilled
> under Section 4.10 will be considered fulfilled and removed from the
> waiting list.
>
> Timetable for Implementation: Immediate
>
> Anything Else:
>
> Currently, organizations can receive no more than a /24 at a time under
> Section 4.10. However, Proposal ARIN-PROP-266, submitted by Chris Tacit
> and myself, could potentially allow an org to receive up to a /21 under
> that section, widening the potential for abuse by “double-dipping”
> waiting list and transition space requests. As such, this proposal
> should be considered in that context.
> _______________________________________________
> 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/90d01f05/attachment.htm>