IETF Logo Mail Archive

[regext] Fwd: New Version Notification for draft-ietf-regext-rdap-reverse-search-16.txt

Mario Loffredo <mario.loffredo@iit.cnr.it> Mon, 21 November 2022 15:43 UTC

Return-Path: <mario.loffredo@iit.cnr.it>
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 F1227C14CEE0 for <regext@ietfa.amsl.com>; Mon, 21 Nov 2022 07:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 h7iy_RhC_8Uf for <regext@ietfa.amsl.com>; Mon, 21 Nov 2022 07:43:34 -0800 (PST)
Received: from iit.cnr.it (mx4.iit.cnr.it [146.48.58.11]) by ietfa.amsl.com (Postfix) with ESMTP id DED26C14F745 for <regext@ietf.org>; Mon, 21 Nov 2022 07:43:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.iit.cnr.it (Postfix) with ESMTP id 07882B80AC2; Mon, 21 Nov 2022 16:43:31 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mx4.iit.cnr.it
Received: from iit.cnr.it ([127.0.0.1]) by localhost (mx4.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJwDZEsI3bPh; Mon, 21 Nov 2022 16:43:27 +0100 (CET)
Received: from [192.168.16.66] (sa.nic.it [192.12.193.247]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by mx4.iit.cnr.it (Postfix) with ESMTPSA id 63D84B80AB6; Mon, 21 Nov 2022 16:43:27 +0100 (CET)
Content-Type: multipart/alternative; boundary="------------Wm0ElgKA6yZk8rs8hmaxOICR"
Message-ID: <3cf24684-e89c-2565-e2ae-be797359ebc4@iit.cnr.it>
Date: Mon, 21 Nov 2022 16:40:28 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
References: <166904400845.63178.12808486915076028699@ietfa.amsl.com>
To: "regext@ietf.org" <regext@ietf.org>, "pawel.kowalik@ionos.com" <pawel.kowalik@ionos.com>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
In-Reply-To: <166904400845.63178.12808486915076028699@ietfa.amsl.com>
X-Forwarded-Message-Id: <166904400845.63178.12808486915076028699@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/JQlZpxZzu6a3nvnx3oizOoawyRw>
Subject: [regext] Fwd: New Version Notification for draft-ietf-regext-rdap-reverse-search-16.txt
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 21 Nov 2022 15:43:38 -0000

Hi all,

this new version addresses last Pawel's feedback.

With regard to the registration of the reverse search properties, I have 
opted for adding entries in the RDAP JSON Values registry rather than 
defining an ad-hoc registry.

That is because servers must include the reverse search properties they 
support in a specific RDAP help response extension.

Therefore, some JSON values related to the pre-defined properties must 
be included in that registry anyway.


Best,

Mario



-------- Messaggio Inoltrato --------
Oggetto: 	New Version Notification for 
draft-ietf-regext-rdap-reverse-search-16.txt
Data: 	Mon, 21 Nov 2022 07:20:08 -0800
Mittente: 	internet-drafts@ietf.org
A: 	Mario Loffredo <mario.loffredo@iit.cnr.it>, Maurizio Martinelli 
<maurizio.martinelli@iit.cnr.it>




A new version of I-D, draft-ietf-regext-rdap-reverse-search-16.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.

Name: draft-ietf-regext-rdap-reverse-search
Revision: 16
Title: Registration Data Access Protocol (RDAP) Reverse search capabilities
Document date: 2022-11-21
Group: regext
Pages: 17
URL: 
https://www.ietf.org/archive/id/draft-ietf-regext-rdap-reverse-search-16.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-reverse-search
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-reverse-search-16

Abstract:
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.



The IETF Secretariat

v2.23.0 | Report a Bug | By Email