%% You should probably cite draft-ietf-regext-rdap-openid instead of this I-D. @techreport{hollenbeck-regext-rdap-openid-10, number = {draft-hollenbeck-regext-rdap-openid-10}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-openid/10/}, author = {Scott Hollenbeck}, title = {{Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect}}, pagetotal = 26, year = 2018, month = aug, day = 29, 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.}, }