IETF Logo Mail Archive

Re: [regext] [Ext] Re: RDAP and link context

"Andrew Newton (andy)" <andy@hxr.us> Mon, 04 March 2024 20:23 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 37E2DC1782B5 for <regext@ietfa.amsl.com>; Mon, 4 Mar 2024 12:23:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 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, 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 (2048-bit key) header.d=hxr-us.20230601.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 myhV5TA5uso9 for <regext@ietfa.amsl.com>; Mon, 4 Mar 2024 12:23:30 -0800 (PST)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 541E0C1654F3 for <regext@ietf.org>; Mon, 4 Mar 2024 12:23:30 -0800 (PST)
Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2d29111272eso79426841fa.0 for <regext@ietf.org>; Mon, 04 Mar 2024 12:23:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20230601.gappssmtp.com; s=20230601; t=1709583807; x=1710188607; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=H5AJMW4L9L9St8sEsshub2qT+w/J/waHQv2ZWf+vLGQ=; b=jqQPXdbXgjhQmBd9YoP1PpPjDfv+k/FCEV4gK/Knn7nPNuBJ5LyaFL1wgw96JCVEWb CaFeic5XoeYyrc7+r9W+urlLZKaOcNtwRcWv7Tt+NqJTmTCBlmGDdyVOUEJ1s66Rw1OS Tw88BOzW9b05cI+Z5JAJQ2dTw+q2kWTtx5TVMAYsoz1zcZvqxiQ9mo4uW0LBDEST/hVB Qr03HnqjAn9qZpwIAHYEk27lw7AIeGH2y+5vULFquKw/od3Va+kIPhV41Jg170LIUAac xaX+s9Vsd0eM3BdohauY+iCgRy90DTULmcKY2t+w++wW39sPGwYnNpcDEM6Qrk/Ct2kX s+SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709583807; x=1710188607; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=H5AJMW4L9L9St8sEsshub2qT+w/J/waHQv2ZWf+vLGQ=; b=mAtzqXG67zrnHPgJXsUjp78Pzt2VAXc87mbyE/U3jz3YfX7fq5x0LDbZoVfGBpAalY 9REzI93PHmauZS2XuYhpaqhvJyLsk7hjhTvIDSfc8TeOBONDJP01DcS2MzaJa+Qx8/GZ Y4u2W/iT67zAXKCKtBDdtAmItKgruxcluv3hEGY82F1nVp2Qb+dsAwBp5j443yu1RDom +5j2VDlBFgLRLwoTvJ7scTq06hFssq1UcVsfeCpPz6vnr7E2BlmA9IXbW1/bUL2DU2O2 jntqCI1yN2kYZaJ83JcGLm5Zvpi4WZIkc0PL+V8it3wsqj062nLZj3OnXRa5mjvpy1Go PzPA==
X-Gm-Message-State: AOJu0YwSN1gXsKMP/QbnHMXEktSM6oS9/Y/KbYD7XE98QTdeIOYdHCoC v2ws1s5nj+vsoeZyewLFfDE5c1OkT9eJGwJ6gamwhSAFDgI/lZur54ncCVbac1CCOiqfndtFy2c hzL7uhSAY/C1fcEviW1eAh9p2J6+FL1nI1Hz9BrAvtE+TVLr0ltI=
X-Google-Smtp-Source: AGHT+IHEweF1s5ZHOfwUHGaNKZfp09O4B+7B+9dMLXIRwwU/qOydaaqbqgPJGkmlYN4JLMFXakMXu0xtcSXLrHZ7Uzg=
X-Received: by 2002:a2e:300c:0:b0:2d2:45e0:f154 with SMTP id w12-20020a2e300c000000b002d245e0f154mr6057276ljw.26.1709583807522; Mon, 04 Mar 2024 12:23:27 -0800 (PST)
MIME-Version: 1.0
References: <E057A842-3FF6-4A0A-BD95-9CB8C047BBE9@iana.org> <CAAQiQRco_P-U2EzwXPOudpohUvO0kNhbBkkFBGKbrCG+ANUogA@mail.gmail.com> <A56D1534-E81E-4783-A731-B2ADC1D0E5EA@iana.org>
In-Reply-To: <A56D1534-E81E-4783-A731-B2ADC1D0E5EA@iana.org>
From: "Andrew Newton (andy)" <andy@hxr.us>
Date: Mon, 04 Mar 2024 15:23:16 -0500
Message-ID: <CAAQiQRdkesvL_kQURA55VcPi80z+HrAip3CzMKbtNEcYNAVunw@mail.gmail.com>
To: James Mitchell <james.mitchell@iana.org>
Cc: "regext@ietf.org" <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/K-QSWI5rEeuwQImCYYusCkxSa4Q>
Subject: Re: [regext] [Ext] Re: RDAP and link context
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, 04 Mar 2024 20:23:34 -0000

On Fri, Mar 1, 2024 at 6:57 PM James Mitchell <james.mitchell@iana.org> wrote:
>
>
> The new gTLD Response profile (https://www.icann.org/en/system/files/files/rdap-response-profile-21feb24-en.pdf) says … “a value with the RDAP lookup path that generated the RDAP response.”, requirements 2.6.3 and 2.10. Unless you are referring to another document, this is quite different from the RDAP base URL. I would interpret requests under this profile for /domains/EXAMPLE.COM and /domains/example.com to set the link context to /domains/EXAMPLE.COM and /domains/example.com respectively (or less contrived, lookups for /domain/xn--bcher-kva and /domain/b%C3%BCcher to have different link contexts)
>

I was thinking of 2.4.6 which sets the link context to the Base URL of
the registrar, which seems mighty useful. I agree with your
interpretation of 2.6.3 and 2.10

>
>
> It seems a shame that the spec did not allow the undefined link context to be interpreted as the request URI. However we are where we are and the link context is now mandatory. If someone can shed some light on the utility of the link context then I can look to support that with our server. Otherwise I’ll likely hold onto on the RFC 7483 requirements for links.
>

What's the issue with setting it to the request URI?

-andy

v2.23.0 | Report a Bug | By Email