RE: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-17.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Woops!  That's not right...

   ws-frame                = frame-fin           ; 1 bit in length
                             frame-rsv1          ; 1 bit in length
                             frame-rsv2          ; 1 bit in length
                             frame-rsv3          ; 1 bit in length
                             frame-opcode        ; 4 bits in length
                             frame-masked        ; 1 bit in length
                             frame-payload-length   ;  7 bits in length
                             [ frame-masking-key ]  ; 16 or 64 bits in length
                             frame-payload-data     ; n * 8 bits in length,
                                                    ; where n >= 0

frame-payload-length is 7, 16 or 64 bits in length.
frame-masking-key is 32 bits in length

The comments next to the actual productions are correct.  Except that frame-opcode-non-control is missing the length comment (4 bits).

> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Friday, September 30, 2011 5:22 AM
> To: i-d-announce@ietf.org
> Cc: hybi@ietf.org
> Subject: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-17.txt
> 
> 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
>                           Alexey Melnikov
> 	Filename        : draft-ietf-hybi-thewebsocketprotocol-17.txt
> 	Pages           : 77
> 	Date            : 2011-09-30
> 
>    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.  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 <iframe>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-17.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-17.txt
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux