RE: ietf-nntp Comments on "NNTP LIST additions"

"David Johnson (Exchange)" <djohnson@exchange.microsoft.com> Fri, 13 December 1996 01:06 UTC

Received: from cnri by ietf.org id aa12178; 12 Dec 96 20:06 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa00988; 12 Dec 96 20:06 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id TAA08157 for ietf-nntp-outgoing; Thu, 12 Dec 1996 19:04:11 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id TAA08152 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 12 Dec 1996 19:04:05 -0600 (CST)
Received: from doggate.microsoft.com (doggate.microsoft.com [131.107.2.63]) by academ.com (8.8.3/8.7.1) with SMTP id TAA10129 for <ietf-nntp@academ.com>; Thu, 12 Dec 1996 19:04:03 -0600 (CST)
Received: by DOGGATE with Internet Mail Service (5.0.1389.3) id <01BBE84E.78BD5DF0@DOGGATE>; Thu, 12 Dec 1996 17:04:01 -0800
Message-ID: <2FBF98FC7852CF11912A0000000000010360557A@DINO>
From: "David Johnson (Exchange)" <djohnson@exchange.microsoft.com>
To: Rich Salz <rsalz@osf.org>, 'Brian Hernacki' <bhern@netscape.com>
Cc: ietf-nntp@academ.com
Subject: RE: ietf-nntp Comments on "NNTP LIST additions"
Date: Thu, 12 Dec 1996 17:03:37 -0800
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1389.3)
Content-Type: text/plain
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> ----------
> From:
> owner-ietf-nntp@academ.com[SMTP:owner-ietf-nntp@academ.com] on behalf
> of Brian Hernacki[SMTP:bhern@netscape.com]
> 
> As for charset, I was trying to leave it open enough that people could
> use it as they saw fit, but I see your point. I will try to clarify
> that. Suggestions (from anyone) are welcome.
> 
I recommend staying away from MIME-2 encoding and using UTF-7 or 8
instead. UTF-8 is being used in IMAP, ACAP, LDAP, and other protocols.
We should stay away from Euro-centric models or the complexity of
allowing any character set and follow suit with these other protocols.

- david
-----------------
David C. Johnson   <djohnson@microsoft.com>
Program Manager -- Microsoft Exchange
Microsoft Corporation