IETF Logo Mail Archive

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

Harald.T.Alvestrand@uninett.no Thu, 19 December 1996 11:53 UTC

Received: from cnri by ietf.org id aa28286; 19 Dec 96 6:53 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa07137; 19 Dec 96 6:53 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id FAA14881 for ietf-nntp-outgoing; Thu, 19 Dec 1996 05:49:32 -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 FAA14876 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 19 Dec 1996 05:49:26 -0600 (CST)
Received: from aun.uninett.no (aun.uninett.no [129.241.1.99]) by academ.com (8.8.3/8.7.1) with SMTP id FAA13469 for <ietf-nntp@academ.com>; Thu, 19 Dec 1996 05:49:24 -0600 (CST)
Received: from dale.uninett.no by aun.uninett.no with SMTP (PP); Thu, 19 Dec 1996 12:49:09 +0100
Received: from dale.uninett.no (localhost [127.0.0.1]) by dale.uninett.no (8.6.9/8.6.12) with ESMTP id LAA00315; Thu, 19 Dec 1996 11:08:37 +0100
From: Harald.T.Alvestrand@uninett.no
To: Chris Newman <Chris.Newman@innosoft.com>
cc: Brian Hernacki <bhern@netscape.com>, ietf-nntp@academ.com
Subject: Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF
In-reply-to: Your message of "Tue, 17 Dec 1996 16:18:55 PST." <Pine.SOL.3.95.961217160859.13274J-100000@eleanor.innosoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <311.850990117.1@dale.uninett.no>
Date: Thu, 19 Dec 1996 11:08:37 +0100
Message-ID: <313.850990117@dale.uninett.no>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

This AD certainly won't say that not addressing i18n in the new
protocol won't hold it up.

We currently have <just send 8-bit> deployed in certain parts of the
world. The new spec needs to do one of:

- Frown on the practice and declare ASCII forever (and be ignored)
- Mandate a single charset for all conformant implementations
- Add tag&bag or negotiated identification of all strings that
  may contain i18n-ed strings

I won't dictate your decision - *all* of these cause harm to the
installed base, finding the least painful solution is the WG's job.

            Harald

v2.8.7 | Report a Bug | By Email