IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 04 March 2024 16:28 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 EC388C15108E for <regext@ietfa.amsl.com>; Mon, 4 Mar 2024 08:28:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 XoXcbUFaYV7k for <regext@ietfa.amsl.com>; Mon, 4 Mar 2024 08:28:26 -0800 (PST)
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 6E816C14F69E for <regext@ietf.org>; Mon, 4 Mar 2024 08:28:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=8586; q=dns/txt; s=VRSN; t=1709569696; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Tdj0ayASj1/xSuLCHklB7W+1Hj4iP7akctzKL/cyYOg=; b=W53fNhrfKMCVsZm7FvEmkgK9/NUEQVFo+ReycnH7XzsMLikJSba0xBo4 GbhFPCk1zJih9Z/pvBN0eTMabptrUaThZ/8XBaAi16dYL/7K4/c9GI55n 9dV31tUHWOh0HV0dufllfEEDdzqfnuhvGOx3J+bC4OLL0lNod1J/gVbKR EJ8jlZ6f1qZaBp2By7rF3CC4KiOZedQKoCD7XzVSENfZ6QstSJ7jXMMc4 vWLzz4XOTGHTl4BiAKjc+6/uwm/adVaOpiWpY/VsjiPwxMU/wds/k0vj9 gHrgfk7Ebo58hIMh3cbciDBndawr+Q4IockocKvDbhUYxIEVvlJwtozaA Q==;
X-CSE-ConnectionGUID: q66YR4ATSCWpibsy5iG0ew==
X-CSE-MsgGUID: getXicczQDmTqn1qBh4gEA==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:l4tM+KlDBetvULLn39pD7/Lo5gyXJ0RdPkR7XQ2eYbSJt1+Wr1Gzt xIZXG/XMq6DYTajKdB1OYjioU0PsZLQnIU2HgZppX88Ei4T+ZvOCOrCIxarNUt+DCFhoGFPt JxCN4aafKjYaleG+39B55C49SEUOZmgH+e6UKicfHkpGWeIcQ954Tp7gek1n4V0ttawBgKJq LvartbWULOf82cc3lk8teTb9nuDgNyo4GlE5gdmOagR1LPjvyJ94Kw3dPnZw0TQH9E88t6SH 47r0Ly/92XFyBYhYvvNfmHTKxBirhb6ZGBiu1IOM0SQqkEqSh8ai87XAMEhhXJ/0F1lqfgqk YkQ6sbgIeseFvakdOw1C3G0GgkgZfEWoOevzXKX6aR/xGWeG5fgLmkH4Ojb8uT0984uaVyi+ 8D0JxgUME6yvb6f/ImQdfFtjN8yccjEZI4A7yQIITHxVZ7KQLjpeYOT2vl17G9qwN5FGuzGI cMVLyR1dxKGaBpKUrsVIMtm2r733T+mLmYe9AP9SakfugA/yCRq0L/pNNfTcNGBRu1Lk1yZv WPJ+SLyBRRy2Nm3kmLdoyvz2L+ncSXTV48OJLyz/exTrFiv32pKETcWCVSWiKzs4qK5c5cFQ 6AOwQIspLM+9VSwZtDnXhv+pnOY1jYeUt9dCKs/6R2GyqfQ5y6YD24NCDlbZ7QOvck6VBQqx kXPgsiBLSZiv7CFVVqc+6ua6zSoNkAowXQqbzUCFBQD7sm7+sQokAiJS9d4VaSyyNfvH2i23 SqRqm41gLB7YdM36phXNGvv21qEzqUlhCZsjukLdgpJNj9EWbM=
IronPort-HdrOrdr: A9a23:xgObKK5uSD7Vdl0zSwPXwOTXdLJyesId70hD6qkoc20wTiSZ// rDoB1p726StN9xYgBapTnuAsm9qB/nn6KdpLNhWItKPzOWwldATrsSjrcKqgeIc0bDH6xmpM VdmsNFZ+EYeGIasS+M2meF+rgbreVvu5rY49s2h00dND2CRZsQlztENg==
X-Talos-CUID: 9a23:+CjGQWqDROpjUyehnMWovmTmUdl7LEznkF7sGGSHEWdjU6zISHDI9bwxxg==
X-Talos-MUID: 9a23:eutUIgYV3XnYmeBTuDLwtDBpP9VRz6GSEUZUiL8G58apHHkl
X-IronPort-AV: E=Sophos;i="6.06,203,1705381200"; d="scan'208,217";a="30091768"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Mon, 4 Mar 2024 11:28:15 -0500
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.035; Mon, 4 Mar 2024 11:28:15 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "jasdips@arin.net" <jasdips@arin.net>, "james.mitchell@iana.org" <james.mitchell@iana.org>, "andy@hxr.us" <andy@hxr.us>
CC: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [regext] [Ext] Re: RDAP and link context
Thread-Index: AQHabZ689/3xwo9o8Ee9SAuBaG9Vg7EnxTNg
Date: Mon, 04 Mar 2024 16:28:14 +0000
Message-ID: <59520332939e4bfcb6c64802f08226e5@verisign.com>
References: <E057A842-3FF6-4A0A-BD95-9CB8C047BBE9@iana.org> <CAAQiQRco_P-U2EzwXPOudpohUvO0kNhbBkkFBGKbrCG+ANUogA@mail.gmail.com> <A56D1534-E81E-4783-A731-B2ADC1D0E5EA@iana.org> <LV3PR15MB6453ADFFF1B4935F50F26444C95C2@LV3PR15MB6453.namprd15.prod.outlook.com>
In-Reply-To: <LV3PR15MB6453ADFFF1B4935F50F26444C95C2@LV3PR15MB6453.namprd15.prod.outlook.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: multipart/alternative; boundary="_000_59520332939e4bfcb6c64802f08226e5verisigncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/um26c0IHkEMQ7O_D44sVBbAwH0A>
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 16:28:30 -0000

From: regext <regext-bounces@ietf.org> On Behalf Of Jasdip Singh
Sent: Sunday, March 3, 2024 2:12 PM
To: James Mitchell <james.mitchell@iana.org>; Andrew Newton (andy) <andy@hxr.us>
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] [Ext] Re: RDAP and link context



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.

Hi.



Did some digging on this.



Right, RFC 7483 had only “href” as a MUST. RFC 7483bis (eventually RFC 9083) additionally made “rel” and “value” as MUST’s. Looks like the “rel” MUST came about because of RFC 8288 mandating so [1], and the RDAP Deployment Findings and Update draft highlighting so [2]. As for making “value” a MUST, the rationale is not very clear from [2]. It even passed the IESG review [3]. (Scott might be able to shed more light on this. :))

[SAH] The change was made in version -01 of draft-hollenbeck-regext-rfc7483bis (“Clarified that the "value", "rel" and "href" JSON values MUST be specified in the "links" array.”) Here’s the on-list discussion:



https://mailarchive.ietf.org/arch/msg/regext/kWZ9ix80uaUAHqXjJsf_L2IN-Ys/



Blame RFC 5988.



[SAH] Scott

v2.23.0 | Report a Bug | By Email