IETF Logo Mail Archive

Re: XBATCH Command (Was: Re: New NNTP extensions in INN 1.5?)

Brian Kantor <brian@nothing.ucsd.edu> Mon, 15 July 1996 21:31 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23691; 15 Jul 96 17:31 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23687; 15 Jul 96 17:31 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa16753; 15 Jul 96 17:31 EDT
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.academ.com (8.7.5/8.6.9) with ESMTP id QAA07841 for <ietf-nntp@PHEASANT.ACADEM.COM>; Mon, 15 Jul 1996 16:04:26 -0500
Received: from nothing.ucsd.edu (nothing.ucsd.edu [132.239.1.4]) by academ.com (8.7.5/8.7.1) with SMTP id QAA12147 for <ietf-nntp@academ.com>; Mon, 15 Jul 1996 16:04:23 -0500 (CDT)
Received: by nothing.ucsd.edu (8.6.12/UCSDGENERIC.5) id OAA29231 to ietf-nntp@academ.com; Mon, 15 Jul 1996 14:04:05 -0700
Date: Mon, 15 Jul 1996 14:04:05 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199607152104.OAA29231@nothing.ucsd.edu>
To: ietf-nntp@academ.com
Subject: Re: XBATCH Command (Was: Re: New NNTP extensions in INN 1.5?)

Sorry, Stan, I came in late, and would like some clarification.

Question: Am I correct that it is your intent to produce a document
that will solely reflect NNTP as it is currently practiced?  That is,
it will NOT be the revised and expanded protocol specification ("NNTPv2")
that Eliot and I and others were working on?  That you regard that
whole process and the resulting document as a different charter than
what you are pursuing here?

I think this is a laudable goal, and will help in any way I can.
	- Brian

v2.8.7 | Report a Bug | By Email