ietf-nntp 7-bit restriction in command arguments
"David Johnson (Exchange)" <djohnson@exchange.microsoft.com> Thu, 10 October 1996 02:15 UTC
Received: from cnri by ietf.org id aa00096; 9 Oct 96 22:15 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa26545;
9 Oct 96 22:15 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
VAA06797 for ietf-nntp-outgoing; Wed, 9 Oct 1996 21:12:01 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to
owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id VAA06793 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 9 Oct 1996 21:11:59 -0500
Received: from feyuri.microsoft.com (feyuri.microsoft.com [131.107.243.53]) by
academ.com (8.7.6/8.7.1) with ESMTP id VAA27649 for <ietf-nntp@academ.com>;
Wed, 9 Oct 1996 21:11:56 -0500 (CDT)
Message-Id: <199610100211.VAA27649@academ.com>
Received: by FEYURI with IMAIL 2.0
id <01BBB615.4999DF50@FEYURI>; Wed, 9 Oct 1996 19:08:42 -0700
From: "David Johnson (Exchange)" <djohnson@exchange.microsoft.com>
To: "'ietf-nntp@academ.com'" <ietf-nntp@academ.com>
Subject: ietf-nntp 7-bit restriction in command arguments
Date: Wed, 9 Oct 1996 14:33:25 -0700
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Connector (4.5.1338.4)
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
From draft-barber-nntp-news-00.txt:
Commands in the NNTP MUST consist of a case-insensitive
keyword, which MAY be followed by one or more arguments.
All commands MUST be terminated by a CRLF pair. Multiple
commands MUST not be permitted on the same line.
Keywords
and arguments MUST consist of printable ASCII
characters.
I know this restriction exists in RFC-977, but is it really necessary
to continue limiting command arguments to ascii characters? It makes
handling non-ascii character sets more difficult. The restriction in
IMAP seems much more reasonable, where unencoded binary strings with
NUL or excessive control characters must be encoded, but otherwise
8-bit data is allowed.
I also think this draft should specify how binary arguments are to be
encoded (i.e., use a MIME content transfer encoding), to avoid a
proliferation of different encodings as people define new extensions.
- David
-----------------
David C. Johnson <djohnson@microsoft.com>
Program Manager
Microsoft Exchange Product Unit
Microsoft Corporation
- ietf-nntp 7-bit restriction in command arguments David Johnson (Exchange)