IETF Logo Mail Archive

[rtcweb] PPID, UTF-16 and DOMString (Re: RTCWEB Data Channel: Usage of PPID for protocol multiplexing)

Harald Alvestrand <harald@alvestrand.no> Thu, 06 February 2014 23:18 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E125B1A0426 for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 15:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level:
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4lIi_vT2UmLq for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 15:18:12 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8D91A04C8 for <rtcweb@ietf.org>; Thu, 6 Feb 2014 15:18:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id CBD6E7C4A9D for <rtcweb@ietf.org>; Fri, 7 Feb 2014 00:18:10 +0100 (CET)
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rZ4tAPmLDEb for <rtcweb@ietf.org>; Fri, 7 Feb 2014 00:18:10 +0100 (CET)
Received: from [172.19.7.58] (unknown [216.239.45.90]) by mork.alvestrand.no (Postfix) with ESMTPSA id 4A8DB7C4A53 for <rtcweb@ietf.org>; Fri, 7 Feb 2014 00:18:10 +0100 (CET)
Message-ID: <52F4182F.60404@alvestrand.no>
Date: Fri, 07 Feb 2014 00:18:07 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D15E955@ESESSMB209.ericsson.se> <74072016-DA11-41E8-9944-779428163EE4@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D15ED94@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826DFCF6C8@US70UWXCHMBA02.zam.alcatel-lucent.com> <B304F67A-9EA2-44A0-86DD-9DD0E21CB86F@lurchi.franken.de>
In-Reply-To: <B304F67A-9EA2-44A0-86DD-9DD0E21CB86F@lurchi.franken.de>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCWEB Data Channel: Usage of PPID for protocol multiplexing)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 23:18:15 -0000

On 02/06/2014 08:17 PM, Michael Tuexen wrote:
>> Also, I think "DOMString" PPID is too specific to Javascript, instead it should probably have a generic name like "UTF-16 String". The send API can still use DOMString as this is Javascript API.
> Any comments from others?

Note: The WebSockets protocol defines the transferred strings as UTF-8.
http://tools.ietf.org/html/rfc6455#section-5.6

As far as I can tell, we've always intended to follow that example.

The fact that Javascript implementations currently choose to represent
text strings as UTF-16 at their API is sad, but not an argument for
sending that particular text representation over the wire, or reflecting
the name in the API.


-- 
Surveillance is pervasive. Go Dark.

v2.23.0 | Report a Bug | By Email