Tom and I put together an I-D outlining what a SimpleContact might look like.
Of course I am biased, but I think this does simplify RDAP contact data considerably. Also note that while this I-D does support structured names (as is found in jCard and JSContact), we are unsure if they are needed in the RDAP context as we can find no evidence of structured name usage in the current RDAP ecosystem. -andy ---------- Forwarded message --------- From: <internet-dra...@ietf.org> Date: Wed, Jul 5, 2023 at 8:21 AM Subject: New Version Notification for draft-newton-regext-rdap-simple-contact-00.txt To: Andy Newton <a...@hxr.us>, Tom Harrison <t...@apnic.net> A new version of I-D, draft-newton-regext-rdap-simple-contact-00.txt has been successfully submitted by Andy Newton and posted to the IETF repository. Name: draft-newton-regext-rdap-simple-contact Revision: 00 Title: RDAP Simple Contact Document date: 2023-07-05 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/archive/id/draft-newton-regext-rdap-simple-contact-00.txt Status: https://datatracker.ietf.org/doc/draft-newton-regext-rdap-simple-contact/ Html: https://www.ietf.org/archive/id/draft-newton-regext-rdap-simple-contact-00.html Htmlized: https://datatracker.ietf.org/doc/html/draft-newton-regext-rdap-simple-contact Abstract: This document describes an extension to the Registry Data Access Protocol for entity contact data using basic JSON values, objects, and arrays. The data model defined by this document is purposefully limited to the data in-use by Internet Number Registries and Domain Name Registries and does not attempt to model the full data-set that can be expressed with other contact models such as jCard or JSContact. The IETF Secretariat _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
