Re: [rtcweb] Text communication in RTCWEB sessions

worley@ariadne.com (Dale R. Worley) Tue, 13 November 2012 15:47 UTC

Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F293921F86F1 for <rtcweb@ietfa.amsl.com>; Tue, 13 Nov 2012 07:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.703
X-Spam-Level:
X-Spam-Status: No, score=-2.703 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 aJFNUjJkkr3r for <rtcweb@ietfa.amsl.com>; Tue, 13 Nov 2012 07:47:59 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id D328A21F86AD for <rtcweb@ietf.org>; Tue, 13 Nov 2012 07:47:56 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qADFl4AV020960 for <rtcweb@ietf.org>; Tue, 13 Nov 2012 10:47:06 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qADFl3KR977501 for <rtcweb@ietf.org>; Tue, 13 Nov 2012 10:47:04 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qADFl3Sc971105; Tue, 13 Nov 2012 10:47:03 -0500 (EST)
Date: Tue, 13 Nov 2012 10:47:03 -0500
Message-Id: <201211131547.qADFl3Sc971105@shell01.TheWorld.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: rtcweb@ietf.org
In-reply-to: <50A1FD99.3030501@it.aoyama.ac.jp> (duerst@it.aoyama.ac.jp)
Subject: Re: [rtcweb] Text communication in RTCWEB sessions
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 13 Nov 2012 15:48:00 -0000

> From: Adam Roach <adam@nostrum.com>
> 
> I look forward to the UTF-8 versus UTF-16 battle. :)

> From: "Martin J. DC<rst" <duerst@it.aoyama.ac.jp>
> 
> The IETF is very strongly UTF-8. The W3C is very strongly UTF-8 on the 
> wire, but of course UTF-16 in JavaScript. So these battles are over.

RFC 4103 specifies that text/t140 is encoded in UTF-8.  Of course, the
API can present it to the Javascript in whatever way it wants.  There
are a bunch of CJK extension sets above 0x10000, though, so UTF-16 may
be problematic.

Dale