<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Support</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 4/16/2020 10:32 AM, Brian Jones
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANyqO+Foq9RS1_6GnC7F599HpTEDXs1VLdNkLVtnGkbB+NL+zA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default" style="font-size:small">Looking at
the numbers John posted concerning this issue, it tends to <i>look
like</i> some of these 3x small folks decided to drop their
request once they encountered the price increase. If this is
the case then we should move forward with this proposal. We do
not want to create a situation where folks are continuing to
use only IPv4 because of costs. <br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small">I support
this proposal.</div>
<div class="gmail_default" style="font-size:small"><br
clear="all">
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>—<br>
Brian <br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 16, 2020 at 7:19
AM <<a href="mailto:hostmaster@uneedus.com"
moz-do-not-send="true">hostmaster@uneedus.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">Is
that very much because they found out if they accepted the
IPv6 space, <br>
their fees would double???<br>
<br>
If so, this PROVES the need to adopt this plan. We should not
have things <br>
in place that prevent IPv6 adoption. We have already decided
that IPv6 <br>
should be cost neutral. Lets fix this glitch and let these 3x
small <br>
people have IPv6 without doubling their cost.<br>
<br>
Albert Erdmann<br>
Network Administrator<br>
Paradise On Line Inc.<br>
<br>
On Thu, 16 Apr 2020, John Sweeting wrote:<br>
<br>
> Yes that is exactly what it means. After approval they
decided for whatever reason they no longer wanted the
resource.<br>
><br>
> Sent from my iPhone<br>
><br>
>> On Apr 16, 2020, at 1:56 AM, John Santos <<a
href="mailto:john@egh.com" target="_blank"
moz-do-not-send="true">john@egh.com</a>> wrote:<br>
>><br>
>> What does "closed with no action" mean? Does it
mean the RSP abandoned the request?<br>
>><br>
>><br>
>>> On 4/15/2020 7:18 PM, John Sweeting wrote:<br>
>>> Hi Andrew,<br>
>>><br>
>>> The numbers around this are:<br>
>>><br>
>>> 320 3x small RSPs<br>
>>> 30 have applied and been approved for IPv6 of
which 26 closed with no action to complete by the requester.
The other 4 are currently still open and pending action.<br>
>>><br>
>>> Thanks,<br>
>>> John S.<br>
>>><br>
>>> On 4/15/20, 11:30 AM, "Andrew Dul" <<a
href="mailto:andrew.dul@quark.net" target="_blank"
moz-do-not-send="true">andrew.dul@quark.net</a>> wrote:<br>
>>><br>
>>> John,<br>
>>> Could you provide the community with a
rough magnitude of this issue?<br>
>>> Approximately how many of these 3x-small
ISP organizations have come to<br>
>>> ARIN and requested IPv6? How many accepted
the block and how many<br>
>>> refused because of the fee issue? How many
3x-small ISP organizations<br>
>>> does ARIN currently serve.<br>
>>> Thanks,<br>
>>> Andrew<br>
>>> On 4/14/2020 2:29 PM, John Sweeting
wrote:<br>
>>> > All,<br>
>>> ><br>
>>> > For anyone interested in the content of
the "Policy Experience Report presented by Registration<br>
>>> > Services to the AC at its annual workshop
in January 2020" referenced in the problem statement you can
see that report here:<br>
>>> ><br>
>>> > <a
href="https://www.arin.net/about/welcome/ac/meetings/2020_0124/policy_experience_report.pdf"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.arin.net/about/welcome/ac/meetings/2020_0124/policy_experience_report.pdf</a><br>
>>> ><br>
>>> > Thank you.<br>
>>> ><br>
>>> > On 3/24/20, 1:22 PM, "ARIN-PPML on behalf
of ARIN" <<a href="mailto:arin-ppml-bounces@arin.net"
target="_blank" moz-do-not-send="true">arin-ppml-bounces@arin.net</a>
on behalf of <a href="mailto:info@arin.net" target="_blank"
moz-do-not-send="true">info@arin.net</a>> wrote:<br>
>>> ><br>
>>> > On 19 March 2020, the ARIN Advisory
Council (AC) accepted<br>
>>> > "ARIN-prop-285: IPv6
Nano-allocations" as a Draft Policy.<br>
>>> ><br>
>>> > Draft Policy ARIN-2020-3 is below and
can be found at:<br>
>>> ><br>
>>> > <a
href="https://www.arin.net/participate/policy/drafts/2020_3/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.arin.net/participate/policy/drafts/2020_3/</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-2020-3: IPv6
Nano-allocations<br>
>>> ><br>
>>> > Problem Statement:<br>
>>> ><br>
>>> > ARIN's fee structure provides a
graduated system wherein organizations<br>
>>> > pay based on the amount of number
resources they consume.<br>
>>> ><br>
>>> > In the case of the very smallest
ISPs, if a 3X-Small ISP (with a /24 or<br>
>>> > smaller of IPv4) gets the present
minimal-sized IPv6 allocation (a /36),<br>
>>> > its annual fees will double from $250
to $500/year.<br>
>>> ><br>
>>> > According to a Policy Experience
Report presented by Registration<br>
>>> > Services to the AC at its annual
workshop in January 2020, this<br>
>>> > represents a disincentive to IPv6
adoption with a substantial fraction<br>
>>> > of so-situated ISPs saying "no
thanks" and abandoning their request for<br>
>>> > IPv6 number resources when informed
of the impact on their annual fees.<br>
>>> ><br>
>>> > This can be addressed by rewriting
subsection 6.5.2(b). Initial<br>
>>> > Allocation Size to allow allocation
of a /40 to only the smallest ISPs<br>
>>> > upon request, and adding a new clause
6.5.2(g) to cause an automatic<br>
>>> > upgrade to at least a /36 in the case
where the ISP is no longer 3X-Small.<br>
>>> ><br>
>>> > Reserving /40s only for organizations
initially expanding into IPv6 from<br>
>>> > an initial sliver of IPv4 space will
help to narrowly address the<br>
>>> > problem observed by Registration
Services while avoiding unintended<br>
>>> > consequences by accidentally giving a
discount for undersized allocations.<br>
>>> ><br>
>>> > Policy Statement:<br>
>>> ><br>
>>> > Replace the current 6.5.2(b) with the
following:<br>
>>> ><br>
>>> > b. In no case shall an LIR receive
smaller than a /32 unless they<br>
>>> > specifically request a /36 or /40.<br>
>>> ><br>
>>> > In order to be eligible for a /40, an
ISP must meet the following<br>
>>> > requirements:<br>
>>> > * Hold IPv4 direct allocations
totaling a /24 or less (to include zero)<br>
>>> > * Hold IPv4
reassignments/reallocations totaling a /22 or less (to<br>
>>> > include zero)<br>
>>> ><br>
>>> > In no case shall an ISP receive more
than a /16 initial allocation.<br>
>>> ><br>
>>> > Add 6.5.2(g) as follows:<br>
>>> ><br>
>>> > g. An LIR that requests a smaller /36
or /40 allocation is entitled to<br>
>>> > expand the allocation to any nibble
aligned size up to /32 at any time<br>
>>> > without renumbering or additional
justification. /40 allocations shall<br>
>>> > be automatically upgraded to /36 if
at any time said LIR's IPv4 direct<br>
>>> > allocations exceed a /24. Expansions
up to and including a /32 are not<br>
>>> > considered subsequent allocations,
however any expansions beyond /32 are<br>
>>> > considered subsequent allocations and
must conform to section 6.5.3.<br>
>>> > Downgrades of any IPv6 allocation to
less than a /36 are not permitted<br>
>>> > regardless of the ISP's current or
former IPv4 number resource holdings.<br>
>>> ><br>
>>> > Comments:<br>
>>> ><br>
>>> > The intent of this policy proposal is
to make IPv6 adoption at the very<br>
>>> > bottom end expense-neutral for the
ISP and revenue-neutral for ARIN. The<br>
>>> > author looks forward to a future era
wherein IPv6 is the dominant<br>
>>> > technology and IPv4 is well in
decline and considered optional leading<br>
>>> > the Community to conclude that
sunsetting this policy is prudent in the<br>
>>> > interests of avoiding an incentive to
request undersized IPv6 allocations.<br>
>>> ><br>
>>> > Timetable for implementation:
Immediate<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"
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>
>>> ><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"
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>
>>><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>
>><br>
>> --<br>
>> John Santos<br>
>> Evans Griffiths & Hart, Inc.<br>
>> 781-861-0670 ext 539<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"
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>
> _______________________________________________<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>
>_______________________________________________<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>
<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>
<pre class="moz-signature" cols="80">--
John Santos
Evans Griffiths & Hart, Inc.
781-861-0670 ext 539
</pre>
</body>
</html>