On Fri, Jun 14, 2024 at 10:36 AM Emily Stark wrote:
> (Apologies for the slow response, we had some OOOs)
>
> On Mon, Jun 3, 2024 at 7:55 PM Mike Taylor wrote:
>
>> Hi Emily,
>>
>> A few questions inline:
>> On 6/1/24 5:05 AM, Emily Stark wrote:
>>
&
(Apologies for the slow response, we had some OOOs)
On Mon, Jun 3, 2024 at 7:55 PM Mike Taylor wrote:
> Hi Emily,
>
> A few questions inline:
> On 6/1/24 5:05 AM, Emily Stark wrote:
>
> Contact emails est...@google.com, jdebla...@google.com, dadr...@google.com
> , l.
Contact emailsest...@google.com, jdebla...@google.com, dadr...@google.com,
l...@chromium.org, tito...@chromium.org, cl...@chromium.org,
mk...@chromium.org, v...@chromium.org
Explainer
https://github.com/WICG/private-network-access/blob/master/explainer.md
Specificationhttps://wicg.github.io/priva
Update: this will likely now be deprecated in M106 and removed in M107;
using the Deprecation Reporting mechanism is proving to be significantly
more complicated than I expected.
On Tue, Jul 12, 2022 at 1:52 PM Emily Stark wrote:
> Hi Joe -- I'm planning to deprecate in M105 and remove
6)%20678-7195>
> *If an API's not documented it doesn't exist.*
>
>
> On Fri, Jul 8, 2022 at 9:31 AM Emily Stark wrote:
>
>> Contact emailsest...@chromium.org
>>
>> ExplainerNone
>>
>> Specificationhttps://datatracker.ietf.org/doc/rfc
On Fri, Jul 8, 2022 at 9:34 AM Yoav Weiss wrote:
> What deprecation/removal timelines did you have in mind?
>
Since there's no user-visible impact, I was hoping to do a console message
in M105 and then remove in M106.
>
> On Fri, Jul 8, 2022 at 6:31 PM Emily Stark wr
Contact emailsest...@chromium.org
ExplainerNone
Specificationhttps://datatracker.ietf.org/doc/rfc9163
Summary
Expect-CT is an HTTP header that allowed websites to opt in to Certificate
Transparency enforcement before it was enforced by default. It also has
reporting functionality to help develo
I want to note that there are some pretty big open questions in
https://github.com/w3c/webtransport/issues/349. I think we might want to
have more restrictions on the allowed types of certificates than the spec
currently outlines, and introducing those restrictions after shipping the
feature would
