> -----Original Message----- > From: regext <regext-boun...@ietf.org> On Behalf Of Mario Loffredo > Sent: Friday, March 31, 2023 7:45 AM > To: regext@ietf.org > Subject: [EXTERNAL] [regext] Redacting JSContact uid in RDAP - Updated > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content is > safe. > > Hi folks, > > just reported below all the options (including Gavin's proposal) and the > preferences given thus far. > > Please, express your preference(s). > > Thanks a lot in advance. > > > 1) Redacting by Empty Value method > > 2) Making uid optional in RDAP and then redacting by Removal method > > - J.Gould > > 3) Recommending the use of UUIDs that prevent from correlation (e.g. > either randomly generated or nil UUIDs) > > 4) Redacting by using a registered URN in the IANA namespace (e.g. > "urn:ietf:params:json:rdap+jscontact:uidRedacted") > > - G. Brown > > 5) Anything else ?
[SAH] Which of these options is the least likely to break a JSContact parser? My preference is leans towards whichever option or options will be the most compatible with implementations of JSContact such that any RDAP complexity is handled in the RDAP-implementing software. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
