IETF Logo Mail Archive

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

Evan Champion <evanc@synapse.net> Thu, 19 December 1996 00:24 UTC

Received: from cnri by ietf.org id aa13827; 18 Dec 96 19:24 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa28726; 18 Dec 96 19:24 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id SAA11188 for ietf-nntp-outgoing; Wed, 18 Dec 1996 18:21:44 -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 SAA11183 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 18:21:42 -0600 (CST)
Received: from clarinet.synapse.net (clarinet.synapse.net [199.84.54.19]) by academ.com (8.8.3/8.7.1) with ESMTP id SAA05686 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 18:21:40 -0600 (CST)
Received: from piano.synapse.net (piano.synapse.net [199.84.54.20]) by clarinet.synapse.net (8.8.4/8.8.4) with ESMTP id TAA00955; Wed, 18 Dec 1996 19:21:33 -0500 (EST)
Received: from piano.synapse.net (localhost [127.0.0.1]) by piano.synapse.net (8.8.4/8.8.4) with SMTP id TAA07426; Wed, 18 Dec 1996 19:21:33 -0500 (EST)
Date: Wed, 18 Dec 1996 19:21:33 -0500 (EST)
From: Evan Champion <evanc@synapse.net>
To: Rich Salz <rsalz@osf.org>
cc: clewis@nortel.ca, ietf-nntp@academ.com
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
In-Reply-To: <9612181920.AA15629@sulphur.osf.org>
Message-ID: <Pine.BSI.3.91.961218185841.951J@piano.synapse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Wed, 18 Dec 1996, Rich Salz wrote:

> >2) During POST: discard any pre-existing Path:.
> 
> No.  Useful for mail/news gateways and to allow clients to reroute
> avoiding "hostile" hosts (r.h.f and Waterloo)

I know this has been discussed ad infinitum in news.software.nntp.

I do not see any reason for standard readers to need to specify a Path. 
If there are "hostile" hosts out there, then we should be spending the
effort to get them shut down rather than "breaking the rules" in order to 
let people get around these sites.

Gateways are somewhat trickier, in that I assume the case you mean is for
news-to-mail-to-news gatewaying, where you'd want to restore the path.  
What about posting it via ihave?  That would at least require the posting 
agent to have server access to the machine, something one could 
reasonably expect from a gateway.

In my mind, the path is supposed to represent the news servers a message 
has passed through, and if you're not an news server you shouldn't be 
playing with it.

If it is really an issue, I'd be happy with the following wording:
"Servers MUST by default remove Path headers on post, however they MAY
have a configurable option to disable this behaviour." 

Evan
--
Evan Champion            * Director, Network Operations
mailto:evanc@synapse.net * Directeur, Exploitation du reseau
http://www.synapse.net/  * Synapse Internet

v2.8.7 | Report a Bug | By Email