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

Jack De Winter <jack@wildbear.on.ca> Fri, 01 November 1996 01:20 UTC

Received: from cnri by ietf.org id aa09803; 31 Oct 96 20:20 EST
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa26544; 31 Oct 96 20:20 EST
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id TAA13690 for ietf-nntp-outgoing; Thu, 31 Oct 1996 19:17:37 -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 TAA13685 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 31 Oct 1996 19:17:35 -0600
Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by academ.com (8.7.6/8.7.1) with ESMTP id TAA14464 for <ietf-nntp@academ.com>; Thu, 31 Oct 1996 19:17:32 -0600 (CST)
Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Thu, 31 Oct 1996 20:12:08 -0500
Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Thu, 31 Oct 1996 20:12:08 -0500
X-Sender: "Jack De Winter" <jack@wildbear.on.ca>
X-Mailer: Windows Eudora Version 2.1.1
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Brian Hernacki <bhern@netscape.com>
From: Jack De Winter <jack@wildbear.on.ca>
Subject: Re: nntp-extensions Re: ietf-nntp NNTP SEARCH extension internet-draft available
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>
Date: Thu, 31 Oct 1996 20:12:08 -0500
Message-Id: <19961031201208.067d0854.in@lacroix.wildbear.on.ca>
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

>> 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.

It seems covered if you care to use TAR and get some formats but hunting
through code on a site.  I asked him about this, and his attitude was to
find a Windows TAR program or to use a real operating system that had that.
That put me off I must admit.

From past experience in the mail field, if someone is preparing a draft
that outlines what kind of responses a command returns, saying what that
format is in that draft/rfc or an exisiting RFC is necessary.  When it
comes time to vote for the NNTP drafts, I will make sure that my feelings
about this are mentioned to others, as Stan is not disposed to listen to
me.

regards,
Jack
-------------------------------------------------
Jack De Winter - Wildbear Consulting, Inc.
(519) 576-3873		http://www.wildbear.on.ca/

Author of SLMail(95/NT) (http://www.seattlelab.com/) and other great products.