[regext] STD 95, RFC 9224 on Finding the Authoritative Registration Data Access Protocol (RDAP) Service
rfc-editor@rfc-editor.org Thu, 31 March 2022 23:09 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 71C573A1F90;
Thu, 31 Mar 2022 16:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248,
SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01,
URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id wKCCSgmVVftY; Thu, 31 Mar 2022 16:09:11 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [IPv6:2001:1900:3001:11::31])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 08CA03A1F7D;
Thu, 31 Mar 2022 16:09:11 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499)
id 54AE5AE92; Thu, 31 Mar 2022 16:09:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, regext@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20220331230910.54AE5AE92@rfcpa.amsl.com>
Date: Thu, 31 Mar 2022 16:09:10 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/hwE3GWbVdWPswJRbwDjcmjv9vvg>
Subject: [regext] =?utf-8?q?STD_95=2C_RFC_9224_on_Finding_the_Authoritati?=
=?utf-8?q?ve_Registration_Data_Access_Protocol_=28RDAP=29_Service?=
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 31 Mar 2022 23:09:18 -0000
A new Request for Comments is now available in online RFC libraries.
STD 95
RFC 9224
Title: Finding the Authoritative Registration Data
Access Protocol (RDAP) Service
Author: M. Blanchet
Status: Standards Track
Stream: IETF
Date: March 2022
Mailbox: Marc.Blanchet@viagenie.ca
Pages: 15
Obsoletes: RFC 7484
See Also: STD 95
I-D Tag: draft-ietf-regext-rfc7484bis-06.txt
URL: https://www.rfc-editor.org/info/rfc9224
DOI: 10.17487/RFC9224
This document specifies a method to find which Registration Data
Access Protocol (RDAP) server is authoritative to answer queries for
a requested scope, such as domain names, IP addresses, or Autonomous
System numbers. This document obsoletes RFC 7484.
This document is a product of the Registration Protocols Extensions Working Group of the IETF.
This is now an Internet 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
Association Management Solutions, LLC