Re: [regext] IANA Considerations in draft-ietf-regext-rdap-reverse-search

"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 31 July 2020 16:21 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 6CDEC3A0B38 for <regext@ietfa.amsl.com>; Fri, 31 Jul 2020 09:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xQ8sL46671u for <regext@ietfa.amsl.com>; Fri, 31 Jul 2020 09:21:23 -0700 (PDT)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 A345E3A0B00 for <regext@ietf.org>; Fri, 31 Jul 2020 09:21:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=1902; q=dns/txt; s=VRSN; t=1596212483; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=vqIHS9R+eQMv1wGvll/uTzmnEdpZr1ocUaLPEEz1CXo=; b=HeC6llPtsotgmgbYp6mJNG5GZK4hIjX7t/RyDyI/zzi8MZ36qX0B4pGs w8PvuzRhpM4qh/1DQG1aNFMK45NsXC0EFd7VYpXlm7Ge86JeZgLTdtXiE 7hS7HuQgj6IBU1lXAYikyAVjDRR48+uWZdxOdK+5WIJzxCMQraqCU80U5 LEGzBTR8CSy5cJfP2ZO9Qq7oZJqEg1Q7q2T+/uF2Lwizq+9eAqbGm8uqe CA9z6AbdS28JgLKhwSlLM/fGDiM0xvZ0Fe9fkuloECRZ5hADlKR9D5mM6 9/lz8mAzU5UiSZXpprnohePYXYd/VIgF66M00e/acDeYpq+1LSEBYBZC+ A==;
IronPort-SDR: 5eN72X+HErdbWKQsgPekkRA3u1LA2JISGqocRw3KdiQKlhVHAzUxaGRgOsyFSfzumu8iwygc6a JpVHK+qhtxZaeQH30VMY5njtbuZZ4QOmqISUZ36gs+SgfdRj01xFhpzc9tnsqBny7xuP6vxHvM kLwiVHOAy8EfZHgwzeaSENnEgsR4PEklmXG4GfWGz1S7rl77WSYuMRL9D8G3Utp6juxn4md6jB hPb6pJcdPhNGYgGr/1vf0ceNiBqrEQoiPq6rirhmyg+7ul/5/AxtXnytXZVef6Yd3jW7qsFb0b FGc=
X-IronPort-AV: E=Sophos;i="5.75,418,1589256000"; d="scan'208";a="2377639"
IronPort-PHdr: =?us-ascii?q?9a23=3A0bmKFBX33lyXuFM8cofVrEDmLljV8LGtZVwlr6?= =?us-ascii?q?E/grcLSJyIuqrYbRyBt8tkgFKBZ4jH8fUM07OQ7/m+HzJQqsbe+Fk5M7V0Hy?= =?us-ascii?q?cfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aFR?= =?us-ascii?q?rwLxd6KfroEYDOkcu3y/qy+5rOaAlUmTaxe7x/IAi3oAnLt8QbgoRuJ6Uzxx?= =?us-ascii?q?DUvnZGZuNayH9yK1mOhRj8/MCw/JBi8yRUpf0s8tNLXLv5caolU7FWFSwqPG?= =?us-ascii?q?8p6sLlsxnDVhaP6WAHUmoKiBpIAhPK4w/8U5zsryb1rOt92C2dPc3rUbA5XC?= =?us-ascii?q?mp4ql3RBP0jioMKjg0+3zVhMNtlqJWuBKvqQJizY7Ibo+bN/R+caHcfdwGSm?= =?us-ascii?q?ROUd1cVzBYAoO+c4cDE/YNMfheooLgp1UOtxy+BQy0Ce/hyDFIgXv23akk3O?= =?us-ascii?q?QnCg7JwhAvH9EWvH/Jsdv6KKASUfypzKXG0D7OaOhW2Tf66IjMdhAuv/eMUq?= =?us-ascii?q?lufsXNykkiDB3FgUuKqYzkJDOV1+sNs26B4+V8UuKvjncqpgdsqTeg2skikJ?= =?us-ascii?q?PGhp4Jyl/a7yV5xp44KMC4RUN7fdOpDpldujyeOoZ5X84sTH1ktSImxrEbpZ?= =?us-ascii?q?K2ciYExYkkyhPQd/CLb4iG7BL/WOifIzp2imxodbajihu07EOuyfX8W9Gp3F?= =?us-ascii?q?pWtCZJj9vBu34X2xDO6sWKROFx80ii1DqXygzf9vtILV02mKbHMZIt37E9m5?= =?us-ascii?q?kJvUjeHSL7nlj9grWMeUU+4Oeo7vzqYrDhppCBKYB5khr+MqEymsynBuQ4Lx?= =?us-ascii?q?QOU3Cb+eui0L3j+lX0TahWgPMuj6XWsIjUK8saqaKlHgNZyJgj5Aq4Dze8yN?= =?us-ascii?q?QUh2MII09fdBKZlYjpIFfOLOrkAve4hlSgiDZrx/bYMb39GpjBM2TPnK38cb?= =?us-ascii?q?t/5UNQ0hc/wNBR6p5OBbwMI+r/Wkrru9zZCh85PRa0w+HiCNhlzYMeWWWPAq?= =?us-ascii?q?udMKzMt1+H/fwgLPWPZIIOpjbyNeIl5//1jX84ll8de7Ol0ocQaHC9BvhmOV?= =?us-ascii?q?mWYWLwgtcdFmcHphI+TOnxhVKfVj5Te2y9X6Qh6T4nD4KqF5vMRoeogLaZxi?= =?us-ascii?q?e0AoVWZnxaClCLCXrobZuLW/gSZyOdPs9siT0EWqa9S48vzx2usxX6y7U0Zt?= =?us-ascii?q?bTr2cAsLrv08R84eHYklc58jk+R5CF1kmBSH19mG8DQHk926Up5QQ30FqM3L?= =?us-ascii?q?hkq/1VCdIV4OlGGE9uL5PTwvxmI9H/RgyHec2GHgWIWNKjVHsRSdY1ztkEbk?= =?us-ascii?q?1+X52ZhRffw2DiV6QVkLiPCZo+/6nf92b8PcdmynnAkqImig91EYN0KWS6i/?= =?us-ascii?q?snpEDoDInTnhDBmg=3D=3D?=
X-IPAS-Result: =?us-ascii?q?A2HsAAA7QyRf/zCZrQpgGwEBAQEBAQEBBQEBARIBAQEDA?= =?us-ascii?q?wEBAUCBSoF1glcKlUKcDQsBAQEBAQEBAQEHAS8EAQGETAKCNSU4EwIDAQELA?= =?us-ascii?q?QEBBQEBAQEBBgMBAQEChlGCNyKDcQEBAQEDOksEAgEIEQQBAQEeEDIdCAEBB?= =?us-ascii?q?AESCLZZdIE0hVKEfIE4jSiBQj6BEYMQPoQlhg4Ej1ymLgMHgmCZeyqfd5Ijn?= =?us-ascii?q?yMCBAIEBQIVgWqBe3BQgmlQFwINjlaOEHQ3AgYIAQEDCZAOgREBAQ?=
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_128_GCM_SHA256) id 15.1.1913.5; Fri, 31 Jul 2020 12:21:21 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.1913.005; Fri, 31 Jul 2020 12:21:21 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "pm@dotandco.com" <pm@dotandco.com>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] IANA Considerations in draft-ietf-regext-rdap-reverse-search
Thread-Index: AdZnNOUF5N2RSl5aSj6EkwI8/xgDnAAJ4D4AAAMu8oAAAiqfgAAAiMuAAAeIxrA=
Date: Fri, 31 Jul 2020 16:21:20 +0000
Message-ID: <abb138473ef245ce9eb3e263f2e85a57@verisign.com>
References: <1cb2fde4261748afa8163333d090b84a@verisign.com> <df404a43-8284-5466-7d83-88e27d5691ef@iit.cnr.it> <0f361bcb-cd2d-4336-8f71-f06f72430e48@www.fastmail.com> <234b29a5-ab00-6f1e-64f7-1da48673dbe2@iit.cnr.it> <65ee0574-0a07-4bf4-a73c-2d5fe8ec57f4@www.fastmail.com>
In-Reply-To: <65ee0574-0a07-4bf4-a73c-2d5fe8ec57f4@www.fastmail.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/nMSpOZnoTNx-x4NkJXql4DFnOYs>
Subject: Re: [regext] IANA Considerations in draft-ietf-regext-rdap-reverse-search
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 31 Jul 2020 16:21:26 -0000

> -----Original Message-----
> From: regext <regext-bounces@ietf.org> On Behalf Of Patrick Mevzek
> Sent: Friday, July 31, 2020 11:51 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] IANA Considerations in draft-ietf-regext-
> rdap-reverse-search
>
> On Fri, Jul 31, 2020, at 10:35, Mario Loffredo wrote:
>
> > The server might inlcude in rdapConformance either the hints to all
> > the supported features or the only hints to the features allowed to
> > the consumer.
> >
> > This also applies to the help response. Definitively, it's a matter of
> > server policy.
>
> If you introduce options (the list is either related to the content OR the full
> list of server features), how is a client supposed to know in which case he is?
> He can't right now, which is why I don't think such options should be added.

As it's currently written, 7482bis says this about the help query:

"The help path segment can be used to request helpful information (command syntax, terms of service, privacy policy, rate-limiting policy, supported authentication methods, supported extensions, technical support contact, etc.) from an RDAP server.  The response to "help" should provide basic information that a client needs to successfully use the service."

Note "supported extensions". This is why I'm saying that we need to register all extensions with IANA and include them in the rdapConformance data structure even if they don't describe a response extension. To Patrick's question above, I think it's a good idea to be consistent about it. The help response should include supported extensions that are available to that client. Note, though, that the list of supported extensions might vary if the client is identified and authenticated. In that case, some clients MAY have access to extensions that other clients don't.

Scott