W3C home > Mailing lists > Public > public-webappsec@w3.org > February 2017

Re: [webappsec] Teleconference Agenda 21-FEB-2017

From: Mike West <mkwst@google.com>
Date: Tue, 21 Feb 2017 10:44:31 +0100
Message-ID: <CAKXHy=eYZjpti2EMJ46Yg64z=4mB-nd9X+zY1sVsW_DDjA0sUQ@mail.gmail.com>
To: Brad Hill <hillbrad@gmail.com>, Boris Zbarsky <bzbarsky@mit.edu>
Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>, Deian Stefan <deian@cs.ucsd.edu>
Thanks, Brad!

On Tue, Feb 21, 2017 at 12:33 AM, Brad Hill <hillbrad@gmail.com> wrote:

> Implementation status and outstanding issues for:
>   * Mixed Content
>   * Secure Contexts
>   * Upgrade Insecure Requests
>

I vaguely recall all of these being blocked in one way or another on
referencing Fetch, and on some things landing in W3C's HTML. I'll dig
around today to see if those landed in the meantime.

I believe that Boris also wanted some clarification/restructuring in Mixed
Content that I haven't gotten to yet. He probably also has opinions about
the clarity of these docs in general. :) (CCing Boris; Hi!)


> TOPIC: Call structure for 2017.  Back to spec-based calls?
>

This makes sense to me. Regular checkins are a nice forcing function for
getting things into shape.


> TOPIC: AOB
>

I'd point folks to some ongoing conversations in
https://github.com/w3c/webappsec-csp/issues/87,
https://github.com/whatwg/html/pull/2373,
https://github.com/w3c/webappsec-csp/issues/98,
https://github.com/whatwg/fetch/pull/465, and
https://github.com/whatwg/fetch/pull/464, which might be of interest.

-mike
Received on Tuesday, 21 February 2017 09:45:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:22 UTC