IETF Logo Mail Archive

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 aa23358; 31 Oct 96 15:39 EST
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa20539; 31 Oct 96 15:39 EST
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id OAA12165 for ietf-nntp-outgoing; Thu, 31 Oct 1996 14:31:34 -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 OAA12158 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 31 Oct 1996 14:31:30 -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 OAA12696; Thu, 31 Oct 1996 14:31:14 -0600 (CST)
Received: from ventnor.mcom.com ([207.1.137.53]) by hedgehog.mcom.com (Netscape Mail Server v1.1) with SMTP id AAA19784; Thu, 31 Oct 1996 12:30:40 -0700
Message-ID: <32790BEF.105@netscape.com>
Date: Thu, 31 Oct 1996 12:28:31 -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: Jack De Winter <jack@wildbear.on.ca>
CC: Jeff Coffler <jeffc@netmanage.com>, Keith Moore <moore@cs.utk.edu>, Nat Ballou <natba@ims.microsoft.com>, ietf-nntp@academ.com, imap@cac.washington.edu, nntp-extensions@academ.com, Rich Salz <rsalz@osf.org>
Subject: Re: nntp-extensions Re: ietf-nntp NNTP SEARCH extension internet-draft available
References: <19961031151751.056f994a.in@lacroix.wildbear.on.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> I think the original point that was made is that NNTP was designed
> originally for news transfer, not reading.  IMAP was designed to handle
> messages, and was focused on mail messages because it seemed like a better
> bet.

People keep saying this, but I think it's outright wrong. From the
earliest days NNTP included reader protocol. Despite it's acronym, it
has been both a transport AND a reader protocol.

> My personal preferences would be to see NNTP set as a transfer protocol
> and IMAP used to read the articles.  NNTP is good for transfering articles,
> but the specs for any of the news reading stuff is poorly done. 

As far as I have seen, between RFC977, RFC1036, and the more recent ID
from Stan Barber the protocol (reading and transfer) seem pretty well
covered.

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

v2.8.7 | Report a Bug | By Email