Good Afternoon Ben,
This change was made as part of 1.109 release. We added that attribute into the redacted field
and removed it from the RDAP entity.
Email is considered to be personal data, so we must be consistent between our APIs and keep
it filtered in all of them. If an email address is returned, this is accounted agains a daily limit
according to the Acceptable Use Policy , so your IP will get blocked if you request too many objects
which have personal attributes like email.
We are open to discussion, so if there is an agreement in db-wg we will investigate how to include
personal data in the RDAP response.
Thanks
Miguel
On 4 Jan 2024, at 17:39, Ben Cartwright-Cox via db-wg <db-wg@ripe.net> wrote:Hi everybody,
I was just re-running some tests internally within bgp.tools and I've
noticed that the RDAP responses from RIPE no longer include the email
address of the person object. For example I used to (and expected) to
get the email address in the object for
https://rdap.db.ripe.net/entity/BC6775-RIPE, but it seems to have been
removed from the output at some point.
That does not appear to be a way to log in to authenticate
trustworthiness of RDAP responses, is there any other way to get
this information? I can see this information on the RIPE website (
https://apps.db.ripe.net/db-web-ui/lookup?source=ripe&key=BC6775-RIPE&type=person
) but I do not want to scrape that, and this information is incredibly
useful for helping users onboard ( with a trustworthy email address )
to services like bgp.tools.
Is this an intended change? Have I done something silly? All of the above ;) ?
By looking at the release info I can see it was added in November (#1333)
Thanks
Ben
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg