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] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
- Previous message (by thread): [ncc-services-wg] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
- Next message (by thread): [ncc-services-wg] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Sun May 12 10:25:49 CEST 2013
Hi Sasha, > This would appear to empower the NCC to unilaterally, de-register or > even re-register such resources. (which is, IIRC, what the NCC > originally proposed and what triggered this proposal) > Maybe we should limit this to changing the relevant objects to "Unknown" > or similar... I think that is too limiting. We should limit the NCC to putting in accurate information. Deregistration would then only be possible if the NCC *knows* nobody is using that resource anymore, and I see no problem with that. (the problem will be finding proof, not the deregistration itself) Cheers, Sander
- Previous message (by thread): [ncc-services-wg] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
- Next message (by thread): [ncc-services-wg] 2012-07 New Draft Document and Impact Analysis Published (RIPE NCC Services to Legacy Internet Resource Holders)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]