Re: ietf-nntp AUTHINFO GENERIC (no args) proposal

Brian Hernacki <bhern@netscape.com> Wed, 11 December 1996 04:30 UTC

Received: from cnri by ietf.org id aa16991; 10 Dec 96 23:30 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa00552; 10 Dec 96 23:30 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id WAA09359 for ietf-nntp-outgoing; Tue, 10 Dec 1996 22:28:25 -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 WAA09354 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 10 Dec 1996 22:28:14 -0600 (CST)
Received: from c3po.mcom.com (h-205-217-237-46.netscape.com [205.217.237.46]) by academ.com (8.8.3/8.7.1) with ESMTP id WAA11939 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 22:28:12 -0600 (CST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by c3po.mcom.com (8.7.5/8.7.3) with ESMTP id UAA12688 for <ietf-nntp@academ.com>; Tue, 10 Dec 1996 20:27:41 -0800 (PST)
Received: from elmo ([205.217.240.186]) by dredd.mcom.com (Netscape Mail Server v2.02) with SMTP id AAA8470; Tue, 10 Dec 1996 20:27:39 -0800
Message-ID: <32AE37D8.3B38@netscape.com>
Date: Tue, 10 Dec 1996 20:26:00 -0800
From: Brian Hernacki <bhern@netscape.com>
Reply-To: bhern@netscape.com
Organization: Netscape, Floating Point Division
X-Mailer: Mozilla 3.01 (WinNT; I)
MIME-Version: 1.0
To: Nat Ballou <NatBa@microsoft.com>
CC: ietf-nntp@academ.com
Subject: Re: ietf-nntp AUTHINFO GENERIC (no args) proposal
References: <05e0b1857000bc6IMSMAIL@ims.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Nat Ballou wrote:
> Actually, it's supported by the Microsoft News Server (you can download
> it from www.microsoft.com) and is the preferred way for clients to
> negotiate
> authentication packages.
> 
> Is that sufficient for this to be added to the draft?

That would be something we would need to decide at the IETF
meetings...what exactly defines an "existing/de-facto standard". My
first intuition is that there will be some requirement about use in
shipping products...maybe a minimum number of implementations. 

On the other hand, I like the idea of being able to list the auth
packages supported, but I think it would make an excellant extension via
the new LIST EXTENSIONS method.

-brian