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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] LIR membership, was Policy disallowing spam from RIPE blocks
- Previous message (by thread): [anti-abuse-wg] LIR membership, was Policy disallowing spam from RIPE blocks
- Next message (by thread): [anti-abuse-wg] LIR membership, was Policy disallowing spam from RIPE blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Thu Mar 10 14:26:38 CET 2011
* Shane Kerr: > Tricky. The RIPE NCC is a membership organization - the LIRs are the > owners. Right now the membership process is really easy, but membership > does not automatically get you an allocation. I think it basically does, for IPv6. > You still have to justify your first allocation, and then justify > the assignments within your allocation when you want to use the > space. For creating the route object, allocation is sufficient. It's difficult to introduce the right level of barriers because we need to walk a fine line between preventing devaluation of RIPE address space and forming a cartel which excludes potential competitors. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [anti-abuse-wg] LIR membership, was Policy disallowing spam from RIPE blocks
- Next message (by thread): [anti-abuse-wg] LIR membership, was Policy disallowing spam from RIPE blocks
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]