On 1/27/23 5:56 PM, Rob Sayre wrote:
Hi,
Peter Saint-Andre wrote:
> It's unclear to me what kind of text folks want in this document
I think the document should direct implementations
Which ones? TLS clients, TLS servers, TLS libraries, certificate
authorities, certbots, all of the above?
to follow UTS-46 and
the WHATWG.
Well, we would need to specify what it means to "follow" UTS-46 and the
WHATWG (does this mean the WHATWG's URL specification?) in the context
of certificate generation and validation.
That is what works.
Well, IDNA2008 works for many applications and UTS-46 works for many
other applications. I'm not as certain as you are that one of these
technologies works and the other does not. Can you produce evidence
that, by implication, IDNA2008 does not work? What problems does it not
solve?
If those documents are not relevant, take them out of the draft.
We added mentions of those documents because someone who is deeply
versed in internationalization reviewed rfc6125bis and suggested that we
point out the existence of different approaches to IDNs (i.e., IDN2008
and UTS-46), specifically with regard to security implications.
Peter
_______________________________________________
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta
