Re: [hybi] thewebsocketprotocol #40 (new): Clarify binary/utf-8 mixed handling

John Tamplin <jat@google.com> Fri, 11 February 2011 21:49 UTC

Return-Path: <jat@google.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EC123A6A04 for <hybi@core3.amsl.com>; Fri, 11 Feb 2011 13:49:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.8
X-Spam-Level:
X-Spam-Status: No, score=-105.8 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqALYvnj66En for <hybi@core3.amsl.com>; Fri, 11 Feb 2011 13:49:11 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 2B3F83A699F for <hybi@ietf.org>; Fri, 11 Feb 2011 13:49:11 -0800 (PST)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id p1BLnQVH005848 for <hybi@ietf.org>; Fri, 11 Feb 2011 13:49:26 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1297460966; bh=peolxe3vumQWNmfReVOd+wEKlOc=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=usN3zcK7+7iGI12JUuS6YPFtNWsZzAW/5wtM+oZ9oqKQaw2qAJ9wT/3otSPYgZXLJ xTqUJUiT9OXIiV6EaaZbA==
Received: from gyd12 (gyd12.prod.google.com [10.243.49.204]) by hpaq11.eem.corp.google.com with ESMTP id p1BLn1WQ029122 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Fri, 11 Feb 2011 13:49:25 -0800
Received: by gyd12 with SMTP id 12so1336504gyd.17 for <hybi@ietf.org>; Fri, 11 Feb 2011 13:49:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Hdxo19PMt3EW6fiFz/5sMd9ZQswwVOUWYC48OClFrVI=; b=vrnVgyGVU+DiuF9W6TRrdSnaMK+d+N0VspM75W7g37IugCWk75gXWHEcc1etiFgHhX iBJgtpm4NkjuH6bhuMnw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=UgTd6JwJiKXpUELj5Falu3loxDceLFojSb0sqWTDRsZtOUUR9BIiDmUv7tb309Ag5w JrOlaQpJHoR34E8Ey9Ow==
Received: by 10.150.145.21 with SMTP id s21mr1102875ybd.434.1297460964382; Fri, 11 Feb 2011 13:49:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.206.19 with HTTP; Fri, 11 Feb 2011 13:49:04 -0800 (PST)
In-Reply-To: <CA566BAEAD6B3F4E8B5C5C4F61710C1126E0B5EB@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <063.e489b6d352cc1192d00acf7f96150ea7@tools.ietf.org> <buc6l61vlv7fh3s8nmu335g3d7897pcf0r@hive.bjoern.hoehrmann.de> <CA566BAEAD6B3F4E8B5C5C4F61710C1126E0501B@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com> <AANLkTinsXn=re_Ksr_wQdz4pyW2iXtUzBRz+nPYJtD-z@mail.gmail.com> <CA566BAEAD6B3F4E8B5C5C4F61710C1126E0B5EB@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
From: John Tamplin <jat@google.com>
Date: Fri, 11 Feb 2011 16:49:04 -0500
Message-ID: <AANLkTi==Re953Aj2Bwv-FVA15dnM8DXkbNWHJChYgCVn@mail.gmail.com>
To: Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Content-Type: multipart/alternative; boundary="0015174bdbf2e45a4f049c08ab62"
X-System-Of-Record: true
Cc: "hybi@ietf.org" <hybi@ietf.org>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: [hybi] thewebsocketprotocol #40 (new): Clarify binary/utf-8 mixed handling
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Feb 2011 21:49:12 -0000

On Fri, Feb 11, 2011 at 4:08 PM, Gabriel Montenegro <
Gabriel.Montenegro@microsoft.com> wrote:

> OLD:
>
>    o  An intermediary MAY change the fragmentation of a message if the
>
>       message uses only opcode and reserved bit values known to the
>
>       intermediary.
>
>
>
> NEW:
>
>    o  An intermediary MAY change the fragmentation of a message if the
>
>       message uses only opcode and reserved bit values known to the
>
>       intermediary.
>
>
>
>    As a consequence of these rules, all fragments of a message are of the same type,
>
>    as set by the first fragment’s opcode. Since Control frames cannot be fragmented,
>
>    the type for all fragments in a message MUST be either text or binary.
>
>
I don't object to this, but I note the general problem of saying essentially
the same thing several places in the document in slightly different ways.
 If we aren't very careful, there will be slight differences and thus
ambiguity as to which one is correct.

-- 
John A. Tamplin
Software Engineer (GWT), Google