IETF Logo Mail Archive

Re: ietf-nntp Use of the LISTGROUP command

Nat Ballou <NatBa@microsoft.com> Tue, 10 December 1996 18:48 UTC

Received: from cnri by ietf.org id aa22038; 10 Dec 96 13:48 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa17446; 10 Dec 96 13:48 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id MAA06873 for ietf-nntp-outgoing; Tue, 10 Dec 1996 12:33:12 -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 MAA06860 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 10 Dec 1996 12:33:08 -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 MAA04880 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 12:33:06 -0600 (CST)
Received: by tide03.microsoft.com; id KAA12673; Tue, 10 Dec 1996 10:33:04 -0800 (PST)
Received: from unknown(157.54.17.74) by tide03.microsoft.com via smap (V3.1) id xma012655; Tue, 10 Dec 96 10:32:40 -0800
Received: from IMSMAIL ([157.55.65.201]) by imail2.microsoft.com (8.7.3/8.7.1) with ESMTP id KAA26348 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 10:32:46 -0800 (PST)
Received: from natba - 157.54.19.130 by ims.microsoft.com with Microsoft SMTPSVC; Tue, 10 Dec 1996 10:38:00 -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 10:18:52 -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: <0c2cc0038180ac6IMSMAIL@ims.microsoft.com>
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?

Also, would the chair list other commands that made it into
the draft under similar circumstances?

Nat

----------
> From: Rich Salz <rsalz@osf.org>
> To: ErnieV@MetaInfo.com; ietf-nntp@academ.com
> Subject: Re:  ietf-nntp Use of the LISTGROUP command
> Date: Monday, December 02, 1996 10:06 AM
> 
> 
> It was added for the 'nn' newsreader.

v2.8.7 | Report a Bug | By Email