Hi James,
honestly don't think that the "uid" field will ever get redacted, I
mean, it's recommended to be an UUID and normally UUIDs are opaque. Both
UUIDv3 (MD5) and UUIDv5 (SHA1) can be derived from a string (like for
example the entity handle) so there is no need to generate and store a
new value. If it was optionally represented as an URI, a reasonable
value could be the URL of the entity lookup whose response includes the
contact card. Since the entity lookup is based on the entity handle
value and such a value is a registry unique identifier, either in this
case, the "uid" redaction seems very unlikely to me. Anyway, I can't
completely exclude such a corner case. In the unlikely event that the
"uid" field is redacted, I would process it in the same way as the jCard
"fn" property.
Both of them are required text fields so don't see why they should be
processed differently. In addition, there is a requirement from calext
about keeping uid mandatory.
Best,
Mario
Il 03/01/2023 17:33, Gould, James ha scritto:
Mario,
I don't see any need to add a dependency between draft-ietf-regext-rdap-jscontact and
draft-ietf-regext-rdap-redacted, but this does add an interesting case for
draft-ietf-regext-rdap-redacted with redacting a required JSON member. Do you see the
requirement to be able to redact the required "uid" JSContact property? If
there is the need to redact it, then wouldn't that make the case for it not to be defined
as mandatory in draft-ietf-calext-jscontact? I'm not sure whether providing an empty
value via the Redaction by Empty Value Method is any better than simply removing it via
the Redaction by Removal Method. We would need to first determine whether there is the
need to cover the case of redacting a required JSON member in
draft-ietf-regext-rdap-redacted and if so how best to handle it.
Thanks,
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext