<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Well said !<br>
</p>
<div class="moz-cite-prefix">On 18/06/2019 13:53,
<a class="moz-txt-link-abbreviated" href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:Pine.LNX.4.64.1906181244380.21091@bigone">The main
problem I see is that this policy for the first time will open the
door up to IPv6 transfers. I do not agree with IPv6 transfers.
<br>
</blockquote>
Me either<br>
<blockquote type="cite"
cite="mid:Pine.LNX.4.64.1906181244380.21091@bigone">
<br>
Up to this point, the primary reason why we allow transfers of
IPv4 and 16 bit ASN numbers is the shortage of these resources.
<br>
<br>
In the case of IPv6 addresses, there is no shortage, therefore I
do not think we need to be going down that road.
<br>
</blockquote>
Exactly.<br>
<blockquote type="cite"
cite="mid:Pine.LNX.4.64.1906181244380.21091@bigone">
<br>
If the policy was limited to IPv4 and 16 bit ASN's, I would not
have a problem if indeed the business has moved to another
region. However, I do not want to see this policy being used for
forum shopping. I do not want to see the "I do not like the
policies of RIR A, so I am taking my ball (and my numbers) to RIR
B"<br>
</blockquote>
<p>That seems to be the environment some people seems to be trying
to turn things into. Kind of "It is like this now", "The market
demands", "People ask for it", while in true is is only in the
interest of a small part of them.</p>
<p>But the argument of people not liking the policies of RIR A
willing to move to RIR B is the strongest one in my view. Should
never be like this in this ecosystem.<br>
</p>
<blockquote type="cite"
cite="mid:Pine.LNX.4.64.1906181244380.21091@bigone">
<br>
Albert Erdmann
<br>
Network Administrator
<br>
Paradise On Line Inc.
<br>
<br>
<br>
On Tue, 18 Jun 2019, Chris Woodfield wrote:
<br>
<br>
<blockquote type="cite">Hello PPML,
<br>
<br>
The Advisory Council is seeking statements of support or
opposition to the below draft policy, which so far have not been
seen on PPML. I’d advise the community to consider the following
questions:
<br>
<br>
1. Is the problem statement a valid and/or likely occurrence
that would require a change of policy to address?
<br>
2. Is the proposed text to address the problem statement a valid
means to do so? Are there other approaches the community would
like the AC to consider?
<br>
3. Is there any potential deleterious impact should this
language be adopted into the NRPM?
<br>
<br>
We look forward to hearing the community’s response.
<br>
<br>
Thank you,
<br>
<br>
-Chris Woodfield
<br>
ARIN Advisory Council
<br>
<br>
<blockquote type="cite">On May 21, 2019, at 11:01 AM, ARIN
<a class="moz-txt-link-rfc2396E" href="mailto:info@arin.net"><info@arin.net></a> wrote:
<br>
<br>
On 16 May 2019, the ARIN Advisory Council (AC) accepted
"ARIN-prop-270: Inter-RIR M&A" as a Draft Policy.
<br>
<br>
Draft Policy ARIN-2019-10 is below and can be found at:
<br>
<a class="moz-txt-link-freetext" href="https://www.arin.net/participate/policy/drafts/2019_10/">https://www.arin.net/participate/policy/drafts/2019_10/</a>
<br>
<br>
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:
<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 class="moz-txt-link-freetext" href="https://www.arin.net/participate/policy/pdp/">https://www.arin.net/participate/policy/pdp/</a>
<br>
<br>
Draft Policies and Proposals under discussion can be found at:
<br>
<a class="moz-txt-link-freetext" href="https://www.arin.net/participate/policy/drafts/">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-10: Inter-RIR M&A
<br>
<br>
Problem Statement:
<br>
<br>
Merger, acquisition, or reorganization activity sometimes
results in a restructuring where company resources, the
management of number resources, or the use of number resources
are concentrated outside the ARIN service region. In this case
it may be desirable for the current legal entity or a legal
entity that is a parent, child or sister to move the servicing
of the number resources to a different RIR.
<br>
<br>
Example:
<br>
<br>
Imagine a case where a global company has decided to
discontinue service in the ARIN service region (shuttering
ARIN region offices laying off ARIN region employees, and
canceling ARIN region customers) and repurpose the network
resources and number resources in the rest of its global
footprint.
<br>
<br>
Imagine a case where a global company has decided to divest
its service in the ARIN region (selling all ARIN region
offices, all ARIN region network assets, all ARIN service
region customers, all number resources used in the ARIN
(associated with previous noted sale of network and
customers), but retaining ARIN issued resources in use outside
of the ARIN service region.
<br>
<br>
Policy Statement:
<br>
<br>
Add to section 8.2:
<br>
<br>
When merger, acquisition, or reorganization activity results
in surviving legal entity that is incorporated outside the
ARIN service region, or focused outside the ARIN service
region, or is merging with an organization that already has a
relationship with another RIR, then resources may be moved to
another RIR in accordance with the receiving RIR’s policies.
<br>
<br>
Comments:
<br>
<br>
Timetable for implementation: Immediate
<br>
_______________________________________________
<br>
ARIN-PPML
<br>
You are receiving this message because you are subscribed to
<br>
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
<br>
Unsubscribe or manage your mailing list subscription at:
<br>
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
<br>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
<br>
</blockquote>
<br>
_______________________________________________
<br>
ARIN-PPML
<br>
You are receiving this message because you are subscribed to
<br>
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
<br>
Unsubscribe or manage your mailing list subscription at:
<br>
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
<br>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
<br>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</body>
</html>