I am also curious. Theo, what is the reasoning?
It would be logical that a response to a query would contain both the public and non-public information. There is no harm in providing the public info at the same time. And there is a crucial benefit: no one wants race conditions, in which the public set and the non-public set are not synched and people cannot see the state of the entire set of data at the point in time. That discontinuity was something that the Thick WHOIS PDP found undesirable, and that PDP solved for.
All best,
--Greg
From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> On Behalf Of Mark Svancarek (CELA) via Gnso-epdp-team
Sent: Thursday, July 25, 2019 4:30 PM
To: theo geurts <gtheo@xs4all.nl>; gnso-epdp-team@icann.org
Subject: Re: [Gnso-epdp-team] RrSG Response to LEA1 use case
Theo, can you clarify why SSAD is limited to on non-public data delivery?
From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> On Behalf Of theo geurts
Sent: Tuesday, July 23, 2019 12:17 PM
To: gnso-epdp-team@icann.org
Subject: [Gnso-epdp-team] RrSG Response to LEA1 use case
Countless of hours of hard work are attached ;)
Best,
Theo Geurts CIPP/E
Privacy & GRC Officer | Realtime Register B.V.
Ceintuurbaan 32A
8024 AA - ZWOLLE - The Netherlands
T: +31.384530759
F: +31.384524734