<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>That's the main point. If such thing would ever becomes normal I
have no doubt it would create "internet landlords" and that's one
of the reasons I consider leasing a total misuse of the IP address
propose.<br>
I see by the many different views of the questions and even from
those who would be prepared to accept it, that there reservations
and concerns so clearly there is something that 'doesn't look
good' and is strange to the question.<br>
</p>
<p>There are already mechanisms to accommodate the needs of those
who need more IP addresses, the need of newcomers even with some
restrictions which has been working well since it was implemented
and in my view leases only accomplish very specific the needs of a
few mentioned.</p>
<p>Regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 03/11/2019 19:56, scott wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.DEB.2.21.1911031749440.8189@solarnetone.org">IMHO,
we should do everything we can to prevent "internet landlords."
Further, I do not see a legitimage use case problem that is solved
by allowing leasing that is not solved by upstream provided
address space, or barring that, 4.10 of the NRPM. If we want to
enable spammers, attack networks, and other bad actors, then
leasing is for sure a great solution for them, and the "internet
slumlords" that would provide their resources.
<br>
<br>
Scott
<br>
<br>
On Sun, 3 Nov 2019, Martin Hannigan wrote:
<br>
<br>
<blockquote type="cite">
<br>
<br>
On Sat, Nov 2, 2019 at 10:30 PM Owen DeLong
<a class="moz-txt-link-rfc2396E" href="mailto:owen@delong.com"><owen@delong.com></a> wrote:
<br>
<br>
<br>
[ clip ]
<br>
<br>
However, what I do not want to see is a situation where we
<br>
permit the desire to lease space as a justification for
<br>
obtaining space through the transfer market (or
<br>
any other mechanism). If you want to leas space you already
have,
<br>
then fine. But the desire to lease space in and of itself should
not
<br>
qualify as “utilization” or
<br>
“need” in evaluation of any form of resource request.
<br>
<br>
<br>
<br>
Needs a little more clarify for me. Either the lessor or lessee
has a right
<br>
to use the numbers as justification? The lessee may be the
logical party,
<br>
but seems less likely to be in the transfer market. However, if
they are
<br>
leasing numbers they may have legitimate need. On the other
hand, if a
<br>
lessor has a ratio like an ISP or other provider using numbers
in an
<br>
aggregated manner _and_ the lessee can't use the lease as
justification for
<br>
transfers, that would seem to be inline with current practice. I
do think
<br>
legitimately "in use" addresses should be eligible for "need"
credit. Isn't
<br>
the idea that "access" is being facilitated by providing the
numbers? You
<br>
can use RFC 1918 address space as a justification for need and
the numbers
<br>
are technically "not connected". I'm thinking source nor
business model
<br>
should matter, but that we're careful who is getting credit for
them. Just
<br>
saying that made me wonder if this is even worth addressing.
<br>
<br>
Feels like it is more sensible to allow the both to demonstrate
use as a
<br>
justification and let ARIN process sort it out.
<br>
<br>
$0.02
<br>
<br>
Best,
<br>
<br>
-M<
<br>
<br>
<br>
<br>
<br>
<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>