We are looking into that one and others, thanks for the reminder, seems I missed Mark's question due the usual ICANN "list flood", my bad. Best, Theo On 29-7-2019 21:07, Greg Aaron wrote:

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 <mailto: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 <mailto: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

U: www.realtimeregister.com <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.realtimeregister.com&data=02%7C01%7Cmarksv%40microsoft.com%7C38ba87e17dd942a7b18d08d70fa25f43%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636995062692468874&sdata=f8BLP9U8Iwu2jHrboqUyzu1hCES2gmepoVtTKcOdWqo%3D&reserved=0>

E: legal@realtimeregister.com <mailto:legal@realtimeregister.com>