Hi all,
I just uploaded our preliminary agenda for IETF 119 to the datatracker:
https://datatracker.ietf.org/meeting/119/materials/agenda-119-regext-00
Please verify that I didn’t forget or misinterpreted any requests and let the
chairs know if you still want a slot on our agenda.
Though our ag
From: regext On Behalf Of Jasdip Singh
Sent: Sunday, March 3, 2024 2:12 PM
To: James Mitchell ; Andrew Newton (andy)
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 at
Thanks, Scott. RFC 8288 (obsoletes RFC 5988) also retains this requirement (in
section 2).
Jasdip
From: Hollenbeck, Scott
Date: Monday, March 4, 2024 at 11:28 AM
To: Jasdip Singh , james.mitch...@iana.org
, a...@hxr.us
Cc: regext@ietf.org
Subject: RE: [regext] [Ext] Re: RDAP and link contex
Thanks for the link, Scott.
It appears that the context was made mandatory because of an interpretation of
“according to Section 3 of RFC5988, the members "value", "rel" and "href" are
all required.”
This is correct by definition, however fails to consider web linking as a
whole. RFC 8288 defi
Note that 9083 can’t be “fixed”. It’s a Standard RFC, not an Internet-Draft.
Errata can be submitted, but that only applies if there’s an editorial or
technical error. This sounds more like a desire for clarification, or text that
describes how to interpret the requirement in an RDAP context. We
On Fri, Mar 1, 2024 at 6:36 PM James Mitchell wrote:
>
> I’d say the matching logic is arguably incorrect – matching should begin with
> the parent of the supplied domain name. However, I acknowledge this arguably
> affects only queries for TLDs themselves, as a TLD’s RDAP server could
> redire
On Fri, Mar 1, 2024 at 6:57 PM James Mitchell 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
Internet-Draft draft-ietf-regext-rdap-geofeed-02.txt is now available. It is a
work item of the Registration Protocols Extensions (REGEXT) WG of the IETF.
Title: An RDAP Extension for Geofeed Data
Authors: Jasdip Singh
Tom Harrison
Name:draft-ietf-regext-rdap-geofeed-02.
