<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=UTF-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 11.00.10570.1001">
<STYLE>@font-face {
font-family: Helvetica;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Verdana;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
LI.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
DIV.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
A:link {
TEXT-DECORATION: underline; COLOR: blue; mso-style-priority: 99
}
SPAN.MsoHyperlink {
TEXT-DECORATION: underline; COLOR: blue; mso-style-priority: 99
}
A:visited {
TEXT-DECORATION: underline; COLOR: purple; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
TEXT-DECORATION: underline; COLOR: purple; mso-style-priority: 99
}
P.msonormal0 {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; mso-style-name: msonormal; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
LI.msonormal0 {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; mso-style-name: msonormal; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
DIV.msonormal0 {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; mso-style-name: msonormal; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.apple-converted-space {
mso-style-name: apple-converted-space
}
SPAN.EmailStyle19 {
FONT-FAMILY: "Calibri",sans-serif; FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<META name=GENERATOR content="MSHTML 6.00.5730.13">
<STYLE>BLOCKQUOTE {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
UL {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
</STYLE>
</HEAD>
<BODY>
<P>Agreed with Owen, first we kill waiting list where people were waiting for
last 2 years and not going to open market because they went through a long
approval process and got into the waiting list, all those waiting list entries
would have bought the IP's from open Market at less than half the price if this
was known then, </P>
<P>And now we are stocked up for next 5 years.</P>
<P>
<P>Regards<BR>Hayee </P>
<P>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="100%">
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; PADDING-RIGHT: 0px; MARGIN-RIGHT: 0px">
<DIV class=WordSection1>
<P class=MsoNormal>Hi Owen,<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>It’s hard to predict when the useful IPv4 lifetime
will end, so it’s hard to say whether runout of these reserved pools is
unlikely, especially if conditions change.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>If you feel 4.4 and 4.10 are severely
overstocked, maybe a proposal to release those “sequestered” addresses
should be forthcoming, as maintaining those pools at those levels is
counter to our mission?<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Do you have any comments on the problem statement,
and the idea that the haphazard and unpredictable influx of addresses
into the waiting list is problematic? For example, doesn’t the current
constitution of the waiting list encourage virtually all ARIN members to
enter the lottery for a /22? The size is small, the justification
options pretty generous, the downside minimal.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>In my mind the waiting list is a fraud magnet and has
outlived its usefulness, and yes, this is an attempt to eliminate
it without going down the auction route. The addresses haven’t
been destroyed, just taken off the market, adding the tiniest bit to the
existing pools, whose size was approved by the community.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I support the policy as written and
amended.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Regards,<o:p></o:p></P>
<P class=MsoNormal>Mike<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<DIV
style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B>From:</B> ARIN-PPML
<arin-ppml-bounces@arin.net> <B>On Behalf Of </B>Owen
DeLong<BR><B>Sent:</B> Thursday, August 15, 2019 5:10 PM<BR><B>To:</B>
WOOD Alison * DAS <Alison.WOOD@oregon.gov><BR><B>Cc:</B> arin-ppml
<arin-ppml@arin.net><BR><B>Subject:</B> Re: [arin-ppml] Draft
Policy ARIN-2019-17: Returned Addresses to the 4.10 Reserved
Pool<o:p></o:p></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Really, it seems to me that this proposal is another
attempt at eliminating the waiting list for unmet
requests.<o:p></o:p></P>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>The first attempt (ARIN auctions the space) met with
resistance from ARIN’s legal team (for good reason), so now this
attempts to sequester the space where it will be hard to distribute
rather than allowing the waiting list to have any potential to compete
with the transfer market.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>The proposed targets (4.4 and 4.10 pools) are well
stocked and unlikely to run out in any useful IPv4
lifetime.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>As such, restocking them from returned space strikes
me as just a way to sequester this space where it cannot be
used.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>IMHO, this is counter to ARIN’s mission and should
not be allowed.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>I oppose the policy as written and as proposed to be
amended.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>Owen<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><BR><BR><o:p></o:p></P>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal>On Aug 15, 2019, at 13:55 , WOOD Alison * DAS via
ARIN-PPML <<A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A>>
wrote:<o:p></o:p></P></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>Thank
you for the continued input on this draft policy proposal.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>I
will be updating the text of the draft policy to include both 4.4 and
4.10 pools. Point of information, the 4.4 pool currently has
approximately 391 /24’s and 4.10 has approximately 15,753 /24’s
available and are not estimated to run out in the next five
years.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>Please
keep your feedback coming, it is very helpful for the
council.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>-Alison</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<DIV
style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><B>From:</B><SPAN
class=apple-converted-space> </SPAN>ARIN-PPML [<A
href="mailto:arin-ppml-bounces@arin.net">mailto:arin-ppml-bounces@arin.net</A>]<SPAN
class=apple-converted-space> </SPAN><B>On Behalf Of<SPAN
class=apple-converted-space> </SPAN></B>Fernando
Frediani<BR><B>Sent:</B><SPAN
class=apple-converted-space> </SPAN>Tuesday, July 30, 2019 6:44
AM<BR><B>To:</B><SPAN
class=apple-converted-space> </SPAN>arin-ppml <<A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A>><BR><B>Subject:</B><SPAN
class=apple-converted-space> </SPAN>Re: [arin-ppml] Draft Policy
ARIN-2019-17: Returned Addresses to the 4.10 Reserved Pool<SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'> <o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal
style="BACKGROUND: white; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>The
point is that you treating IP marketing as something 'natural' or a
'default route' which it is not and can never be. Natural is to
receive some addresses from the RIR in first place so they are treated
as anyone else was in the past and have a chance to exist in the
Internet with same conditions as all others. From that if they need
extra space then fine to seek for alternative
ways.<o:p></o:p></SPAN></P>
<P class=MsoNormal
style="BACKGROUND: white; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>I don't
think a new entrants would automatically qualify for 4.10 in all cases
therefore any space left should be targeted also to them as well to
IPv6 transition and critical infrastructure. Otherwise the community
will be creating an artificial barrier to them in order to favor the
IP market while the RIR still has IPv4 space available for
them.<o:p></o:p></SPAN></P>
<P class=MsoNormal
style="BACKGROUND: white; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>Fernando<o:p></o:p></SPAN></P>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>On
30/07/2019 10:30, Tom Fantacone
wrote:<o:p></o:p></SPAN></P></DIV></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'>I would
think that the majority of new entrants would need at least some
allocation to help with IPv6 transition and would qualify for
addresses from the 4.10 pool. Depending on what they receive
from that pool and when, they may not qualify for additional waiting
list addresses and would have to go to the transfer market for
additional IPv4 space anyway. Those that don't qualify under
4.10 can still get smaller IPv4 blocks on the transfer market
readily, and the cost for blocks in the /24-/22 range is not
prohibitive. Certainly an organization seeking a small IPv4
block for multi-homing or other purposes is better off spending a
few thousand dollars to purchase a range than waiting a year on the
waiting list to put their plans in motion.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal
style="MARGIN-BOTTOM: 12pt; BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'><BR>Note
that while RIPE does not have a reserve pool specifically for IPv6
transition, the expectation of their final /8 policy was to allow
new entrants access to IPv4 to assist in this transition. In
reality, it didn't work out that way and most of the /22 allocations
to new LIRs from the final /8 were to existing organizations who
spun up new, related entities in order to increase their IPv4
holdings:<BR><A
href="https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations"
target=_blank><SPAN
style="COLOR: purple"><BR>https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations</SPAN></A><BR><BR>I'm
also sympathetic to new entrants, but don't see the current waiting
list as a great help to them vs. the 4.10 pool or the transfer
market, both of which allow you your allocation in a timely
fashion.<BR><BR>Best Regards,<BR><BR>Tom Fantacone</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV id=Zm-_Id_-Sgn1>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'>---- On
Mon, 29 Jul 2019 11:39:32 -0400<SPAN
class=apple-converted-space> </SPAN><B>Fernando Frediani <<A
href="mailto:fhfrediani@gmail.com" target=_blank><SPAN
style="COLOR: purple">fhfrediani@gmail.com</SPAN></A>></B><SPAN
class=apple-converted-space> </SPAN>wrote ----</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<BLOCKQUOTE
style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 5pt; BORDER-LEFT: #cccccc 1pt solid; MARGIN: 5pt 0in 5pt 3.75pt; PADDING-RIGHT: 0in">
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'>I find
it interesting the idea of privileging the pool dedicated to<SPAN
class=apple-converted-space> </SPAN><BR>facilitate IPv6
Deployment and I also agree with the comments below in<SPAN
class=apple-converted-space> </SPAN><BR>the sense that it's
not very beneficial do most ARIN members due to max<SPAN
class=apple-converted-space> </SPAN><BR>size, /22, cannot be
holding more than a /20.<BR><BR>However one point I couldn't
identify is where the new entrants stand in<SPAN
class=apple-converted-space> </SPAN><BR>this new possible
scenario ? Will they only be able to apply under the<SPAN
class=apple-converted-space> </SPAN><BR>4.10 reserved pool ?
If so for a access/broadband ISPs may be easier to<SPAN
class=apple-converted-space> </SPAN><BR>fit, but not
necessarily for other scenarios and types of ISPs.<SPAN
class=apple-converted-space> </SPAN><BR>Therefore if I didn't
miss anything these returned addresses should also<SPAN
class=apple-converted-space> </SPAN><BR>be able to go to new
entrants, not only to 4.10 reserved pool conditions.<BR><BR>Best
regards<BR>Fernando Frediani<BR><BR>On 25/07/2019 17:32, Tom
Fantacone wrote:<BR>> I found the wording of the Problem
Statement on this one a bit<SPAN
class=apple-converted-space> </SPAN><BR>> confusing.
However, after deciphering the effect of the actual policy<SPAN
class=apple-converted-space> </SPAN><BR>> change I support
it.<BR>><BR>> Essentially, all returned IPv4 space will no
longer go to the waiting<SPAN
class=apple-converted-space> </SPAN><BR>> list but will
supplement the 4.10 reserved pool used to enhance IPv6<SPAN
class=apple-converted-space> </SPAN><BR>>
deployment. This essentially kills off the waiting
list.<BR>><BR>> The recent restrictions placed on the
waiting list to reduce fraud<SPAN
class=apple-converted-space> </SPAN><BR>> have hobbled it
to the point where it's not very beneficial to most<SPAN
class=apple-converted-space> </SPAN><BR>> ARIN
members. (Max size, /22, cannot be holding more than a
/20). <SPAN class=apple-converted-space> </SPAN><BR>>
It's essentially only useful to new entrants, but those that go on
it<SPAN class=apple-converted-space> </SPAN><BR>> still
have to wait many months to receive their small allocation.
If<SPAN class=apple-converted-space> </SPAN><BR>> they
justify need now, but have to wait that long, how critical is<SPAN
class=apple-converted-space> </SPAN><BR>> their need if
they're willing to wait that long? Small blocks are not<SPAN
class=apple-converted-space> </SPAN><BR>> terribly
expensive and can be quickly gotten on the transfer
market. <SPAN
class=apple-converted-space> </SPAN><BR>> I can understand
waiting that long for a large block needed for a<SPAN
class=apple-converted-space> </SPAN><BR>> longer term
project due to prohibitive cost, but I don't see a great<SPAN
class=apple-converted-space> </SPAN><BR>> benefit to the
waiting list as it stands.<BR>><BR>> Also, if there's any
fraud left on the waiting list, this would kill
it.<BR>><BR>> I would hope, however, that if implemented,
those currently on the<SPAN
class=apple-converted-space> </SPAN><BR>> waiting list
would be grandfathered in. I do think some entities
with<SPAN class=apple-converted-space> </SPAN><BR>>
legitimate need got burned on the last change made to the waiting
list.<BR>><BR>> At 04:05 PM 7/23/2019, ARIN
wrote:<BR>>> On 18 July 2019, the ARIN Advisory Council (AC)
accepted<SPAN
class=apple-converted-space> </SPAN><BR>>>
"ARIN-prop-276: Returned Addresses to the 4.10 Reserved Pool" as
a<SPAN class=apple-converted-space> </SPAN><BR>>> Draft
Policy.<BR>>><BR>>> Draft Policy ARIN-2019-17 is below
and can be found at:<BR>>><BR>>><SPAN
class=apple-converted-space> </SPAN><A
href="https://www.arin.net/participate/policy/drafts/2019_17/"
target=_blank><SPAN
style="COLOR: purple">https://www.arin.net/participate/policy/drafts/2019_17/</SPAN></A><BR>>><BR>>>
You are encouraged to discuss all Draft Policies on PPML. The AC
will<SPAN class=apple-converted-space> </SPAN><BR>>>
evaluate the discussion in order to assess the conformance of
this<SPAN class=apple-converted-space> </SPAN><BR>>>
draft policy with ARIN's Principles of Internet number
resource<SPAN
class=apple-converted-space> </SPAN><BR>>> policy as
stated in the Policy Development Process (PDP).<SPAN
class=apple-converted-space> </SPAN><BR>>>
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>>><SPAN
class=apple-converted-space> </SPAN><A
href="https://www.arin.net/participate/policy/pdp/"
target=_blank><SPAN
style="COLOR: purple">https://www.arin.net/participate/policy/pdp/</SPAN></A><BR>>><BR>>>
Draft Policies and Proposals under discussion can be found
at:<BR>>><SPAN class=apple-converted-space> </SPAN><A
href="https://www.arin.net/participate/policy/drafts/"
target=_blank><SPAN
style="COLOR: purple">https://www.arin.net/participate/policy/drafts/</SPAN></A><BR>>><BR>>>
Regards,<BR>>><BR>>> Sean Hopkins<BR>>> Policy
Analyst<BR>>> American Registry for Internet Numbers
(ARIN)<BR>>><BR>>> Draft Policy ARIN-2019-17: Returned
Addresses to the 4.10 Reserved Pool<BR>>><BR>>>
Problem Statement:<BR>>><BR>>> An inconsistent and
unpredictable stream of address space is an<SPAN
class=apple-converted-space> </SPAN><BR>>> unsuitable
method of populating the waiting list (4.1.8.1) and<SPAN
class=apple-converted-space> </SPAN><BR>>> fulfilling
subsequent requests.<BR>>><BR>>> Policy
statement:<BR>>><BR>>> Change "4.10. Dedicated IPv4
Block to Facilitate IPv6 Deployment" to<SPAN
class=apple-converted-space> </SPAN><BR>>> "4.10
Dedicated IPv4 Pool to Facilitate IPv6
Deployment"<BR>>><BR>>> Change" When ARIN receives its
last /8 IPv4 allocation from IANA, a<SPAN
class=apple-converted-space> </SPAN><BR>>> contiguous
/10 IPv4 block will be set aside and dedicated to<SPAN
class=apple-converted-space> </SPAN><BR>>> facilitate
IPv6 deployment. Allocations and assignments from this<SPAN
class=apple-converted-space> </SPAN><BR>>> block " to
"In addition to the contiguous /10 IPv4 block set aside<SPAN
class=apple-converted-space> </SPAN><BR>>> and
dedicated to facilitate IPv6 deployment, all returns and<SPAN
class=apple-converted-space> </SPAN><BR>>> revocations
of IPv4 blocks will be added to the pool of space<SPAN
class=apple-converted-space> </SPAN><BR>>> dedicated to
the facilitation of IPv6 deployment. Allocations and<SPAN
class=apple-converted-space> </SPAN><BR>>> assignments
from this pool "<BR>>><BR>>> Change "This block will
be subject to a minimum size allocation of<SPAN
class=apple-converted-space> </SPAN><BR>>> /28 and a
maximum size allocation of /24. ARIN should use sparse<SPAN
class=apple-converted-space> </SPAN><BR>>> allocation
when possible within that /10 block." to "This pool will<SPAN
class=apple-converted-space> </SPAN><BR>>> be subject
to a minimum size allocation of /28 and a maximum sized<SPAN
class=apple-converted-space> </SPAN><BR>>> allocation
of /24. ARIN should use sparse allocation when possible<SPAN
class=apple-converted-space> </SPAN><BR>>> within the
pool."<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 href="mailto:ARIN-PPML@arin.net" target=_blank><SPAN
style="COLOR: purple">ARIN-PPML@arin.net</SPAN></A>).<BR>>>
Unsubscribe or manage your mailing list subscription
at:<BR>>><SPAN class=apple-converted-space> </SPAN><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank><SPAN
style="COLOR: purple">https://lists.arin.net/mailman/listinfo/arin-ppml</SPAN></A><BR>>>
Please contact<SPAN class=apple-converted-space> </SPAN><A
href="mailto:info@arin.net" target=_blank><SPAN
style="COLOR: purple">info@arin.net</SPAN></A><SPAN
class=apple-converted-space> </SPAN>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><SPAN
style="COLOR: purple">ARIN-PPML@arin.net</SPAN></A>).<BR>>
Unsubscribe or manage your mailing list subscription
at:<BR>><SPAN class=apple-converted-space> </SPAN><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank><SPAN
style="COLOR: purple">https://lists.arin.net/mailman/listinfo/arin-ppml</SPAN></A><BR>>
Please contact<SPAN class=apple-converted-space> </SPAN><A
href="mailto:info@arin.net" target=_blank><SPAN
style="COLOR: purple">info@arin.net</SPAN></A><SPAN
class=apple-converted-space> </SPAN>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><SPAN
style="COLOR: purple">ARIN-PPML@arin.net</SPAN></A>).<BR>Unsubscribe
or manage your mailing list subscription at:<BR><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank><SPAN
style="COLOR: purple">https://lists.arin.net/mailman/listinfo/arin-ppml</SPAN></A><BR>Please
contact<SPAN class=apple-converted-space> </SPAN><A
href="mailto:info@arin.net" target=_blank><SPAN
style="COLOR: purple">info@arin.net</SPAN></A><SPAN
class=apple-converted-space> </SPAN>if you experience any
issues.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV></BLOCKQUOTE></DIV>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'> <o:p></o:p></SPAN></P></DIV></BLOCKQUOTE>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica",sans-serif; BACKGROUND: white'>_______________________________________________</SPAN><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica",sans-serif'><BR><SPAN
style="BACKGROUND: white">ARIN-PPML</SPAN><BR><SPAN
style="BACKGROUND: white">You are receiving this message because you
are subscribed to</SPAN><BR><SPAN style="BACKGROUND: white">the ARIN
Public Policy Mailing List (<A
href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</A>).</SPAN><BR><SPAN
style="BACKGROUND: white">Unsubscribe or manage your mailing list
subscription at:</SPAN><BR><SPAN style="BACKGROUND: white"><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</A></SPAN><BR><SPAN
style="BACKGROUND: white">Please contact <A
href="mailto:info@arin.net">info@arin.net</A> if you experience any
issues.</SPAN></SPAN><o:p></o:p></P></DIV></BLOCKQUOTE></DIV>
<P
class=MsoNormal><o:p> </o:p></P></DIV></DIV></BLOCKQUOTE></TD></TR></TBODY></TABLE></P></P>
<DIV class=WordSection1>
<P class=MsoNormal>Hi Owen,<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>It’s hard to predict when the useful IPv4 lifetime will end,
so it’s hard to say whether runout of these reserved pools is unlikely,
especially if conditions change.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>If you feel 4.4 and 4.10 are severely overstocked,
maybe a proposal to release those “sequestered” addresses should be forthcoming,
as maintaining those pools at those levels is counter to our
mission?<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Do you have any comments on the problem statement, and the
idea that the haphazard and unpredictable influx of addresses into the waiting
list is problematic? For example, doesn’t the current constitution of the
waiting list encourage virtually all ARIN members to enter the lottery for a
/22? The size is small, the justification options pretty generous, the downside
minimal.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>In my mind the waiting list is a fraud magnet and has
outlived its usefulness, and yes, this is an attempt to eliminate it
without going down the auction route. The addresses haven’t been
destroyed, just taken off the market, adding the tiniest bit to the existing
pools, whose size was approved by the community.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I support the policy as written and amended.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Regards,<o:p></o:p></P>
<P class=MsoNormal>Mike<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<DIV
style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B>From:</B> ARIN-PPML <arin-ppml-bounces@arin.net>
<B>On Behalf Of </B>Owen DeLong<BR><B>Sent:</B> Thursday, August 15, 2019 5:10
PM<BR><B>To:</B> WOOD Alison * DAS <Alison.WOOD@oregon.gov><BR><B>Cc:</B>
arin-ppml <arin-ppml@arin.net><BR><B>Subject:</B> Re: [arin-ppml] Draft
Policy ARIN-2019-17: Returned Addresses to the 4.10 Reserved
Pool<o:p></o:p></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Really, it seems to me that this proposal is another attempt
at eliminating the waiting list for unmet requests.<o:p></o:p></P>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>The first attempt (ARIN auctions the space) met with
resistance from ARIN’s legal team (for good reason), so now this attempts to
sequester the space where it will be hard to distribute rather than allowing the
waiting list to have any potential to compete with the transfer
market.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>The proposed targets (4.4 and 4.10 pools) are well stocked
and unlikely to run out in any useful IPv4 lifetime.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>As such, restocking them from returned space strikes me as
just a way to sequester this space where it cannot be used.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>IMHO, this is counter to ARIN’s mission and should not be
allowed.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>I oppose the policy as written and as proposed to be
amended.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<DIV>
<P class=MsoNormal>Owen<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><BR><BR><o:p></o:p></P>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal>On Aug 15, 2019, at 13:55 , WOOD Alison * DAS via ARIN-PPML
<<A href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A>>
wrote:<o:p></o:p></P></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>Thank
you for the continued input on this draft policy proposal.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>I
will be updating the text of the draft policy to include both 4.4 and 4.10
pools. Point of information, the 4.4 pool currently has approximately
391 /24’s and 4.10 has approximately 15,753 /24’s available and are not
estimated to run out in the next five years.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>Please
keep your feedback coming, it is very helpful for the council.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'>-Alison</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Arial",sans-serif; COLOR: #44546a'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV>
<DIV
style="BORDER-TOP: #e1e1e1 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><B>From:</B><SPAN
class=apple-converted-space> </SPAN>ARIN-PPML [<A
href="mailto:arin-ppml-bounces@arin.net">mailto:arin-ppml-bounces@arin.net</A>]<SPAN
class=apple-converted-space> </SPAN><B>On Behalf Of<SPAN
class=apple-converted-space> </SPAN></B>Fernando
Frediani<BR><B>Sent:</B><SPAN
class=apple-converted-space> </SPAN>Tuesday, July 30, 2019 6:44
AM<BR><B>To:</B><SPAN class=apple-converted-space> </SPAN>arin-ppml
<<A
href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</A>><BR><B>Subject:</B><SPAN
class=apple-converted-space> </SPAN>Re: [arin-ppml] Draft Policy
ARIN-2019-17: Returned Addresses to the 4.10 Reserved Pool<SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'> <o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal
style="BACKGROUND: white; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>The point is
that you treating IP marketing as something 'natural' or a 'default route'
which it is not and can never be. Natural is to receive some addresses from
the RIR in first place so they are treated as anyone else was in the past and
have a chance to exist in the Internet with same conditions as all others.
From that if they need extra space then fine to seek for alternative
ways.<o:p></o:p></SPAN></P>
<P class=MsoNormal
style="BACKGROUND: white; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>I don't think a
new entrants would automatically qualify for 4.10 in all cases therefore any
space left should be targeted also to them as well to IPv6 transition and
critical infrastructure. Otherwise the community will be creating an
artificial barrier to them in order to favor the IP market while the RIR still
has IPv4 space available for them.<o:p></o:p></SPAN></P>
<P class=MsoNormal
style="BACKGROUND: white; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>Fernando<o:p></o:p></SPAN></P>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'>On 30/07/2019
10:30, Tom Fantacone wrote:<o:p></o:p></SPAN></P></DIV></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'>I would think
that the majority of new entrants would need at least some allocation to
help with IPv6 transition and would qualify for addresses from the 4.10
pool. Depending on what they receive from that pool and when, they may
not qualify for additional waiting list addresses and would have to go to
the transfer market for additional IPv4 space anyway. Those that don't
qualify under 4.10 can still get smaller IPv4 blocks on the transfer market
readily, and the cost for blocks in the /24-/22 range is not
prohibitive. Certainly an organization seeking a small IPv4 block for
multi-homing or other purposes is better off spending a few thousand dollars
to purchase a range than waiting a year on the waiting list to put their
plans in motion.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt; BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'><BR>Note that
while RIPE does not have a reserve pool specifically for IPv6 transition,
the expectation of their final /8 policy was to allow new entrants access to
IPv4 to assist in this transition. In reality, it didn't work out that
way and most of the /22 allocations to new LIRs from the final /8 were to
existing organizations who spun up new, related entities in order to
increase their IPv4 holdings:<BR><A
href="https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations"
target=_blank><SPAN
style="COLOR: purple"><BR>https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the-allocations</SPAN></A><BR><BR>I'm
also sympathetic to new entrants, but don't see the current waiting list as
a great help to them vs. the 4.10 pool or the transfer market, both of which
allow you your allocation in a timely fashion.<BR><BR>Best
Regards,<BR><BR>Tom Fantacone</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<DIV id=Zm-_Id_-Sgn1>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'>---- On Mon, 29
Jul 2019 11:39:32 -0400<SPAN
class=apple-converted-space> </SPAN><B>Fernando Frediani <<A
href="mailto:fhfrediani@gmail.com" target=_blank><SPAN
style="COLOR: purple">fhfrediani@gmail.com</SPAN></A>></B><SPAN
class=apple-converted-space> </SPAN>wrote ----</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV>
<BLOCKQUOTE
style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 5pt; BORDER-LEFT: #cccccc 1pt solid; MARGIN: 5pt 0in 5pt 3.75pt; PADDING-RIGHT: 0in">
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'>I find it
interesting the idea of privileging the pool dedicated to<SPAN
class=apple-converted-space> </SPAN><BR>facilitate IPv6 Deployment
and I also agree with the comments below in<SPAN
class=apple-converted-space> </SPAN><BR>the sense that it's not very
beneficial do most ARIN members due to max<SPAN
class=apple-converted-space> </SPAN><BR>size, /22, cannot be holding
more than a /20.<BR><BR>However one point I couldn't identify is where the
new entrants stand in<SPAN
class=apple-converted-space> </SPAN><BR>this new possible scenario ?
Will they only be able to apply under the<SPAN
class=apple-converted-space> </SPAN><BR>4.10 reserved pool ? If so
for a access/broadband ISPs may be easier to<SPAN
class=apple-converted-space> </SPAN><BR>fit, but not necessarily for
other scenarios and types of ISPs.<SPAN
class=apple-converted-space> </SPAN><BR>Therefore if I didn't miss
anything these returned addresses should also<SPAN
class=apple-converted-space> </SPAN><BR>be able to go to new
entrants, not only to 4.10 reserved pool conditions.<BR><BR>Best
regards<BR>Fernando Frediani<BR><BR>On 25/07/2019 17:32, Tom Fantacone
wrote:<BR>> I found the wording of the Problem Statement on this one a
bit<SPAN class=apple-converted-space> </SPAN><BR>> confusing.
However, after deciphering the effect of the actual policy<SPAN
class=apple-converted-space> </SPAN><BR>> change I support
it.<BR>><BR>> Essentially, all returned IPv4 space will no longer go
to the waiting<SPAN class=apple-converted-space> </SPAN><BR>> list
but will supplement the 4.10 reserved pool used to enhance IPv6<SPAN
class=apple-converted-space> </SPAN><BR>> deployment. This
essentially kills off the waiting list.<BR>><BR>> The recent
restrictions placed on the waiting list to reduce fraud<SPAN
class=apple-converted-space> </SPAN><BR>> have hobbled it to the
point where it's not very beneficial to most<SPAN
class=apple-converted-space> </SPAN><BR>> ARIN members. (Max
size, /22, cannot be holding more than a /20). <SPAN
class=apple-converted-space> </SPAN><BR>> It's essentially only
useful to new entrants, but those that go on it<SPAN
class=apple-converted-space> </SPAN><BR>> still have to wait many
months to receive their small allocation. If<SPAN
class=apple-converted-space> </SPAN><BR>> they justify need now,
but have to wait that long, how critical is<SPAN
class=apple-converted-space> </SPAN><BR>> their need if they're
willing to wait that long? Small blocks are not<SPAN
class=apple-converted-space> </SPAN><BR>> terribly expensive and
can be quickly gotten on the transfer market. <SPAN
class=apple-converted-space> </SPAN><BR>> I can understand waiting
that long for a large block needed for a<SPAN
class=apple-converted-space> </SPAN><BR>> longer term project due
to prohibitive cost, but I don't see a great<SPAN
class=apple-converted-space> </SPAN><BR>> benefit to the waiting
list as it stands.<BR>><BR>> Also, if there's any fraud left on the
waiting list, this would kill it.<BR>><BR>> I would hope, however,
that if implemented, those currently on the<SPAN
class=apple-converted-space> </SPAN><BR>> waiting list would be
grandfathered in. I do think some entities with<SPAN
class=apple-converted-space> </SPAN><BR>> legitimate need got
burned on the last change made to the waiting list.<BR>><BR>> At
04:05 PM 7/23/2019, ARIN wrote:<BR>>> On 18 July 2019, the ARIN
Advisory Council (AC) accepted<SPAN
class=apple-converted-space> </SPAN><BR>>> "ARIN-prop-276:
Returned Addresses to the 4.10 Reserved Pool" as a<SPAN
class=apple-converted-space> </SPAN><BR>>> Draft
Policy.<BR>>><BR>>> Draft Policy ARIN-2019-17 is below and can
be found at:<BR>>><BR>>><SPAN
class=apple-converted-space> </SPAN><A
href="https://www.arin.net/participate/policy/drafts/2019_17/"
target=_blank><SPAN
style="COLOR: purple">https://www.arin.net/participate/policy/drafts/2019_17/</SPAN></A><BR>>><BR>>>
You are encouraged to discuss all Draft Policies on PPML. The AC will<SPAN
class=apple-converted-space> </SPAN><BR>>> evaluate the
discussion in order to assess the conformance of this<SPAN
class=apple-converted-space> </SPAN><BR>>> draft policy with
ARIN's Principles of Internet number resource<SPAN
class=apple-converted-space> </SPAN><BR>>> policy as stated in
the Policy Development Process (PDP).<SPAN
class=apple-converted-space> </SPAN><BR>>> 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>>><SPAN class=apple-converted-space> </SPAN><A
href="https://www.arin.net/participate/policy/pdp/" target=_blank><SPAN
style="COLOR: purple">https://www.arin.net/participate/policy/pdp/</SPAN></A><BR>>><BR>>>
Draft Policies and Proposals under discussion can be found
at:<BR>>><SPAN class=apple-converted-space> </SPAN><A
href="https://www.arin.net/participate/policy/drafts/" target=_blank><SPAN
style="COLOR: purple">https://www.arin.net/participate/policy/drafts/</SPAN></A><BR>>><BR>>>
Regards,<BR>>><BR>>> Sean Hopkins<BR>>> Policy
Analyst<BR>>> American Registry for Internet Numbers
(ARIN)<BR>>><BR>>> Draft Policy ARIN-2019-17: Returned
Addresses to the 4.10 Reserved Pool<BR>>><BR>>> Problem
Statement:<BR>>><BR>>> An inconsistent and unpredictable
stream of address space is an<SPAN
class=apple-converted-space> </SPAN><BR>>> unsuitable method of
populating the waiting list (4.1.8.1) and<SPAN
class=apple-converted-space> </SPAN><BR>>> fulfilling
subsequent requests.<BR>>><BR>>> Policy
statement:<BR>>><BR>>> Change "4.10. Dedicated IPv4 Block to
Facilitate IPv6 Deployment" to<SPAN
class=apple-converted-space> </SPAN><BR>>> "4.10 Dedicated IPv4
Pool to Facilitate IPv6 Deployment"<BR>>><BR>>> Change" When
ARIN receives its last /8 IPv4 allocation from IANA, a<SPAN
class=apple-converted-space> </SPAN><BR>>> contiguous /10 IPv4
block will be set aside and dedicated to<SPAN
class=apple-converted-space> </SPAN><BR>>> facilitate IPv6
deployment. Allocations and assignments from this<SPAN
class=apple-converted-space> </SPAN><BR>>> block " to "In
addition to the contiguous /10 IPv4 block set aside<SPAN
class=apple-converted-space> </SPAN><BR>>> and dedicated to
facilitate IPv6 deployment, all returns and<SPAN
class=apple-converted-space> </SPAN><BR>>> revocations of
IPv4 blocks will be added to the pool of space<SPAN
class=apple-converted-space> </SPAN><BR>>> dedicated to the
facilitation of IPv6 deployment. Allocations and<SPAN
class=apple-converted-space> </SPAN><BR>>> assignments from
this pool "<BR>>><BR>>> Change "This block will be subject to
a minimum size allocation of<SPAN
class=apple-converted-space> </SPAN><BR>>> /28 and a maximum
size allocation of /24. ARIN should use sparse<SPAN
class=apple-converted-space> </SPAN><BR>>> allocation when
possible within that /10 block." to "This pool will<SPAN
class=apple-converted-space> </SPAN><BR>>> be subject to a
minimum size allocation of /28 and a maximum sized<SPAN
class=apple-converted-space> </SPAN><BR>>> allocation of /24.
ARIN should use sparse allocation when possible<SPAN
class=apple-converted-space> </SPAN><BR>>> within the
pool."<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
href="mailto:ARIN-PPML@arin.net" target=_blank><SPAN
style="COLOR: purple">ARIN-PPML@arin.net</SPAN></A>).<BR>>>
Unsubscribe or manage your mailing list subscription at:<BR>>><SPAN
class=apple-converted-space> </SPAN><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank><SPAN
style="COLOR: purple">https://lists.arin.net/mailman/listinfo/arin-ppml</SPAN></A><BR>>>
Please contact<SPAN class=apple-converted-space> </SPAN><A
href="mailto:info@arin.net" target=_blank><SPAN
style="COLOR: purple">info@arin.net</SPAN></A><SPAN
class=apple-converted-space> </SPAN>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><SPAN
style="COLOR: purple">ARIN-PPML@arin.net</SPAN></A>).<BR>> Unsubscribe
or manage your mailing list subscription at:<BR>><SPAN
class=apple-converted-space> </SPAN><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank><SPAN
style="COLOR: purple">https://lists.arin.net/mailman/listinfo/arin-ppml</SPAN></A><BR>>
Please contact<SPAN class=apple-converted-space> </SPAN><A
href="mailto:info@arin.net" target=_blank><SPAN
style="COLOR: purple">info@arin.net</SPAN></A><SPAN
class=apple-converted-space> </SPAN>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><SPAN
style="COLOR: purple">ARIN-PPML@arin.net</SPAN></A>).<BR>Unsubscribe or
manage your mailing list subscription at:<BR><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml"
target=_blank><SPAN
style="COLOR: purple">https://lists.arin.net/mailman/listinfo/arin-ppml</SPAN></A><BR>Please
contact<SPAN class=apple-converted-space> </SPAN><A
href="mailto:info@arin.net" target=_blank><SPAN
style="COLOR: purple">info@arin.net</SPAN></A><SPAN
class=apple-converted-space> </SPAN>if you experience any
issues.</SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV></BLOCKQUOTE></DIV>
<DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Verdana",sans-serif'> </SPAN><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'><o:p></o:p></SPAN></P></DIV></DIV></DIV>
<DIV>
<P class=MsoNormal style="BACKGROUND: white"><SPAN
style='FONT-SIZE: 12pt; FONT-FAMILY: "Times New Roman",serif'> <o:p></o:p></SPAN></P></DIV></BLOCKQUOTE>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica",sans-serif; BACKGROUND: white'>_______________________________________________</SPAN><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica",sans-serif'><BR><SPAN
style="BACKGROUND: white">ARIN-PPML</SPAN><BR><SPAN
style="BACKGROUND: white">You are receiving this message because you are
subscribed to</SPAN><BR><SPAN style="BACKGROUND: white">the ARIN Public Policy
Mailing List (<A
href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</A>).</SPAN><BR><SPAN
style="BACKGROUND: white">Unsubscribe or manage your mailing list subscription
at:</SPAN><BR><SPAN style="BACKGROUND: white"><A
href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</A></SPAN><BR><SPAN
style="BACKGROUND: white">Please contact <A
href="mailto:info@arin.net">info@arin.net</A> if you experience any
issues.</SPAN></SPAN><o:p></o:p></P></DIV></BLOCKQUOTE></DIV>
<P class=MsoNormal><o:p> </o:p></P></DIV></DIV><BR>2019-08-1517:48:10
<P></P>
<P>Notice <BR>This communication is intended to be received only by the
individual[s] or<BR>entity[s] to whom or to which it is addressed, and contains
information<BR>which is confidential, privileged and subject to copyright. Any
unauthorized<BR>use, copying, review or disclosure is prohibited. Please notify
the sender<BR>immediately if you have received this communication in error [by
calling<BR>collect, if necessary] so that we can arrange for its return at our
expense.<BR>Thank you in advance for your anticipated assistance and
cooperation.<BR> <BR> <BR>Cette communication est destinée uniquement
à la personne ou à la personne<BR>morale à qui elle est adressée. Elle contient
de l'information<BR>confidentielle, protégée par le secret professionnel et
sujette à des droits<BR>d'auteurs. Toute utilisation, reproduction, consultation
ou divulgation non<BR>autorisées sont interdites. Nous vous prions d'aviser
immédiatement<BR>l'expéditeur si vous avez reçu cette communication par erreur
(en appelant à<BR>frais virés, si nécessaire), afin que nous puissions prendre
des<BR>dispositions pour en assurer le renvoi à nos frais. Nous vous remercions
à<BR>l'avance de votre coopération.</P>
<P> </P>
<P> </P></BODY></HTML>