[Gnso-epdp-team] Accreditation Building Block - Principle "u" concerning RDAP Identifying Accredited SSAD Users

[Anderson, Marc]

I agree with the points Amr is raising.  I appreciate Marika’s response but I think it’s clear that the current bracketed placeholder language is confusing and at this time a distraction.  I suggest replacing the Technical capabilities section (U and V) with placeholder language along the lines of Marika’s email.



Placeholder – EPDP to consider (from the charter) – How can RDAP, that is technically capable, allow Registries/Registrars to accept accreditation tokens and purpose for the query? Once accreditation models are developed by the appropriate accreditors and approved by the relevant legal authorities, how can we ensure that RDAP is technically capable and is ready to accept, log and respond to the accredited requestor’s token?



Best,

Marc











From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org> On Behalf Of Marika Konings
Sent: Friday, October 25, 2019 9:51 AM
To: Amr Elsadr <aelsadr at icannpolicy.ninja>; gnso-epdp-team at icann.org
Subject: [EXTERNAL] Re: [Gnso-epdp-team] Accreditation Building Block - Principle "u" concerning RDAP Identifying Accredited SSAD Users



Amr, please note that this principle was put in brackets as it was recognized during yesterday’s meeting that this one needed further work, if it is to be included at all.



As a reminder, this section was originally introduced in an attempt to be responsive to the following charter question: “How can RDAP, that is technically capable, allow Registries/Registrars to accept accreditation tokens and purpose for the query? Once accreditation models are developed by the appropriate accreditors and approved by the relevant legal authorities, how can we ensure that RDAP is technically capable and is ready to accept, log and respond to the accredited requestor’s token?“.



Hopefully someone more technically versed in RDAP can respond to your questions.



Best regards,



Caitlin, Berry and Marika



From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org<mailto:gnso-epdp-team-bounces at icann.org>> on behalf of Amr Elsadr <aelsadr at icannpolicy.ninja<mailto:aelsadr at icannpolicy.ninja>>
Reply-To: Amr Elsadr <aelsadr at icannpolicy.ninja<mailto:aelsadr at icannpolicy.ninja>>
Date: Friday, October 25, 2019 at 07:15
To: "gnso-epdp-team at icann.org<mailto:gnso-epdp-team at icann.org>" <gnso-epdp-team at icann.org<mailto:gnso-epdp-team at icann.org>>
Subject: [Gnso-epdp-team] Accreditation Building Block - Principle "u" concerning RDAP Identifying Accredited SSAD Users



Hi,



I’m having trouble understanding why one of the principles in the Accreditation Building Block requires RDAP to be technically capable of identifying SSAD Accredited Users. This is included in sub-point “u” in the Accreditation Building Block<https://docs.google.com/document/d/1-90NgBnkZt8mRL2acJUPOwoIkx5clvXlCaCC3RAOGWU/edit>.



Isn’t SSAD meant to be the tool by which 3rd Parties will be requesting disclosure of redacted Registration Data? Accreditation of users of SSAD provides “benefits” to its users, which are specific to SSAD itself. SSAD in turn, will interface with RDAP to provide disclosure of requested redacted data following a successful conclusion to a disclosure request. I’m failing to see how requiring RDAP to be able to identify accredited users assists this in any way.



If we do proceed with this principle/recommendation, wouldn’t that require significant changes being made to the RDAP profile? RDAP will need to include all domain name registration data, as well as all the data (or at least access to it) necessary to identify all SSAD-accredited users. I’m guessing this could be done by either duplicating the database of SSAD-accredited users, or allow the RDAP interface to enable RDAP operators to look up information on accredited users in SSAD.



The only benefit I can think of in doing this would be to enable 3rd Parties accredited in SSAD to either submit their disclosure requests via SSAD, or directly via a Contracted Party allowing it to confirm that the Requestor is accredited. But that isn’t what we’ve agreed to do, is it?



If a 3rd Party would like to seek disclosure of redacted Registration Data directly via a (for example) Registrar, then it should do so according to the Registrar’s own procedures. The Registrar should then proceed to evaluate the disclosure request based on its own evaluation of the request, and not based on any ICANN Policies we are developing concerning a standardized system.



I’m guessing that adding this feature to RDAP will be both costly and burdensome, and absent justification to do so, should likely not be done at all. Unless I’m missing something, of course, which I very well might be.



Thanks.



Amr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-epdp-team/attachments/20191025/f1348eff/attachment-0001.html>