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

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

Received: from ietf.org by ietf.org id aa22079; 12 Aug 96 23:59 EDT
Received: from cnri by ietf.org id aa22075; 12 Aug 96 23:59 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa00744; 12 Aug 96 23:59 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id DAA02885 for ietf-nntp-outgoing; Tue, 13 Aug 1996 03:59:46 -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 DAA02881 for <ietf-nntp@PHEASANT.ACADEM.COM>; Tue, 13 Aug 1996 03:59:44 -0500
Received: (from sob@localhost) by academ.com (8.7.5/8.7.1) id WAA10785; Mon, 12 Aug 1996 22:59:25 -0500 (CDT)
Message-Id: <199608130359.WAA10785@academ.com>
Sender: ietf-archive-request@ietf.org
From: Stan Barber <sob@academ.com>
Date: Mon, 12 Aug 1996 22:59:24 CDT
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: NetWin Support <netwin@world.std.com>, ietf-nntp@academ.com
Subject: Re: ietf-nntp re: batch, streaming, Adding extensions?
X-Orig-Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> > If you can point out two distinct publically available implementations 
> > that implement this, I'd be delighted.
> 
>         DNEWS, INN, CNEWS
> With DNEWS it's built in, with INN and CNEWS I understand
> patches are available, I could be wrong about CNEWS.

That means that the only package you know if that has this functionality
built-in to the standard release is DNEWS. That seems to contradict your
assertion that this protocol was widely used. Perhaps there are lots of
people that routinely patch software or DNEWS has suddenly become more
popular than INN or CNEWS for transporting articles around the Internet.
Which do you think it is?

> Is that what you were asking, I'm not sure if I mis understood you.
> And I'm not sure of your definition of 'publicly available'.

By "publically available" I mean that either the source code is freely
available, or there is extensive docuementation freely available on how the
software works (configuration, protocols, internals). 

In any case, I'd welcome to write up a draft of the "takethis/check"
protocol for consideration as a standard extension. 


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