Hi,
this version doesn't include support for the uid property as it refers
to JSContact v2.0 which made uid optional
(draft-ietf-calext-jscontact-uid
<https://datatracker.ietf.org/doc/draft-ietf-calext-jscontact-uid/>).
Therefore, there is no longer any concern about the uid property being
mandatory in RDAP.
It also includes a section about registering the "rdap" JSContact
profile (draft-ietf-calext-jscontact-profiles
<https://datatracker.ietf.org/doc/draft-ietf-calext-jscontact-profiles/>).
Any feedback is appreciated.
Best,
Mario
-------- Messaggio Inoltrato --------
Oggetto: [regext] I-D Action: draft-ietf-regext-rdap-jscontact-22.txt
Data: Tue, 01 Jul 2025 07:14:48 -0700
Mittente: [email protected]
Rispondi-a: [email protected]
A: [email protected]
CC: [email protected]
Internet-Draft draft-ietf-regext-rdap-jscontact-22.txt is now available.
It is
a work item of the Registration Protocols Extensions (REGEXT) WG of the
IETF.
Title: Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Authors: Mario Loffredo
Gavin Brown
Name: draft-ietf-regext-rdap-jscontact-22.txt
Pages: 32
Dates: 2025-07-01
Abstract:
This document describes an RDAP extension which represents entity
contact information in JSON responses using JSContact.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-jscontact/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-jscontact-22
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-jscontact-22
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
