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

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

From: Brian Smith <brian@briansmith.org>
Date: Tue, 7 Jul 2015 11:08:32 -0400
Message-ID: <CAFewVt6tfA+Zno-xUu_CoW49Yrzf3tG_zQTVYExvRhyw2yLLuw@mail.gmail.com>
To: Ryan Sleevi <sleevi@google.com>
Cc: Mike West <mkwst@google.com>, Anne van Kesteren <annevk@annevk.nl>, "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>

We (Mike and I, at least) already had a debate like this months ago. Look
it up if you're interested in it.

My point is that there are not two implementations (IIUC) of the feature
described in 5.3 and the stuff related to deprecated TLS stuff, so,
according to my understanding of the charter, it has to be removed to
advance to PR:

"To advance to Proposed Recommendation, each specification is expected to
have two independent implementations of each feature described in the
specification." - http://www.w3.org/2015/03/webappsec-charter-2015.html

If there are two implementations, I don't think a debate will get anything
changed. And if there aren't two implementations, it has to be removed. So,
I don't think it's worth debating any more.

Now, from Anne's latest message on the thread, it seems like we may very
well end up resetting the process back to "working draft" status so that we
can debate the "fetch" issue again. If so, then I guess it may make sense
to debate this issue too.

Received on Tuesday, 7 July 2015 15:09:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:49 UTC