<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>To those who oppose because they find the mechanism in the
proposal is not effective do you have an alternative and more
effective text to propose so the author may consider a change. I
guess if you the current is ineffective the alternative would have
to be more complex but still objective. <br>
</p>
<p>The point I believe is not about creating hurdles for IPv4 but a
natural and quiet obvious move to what IS the current Internet
protocol and what must work in order for Internet to survive.
Otherwise why would ARIN's Board issue such resolution in that
sense ? And there are plenty of other Internet related
organizations in the same direction.</p>
<p>There will be conflicts in either cases, if things a left loose
are they are at the people's pleasure there will be as mentioned,
growing conflicts regarding IPv4 exhaustion and they tend to grow
quiet fastly. If things push for transition to IPv6 (in this case
much more softly) there will be conflicts with those who believe
they have the right to hold themselves and all others to the past.<br>
</p>
<p>Even more important is that due to these ones willing to wash
their hands and deny evolution making *all others will be paying
the price* due not only the problems caused by the lack of IPv4
but also to the price increasing they will have to pay should they
to need to purchase any extra chunk of addresses to be able to
exist in the internet while there is a feasible solution
available.<br>
That's why it is very reasonable and fair that this same impacted
community desire to have more mechanisms to that direction and is
completely legit they come out from a change in the policy<br>
</p>
<p>Between both types of conflicts my bet is that the second which
means evolution will prevail.</p>
<p>Best regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 06/11/2019 18:08, David Farmer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAN-Dau3dc7CK47mj8NXDBEo14fuMJkgWS8bLq0+8w1mhbsPbdQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">I oppose this policy.
<div><br>
</div>
<div>I'm not convinced of the efficacy of this policy, the
policy's ability to produce its intended or desired result. I
presume the intended result is to increase the deployment of
IPv6. I'm not convinced that creating artificial hurdles for
IPv4 will increase the deployment of IPv6 in any way. If the
natural hurdle of having to go to the market to get IPv4 isn't
enough to convince people to deploy IPv6, why would this
artificial hurdle convince them? Given human nature, if this
policy goes forward, I expect many people will turn on IPv6 to
complete their IPv4 transfer and then simply turn IPv6 off
again, the end result does nothing for IPv6 deployment.
Further, I suspect this policy is more likely to antagonize
people against deploying IPv6 more than it is will incentivize
them toward deploying IPv6.</div>
<div><br>
</div>
<div>Please let's not go in this direction.</div>
<div><br>
</div>
<div>Thanks.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Nov 6, 2019 at 11:55
AM ARIN <<a href="mailto:info@arin.net"
moz-do-not-send="true">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">On
1 November 2019, the ARIN Advisory Council (AC) accepted <br>
"ARIN-prop-278: Require IPv6 Before Receiving Section 8 IPv4
Transfers" <br>
as a Draft Policy.<br>
<br>
Draft Policy ARIN-2019-19 is below and can be found at:<br>
<br>
<a
href="https://www.arin.net/participate/policy/drafts/2019_19/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.arin.net/participate/policy/drafts/2019_19/</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" moz-do-not-send="true">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" moz-do-not-send="true">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-19: Require IPv6 Before Receiving
Section 8 IPv4 <br>
Transfers<br>
<br>
Problem Statement:<br>
<br>
On 7 May 2007 the ARIN Board unanimously passed an IPv6
resolution. In <br>
2011, the last /8 blocks were assigned to the RIR’s and has
now been <br>
over 4 years since the IPv4 free pool was exhausted at ARIN.<br>
<br>
Now is the time for ARIN to require those who receive
transferred IPv4 <br>
space to have in place an operational IPv6 network.<br>
<br>
Policy statement:<br>
<br>
In section 8.5.2, add the following language to the end of the
paragraph <br>
entitled “Operational Use”:<br>
<br>
Such operational network must at minimum include an allocation
or <br>
assignment by ARIN of IPv6 address space under the same Org ID
receiving <br>
the transferred IPv4 space. Such Org must be able to prove
this IPv6 <br>
space is being routed by using it to communicate with ARIN.<br>
<br>
In the event the receiver provides a written statement from
its upstream <br>
that IPv6 connectivity is unavailable, the IPv6 requirement
may be waived.<br>
<br>
Timetable for Implementation: Upon Passage<br>
<br>
Anything Else:<br>
<br>
The following was included in the IPv6 resolution:<br>
<br>
BE IT RESOLVED, that this Board of Trustees hereby requests
the ARIN <br>
Advisory Council to consider Internet Numbering Resource
Policy changes <br>
advisable to encourage migration to IPv6 numbering resources
where possible.<br>
<br>
This proposal is part of an effort to encourage migration to
IPv6.<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"
moz-do-not-send="true">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" moz-do-not-send="true">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank"
moz-do-not-send="true">info@arin.net</a> if you experience
any issues.<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">===============================================<br>
David Farmer <a
href="mailto:Email%3Afarmer@umn.edu" target="_blank"
moz-do-not-send="true">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>
<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>