I would like to bring to the group's attention the Historical RDAP protocol standard draft presented by Tom Harrison to the REGEXT Working Group during IETF 99 last July: https://datatracker.ietf.org/doc/draft-ellacott-historical-rdap/?include_tex... https://datatracker.ietf.org/meeting/99/materials/slides-99-regext-5-history... Its implementation is under active development at APNIC and you can find an experimental UI to the service at https://www.apnic.net/static/whowas-ui/ Some more detail: https://www.apnic.net/about-apnic/whois_search/whowas/ Cheers, Raf den is via db-wg <db-wg@ripe.net> writes:
Colleagues
The DB WG co-chairs would now like to address this issue. There was some discussion on the mailing list in May to July of 2016.
In brief the issue is that the current history mechanism has an arbitrary design constraint that only the history of currently existing objects can be seen. This may also not be complete if the object has been deleted and re-created.
The problem definition has not yet been finalised. Also there was some discussion about the reasons for wanting more historical information being made available for resource objects (and possibly some other object types).
We would therefore like to ask anyone with concerns about historical data to please review what was said last year and express support or otherwise and perhaps add some reasoning as to why more data is needed.
cheers denis co-chair DB WG