Hi, I oppose policy 2015-01 because it can affect LIRs which are not new but they recently have received their /22 from last /8. (For example an LIR which is registered in 2010 and just received its /22) the LIR is not established to just receive the /22 but it has to wait for 2 years to be able to transfer it and I don't see any reason for this limitation. As a side effect it makes it harder for IP distribution which is the main goal of RIPE. Regards, Arash Naderpour
Hi,
I oppose policy 2015-01 because it can affect LIRs which are not new but they recently have received their /22 from last /8. (For example an LIR which is registered in 2010 and just received its /22) the LIR is not established to just receive the /22 but it has to wait for 2 I may misunderstand your reasoning, but that's why 2015-1 was desgined to do ... keep "dummy-LIRs" from being set up just to move the /22 to another LIR. limitation. As a side effect it makes it harder for IP distribution which is the main goal of RIPE. Actually, it aids it, as it keeps existing LIRs from going around and grabbing the available IP spaces and thereby keeping new entries from getting any ... please look at the ARIN region - they are down to ~140 /22 (fragmented into /23 and /24), which is still dropping quickly ... in contrast, RIPE's policies habe helped to still have a pool that might still last ~5 years ...
-garry
Hi, I'm not sure what you mean from dummy-LIRs but I think you mean the ones that just set up to get a single /22 to transfer it, am I right? If yes, It cannot keep "dummy-LIRs" from being set up, it just make it less attractive. But My argument was not about "dummy-LIRs set up", I'm talking about the LIRs that are not new and are already registered years ago, (before RIPE NCC starts distribution of last /8, before 2012) now if they apply to receive their last /22 why they have to wait for 2 years to be able to transfer them to others. (that makes IP distribution more difficult) It was not mandatory to receive last /22 and they are plenty of LIRs that are still using their existing allocations without getting their last /22. Not every olds LIR received its /22 till now and this 2015-01 can affect them too. Is it something supposed to be happened? I oppose this proposal because it has unnecessary effect on some of the genuine LIRs too. Arash Naderpour -----Original Message----- From: address-policy-wg [mailto:address-policy-wg-bounces@ripe.net] On Behalf Of Garry Glendown Sent: Wednesday, July 01, 2015 2:21 PM To: address-policy-wg@ripe.net Subject: Re: [address-policy-wg] Opposing policy 2015-01 Hi,
I oppose policy 2015-01 because it can affect LIRs which are not new but they recently have received their /22 from last /8. (For example an LIR which is registered in 2010 and just received its /22) the LIR is not established to just receive the /22 but it has to wait for 2 I may misunderstand your reasoning, but that's why 2015-1 was desgined to do ... keep "dummy-LIRs" from being set up just to move the /22 to another LIR. limitation. As a side effect it makes it harder for IP distribution which is the main goal of RIPE. Actually, it aids it, as it keeps existing LIRs from going around and grabbing the available IP spaces and thereby keeping new entries from getting any ... please look at the ARIN region - they are down to ~140 /22 (fragmented into /23 and /24), which is still dropping quickly ... in contrast, RIPE's policies habe helped to still have a pool that might still last ~5 years ...
-garry
I'm not sure what you mean from dummy-LIRs but I think you mean the ones that just set up to get a single /22 to transfer it, am I right? If yes, Yup It cannot keep "dummy-LIRs" from being set up, it just make it less attractive. exactly!
But
My argument was not about "dummy-LIRs set up", I'm talking about the LIRs that are not new and are already registered years ago, (before RIPE NCC starts distribution of last /8, before 2012) now if they apply to receive their last /22 why they have to wait for 2 years to be able to transfer them to others. (that makes IP distribution more difficult) Personally, I don't think any LIR that already has an allocation in the range of /19 or larger should even be allowed to get a /22 from the last /8 ... considering the trouble new LIRs have to get around with just a single /22, why shouldn't existing companies be stuck with what they have and think about conserving IPs a bit more? Also, if you e.g. already have a /16 (65k addresses), how much good do an additional 1024 addresses do you? Except maybe to monetize them by selling them off to someone who wants them ... So, in summary, keeping the restrictions on the /22 transfers up for both new and existing LIRs is more than fair ...
-garry
On Wed, Jul 1, 2015, at 07:23, Arash Naderpour wrote:
My argument was not about "dummy-LIRs set up", I'm talking about the LIRs that are not new and are already registered years ago, (before RIPE NCC starts distribution of last /8, before 2012) now if they apply to receive their last /22 why they have to wait for 2 years to be able to transfer them to others. (that makes IP distribution more difficult)
If by "distributing to others" you mean to customers, nothing stops you from doing that. If by "distributing to others" you mean "transfer" (generally the permanent transfer, which must pass RIPE NCC approval), yes, it does stop you from doing that, and that's the whole point.
It was not mandatory to receive last /22 and they are plenty of LIRs that are still using their existing allocations without getting their last /22.
No impact for them. They are not "obliged" to get their "last /22".
Not every olds LIR received its /22 till now and this 2015-01 can affect them too. Is it something supposed to be happened? I oppose this proposal because it has unnecessary effect on some of the genuine LIRs too.
Please explain.
Hi, On Wed, Jul 01, 2015 at 10:21:21AM +1000, Arash Naderpour wrote:
I oppose policy 2015-01 because it can affect LIRs which are not new but they recently have received their /22 from last /8. (For example an LIR which is registered in 2010 and just received its /22) the LIR is not established to just receive the /22 but it has to wait for 2 years to be able to transfer it and I don't see any reason for this limitation. As a side effect it makes it harder for IP distribution which is the main goal of RIPE.
This is not a new argument. It has been brought up, addressed, and indeed, this is one of the actual *goals* of the policy: stop LIRs from trading away /22s right away. I can see that those LIRs planning to trade off their /22 as soon as possible will not like the policy change, but I think we'll have to live with that (totally unexpected) side effect. (Besides, the main goal of RIPE is not "enable people to sell /22s" but "ensure that the remaining scraps of IPv4 address space are distributed in a way that is as fairly as possible, given the inherent unfairness of a run-out situation") Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Am I wrong, but the /22 for the existing companies is still subject to "need analysis"? Sort to say - if you have enough IPs in your existing netblock you are not eligible to get this add-ons? Then why the LIR should transfer the IPs if in the process of getting them it shows the need? RIPE NCC is for distributing addresses - it's OK - but for USAGE, not for SELLING. Second consideration is about supposed limitation in distribution of the IP addresses. Am I wrong again, but initially LIR is not the same as ISP? Yes, I agree that often it is the same company, but if an ISP is so badly in need of IPs it can buy SERVICE from a external LIR (the LIR will allow to use a block of its IP addresses). Transfers are not the only way of helping an ISP with addresses. Regards, Vladislav Potapov -----Original Message----- From: address-policy-wg [mailto:address-policy-wg-bounces@ripe.net] On Behalf Of Arash Naderpour Sent: Wednesday, July 1, 2015 3:21 AM To: address-policy-wg@ripe.net Subject: [address-policy-wg] Opposing policy 2015-01 Hi, I oppose policy 2015-01 because it can affect LIRs which are not new but they recently have received their /22 from last /8. (For example an LIR which is registered in 2010 and just received its /22) the LIR is not established to just receive the /22 but it has to wait for 2 years to be able to transfer it and I don't see any reason for this limitation. As a side effect it makes it harder for IP distribution which is the main goal of RIPE. Regards, Arash Naderpour
participants (6)
-
Arash Naderpour
-
Garry Glendown
-
Garry Glendown
-
Gert Doering
-
poty@iiat.ru
-
Radu-Adrian FEURDEAN