On Thu, Aug 17, 2023 at 4:43 AM Mario Loffredo
<[email protected]> wrote:
>
> Hi Andy,
>
> could it work for you and Scott if I changed the text in Section 12.2.1 as in
> the following ?
>
> OLD
>
> Creators of either new RDAP reverse searches or new mappings for
> registered reverse searches SHOULD NOT replicate functionality
> already available by way of other documents referenced in these
> registries.
>
> NEW
>
> Creators of either new RDAP reverse searches or new mappings for
> registered reverse searches SHOULD NOT replicate functionality
> already available by way of other documents referenced in these
> registries. Likewise, they SHOULD NOT map a registered reverse search
> property
> to a response field with a meaning other than that of the response fields
> referenced by the mappings already registered for that property.
> In other words, all the mappings for a reverse search property MUST
> point to response fields with the same meaning.
Could I offer a slight modification?
NEW
Creators of either new RDAP reverse searches or new mappings for
registered reverse searches SHOULD NOT replicate functionality
already available by way of other documents referenced in these
registries. Creators MAY register additional reverse search mappings for
existing properties, but they SHOULD NOT map a registered reverse
search property
to a response field with a meaning other than that of the response fields
referenced by the mappings already registered for that property.
In other words, all the mappings for a reverse search property MUST
point to response fields with the same meaning.
-andy
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
