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/ncc-services-wg@ripe.net/
[ncc-services-wg] RIPE NCC as escrow
- Previous message (by thread): [ncc-services-wg] RIPE NCC as escrow
- Next message (by thread): [ncc-services-wg] RIPE NCC as escrow
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco d'Itri
md at Linux.IT
Mon Dec 21 08:59:13 CET 2015
On Dec 17, Max Tulyev <president at ukraine.su> wrote: > Why RIPE NCC? > 1. RIPE NCC is exactly that entity who do (or reject to do) the IPv4 > transfer. Tha't the main point. RIPE NCC hostmasters using RIPE rules > evaluate the request and papers for IP transfer. Most of all escrow > companies don't even know what IP address is, and who is wrong or right > in potential conflict based on IP transfer. Can you show that: - there is a demonstrable need for this kind of services, and - the free market has failed to provide them, and - the fees that RIPE NCC would charge for providing this service would make it self-sustainable? -- ciao, Marco -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 648 bytes Desc: not available URL: </ripe/mail/archives/ncc-services-wg/attachments/20151221/50754738/attachment.sig>
- Previous message (by thread): [ncc-services-wg] RIPE NCC as escrow
- Next message (by thread): [ncc-services-wg] RIPE NCC as escrow
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]