Hi Bijal, I do not believe more data than is currently available should be made available. I suppose trying to filter fields that shouldn't contain personal data could be a good idea but I am not sure how practical that would be. If you remove all free text attributes other than org-name I guess you could do it. Like remove remarks, descr, etc. But I am not sure how feasible this is in practice. -Cynthia On Wed, Apr 14, 2021 at 3:10 PM Bijal Sanghani via db-wg <db-wg@ripe.net> wrote:
Dear colleagues,
As part of our work in the RIPE Database Requirements Task Force (DBTF), we are trying to understand if providing historical data is one of the requirements the RIPE Database must fulfil. Currently some attributes are filtered out to limit the exposure of unnecessary personal data. If providing historical data is a requirement the RIPE Database must fulfill, we will recommend the RIPE NCC to examine if additional filtering can be applied to limit further the unnecessary exposure of personal data in attributes that are not meant to contain personal data.
We are looking specifically for arguments pro or against this recommendation. We’ll then discuss each argument with the task force and make a decision.
Kind regards, Bijal on behalf of the DBTF