[regext] I-D Action: draft-ietf-regext-rdap-openid-04.txt
internet-drafts@ietf.org Thu, 16 January 2020 12:30 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85D5612002E; Thu, 16 Jan 2020 04:30:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: regext@ietf.org
Message-ID: <157917783446.26183.11407313603587601326@ietfa.amsl.com>
Date: Thu, 16 Jan 2020 04:30:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/3u9JYzToiloX-gPBTfAJEXnncD8>
Subject: [regext] I-D Action: draft-ietf-regext-rdap-openid-04.txt
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2020 12:30:34 -0000
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-04.txt Pages : 25 Date : 2020-01-16 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-04 https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-openid-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-openid-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [regext] I-D Action: draft-ietf-regext-rdap-openi⦠internet-drafts