Re: ietf-nntp re: batch, streaming, Adding extensions?

Stan Barber <sob@academ.com> Tue, 13 August 1996 18:39 UTC

Received: from ietf.org by ietf.org id aa04220; 13 Aug 96 14:39 EDT
Received: from cnri by ietf.org id aa04216; 13 Aug 96 14:39 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa10622; 13 Aug 96 14:39 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id SAA04494 for ietf-nntp-outgoing; Tue, 13 Aug 1996 18:38:26 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to owner-ietf-nntp using -f
Received: from academ.com (sob@ACADEM.COM [198.137.249.2]) by pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id SAA04490 for <ietf-nntp@PHEASANT.ACADEM.COM>; Tue, 13 Aug 1996 18:38:20 -0500
Received: (from sob@localhost) by academ.com (8.7.5/8.7.1) id NAA19742; Tue, 13 Aug 1996 13:37:28 -0500 (CDT)
Message-Id: <199608131837.NAA19742@academ.com>
Sender: ietf-archive-request@ietf.org
From: Stan Barber <sob@academ.com>
Date: Tue, 13 Aug 1996 13:37:28 CDT
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Rich Salz <rsalz@osf.org>, brian@nothing.ucsd.edu, ietf-nntp@academ.com
Subject: Re: ietf-nntp re: batch, streaming, Adding extensions?
X-Orig-Sender: owner-ietf-nntp@academ.com
Precedence: bulk

>   Actually, ISC is now the maintainer of the INN program. When 1.5 comes out
>   with the additions of this functionality, that will meet my criteria for
>   being in a standard release. 
> 
> Does anything in Wayne's "nntp1.5tXXX" release count?

No, it does not meet my critera.

> unoff means nothing other than:  Rich Salz had nothing to do with this
> verison.

So, it does not meet my criteria.

Remember, this is my criteria that we are discussing here. After the draft is
released, folks are welcome to comment on it. If they don't like my criteria
for what is in or not in that document, they are welcome to suggest changes
to the draft that will liberalize or make more restrictive what is considered
part of the basic functionality of NNTP. Alternatively, they can write
drafts for extensions to NNTP under the new extension mechanism to add
whatever functions they like. Some of those may become standard extensions,
others may not. That's part of the process.

However, in the process, we get some useful documentation of these extensions.
That has not be the case in the past and strikes me as a big benefit of this
process. 




-- 
Stan   | Academ Consulting Services        |internet: sob@academ.com
Olan   | For more info on academ, see this |uucp: {mcsun|amdahl}!academ!sob
Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.