[rfc-dist] RFC 9536 on Registration Data Access Protocol (RDAP) Reverse Search

rfc-editor@rfc-editor.org Thu, 11 April 2024 16:07 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB66C14F6A8; Thu, 11 Apr 2024 09:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.65
X-Spam-Level:
X-Spam-Status: No, score=-6.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhZHJ8KF1oX0; Thu, 11 Apr 2024 09:07:54 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC808C14F699; Thu, 11 Apr 2024 09:07:54 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9AD7551B905; Thu, 11 Apr 2024 09:07:54 -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: <20240411160754.9AD7551B905@rfcpa.amsl.com>
Date: Thu, 11 Apr 2024 09:07:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/-k0ZAmyH_EqysPLprvSecnY4gIg>
Subject: [rfc-dist] RFC 9536 on Registration Data Access Protocol (RDAP) Reverse Search
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 16:07:58 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9536

        Title:      Registration Data Access Protocol (RDAP) 
                    Reverse Search 
        Author:     M. Loffredo,
                    M. Martinelli
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2024
        Mailbox:    mario.loffredo@iit.cnr.it,
                    maurizio.martinelli@iit.cnr.it
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-rdap-reverse-search-25.txt

        URL:        https://www.rfc-editor.org/info/rfc9536

        DOI:        10.17487/RFC9536

The Registration Data Access Protocol (RDAP) does not include query
capabilities for finding the list of domains related to a set of
entities matching a given search pattern.  Considering that an RDAP
entity can be associated with any defined object class and other
relationships between RDAP object classes exist, a reverse search can
be applied to other use cases besides the classic domain-entity
scenario.  This document describes an RDAP extension that allows
servers to provide a reverse search feature based on the relationship
defined in RDAP between an object class for search and any related
object class.  The reverse search based on the domain-entity
relationship is treated as a particular case.

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
Association Management Solutions, LLC