On 8/20/24 09:15, Gould, James wrote:
Andy,
In reviewing the updates to draft-ietf-regext-rdap-extensions, I believe that we need to
reconsider the criteria for the RDAP JSON Registry values. Based on the types initially
defined, the use of lowercase only values may make sense, but for the recently registered
values from the RDAP Profile for redaction includes mixed case to exactly match the
values in the source policy. The use of lowercase is a non-normative "should",
so would future registration requests that have justification for mixed case run into an
issue and be considered a violation of the criteria? Should we consider updating the
criteria in RFC 9083 based on the implementation experience of the recent registrations
or provide additional clarity in draft-ietf-regext-rdap-extensions?
Thanks,
James,
Those are all good points, and I am unaware of any impact on
implementations from the mixed case registrations. I think the need to
match text from another document is a good use case and overrides any
desired "style". I'll change this section in a PR and pass the link when
it is up. Until then I have created this tracking issue.
https://github.com/anewton1998/draft-regext-rdap-extensions/issues/29
Thanks for the input.
-andy
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
