Re: ietf-nntp Initial draft FINALLY available

Ben Polk <bpolk@netscape.com> Fri, 04 October 1996 02:16 UTC

Received: from cnri by ietf.org id aa28293; 3 Oct 96 22:16 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa28053; 3 Oct 96 22:16 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id VAA29276 for ietf-nntp-outgoing; Thu, 3 Oct 1996 21:14:04 -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 VAA29272 for <ietf-nntp@PHEASANT.ACADEM.COM>; Thu, 3 Oct 1996 21:14:02 -0500
Received: from hedgehog.mcom.com (h-207-1-136-17.netscape.com [207.1.136.17]) by academ.com (8.7.6/8.7.1) with ESMTP id VAA25113 for <ietf-nntp@academ.com>; Thu, 3 Oct 1996 21:13:58 -0500 (CDT)
Received: from bpolk.mcom.com ([207.1.137.51]) by hedgehog.mcom.com (Netscape Mail Server v1.1) with SMTP id AAA10449 for <ietf-nntp@academ.com>; Thu, 3 Oct 1996 19:13:25 -0700
X-Sender: bpolk@pdmail2.mcom.com
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf-nntp@academ.com
From: Ben Polk <bpolk@netscape.com>
Subject: Re: ietf-nntp Initial draft FINALLY available
Date: Thu, 3 Oct 1996 19:13:25 -0700
Message-ID: <19961004021325.AAA10449@bpolk.mcom.com>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

At 04:04 PM 10/3/96 +0000, chris (c.) lewis wrote:

>From another perspective, I don't believe AUTHINFO SIMPLE is actually
>implemented.  Isn't it purely something that got lost when the older
>NNTP-II spec got abandoned?  Both NNTP 1.5.x and INN 1.4 support
>AUTHINFO USER/PASS, as do a number of newsreaders.  Which I think meets
>the requirements for "at least two independent implementations".

The Netscape News Server uses AUTHINFO USER/PASS.  Not surprising, 
since it's based on INN 1.4.  But I think it's fair to claim that
it has diverged enough to be another independent implementation.
It uses the 480 response to indicate that authentication is
required.

The Netscape newsreader responds to 480 with AUTHINFO USER/PASS,
and 450 with AUTHINFO SIMPLE.  The 48x number space is too polluted
by common use to do anything but agree that it will be used for
authentication (IMO).  I don't know about 45x, but I suspect it
will cause a lot of problems as well.  These authentication required
responses are more problematic than a general 4xx error, because 
they often trigger a specific authentication response by the client, 
rather than just indicating an error has occurred. 

Should we add the response codes that NNTP extensions will use to
the information that is required to register them?