[regext] Re: WGLC: draft-ietf-regext-rdap-rir-search-09

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 15 July 2024 17:19 UTC

Return-Path: <shollenbeck@verisign.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 95642C1840C7 for <regext@ietfa.amsl.com>; Mon, 15 Jul 2024 10:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 o2rc19o0CJ3x for <regext@ietfa.amsl.com>; Mon, 15 Jul 2024 10:19:09 -0700 (PDT)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.30]) (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 2ADDDC16941F for <regext@ietf.org>; Mon, 15 Jul 2024 10:19:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=4312; q=dns/txt; s=VRSN; t=1721063949; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=gqDmIWBKPZtZZN9x6NSJY30sPqUbniNwpiaCLjM4T7Q=; b=m3Wg6/BWeViZyjiXUX/XJHCyX4Bzx+uVev2EN70IiTQUnGQ2fXQAB5vI d9P8QWWwUbO/ZCiSy7IBojZ3aOCsG7xHkR7SxYWB2jpYGtOYjbJRBui4r X6rLpH/m77rXItMJRk68WwBKZhhNRo6gOH1DKjykwwZz/lniqjMSL6YhJ I6kwT/jK6P1SO1ThPYVoQ+Z3uWmvIMtyywRptztSOIDTVaxDarWKKNCxn 9pkYAsRblCN7NcEaeGVy/Xpokn2WQo5Dlcny//CbuXTuPyaO6gjVAiMU4 69vChdKBfx5PiPMY0U+0GiCY83Qp/9k5VAaCIqJZ4Ym4GYGCQ5p3aGxGr Q==;
X-CSE-ConnectionGUID: 4L08Hbo+RPaMd1jQjr/zvg==
X-CSE-MsgGUID: O4mxh6kySrm9w03Ti3GPQA==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:bpIowaI2hfpV/kH+FE+R1ZQlxSXFcZb7ZxGr2PjKsXjdYENS3mFWn DMcXmuAOKrfMDenctB/atjn/BgD6J7XmN4xS1NorCE8RH908seUXt7xwmUcnc+xBpaaEB84t ZV2hv3odp1coqr0/0/1WlTZhSAhk/zOH/ykVbOs1hlZHWdMUD0mhQ9oh9k3i4tphcnRKw6Ws LsemeWGULOe82AyajN8B56r8ks14Kyt4W5A5zTSWNgQ1LPgvyhNZH4gDfzpR5fIatE8NvK3Q e/F0Ia48gvxlz8xCsmom6rMaUYDRLjfJ2Cm0hK6jID733CuDgRrukoKHKJ0hXV/0l1lrPgoo Dl5jqFcfC9yVkH6sL9ED0QHSXEW0Zpuo9crKVDn2SCa5xOeLyu0m52CBmluVWET0r4f7W2ja ZX0gd3CB/yOr7ve/V61dgVjrpgHdJnLNoRcgElp6D2AD88kW9fRXaqfsLe03B9o7ixPNdzkQ ZMmTxdfNE2GfRZIIE9RAZ54gv2zgD/0dDgwRFC9/PJxujeIilUsi/6xYLI5efTTLSlRtl2Yo WbC8mLzDxoZHMKS0zue832qwOTImEsXXapJTuHorqEy2DV/wEQ0VBgGVQW4sMKjjx+hA4ljK hc7whMH+P1aGEuDC4OVsweDiHGNugAdXfJdF+wh9BHLwa3Riy6DC2cJXiJpadE6uokxXzNC6 7OSt9nzA2VwtrCFESvY7amO6zazIm0fKikIfyldCxUf+N+lq4Y25v7Scute/GeOpoWdMVnNL /qi9UDSW517YRY36piG
IronPort-HdrOrdr: A9a23:2LJwaqxTkr+w9ngpVSjsKrPw8b1zdoMgy1knxilNoHtuA6mlfq GV7ZYmPHDP6Ar5NEtPpTniAsa9qBrnnPZICOIqTNSftWfd2VeAHcVN4Yzv2DX8FyC73f4178 tdWpk7LNHrF1B1gYLZ7BnQKbwd6ejC1Kyzn+/RwzNWUAdwZ8hbgjtREAqBDUFsfgVACKc4EJ b03KF6mwY=
X-Talos-CUID: 9a23:/NlEUm7iOQt8cHs9eNssqGpMSuAvdT7n9H71Lxa6MGRzD6+LRgrF
X-Talos-MUID: 9a23:c5cG4gkUSiyjx4oxscQwdnpFaMJ44/qtGXsXlMQZ45K4NHdfAw602WE=
X-IronPort-AV: E=Sophos;i="6.09,210,1716249600"; d="scan'208";a="32480700"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.37; Mon, 15 Jul 2024 13:19:07 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) by BRN1WNEX02.vcorp.ad.vrsn.com ([10.173.153.49]) with mapi id 15.01.2507.037; Mon, 15 Jul 2024 13:19:07 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "galvin@elistx.com" <galvin@elistx.com>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-rir-search-09
Thread-Index: AQHa1KEFSHocVKc4RkmZVhyBqJROQ7H4BtRQ
Date: Mon, 15 Jul 2024 17:19:07 +0000
Message-ID: <fe904076b26746dea5c81b3a2d0955f6@verisign.com>
References: <AF4A27B5-84A4-4CDC-A3DF-0538B2E17D75@elistx.com>
In-Reply-To: <AF4A27B5-84A4-4CDC-A3DF-0538B2E17D75@elistx.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: LPZ52YXBCCKIOR2UHK5W6FTYDDJMQMBP
X-Message-ID-Hash: LPZ52YXBCCKIOR2UHK5W6FTYDDJMQMBP
X-MailFrom: shollenbeck@verisign.com
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: WGLC: draft-ietf-regext-rdap-rir-search-09
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Dp8L3twtVBcOENIhja3FapO1aHE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

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.

Scott

> -----Original Message-----
> From: James Galvin <galvin@elistx.com>
> Sent: Friday, July 12, 2024 5:18 PM
> To: REGEXT Working Group <regext@ietf.org>
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-rir-search-09
> 
> Caution: This email originated from outside the organization. Do not click links
> or open attachments unless you recognize the sender and know the content is
> safe.
> 
> The document editors have indicated that the following document is ready for
> submission to the IESG to be considered for publication as a Best Current
> Practice:
> 
> RDAP RIR Search
> https://secure-web.cisco.com/1bZSsnQGQmxhBWWisxpA-e7EjLi-
> FF0G4N3sfIfipgTWVCmeXwOierTpwOew31D7g3qSZRMxhe_HESJdmm6NBVfl
> 9-PQKs8ZX0Z1XihN4BcG-4k6wgMbq05HaLTiUO47a-
> ylj0vgXs1JhxgJle21VH7uz0egkUqSAS4RzRaLe7Ebvb8pRM1knYxxX24lySavXliF
> ANQlXRmnyX0R5sZhzAQ8a49IDSS2prEKgZcI8RtJ5NJl_5GvZU1G0rmok_UFyg
> g8JJMOxd5Aq8_5I4kB6G9TYndwZtR5U8XXJTUGsreM/https%3A%2F%2Fdat
> atracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-rir-search%2F09%2F
> 
> This document has been through WGLC previously.  However, a number of
> questions arose and changes were made that are considered material and thus
> we are proceeding with this additional WGLC.
> 
> Please indicate your support or no objection for the publication of this
> document by replying to this message on list (a simple “+1” is sufficient).
> 
> If any working group member has questions regarding the publication of this
> document please respond on the list with your concerns by close of business
> everywhere, Friday, 2 August 2024.  This WGLC has been extended to 3 weeks
> because of the IETF120 meeting.
> 
> If there are no objections the document will be submitted to the IESG.
> 
> The Document Shepherd for this document is Mario Loffredo.
> 
> Thanks,
> 
> Antoin and Jim
> REGEXT WG Co-Chairs
> 
> _______________________________________________
> regext mailing list -- regext@ietf.org
> To unsubscribe send an email to regext-leave@ietf.org