ietf-nntp Re: nntp-extensions draft-ballou-nntpsrch-00.txt

Jeff Coffler <jeffc@netmanage.com> Tue, 10 December 1996 19:17 UTC

Received: from cnri by ietf.org id aa23463; 10 Dec 96 14:17 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa18361; 10 Dec 96 14:17 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id NAA07304 for ietf-nntp-outgoing; Tue, 10 Dec 1996 13:07:36 -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 NAA07294 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 10 Dec 1996 13:07:33 -0600 (CST)
Received: from mail.netmanage.com (mail.netmanage.com [156.27.1.4]) by academ.com (8.8.3/8.7.1) with SMTP id NAA08746; Tue, 10 Dec 1996 13:07:23 -0600 (CST)
Received: from bellevue.NetManage.COM by mail.netmanage.com (SMI-8.6/SMI-SVR4) id KAA17296; Tue, 10 Dec 1996 10:54:59 -0800
Received: from jeffc (jeffc.netmanage.com) by bellevue.NetManage.COM (5.0/satellite-06oct94-MarkS) id AA07273; Tue, 10 Dec 1996 10:53:14 +0800
Date: Tue, 10 Dec 96 10:47:05 -0800
From: Jeff Coffler <jeffc@netmanage.com>
Subject: ietf-nntp Re: nntp-extensions draft-ballou-nntpsrch-00.txt
To: Nat Ballou <NatBa@microsoft.com>
Cc: ietf-nntp@academ.com, imap@cac.washington.edu, nntp-extensions@academ.com
X-Mailer: Chameleon ATX 6.0.1, Standards Based IntraNet Solutions, NetManage Inc.
X-Priority: 3 (Normal)
References: <0c3165737180ac6IMSMAIL@ims.microsoft.com>
Message-Id: <Chameleon.850244054.jeffc@jeffc>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Hi Nat,

I have a comment on your proposal for NNTP.  You said:

>The SEARCH  command searches the newsgroup for  articles that  match the
>given searching criteria.   Searching  criteria consist of one   or more
>search keys.  If there are articles that  match the search criteria, the
>server responds with  code 224 and returns  OVER data for each  matching
>article in the same  format as described  in [NNTP-NEW].  The article ID
>is only  meaningful  when searching either  the  current newsgroup or  a
>single newsgroup.

I think the last line is needlessly restrictive.

I think that, in the case of a search, the return format should be in one
of two formats:

(1) Existing overview format, but modify the article number to be a
newsgroup/article# pair (like "comp.databases:30954" rather than "30954").

(2) Existing overview format with the extension: "Newsgroups: xxx" at
the end, where "xxx" is the newsgroup that matches the article number.

Personally, even though it deviates slightly from the XOVER standard,
I prefer the first format, solely because, in common cases (searching
across a range of newsgroups), you'll have all the information you
need.  The second format is consistent with an extended header for
XOVER, so meshes somewhat nicely with the existing spec, but it would
make it slightly more difficult for the client to get the info needed
(more parsing would be needed).

That's my input.  Otherwise, I thought it looked pretty good ...

	-- Jeff Coffler
	   NetManage, Inc.
           2340 130th Avenue NE
           Bellevue, WA  98005