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

Brian Hernacki <bhern@netscape.com> Thu, 31 October 1996 20:39 UTC

Received: from cnri by ietf.org id aa23352; 31 Oct 96 15:39 EST
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa20533; 31 Oct 96 15:39 EST
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id OAA12225 for ietf-nntp-outgoing; Thu, 31 Oct 1996 14:36:52 -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 OAA12218 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 31 Oct 1996 14:36:48 -0600
Received: from hedgehog.mcom.com (h-207-1-136-17.netscape.com [207.1.136.17]) by academ.com (8.7.6/8.7.1) with ESMTP id OAA13025; Thu, 31 Oct 1996 14:36:46 -0600 (CST)
Received: from ventnor.mcom.com ([207.1.137.53]) by hedgehog.mcom.com (Netscape Mail Server v1.1) with SMTP id AAA20507; Thu, 31 Oct 1996 12:36:12 -0700
Message-ID: <32790D3E.3C18@netscape.com>
Date: Thu, 31 Oct 1996 12:34:06 -0800
From: Brian Hernacki <bhern@netscape.com>
Organization: Netscape, Floating Point Division
X-Mailer: Mozilla 3.0GoldC (X11; U; SunOS 5.5 sun4u)
MIME-Version: 1.0
To: Chris Newman <chris@innosoft.com>
CC: ietf-nntp@academ.com, nntp-extensions@academ.com, IMAP Discusson List <imap@cac.washington.edu>
Subject: Re: nntp-extensions Re: ietf-nntp NNTP SEARCH extension internet-draft available
References: <Pine.SOL.3.95.961031113632.380C-100000@eleanor.innosoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> Because of this, and especially because of #1, I don't think it's
> productive to try to stop further development on NNTP's reading
> capabilities as long as people actively want to pursue it (although I
> hold my own opinions about whether those people are making wise use of
> their time). However, if you go and develop protocol for an IMAP function
> in NNTP, the syntax should be as similar as possible.  There is no
> technical justification to create incompatible mechanisms.
> 
> So if you want to add searching, steal IMAP's SEARCH command, and if
> anything is missing, add the new functionality in such a way that it can
> be put in IMAP as well.  If you want to do real authentication, copy
> IMAP's mechanism (SASL).  If you want to do fetching of MIME parts or
> individual headers, copy IMAP's syntax as much as possible.

I agree that when replicating functionality into NNTP that exists in
IMAP we should attempt to keep as similar as practical. I think we did
this reasonably well with the proposed search extension.

However, what about other mechanisms which do not exist in IMAP but
exist or are need in NNTP? NEWGROUPS and (the proposed) LIST
SUBSCRIPTIONS, and LIST MOTD for example?

--brian
--------------------------------------------------------
Brian Hernacki                 mailto:bhern@netscape.com
Usenet foot-soldier	       Netscape Communications
(setf disclaimer "I speak for myself, not the company")