<div dir="ltr"><div dir="ltr"><div>To expand on Andrew's response a little;</div><div><br></div><div>This would affect all detailed reassignments or reallocations, requiring the organization and POC records to pre-exist in the database. With a likely outcome, that fewer detailed reassignments and more simple reassignments will be made especially for /29 or shorter IPv4 reassignments.</div><div><br></div><div>This works closely with a companion policy, ARIN-2019-5: Disallow Third-party Organization Record Creation, to ensures only authorized representatives of an organization are allowed to initiate the creation of an organization record for the organization. Again with the likely outcome, that there will be fewer detailed reassignments and more simple reassignments ending up in the database. With the detailed reassignments or reallocations that are put in the database being authorized by the organization in question, and therefore are more likely to have valid and accurate POC records.</div><div><br></div><div>The current system where ISPs create organizations with new POC records seeming every time they make a reassignment has lead to significant duplicative, inaccurate, and irrelevant records being put into the database. This increases the volume of information in the database but seems to significantly decrease the overall accuracy of the information in the database.</div><div><br></div><div>So, yes this is expected to result in more simple reassignments of /29 or smaller for IPv4 and fewer detailed reassignments for such, but with more accuracy for the detailed reassignments that are made.</div><div><br></div><div>Hope that helps.</div></div></div><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 24, 2019 at 1:13 PM Andrew Dul <<a href="mailto:andrew.dul@quark.net" target="_blank">andrew.dul@quark.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-cite-prefix">You are correct, this policy change
only affects detailed-reassignments and reallocations.
Simple-reassignments do not have POC records associated with them.</div>
<div class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-cite-prefix"><br>
</div>
<div class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-cite-prefix">Andrew<br>
</div>
<div class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-cite-prefix"><br>
</div>
<div class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-cite-prefix">On 4/24/2019 10:18 AM, Andrew Bagrin
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'm sorry if I missed this somewhere, but this does
not affect simple reassignment of /29 or smaller, correct?
<div><br>
</div>
<div>Thanks,</div>
<div>Andrew</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Apr 22, 2019 at 10:58
PM Owen DeLong <<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>Support…
Implementation ASAP, please.
<div><br>
</div>
<div>Owen</div>
<div><br>
<div><br>
<blockquote type="cite">
<div>On Apr 22, 2019, at 07:27 , David Farmer <<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>>
wrote:</div>
<br class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973gmail-m_-3300514509990807420Apple-interchange-newline">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>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. </div>
<div><br>
</div>
<div>ARIN 43 transcript;</div>
<div><a href="https://www.arin.net/vault/participate/meetings/reports/ARIN_43/ppm1_transcript.html#anchor_9" target="_blank">https://www.arin.net/vault/participate/meetings/reports/ARIN_43/ppm1_transcript.html#anchor_9</a><br>
</div>
<div><br>
</div>
<div>ARIN 43 Video for presentation;</div>
<div><a href="https://www.youtube.com/watch?v=KxfZ128IqMU" target="_blank">https://www.youtube.com/watch?v=KxfZ128IqMU</a><br>
</div>
<div><br>
</div>
<div>ARIN 43 Presentation Slide deck;</div>
<div><a href="https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/2017_12_intro.pdf" target="_blank">https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/2017_12_intro.pdf</a><br>
</div>
<div><a href="https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/2017_12.pdf" target="_blank">https://www.arin.net/vault/participate/meetings/reports/ARIN_43/PDF/PPM/2017_12.pdf</a></div>
<div><br>
</div>
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.
<div><br>
</div>
<div>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?
<div><br>
</div>
<div>All comments are appreciated.</div>
<div><br>
</div>
<div>Thank you.</div>
<div><br>
</div>
<div>David Farmer</div>
<div>
<div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Apr 15,
2019 at 1:04 PM ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The ARIN
Advisory Council (AC) met on 10 April 2019 and
decided to send <br>
the following Recommended Draft Policy to Last
Call:<br>
<br>
ARIN-2017-12: POC Notification and Validation
Upon Reassignment or <br>
Reallocation<br>
<br>
Feedback is encouraged during the Last Call
period. All comments should <br>
be provided to the Public Policy Mailing List.
Last Call will expire on <br>
29 April 2019.<br>
<br>
The Recommended Draft Policy text is below and
available at:<br>
<a href="https://www.arin.net/participate/policy/drafts/" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/</a><br>
<br>
The ARIN Policy Development Process is available
at:<br>
<a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br>
<br>
Regards,<br>
<br>
Sean Hopkins<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
Recommended Draft Policy ARIN-2017-12: POC
Notification and Validation <br>
Upon Reassignment or Reallocation<br>
<br>
AC Assessment of Conformance with the Principles
of Internet Number <br>
Resource Policy:<br>
<br>
This recommended draft policy: (1) enables fair
and impartial number <br>
administration as it ensures that ARIN has the
means to communicate with <br>
organizations receiving reallocations or
detailed reassignments, and <br>
does so in a clear, complete, concise and
unambiguous manner; (2) is <br>
technically sound in that it supports ARIN’s
ability to maintain the <br>
unique registration of Internet number
resources; and (3) has community <br>
support.<br>
<br>
Problem Statement:<br>
<br>
Some ISPs assign individuals to be POCs for
reassigned blocks without <br>
consultation of the individual they are
inserting into Whois. For <br>
example, during the reassignment/reallocation
process, some large ISPs <br>
automatically create POCs from their customer’s
order form. This process <br>
is automated for many ISPs and therefore the
resulting POCs are not <br>
validated prior to being created in the ARIN
Whois database. This <br>
creates unknowing POCs that have no idea what
Whois is or even who ARIN <br>
is at the time they receive the annual POC
validation email. It can also <br>
create multiple POCs per email address causing
that same person to <br>
receive a multitude of POC Validation emails
each year.<br>
<br>
This policy proposal seeks to prevent the
situation where a POC is <br>
unwittingly and unintentionally inserted into
Whois. Doing so will <br>
reduce the significant amount of time that ARIN
staff spend fielding <br>
phone calls from POCs who have no idea they are
in Whois.<br>
<br>
The proposal will improve the overall POC
validation situation, by <br>
ensuring that all reallocation or detailed
reassignment requests are <br>
related to a pre-existing receiving organization
with at least one valid <br>
POC object, and by requesting that any other
existing invalid POC <br>
objects are validated.<br>
<br>
Policy statement:<br>
<br>
Insert one new section into NRPM 3:<br>
<br>
3.7 POC Notification and Validation Upon
Reassignment or Reallocation<br>
<br>
When a request for reallocation or detailed
reassignment is made to <br>
ARIN, the receiving organization must already be
in the ARIN database <br>
and associated with at least one validated POC
object. If there are no <br>
validated POC objects associated with the
receiving organization, ARIN <br>
shall reject the request.<br>
<br>
In addition to notifying the requester, ARIN
will also notify, via <br>
email, all POCs associated with the receiving
organization, whether the <br>
request was successful or not, and will request
validation of any <br>
invalid POC objects associated with the
receiving organization.<br>
<br>
Note: Simple reassignments are made without any
linkage to an <br>
organization or POC objects in the ARIN
database.<br>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are
subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list
subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a>
if you experience any issues.<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973gmail-m_-3300514509990807420gmail-m_-4883910476087198405gmail-m_6721131481148440875gmail_signature">===============================================<br>
David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>
Networking & Telecommunication Services<br>
Office of Information Technology<br>
University of Minnesota <br>
2218 University Ave SE Phone: 612-626-0815<br>
Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>
=============================================== </div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are
subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription
at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a>
if you experience any issues.<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience
any issues.<br>
</blockquote>
</div>
<br>
<fieldset class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-quote-pre">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail-m_901531738142673973moz-txt-link-abbreviated" href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
<p><br>
</p>
</div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_7077425750134896488gmail-m_3548917401511598811gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div></div>