Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF

Brian Hernacki <bhern@netscape.com> Wed, 18 December 1996 18:49 UTC

Received: from cnri by ietf.org id aa03272; 18 Dec 96 13:49 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa20533; 18 Dec 96 13:49 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id MAA10003 for ietf-nntp-outgoing; Wed, 18 Dec 1996 12:46:04 -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 MAA09997 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 12:46:03 -0600 (CST)
Received: from r2d2.mcom.com (h-205-217-237-47.netscape.com [205.217.237.47]) by academ.com (8.8.3/8.7.1) with ESMTP id MAA02264 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 12:45:55 -0600 (CST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by r2d2.mcom.com (8.7.5/8.7.3) with ESMTP id KAA06624 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 10:45:21 -0800 (PST)
Received: from ventnor.mcom.com ([207.1.137.53]) by dredd.mcom.com (Netscape Mail Server v2.02) with SMTP id AAA15457; Wed, 18 Dec 1996 10:45:20 -0800
Message-ID: <32B83BF5.6C48@netscape.com>
Date: Wed, 18 Dec 1996 10:46:13 -0800
From: Brian Hernacki <bhern@netscape.com>
Organization: Netscape, Floating Point Division
X-Mailer: Mozilla 3.0GoldC (X11; U; SunOS 5.5 sun4u)
MIME-Version: 1.0
To: Chris Lewis <clewis@nortel.ca>
CC: Chris.Newman@innosoft.com, ietf-nntp@academ.com
Subject: Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF
References: <199612181826.KAA24376@xwing.netscape.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Chris Lewis wrote:
> The defacto standards (INN + Cnews/Reference NNTP implementation) transport
> 8-bit article bodies unmolested.  I see no reason to continue to enforce
> this _unnecessary_ archaism which has already been purposefully abandoned.
> 
> We don't need to deal with charsets - NNTP is a transport mechanism, and
> isn't involved in display issues.  The only place where it matters is in
> the headers - where we may simply wish to take a similar bailout as,
> say, Posix C did, and insist that the headers are, say, UTF8 (where can
> I find a listing of this?) or Latin-1.  Indeed, we may well be able
> to get away with insisting that the keywords are the current ASCII
> encodings, and most of/all of the keyword values are 8-bit.

OK...my bad. I thought you were proposing adding alot of charset and
other i18n supprt stuff to NNTP. I'm all for at least clarifying the use
of 8-bit vs 7 bit. I think this does fall under documenting current
de-fact standards and would go a long way to i18n support.

--brian