Hi all,
this new version addresses the outcome of the discussion about redacting
JSContact uid in RDAP.
The examples have been updated to be compliant with last version of
JSContact spec.
Have not yet removed transition stages altogether but I have partially
adjusted them to make the transition simpler.
Would like to collect more feedback on this matter before changing the
document significantly.
Any feedback is welcome.
Best,
Mario
-------- Messaggio Inoltrato --------
Oggetto: New Version Notification for
draft-ietf-regext-rdap-jscontact-16.txt
Data: Tue, 06 Jun 2023 04:50:33 -0700
Mittente: internet-dra...@ietf.org
A: Gavin Brown <gavin.br...@centralnic.com>, Mario Loffredo
<mario.loffr...@iit.cnr.it>
A new version of I-D, draft-ietf-regext-rdap-jscontact-16.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-jscontact
Revision: 16
Title: Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Document date: 2023-06-06
Group: regext
Pages: 25
URL: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-jscontact-16.txt
Status: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-jscontact/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-jscontact
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-jscontact-16
Abstract:
This document describes an RDAP extension which represents entity
contact information in JSON responses using JSContact.
The IETF Secretariat
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
