RFC 9910 on Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search
rfc-editor@rfc-editor.org Thu, 08 January 2026 00:13 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id BC946A46FA55; Wed, 7 Jan 2026 16:13:32 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 8D412C000CC0; Wed, 7 Jan 2026 16:13:32 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9910 on Registration Data Access Protocol (RDAP) Regional Internet Registry (RIR) Search
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260108001332.8D412C000CC0@rfcpa.rfc-editor.org>
Date: Wed, 07 Jan 2026 16:13:32 -0800
Message-ID-Hash: 2W67SJ2IWZA2LQXRPK2ME6Y5BSDWKZSR
X-Message-ID-Hash: 2W67SJ2IWZA2LQXRPK2ME6Y5BSDWKZSR
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, regext@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/WUV7km6zzNs4CofxZulACGs7Wz8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9910
Title: Registration Data Access Protocol (RDAP)
Regional Internet Registry (RIR) Search
Author: T. Harrison,
J. Singh
Status: Standards Track
Stream: IETF
Date: January 2026
Mailbox: tomh@apnic.net,
jasdips@arin.net
Pages: 26
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-regext-rdap-rir-search-19.txt
URL: https://www.rfc-editor.org/info/rfc9910
DOI: 10.17487/RFC9910
The Registration Data Access Protocol (RDAP) is used by Regional
Internet Registries (RIRs) and Domain Name Registries (DNRs) to
provide access to their resource registration information. The core
specifications for RDAP define basic search functionality, but there
are various search options related to IP addresses, IP prefixes, and
Autonomous System Numbers (ASNs), which are provided by RIRs via
their WHOIS services, but for which there is no corresponding RDAP
functionality. This document extends RDAP to support those search
options.
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-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team