[hybi] -09: sending, closing, errors, extensions
Peter Saint-Andre <stpeter@stpeter.im> Thu, 16 June 2011 23:49 UTC
Return-Path: <stpeter@stpeter.im>
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 84D8A11E8119 for <hybi@ietfa.amsl.com>; Thu, 16 Jun 2011 16:49:22 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJq3wdd9nqgZ for <hybi@ietfa.amsl.com>; Thu, 16 Jun 2011 16:49:22 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E580511E80E8 for <hybi@ietf.org>; Thu, 16 Jun 2011 16:49:21 -0700 (PDT)
Received: from squire.local (dsl-179-111.dynamic-dsl.frii.net [216.17.179.111]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id BEE5C400A5 for <hybi@ietf.org>; Thu, 16 Jun 2011 17:49:46 -0600 (MDT)
Message-ID: <4DFA967D.5050308@stpeter.im>
Date: Thu, 16 Jun 2011 17:49:17 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "hybi@ietf.org" <hybi@ietf.org>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms070208030406070509080000"
Subject: [hybi] -09: sending, closing, errors, extensions
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 23:49:22 -0000
More comments... Section 6.1 states: 5. If the data is being sent by the client, the frame(s) MUST be masked as defined in Section 4.3. Section 6.2 states: Data frames received by a server from a client MUST be unmasked as described in Section 4.3. The word "unmasked" makes it sound like this contradicts the text in Section 6.1 -- as in, "must not be masked" as opposed to "the server shall remove the masking applied by the client". In Section 7, the text about the close /reason/ makes it sound as if an application might choose to show UTF-8 encoded data to an end user. That might lead the reader to think that language tagging might be necessary. Is it? In Section 8.2, there is no deterministic server behavior upon receiving data that is not valid UTF-8. Why? What use cases would motivate accepting such data instead of just closing the connection? Section 9.1 says: Any extension-token used MUST either be a registered token (registration TBD), or have a prefix of "x-" to indicate a private- use token. It's probably not a good idea to have "registration TBD" in a document that is going for IETF Last Call. :) Presumably a forward pointer to Section 11.6 would suffice. Do we really want to encourage use of "x-"? See here for relevant considerations (I plan to submit an updated version soon): http://tools.ietf.org/id/draft-saintandre-xdash-considered-harmful-01.txt Peter -- Peter Saint-Andre https://stpeter.im/
- [hybi] -09: sending, closing, errors, extensions Peter Saint-Andre
- Re: [hybi] -09: sending, closing, errors, extensi… Alexey Melnikov