> -----Original Message-----
> From: I-D-Announce <[email protected]> On Behalf Of
> [email protected]
> Sent: Monday, August 19, 2019 7:18 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [EXTERNAL] I-D Action: draft-ietf-regext-rdap-openid-03.txt
>
>
> 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-03.txt
>       Pages           : 25
>       Date            : 2019-08-19
>
> 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-ietf-regext-rdap-openid/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-regext-rdap-openid-03
> https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-openid-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-openid-03

This version includes an updated description and reference to RFC 8628 ( OAuth 
2.0 device flow/authorization grant), which was published last week. I had 
previously referenced the Internet-Draft.

Scott

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to