> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-boun...@ietf.org] On Behalf Of
> internet-dra...@ietf.org
> Sent: Monday, September 26, 2016 1:04 PM
> To: i-d-annou...@ietf.org
> Subject: I-D Action: draft-hollenbeck-regext-rdap-openid-01.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-01.txt
>       Pages           : 22
>       Date            : 2016-09-26
> 
> 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/

This version adds a new section describing implementation status as described 
in RFC 7942. Please let me know if you have an implementation that you would 
like to have added. Note that I'll need *you* to provide the text to add.

Scott

_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to