This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/members-discuss@ripe.net/
[members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
- Previous message (by thread): [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
- Next message (by thread): [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jérôme Nicolle
jerome at ceriz.fr
Thu Feb 18 00:45:47 CET 2016
Hi Niels, 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. Best regards, -- Jérôme Nicolle +33 6 19 31 27 14
- Previous message (by thread): [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
- Next message (by thread): [members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]