Re: ietf-nntp Re: nntp-extensions draft-ballou-nntpsrch-00.txt

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

Received: from cnri by ietf.org id aa11380; 19 Dec 96 14:02 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa17088; 19 Dec 96 14:02 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id MAA16216 for ietf-nntp-outgoing; Thu, 19 Dec 1996 12:53:56 -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 MAA16207 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 19 Dec 1996 12:53:52 -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 MAA15353; Thu, 19 Dec 1996 12:53:50 -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 NAA27195; Thu, 19 Dec 1996 13:53:40 -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 NAA25926; Thu, 19 Dec 1996 13:53:40 -0500 (EST)
Date: Thu, 19 Dec 1996 13:53:40 -0500 (EST)
From: Evan Champion <evanc@synapse.net>
To: Chris Lewis <clewis@nortel.ca>
cc: nntp-extensions@academ.com, ietf-nntp@academ.com
Subject: Re: ietf-nntp Re: nntp-extensions draft-ballou-nntpsrch-00.txt
In-Reply-To: <199612191806.MAA15107@academ.com>
Message-ID: <Pine.BSI.3.91.961219131909.23295G-100000@piano.synapse.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On 19 Dec 1996, Chris Lewis wrote:

> 	1) people adjusting headers etc - how do you identify which profile
> 	   belongs to whom?  (short of full authentication)

Well, what's wrong with full authentication?  Most open services only 
allow read access (think of the web, or anonymous FTP, etc.)  It would be 
nice if a future RFC would recommend authenticated posting if nothing 
else, and that would be your way out for for stateful servers.

It would also be nice if a future INN shipped with a Kerberos AUTHINFO
authenticator.  A lot of services are moving towards Kerberos
authenticators and I'm hoping 1Q97 to get all user services Kerberos
authenticated (my radius, pop/imap, ftp and http servers can all
authenticate against a Kerberos server, so news is pretty much the only
major service that can't/doesn't out of the box.)

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