IETF Logo Mail Archive

Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF

Nat Ballou <NatBa@microsoft.com> Thu, 19 December 1996 16:30 UTC

Received: from cnri by ietf.org id aa06421; 19 Dec 96 11:30 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa13296; 19 Dec 96 11:30 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id KAA15679 for ietf-nntp-outgoing; Thu, 19 Dec 1996 10:27:39 -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 KAA15674 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 19 Dec 1996 10:27:37 -0600 (CST)
Received: from tide03.microsoft.com (firewall-user@tide03.microsoft.com [131.107.3.13]) by academ.com (8.8.3/8.7.1) with ESMTP id KAA14718 for <ietf-nntp@academ.com>; Thu, 19 Dec 1996 10:27:35 -0600 (CST)
Received: by tide03.microsoft.com; id IAA00419; Thu, 19 Dec 1996 08:27:21 -0800 (PST)
Received: from unknown(157.54.17.74) by tide03.microsoft.com via smap (V3.1) id xma000413; Thu, 19 Dec 96 08:27:06 -0800
Received: from IMSMAIL ([157.55.65.201]) by imail2.microsoft.com (8.7.3/8.7.1) with ESMTP id IAA07053; Thu, 19 Dec 1996 08:27:22 -0800 (PST)
Received: from natba1 - 172.31.178.33 by ims.microsoft.com with Microsoft SMTPSVC; Thu, 19 Dec 1996 08:31:34 -0800
From: Nat Ballou <NatBa@microsoft.com>
To: Brian Kantor <brian@nothing.ucsd.edu>, Chris.Newman@innosoft.com, moore@cs.utk.edu
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Cc: ietf-nntp@academ.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF
Date: Thu, 19 Dec 1996 08:28:08 -0800
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1160
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID: <038c034311613c6IMSMAIL@ims.microsoft.com>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> From: Brian Kantor <brian@nothing.ucsd.edu>
> To: Chris.Newman@INNOSOFT.COM; moore@cs.utk.edu
> Cc: ietf-nntp@academ.com
> Subject: Re: ietf-nntp My notes from the NNTP WG meeting at the 37th IETF
> Date: Thursday, December 19, 1996 7:07 AM
> 
> Gentlemen,
> 
> Please do not forget that AUTHINFO USER does NOT REQUIRE A PASSWORD.
> 
> I originally added it to facilitate gathering of readership statistics,
> and in that application, it needed only supply the username.
> 
> While AUTHINFO may be used to control access, that is not its only use.

While that might have been the intent, I believe every implementation
requires an AUTHINFO PASS after an AUTHINFO USER.  I may be wrong here
- but if I'm right, I'd rather RFC977 driven by current practices rather
than intentions.

So - are there any implementations that accept AUTHINFO USER without an
AUTHINFO PASS?

Nat

v2.8.7 | Report a Bug | By Email