[arin-ppml] Board of Trustees Remands Recommended Draft Policy ARIN-2017-12

[David Farmer]

Here are some simplified text and a update the title.  I think using an "at
least one" standard creates an appropriate burden for organizations
submitting reallocation or detailed reassignment requests while ensuring
POCs are notified and there is minimal validity based on the standard in
section 3.6.5. Having all POCs valid for a request to move forward is
probably too high of a burden for organizations submitting reallocation or
detailed reassignment requests.

3.7 POC Notification and Validation Upon Reassignment or Reallocation

When an organization submits a reallocation or detailed reassignment
request to ARIN, it must contain at least one POC object which is currently
valid in the ARIN database.  If none the POC objects are valid, ARIN shall
immediately reject the request.

ARIN will notify, via email, all POC objects associated with such requests
as to its result, successful or rejected, along with a request to validate
any invalid POC objects.


On Thu, Oct 25, 2018 at 1:35 PM David Farmer <farmer at umn.edu> wrote:

> I like this approach. However, I have a question, do all the POC objects
> need to be valid or does at least one of the POC objects need to be valid?
>
> If we care we might want to be more specific on that point, I think it is
> possible to read the current text either way right now.
>
> I think I like at least one POC MUST be valid, then notify all POCs of the
> detailed reassignment or reallocation, and of any other POCs that are
> invalid.
>
> In other words, only fail if all the POCs are invalid.
>
> Thanks
>
> On Sat, Oct 20, 2018 at 1:23 PM Andrew Dul <andrew.dul at quark.net> wrote:
>
>> I'd like to propose to the community a rewrite of 2017-12 that would
>> hopefully bring it in line with the Implementation B option of the Staff
>> Implementation memo.
>>
>> What do others think of this approach?
>>
>> Andrew
>>
>>
>> ===
>>
>> Policy statement:
>>
>> Insert one new section into NRPM 3:
>>
>> 3.7 POC Validation Upon Reassignment or Reallocation
>>
>> When an organization submits a valid reallocation or detailed
>> reassignment request to ARIN, the reallocation or reassignment record must
>> contain POC objects which are currently valid in the ARIN database.  If the
>> POC objects are not valid, ARIN shall immediately reject the reallocation
>> or reassignment request.
>>
>> If the reassignment or relocation record is inserted into the database,
>> ARIN will email the POCs associated with the new record notifying them of
>> the new resource being attached to their POC.
>>
>> If the reassignment or relocation record fails to be inserted because the
>> POCs are not currently valid, ARIN should send an email notification to the
>> associated POCs that a reassignment or reallocation record was rejected
>> because their POC is not currently valid, and provide a link for the user
>> to validate their POC.
>>
>>
>>
>> On 8/27/2018 8:12 AM, John Curran wrote:
>>
>> On 16 Aug 2018, at 7:04 PM, ARIN <info at arin.net> <info at arin.net> wrote:
>>
>> On 31 July 2018, the ARIN Board of Trustees remanded Recommended Draft Policy ARIN-2017-12: Require New POC Validation Upon Reassignment to the Advisory Council, noting:
>>
>> "The ARIN Board of Trustees remands ARIN Recommended Draft Policy 2017-12: Require New POC Validation Upon Reassignment to the ARIN Advisory Council. Noting the complexity of the policy, the Board wants a more complete policy assessment of technical soundness, and recommends interviews by the Advisory Council with ISPs who make numerous delegation requests including those with IP management platforms, if such interviews have not been already conducted."
>>
>> The Advisory Council is considering the remand of the Recommended Draft Policy and appropriate next steps.
>>
>> Board of Trustees Meeting Minutes are available at:
>> https://www.arin.net/about_us/bot/index.html
>>
>> Draft Policy and Policy Proposal texts are available at:
>> https://www.arin.net/policy/proposals/index.html
>>
>> The ARIN Policy Development Process (PDP) can be found at:
>> https://www.arin.net/policy/pdp.html
>>
>> Note also that the ARIN Board of Trustees reviewed the AC recommendation as well as a Staff Implementation Assessment memo when considering disposition of Recommended Draft Policy ARIN-2017-12.   A copy of that Staff Implementation Assessment memo is attached as background.
>>
>> /John
>>
>> John Curran
>> President and CEO
>> ARIN
>>
>>
>>
>>
>> _______________________________________________
>> 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.
>>
>
>
> --
> ===============================================
> David Farmer               Email:farmer at umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>


-- 
===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20181102/edf3ffed/attachment.htm>