Re: ietf-nntp Use of the LISTGROUP command

Rich Salz <rsalz@osf.org> Tue, 10 December 1996 19:13 UTC

Received: from cnri by ietf.org id aa23284; 10 Dec 96 14:13 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa18279; 10 Dec 96 14:13 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id NAA07222 for ietf-nntp-outgoing; Tue, 10 Dec 1996 13:03:47 -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 NAA07217 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 10 Dec 1996 13:03:45 -0600 (CST)
Received: from postman.osf.org (postman.osf.org [130.105.1.152]) by academ.com (8.8.3/8.7.1) with ESMTP id NAA07984 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 13:03:41 -0600 (CST)
Received: from sulphur.osf.org (sulphur.osf.org [130.105.1.123]) by postman.osf.org (8.7.6/8.7.3) with SMTP id OAA01529; Tue, 10 Dec 1996 14:03:09 -0500 (EST)
From: Rich Salz <rsalz@osf.org>
Received: by sulphur.osf.org (1.38.193.4/4.7) id AA21069; Tue, 10 Dec 1996 14:01:16 -0500
Date: Tue, 10 Dec 1996 14:01:16 -0500
Message-Id: <9612101901.AA21069@sulphur.osf.org>
To: NatBa@microsoft.com, ietf-nntp@academ.com
Subject: Re: ietf-nntp Use of the LISTGROUP command
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

>This seems like a pretty weak reason to add the LISTGROUP 
>command to the draft - especially if the newsreader has a 
>workaround for when the command does not exist.  We're going 
>to be here forever if we allow clients to decide which commands
>get put in the draft.  Could we remove this command from the 
>draft?

I said why it was originally added -- for nn.  According to my RCS
log it was added in 1991 before the first public release of INN.

I am sure many other clients have since started using it for their
own reasons.

And yes, clients get a big voice in deciding what goes into NNTP,
else what's the point?
	/r$