[hybi] -10: Typo and comment on 5.1 Client Requirements

Brian Raymor <Brian.Raymor@microsoft.com> Wed, 13 July 2011 04:58 UTC

Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9CE7421F8773 for <hybi@ietfa.amsl.com>; Tue, 12 Jul 2011 21:58:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 94lsrS3y3t0S for <hybi@ietfa.amsl.com>; Tue, 12 Jul 2011 21:58:49 -0700 (PDT)
Received: from smtp.microsoft.com (mail3.microsoft.com []) by ietfa.amsl.com (Postfix) with ESMTP id 20E8621F8764 for <hybi@ietf.org>; Tue, 12 Jul 2011 21:58:49 -0700 (PDT)
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com ( by TK5-EXGWY-E803.partners.extranet.microsoft.com ( with Microsoft SMTP Server (TLS) id; Tue, 12 Jul 2011 21:58:48 -0700
Received: from TK5EX14MBXC136.redmond.corp.microsoft.com ([]) by TK5EX14HUBC105.redmond.corp.microsoft.com ([]) with mapi id 14.01.0323.002; Tue, 12 Jul 2011 21:58:48 -0700
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Thread-Topic: -10: Typo and comment on 5.1 Client Requirements
Thread-Index: AcxBGNMdRar/bzrvT0CSbv50s/SpbQ==
Date: Wed, 13 Jul 2011 04:58:48 +0000
Message-ID: <61058FE4146DA54D8F2D7BF5495B77221DE2FF71@TK5EX14MBXC136.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 12 Jul 2011 22:23:15 -0700
Subject: [hybi] -10: Typo and comment on 5.1 Client Requirements
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 05:00:49 -0000

There is a typo in 7.1.7 - "instruted" intead of "instructed".

    7.1.7.  Fail the WebSocket Connection
    An endpoint MUST NOT continue to attempt to process data (including a responding Close frame) from the remote endpoint after being instruted to _Fail the WebSocket Connection_.

In 5.1.  Client Requirements, there is a _Fail the WebSocket Connection_ case for Sec-WebSocket-Extensions but not for Sec-WebSocket-Protocol:

  5.  If the response includes a "Sec-WebSocket-Extensions" header, and
       this header indicates the use of an extension that was not
       present in the client' handshake (the server has indicated an
       extension not requested by the client), the client MUST _Fail the
       WebSocket Connection_.  (The parsing of this header to determine
       which extensions are requested is discussed in Section 9.1.)

For symmetry, should there be a similar paragraph for Sec-WebSocket-Protocol -or- should the Sec-WebSocket-Extensions case be removed, since the correct behavior is also specified in the paragraph following this one:

   If the server's response does not conform to the requirements for the
   server's handshake as defined in this section and in Section 5.2.2,
   the client MUST _Fail the WebSocket Connection_.