Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect
draft-ietf-regext-rdap-openid-27

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, Zaid AlBanna <zalbanna@verisign.com>, draft-ietf-regext-rdap-openid@ietf.org, regext-chairs@ietf.org, regext@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com, zalbanna@verisign.com
Subject: Protocol Action: 'Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect' to Proposed Standard (draft-ietf-regext-rdap-openid-27.txt)

The IESG has approved the following document:
- 'Federated Authentication for the Registration Data Access Protocol
   (RDAP) using OpenID Connect'
  (draft-ietf-regext-rdap-openid-27.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions Working
Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-openid/

Ballot Text

Technical Summary

   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.

Working Group Summary

   Broad agreement was reached. There have been 7 expressions of
   support (not counting the editors or document shepherd) and no
   objections.

   No appeal has been threatened.

Document Quality

   Section 10 contains implementation status.

   IANA Considerations appear to be correct and clear.

Personnel

   The Document Shepherd for this document is Zaid AlBanna. The Responsible
   Area Director is Murray Kucherawy.

RFC Editor Note