IETF Logo Mail Archive

RE: ietf-nntp Use of the LISTGROUP command

Nat Ballou <NatBa@microsoft.com> Wed, 11 December 1996 00:55 UTC

Received: from cnri by ietf.org id aa04660; 10 Dec 96 19:55 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa26181; 10 Dec 96 19:55 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id SAA08448 for ietf-nntp-outgoing; Tue, 10 Dec 1996 18:53:02 -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 SAA08437 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 10 Dec 1996 18:52:59 -0600 (CST)
Received: from tide03.microsoft.com (firewall-user@tide03.microsoft.com [131.107.3.13]) by academ.com (8.8.3/8.7.1) with ESMTP id SAA10748 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 18:52:55 -0600 (CST)
Received: by tide03.microsoft.com; id QAA17919; Tue, 10 Dec 1996 16:52:54 -0800 (PST)
Received: from unknown(157.54.17.74) by tide03.microsoft.com via smap (V3.1) id xma017913; Tue, 10 Dec 96 16:52:53 -0800
Received: from IMSMAIL ([157.55.65.201]) by imail2.microsoft.com (8.7.3/8.7.1) with ESMTP id QAA00702 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 16:52:59 -0800 (PST)
Received: from natba - 157.54.26.119 by ims.microsoft.com with Microsoft SMTPSVC; Tue, 10 Dec 1996 16:57:14 -0800
From: Nat Ballou <NatBa@microsoft.com>
To: ietf-nntp@academ.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: RE: ietf-nntp Use of the LISTGROUP command
Date: Tue, 10 Dec 1996 16:03:49 -0800
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1160
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <05f461457000bc6IMSMAIL@ims.microsoft.com>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> From: 	Rich Salz[SMTP:rsalz@osf.org]
> Sent: 	Tuesday, December 10, 1996 11:01 AM
> To: 	Nat Ballou; ietf-nntp@academ.com
> Subject: 	Re: ietf-nntp Use of the LISTGROUP command
>
> [...]
>
> 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.

Then there must be a good reason for the functionality it
provides - let's get that on the table and decide if listgroup is
the best way to go about it ...

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

Agreed - as do implementors ... both must work together to 
provide the best solutions.

Nat

v2.8.7 | Report a Bug | By Email