[TSG-Access-RD] [Ext] Re: Bulk Data, Bulk Query, WhoWas and Charter scope

[Hollenbeck, Scott]

> -----Original Message-----
> From: Andrew Newton <andy at hxr.us>
> Sent: Friday, January 4, 2019 12:46 PM
> To: Hollenbeck, Scott <shollenbeck at verisign.com>
> Cc: francisco.arias at icann.org; tsg-access-rd at icann.org
> Subject: [EXTERNAL] Re: Re: [TSG-Access-RD] [Ext] Re: Bulk Data, Bulk Query,
> WhoWas and Charter scope
>
> On Fri, Jan 4, 2019 at 12:09 PM Hollenbeck, Scott
> <shollenbeck at verisign.com> wrote:
> >
> >
> > As I understand it, Francisco (I believe Ram also mentioned it in our first
> call) is describing an operational model in which ICANN will operate an RDAP
> service that is intended to be the public-facing source of information for
> gTLD-related non-public data. Registries and registrars will be expected to
> provide a public-facing service for public data, and some form of non-public
> (details TBD; perhaps with client authentication, for example) service for
> ICANN's use to retrieve non-public data. Clients will need to submit two
> queries to form a complete RDAP response: one must be sent to ICANN's
> service for non-public data, and the second must be sent to the appropriate
> registry/registrar for public data. Assuming I've described it correctly, I'm
> trying to understand if this model is a suggestion or a requirement.
>
>
> Ah! Now I understand.
>
> But I disagree. :)
> I client seeking non-public data would use the non-public data query
> mechanism and the answer from that should contain both non-public data
> and public data. Why would it not?

I believe Francisco mentioned that ICANN does not want/intend to provide a public-facing interface for queries that will return public data.

Scott