A new Request for Comments is now available in online RFC libraries.
RFC 9560
Title: Federated Authentication for the Registration
Data Access Protocol (RDAP) Using OpenID
Connect
Author: S. Hollenbeck
Status: Standards Track
Stream: IETF
Date: April 2024
Mailbox: shollenb...@verisign.com
Pages: 40
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-regext-rdap-openid-27.txt
URL: https://www.rfc-editor.org/info/rfc9560
DOI: 10.17487/RFC9560
The Registration Data Access Protocol (RDAP) provides
Representational State Transfer (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 document is a product of the Registration Protocols Extensions Working
Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
