Re: [hybi] -09: abstract and introduction

Iñaki Baz Castillo <ibc@aliax.net> Thu, 16 June 2011 12:06 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0CD11E8074 for <hybi@ietfa.amsl.com>; Thu, 16 Jun 2011 05:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.664
X-Spam-Level:
X-Spam-Status: No, score=-2.664 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id poHDb0TgSUPD for <hybi@ietfa.amsl.com>; Thu, 16 Jun 2011 05:06:36 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 02F6311E8070 for <hybi@ietf.org>; Thu, 16 Jun 2011 05:06:33 -0700 (PDT)
Received: by qwc23 with SMTP id 23so1019867qwc.31 for <hybi@ietf.org>; Thu, 16 Jun 2011 05:06:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.115.21 with SMTP id g21mr619213qcq.230.1308225993344; Thu, 16 Jun 2011 05:06:33 -0700 (PDT)
Received: by 10.229.230.129 with HTTP; Thu, 16 Jun 2011 05:06:33 -0700 (PDT)
In-Reply-To: <op.vw51kblbidj3kv@simon-pieterss-macbook.local>
References: <4DF91FCA.8060403@stpeter.im> <op.vw51kblbidj3kv@simon-pieterss-macbook.local>
Date: Thu, 16 Jun 2011 14:06:33 +0200
Message-ID: <BANLkTi=ddGU-Fwm1EwcYVFFiK=Xb5ys1Sw@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Simon Pieters <simonp@opera.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] -09: abstract and introduction
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: Thu, 16 Jun 2011 12:06:37 -0000

2011/6/16 Simon Pieters <simonp@opera.com>om>:
>>   If the |Sec-WebSocket-Accept|
>>   value does not match the expected value, or if the header is missing,
>>   or if the HTTP status code is not 101, the browser MUST NOT
>>   establish the connection and MUST NOT send WebSocket frames.
>
> All of section 1 is non-normative so shouldn't contain any requirements.

The question is: should such text be non-normative? WebSocket uses two
protocols:
1) HTTP for the handshake.
2) WebSocket "pure" protocol (masking, framing, WS messages, and so).

If this specification creates an extension for HTTP (as it does, point
1) it MUST specify certain HTTP response codes for certains
situations.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>