IETF Logo Mail Archive

Re: [regext] OK, What Next? (was RDAP Extensions Approach Analysis v2)

Andrew Newton <andy@hxr.us> Tue, 19 July 2022 15:11 UTC

Return-Path: <andy@hxr.us>
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 3F95EC14CF0A for <regext@ietfa.amsl.com>; Tue, 19 Jul 2022 08:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20210112.gappssmtp.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 TQlORW98jjSy for <regext@ietfa.amsl.com>; Tue, 19 Jul 2022 08:10:57 -0700 (PDT)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 B6EFCC14F739 for <regext@ietf.org>; Tue, 19 Jul 2022 08:10:57 -0700 (PDT)
Received: by mail-ua1-x92a.google.com with SMTP id 94so1376706uau.8 for <regext@ietf.org>; Tue, 19 Jul 2022 08:10:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mMjwWo7ixXf6w28zJ1xOgFZtN7LDLXBmpVqfceTIl0g=; b=mreGIw5SvhKma5xheTI7mnNmaX3Y/67PYjdAthaty5SfI8Wy4mmZcsC3vkgYT1ifJL fBrAO9WL6fQ2SitE1QV5KoS96x9/49FP1dV/KmcOo3Q2kGzJcbxwFGot8GiR1riq7mXP OIth59FCr0NJ0Av3keRE6ZHtB5k0do+Zys8DzQ3g4jUrEg/2UeJZS+cpBc2BKuEKOXJ7 lBvxG68OtSMlKrxXdO/Q3TNeKJ6lXriXdsEypF7IpFvKGtJoCxw7hK8ZrUu3YJ1eRPBg qWqJcC8epMSQHRe5U5RGE+akoPCXqoGFnNSk1eLTnO2R7FkSDSRTpcP2u4/MIXQXAYod rc0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mMjwWo7ixXf6w28zJ1xOgFZtN7LDLXBmpVqfceTIl0g=; b=KW9BKunv0wrV+77Xg1q7G5aw/ZIGMd7te6ZpXkYkE1Kqy8XdS/C/x3+qSIhfCYBa2X pG2FuJoiM3h5VXRbLXVnyES/72oLnIfI36nOQa4CJoZJxeMu5gW4FLUhXnm8WMJ9/iDc J1af1i6CDVrAFHL9ot4yAqISoHqQ6MnZj7CL4PsRNbd5T7dBT38kHR2k1D3jb9GfUOSk L1t3ZO7nAGxF7vFe0vmMy9/kjRw2A/sznuPfN26VFc9sgZTy1uO+/lXbo2UvEdLEEVyN dFL7GMTdJrQTUxzlBXLuJAs+d6QNzxC0oX9+J3qLLA4N8sHFq4RieI1KPWfrwApNB04n E49g==
X-Gm-Message-State: AJIora8Khk/aN5dFu8uSnmz5xkGUGtYSpZOJWaTeDjznuddjg/Qsl3nh xeBs/qIO23HgDSUFWCqUJAgtDXlA+TwVopRq8x/g2A==
X-Google-Smtp-Source: AGRyM1s+KOpqR6nW3nJups/Q0wB4/4N6WcTo+2EjdKbBgL/NFsHe708qPV4ZSUdnm7mud/WWFEAWYvYt6inJKzxjoi8=
X-Received: by 2002:ab0:3570:0:b0:384:20af:2088 with SMTP id e16-20020ab03570000000b0038420af2088mr2079283uaa.40.1658243456564; Tue, 19 Jul 2022 08:10:56 -0700 (PDT)
MIME-Version: 1.0
References: <DB38F1D3-FC41-4B42-8C00-AB408FD1F204@verisign.com>
In-Reply-To: <DB38F1D3-FC41-4B42-8C00-AB408FD1F204@verisign.com>
From: Andrew Newton <andy@hxr.us>
Date: Tue, 19 Jul 2022 11:10:45 -0400
Message-ID: <CAAQiQReG1MTF8EFuSMASoeuct+h+wmLUZRmgyvyo-fHL2g918g@mail.gmail.com>
To: "Gould, James" <jgould@verisign.com>
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>, "regext@ietf.org" <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/7U7AlW_6uCu-tjVoUDcA5njkdFc>
Subject: Re: [regext] OK, What Next? (was RDAP Extensions Approach Analysis v2)
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: Tue, 19 Jul 2022 15:11:02 -0000

On Tue, Jul 19, 2022 at 10:58 AM Gould, James <jgould@verisign.com> wrote:
>
> Since rdapConformance is defined as an array of strings, adding the sub-element definition in the rdapConformance is something new.

It is not new. Adding another string to the array is exactly how it is
supposed to work. I'm not in favor of creating entirely new mechanisms
if the ones we have will suffice. Can you please demonstrate why it
will not work?

As for auto-discovery, I am not discounting your call-out for that
feature. I just don't think it applies to the use cases you have
provided. Additionally, I don't know if it is a problem yet, as Scott
has pointed out the /help query allows a client to discover a server's
capabilities.

-andy

v2.23.0 | Report a Bug | By Email