idnits 2.17.1 draft-ietf-hybi-thewebsocketprotocol-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 12 instances of too long lines in the document, the longest one being 9 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (August 23, 2011) is 4602 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110) ** Obsolete normative reference: RFC 3490 (Obsoleted by RFC 5890, RFC 5891) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-06) exists of draft-ietf-websec-origin-02 Summary: 6 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 HyBi Working Group I. Fette 3 Internet-Draft Google, Inc. 4 Intended status: Standards Track A. Melnikov 5 Expires: February 24, 2012 Isode Ltd 6 August 23, 2011 8 The WebSocket protocol 9 draft-ietf-hybi-thewebsocketprotocol-11 11 Abstract 13 The WebSocket protocol enables two-way communication between a client 14 running untrusted code running in a controlled environment to a 15 remote host that has opted-in to communications from that code. The 16 security model used for this is the Origin-based security model 17 commonly used by Web browsers. The protocol consists of an opening 18 handshake followed by basic message framing, layered over TCP. The 19 goal of this technology is to provide a mechanism for browser-based 20 applications that need two-way communication with servers that does 21 not rely on opening multiple HTTP connections (e.g. using 22 XMLHttpRequest or