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
Thu May 7 13:32:20 CEST 2015
On Thu, 07 May 2015 00:01:21 +0100, Shane Kerr wrote: > > However, we know that some people who maintain the parent objects are > unable to correct the database. This is a problem both for those > maintainers and for anyone hoping for accurate information about the > network. > > We know there is a theoretical problem where someone might have network > information deleted from the RIPE database that they want to keep there. > We do not now if this is an actual problem. > > I remind the working group that if someone *does* have their network > deleted inappropriately, then the record can be re-created. Updating a > RIPE Database entry does not instantly de-peer people or the like. > > I'm quite happy with a dispute policy that works to always restore a > more-specific inetnum object in case of complaint by the former > maintainer of the object, and then lets any further resolution occur > using other means. That all makes sense to me. Thnaks, Shane. 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 ]