[members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple

>Le 17/02/2016 16:17, Kampen, Niels van a écrit :
>> Could be as easy as making the initial /22 of a LIR non-transferable?
>
>This is one of the smartest things i've read all day, thank you for that.
>
>I do agree that the initial /22 assigned to a new LIR should not be
>allowed for transfer, no matter the context (merge ?).
>
>We'll all be better off if the acquisition of a new /22 to be
>re-integrated into an existing LIR's pool should be more expensive
>thanit's facial market value.
>
>So let's forbid new LIRs from transfer before, well, at least 5 years,
>that should help with regulating this mess.

We've gone through an acquisition a while back and I'm trying to change the name on our LIR. The RIPE NCC currently has the tendency to shift anything like this that isn't the most simple type of name change imaginable onto the Transfer Policy pile.

Given the number of hoops I'm forced to jump through for what isn't really that complicated, I'm seriously considering canceling my name change ticket and just waiting until the 24 months on my /22 expires so I can just do a transfer to get all my resources renamed.

Before we go down the path of extending the non-transfer period, I would like to see the RIPE NCC clean up its processes with regards to name changes.

Alex Le Heux
Rakuten Kobo Inc