Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-17.txt

["Hollenbeck, Scott" <[e-mail]>]

> -----Original Message-----
> From: regext <[e-mail]> On Behalf Of [e-mail]
> Sent: Thursday, August 18, 2022 9:19 AM
> To: [e-mail]
> Cc: [e-mail]
> Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-openid-17.txt
>
> Caution: This email originated from outside the organization. Do not click links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Registration Protocols Extensions WG of the
> IETF.
>
>         Title           : Federated Authentication for the Registration Data Access
> Protocol (RDAP) using OpenID Connect
>         Author          : Scott Hollenbeck
>   Filename        : draft-ietf-regext-rdap-openid-17.txt
>   Pages           : 40
>   Date            : 2022-08-18
>
> 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.

This version corrects a few outdated references and one error where a boolean true value was represented as a string. With these fixes, I believe the draft is finished and is ready for working group last call.

In the past we've thought that it might be prudent to hold off on completing this draft until ICANN processes focused on authenticated access to registration data ran to completion. It's now clear that those ICANN processes aren't focused on using RDAP, so I think it's best if we declare victory and move this document over the finish line.

Scott