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
gt; what it is trying to convey.
>
>
>
> Thanks,
>
> Corey
>
>
>
>
>
> *From:* Rob Sayre
> *Sent:* Thursday, January 26, 2023 7:58 PM
> *To:* Corey Bonnell
> *Cc:* Peter Saint-Andre ; uta@ietf.org
> *Subject:* Re: [Uta] Browser behavior in draft-ietf-uta-rfc612
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
ndre ; uta@ietf.org
Subject: Re: [Uta] Browser behavior in draft-ietf-uta-rfc6125bis
Hi,
I'll firstly treat this message as a signal of rough consensus, since I totally
agree with what you phrased as "operational reality". But, I must note that the
WHATWG document you linked* has a gre
icode.org/reports/tr46/#Mapping
>
>
>
> *From:* Rob Sayre
> *Sent:* Thursday, January 26, 2023 4:59 PM
> *To:* Peter Saint-Andre
> *Cc:* Corey Bonnell ; uta@ietf.org
> *Subject:* Re: [Uta] Browser behavior in draft-ietf-uta-rfc6125bis
>
>
>
>
>
>
&g
: Rob Sayre
Sent: Thursday, January 26, 2023 4:59 PM
To: Peter Saint-Andre
Cc: Corey Bonnell ; uta@ietf.org
Subject: Re: [Uta] Browser behavior in draft-ietf-uta-rfc6125bis
On Thu, Jan 26, 2023 at 1:39 PM Peter Saint-Andre mailto:stpe...@stpeter.im> > wrote:
On 1/26/23 2:28 PM, Rob
On Thu, Jan 26, 2023 at 1:39 PM Peter Saint-Andre
wrote:
> On 1/26/23 2:28 PM, Rob Sayre wrote:
> > Since you phrased your message as a question, I will answer. I don't
> know.
> >
> > But what the draft says also does not align with your last check.
>
> How so? The draft currently makes no
On 1/26/23 2:28 PM, Rob Sayre wrote:
Since you phrased your message as a question, I will answer. I don't know.
But what the draft says also does not align with your last check.
How so? The draft currently makes no claims about what is implemented in
browsers, only notes that there can be
On Behalf Of *Rob Sayre
> *Sent:* Thursday, January 26, 2023 2:55 PM
> *To:* Peter Saint-Andre ; uta@ietf.org
> *Subject:* [Uta] Browser behavior in draft-ietf-uta-rfc6125bis
>
>
>
> Hi,
>
>
>
> I just filed an issue* to track treatment of browser behavior and WHATWG
>
,
Corey
From: Uta On Behalf Of Rob Sayre
Sent: Thursday, January 26, 2023 2:55 PM
To: Peter Saint-Andre ; uta@ietf.org
Subject: [Uta] Browser behavior in draft-ietf-uta-rfc6125bis
Hi,
I just filed an issue* to track treatment of browser behavior and WHATWG specs
in
https://www.ietf.org
Hi,
I just filed an issue* to track treatment of browser behavior and WHATWG
specs in
https://www.ietf.org/archive/id/draft-ietf-uta-rfc6125bis-10.html
It's probably easier to track that way, whatever the resolution might be.
thanks,
Rob
*
13 matches
Mail list logo
