Internet-Draft draft-ietf-regext-rdap-x-media-type-01.txt is now available. It
is a work item of the Registration Protocols Extensions (REGEXT) WG of the
IETF.
Title: An RDAP With Extensions Media Type
Authors: Andy Newton
Jasdip Singh
Name:draft-ietf-regext-rdap-x-media
Internet-Draft draft-ietf-regext-rdap-extensions-02.txt is now available. It
is a work item of the Registration Protocols Extensions (REGEXT) WG of the
IETF.
Title: RDAP Extensions
Authors: Andy Newton
Jasdip Singh
Tom Harrison
Name:draft-ietf-regext-rdap-ext
Hi all,
This new version of the draft has a couple of new sections.
Two of the new sections call for the addition of more expert reviewers
for the IANA RDAP registries and for the reviewers to check each others
work.
And the other two sections regard security considerations and privacy
cons
Andy,
In reviewing the updates to draft-ietf-regext-rdap-extensions, I believe that
we need to reconsider the criteria for the RDAP JSON Registry values. Based on
the types initially defined, the use of lowercase only values may make sense,
but for the recently registered values from the RDAP
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Monday, August 19, 2024 7:14 PM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] a list of RDAP clients
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments unless you rec
> [SAH] This is something you're maintaining, Andy? How did you manage to find
> them all?
The genesis of it is explained at
https://blog.rcode3.com/blog/a-guide-to-rdap/
The referenced paper at https://pam2024.cs.northwestern.edu/pdfs/paper-89.pdf
does list various clients.
With the latest updates posted for draft-ietf-regext-rdap-x-media-type and
draft-ietf-regext-rdap-extensions, we need to look at the below alignment
feedback that I provided back in July between the three drafts.
I believe that merging draft-ietf-regext-rdap-x-media-type into
draft-ietf-regext-
