[TSG-Access-RD] Text Added

Andrew Newton andy at hxr.us
Tue Feb 19 15:32:46 UTC 2019


On Mon, Feb 18, 2019 at 10:31 PM Jorge Cano <jcano at nic.mx> wrote:

> Dear all,
>
> I read the document and pretty much agree with it, but have a couple of
> questions.
>
> 1. In the Actor Models section, at the mapping of the organizational
> entities to the actors, the point 5 defines the ICANN RDAP Proxy as a
> Relying Party. Shouldn’t the ICANN RDAP Proxy be defined as a Resource
> Server?
>
> From RFC 6749 “The OAuth 2.0 Authorization Framework” (
> https://www.rfc-editor.org/rfc/rfc6749.txt)
> Resource server: The server hosting the protected resources, capable of
> accepting and responding to protected resource requests using access tokens.
>
> And from “OpenID Connect Core 1.0 Specification” (
> https://openid.net/specs/openid-connect-core-1_0.html)
> Relying Party (RP): OAuth 2.0 Client application requiring End-User
> Authentication and Claims from an OpenID Provider.
>
> Isn’t this last definition better suited for the ICANN RDAP Access Service?
>
>

Jorge,

I believe you are correct. I'll make the change. Thanks for double checking
this.

-andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tsg-access-rd/attachments/20190219/a6801934/attachment.html>


More information about the TSG-Access-RD mailing list