Dear AP WG list,
as Marco reported we decided to withdraw the 2015-05 policy proposal.
Summary:
This proposal aimed to lower competitive disadvantage of new LIRs
allowing the request of an additional IPv4 /22 every 18 months if they
meet some requirements:
- Additional /22 IPv4 allocations
Hi everybody,
> We have had that discussion here on the list. Let's finish this with a
> constructive discussion on Thursday.
The RIPE meeting has just started its second day, and my brain has already
melted down.
s/Thursday/Wednesday/
Repeat: the session is on WEDNESDAY
Sorry for the
Hi *,
initially reading, nowadays just browsing over the posts about 2015-05,
I don't get it ...
Yes, I understand the pain new LIRs have with the limited availability
of v4 addresses. We have a small local provider, a small city that has
gone through the trouble of installing a FO
* Riccardo Gori
> Hi again Tore,
>
> Il 22/05/2016 12:01, Tore Anderson ha scritto:
> > * Riccardo Gori
> >
> >> and we turn minimum request to a /24
> >> we can address this kind of problem while slowing down LIRs sign up rate
> >> to obtain a /23 or /24 to address this kind of requests
> >
Hi again Tore,
Il 22/05/2016 12:01, Tore Anderson ha scritto:
* Riccardo Gori
and we turn minimum request to a /24
we can address this kind of problem while slowing down LIRs sign up rate
to obtain a /23 or /24 to address this kind of requests
This, in isolation, I think is idea worth
Hi Roger,
Il 23/05/2016 14:58, Roger Jørgensen ha scritto:
On Mon, May 23, 2016 at 2:48 PM, Riccardo Gori > wrote:
Hi Roger,
Il 23/05/2016 14:38, Roger Jørgensen ha scritto:
On Sun, May 22, 2016 at 10:25 AM, Riccardo Gori
Hi Nick,
Il 22/05/2016 13:10, Nick Hilliard ha scritto:
Riccardo Gori wrote:
There are no good solutions to the problem at hand, only compromises.
If the current policy is changed to something else, the people who
benefit in the short term will be happier and the people who pay for
this
Hi Ricardo,
> I am not expecting consensum. I just want to be serius about the
> considerations and the discussion that can come to some costructive for
> everyone.
We have had that discussion here on the list. Let's finish this with a
constructive discussion on Thursday.
> Someone choosed
Hi Sander,
Il 23/05/2016 22:06, Sander Steffann ha scritto:
Hi Ricardo,
If your read again 2015-05 you can easily find out that is not so silly.
Currently the only reasonable objection about 2015-05 is that may (I underline
may) speed up the allocation rate.
Please note that this ojection
Hi Tore,
> In order to facilitate growing your business beyond three customers, [...]
Please don't exaggerate like that. I understand what you mean, but please don't
make it personal.
> In any case, it is inevitable that at some point in time the RIPE NCC will
> simply not have any IPv4
Hi Ricardo,
> If your read again 2015-05 you can easily find out that is not so silly.
> Currently the only reasonable objection about 2015-05 is that may (I
> underline may) speed up the allocation rate.
> Please note that this ojection is based on the insinuation [...]
Ok, this is enough.
Tore,
can we turn back to non silly insinuations? and please stop personal
attacks. If your read again 2015-05 you can easily find out that is not
so silly.
Currently the only reasonable objection about 2015-05 is that may (I
underline may) speed up the allocation rate.
Please note that
* Riccardo Gori
> I think I answered, It's not nice to have, It's business demand and LIRs
> should be able to offer... with a /22 I can serve just up to 2 or 3 of
> my tipical business customers.
> This is lack of competitiveness.
So, let me get this straight:
In order to facilitate growing
Roger Jørgensen wrote:
> We've passed the "it's nice to have" some years ago, now we're down
> to , do you _really_ need 10 addresses? Can you survive with 2 and
> deploy IPv6?
No really, we're not. The RIPE Community exited the "do you really need
X addresses?" stage in 2014.
We're now at the
On Mon, May 23, 2016 at 2:48 PM, Riccardo Gori wrote:
> Hi Roger,
>
> Il 23/05/2016 14:38, Roger Jørgensen ha scritto:
>
> On Sun, May 22, 2016 at 10:25 AM, Riccardo Gori wrote:
>
>> Hi Roger,
>>
>> thank you for your questions. I try to answer below
>>
>> Il
On Sun, May 22, 2016 at 10:25 AM, Riccardo Gori wrote:
> Hi Roger,
>
> thank you for your questions. I try to answer below
>
> Il 21/05/2016 09:45, Roger Jørgensen ha scritto:
>
>
>
> Be specific, is it for having more address for the end-users? Datacenter?
> Services?
Riccardo Gori wrote:
>> There are no good solutions to the problem at hand, only compromises.
>> If the current policy is changed to something else, the people who
>> benefit in the short term will be happier and the people who pay for
>> this generosity will be disappointed.
> IPv6
If ipv6
* Gert Doering
> OTOH, I'm not sure if I see a pressing need here - LIRs that haven't
> asked for their /22 yet because they don't need it might just never
> show up, because they don't need it...
Absolutely true.
However, in my opition it would be more about fixing a couple of
perception
Hi,
Am 22.05.2016 um 12:01 schrieb Tore Anderson:
* Riccardo Gori
and we turn minimum request to a /24
we can address this kind of problem while slowing down LIRs sign up rate
to obtain a /23 or /24 to address this kind of requests
This, in isolation, I think is idea worth exploring
* Riccardo Gori
> and we turn minimum request to a /24
> we can address this kind of problem while slowing down LIRs sign up rate
> to obtain a /23 or /24 to address this kind of requests
This, in isolation, I think is idea worth exploring further.
The minimum allocation size started out as a
On Sun, May 22, 2016 at 10:36 AM, Gert Doering wrote:
>
>
> New LIRs - holders of /22 - have all the incentives to deploy IPv6
> already (because they do not have enough IPv4 to number everything with
> public v4 addresses) - but how would such a policy incentivize a big
> content
Hi,
On Sun, May 22, 2016 at 10:29:37AM +0200, Riccardo Gori wrote:
> every policy that makes IPv6 adoption a must can help slow down IPv4
> allocation rate and in the meanwhile will even lower IPv4 maket value
> that's why there is the so called "no solution"
> sorry for brevity, family time
Il 21/05/2016 12:05, Nick Hilliard ha scritto:
Roger Jørgensen wrote:
Be specific, is it for having more address for the end-users? Datacenter?
Services? Infrastructure? IPv6-to-IPv4 services? CGN? Proxyes?
[x] all of the above, and more.
This question isn't relevant as it seems - lots of
Hi Roger,
thank you for your questions. I try to answer below
Il 21/05/2016 09:45, Roger Jørgensen ha scritto:
On Fri, May 20, 2016 at 3:17 PM, Gert Doering wrote:
Dear Working Group,
On Fri, May 20, 2016 at 03:02:43PM +0200, Marco Schmidt wrote:
The Discussion Period for
Gert Doering wrote:
> Right - *but* it might be an interesting idea to turn around this discussion,
> away from haggling about the last scraps, into being able to give more
> useful guidance to LIRs.
>
> Like,
>
> - if you need to connect end-users, best practice is dual-stack with
>
Hi,
On Sat, May 21, 2016 at 11:05:16AM +0100, Nick Hilliard wrote:
> Roger Jørgensen wrote:
> > Be specific, is it for having more address for the end-users? Datacenter?
> > Services? Infrastructure? IPv6-to-IPv4 services? CGN? Proxyes?
>
> [x] all of the above, and more.
>
> This question
Roger Jørgensen wrote:
> Be specific, is it for having more address for the end-users? Datacenter?
> Services? Infrastructure? IPv6-to-IPv4 services? CGN? Proxyes?
[x] all of the above, and more.
This question isn't relevant as it seems - lots of organisations have
their needs and the RIPE NCC
On Fri, May 20, 2016 at 3:17 PM, Gert Doering wrote:
> Dear Working Group,
>
> On Fri, May 20, 2016 at 03:02:43PM +0200, Marco Schmidt wrote:
>> The Discussion Period for the proposal 2015-05, "Last /8 Allocation
>> Criteria Revision" has been extended until 13 June 2016.
>
> this
Dear Working Group,
On Fri, May 20, 2016 at 03:02:43PM +0200, Marco Schmidt wrote:
> The Discussion Period for the proposal 2015-05, "Last /8 Allocation
> Criteria Revision" has been extended until 13 June 2016.
this has been decided by proposers and WG chairs based on your discussion
and the
Hi Arash -
On 13.05.2016 03:01, Arash Naderpour wrote:
> That's not true, I know some LIRs qualified for /22 not requesting it
> and they are not running on auto-pilot (there are fully aware of the
> market situation)
OK, even then: your point is?
Do you empty your bank account the second your
Hi everyone,
I agree with Wilhelms arguments and I want to add my personal thoughts about
2015-05. I dont think that it is a good thing, if depletation of the RIPE NCCs
IPv4 address pool will speed up and in my opinion it is the wrong signal to
support the NCCs members with the historical
* Riccardo Gori
> Thank you to all old LIRs that didn't request their last /22 so I had
> the oportunity to request for it early Jan/2015.
Marco estimated that the pool would last for around five years under
the current policy[1]. For the sake of the argument, let's assume he's
spot on, to the
Am 12.05.2016 um 15:48 schrieb Randy Bush:
it's not just our grandchildren. if the last /8 policy had not been put
in place and taken seriously, *today's* new LIRs might not be able to get
IPv4 space.
randy
Well said.
Look at the other RIRs who cannot offer any IPv4 space to new members.
Hi Peter,
Il 12/05/2016 18:15, Peter Hessler ha scritto:
On 2016 May 12 (Thu) at 18:00:07 +0200 (+0200), Riccardo Gori wrote:
:We are proposing to help LIRs to gain some sustainability of their new
:businesses.
First you say this.
:again many thanks to all LIRs that didn't request their last
Hi Randy,
that's why we (defined somewhere pigs) are not rewriting base concept of
"last /8"
We are proposing to help LIRs to gain some sustainability of their new
businesses.
This is 'cause some LIRs in the past eated almost all the space and
created stockpiles of unused space and some years
Hi Sander,
thank you for your answer
Il 12/05/2016 14:16, Sander Steffann ha scritto:
Hi Riccardo,
Please explain how the current policy obtained a "success", luck? Why such
policy was accepted and reached its consensum at that time?
I can answer that one.
For 2010-02
Dear Remco and Radu-Adrian,
On 11/05/2016 23:21, Radu-Adrian FEURDEAN wrote:
(if any of the NCC staff wants to verify my numbers, feel free to do so)
Please !
Since it's not easy to find the following information:
- if a LIR received or not it's "last /22" (cannot distinguish from one
that
Hi,
> Op 12 mei 2016, om 15:48 heeft Randy Bush het volgende
> geschreven:
>
> it's not just our grandchildren. if the last /8 policy had not been put
> in place and taken seriously, *today's* new LIRs might not be able to get
> IPv4 space.
True. Without the current policy
it's not just our grandchildren. if the last /8 policy had not been put
in place and taken seriously, *today's* new LIRs might not be able to get
IPv4 space.
randy
Hi
The suggested Rule is a way to support new and small LIR, There is many
small LIR they need new IP addresses, The Rule can help them.
Thanks
On 5/12/2016 3:46 PM, Sander Steffann wrote:
Hi Riccardo,
Please explain how the current policy obtained a "success", luck? Why such
policy was
Hi Riccardo,
> Please explain how the current policy obtained a "success", luck? Why such
> policy was accepted and reached its consensum at that time?
I can answer that one.
For 2010-02 (https://www.ripe.net/participate/policies/proposals/2010-02) the
WG started working down from one /8.
Goodmoring Remco,
I read that you don't want to comment more about 2015-05.
I'll respect you and I won't wait for an answer and we can leave
everything for a quick chat in Copenhagen but I have to leave my comment
on your analisys.
In your example you suppose that every LIR under a /20 will
On Wed, May 11, 2016, at 21:53, Remco van Mook wrote:
> OK, have it your way. Let's look at some numbers:
>
> Available in 185/8 right now: ~ 6,950 /22s (1)
> Available outside 185/8 right now: ~ 8,180 /22s (1)
I'm OK with that.
> New LIRs since January 2013: ~4,600 (2,3)
> Budgeted membership
On Wed, May 11, 2016, at 09:47, Remco van Mook wrote:
> Again, you can't have it both ways. Current policy is not limited to
> 185/8, so your proposal does have an impact. Actually 185/8 is more than
> half gone by now (9571 allocations that I can see as of this morning) -
> effectively this
Arash,
> On 10 May 2016, at 03:18 , Arash Naderpour wrote:
>
> Remco, <>
>
> Calling anyone supporting a policy delusional is not really helping the
> discussion we have here, you can still express your own opinion without using
> that.
>
you can't have it both
On Wed, May 11, 2016 at 9:22 AM, Riccardo Gori wrote:
>
> Il 11/05/2016 09:02, Roger Jørgensen ha scritto:
>
>
>
> minor correction, it is a state that was reached once IANA allocated the
> last /8 to all the RIR's, and it affect _all_ address space after that point.
>
>
>
>
>
Il 11/05/2016 09:02, Roger Jørgensen ha scritto:
On Tue, May 10, 2016 at 3:44 AM, Randy Bush wrote:
you may find reading the actual last /8 policy informative.
Last /8 is not really get affected by this policy.
- Additional /22 IPv4 allocations can be only provided from
> P.S my understanding from 2015-05 is that it divides the current pool
> into 2 separate parts, last allocation of /8 and additional free IP
> pool received from IANA.
that's nice. as i said a bit ago, you may want to read the last /8
policy and not start trying to redifine terms.
om]
Sent: Tuesday, 10 May 2016 11:44 AM
To: Arash Naderpour <arash_...@parsun.com>
Cc: RIPE address policy WG <address-policy-wg@ripe.net>
Subject: Re: [address-policy-wg] 2015-05 Discussion Period extended until 13
May 2016 (Last /8 Allocation Criteria Revision)
you may find reading the
you may find reading the actual last /8 policy informative.
> Last /8 is not really get affected by this policy.
> - Additional /22 IPv4 allocations can be only provided from address space
> outside 185/8
this is misleading or just sadly misinformed
last /8 is not an address range, it is a
[mailto:address-policy-wg-boun...@ripe.net] On
Behalf Of Mikael Abrahamsson
Sent: Friday, 15 April 2016 5:46 PM
To: RIPE Address Policy WG <address-policy-wg@ripe.net>
Subject: Re: [address-policy-wg] 2015-05 Discussion Period extended until 13
May 2016 (Last /8 Allocation Criteria Revision)
ehalf
Of remco van mook
Sent: Friday, 15 April 2016 8:50 AM
To: Marco Schmidt <mschm...@ripe.net>; address-policy-wg@ripe.net
Subject: Re: [address-policy-wg] 2015-05 Discussion Period extended until 13
May 2016 (Last /8 Allocation Criteria Revision)
Dear colleagues,
I'd
> On 9 May 2016, at 15:16, Arash Naderpour wrote:
>
>
>> Tough. We’re out of IPv4. We’re all struggling due to a lack of IPv4
>> resources. Everyone just has to make the best of it with whatever they have
>> now. Anyone >planning to grow their network using IPv4 simply
>Tough. We’re out of IPv4. We’re all struggling due to a lack of IPv4
>resources. Everyone just has to make the best of it with whatever they have
>now. Anyone >planning to grow their network using IPv4 simply cannot base
>their plans on repeatedly going to >the NCC and asking for more. It’s
> On 9 May 2016, at 11:37, Fabio Zannicolò - Voix s.r.l.
> wrote:
>
> Today small companies have competitiveness problems due to lack of IPv4
> resources.
Tough. We’re out of IPv4. We’re all struggling due to a lack of IPv4 resources.
Everyone just has to make the best of
> For me, the issue is that right now we are in a "please suffer, the
> solution is not working yet" situation.
what solution is not working for you?
randy, running v6 commercially since '97
On Fri, Apr 22, 2016 at 2:29 PM, Radu-Adrian FEURDEAN <
ripe-...@radu-adrian.feurdean.net> wrote:
>
> You are talking about people addicted to Coca-Cola. You can't just ask
> them to plain stop drinking Coca-Cola, as long as you have some (and
> even if you no longer have, it's still difficult).
On Fri, Apr 22, 2016, at 18:00, Nick Hilliard wrote:
> Radu-Adrian FEURDEAN wrote:
> > I do understand that. I just do not agree with the "as long as possible,
> > no matter what" approach.
> > For me, the issue is that right now we are in a "please suffer, the
> > solution is not working yet"
On Fri, Apr 22, 2016, at 17:37, Nick Hilliard wrote:
> As a separate issue, the RIPE NCC is not in the business of telling its
> members how to run their networks.
Still a somehow separate issue, it shouldn't be in the "sell IPs"
business neither, but it looks like it's exactly what it's doing
Hi Roger,
Il 21/04/2016 08:40, Roger Jørgensen ha scritto:
On Wed, Apr 20, 2016 at 10:43 PM, Radu-Adrian FEURDEAN
wrote:
On Wed, Apr 20, 2016, at 12:50, Niall O'Reilly wrote:
As Roger Jørgensen has explained, once the policy was triggered, it
was to
Adrian Pitulac wrote:
> I think this has not been expressed directly, but IPv6 implementation
> obligations in this policy might be the reason why it could be MUCH
> better than existing policy who offers the opportunities for future
> entrants but does not have a long term solution for the real
On 22/04/16 16:05, Nick Hilliard wrote:
Regarding the current allocation policies, you still have not addressed
the query that several people have raised about why it is better to shut
off opportunities for future internet service market entrants than it is
to make things marginally easier for a
Hi,
> I do understand that. I just do not agree with the "as long as possible,
> no matter what" approach.
> For me, the issue is that right now we are in a "please suffer, the
> solution is not working yet" situation.
> Pain management. The only solution right now is pain suppressors. Some
>
On Fri, Apr 22, 2016, at 15:05, Nick Hilliard wrote:
> Regarding the current allocation policies, you still have not addressed
> the query that several people have raised about why it is better to shut
> off opportunities for future internet service market entrants than it is
> to make things
Radu-Adrian FEURDEAN wrote:
> You are talking about people addicted to Coca-Cola. You can't just ask
> them to plain stop drinking Coca-Cola, as long as you have some (and
> even if you no longer have, it's still difficult).
People can be as addicted to using ipv4 addresses as they want. It
On Fri, Apr 22, 2016, at 10:46, Stepan Kucherenko wrote:
> Last /8 policy came with some strings attached (IPv6 allocation) but
> there is no way a new LIR will show some IPv6 progress before initial
> IPv4 allocation was made. But with additional allocation it IS possible
> to check if they
> Last /8 policy came with some strings attached (IPv6 allocation) but there
> is no way a new LIR will show some IPv6 progress before initial IPv4
> allocation was made.
>
Can you elaborate a bit please ?
Denis
On 22.04.2016 11:05, Randy Bush wrote:
believing ipv4 allocation as an incentive for ipv6 deployment is yet
another in a long line of ipv6 marketing fantasies/failures. sure, give
them a v6 prefix, and they may even announce it. but will they convert
their infrastructure, oss, back ends,
believing ipv4 allocation as an incentive for ipv6 deployment is yet
another in a long line of ipv6 marketing fantasies/failures. sure, give
them a v6 prefix, and they may even announce it. but will they convert
their infrastructure, oss, back ends, customers, ... to ipv6? that
decision is
Jan,
Allow me to translate this to your way of seeing it.. :)
Coca-Cola is ending soon, so no one could get any.. There are parties
who never drank water, so based on the the policy, they are given a
little coca-cola if they start drinking water (IPv6). This if in their
help so they can get
On Thu, Apr 21, 2016 at 10:19 PM, Radu-Adrian FEURDEAN <
ripe-...@radu-adrian.feurdean.net> wrote:
>
> Small guys are either among the first or among the last to do it. You
> can find incetives from them (??? extra /22 ???)
>
This is a part of reasoning I don't understand.
"We would like for you
On Thu, Apr 21, 2016, at 12:38, Stepan Kucherenko wrote:
>
> They have to deal with that anyway sooner or later. Also it might become
> an additional pressure, "our rivals have this strange thing called IPv6
> on their site, can we do it too?".
At which point I prefer being in the situation of
> On 21 Apr 2016, at 11:38, Stepan Kucherenko wrote:
>
> There is also a problem with IPv6 roll-outs that it's usually (almost
> always?) bigger guys, but smaller companies will lag behind for years if not
> decades. Small incentive for small companies to keep up ?
Not true
On Wed, Apr 20, 2016 at 10:43 PM, Radu-Adrian FEURDEAN
wrote:
> On Wed, Apr 20, 2016, at 12:50, Niall O'Reilly wrote:
>>As Roger Jørgensen has explained, once the policy was triggered, it
>> was to apply to all subsequent allocations.
>
> However, in the
Hi,
On Tue, Apr 19, 2016, at 16:55, Stepan Kucherenko wrote:
> Why not just check for record for their main site and mention of
> IPv6 somewhere, like "/X for every customer on every tariff" or
> something similar depending on the market ?
>
> It may put enough pressure for them to
On Wed, Apr 20, 2016, at 12:50, Niall O'Reilly wrote:
>IIRC, the triggering of the "last /8" policy (as it has usually been
> known)
>did not coincide with receipt of 185/8 from (NB: not "by") IANA by
> RIPE NCC,
>but rather with the first allocation by RIPE NCC from 185/8.
185/8
Hi Gert,
Il 20/04/2016 13:22, Gert Doering ha scritto:
Hi,
On Wed, Apr 20, 2016 at 01:14:16PM +0200, Riccardo Gori wrote:
sorry but maybe this feeds the confusion about last /8 appling only to
185/8 or the whole RIPE available pool
There was confusion about this in the past, so the NCC
Hi,
On Wed, Apr 20, 2016 at 01:14:16PM +0200, Riccardo Gori wrote:
> sorry but maybe this feeds the confusion about last /8 appling only to
> 185/8 or the whole RIPE available pool
There was confusion about this in the past, so the NCC consulted the working
group, we discussed it here on the
But Niall,
I have to admit that these two statement at point 5.3 confuses me a bit:
[...]
5.3 Address Recycling
Any address space that is returned to the RIPE NCC will be covered by
the same rules as the address space intended in section 5.1.
This section only applies to address space that is
Dear Ingrid,
thank you for you help
Il 20/04/2016 12:09, Ingrid Wijte ha scritto:
Dear Riccardo,
(I am responding on behalf of Andrea, who is currently traveling).
We just wanted to confirm that Hans Petter and Roger are correct. The
policy text you quoted was designed to allow address
Dear Riccardo,
(I am responding on behalf of Andrea, who is currently traveling).
We just wanted to confirm that Hans Petter and Roger are correct. The
policy text you quoted was designed to allow address space to be
returned to IANA. It does not refer to the way that the RIPE NCC should
Hi Roger,
Il 20/04/2016 11:00, Roger Jørgensen ha scritto:
On Wed, Apr 20, 2016 at 1:17 AM, Hans Petter Holen wrote:
On 16.04.2016 12.29, remco.vanm...@gmail.com wrote:
This confusion has been haunting the final /8 policy from day one - it was
never about what to do with
On Mon, Apr 18, 2016 at 9:06 PM, Radu-Adrian FEURDEAN
wrote:
> If it can get more support, why not ?
> 5 stars, why not ? (actually I have some idea why, and it wouldn't
> bother me)
To me it seems like there are a not so minor misunderstanding right
here. It
Hi Hans, good morning list,
I think there is no confusion.
section 5.3 https://www.ripe.net/publications/docs/ripe-649
[...]
5.3 Address Recycling
Any address space that is returned to the RIPE NCC will be covered by
the same rules as the address space intended in section 5.1.
This section
> On 19 Apr 2016, at 23:21, Hans Petter Holen wrote:
>
> I also see new LIRs beeing set up to sell the space for profit.
That’s regrettable and I wish it stopped. [Well it will when we run out of
v4... :-)]
But if we could stop this, I suppose those “bad actors” would just
On 16.04.2016 12.29,
remco.vanm...@gmail.com wrote:
This confusion has been haunting the final /8 policy
from day one - it was never about what to do with specifically
185/8, but what to do with all future allocations from the moment
we needed to start
On 15.04.2016 00.50, remco van mook wrote:
a few obvious loopholes that are now being used to contravene the
intention of the policy,
I would be interested to see how this can be done effectively.
As a matter of transparency I think it is important to understand all
the aspects of this.
The
On 14.04.2016 22.07, Erik Bais wrote:
but the difference is an issue of fully running out within 18 months or 5.3
years.
Thanks for a very useful analysis Erik.
I think this is the key point - does the community want to put priority
short term or longer term?
--
Hans Petter Holen
Mobile +47
Hi
On Wednesday 20 April 2016, Hans Petter Holen wrote:
> On 16.04.2016 19.00, Jim Reid wrote:
>
>> I actually said "This proposal, if adopted, would pretty much guarantee
>> the free pool would not survive 10 months. That is one of the reasons why I
>> oppose it.”
>>
> If I
On 15.04.2016 20.59, Adrian Pitulac wrote:
I'm more inclining to believe that certain old LIR's made a big
business from this, by creating an artificial market and then sold
their free ip pools on the market for a hefty profit.
I do not think this is the case.
What I see is that old LIRs
On 14.04.2016 18.13, Jim Reid wrote:
I know companies who've done this. It isn't sensible.
True. But the NCC has ways to deal with those sorts of bad actors. Besides, the
checks on a new LIR raise a reasonably high barrier for those who try to game
the system in this way.
No.
I work for a
On 18/04/16 18:56, Mikael Abrahamsson wrote:
On Mon, 18 Apr 2016, Adrian Pitulac wrote:
Having a condition like 3 star IPv6 RIPEness to be able to get
another IPv4 block each 18 months will provide enough thrust to small
entities to enable IPv6 in their networks and this way doing
Hi Carten,
Il 17/04/2016 23:59, Carsten Schiefner ha scritto:
Riccardo,
On 15.04.2016 07:48, Riccardo Gori wrote:
with all respect I don't see a "remarkable success" in current last /8
policy.
We are dealing with the same amount of space as September 2012
so it works as designed me thinks.
Hello,
I've read the proposal and arguments for and against and indeed all the
various different opinions presented. Although I can see some merit to
support the proposal from a needs based perspective and use of reclaimed
addresses. Personally I cannot however ignore the fact that new LIR's
On 15.04.2016 00:33, Niall O'Reilly wrote:
> On 14 Apr 2016, at 17:01, Jim Reid wrote:
>
>> I strongly disagree with the proposal
>
> what Jim said, which you don't need to see again.
> Well said, Jim.
Ad idem.
Best,
-C.
On Sun, Apr 17, 2016, at 10:42, Lu Heng wrote:
> As I understand, more and more end user are becoming LIR as their ISP
> refuse to give them IP, therefore it fundamentally changed the
> very definition of LIR.
>
> The outbreak in the member mailing list last time reminds us how big that
> group
I am in favor this policy
Daniela
=
Daniela Catellani
+39 338 8986361
dani...@viaturchetta.it
t;ra...@psg.com>
Fecha: domingo, 17 de abril de 2016, 4:50
Para: Lu Heng <h...@anytimechinese.com>
CC: RIPE Address Policy WG <address-policy-wg@ripe.net>
Asunto: Re: [address-policy-wg] 2015-05 Discussion Period extended until 13 May
2016 (Last /8 Allocation Criteria Revision)
>&
> On 16 Apr 2016, at 12:36, Radu-Adrian FEURDEAN
> wrote:
>
> On Fri, Apr 15, 2016, at 16:09, Tim Chown wrote:
>
>> As others have said, everyone wants to grow. If you’re starting a new
>> venture v6 should be at the heart of what you’re doing.
>
> This is a
i'll try to see in the future...
Small LIR will register on different company (or daughter) LIR just to
take a "only one /22"
many other companies will becoma a LIR just to take v4 IPs.
It's cheaper than >10 EUR/ip, right (this is already happening).
Imagine after some period of time how much
1 - 100 of 270 matches
Mail list logo