Re: nntp-extensions Re: ietf-nntp NNTP SEARCH extension internet-draft available

Rich Salz <rsalz@osf.org> Fri, 01 November 1996 05:53 UTC

Received: from cnri by ietf.org id aa26580; 1 Nov 96 0:53 EST
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa02067; 1 Nov 96 0:53 EST
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id XAA14216 for ietf-nntp-outgoing; Thu, 31 Oct 1996 23:35:41 -0600
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 XAA14208 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 31 Oct 1996 23:35:38 -0600
Received: from pheasant.ACADEM.COM (root@PHEASANT.ACADEM.COM [198.137.249.71]) by academ.com (8.7.6/8.7.1) with ESMTP id XAA15562; Thu, 31 Oct 1996 23:35:36 -0600 (CST)
Received: from postman.osf.org (postman.osf.org [130.105.1.152]) by pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id XAA14204; Thu, 31 Oct 1996 23:35:34 -0600
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 AAA28857; Fri, 1 Nov 1996 00:33:14 -0500 (EST)
From: Rich Salz <rsalz@osf.org>
Received: by sulphur.osf.org (1.38.193.4/4.7) id AA18590; Fri, 1 Nov 1996 00:32:07 -0500
Date: Fri, 1 Nov 1996 00:32:07 -0500
Message-Id: <9611010532.AA18590@sulphur.osf.org>
To: MRC@panda.com, bhern@netscape.com
Subject: Re: nntp-extensions Re: ietf-nntp NNTP SEARCH extension internet-draft available
Cc: chris@innosoft.com, ietf-nntp@academ.com, imap@cac.washington.edu, nntp-extensions@academ.com
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

>I think that it is important to separate "exists" from "is needed".

I once tried to do this -- prune down the "nnrpd commands" in INN.
Could'nt be done.  Every single command (and there aren't many of them,
and they're pretty simple, and 977+the two manpages were enough to get
a wide community started hacking) was used by a large existing customer
base.

>For example, I believe that NEWGROUPS is an artifact of a bygone day when it
>was desirable and practical to tell the user about new newsgroups.  But today,
>now that every day a hundred new alt.sex.gerbils.naughty.ha.ha.ha.ha groups
>pop up, I see no value in it.

>The issue is to determine need.  I believe that "need" means "an IMAP
>implementator is stuck without this function being available, and there is no
>satisfactory alternative."  It makes no sense to copy a function from NNTP to
>IMAP just because it's there, or someone who does not plan to implement IMAP
>says it should be there.

It all depends on how much you want to lower the barrier to the One True
Protocol.  I am tired of saying I favor diversity until we know what's best.
But if you believe one protocol is the answer, and you want to make it 
difficult for the existing userbase to convert because.

>I'm not sure what LIST SUBSCRIPTIONS does.  If this is for remote .newsrc
>support, IMAP already supports this with its LSUB command.

Read the NNTP RFC's and drafts.  I have been doing the IMAP crowd the
courtesy of not asking for email-based tutorials, and instead tried to
find some time to read the spec.  Extend the same courtesy, enh?

>I am still waiting for an answer to my question about the "moral" issues of
>search.  Not all that long ago, I heard the NNTP crowd saying that IMAP was
>morally wrong

Please repeat your question.  I recall nothing like "morally wrong" coming
up in the discussion -- perhaps you should retract that comment.

I was surprised to see that the "state of the art" in IMAP was an I-D.
Is the IMAP crowd really saying that an NNTP draft should be withdrawn
just because a previous *draft document* was out a few months earlier?
Wow.
	/r$