ietf-nntp CHARSET isues with new draft.

Nat Ballou <NatBa@ims.microsoft.com> Fri, 05 September 1997 18:52 UTC

Received: from cnri by ietf.org id aa18263; 5 Sep 97 14:52 EDT
Received: from announcer.academ.com (majordomo@ANNOUNCER.ACADEM.COM [198.137.249.60]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid OAA07041 for <ietf-archive@cnri.reston.va.us>; Fri, 5 Sep 1997 14:55:13 -0400 (EDT)
Received: (from majordomo@localhost) by announcer.academ.com (8.8.5/8.8.5) id NAA08932; Fri, 5 Sep 1997 13:50:34 -0500 (CDT)
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by announcer.academ.com (8.8.5/8.8.5) with ESMTP id NAA08927 for <ietf-nntp@ANNOUNCER.ACADEM.COM>; Fri, 5 Sep 1997 13:50:33 -0500 (CDT)
Received: from eemail.microsoft.com (eemail.microsoft.com [131.107.1.244]) by academ.com (8.8.5/8.8.5) with ESMTP id NAA14176 for <ietf-nntp@academ.com>; Fri, 5 Sep 1997 13:50:31 -0500 (CDT)
Received: from ims.microsoft.com - 131.107.1.244 by eemail.microsoft.com with Microsoft SMTPSVC; Fri, 5 Sep 1997 11:50:26 -0700
Received: from natba1 - 157.55.23.225 by ims.microsoft.com with Microsoft SMTPSVC; Fri, 5 Sep 1997 11:50:22 -0700
Reply-To: Nat Ballou <NatBa@ims.microsoft.com>
From: Nat Ballou <NatBa@ims.microsoft.com>
To: NNTP Working Group <ietf-nntp@academ.com>
Subject: ietf-nntp CHARSET isues with new draft.
Date: Fri, 05 Sep 1997 11:45:48 -0700
Message-ID: <01bcba2b$ed21b2e0$e117379d@natba1.dns.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1702.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1702.0
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

I may have missed the discussion on this, but here goes ...

The CHARSET command in Stan's latest draft seems a bit
backwards.  The draft describes a CHARSET command that
clients issue the charset they want to use, and servers come 
back with yes/no type response.

Seems like a negotation model would work better.  That is,
The server returns a list of supported charsets, and the client
can try to pick the best one.  I used this type of model in one
of my earlier search drafts.

Comments?

Nat