Hi James,
some comments from my side:
1) With reference to the following sentence in section 3.2:
such as "" for a jCard [RFC7095] Text ("text") property or null for non-Text
("text") properties.
it seems to me that RFC7095 doesn't include a clear statement in that sense.
Some VCard types (i.e. text, uri, language-tag, utc-offset, and all date
type variants) are mapped to JSON strings, other VCard types are mapped
to other JSON primitive types (i.e number, boolean).
Given that, apart from "fn" that is a required "text" property, a JSON
string can be either null or empty.
For sure, the use of the empty string makes more sense for "text"
values, but null value is not clearly prohibited for the other VCard
properties mapped to JSON strings.
2) WIth regard to redaction by replacement method, should the example in
Fig.7 be updated as in the following:
OLD
"redacted": [
{
"name": {
"type": "Registrant Email"
},
"path":"$.entities[?(@.roles[0]=='registrant')].
vcardArray[1][?(@[0]=='email')][3]",
"replacementPath":"$.entities[?(@.roles[0]=='registrant')].
vcardArray[1][?(@[0]=='contact-uri')][3]",
"pathLang": "jsonpath",
"method": "replacementValue",
}
]
NEW
"redacted": [
{
"name": {
"type": "Registrant Email"
},
"path":"$.entities[?(@.roles[0]=='registrant')].
vcardArray[1][?(@[0]=='email')]",
"replacementPath":"$.entities[?(@.roles[0]=='registrant')].
vcardArray[1][?(@[0]=='contact-uri')]",
"pathLang": "jsonpath",
"method": "replacementValue",
}
]
Based on the example in Fig.6, the "email" property instead of the
"email" value is replaced.
3) Would rephrase the following sentence in section 4.2
OLD
The "redacted" member contains an array of redacted
objects with the following child members
NEW
The "redacted" member contains an array of
objects with the following child members
The objects in the "redacted" array are not redacted but rather the
response fields represented by those objects.
4) Wonder if section 6.2 should include an entry for pathLang.
5) A last feedback about JSONPath Considerations:
5.a) Is it allowed to use wildcard in JSONPath? Think it could be useful
especially when the same redaction rule is applied to each result of a
search response.
For example, if a registry policy consists in redacting all the domain
handles, the "redacted" content could simply be:
"redacted": [
{
"name": {
"type": "Registry Domain ID"
},
"path": "$.domainSearchResults[*].handle",
"pathLang": "jsonpath",
"method": "removal",
"reason": {
"type": "Server policy"
}
}
]
5.b) I consider this a corner case so feel free to ignore it ;-)
The VCard label property (as well as the JSContact fullAddress property)
is usually derived from the postal address information.
When the postal address is partially redacted, what should be the label
value and the related redaction method?
If you think it's worth managing this case, I would suggest a
conservative solution: the label property should be omitted and the
redaction method should be "removal".
Hope it could be helpful.
Best,
Mario
Il 10/11/2022 19:38, Gould, James ha scritto:
This is a formal request to start the WGLC for
draft-ietf-regext-rdap-redacted. There is a normative reference to
draft-ietf-jsonpath-base, which has a JSONPath working group November
milestone. draft-ietf-jsonpath-base looks stable and can progress in
parallel with draft-ietf-regext-rdap-redacted.
Thanks,
--
JG
*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/>
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
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
