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

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

From: Mike West <mkwst@google.com>
Date: Tue, 23 Jun 2015 09:24:02 +0200
Message-ID: <CAKXHy=cB=CEm8jxe5i3L2D0GYabLUXvf8uZBZ22=GdR=z8iVfw@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Arthur Barstow <art.barstow@gmail.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
On Tue, Jun 23, 2015 at 1:30 AM, Mark Nottingham <mnot@mnot.net> wrote:

> >> 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 HYBI WG is still open, but AIUI is closing *very* soon.
> I'd definitely send a message to the mailing list here. One of the
> outcomes *might* be an Errata, but be aware that the IETF has a pretty
> specific definition of errata - generally, technical changes in the
> document are out of scope, unless it's due to a decision that the WG made
> not being reflected in the document (which isn't the case here, AFAICT).
> Errata can be "held for document update", and it feels like that might be
> appropriate here.
> You could also argue that the WG should be held open to spin a quick
> revision of 6455. However, you'd likely need someone willing to be editor,
> since that group has become pretty quiet. Process-wise, it should be pretty
> simple.

Thanks Mark. I've pinged that list, and am now waiting in the non-members
submission queue of shame. :)

Let's see what they say.

Received on Tuesday, 23 June 2015 07:24:51 UTC

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