Re: ietf-nntp Backfill

Brian Kantor <brian@nothing.ucsd.edu> Tue, 17 December 1996 19:43 UTC

Received: from cnri by ietf.org id aa15260; 17 Dec 96 14:43 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa20265; 17 Dec 96 14:42 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id NAA04934 for ietf-nntp-outgoing; Tue, 17 Dec 1996 13:38:59 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id NAA04928 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 17 Dec 1996 13:38:58 -0600 (CST)
Received: from nothing.ucsd.edu (nothing.ucsd.edu [132.239.1.4]) by academ.com (8.8.3/8.7.1) with ESMTP id NAA19494 for <ietf-nntp@academ.com>; Tue, 17 Dec 1996 13:38:56 -0600 (CST)
Received: by nothing.ucsd.edu (8.8.3/UCSDGENERIC.5) id TAA03237 to ietf-nntp@academ.com; Tue, 17 Dec 1996 19:37:50 GMT
Date: Tue, 17 Dec 1996 19:37:50 GMT
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199612171937.TAA03237@nothing.ucsd.edu>
To: ietf-nntp@academ.com
Subject: Re: ietf-nntp Backfill
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Is it the intention of this committee to make RFC977bis a complete
specification for the Usenet news system?

It seems that many of the discussions on here of late have focussed on
the underlying news storage and retrieval system, not on issues of
transport, which is the scope of the original RFC977.

I believe it is time to split the transfer, storage, and reading issues.
	- Brian