LGTM1
On Tue, Sep 26, 2023 at 9:42 PM David Adrian wrote:
> To make it easier for people who are not following the IETF to understand
> the impact on browsers and Chrome, I have provided a brief explainer:
> https://github.com/dadrian/ech-chrome
>
Thanks for the explainer. A brief paragraph RE
To make it easier for people who are not following the IETF to understand
the impact on browsers and Chrome, I have provided a brief explainer:
https://github.com/dadrian/ech-chrome
On Wed, Sep 20, 2023 at 1:48 PM David Adrian wrote:
> I'll note that Chrome does not require that the HTTPS RR be
I'll note that Chrome does not require that the HTTPS RR be resolved over
DoH to use ECH, under the argument that some ECH is still better than no
ECH. Firefox only uses ECH when they are able to query HTTPS RR records
over encrypted DNS.
On Wed, Sep 20, 2023 at 12:54 PM David Benjamin
wrote:
>
I think this discussion is conflating two different things:
1. Whether some content (sections 1 and 3 of the spec) was extracted into
an explainer.
2. Particular questions about the spec that Blink API owners wanted answers
for.
With the expectation that, had there been something under an
We are fine with being flexible with the details when the defaults don't
work out, but every field/question has an underlying purpose that we try
to satisfy through some means. Sometimes some fields might seem
superfluous, but the explainer field is one that is always valuable.
The
> Could we please request a signal?
Done (and positive!). I had forgotten to add it to Chrome Status.
https://github.com/WebKit/standards-positions/issues/46
As for the explainer, between sending the I2S and now, I updated the Chrome
Status description to cover most of what David Benjamin
On Mon, Sep 18, 2023 at 10:06 AM Yoav Weiss wrote:
>
>
> On Sat, Sep 16, 2023 at 5:35 PM David Benjamin
> wrote:
>
>> On Sat, Sep 16, 2023 at 1:12 AM Yoav Weiss
>> wrote:
>>
>>>
>>>
>>> On Fri, Sep 15, 2023 at 10:05 PM Mike Taylor
>>> wrote:
>>>
On 9/11/23 6:34 PM, 'David Adrian' via
On Sat, Sep 16, 2023 at 5:35 PM David Benjamin
wrote:
> On Sat, Sep 16, 2023 at 1:12 AM Yoav Weiss wrote:
>
>>
>>
>> On Fri, Sep 15, 2023 at 10:05 PM Mike Taylor
>> wrote:
>>
>>> On 9/11/23 6:34 PM, 'David Adrian' via blink-dev wrote:
>>>
>>> Contact emails david...@chromium.org,
On Sat, Sep 16, 2023 at 1:12 AM Yoav Weiss wrote:
>
>
> On Fri, Sep 15, 2023 at 10:05 PM Mike Taylor
> wrote:
>
>> On 9/11/23 6:34 PM, 'David Adrian' via blink-dev wrote:
>>
>> Contact emails david...@chromium.org, dadr...@google.com
>>
>> Explainer None
>>
>> I think a short explainer that
On Fri, Sep 15, 2023 at 10:05 PM Mike Taylor wrote:
> On 9/11/23 6:34 PM, 'David Adrian' via blink-dev wrote:
>
> Contact emails david...@chromium.org, dadr...@google.com
>
> Explainer None
>
> I think a short explainer that outlines what this is and what's the
typical flow would be helpful.
On 9/11/23 6:34 PM, 'David Adrian' via blink-dev wrote:
Contact emails
david...@chromium.org, dadr...@google.com
Explainer
None
Specification
https://datatracker.ietf.org/doc/html/draft-ietf-tls-esni
Summary
The TLS Encrypted ClientHello (ECH)
Contact emailsdavid...@chromium.org, dadr...@google.com
ExplainerNone
Specificationhttps://datatracker.ietf.org/doc/html/draft-ietf-tls-esni
Summary
The TLS Encrypted ClientHello (ECH) extension enables clients to encrypt
ClientHello messages, which are normally sent in cleartext, under a
12 matches
Mail list logo
