[regext] Fwd: I-D Action: draft-ietf-regext-rdap-reverse-search-26.txt
Mario Loffredo <mario.loffredo@iit.cnr.it> Mon, 13 November 2023 14:33 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 BB84EC1519AA for <regext@ietfa.amsl.com>; Mon, 13 Nov 2023 06:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 psDV1-6wDWmJ for <regext@ietfa.amsl.com>; Mon, 13 Nov 2023 06:33:27 -0800 (PST)
Received: from mx5.iit.cnr.it (mx5.iit.cnr.it [146.48.58.12]) (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 9B95CC15C287 for <regext@ietf.org>; Mon, 13 Nov 2023 06:33:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.iit.cnr.it (Postfix) with ESMTP id DB3C1C0582 for <regext@ietf.org>; Mon, 13 Nov 2023 15:33:22 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mx5.iit.cnr.it
Received: from mx5.iit.cnr.it ([127.0.0.1]) by localhost (mx5.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vP6gyZnV3cQH for <regext@ietf.org>; Mon, 13 Nov 2023 15:33:20 +0100 (CET)
X-Relay-Autenticated: yes
Content-Type: multipart/alternative; boundary="------------2d0bpatgTAH3daLhJaLOwPXy"
Message-ID: <d5eebab9-8dd9-4a91-864a-c6526cc13cec@iit.cnr.it>
Date: Mon, 13 Nov 2023 15:28:37 +0100
Mime-Version: 1.0
References: <169988563758.63526.16966302943028421511@ietfa.amsl.com>
Content-Language: it
To: "regext@ietf.org" <regext@ietf.org>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
In-Reply-To: <169988563758.63526.16966302943028421511@ietfa.amsl.com>
X-Forwarded-Message-Id: <169988563758.63526.16966302943028421511@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/iYQ5KK5BhdKa5LdlhV3kRYg6zQE>
Subject: [regext] Fwd: I-D Action: draft-ietf-regext-rdap-reverse-search-26.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, 13 Nov 2023 14:33:31 -0000
Hi everyone, just removed the "Description" field from the Reverse Search Mapping registry and both "Change Log" and "Implementation Status" section. No action from IANA is needed. Apart from possible text cleaning, think we are done. Best, Mario -------- Messaggio Inoltrato -------- Oggetto: [regext] I-D Action: draft-ietf-regext-rdap-reverse-search-26.txt Data: Mon, 13 Nov 2023 06:27:17 -0800 Mittente: internet-drafts@ietf.org Rispondi-a: regext@ietf.org A: i-d-announce@ietf.org CC: regext@ietf.org Internet-Draft draft-ietf-regext-rdap-reverse-search-26.txt is now available. It is a work item of the Registration Protocols Extensions (REGEXT) WG of the IETF. Title: Registration Data Access Protocol (RDAP) Reverse Search Authors: Mario Loffredo Maurizio Martinelli Name: draft-ietf-regext-rdap-reverse-search-26.txt Pages: 20 Dates: 2023-11-13 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 datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-reverse-search-26 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-reverse-search-26 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
- [regext] I-D Action: draft-ietf-regext-rdap-rever… internet-drafts
- [regext] Fwd: I-D Action: draft-ietf-regext-rdap-… Mario Loffredo