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/db-wg@ripe.net/
[db-wg] Proposal regarding Orphaned Objects
- Previous message (by thread): [db-wg] Proposal regarding Orphaned Objects
- Next message (by thread): [db-wg] Proposal regarding Orphaned Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Fri May 1 15:47:12 CEST 2015
Dear Denis, On Fri, May 01, 2015 at 12:44:46PM +0000, denis walker wrote: > The reclaim functionality does cover the related routing and reverse > delegation objects. That is what it was introduced for. The point you > are missing is that it ONLY applies to resource objects where the RIPE > NCC has a contractual relationship with the resource holder (or their > sponsoring organisation) for that resource. If you want this > functionality for legacy address space I suspect you need to consider > the address policy issues before looking at database technical issues. I learned something new today! Thank you. Is someone aware of a document that describes why the reclaim functionality was not made available to any and all inetnum holders? Is there some kind of technical limitation? Kind regards, Job
- Previous message (by thread): [db-wg] Proposal regarding Orphaned Objects
- Next message (by thread): [db-wg] Proposal regarding Orphaned Objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]