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/[email protected]/
[members-discuss] [comms] [ncc-announce] [news] RIPE NCC Members and Multiple
- Previous message (by thread): [members-discuss] 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 ]
Radu-Adrian Feurdean
ripe-ncc at radu-adrian.feurdean.net
Wed Feb 17 00:35:46 CET 2016
On Tue, Feb 16, 2016, at 16:02, Max Tulyev wrote: > So quick way is to change policy and say every *COMPANY* should receive > one /22, not every *LIR*. No, that is the SLOW way. Policy change takes 3-4 months in a best-case scenario (everybody agrees - it is not the case here). And there is a difference between *HAVING* multiple LIR accounts for a company (i.e. after a purchase or merger) and *OPENING* a new LIR account for a company that does already have an account. the first case may be legitimate and is less subject to abuse. The second one is much more subject to abuse, as it has been seen during 2015. ... and then there is the "related LIR" issue (or non-issue), which is much more complex and difficult to solve properly. -- Radu-Adrian FEURDEAN fr.ccs
- Previous message (by thread): [members-discuss] 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 ]