Hi folks,
this new version is complaint with last JSContact spec. I also added a
section about registering the JSContact map keys that must be used in
the RDAP context.
Since JSContact will hopefully move to IESG next week, I would like to
finalize this document for WGLC.
in addition to your remarks, there are some open points from my side:
1) The "uid" property is mandatory in JSContact. Currently, the
document recommends to set it to the handle value.
As such, currently the value doesn't represent a universal identifier.
To save it from collisions, a possible solution could be to set it to
the URL of the lookup query for the entity related to the contact card
as in the following:
"handle":
"XXXX<https://datatracker.ietf.org/doc/html/rfc9082#section-3-1-5-4>",
"jscard": {
"@type" : "Card",
"@version" : "1.0",
"uid" :
"https://example.com/rdap/entity/XXXX<https://datatracker.ietf.org/doc/html/rfc9082#section-3-1-5-4>",
....
}
The entity lookup URL MUST always be used regardless of the query
generating the response including the contact card.
Does it work for you?
2) This is connected to the point above.
Usually, the handle is not redacted.
Nevertheless, should I add text stating that, being uid mandatory, it
MUST be redacted by the emptyValue redaction method as defined in
draft-ietf-regext-rdap-redacted ?
3) SInce the contact information as described in RFC5733 doesn't include
a separate property for the postal address street details, should I add
text clarifying that in the RDAP context the JSContact StreetComponent
type "name" is used to
represent all the street details ?
Optionally, it would be possible to register and then use a new
StreetComponent type value.
Please review and provide any feedback.
Thanks a lot in adavance,
Mario
-------- Messaggio Inoltrato --------
Oggetto: New Version Notification for
draft-ietf-regext-rdap-jscontact-15.txt
Data: Sat, 10 Dec 2022 00:36:29 -0800
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-15.txt
has been successfully submitted by Mario Loffredo and posted to the
IETF repository.
Name: draft-ietf-regext-rdap-jscontact
Revision: 15
Title: Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
Document date: 2022-12-10
Group: regext
Pages: 26
URL: https://www.ietf.org/archive/id/draft-ietf-regext-rdap-jscontact-15.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-15
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
