Subject: [regext] FW: I-D Action: draft-hollenbeck-regext-rdap-openid-06.txt

From: "Hollenbeck, Scott" <[email-masked]>
Date: Tue, 17 Apr 2018 16:13:03 +0000

> -----Original Message-----
> From: I-D-Announce [mailto:[email-masked]] On Behalf Of
> [email-masked]
> Sent: Tuesday, April 17, 2018 12:08 PM
> To: [email-masked]
> Subject: [EXTERNAL] I-D Action: draft-hollenbeck-regext-rdap-openid-06.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : Federated Authentication for the Registration
> Data Access Protocol (RDAP) using OpenID Connect
>         Author          : Scott Hollenbeck
>       Filename        : draft-hollenbeck-regext-rdap-openid-06.txt
>       Pages           : 25
>       Date            : 2018-04-17
>
> Abstract:
>    The Registration Data Access Protocol (RDAP) provides "RESTful" web
>    services to retrieve registration metadata from domain name and
>    regional internet registries.  RDAP allows a server to make access
>    control decisions based on client identity, and as such it includes
>    support for client identification features provided by the Hypertext
>    Transfer Protocol (HTTP).  Identification methods that require
>    clients to obtain and manage credentials from every RDAP server
>    operator present management challenges for both clients and servers,
>    whereas a federated authentication system would make it easier to
>    operate and use RDAP without the need to maintain server-specific
>    client credentials.  This document describes a federated
>    authentication system for RDAP based on OpenID Connect.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-openid/

My team has completed preliminary testing of the OAuth 2.0 device flow with and can confirm that it works using code developed by Google, so a description of that method of authorization for UI-constrained devices has been added to the draft. We're planning on doing more testing when the device flow document pops out of the RFC Editor queue and the flow is implemented by additional identity providers.

Scott