[hybi] AUTH48 changes to the WebSocket protocol spec

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 12 December 2011 21:23 UTC

Return-Path: <alexey.melnikov@isode.com>
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 2259B21F8560 for <hybi@ietfa.amsl.com>; Mon, 12 Dec 2011 13:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMqr93rJw2ZY for <hybi@ietfa.amsl.com>; Mon, 12 Dec 2011 13:23:52 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5A821F858C for <hybi@ietf.org>; Mon, 12 Dec 2011 13:23:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1323725031; d=isode.com; s=selector; i=@isode.com; bh=4EPVN+1+29C9YCS05ky5nl55jiXa5Kacpzfz5KZR+Fc=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=XyOII8udTKBKj3/gK/4tHi3IpuhsrsvfDzLLfzGVdv9z5dVXX1cJdxz7IFA9Ac5EqBm9bU NOdOQt9Qfw7XeK3rqd5xbi/QVm1NAZX9d8yR8p71XWOeIx6oKAE1wgX1CKpz09Msa8CUmq jxAOY6wb7HStNwaM/9oyS0/0fTVbne8=;
Received: from [188.29.206.49] (188.29.206.49.threembb.co.uk [188.29.206.49]) by rufus.isode.com (submission channel) via TCP with ESMTPSA id <TuZw4wBaK3so@rufus.isode.com>; Mon, 12 Dec 2011 21:23:49 +0000
Message-ID: <4EE670DC.9010607@isode.com>
Date: Mon, 12 Dec 2011 21:23:40 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
To: hybi@ietf.org
References: <02F41063-6221-4EB8-A4E4-2E396A6B946C@zaphoyd.com> <4ED4E9CB.3040106@isode.com> <CAH_y2NHsOK5Bvf8NO0qd9oSgzN67dEtOtcVKdOROoTLZN0b14w@mail.gmail.com> <4ED56B6F.7000504@stpeter.im>
In-Reply-To: <4ED56B6F.7000504@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [hybi] AUTH48 changes to the WebSocket protocol spec
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: Mon, 12 Dec 2011 21:23:53 -0000

On 29/11/2011 23:31, Peter Saint-Andre wrote:
> On 11/29/11 3:45 PM, Greg Wilkins wrote:
>> On 30 November 2011 01:18, Alexey Melnikov<alexey.melnikov@isode.com>  wrote:
>>> 1011
>>>       1011 indicates that a server is terminating the connection
>>>       because it has encountered an unexpected condition which prevented
>>>       it from fulfilling the request.
>> +1
>>
>> what is the process path from here?
> This code (and a few others) will be slipped into the spec during "AUTH48":
>
> http://www.rfc-editor.org/pubprocess.html#auth48
>
>>    Do we have any other changes needed?
> Some slight editorial issues, registration process clarifications, and
> the close codes that have been discussed on the list. Alexey and Ian can
> provide more details.
To summarize changes between -17 and RFC 6455:

1). Various spelling fixes, corrected punctuation, editorial 
clarifications. Correct placement of references. Consistent marking of 
header fields, updated references, etc.
2). Fixed description of when %-encoding of "#" is needed in ws: URIs to 
be consistent with URI encoding rules
3). Clarified that the "Upgrade" header field can include other keywords 
(and not just be equal to "websocket"), as per RFC 2616.
4). Added missing frame code 0 (frame continuation to the Frame ABNF)
5). Added 2 new close codes as per the mailing list discussions:

1011 - indicates that a server is terminating the connection because
it encountered an unexpected condition that prevented it from
fulfilling the request.

1015 - is a reserved value and MUST NOT be set as a status code in a
Close control frame by an endpoint. It is designated for use in
applications expecting a status code to indicate that the
connection was closed due to a failure to perform a TLS handshake
(e.g., the server certificate can't be verified).

6). Updated IANA registration procedure/text in section 11.6 (WebSocket 
Version Number Registry). The new text better reflects what the WG was 
doing and it seemed clearer to IANA.