December 2018 - address-policy-wg

New on RIPE Labs: So Long Last /8 and Thanks For All the Allocations
by Mirjam Kuehne 28 Aug '19

28 Aug '19

Dear colleagues, On 17 April 2018, we allocated the last available block of 1,024 addresses in 185/8 - the last /8 we received from IANA back in 2011. This article on RIPE Labs looks at how this address space was allocated and how it is used today: https://labs.ripe.net/Members/wilhelm/so-long-last-8-and-thanks-for-all-the… It's important to keep in mind that while 185/8 is finished, we still have around nine million recovered IPv4 addresses in our available pool. Under current policy and growth rates, we expect these to last a further two years. Kind regards, Mirjam Kühne RIPE NCC

3 2

Re: [address-policy-wg] definition of "ASSIGNED PA" in IPv4 address allocation and assignment policy
by Erik Bais 21 Dec '18

21 Dec '18

Hi Martin, If you look at the text, would the LIR who assigned IP space to their own infra-structure not also be an End-User ? In the past, the LIR would describe IP space for themselves as Infra or INFRA-AW, but still give it the status Assigned PA. Something along the lines of this example : https://apps.db.ripe.net/db-web-ui/#/lookup?source=ripe&key=178.249.152.0%2… Regards, Erik Bais From: address-policy-wg <address-policy-wg-bounces(a)ripe.net> on behalf of Martin Tonusoo <martin.tonusoo(a)citictel-cpc.com> Date: Tuesday 13 November 2018 at 13:42 To: "address-policy-wg(a)ripe.net" <address-policy-wg(a)ripe.net> Subject: [address-policy-wg] definition of "ASSIGNED PA" in IPv4 address allocation and assignment policy Hello, according to "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region"(ripe-708) document, the "status" attribute value "ASSIGNED PA" has a definition of "This address space has been assigned to an End User for use with services provided by the issuing LIR". As "ASSIGNED PA" should also be used for assignments for LIR own infrastructure, then isn't the definition of "This address space has been assigned to the issuing LIR infrastructure or End User for use with services provided by the issuing LIR." bit more accurate? Best regards, Martin Tonusoo IP Network Engineer -------------------------- CITIC Telecom CPC www.citictel-cpc.com -------------------------- Direct: +372 622 3321 NOC 24/7: +372 622 3300 NOC 24/7: +7 495 9815670

2 3

Policy violation
by Aleksey Bulgakov 18 Dec '18

18 Dec '18

Hello. On the 7th of September the NCC implemeted the document https://www.ripe.net/publications/docs/ripe-709#transfer35 (The document is published on the 21th of September). The support clarify it that you cannot merge one LIR into the second LIR in case of M&A procedure because of the 24 month resource transfer restriction. However there is another document https://www.ripe.net/publications/docs/ripe-682#2-2-transfer… where you can read the next: 2.2 Transfer Restrictions This restriction does not prevent the resources from being transferred due to further mergers or acquisitions within the 24-month period. In this case the NCC doesn't follow own policies. Or am I wrong? I though the NCC should create the proposal to make changes to the transfer policies but don't implement unclear documents by the executive board consisting of 7 people. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

12 19

Fwd: Policy violation
by Uros Gaber 18 Dec '18

18 Dec '18

Dear Aleksey, Maybe you miss the point of having IPv4 resources (at this time). It is not to resell and make a profit, but to use where the resources are scarce, I think we can (still) be happy that RIPE and its members have made a good job until now so that any new LIR has some IPv4 resources at their disposal. Kind regards, Uros Gaber On Tue, Dec 18, 2018 at 11:31 AM Aleksey Bulgakov <aleksbulgakov(a)gmail.com> wrote: > I think the NCC wants to have Monopoly for IP selling and doesn't want to > devide profit with anyone. > > Of course it has more profit if there are more members with multiple > accounts or many different accounts of different legal entities witch will > pay for many years later. > > вт, 18 дек. 2018 г., 12:40 Gert Doering gert(a)space.net: > >> Hi, >> >> On Tue, Dec 18, 2018 at 12:37:40PM +0300, Aleksey Bulgakov wrote: >> > So then the NCC will say that it's non-commercial organization. >> >> This is not about making money. It is about making it clear that >> you can't just get cheap /22s from the RIPE NCC. >> >> But you know all that. >> >> Gert Doering >> -- NetMaster >> -- >> have you enabled IPv6 on something today...? >> >> SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael >> Emmer >> Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann >> D-80807 Muenchen HRB: 136055 (AG Muenchen) >> Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 >> >

1 0