ietf-nntp draft-ballou-nntpsrch-00.txt

Nat Ballou <NatBa@microsoft.com> Tue, 10 December 1996 18:48 UTC

Received: from cnri by ietf.org id aa22046; 10 Dec 96 13:48 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa17453; 10 Dec 96 13:48 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id MAA06885 for ietf-nntp-outgoing; Tue, 10 Dec 1996 12:33:16 -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 MAA06872 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 10 Dec 1996 12:33:11 -0600 (CST)
Received: from tide03.microsoft.com (firewall-user@tide03.microsoft.com [131.107.3.13]) by academ.com (8.8.3/8.7.1) with ESMTP id MAA04883; Tue, 10 Dec 1996 12:33:08 -0600 (CST)
Received: by tide03.microsoft.com; id KAA12669; Tue, 10 Dec 1996 10:33:03 -0800 (PST)
Received: from unknown(157.54.17.74) by tide03.microsoft.com via smap (V3.1) id xma012654; Tue, 10 Dec 96 10:32:39 -0800
Received: from IMSMAIL ([157.55.65.201]) by imail2.microsoft.com (8.7.3/8.7.1) with ESMTP id KAA26345; Tue, 10 Dec 1996 10:32:44 -0800 (PST)
Received: from natba - 157.54.19.130 by ims.microsoft.com with Microsoft SMTPSVC; Tue, 10 Dec 1996 10:37:57 -0800
From: Nat Ballou <NatBa@microsoft.com>
To: imap@cac.washington.edu, nntp-extensions@academ.com, ietf-nntp@academ.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: ietf-nntp draft-ballou-nntpsrch-00.txt
Date: Tue, 10 Dec 1996 10:15:31 -0800
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1160
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <0c3165737180ac6IMSMAIL@ims.microsoft.com>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

In order to clarify the discussion of adding search to NNTP, 
I (natba@microsoft.com) wrote up a draft and submitted it to the 
IETF (see attached).  This draft is more in line with IMAP search.

I'm particularly interested in hearing from NNTP and IMAP 
implementors on the pros and cons of the different NNTP search
proposals.

Thanks,

Nat

------------------

A New Internet-Draft is available from the on-line Internet-Drafts
directories. 

        Title     : NNTP Full-text Search Enhancements 
        Author(s) : N. Ballou
        Filename  : draft-ballou-nntpsrch-00.txt
        Pages     : 8
        Date      : 11/18/1996
 
This document describes a set of enhancements to the Network News Transport
Protocol [NNTP-977] that allows full-text searching of news articles in
multiple newsgroups.  The proposed SEARCH command supports functionality
similar to the [IMAP4] SEARCH command, minus user specific search keys
(i.e., ANSWERED, DRAFT, FLAGGED, KEYWORD, NEW, OLD, RECENT, SEEN) and minus
search keys based on headers that do not exist in news (i.e., CC, BCC, TO).
 
The availability of the extensions described here will be advertised by the
server using the extension negotiation-mechanism described in the new NNTP 
protocol specification currently being developed [NNTP-NEW]. 
 
Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
     "get draft-ballou-nntpsrch-00.txt".
A URL for the Internet-Draft is:
ftp://ds.internic.net/internet-drafts/draft-ballou-nntpsrch-00.txt
 
Internet-Drafts directories are located at:	
 	
     o  Africa:  ftp.is.co.za
	
     o  Europe:  nic.nordu.net            	
                 ftp.nis.garr.it
 	
     o  Pacific Rim: munnari.oz.au
	
     o  US East Coast: ds.internic.net
	
     o  US West Coast: ftp.isi.edu
	
Internet-Drafts are also available by mail.	

Send a message to:  mailserv@ds.internic.net. In the body type:
     "FILE /internet-drafts/draft-ballou-nntpsrch-00.txt".
							
NOTE: The mail server at ds.internic.net can return the document in
      MIME-encoded form by using the "mpack" utility.  To use this
      feature, insert the command "ENCODING mime" before the "FILE"
      command.  To decode the response(s), you will need "munpack" or
      a MIME-compliant mail reader.  Different MIME-compliant mail readers
      exhibit different behavior, especially when dealing with
      "multipart" MIME messages (i.e., documents which have been split
      up into multiple messages), so check your local documentation on
      how to manipulate these messages.
							
							

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version
of the Internet-Draft.