IETF Logo Mail Archive

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

Chris Newman <chris@innosoft.com> Fri, 01 November 1996 19:45 UTC

Received: from cnri by ietf.org id aa27272; 1 Nov 96 14:45 EST
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa18231; 1 Nov 96 14:45 EST
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id NAA15533 for ietf-nntp-outgoing; Fri, 1 Nov 1996 13:40:18 -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 NAA15525 for <ietf-nntp@PHEASANT.ACADEM.COM>; Fri, 1 Nov 1996 13:40:14 -0600
Received: from sigurd.innosoft.com (SIGURD.INNOSOFT.COM [192.160.253.70]) by academ.com (8.7.6/8.7.1) with ESMTP id NAA00636; Fri, 1 Nov 1996 13:40:08 -0600 (CST)
Received: from eleanor.innosoft.com ("port 34697"@[192.160.253.79]) by sigurd.innosoft.com (PMDF V5.1-4 #8790) with SMTP id <01IBBWGPHW4Y9QWWV0@sigurd.innosoft.com>; Fri, 1 Nov 1996 11:40:03 PST
Date: Fri, 01 Nov 1996 11:40:32 -0800 (PST)
From: Chris Newman <chris@innosoft.com>
Subject: Re: nntp-extensions Re: ietf-nntp NNTP SEARCH extension internet-draft available
In-reply-to: <9611010532.AA18590@sulphur.osf.org>
To: Rich Salz <rsalz@osf.org>
Cc: ietf-nntp@academ.com, IMAP Discusson List <imap@cac.washington.edu>, nntp-extensions@academ.com
Message-id: <Pine.SOL.3.95.961101112912.5825A-100000@eleanor.innosoft.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Fri, 1 Nov 1996, Rich Salz wrote:
> I was surprised to see that the "state of the art" in IMAP was an I-D.
> Is the IMAP crowd really saying that an NNTP draft should be withdrawn
> just because a previous *draft document* was out a few months earlier?

RFC 1730 is a proposed standard.  The draft contains refinements and some
minor bugfixes.  The core command set hasn't changed.

As I've stated before, while I may think improving NNTP's newsreading
abilities is not a productive use of time, I won't stand in the way of the
effort unless you create gratuitously incompatible protocol (such as the
why the proposed SEARCH command deals with charsets).

v2.8.7 | Report a Bug | By Email