Tools logins -- Aaaargh!

"Worley, Dale R (Dale)" <> Tue, 31 August 2010 16:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D1A8E3A67F3 for <>; Tue, 31 Aug 2010 09:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.398
X-Spam-Status: No, score=-102.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id XNxSafeni5Xe for <>; Tue, 31 Aug 2010 09:08:27 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CBB6D3A690F for <>; Tue, 31 Aug 2010 09:08:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,299,1280721600"; d="scan'208";a="32486775"
Received: from unknown (HELO ([]) by with ESMTP; 31 Aug 2010 12:08:57 -0400
X-IronPort-AV: E=Sophos;i="4.56,299,1280721600"; d="scan'208";a="510495425"
Received: from (HELO ([]) by with ESMTP; 31 Aug 2010 12:08:56 -0400
Received: from ([]) by ([2002:870b:3414::870b:3414]) with mapi; Tue, 31 Aug 2010 12:08:56 -0400
From: "Worley, Dale R (Dale)" <>
To: "" <>
Date: Tue, 31 Aug 2010 12:08:56 -0400
Subject: Tools logins -- Aaaargh!
Thread-Topic: Tools logins -- Aaaargh!
Thread-Index: AQHLSSbQ/HamLvI680SyvLxqw+yrlQ==
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 Aug 2010 16:08:27 -0000

There is probably a better place to complain about this, but...

There are various IETF "tools" web pages.  But I have a devil of a time using them because they do not identify themselves usefully when asking for a login.  There are multiple login databases in the whole IETF tools suite, and experienced users know which database controls access to which tool.  But for us unwashed masses, there is no way to guess which web pages demand which password because they are named inconsistently.

Let me propose:

* Each password database has a *single* name which is the only name that it is ever referred to by, such as "IETF tools login" and "IETF datatracker login".

* Each login prompt gives the *single* name of the password database that it is driven by.

Otherwise we get such messes as "" demanding an IETF tools login -- not IETF datatracker login -- and its login prompt identifying the realm only as "IETF".  Which is pretty useless to the uninitiated, since "track", "tools", and "IETF" are all present.

(I'm continuously amused by the fact that a roomful of computer geeks, who spend their days making unambiguous descriptions of operations to computers are unable to make an unambiguous description of an operation to humans.)