[arin-ppml] LAST CALL - Recommended Draft Policy ARIN-2017-12: POC Notification and Validation Upon Reassignment or Reallocation
Andrew Dul
andrew.dul at quark.net
Wed Apr 24 13:59:03 EDT 2019
You are correct, this policy change only affects detailed-reassignments
and reallocations. Simple-reassignments do not have POC records
associated with them.
Andrew
On 4/24/2019 10:18 AM, Andrew Bagrin wrote:
> I'm sorry if I missed this somewhere, but this does not affect simple
> reassignment of /29 or smaller, correct?
>
> Thanks,
> Andrew
>
> On Mon, Apr 22, 2019 at 10:58 PM Owen DeLong <owen at delong.com
> <mailto:owen at delong.com>> wrote:
>
> Support… Implementation ASAP, please.
>
> Owen
>
>
>> On Apr 22, 2019, at 07:27 , David Farmer <farmer at umn.edu
>> <mailto:farmer at umn.edu>> wrote:
>>
>> There have been relatively few comments on this policy on PPML
>> since the text was revised in late January. Although, it seems to
>> have been well supported at the Barbados meeting.
>>
>> ARIN 43 transcript;
>> https://www.arin.net/vault/participate/meetings/reports/ARIN_43/ppm1_transcript.html#anchor_9
>>
>> ARIN 43 Video for presentation;
>> https://www.youtube.com/watch?v=KxfZ128IqMU
>>
>> ARIN 43 Presentation Slide deck;
>> https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/2017_12_intro.pdf
>> https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/2017_12.pdf
>>
>> It is therefore particularly important for anyone who objects to
>> this policy or thinks this policy will create issues for their
>> organization to speak up during this clast call period.
>>
>> Even if you support the policy, comments regarding the proper
>> timeline for implementation are of interest. How long will your
>> organization need to adapt to these changes?
>>
>> All comments are appreciated.
>>
>> Thank you.
>>
>> David Farmer
>>
>>
>> On Mon, Apr 15, 2019 at 1:04 PM ARIN <info at arin.net
>> <mailto:info at arin.net>> wrote:
>>
>> The ARIN Advisory Council (AC) met on 10 April 2019 and
>> decided to send
>> the following Recommended Draft Policy to Last Call:
>>
>> ARIN-2017-12: POC Notification and Validation Upon
>> Reassignment or
>> Reallocation
>>
>> Feedback is encouraged during the Last Call period. All
>> comments should
>> be provided to the Public Policy Mailing List. Last Call will
>> expire on
>> 29 April 2019.
>>
>> The Recommended Draft Policy text is below and available at:
>> https://www.arin.net/participate/policy/drafts/
>>
>> The ARIN Policy Development Process is available at:
>> https://www.arin.net/participate/policy/pdp/
>>
>> Regards,
>>
>> Sean Hopkins
>> Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>>
>>
>>
>> Recommended Draft Policy ARIN-2017-12: POC Notification and
>> Validation
>> Upon Reassignment or Reallocation
>>
>> AC Assessment of Conformance with the Principles of Internet
>> Number
>> Resource Policy:
>>
>> This recommended draft policy: (1) enables fair and impartial
>> number
>> administration as it ensures that ARIN has the means to
>> communicate with
>> organizations receiving reallocations or detailed
>> reassignments, and
>> does so in a clear, complete, concise and unambiguous manner;
>> (2) is
>> technically sound in that it supports ARIN’s ability to
>> maintain the
>> unique registration of Internet number resources; and (3) has
>> community
>> support.
>>
>> Problem Statement:
>>
>> Some ISPs assign individuals to be POCs for reassigned blocks
>> without
>> consultation of the individual they are inserting into Whois.
>> For
>> example, during the reassignment/reallocation process, some
>> large ISPs
>> automatically create POCs from their customer’s order form.
>> This process
>> is automated for many ISPs and therefore the resulting POCs
>> are not
>> validated prior to being created in the ARIN Whois database.
>> This
>> creates unknowing POCs that have no idea what Whois is or
>> even who ARIN
>> is at the time they receive the annual POC validation email.
>> It can also
>> create multiple POCs per email address causing that same
>> person to
>> receive a multitude of POC Validation emails each year.
>>
>> This policy proposal seeks to prevent the situation where a
>> POC is
>> unwittingly and unintentionally inserted into Whois. Doing so
>> will
>> reduce the significant amount of time that ARIN staff spend
>> fielding
>> phone calls from POCs who have no idea they are in Whois.
>>
>> The proposal will improve the overall POC validation
>> situation, by
>> ensuring that all reallocation or detailed reassignment
>> requests are
>> related to a pre-existing receiving organization with at
>> least one valid
>> POC object, and by requesting that any other existing invalid
>> POC
>> objects are validated.
>>
>> Policy statement:
>>
>> Insert one new section into NRPM 3:
>>
>> 3.7 POC Notification and Validation Upon Reassignment or
>> Reallocation
>>
>> When a request for reallocation or detailed reassignment is
>> made to
>> ARIN, the receiving organization must already be in the ARIN
>> database
>> and associated with at least one validated POC object. If
>> there are no
>> validated POC objects associated with the receiving
>> organization, ARIN
>> shall reject the request.
>>
>> In addition to notifying the requester, ARIN will also
>> notify, via
>> email, all POCs associated with the receiving organization,
>> whether the
>> request was successful or not, and will request validation of
>> any
>> invalid POC objects associated with the receiving organization.
>>
>> Note: Simple reassignments are made without any linkage to an
>> organization or POC objects in the ARIN database.
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net
>> <mailto: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 <mailto:info at arin.net> if you
>> experience any issues.
>>
>>
>>
>> --
>> ===============================================
>> David Farmer Email:farmer at umn.edu
>> <mailto:Email%3Afarmer 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
>> ===============================================
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML at arin.net
>> <mailto: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 <mailto: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
> <mailto: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 <mailto: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/20190424/c1377994/attachment.htm>
More information about the ARIN-PPML
mailing list