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

Where to file RFC 6455 bugs? [Was: Re: CfC: Mixed Content to PR; deadline July 6th.]

From: Arthur Barstow <art.barstow@gmail.com>
Date: Mon, 22 Jun 2015 15:05:27 -0400
Message-ID: <55885C77.9030409@gmail.com>
To: Mike West <mkwst@google.com>, Mark Nottingham <mnot@mnot.net>
CC: "public-webappsec@w3.org" <public-webappsec@w3.org>
On 6/22/15 2:05 PM, Mike West wrote:
> On Mon, Jun 22, 2015 at 7:45 PM, Anne van Kesteren <annevk@annevk.nl 
> <mailto:annevk@annevk.nl>> wrote:
>
>     On Mon, Jun 22, 2015 at 7:17 AM, Mike West <mkwst@google.com
>     <mailto:mkwst@google.com>> wrote:
>     > If you have any comments or concerns regarding this CfC, please
>     reply to
>     > public-webappsec@w3.org <mailto: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?

Perhaps the hybi list [1]?

Mark - can you help or give us a contact?

-ArtB

[1] http://www.ietf.org/mail-archive/web/hybi/current/maillist.html

>     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 19:05:57 UTC

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