IETF Logo Mail Archive

Re: ietf-nntp Initial draft FINALLY available

Bob Sloane <SLOANE@kuhub.cc.ukans.edu> Wed, 02 October 1996 19:13 UTC

Received: from cnri by ietf.org id aa27322; 2 Oct 96 15:13 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa18582; 2 Oct 96 15:13 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id OAA25301 for ietf-nntp-outgoing; Wed, 2 Oct 1996 14:10:44 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id OAA25297 for <ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 14:10:42 -0500
Received: from kuhub.cc.ukans.edu (kuhub.cc.ukans.edu [129.237.32.2]) by academ.com (8.7.6/8.7.1) with ESMTP id OAA29455 for <ietf-nntp@academ.com>; Wed, 2 Oct 1996 14:10:39 -0500 (CDT)
Received: from KUHUB.CC.UKANS.EDU by KUHUB.CC.UKANS.EDU (PMDF V5.0-6 #13311) id <01IA64SE6L4W8ZK8BM@KUHUB.CC.UKANS.EDU>; Wed, 02 Oct 1996 14:10:35 -0500 (UTC -05:00)
Date: Wed, 02 Oct 1996 14:06:33 -0500 (UTC -05:00)
From: Bob Sloane <SLOANE@kuhub.cc.ukans.edu>
Subject: Re: ietf-nntp Initial draft FINALLY available
To: ietf-nntp@academ.com
Cc: SLOANE@kuhub.cc.ukans.edu
Message-id: <01IA64Z0YQ7O8ZK8BM@KUHUB.CC.UKANS.EDU>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

>Specifically, I think the AUTHINFO {USER,PASS} should be in the draft RFC.
>It may be deprecated there to reflect that it is being replaced.

I agree.  The stated goal is to document existing practice, rather
than extentions, isn't it?  Is there any reason to beleive that
AUTHINFO {USER,PASS} isn't the most used method of authentication
right now?  In what way does this situation differ from the BATCH
command, which was left out?
-- 
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane@kuhub.cc.ukans.edu, Phone: (913) 864-0444, FAX: (913) 864-0485

v2.8.7 | Report a Bug | By Email