IETF Logo Mail Archive

Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction

Brian Kantor <brian@nothing.ucsd.edu> Thu, 19 December 1996 04:56 UTC

Received: from cnri by ietf.org id aa23416; 18 Dec 96 23:56 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa00925; 18 Dec 96 23:56 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id WAA12068 for ietf-nntp-outgoing; Wed, 18 Dec 1996 22:53:55 -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 WAA12063 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 22:53:53 -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 WAA08994 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 22:53:51 -0600 (CST)
Received: by nothing.ucsd.edu (8.8.3/UCSDGENERIC.5) id EAA22653 to ; Thu, 19 Dec 1996 04:52:21 GMT
Date: Thu, 19 Dec 1996 04:52:21 GMT
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199612190452.EAA22653@nothing.ucsd.edu>
To: evanc@synapse.net, rsalz@osf.org
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
Cc: clewis@nortel.ca, ietf-nntp@academ.com
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

The intention was that IHAVE would only be used by news neighbors, never
by clients.  The headers in an article arriving by IHAVE would not be
tampered with except to prefix the Path line.

An article arriving via POST was assumed to come only from a client, and
could lack some of the headers necessary for transport.

For those who remember the past, that means that 'IHAVE' was equivalent
to the 'rnews' program used to relay news, whereas POST was equivalent
to invoking 'inews' to submit a new article.
	- Brian

v2.8.7 | Report a Bug | By Email