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/[email protected]/
[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 ]
Niall O'Reilly
niall.oreilly at ucd.ie
Tue May 5 10:25:05 CEST 2015
On Mon, 04 May 2015 21:03:20 +0100, denis walker wrote: > > In a neat and perfect world where everyone had all documentation for > all contracts, deals, agreements that have ever been made regarding > address space, then I agree there is no problem giving out these > permissions as everything can be put right if mistakes are made. > > However, we don't all live in that perfect world. There have been > examples where a block of addresses was given to an organisation many > years ago to be divided up and distributed to other organisations. But > sometimes that parent block still exists in the RIPE Database and is > registered with an organisation. If we give this organisation the > reclaim permissions 'by default' they can delete anything they want. Thanks for explaining, Denis and Andrea. Without knowing whether the division and distribution was intended as a sub-allocation or rather as a transfer, it's not possible (for the RIPE NCC or for another external observer) to be sure whether control over the parent block as an aggregate reasonably "belongs to" the registered organization. ATB Niall
- 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 ]