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

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

Received: from ietf.org by ietf.org id aa14122; 12 Aug 96 21:05 EDT
Received: from cnri by ietf.org id aa14118; 12 Aug 96 21:05 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa15966; 12 Aug 96 21:05 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id BAA02130 for ietf-nntp-outgoing; Tue, 13 Aug 1996 01:05:01 -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 BAA02126 for <ietf-nntp@PHEASANT.ACADEM.COM>; Tue, 13 Aug 1996 01:04:59 -0500
Received: (from sob@localhost) by academ.com (8.7.5/8.7.1) id UAA09166; Mon, 12 Aug 1996 20:04:44 -0500 (CDT)
Message-Id: <199608130104.UAA09166@academ.com>
Sender: ietf-archive-request@ietf.org
From: Stan Barber <sob@academ.com>
Date: Mon, 12 Aug 1996 20:04:44 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

> re: nntp v2 specification, I am mystified as to why the 'batch' 
> command has been added instead of the reasonably widely accepted 
> and easy to implement 'takethis/check' protocol.   Or are both going
> to be implemented?

Please cite your reference. I am unaware of any published V2 spec other 
than the one from the working group that existed at the beginning of the
decade. I am sure that spec will influence what is done by this group, but
it is not the output of work of the current working group. In any case, 
when that spec was published, there was no "takethis/check" protocol. 
If you can point out two distinct publically available implementations 
that implement this, I'd be delighted.

> re: mechanism for adding extensions:
>        Has this been defined anywhere, it is mentioned in several 
> places but I couldn't find a proposal for it.  I would suggest we 
> need to get this defined in a hurry, so that those who want / need 
> extensions urgently can start doing it the right way rather than just 
> adding them willy nilly.

This will be defined in the draft document that will be published 
later this month. It will be based on the work from RFC 1869.

 
> We have at least three extensions that we will be releasing in the 
> next month and it would be nice to try and get them to match in with
> the proposed standards.  I will discuss these in this group if this 
> is  the appropriate place, but I suspect it is not at this time.

There is an nntp-extensions mailing list for these discussions. It has been
running for about a month. You can subscribe to it by sending mail to:
	nntp-extensions-request@academ.com





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