Re: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-09.txt

The request MUST include a header with the name "Sec-WebSocket-
        Version".  The value of this header MUST be 8. _Note: Although a
        draft -09 was published, as -09 was comprised of editorial
        changes and not changes to the wire protocol, 9 was not used as
        a valid value for Sec-WebSocket-Version.  This value was
        reserved in the IANA registry but was not and will not be used.

Fette                   Expires December 15, 2011              [Page 30]

  <http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-09#page-31>Internet-Draft
          The WebSocket protocol                June 2011

        If subsequent changes to the wire protocol are necessary, 9 will
        be skipped to prevent confusion with the draft 9 protocol._

On Mon, Jun 20, 2011 at 9:21 PM, Greg Wilkins <gregw@intalio.com> wrote:

> Draft -09 still has examples that say:
>
> Sec-WebSocket-Version: 8
>
> I guess we also need to think about what we are going to do with this
> field as we approach "final"
>
> cheers
>
>
>
>
> On 14 June 2011 09:37,  <internet-drafts@ietf.org> wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the BiDirectional or
> Server-Initiated HTTP Working Group of the IETF.
> >
> >        Title           : The WebSocket protocol
> >        Author(s)       : Ian Fette
> >        Filename        : draft-ietf-hybi-thewebsocketprotocol-09.txt
> >        Pages           : 68
> >        Date            : 2011-06-13
> >
> >   The WebSocket protocol enables two-way communication between a client
> >   running untrusted code running in a controlled environment to a
> >   remote host that has opted-in to communications from that code.  The
> >   security model used for this is the Origin-based security model
> >   commonly used by Web browsers.  The protocol consists of an opening
> >   handshake followed by basic message framing, layered over TCP.  (In
> >   theory, any transport protocol could be used so long as it provides
> >   for reliable transport, is byte clean, and supports relatively large
> >   message sizes.  However, for this document, we consider only TCP.)
> >   The goal of this technology is to provide a mechanism for browser-
> >   based applications that need two-way communication with servers that
> >   does not rely on opening multiple HTTP connections (e.g. using
> >   XMLHttpRequest or &lt;iframe&gt;s and long polling).
> >
> >   Please send feedback to the hybi@ietf.org mailing list.
> >
> >
> > A URL for this Internet-Draft is:
> >
> http://www.ietf.org/internet-drafts/draft-ietf-hybi-thewebsocketprotocol-09.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> >
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-hybi-thewebsocketprotocol-09.txt
> > _______________________________________________
> > hybi mailing list
> > hybi@ietf.org
> > https://www.ietf.org/mailman/listinfo/hybi
> >
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>