<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small">On Wed, Jan 29, 2020 at 11:34 AM Andrew Dul <<a href="mailto:andrew.dul@quark.net">andrew.dul@quark.net</a>> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>I would say as a continuing ARIN member
they are responsible for keeping up their POC and abuse records
just like any other member.</div>
<div><br>
</div>
<div>Andrew<br></div></div></blockquote><div><br></div><div><div class="gmail_default">Point being, if those address blocks are ignored long enough, they could be reclaimed eventually by ARIN for repurposing?</div></div><div class="gmail_default" style="font-size:small">--</div><div class="gmail_default" style="font-size:small">Brian</div><div class="gmail_default" style="font-size:small"><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><div>
</div>
<div><br>
</div>
<div>On 1/28/2020 11:52 AM, Brian Jones
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-size:small"><br>
</div>
<div style="font-size:small">Question:
Does this mean that the entity responsible for the continued
resource holdings is subject to keeping up the POC and abuse
contact information for each of the locations or allocation
blocks where it continues to use ARIN resources? </div>
<div style="font-size:small"><br>
</div>
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>—<br>
Brian Jones</div>
<div>
<div style="font-size:small">NI&S
Virginia Tech</div>
</div>
<div><a href="mailto:bjones@vt.edu" target="_blank">bjones@vt.edu</a></div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jan 28, 2020 at 7:23
AM 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
following has been revised:<br>
<br>
* Draft Policy ARIN-2019-12: M&A Legal Jurisdiction
Exclusion<br>
<br>
Revised text is below and can be found at:<br>
<br>
<a href="https://www.arin.net/participate/policy/drafts/2019_12/" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_12/</a><br>
<br>
You are encouraged to discuss all Draft Policies on PPML. The
AC will <br>
evaluate the discussion in order to assess the conformance of
this Draft <br>
Policy with ARIN's Principles of Internet number resource
policy as <br>
stated in the Policy Development Process (PDP). Specifically,
these <br>
principles are:<br>
<br>
* Enabling Fair and Impartial Number Resource Administration<br>
* Technically Sound<br>
* Supported by the Community<br>
<br>
The PDP can be found 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>
Draft Policies and Proposals under discussion can be found 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>
Regards,<br>
<br>
Sean Hopkins<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
Draft Policy ARIN-2019-12: M&A Legal Jurisdiction
Exclusion<br>
<br>
Problem Statement:<br>
<br>
Merger and acquisition activity sometimes results in a
surviving legal <br>
entity that is not in ARIN service region, but may prefer to
continue <br>
the pre-existing relationship with ARIN.<br>
<br>
Example: Imagine a case where a global company has decided to
<br>
discontinue service in the ARIN service region (shuttering
ARIN region <br>
offices laying off ARIN region employees, and canceling ARIN
region <br>
customers) and repurpose the network resources and number
resources in <br>
the rest of its global footprint. During restructuring the
company <br>
concentrates its holdings in its European subsidiary, and then
dissolved <br>
its US legal entity.<br>
<br>
Imagine a case where a global company has decided to divest
its service <br>
in the ARIN region (selling all ARIN region offices, all ARIN
region <br>
network assets, all ARIN service region customers, all number
resources <br>
used in the ARIN (associated with previous noted sale of
network and <br>
customers), but retaining ARIN issued resources in use outside
of the <br>
ARIN service region. During restructuring the company
concentrates its <br>
holdings which are not in us in the ARIN service region in its
European <br>
subsidiary, and then sells off its US legal entity (including
the <br>
network, customers, addresses in use, etc) dissolved its US
legal entity.<br>
<br>
Policy Statement:<br>
<br>
Add the following to section 8.2<br>
<br>
Mergers, acquisitions, and reorganization activity resulting
in the <br>
surviving entity ceasing to have a real and substantial
connection with <br>
the ARIN region shall be permitted to continue holding any
numbering <br>
resources issued (directly or indirectly) by ARIN prior to the
merger, <br>
acquisition or reorganization activity, but shall not qualify
for any <br>
additional numbering resources (directly or indirectly) from
ARIN, <br>
unless and until it once again has a real and substantial
connection <br>
with the ARIN region as required by the Numbering Resource
Policy Manual.<br>
<br>
Timetable for Implementation: Immediate<br>
<br>
Anything Else:<br>
<br>
This proposal may be overtaken by a more general approach to
ARIN <br>
membership legal jurisdiction exclusion<br>
<br>
To clarify scope, a legal entity present within the ARIN
service region, <br>
and a current ARIN RSA executed with that entity, is necessary
to <br>
receive allocations or assignments from ARIN. Therefore in the
scenario <br>
postulated in the problem statement, the organization would
have to <br>
re-establish itself within the ARIN service region to receive
additional <br>
resources from ARIN, while it can continue to hold the
allocations or <br>
assignments made prior to any merger, acquisition, or
reorganization <br>
activity.<br>
<br>
<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>
<fieldset></fieldset>
<pre>_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a 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></div>