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] Policy proposal for services to legacy Internet resource holders
- Previous message (by thread): [ncc-services-wg] Policy proposal for services to legacy Internet resource holders
- Next message (by thread): [ncc-services-wg] Policy proposal for services to legacy Internet resource holders
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Thu Aug 30 13:12:42 CEST 2012
On 30 Aug 2012, at 11:00, Havard Eidnes wrote: > Therefore, I think I agree with what Daniel Karrenberg said about > what the present discussion should be about, I'm quoting: > > So what we have to decide as a community is: under which policies > does the RIPE community allow legacy space holders to register > their address space in the RIPE Internet Number registry. Nothing > more, nothing less. Indeed. I think it will be helpful to close this thread and start a new one which focuses on this key point. IMO legacy holders should be able to register/manage their space in the NCC database and get the equivalent service they would have enjoyed from SRI or whoever it was that issued the space all those years ago. Since that service was free back then, the comparable services for that space today from the NCC -- updating contact objects and delegation info mostly -- should be free too. YMMV. The incremental cost to the NCC of doing that should be negligible. The database and its supporting infrastructure is already there. And besides, the NCC provides services for the benefit of the broader Internet community than just its members. These must be costing quite a bit more than supporting a bunch of legacy space database entries. So the actual costs of this "free" service to legacy holders would probably be lost in the noise. Of course if that turned out not to be the case, then some mechanism would need to be found to fund it. Says he hand-waving from a distance... A fee of a few euro per update could do that but may be more bother than it's worth. It may well cost more than that to raise an invoice and do the bean counting. If/when the legacy holder needs additional RIR services related to that space -- say a secure reverse delegation or a cert for RPKI -- they can either pay for that on a cost recovery basis or become an LIR. Those services didn't exist when they got the space, so it's only right that a legacy holder pays for that extra functionality somehow.
- Previous message (by thread): [ncc-services-wg] Policy proposal for services to legacy Internet resource holders
- Next message (by thread): [ncc-services-wg] Policy proposal for services to legacy Internet resource holders
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]