Hi James, On Mon, May 23, 2022 at 12:25:06PM +0000, Gould, James wrote: > Thank you for bringing this up, since I was overly focused on the > Domain Name Registries (DNRs). Will the Regional Internet > Registries (RIRs) redact via draft-ietf-regext-rdap-redacted, and > will the Redaction by Replacement Value Method be used?
At least for APNIC, we don't have any plans to implement this at the moment, but there is a reasonable chance we'll want to make use of it in the future. As far as the other RIRs go, I don't know of any concrete plans that they have. > Signaling the replacement of a property is straight forward, with > Figure 5 as an example. The main complexity comes with replacing > the property using a different property, with Figure 7 as an > example. Do you have the path reference the property that is being > replaced (email), the property that is replacing (contact-uri), or > do you reference both (email and contact-uri)? Figure 7 references > the property that is replacing (contact-uri), but a case could be > made to point to the property that is being replaced. In the end, > I'm thinking that it may be better to add another optional path > (replacementPath) for use of pointing to the property that is > replacing (contact-uri) the redacted property (email). > > Thoughts? This sounds like a good idea to me. If a server operator wants to replace different types of properties with different contact-uri properties, then indicating the type of the original property makes sense. It also simplifies things on the client side, because the redacted object will always contain a path to/for the original value being redacted. As far as the multiple-email case goes, I don't think there will be a guaranteed way to use the "redaction by replacement value" method for that, because there may not be any way to distinguish the original property that is being replaced. In that sort of situation, I think falling back on the "redaction by empty value" method will be sufficient, though. -Tom _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
