Re: draft-klensin-net-utf8-06

Julian Reschke <julian.reschke@gmx.de> Mon, 22 October 2007 10:37 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijuev-0004Mn-CR; Mon, 22 Oct 2007 06:37:21 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Ijueu-0004IQ-7t for discuss-confirm+ok@megatron.ietf.org; Mon, 22 Oct 2007 06:37:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ijuet-00048R-7y for discuss@apps.ietf.org; Mon, 22 Oct 2007 06:37:19 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ijuej-0000qz-DN for discuss@apps.ietf.org; Mon, 22 Oct 2007 06:37:15 -0400
Received: (qmail invoked by alias); 22 Oct 2007 10:36:42 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.87]) [217.91.35.233] by mail.gmx.net (mp034) with SMTP; 22 Oct 2007 12:36:42 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19xU1Ii4Ulx/+xIu0hdUzZ0wTM2kmWuvr4kOCDdqJ S5VrSN8M6o1aBn
Message-ID: <471C7D34.2000204@gmx.de>
Date: Mon, 22 Oct 2007 12:36:36 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: tbray@textuality.com
Subject: Re: draft-klensin-net-utf8-06
References: <93F25E18AB3DA3EB0599F092@p3.JCK.COM> <517bf110710220323l493c61ccrcc2d72ee3801f60a@mail.gmail.com>
In-Reply-To: <517bf110710220323l493c61ccrcc2d72ee3801f60a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Tim Bray wrote:
> ...
> "  5.  As suggested in Section 6 of RFC 3629, the Byte Order Mark
>        ("BOM") signature MUST NOT appear at the beginning of these text
>        strings."
> 
> It might be worth adding a note something along these lines: "The BOM
> is useful in establishing the endian-ness of UTF-16 and UTF-32
> encodings, but serves no useful purpose in the context of UTF-8."
> ...

The BOM doesn't server any purpose *here* (because we know it's UTF-8).

In general, a BOM starting a UTF-8 encoded octet stream can be a useful 
hint to the recipient if out-of-band encoding information has been lost 
(such as when storing an HTTP response body in a simple file).

Best regards, Julian