<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Mike,</p>
<p>I would hardly say it's time for a funeral in RIPE, but I would
ask, do you think it's a coincidence that roughly 75% of the /24
blocks that I have blackholed on my network for spamming my email
server are registered to anonymous hosting companies in the RIPE
region? I don't agree that the results of the RIPE policy speak
for themselves, and I would love to see more data aggregated by
some of the more talented internet sleuths on here regarding the
proportion of abuse activity split up by RIR. I also disagree with
all five of your assumptions about opposing this policy. The onus
is not on ARIN to sanctify practices that some are already
engaging in, but rather to distribute number resources in
accordance with community developed policy. If other RIR
communities choose to make other decisions, that doesn't make it
the correct decision for the ARIN region. I don't support any
policy that amplifies the practice of leasing because I reject
your arguments about the necessity of the practice. There is a
waiting list available for legitimate new entrants, and I don't
buy the argument that networks with greater than a /20 cannot
afford the capital outlay to purchase a block. Please feel free to
provide any data you can to back up your five assertions. For my
assertion, please consider the following:</p>
<p>
<blockquote type="cite">Prefixes exchanged within the RIPE region
as sales originate have the highest fraction of blacklisted IPs,
which is statistically significant.</blockquote>
</p>
<p>Source:
<a class="moz-txt-link-freetext" href="https://eprints.lancs.ac.uk/id/eprint/139789/1/VGiotsas_PAM2020_IPv4_Transfers_abuse.pdf">https://eprints.lancs.ac.uk/id/eprint/139789/1/VGiotsas_PAM2020_IPv4_Transfers_abuse.pdf</a><br>
</p>
<p>- Isaiah<br>
</p>
<div class="moz-cite-prefix">On 9/21/2021 3:24 PM, Mike Burns wrote:<br>
</div>
<blockquote type="cite"
cite="mid:00eb01d7af26$b3351ee0$199f5ca0$@iptrading.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<div>
<div>
<p class="MsoNormal">I am in total agreement with your
sentiment and the requirement for a circuit should
continue to stand.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Any policy that removes such a
requirement would render the management of Internet Number
Resources by the registry useless and thereby essentially
lead to no need for the registry after all.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Noah<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Noah,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Are you aware that there has been no
needs-test for RIPE transfers for many years and the RIR
system hasn’t collapsed?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To make it clear, in RIPE you can
purchase address space with the sole purpose of leasing it
out. And you have been able to do that for many years
now. Plainly, openly, within all policy. So please let us
know where to send the flowers for RIPE’s funeral. That
goes for others who predict that bad things will follow
from adopting this policy, please keep RIPE’s example in
mind to provide a reality check. The experiment has
already been performed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Owen has already pointed out the
futility of the circuit requirement in practice, yet you
think that’s what keeps the RIR system functional?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Opposing this policy means the only
lessors are the lucky incumbents. <o:p></o:p></p>
<p class="MsoNormal">Opposing this policy means a lack of
policy is preferred, despite the open practice of leasing.<o:p></o:p></p>
<p class="MsoNormal">Opposing this policy provides incentive
for registry-shopping and address outflow.<o:p></o:p></p>
<p class="MsoNormal">Opposing this policy reduces the lessor
pool and drives up lease rates.<o:p></o:p></p>
<p class="MsoNormal">Opposing this policy dis-incentivizes
accurate registration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Let me know if any of these assertions
require amplification, I guess some may not be clear but
this is already too long.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<br>
Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</body>
</html>