[db-wg] improve --list-sources query to retain history
- Previous message (by thread): [db-wg] improve --list-sources query to retain history
- Next message (by thread): [db-wg] Implementation plan and time line for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Thu Aug 30 16:11:22 CEST 2018
Hi Erik, the current version history implementation does not return the deleted object history to protect the personal data of a previous resource holder. There has been previous discussion by the Working Group to change this, and there is a work item in progress: NWI-2 "displaying history for DB objects where available". Regards Ed Shryane RIPE NCC > On 28 Aug 2018, at 09:27, Erik Bais via db-wg <db-wg at ripe.net> wrote: > > If the WG is going to look at improving the --list-sources code base, I have something that I would love to see on the wish list to be implemented.. > > Maintaining history (upto the point where a prefix is leaving the RIPE DB, due to an inter-rir transfer. ) is helpful to see who the previous holder was or where the prefix came from. > > This is particular the case with Legacy prefixes that are being split up.. as it is current practise to delete the parent prefix after a prefix split and transfer. > Once the parent is deleted, you can't list or request the history of the parent prefix anymore. > > If the historic --list-versions and --show-version could be preserved somehow (on the original prefix size.. instead of them being deleted..), that would be very helpful. > > Regards, > Erik Bais >
- Previous message (by thread): [db-wg] improve --list-sources query to retain history
- Next message (by thread): [db-wg] Implementation plan and time line for NWI5 - Out-of-region ROUTE(6) objects and removal of ASN authorisation for ROUTE(6) object creation.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]