Marc, Precedence has been set in JSON Values Registry of RFC 9083 with the “notice and remark type” to support an enumerated set of notices and remarks with the use of the “type” field. If a similar approach was taken for the reason in draft-gould-regext-rdap-redacted, the reason member would need to be restructured in a similar fashion to the “notices” and “remarks” in RFC 9083. Meaning make it a JSON object with a optional “description” member and an optional “type” member, where the “type” member will match the registered type in the JSON Values Registry. We would then need to add a new JSON Values Registry type for redaction reasons to enable the registration of them. I recommend adding the JSON Values Registry type “redaction reason” for this purpose. The optional “reason” member would then look like the following:
# Reason with an unregistered description "reason" : { “description” : “Client request” } # Reason with only a registered type “reason” : { “type” : “Client request" } # Reason with both a registered type and a description “reason” : { “type” : “Client request" “description” : “Client requested to have the field redacted” } Does this look consistent with the approach taken in RFC 9083 and address your feedback? Thanks, -- JG [cid:image001.png@01D77892.4893C0C0] James Gould Fellow Engineer jgo...@verisign.com<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://verisigninc.com/> From: Marc Blanchet <marc.blanc...@viagenie.ca> Date: Monday, July 12, 2021 at 7:41 AM To: James Gould <jgo...@verisign.com> Cc: "regext@ietf.org" <regext@ietf.org> Subject: [EXTERNAL] Re: [regext] New Version Notification for draft-gould-regext-rdap-redacted-00.txt Le 12 juill. 2021 à 07:26, Gould, James <jgo...@verisign.com<mailto:jgo...@verisign.com>> a écrit : - I really would like to have an IANA registry for the « reason » property. Because this would be potentially displayed to the user, and to avoid having all variations of the same reason in different words. A registry of reserved words would also facilitate translation in multiple languages. We had a desire to stay away from needing to setup an IANA registry for redaction. I view the reason property as not a good candidate for an IANA registry, since it's meant to be a human readable informational value Fine but that does not preclude the use of an IANA registry with reserved text. We already have that: https://www.iana.org/assignments/rdap-json-values/rdap-json-values.xhtml<https://secure-web.cisco.com/1CpBTBaAbWXShtu3I3CgJpJu24mEs9ljN-JZFzuDsQTI3FxgaWMmOrd_t3tvEV72gkQmb5znPpgnRyT4kmZRJDIqFHqcz9Bbyvg57xwiJfZd-N4xqddAw5eLmk_K28myevtwarkxyyRc3Nrd_Hv17G7Ps-CwKFwcGPyigFJVrP1aZw9RCvarhO-h-GExrL1MsE7pkowpYOR3h_QrlwfnEBqhicohhvS7BpAyyBnWL6VIuEMdEN5HFDNJ_DAAljli3/https%3A%2F%2Fwww.iana.org%2Fassignments%2Frdap-json-values%2Frdap-json-values.xhtml>. We can even reuse the same registry and add some rows. Client processing, with reserved words, can act upon: displaying nice icons instead of long words for example. It can also be internationalized. If it is human readable, then that means the server has to send all the languages translations. Not great. I’m sure that we can standardized those reason values to less than a dozen. Marc. that includes normative language not to be used as a client processing dependency. This is a good discussion item. Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com<mailto:jgo...@verisign.com> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://Verisign.com> <http://verisigninc.com/<http://secure-web.cisco.com/1beQfCbdiRGkXWoDIwEZqB-syrWkxKlPLmKXZ5TyPLcyHJefT1L0kWFy55Ogjue3I0e6sl1LZnrl57ZdbPW70plJDkV1TrXSRiOVelUFiAdeskppvN7dLYDFaa0F4fRnqlN0gf6aXzFlIMbtj7PYNnyai6PheZ2iizECnbbRgkFOPor0IF9oPIALohtLm2Ur5hdrKFF3RqLFts6IzaW8svDPPDK_pHe6KQjPjK63W-Cx_D5Xb_GShrkpr4QQRNZyb/http%3A%2F%2Fverisigninc.com%2F>> On 7/12/21, 7:15 AM, "Marc Blanchet" <marc.blanc...@viagenie.ca<mailto:marc.blanc...@viagenie.ca>> wrote: Just read it. Goooood. We need it. (Specially with my hat of RDAP client app). Some early comments: - would be good to include specific text about jscontact, so when we switch to it, this document does not need rev. - I really would like to have an IANA registry for the « reason » property. Because this would be potentially displayed to the user, and to avoid having all variations of the same reason in different words. A registry of reserved words would also facilitate translation in multiple languages. Really would like this document to move forward. As RDAP client implementor, I would like to implement it. If some servers are already implementing it, please contact me directly so we can do some interop testing. Marc. Le 12 juill. 2021 à 07:02, Gould, James <jgould=40verisign....@dmarc.ietf.org<mailto:jgould=40verisign....@dmarc.ietf.org>> a écrit : The "Redacted Fields in the Registration Data Access Protocol (RDAP) Response" draft-gould-regext-rdap-redacted has been published. The goal of the draft is to describe an RDAP extension for explicitly identifying redacted RDAP response fields, using JSONPath as the default expression language. Any review and feedback is welcome. Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com<mailto:jgo...@verisign.com> <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com<http://Verisign.com> <http://secure-web.cisco.com/1mjljSszRHMWBBWiVRrUMrhOUeWm_mQQZEornOV0IrqHX9vEnx-RCoWBk3Zda8WqCNRU2NgrG-u3RKtOxjaTIW2NQLrnU8qmJM0TdYVjnXN4tq91ifewAp8_CuiyCLw6D7pv86v_tMUzLbq-kK-UEKMjw1YjiruuDEgLNYp1REtcP41bcKqFQ78Vfk0NDCZffn1KMxVw3qsSCX0lghUob_fR3sL9B3rSsac77K29Rvaq_6-YuWGw8mpL_8Gsf5msC/http%3A%2F%2Fverisigninc.com%2F> On 7/12/21, 6:47 AM, "internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>" <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> wrote: A new version of I-D, draft-gould-regext-rdap-redacted-00.txt has been successfully submitted by James Gould and posted to the IETF repository. Name: draft-gould-regext-rdap-redacted Revision: 00 Title: Redacted Fields in the Registration Data Access Protocol (RDAP) Response Document date: 2021-07-12 Group: Individual Submission Pages: 24 URL: https://secure-web.cisco.com/1K328CySVpeAdQz8KNkRu7ncZhdPUaP8fTNul1LMbiFUNsZqIiaoBcPF_OjIj35fkwT9gDpIgI0UtjP0gvmatvP7d36VCx0jJYMqBEmzxelQ-PIg05Xfql3NqrTwSL4Q0rFMFYnngRChk0aHwtRt906uYqS23NjDteP_jrqxZQGqLQKBOv5Vgb43XRE8Ihgi27Ri4OozGV8C0GXEqGrZ7b95LpT-V-dDS3cIXEQUtIo-eTKJ-ZWGQKtVrYCNA9LBg/https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-gould-regext-rdap-redacted-00.txt Status: https://secure-web.cisco.com/1XGKSPZDnB5CHFRYeBm5qN0ACnFvTe1ZG2O2llFvSrZi7q2nOKGpyNnv6E_m3_MO7ccF7VFbViZPAwR4-AhBS-dsgLlgR1UWs2nad61Rru2hB4B4t9trR3YvtBbMbIodX7jHHjrS9fI-dpAMLzEEana8BOyRiZ39Ri-bvZ5UE_IFT9l3WqspNfRqWS9oSUFqY-vVM_ewYcTLOwSxMvY7FXlWt6BqjHa2qdBNgIIZeu7bRKJ5BQ06B4AIe9y0IyRKd/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-gould-regext-rdap-redacted Html: https://secure-web.cisco.com/1B_5eD2QiPrj83T06F7L4QtU3TiyBUmvF_j2dCXin9B7g8aMHESwA458zvkfsNCSZ3H37ObhlCl4HDgTiq7FCk0m7tAWuFQNAMEz0gzbNML-5hfGMJS-SZMuc6OuAnS8mkBUX_yXOBGkWsB1aiFk9UNolX6_o5zxWepxXz9nn-00BrxxTi1kyaRTiPZNpjLbdBMA2T4pNfhbpIfvRnlq-ewNw77MmMocKIy0Out4Cqwdx_6T6yGu-QwVjoPehH4Pt/https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-gould-regext-rdap-redacted-00.html Htmlized: https://secure-web.cisco.com/1p7JRanlgcayeNYcfSxig8HPTMLyO10UtuXnj8prHHxr5LSwZTK_a-LVs8jabLArSP8K_rmlxZ1UXoHYVMmGFjCculzG_bqoCTMIdWMI3hZ2nNAgnlOeQ9Py-vf3Jw_R533LAJqInMLvnEvhSaQlcJWdR7ttfJNgVhe04-dcLQt5GX8eCG-_W4P8LLeD1v8jcEH0CxWlSoiZ1Mfo-4sI5sOAnym_uiUApuKbmHO5njJY85ABtWiPCmHlxlVZghFOL/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-gould-regext-rdap-redacted Abstract: This document describes an RDAP extension for explicitly identifying redacted RDAP response fields, using JSONPath as the default expression language. The IETF Secretariat _______________________________________________ regext mailing list regext@ietf.org<mailto:regext@ietf.org> https://secure-web.cisco.com/16CgORZ2fFT66iHVzi7kyPw6Mv9G4kbF2Mgjac7T3eRZU23t5cU1UejDzEN_N3uECtWwJmmdzTr2tME-2vLucgYzZURc3yY1pPZhyd2OA6EY1f6pWeTEY0LdnOjA4EUtLZsfr7Smu9GrMZbxiX5T10srKCMu0VsIZMNNswinhqo37gohlXQnOq_S3LmiXJlIt3gFaIYPid2NMKMibEzU_dtV-3t1v4BgghjRXsqsJQlv9cZq6k-Txw_wXVf2ekDS0/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext