Return-Path: 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 B3251C151532 for ; Tue, 16 Jul 2024 05:18:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.095 X-Spam-Level: X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_HTML_ATTACH=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=apnic.net 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 joxUOuIEgulx for ; Tue, 16 Jul 2024 05:17:58 -0700 (PDT) Received: from AUS01-SY4-obe.outbound.protection.outlook.com (mail-sy4aus01on2126.outbound.protection.outlook.com [40.107.107.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91FD8C151998 for ; Tue, 16 Jul 2024 05:17:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=gK9RqfEiAQAeJmyWh5VVF/oBltRdpY8jv+dcPDF8JxvdL4DVF8mxI2DGwUuo3s3x6PeDuoOKDKeAKilMI9usMiWGCxcZNS/nXfY979biofieafueTBC9SLK6eD3ytWdt3pe+576jrsHu2h8qa0AQ92cUPsYauEz0+1PUtmj9L69tfNLuDDYwKWR3+UDuZujG8/t/GZ+SsZuE+jRN5c2FN9hrSXbABiZFX7v0bVS0MG/X69nGeWyXsf3PjNEcBwTiP9HwY1zvJPote+7uz3ijpgtqmBx8Hle1nALFFtdLZnk1FVcIENmqMolGZI/2ddskX/VDdMZLQI6s2eiFnsbmJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=szsdrFYFHDliesaKWVfweDWiVi55ReAGPFyZ3JBOaHs=; b=itShsiyuxW5a/1UzYZeXCL4E1uyHQjw88cZ2mfqcCiwMGGMi/eom6KJ+kjjzXh4T3ZLU7Xnn0yuHyYEkNkNhWhGacivEOrbhU5VIeEiDrS+E1CRNJmQYStIDQhCdQe8uOkGLxsgn7LuxU6vynlTzGPZTuUaviI6luJWqqP8dURrmAYx8OpZf26JPP3RZztkiOeKiphrINcnp4k/f5qrPQf9PwIcpl7gnxusrbU4RpIk5hnleybCPiFg0JPIg6cVsN1itSjoHl3OSitBxVvNFrEPTgK0Q8ChcbljDnuaiBVFCPJLpTvZWsnFtCr2SWekX+rDw1vBiD1X4/NCMxX9Rjg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=apnic.net; dmarc=pass action=none header.from=apnic.net; dkim=pass header.d=apnic.net; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=szsdrFYFHDliesaKWVfweDWiVi55ReAGPFyZ3JBOaHs=; b=Fz/fYXTi7XnaSUWuzWby8Al353aLJP7RF6UVo3G2ubEcGyAI7rpibMxclG3c2m4kymjuI3I/kum7hTwKpRU4mA4RYTA1TapWItkX9BPkziJGF9bZajpoF1GTpN888u2p0sTqeM6s9A/U0nzwZz3ZtiECuCiFwKbCJDs8d1STGKw= Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=apnic.net; Received: from SY7P282MB4761.AUSP282.PROD.OUTLOOK.COM (2603:10c6:10:273::5) by SY4P282MB3892.AUSP282.PROD.OUTLOOK.COM (2603:10c6:10:194::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7762.29; Tue, 16 Jul 2024 12:17:52 +0000 Received: from SY7P282MB4761.AUSP282.PROD.OUTLOOK.COM ([fe80::8ec3:ea17:ca08:65b5]) by SY7P282MB4761.AUSP282.PROD.OUTLOOK.COM ([fe80::8ec3:ea17:ca08:65b5%7]) with mapi id 15.20.7762.027; Tue, 16 Jul 2024 12:17:52 +0000 Date: Tue, 16 Jul 2024 22:17:50 +1000 From: Tom Harrison To: "Hollenbeck, Scott" Message-ID: Mail-Followup-To: "Hollenbeck, Scott" , "galvin@elistx.com" , "regext@ietf.org" References: Content-Type: multipart/mixed; boundary="EYvWa/gZiApa8hQU" Content-Disposition: inline In-Reply-To: X-ClientProxiedBy: SY5PR01CA0108.ausprd01.prod.outlook.com (2603:10c6:10:246::22) To SY7P282MB4761.AUSP282.PROD.OUTLOOK.COM (2603:10c6:10:273::5) MIME-Version: 1.0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: SY7P282MB4761:EE_|SY4P282MB3892:EE_ X-MS-Office365-Filtering-Correlation-Id: a799073f-2e9f-4d8b-2cd4-08dca5915076 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0;ARA:13230040|376014|1800799024|366016|2613699012; X-Microsoft-Antispam-Message-Info: =?us-ascii?Q?lUF1bGd0aTn4RjPmCbDCTPKl7kvlNWzliDXkeGZgUXEz+onsaDAYVPY85Sim?= =?us-ascii?Q?SWjjNtZbvH+gWoLxPcYYKKBaz0qZt5oLcIDFkWyDv5ut4QyDNBdYK8J+EaZu?= =?us-ascii?Q?Lv/XMTSk8/WJgjaqdWfWCynNIWfBkA/1FZPECIH8LOWKFuiZdGzXKXJDl2b3?= =?us-ascii?Q?Wptblw2wXlpjR6wBujT/Q4pzJdJ77QgQtBIQqbgSchfcYSULRDq8q7mE/IHo?= =?us-ascii?Q?Gp5jj/2ioGVImD9cVjeQTbSNyKqpH+JjYY4sS8dvmnYwckjVTYg6IP+rbJrj?= =?us-ascii?Q?i0m/s7IYLTDWxvNtWBssoClCoEY/5547ltLX6jBEIwCEN3hWy96NlD/c5Upn?= =?us-ascii?Q?6h8kxomMeHCnF7q2H7C4IF0qRwIb6Yqr3ka3dUoFNUb4NbpjTAeudqowG9jM?= =?us-ascii?Q?RRls+Iw4S3bHAsOUqzmLhuXyFOVTpTanRxgQDSmnILASb07kP4ilHkL3HLka?= =?us-ascii?Q?MCvQ1R9VulNQmv522SvFDHr2FbEpT5ZdZbp8jRN4LzYMhPBV6jGpiu+x4Vb4?= =?us-ascii?Q?/5Wowol6xzTmieOeze1oaCsfkNnp6fytk5UTDcWhMcj1e2ma8p4gY9lDfCzE?= =?us-ascii?Q?u3jIaJqEM2LyXYH38/qOc/ze+xFCScXl7987VAEm+xZ1KRgxm2somhOjqGlz?= =?us-ascii?Q?oH80GyDs0k4pwVhERHvM6+eKKAAE+N0NU1MH7Ww+RDdkHUQJWAX0CcjtuZJ4?= =?us-ascii?Q?OHAQgoyLnSac3A+F2M1TS1ZWm6llvzciSXA1YXcxDFMEgPJwfdumJ3Htrf/p?= =?us-ascii?Q?PxwiCV+35+CJC5vLbb45N+btzCHNjaevuKaJ0iwnE9KCV6QexIyCf3Ag396Z?= =?us-ascii?Q?XzUEgnnIIS8mVegfgSny3Mn4RkV7qPCkX46M+neIA6I38yODBDD399VghqAr?= =?us-ascii?Q?0viVkRs8xeyXmkHawCal2aoRr99TIvNet09WfbmWWh0IYbJ33H1kIhCu8NGz?= =?us-ascii?Q?nWyrDTYa/D+2r1UBkA93q/Z+74dTA4xM4libbfJ0HPauc9ljiIcDdVz6/AVy?= =?us-ascii?Q?LyZoKlJge8XJhxHlfTZGBfX/891gizbeMSa/pUp7oZqdgBBQW7Vvin2gQzPG?= =?us-ascii?Q?vF/gQgcLz6dRrOPeVe9S2Gz31y0KzPLPfNicx3GTO9r98dSZdDTj8J5QPlf4?= =?us-ascii?Q?kH/xUToCIldy2hk6L+or5z6XBE2EPHlhVc+XyqVMt5WeocG7WwbbGm0cPP+u?= =?us-ascii?Q?EjY2I0ltZvX/4+bbBkg7fP0k5HIbjjkvksqT4r2JoNAqPfm1D0/7pjxLdZLG?= =?us-ascii?Q?u6ix6Qu9SiHoyEIpxqKjzDslEf21QRK3EVmPpFAHbzkoST1Eer8DmB/8YGhn?= =?us-ascii?Q?ie8=3D?= X-Forefront-Antispam-Report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:SY7P282MB4761.AUSP282.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(376014)(1800799024)(366016)(2613699012);DIR:OUT;SFP:1102; X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1 X-MS-Exchange-AntiSpam-MessageData-0: =?us-ascii?Q?hi+zyUYBirlZLRrMO3bvJTviVM3+MnJllz3WadEwndIXRxiypwALf3N16it2?= =?us-ascii?Q?i04RhYvtKHu1hf2CPZAOQ1HiIJSRjKxD9z69DD0UFAGjYfuHH8bUmvPtT4Mk?= =?us-ascii?Q?509RYUWkKKVAxlzEGf2SNBxxHZ4wSm18nZPQ7OwxGtJzkKab9k7hjh547Kcd?= =?us-ascii?Q?65sl0KQ2I9MAePGAnntJHrb5yDoAz75QPh/D0dG+MChFWQ2wg5SvtoGzjTjC?= =?us-ascii?Q?M1qYd5h+82dcnXvAhO43J1QA58ga4Swi01Ewt+8XtZ95ZTwWos+3FwhFLk3Q?= =?us-ascii?Q?mgiUGeynzZz96koGkUBc+fWG4TvfbO4h63hIGSm+5Mw4aLUKa/Rx2QDurrR+?= =?us-ascii?Q?vKSvYczfrAHyM+bB4siBDjnSHLmDG4+eO09pQpShcrTYvHKsjILk7UeAx7BQ?= =?us-ascii?Q?+C0fXsBvoL8z3mVrpPLXqlac+Raciy1OnDmgxkmA6/kwIE40bP5MoYhs3wk2?= =?us-ascii?Q?TYNtf7wPc0m2s3Ni0oIVkLD34utlThtXircuJo38+ZRG/xrAPXxsITPy8PaL?= =?us-ascii?Q?hf9bKSh+eDz90JHfKivNAs1W8ibhbrkXsi+c6a+G9F9LGA9MzBmjqHXncPWv?= =?us-ascii?Q?8XRmMbPyO1xPM0exFggqA5sIwz0iQ+2YMD3D509rn5jA1zBaiAZpJOTsbP7c?= =?us-ascii?Q?UC0PaL5xGBz5Z24nSj27ywfwi1oKi6/bq6erIMRH1Y5YRDWU0qAVDt+Vihfs?= =?us-ascii?Q?KW5reKK2Kc0CVdFqE4Vyy5GI8w9iOImnq/fSsDY0ytWptrcTmFgyMXRUdxF8?= =?us-ascii?Q?alB4/OpD/PGxBgST6BxTM0IXcuWz8iHZ6uGivf9/PTnz1uCpZCuFb2Pmq8fL?= =?us-ascii?Q?gh09/lgn9ji7YElRatbT67uWGH2nWlJNBDGeBDID/O5/pEKdxo82mQxVGQa5?= =?us-ascii?Q?ObCbcCb9z1CA9IRApM8cA0aP+KKt7OLTbYGso90doEApU0eS1oJSBP0DUp2u?= =?us-ascii?Q?8YufQXPfPF4ApaKCekxjVx7ccdXfaqVWNUDJJBFRDZwIMpVlMbNm4JwYBgB9?= =?us-ascii?Q?N5KZGvbC+zrh+S32lYL6rs4BEQdkRr7zHfkDmzY0lUPTcLPyLV1QWW0m2L2M?= =?us-ascii?Q?dOx3F8aUpUsep/deoIWnaCGUkY4EHIgYBf3WiycXW11GzVEi5Tgt1Dm5CIpB?= =?us-ascii?Q?/jsfceU0Rk67LjBZ9RPzU3hO+tJKBO6gbOgln07r7ZnM5OnCaOJcVZyqADp5?= =?us-ascii?Q?58PElUOkj0//NFf8RfZuuhy1MaNt+G7tzI9aOBGKEO1CrNX9o7hOtXMDfU4l?= =?us-ascii?Q?RvCXxkazOp6xvIzB9UnYo9bYqPBp9Rb7jUO/aUaPcuFL+AQmbu1c1M/xVsDK?= =?us-ascii?Q?BU6Rv1S1hqxT5ITqrpsyNSw07fU0L5dVIP541x6X3XgLSAATWD//JNm1rLMD?= =?us-ascii?Q?9KXfgcC+RRw2n+vu6/seQ6c7fDzKnt+H6mGbT7vQQuSuw3yEtMzrx2UZGKNy?= =?us-ascii?Q?FirAKLA8b9XNhad+idtpltiRSrpfcCjVLtP3HI+g6Y/x/0TFFR3HXvVsjc37?= =?us-ascii?Q?rPCkYzAKlwm1tdtitDTMfRgKBjBkUjkMbuLwFv0d4nPS/7/x9VpHK76X//x+?= =?us-ascii?Q?XRBxXM08KZP32r3SVxwL32xRDvxRip/plG1JvC5aZ/vEeNYQIGynWta7Qmec?= =?us-ascii?Q?jbFc4Y7hqigX+hn48mmR7PymHGJFOfZ0b4nhyfSQ7iOE?= X-OriginatorOrg: apnic.net X-MS-Exchange-CrossTenant-Network-Message-Id: a799073f-2e9f-4d8b-2cd4-08dca5915076 X-MS-Exchange-CrossTenant-AuthSource: SY7P282MB4761.AUSP282.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Jul 2024 12:17:52.0096 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: 127d8d0d-7ccf-473d-ab09-6e44ad752ded X-MS-Exchange-CrossTenant-MailboxType: HOSTED X-MS-Exchange-CrossTenant-UserPrincipalName: N8AvyxjzqWj8jZMTrA0J65pFM7ZpQraWbDw2nuyDrs7eN7YkLwZJsXS0yiNH9Rx+ X-MS-Exchange-Transport-CrossTenantHeadersStamped: SY4P282MB3892 Message-ID-Hash: C7FCZRIFOI2YBM74EFPXM4EJB2KULLIK X-Message-ID-Hash: C7FCZRIFOI2YBM74EFPXM4EJB2KULLIK X-MailFrom: tomh@apnic.net X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "galvin@elistx.com" , "regext@ietf.org" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5Bregext=5D_Re=3A_WGLC=3A_draft-ietf-regext-rdap-rir-search-09?= List-Id: Registration Protocols Extensions Working Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --EYvWa/gZiApa8hQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Scott, On Mon, Jul 15, 2024 at 05:19:07PM +0000, Hollenbeck, Scott wrote: > A few small things: > > The last call notice refers to the draft as "considered for > publication as a Best Current Practice". The draft describes itself > as a Standards Track candidate. I believe that's just an error in > the last call notice. > > [I-D.ietf-regext-rdap-reverse-search] is now RFC 9536. > > I'd like to see something more in the Security Considerations > section that specifically notes how search functionality increases > the risk of disclosing information that wasn't explicitly requested. > We have this text in RFC 9082: > > "Search functionality also increases the privacy risk of disclosing > object relationships that might not otherwise be obvious. For > example, a search that returns IDN variants [RFC6927] that do not > explicitly match a client-provided search pattern can disclose > information about registered domain names that might not be > otherwise available. Implementers need to consider the policy and > privacy implications of returning information that was not > explicitly requested." > > Maybe just note that the Security Considerations described in RFC > 9082 also apply here. Thanks, updates have been applied per the above (see attached for the current diff from -09). -Tom --EYvWa/gZiApa8hQU Content-Type: text/html; charset=us-ascii Content-Disposition: attachment; filename="draft-ietf-regext-rdap-rir-search-10-from-09.diff.html" Diff: draft-ietf-regext-rdap-rir-search-09.txt - draft-ietf-regext-rdap-rir-search-10.txt
 draft-ietf-regext-rdap-rir-search-09.txt   draft-ietf-regext-rdap-rir-search-10.txt 
Internet Engineering Task Force T. Harrison Internet Engineering Task Force T. Harrison
Internet-Draft APNIC Internet-Draft APNIC
Intended status: Standards Track J. Singh Intended status: Standards Track J. Singh
Expires: 21 September 2024 ARIN Expires: 17 January 2025 ARIN
20 March 2024 16 July 2024
RDAP RIR Search RDAP RIR Search
draft-ietf-regext-rdap-rir-search-09 draft-ietf-regext-rdap-rir-search-10
Abstract Abstract
The Registration Data Access Protocol (RDAP) is used by Regional The Registration Data Access Protocol (RDAP) is used by Regional
Internet Registries (RIRs) and Domain Name Registries (DNRs) to Internet Registries (RIRs) and Domain Name Registries (DNRs) to
provide access to their resource registration information. The core provide access to their resource registration information. The core
specifications for RDAP define basic search functionality, but there specifications for RDAP define basic search functionality, but there
are various IP and ASN-related search options provided by RIRs via are various IP and ASN-related search options provided by RIRs via
their Whois services for which there is no corresponding RDAP their Whois services for which there is no corresponding RDAP
functionality. This document extends RDAP to support those search functionality. This document extends RDAP to support those search
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 21 September 2024. This Internet-Draft will expire on 17 January 2025.
Copyright Notice Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 17, line 16 skipping to change at page 17, line 16
Responses for relation searches for reverse domain objects have the Responses for relation searches for reverse domain objects have the
same form as for a standard domain search response, per [RFC9083]. same form as for a standard domain search response, per [RFC9083].
If the search can be processed by the server, but there are no If the search can be processed by the server, but there are no
results for the search, then the server returns an HTTP 200 (OK) results for the search, then the server returns an HTTP 200 (OK)
[RFC9110] response code, with the body of the response containing an [RFC9110] response code, with the body of the response containing an
empty results array. empty results array.
5. Reverse Search 5. Reverse Search
RDAP reverse search is defined by RDAP reverse search is defined by [RFC9536]. That document limits
[I-D.ietf-regext-rdap-reverse-search]. That document limits reverse reverse search to domains, nameservers, and entities. This document
search to domains, nameservers, and entities. This document extends extends reverse search to cover IP networks and autonomous system
reverse search to cover IP networks and autonomous system numbers as numbers as well.
well.
If a server receives a reverse search query with a searchable If a server receives a reverse search query with a searchable
resource type (per the definition of that term in resource type (per the definition of that term in [RFC9536]) of
[I-D.ietf-regext-rdap-reverse-search]) of "ips", then the reverse "ips", then the reverse search will be performed on the IP network
search will be performed on the IP network objects from its data objects from its data store. Similarly, if a server receives a
store. Similarly, if a server receives a reverse search query with a reverse search query with a searchable resource type of "autnums",
searchable resource type of "autnums", then the reverse search will then the reverse search will be performed on the autonomous system
be performed on the autonomous system number objects from its data number objects from its data store.
store.
Additionally, Section 10 includes requests to register new entries Additionally, Section 10 includes requests to register new entries
for IP network and autonomous system number searches in the RDAP for IP network and autonomous system number searches in the RDAP
Reverse Search and RDAP Reverse Search Mapping IANA registries. Reverse Search and RDAP Reverse Search Mapping IANA registries.
6. RDAP Conformance 6. RDAP Conformance
A server that supports the functionality specified in this document A server that supports the functionality specified in this document
MUST include additional string literals in the rdapConformance array MUST include additional string literals in the rdapConformance array
of its responses, in accordance with the following: of its responses, in accordance with the following:
skipping to change at page 19, line 29 skipping to change at page 19, line 29
"Personal Data", per the definition in [RFC6973]. Given that, server "Personal Data", per the definition in [RFC6973]. Given that, server
operators should ascertain whether the regulatory environment in operators should ascertain whether the regulatory environment in
which they operate permits implementation of the functionality which they operate permits implementation of the functionality
defined in this document. defined in this document.
9. Security Considerations 9. Security Considerations
[RFC7481] describes security requirements and considerations for RDAP [RFC7481] describes security requirements and considerations for RDAP
generally. generally.
[RFC9082] includes security considerations relating to object
retrieval in RDAP. Those considerations are relevant here as well.
10. IANA Considerations 10. IANA Considerations
10.1. RDAP Extensions Registry 10.1. RDAP Extensions Registry
IANA is requested to register the following values in the RDAP IANA is requested to register the following values in the RDAP
Extensions Registry: Extensions Registry:
* Extension identifier: rirSearch1 * Extension identifier: rirSearch1
* Registry operator: Any * Registry operator: Any
skipping to change at page 25, line 31 skipping to change at page 25, line 31
* Level of Maturity: This is a production implementation. * Level of Maturity: This is a production implementation.
* Coverage: This implementation includes the new basic searches * Coverage: This implementation includes the new basic searches
only. only.
* Contact Information: Ed Shryane, eshryane@ripe.net * Contact Information: Ed Shryane, eshryane@ripe.net
12. Acknowledgements 12. Acknowledgements
The authors wish to thank Mario Loffredo, Andy Newton, Antoin The authors wish to thank Mario Loffredo, Andy Newton, Antoin
Verschuren, and James Gould for document review and associated Verschuren, James Gould, and Scott Hollenbeck for document review and
comments. associated comments.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-regext-rdap-reverse-search]
Loffredo, M. and M. Martinelli, "Registration Data Access
Protocol (RDAP) Reverse Search", Work in Progress,
Internet-Draft, draft-ietf-regext-rdap-reverse-search-26,
13 November 2023, <https://datatracker.ietf.org/doc/html/
draft-ietf-regext-rdap-reverse-search-26>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the [RFC7481] Hollenbeck, S. and N. Kong, "Security Services for the
Registration Data Access Protocol (RDAP)", STD 95, Registration Data Access Protocol (RDAP)", STD 95,
RFC 7481, DOI 10.17487/RFC7481, March 2015, RFC 7481, DOI 10.17487/RFC7481, March 2015,
<https://www.rfc-editor.org/info/rfc7481>. <https://www.rfc-editor.org/info/rfc7481>.
skipping to change at page 26, line 29 skipping to change at page 26, line 20
[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the [RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the
Registration Data Access Protocol (RDAP)", STD 95, Registration Data Access Protocol (RDAP)", STD 95,
RFC 9083, DOI 10.17487/RFC9083, June 2021, RFC 9083, DOI 10.17487/RFC9083, June 2021,
<https://www.rfc-editor.org/info/rfc9083>. <https://www.rfc-editor.org/info/rfc9083>.
[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, [RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
Ed., "HTTP Semantics", STD 97, RFC 9110, Ed., "HTTP Semantics", STD 97, RFC 9110,
DOI 10.17487/RFC9110, June 2022, DOI 10.17487/RFC9110, June 2022,
<https://www.rfc-editor.org/info/rfc9110>. <https://www.rfc-editor.org/info/rfc9110>.
[RFC9536] Loffredo, M. and M. Martinelli, "Registration Data Access
Protocol (RDAP) Reverse Search", RFC 9536,
DOI 10.17487/RFC9536, April 2024,
<https://www.rfc-editor.org/info/rfc9536>.
13.2. Informative References 13.2. Informative References
[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Morris, J., Hansen, M., and R. Smith, "Privacy Morris, J., Hansen, M., and R. Smith, "Privacy
Considerations for Internet Protocols", RFC 6973, Considerations for Internet Protocols", RFC 6973,
DOI 10.17487/RFC6973, July 2013, DOI 10.17487/RFC6973, July 2013,
<https://www.rfc-editor.org/info/rfc6973>. <https://www.rfc-editor.org/info/rfc6973>.
[RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the [RFC7480] Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the
Registration Data Access Protocol (RDAP)", STD 95, Registration Data Access Protocol (RDAP)", STD 95,
 End of changes. 9 change blocks. 
25 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/
--EYvWa/gZiApa8hQU--