<div dir="ltr">So I have yet another advice.<div><br></div><div>I like idea to pay some taxes for each transferred subnet. If you move /16 you should "pay" /20 to public RIPE's pool. What about this? </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 11, 2016 at 6:25 PM, Raul Pizarro Vazquez <span dir="ltr"><<a href="mailto:intervenciones@electronicamartinez.com" target="_blank">intervenciones@electronicamartinez.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Why not just to set a yearly fee for all IPs? for example 0,01$ / IP
per Month or so. Making that ips will really unused will get back to
ripe soon. Ripe could give them free again but all of us should pay
a little monthly for have them.<br>
<br>
<div>El 11/02/16 a las 16:05, Pavel Odintsov
escribió:<br>
</div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">I have few words about IPv6. I'm real fan of IPv6.
<div><br>
</div>
<div>But actually almost all companies who want last /22 subnet
just get IPv6 and do not use it really. From my point of view,
you should check real network usage by analyzing BGP routing
table.</div>
<div><br>
</div>
<div>In other words each LIR should:</div>
<div>1) Get new IPv6 subet from RIPE</div>
<div>2) Announce it and offer IPv6 address for checks</div>
<div>3) Get last /22 IPv4 subnet</div>
<div><br>
</div>
<div>Almost all "IPv6" subnets received for last months haven't
used really. That's bad. </div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Feb 11, 2016 at 6:01 PM, Jack <span dir="ltr"><<a href="mailto:noc@kwaoo.net" target="_blank">noc@kwaoo.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>> RIPE supports reselling of big subnets by
providing their Transfer listing service.<br>
> Those networks shouldn’t be sold. They should be
returned to the NCC pool and be assigned to providers who
need them.<br>
</span>Providers who need them, means, in my opinion,
providers who have a wide<br>
IPv6 deployment.<br>
Tough job to appreciate the IPv6 deployement status of a
LIR, but I<br>
really think this must be a requirement for getting more
IPv4 easily.<br>
<br>
You want IPv4 ? Deploy IPv6, then we will talk. You do not
care about<br>
IPv6 ? No v4 for you.<br>
<span><br>
<br>
><br>
><br>
> Von: members-discuss [mailto:<a href="mailto:members-discuss-bounces@ripe.net" target="_blank"></a><a href="mailto:members-discuss-bounces@ripe.net" target="_blank">members-discuss-bounces@ripe.net</a>]
Im Auftrag von Pavel Odintsov<br>
> Gesendet: Donnerstag, 11. Februar 2016 15:42<br>
</span>> An: Radu Brebu <<a href="mailto:dial@dialcube.ro" target="_blank">dial@dialcube.ro</a><mailto:<a href="mailto:dial@dialcube.ro" target="_blank"></a><a href="mailto:dial@dialcube.ro" target="_blank">dial@dialcube.ro</a>>><br>
> Cc: <a href="mailto:members-discuss@ripe.net" target="_blank">members-discuss@ripe.net</a><mailto:<a href="mailto:members-discuss@ripe.net" target="_blank"></a><a href="mailto:members-discuss@ripe.net" target="_blank">members-discuss@ripe.net</a>><br>
<span>> Betreff: Re: [members-discuss]
[ncc-announce] [news] RIPE NCC Members and Multiple LIR
Accounts - Please Discuss<br>
><br>
> Hello, folks!<br>
><br>
> That's good conversation. I'm representing VPS
service company. We bought multiple /20 and /21 subnets at
last 2 years.<br>
><br>
> But actually there really big injustice exists here!<br>
><br>
> I've followed all RIPE guidance and request resources
only when they really required for next 3-6 months. I have
95% subnet utilization in each network! All my IP
addresses really used.<br>
><br>
> But I known so much LIR's who just ignore RIPE rules
and requested bunch of /18, /16 networks many years
ago.... just because they can. Right now almost all this
networks are on IPv4 market.<br>
><br>
> And I should pay my money to persons which violated
RIPE rules for a long time.<br>
><br>
> Than't really weird, isn't it?<br>
><br>
</span>
<div>
<div>> On Thu, Feb 11, 2016 at 5:34 PM, Radu
Brebu <<a href="mailto:dial@dialcube.ro" target="_blank">dial@dialcube.ro</a><mailto:<a href="mailto:dial@dialcube.ro" target="_blank"></a><a href="mailto:dial@dialcube.ro" target="_blank">dial@dialcube.ro</a>>>
wrote:<br>
> Hi all,<br>
><br>
> This is a socialist way of thinking, you are free
(ipotetic speaking) to open another lir and satisfy your
VPS needs no? some companies prefer to plan their
business long term. In my opinion it's not ok to
prioritize resources keeping in mind only the need. We
are leaving and doing business in a capitalist
environment, buying resources it is what is all about.<br>
><br>
><br>
> On 02/11/16 16:19, José Manuel Giner wrote:<br>
> I agree with it. We need IPs to continue providing
VPS servers, and other LIRs with unused prefixes, no
sense...<br>
><br>
><br>
><br>
> On 11/02/2016 15:09, Aleksey Bulgakov wrote:<br>
> Hi, all.<br>
><br>
> I think, it is better to return unused
allocations, received before<br>
> 2012, to the NCC pool.<br>
><br>
> --<br>
> Kind regards,<br>
> Aleksey Bulgakov<br>
> FastTelecom, CEO<br>
> 7 926 6908729<br>
><br>
> 14:02, 11 февраля 2016 г., Nigel Titley :<br>
><br>
> Dear colleagues,<br>
><br>
> The RIPE NCC Executive Board would like to ask
the membership to<br>
> discuss<br>
> the issue of RIPE NCC members opening
additional LIR accounts.<br>
><br>
> There were comments at the RIPE NCC General
Meeting (GM) in November<br>
> 2015 that members having the ability to open
additional LIR accounts,<br>
> each of which can request a /22 of IPv4 address
space, may run against<br>
> the spirit of the last /8 policy. In light of
this, the Board<br>
> decided to<br>
> temporarily suspend the ability of RIPE NCC
members to open additional<br>
> LIR accounts.<br>
><br>
> The RIPE NCC began to allocate IPv4 address
space from the last /8<br>
> policy on 14 September 2012. Since that time
the RIPE NCC has<br>
> allocated<br>
> more than 8,600 /22s, yet there remains 0.94 of
a /8 still in the<br>
> pool.<br>
><br>
> ACTION REQUIRED:<br>
> The Board asks the membership to provide their
opinion on and discuss<br>
> the following points:<br>
><br>
> 1. Is the activity of members opening
additional LIR accounts a<br>
> problem<br>
> that must be prevented?<br>
><br>
> 2. If this activity is a problem that must be
prevented, what action<br>
> should the RIPE NCC take to attempt its
prevention?<br>
><br>
> Statistics pertinent to this discussion are
available in this<br>
> article on<br>
> RIPE Labs:<br>
> <a href="https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-lir-accounts?pk_campaign=members&pk_kwd=list-ncc" rel="noreferrer" target="_blank">https://labs.ripe.net/Members/laura_cobley/ripe-ncc-members-and-multiple-lir-accounts?pk_campaign=members&pk_kwd=list-ncc</a><br>
><br>
> The Board asks that members discuss this issue
on the Members Discuss<br>
> mailing list .<br>
><br>
> The Board will monitor the discussion and will
review it at the next<br>
> Executive Board Meeting on 31 March 2016.
Depending on the outcome of<br>
> that meeting, the Board may propose a
resolution for members to<br>
> vote on<br>
> at the RIPE NCC General Meeting in May 2016.<br>
><br>
> Best regards,<br>
><br>
> Nigel Titley<br>
> RIPE NCC Executive Board<br>
><br>
><br>
><br>
><br>
> ----<br>
> If you don't want to receive emails from the RIPE
NCC members-discuss<br>
> mailing list, please log in to your LIR Portal
account and go to the general page:<br>
> <a href="https://lirportal.ripe.net/general/" rel="noreferrer" target="_blank">https://lirportal.ripe.net/general/</a><br>
><br>
> Click on "Edit my LIR details", under "Subscribed
Mailing Lists". From here, you can add or remove
addresses.<br>
><br>
><br>
><br>
> ----<br>
> If you don't want to receive emails from the RIPE
NCC members-discuss<br>
> mailing list, please log in to your LIR Portal
account and go to the general page:<br>
> <a href="https://lirportal.ripe.net/general/" rel="noreferrer" target="_blank">https://lirportal.ripe.net/general/</a><br>
><br>
> Click on "Edit my LIR details", under "Subscribed
Mailing Lists". From here, you can add or remove
addresses.<br>
><br>
><br>
><br>
> --<br>
> Sincerely yours, Pavel Odintsov<br>
> CTO, FastVPS Eesti OU<br>
><br>
><br>
><br>
> ----<br>
> If you don't want to receive emails from the RIPE
NCC members-discuss<br>
> mailing list, please log in to your LIR Portal
account and go to the general page:<br>
> <a href="https://lirportal.ripe.net/general/" rel="noreferrer" target="_blank">https://lirportal.ripe.net/general/</a><br>
><br>
> Click on "Edit my LIR details", under "Subscribed
Mailing Lists". From here, you can add or remove
addresses.<br>
><br>
<br>
<br>
--<br>
</div>
</div>
Jack<br>
Kwaoo noc<br>
<br>
More details about KWAOO can be found at:<br>
<a href="https://as24904.kwaoo.net/" rel="noreferrer" target="_blank">https://as24904.kwaoo.net/</a><br>
<div>
<div><br>
----<br>
If you don't want to receive emails from the RIPE NCC
members-discuss<br>
mailing list, please log in to your LIR Portal account
and go to the general page:<br>
<a href="https://lirportal.ripe.net/general/" rel="noreferrer" target="_blank">https://lirportal.ripe.net/general/</a><br>
<br>
Click on "Edit my LIR details", under "Subscribed
Mailing Lists". From here, you can add or remove
addresses.</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Sincerely yours, Pavel Odintsov<br>
CTO, FastVPS Eesti OU</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>----
If you don't want to receive emails from the RIPE NCC members-discuss
mailing list, please log in to your LIR Portal account and go to the general page:
<a href="https://lirportal.ripe.net/general/" target="_blank">https://lirportal.ripe.net/general/</a>
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.</pre>
</blockquote>
<br>
</div></div><div>-- <br>
<hr style="width:670px" align="left">
<div>
<div> <img src="cid:part15.07030006.01060304@electronicamartinez.com" alt="Electrónica Martínez" height="220" width="220"> </div>
<div>
<p> <b>Nombre:</b> Raul Pizarro Vazquez<br>
<b>Cargo:</b> Responsable Técnico<br>
<b>Departamento:</b> Centro de Observacion de Red<br>
<b>Email:</b> <a href="mailto:intervenciones@electronicamartinez.com" target="_blank">intervenciones@electronicamartinez.com</a><br>
<b>Oficina:</b> 968 165 000<br>
<b>Averías:</b> 676 966 000<br>
<b>Página web:</b> <a href="http://www.electronicamartinez.es" target="_blank"></a><a href="http://www.electronicamartinez.es" target="_blank">www.electronicamartinez.es</a>
</p>
<hr> <a href="https://www.linkedin.com/company/10271615" target="_blank"> <img src="cid:part17.06090409.01060609@electronicamartinez.com" alt="LinkedIn" height="45" width="45"></a> <a href="https://twitter.com/EMartinez_SL" style="margin-left:10px" target="_blank"> <img src="cid:part19.09020004.05080408@electronicamartinez.com" alt="Twitter" height="45" width="45"></a> <a href="https://www.facebook.com/electronicamartinez0" style="margin-left:10px" target="_blank"> <img src="cid:part21.08050800.08020803@electronicamartinez.com" alt="Facebook" height="45" width="45"></a> <a href="https://plus.google.com/b/114382878353884084293/114382878353884084293" style="margin-left:10px" target="_blank"> <img src="cid:part23.03090907.02090709@electronicamartinez.com" alt="Google Plus" height="45" width="45"></a> </div>
</div>
<hr style="width:670px" align="left"></div>
</div>
<br>----<br>
If you don't want to receive emails from the RIPE NCC members-discuss<br>
mailing list, please log in to your LIR Portal account and go to the general page:<br>
<a href="https://lirportal.ripe.net/general/" rel="noreferrer" target="_blank">https://lirportal.ripe.net/general/</a><br>
<br>
Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Sincerely yours, Pavel Odintsov<br>CTO, FastVPS Eesti OU</div>
</div>