W3C home > Mailing lists > Public > public-webappsec@w3.org > June 2015

Re: CfC: Mixed Content to PR; deadline July 6th.

From: Mike West <mkwst@google.com>
Date: Mon, 22 Jun 2015 20:05:57 +0200
Message-ID: <CAKXHy=eVx=SKaXYmd=8Eco9HC5JynHWjOHqwDzKX3iqfsPpKDw@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>, Dan Veditz <dveditz@mozilla.com>, Wendy Seltzer <wseltzer@w3.org>, Brad Hill <hillbrad@gmail.com>, Kristijan Burnik <burnik@google.com>, Brian Smith <brian@briansmith.org>, Ryan Sleevi <sleevi@google.com>
On Mon, Jun 22, 2015 at 7:45 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Mon, Jun 22, 2015 at 7:17 AM, Mike West <mkwst@google.com> wrote:
> > If you have any comments or concerns regarding this CfC, please reply to
> > public-webappsec@w3.org by the end of June 6th at the latest. Silence
> will
> > be interpreted as glowing praise and full-throated agreement, but I'd
> > encourage you to praise full-throatedly, glowingly, _and_ explicitly on
> the
> > list. :)
>
> Looks pretty good.
>

I'll take it!


> Are there bugs on WebSocket to get the specification updated to take
> Mixed Content into account?
>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28841

It's not entirely clear to me where to file a bug on the protocol. Is there
a group working on an update to RFC 6455?


> The phrase "That is certainly the intent." can be removed.
>
> Also, you need to replace "TLS state" with "HTTPS state". We decided
> to rename that term together a while back to avoid OE confusion.
>

Done and done:
https://github.com/w3c/webappsec/commit/d9c40227d28c42dbf9262abfa69427f940fbcb78

Thanks!

-mike
Received on Monday, 22 June 2015 18:06:45 UTC

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