<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Unfortunately this issue spans both policy and membership, as it's
the limitations on the IPv4 space that is the trigger for the
multiple LIR discussion.<br>
The issues can't be accurately discussed as distinct parts, they are
co-dependant.<br>
-Tim.<br>
<br>
<div class="moz-cite-prefix">On 11/02/16 17:15,
<a class="moz-txt-link-abbreviated" href="mailto:h.lu@anytimechinese.com">h.lu@anytimechinese.com</a> wrote:<br>
</div>
<blockquote
cite="mid:32A64FFE-3855-4250-ABFF-C60CB2E6AC8C@anytimechinese.com"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>Hi</div>
<div><br>
</div>
<div>I think one thing need to be clarified here, if I am not
mistaken, Gert and Sander should confirm this as well, how many
LIR can a single entity open is an member issue, how many IP
each LIR get, should LIR return address, should v4 allocation
request to have v6 in place first etc, is an policy issue need
to be discussed in policy mailing list.</div>
<div><br>
在 2016年2月11日，下午5:09，Tim Armstrong <<a moz-do-not-send="true"
href="mailto:tim@treestle.com">tim@treestle.com</a>> 写道：<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
That's not viable yet, have you seen how fragmented th v6
table is, even Tier 1 ISPs have gaps.<br>
<br>
I would argue that we just reduce the allocation for
additional LIRs. That is if a single legal entity (or it's
subsidiaries) register a new LIR, then the new LIR registered
can only receive a /24 not a /22.<br>
<br>
This way no one would act in bad faith trying to skirt the
rules, and young ISPs still have the ability to grow without
feeling significantly choked.<br>
<br>
-Tim<br>
<br>
<div class="moz-cite-prefix">On 11/02/16 17:02, Janis
Jaunosans wrote:<br>
</div>
<blockquote cite="mid:56BCB0A2.4080502@streamnetworks.lv"
type="cite">just get ipv6. <br>
<br>
On 11/02/16 17:58, Matthias Šubik wrote: <br>
<blockquote type="cite">Additionally … <br>
<blockquote type="cite">On 11.02.2016, at 16:26, Simon
Lockhart <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:s.lockhart@cablecomnetworking.co.uk"><s.lockhart@cablecomnetworking.co.uk></a>
wrote: <br>
<br>
On Thu Feb 11, 2016 at 04:22:14PM +0100, Sebastian
Wiesinger wrote: <br>
<blockquote type="cite">* Nigel Titley <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:exec-board@ripe.net"><a class="moz-txt-link-rfc2396E" href="mailto:exec-board@ripe.net"><exec-board@ripe.net></a></a>
[2016-02-11 12:02]: <br>
<blockquote type="cite">2. If this activity is a
problem that must be prevented, what action <br>
should the RIPE NCC take to attempt its prevention?
<br>
</blockquote>
Do not allow additional LIR accounts for a member. <br>
</blockquote>
I would concur. <br>
<br>
One legal entity, one LIR. This should be easy for RIPE
to implement, given <br>
that they require evidence of company registration or
equivalent when <br>
establishing an LIR. <br>
</blockquote>
Even if it is possible to open more legal entities in the
RIPE region, when requiring an exclusive contact person it
makes it not any harder for really new members, but harder
for self cloning of members. <br>
<br>
It might even be needed, to require the new contact person
to complete the RIPE course, to slow down abusive
behavior. <br>
The use of a simple nominee is therefor more difficult
than without the course requirement. <br>
<br>
just my two cents <br>
Matthias <br>
<br>
<br>
</blockquote>
</blockquote>
</div>
</blockquote>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<style>
#liquid{
width:262px;
height: 94px;
padding-right: 20px;
}
#aws{
width:140px;
height:60px;
padding-top: 4px;
padding-bottom:0px;
}
#ripe{
width: 134px;
height: 62px;
}
#cloudstack{
padding-top: 28px;
padding-bottom: 8px;
width:150px;
height:28px;
}
#interoute{
width:112px;
height:64px;
}
.h_line{width:20px; height:1px;}
.v_line{width:1px; height:100px;}
</style>
<table border="0" cellpadding="0" cellspacing="0" width="606">
<tbody>
<tr>
<td width="266">
<div align="left"><a href="http://liquidns.com"><img
id="liquid" title="" alt=""
src="cid:part4.03080207.07060207@treestle.com">
</a></div>
</td>
<td colspan="3">
<h1 style="font-family: Arial, Helvetica, sans-serif;
font-size: 14px; color: #141414;">Tim Armstrong </h1>
<h2 style="font-family: Arial, Helvetica, sans-serif;
color: #787878; font-size: 12px; font-weight: 100;">Technical
Director<br>
Treestle B.V.<br>
Goudsesingel 78, 3011 KD, <br>
Rotterdam, The Netherlands<br>
Chamber of Commerce: 59116803<br>
Office: +31 (0) 10 3400 720<br>
Mobile: +31 (0) 61 7544 472</h2>
</td>
</tr>
<tr>
<td colspan="4">
<h2 style="font-family: Arial, Helvetica, sans-serif;
color: #787878; font-size: 12px; font-weight: 100;"
align="left"><img title="" alt="" class="h_line"
src="cid:part6.02030603.00050904@treestle.com"
height="1" width="20"><br>
<br>
Treestle runs one of the world's fastest global managed
DNS platforms at <a href="http://www.liquidns.com/"
target="_blank" rel="noreferrer"><span lang="EN-GB">www.liquidns.com</span></a><span
lang="EN-GB"> and <br>
offers LiquiD AutoScaler, a website-user centric
autoscaling solution at </span><a
href="http://www.liquidautoscaler.com/"
target="_blank" rel="noreferrer"><span lang="EN-GB"><a class="moz-txt-link-abbreviated" href="http://www.liquidautoscaler.com">www.liquidautoscaler.com</a></span></a>.<br>
<br>
<img title="" alt="" class="h_line"
src="cid:part6.02030603.00050904@treestle.com"
height="1" width="20"> </h2>
</td>
</tr>
<tr>
<td>
<h2 style="font-family: Arial, Helvetica, sans-serif;
color: #787878; font-size: 12px; font-weight: 100;"
align="left">Independent software vendor for:</h2>
</td>
<td width="153"> </td>
<td rowspan="2" width="5"><a
href="https://apps.db.ripe.net/search/lookup.html?source=ripe&key=ORG-TB77-RIPE&type=organisation"><img
title="" alt="" class="v_line"
src="cid:part6.02030603.00050904@treestle.com"
height="100" width="1"></a></td>
<td rowspan="2" width="182">
<h2 style="font-family: Arial, Helvetica, sans-serif;
color: #787878; font-size: 12px; font-weight: 100;"
align="left">Member of:
<p><a
href="https://apps.db.ripe.net/search/lookup.html?source=ripe&key=ORG-TB77-RIPE&type=organisation"><img
src="cid:part12.06090306.04070307@treestle.com"
alt="" title="" id="ripe" border="0" height="62"
width="134"></a></p>
</h2>
</td>
</tr>
<tr>
<td colspan="2" valign="top">
<div align="left"><a
href="https://aws.amazon.com/marketplace/pp/B013UXHSOO/?ref=_ptnr_pe_"><img
src="cid:part14.02050306.04030500@treestle.com"
alt="" title="" border="0" height="60" width="140"></a>
<a
href="https://cloudstore.interoute.com/LiquiDAutoScalerBasic"><img
id="interoute"
src="cid:part16.03090700.07070104@treestle.com"
alt="" title="" border="0" height="64" width="112"></a><a
href="https://liquidautoscaler.com/documentation/other/quickstart"><img
src="cid:part18.03090703.04060108@treestle.com"
alt="" id="cloudstack" title="" border="0"
height="28" width="150"></a></div>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>