Possibly relevant, not sure if helpful:
- https://github.com/whatwg/url/issues/341
- https://github.com/whatwg/url/issues/733
On Fri, Jan 27, 2023, 7:26 PM Rob Sayre wrote:
> On Fri, Jan 27, 2023 at 5:16 PM Peter Saint-Andre
> wrote:
>
>> > That is what works.
>>
>> Well, IDNA2008 works for
On Fri, Jan 27, 2023 at 5:16 PM Peter Saint-Andre
wrote:
> > 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
>
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?
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 to follow UTS-46 and the
WHATWG. That is what works.
If those documents are not relevant, take them out of the draft.
thanks,
Rob
On 1/27/23 1:43 PM, Viktor Dukhovni wrote:
But but I don't see how this is relevant to the security of certificate
validation. If the application wants to authenticate "☕.example", it
matches the A-label form to the certificate. Perhaps it should have
refused to communicate with "☕.example",
On 26/1/2023 7:58 pm, Rob Sayre wrote:
For instance, ☕.example becomes xn--53h.example and not failure.
[UTS46] [RFC5890]"
Yes, thus, for example, Postfix via libicu (my terminal doesn't actually
display "☕", but it was part of the input argument anyway):
$ posttls-finger "☕.example"
On Fri, Jan 27, 2023 at 11:16 AM Rob Sayre wrote:
> Hi,
>
> I'm a little confused as well, but the character is covered in recent
> UTS-46 test suites. I looked at this one:
> https://www.unicode.org/Public/idna/15.0.0/
>
> I tried to read all of UTS-46, but it made me want to throw my computer
Hi,
I'm a little confused as well, but the character is covered in recent
UTS-46 test suites. I looked at this one:
https://www.unicode.org/Public/idna/15.0.0/
I tried to read all of UTS-46, but it made me want to throw my computer out
of the window. This must be what to follow for good
It appears that Corey Bonnell said:
>Thanks for the pointer to this text. It is a very interesting statement,
>mainly because the illustrative example does not align
>with the first sentence. The A-label “xn--53h” contains a single code point
>“Hot Beverage” U+2615. This code point was
>first
Hi Rob,
* "This document and the web platform at large use Unicode IDNA
Compatibility Processing and not IDNA2008. For instance, ☕.example becomes
xn--53h.example and not failure. [UTS46] [RFC5890]"
Thanks for the pointer to this text. It is a very interesting statement, mainly
10 matches
Mail list logo
