IETF Logo Mail Archive

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

Evan Champion <evanc@synapse.net> Wed, 18 December 1996 23:44 UTC

Received: from cnri by ietf.org id aa13131; 18 Dec 96 18:44 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa27930; 18 Dec 96 18:44 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id RAA10944 for ietf-nntp-outgoing; Wed, 18 Dec 1996 17:40:42 -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 RAA10939 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 17:40:39 -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 RAA05451 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 17:40:37 -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 SAA28624; Wed, 18 Dec 1996 18:40:35 -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 SAA04863; Wed, 18 Dec 1996 18:40:35 -0500 (EST)
Date: Wed, 18 Dec 1996 18:40:35 -0500 (EST)
From: Evan Champion <evanc@synapse.net>
To: Chris Lewis <clewis@nortel.ca>
cc: ietf-nntp@academ.com
Subject: Re: ietf-nntp BCP for RFC977 server/RFC1036 interaction
In-Reply-To: <199612181826.MAA02212@academ.com>
Message-ID: <Pine.BSI.3.91.961218183452.951G-100000@piano.synapse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On 18 Dec 1996, Chris Lewis wrote:

> The title would be something along the lines of "Best Current
> Practises regarding Usenet traceability in an NNTP environment
> as it pertains to Usenet news article headers".  Which is quite
> a mouthful ;-)

I'd have to check, but that might just win the record for longest RFC 
title :-)
 
In terms of a BCP I don't think one can do much better than this.

In terms of moving forward, there are a number of points I don't like, 
mostly surrounding authentication and how an authenticated post is 
presented.  But there are enough arguments in here as it is, and I think 
having a BCP released is too useful to have slowed down or abandonned by 
discussion of what's wrong with the way things are done today.  Let's 
get agreement on what the BCP is first and then try to fix it :-)

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