IETF Logo Mail Archive

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

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

Received: from cnri by ietf.org id aa03173; 19 Dec 96 10:27 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa11477; 19 Dec 96 10:27 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id JAA15345 for ietf-nntp-outgoing; Thu, 19 Dec 1996 09:24:40 -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 JAA15340 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 19 Dec 1996 09:24:38 -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 JAA14386 for <ietf-nntp@academ.com>; Thu, 19 Dec 1996 09:24:33 -0600 (CST)
Received: by nothing.ucsd.edu (8.8.3/UCSDGENERIC.5) id PAA08268 to ; Thu, 19 Dec 1996 15:23:22 GMT
Date: Thu, 19 Dec 1996 15:23:22 GMT
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199612191523.PAA08268@nothing.ucsd.edu>
To: ietf-nntp@academ.com, magill@isc.upenn.edu
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

The definition of whether a connection is between two peers or between
a client and a server is currently handled by an access control list
mechanism INDEPENDENT of the protocol.

A key issue which may not be apparent here is that UNLIKE mail, ftp,
and other such connectivity, news connections are BY ARRANGEMENT.

As such, many peer-to-peer issues are not protocol issues.
	- Brian

v2.8.7 | Report a Bug | By Email