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

Alex Deacon alex at colevalleyconsulting.com
Fri Oct 25 21:30:21 UTC 2019

Hi Amr,

I would suggest you take a second look at TSG01 for the answer to many of
your questions.


Bottom line - RDAP (and the standard internet technologies it uses) is
easily updated to layer on standard security services that will provide
encryption, authentication and authorization.   In fact there already
exists an IETF internet-draft describing how to do it.


*Alex Deacon*
Cole Valley Consulting
alex at colevalleyconsulting.com

On Fri, Oct 25, 2019 at 6:15 AM Amr Elsadr <aelsadr at icannpolicy.ninja>

> 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
> _______________________________________________
> Gnso-epdp-team mailing list
> Gnso-epdp-team at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-epdp-team
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-epdp-team/attachments/20191025/86c6527b/attachment.html>

More information about the Gnso-epdp-team mailing list