Re: [EAI] Body parts

[Shawn Steele <Shawn.Steele at microsoft.com>]

I guess the WG scope doesn't include the body, but it does include UTF-8 :)

> I hate to say "cleaning up your own house would make more
> difference than anything the IETF could do"

Unfortunately its not "our own house" that's the entire problem, but rather interoperability with software from a large number of other vendors.

> if it were made very difficult to transmit anything textual from, e.g.,
> Outlook (both current and, via service packs, back to at least
to the 2003 version) in other than UTF-8...

My understanding is that we did that once, and the Japanese market reacted strongly because (my understanding) the cell phone industry was stuck with shift-jis.

So I would like it to be included that ALL clients need to support UTF-8, otherwise we can't move forward.

I can't speak to the accuracy of our tagging, however I do know we've experienced incompatibilities with the JIS extensions, for data nominally in the same code page.

- Shawn


_______________________________________________
IMA mailing list
IFrom ima-bounces at ietf.org  Sun Jul 13 10:40:32 2008
Return-Path: <ima-bounces at ietf.org>
X-Original-To: ima-archive at megatron.ietf.org
Delivered-To: ietfarch-ima-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B12E3A6870;
	Sun, 13 Jul 2008 10:40:32 -0700 (PDT)
X-Original-To: ima at core3.amsl.com
Delivered-To: ima at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF2393A6870
	for <ima at core3.amsl.com>; Sun, 13 Jul 2008 10:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.571
X-Spam-Level: 
X-Spam-Status: No, score=-10.571 tagged_above=-999 required=5
	tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 i8kI4k-C-gN8 for <ima at core3.amsl.com>;
	Sun, 13 Jul 2008 10:40:30 -0700 (PDT)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215])
	by core3.amsl.com (Postfix) with ESMTP id 026D33A6827
	for <ima at ietf.org>; Sun, 13 Jul 2008 10:40:29 -0700 (PDT)
Received: from TK5-EXHUB-C101.redmond.corp.microsoft.com (157.54.18.48) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.251.2; Sun, 13 Jul 2008 10:40:53 -0700
Received: from NA-EXMSG-C116.redmond.corp.microsoft.com ([157.54.62.39]) by
	TK5-EXHUB-C101.redmond.corp.microsoft.com ([157.54.18.48]) with mapi;
	Sun, 13 Jul 2008 10:40:53 -0700
From: Shawn Steele <Shawn.Steele at microsoft.com>
To: John C Klensin <klensin at jck.com>, "ima at ietf.org" <ima at ietf.org>
Date: Sun, 13 Jul 2008 10:40:51 -0700
Thread-Topic: [EAI] Body parts
Thread-Index: AcjlC8EwNs5ZmCHTRdu05/XjttOOqAAAvj9A
Message-ID: <C9BF0238EED3634BA1866AEF14C7A9E561C8486E8B at NA-EXMSG-C116.redmond.corp.microsoft.com>
References: <mailman.17.1215889202.8186.ima at ietf.org>
	<C9BF0238EED3634BA1866AEF14C7A9E561C8486E14 at NA-EXMSG-C116.redmond.corp.microsoft.com>
	<1BBF51B2B05A27464FF3BBBD at p3.JCK.COM>
	<C9BF0238EED3634BA1866AEF14C7A9E561C8486E49 at NA-EXMSG-C116.redmond.corp.microsoft.com>
	<E2A51F7B5611E57DE9977595 at p3.JCK.COM>
In-Reply-To: <E2A51F7B5611E57DE9977595 at p3.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [EAI] Body parts
X-BeenThere: ima at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>,
	<mailto:ima-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ima>
List-Post: <mailto:ima at ietf.org>
List-Help: <mailto:ima-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>,
	<mailto:ima-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ima-bounces at ietf.org
Errors-To: ima-bounces at ietf.org

I guess the WG scope doesn't include the body, but it does include UTF-8 :)

> I hate to say "cleaning up your own house would make more
> difference than anything the IETF could do"

Unfortunately its not "our own house" that's the entire problem, but rather interoperability with software from a large number of other vendors.

> if it were made very difficult to transmit anything textual from, e.g.,
> Outlook (both current and, via service packs, back to at least
to the 2003 version) in other than UTF-8...

My understanding is that we did that once, and the Japanese market reacted strongly because (my understanding) the cell phone industry was stuck with shift-jis.

So I would like it to be included that ALL clients need to support UTF-8, otherwise we can't move forward.

I can't speak to the accuracy of our tagging, however I do know we've experienced incompatibilities with the JIS extensions, for data nominally in the same code page.

- Shawn


_______________________________________________
IMA mailing list
IMA at ietf.MA@ietf.org
https://www.ietf.org/mailman/listinfo/ima


org
https://www.ietf.org/mailman/listinfo/ima