Hi,
this continues the brief discussion we had at the last meeting about
turning the rdap-jscontact draft back into ST.
Since that draft has been made experimental, the following revision
documents have been published for the JSContact properties that were the
WG's primary concern regarding the use of JSContact in RDAP:
- draft-ietf-calext-jscontact-uid, now in IETF Last Call, makes the
JSContact "uid" property optional. This specification prevents RDAP
providers prevent response correlation and thus manage the redaction of
that property.
- draft-ietf-calext-jscontact-profiles, which is also expected to go
through the IETF Last Call shortly, simplifies the handling of the
JSContact "localizations" property to allow RDAP providers to avoid
handling JSON pointers. This simplification was also demonstrated
through the POC published at
https://github.com/mario-loffredo/TestJSContactProfile.
Furthermore, the RPP requirements, as described in
draft-ietf-rpp-requirements, include a recommendation to use the
JSContact format for representing contacts.Therefore, although RPP has
recommended to adopt JSContact and not the corresponding RDAP extension,
RPP implementers would benefit from a direct conversion of RPP data to
RDAP data through the standardization of this extension.
Consequently, Gavin and I believe this new information is sufficient to
prompt the WG to reconsider the draft's category.
It would be appropriate to conclude this matter so that the document can
proceed to the next standardization phases, depending on its category.
Thoughts ?
Best,
Mario
--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
Address: Via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
