Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)

"tom.petch" <cfinss@dial.pipex.com> Mon, 10 September 2007 19:09 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUodS-0002MT-8o; Mon, 10 Sep 2007 15:09:26 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1IUodQ-0002MO-Js for discuss-confirm+ok@megatron.ietf.org; Mon, 10 Sep 2007 15:09:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUodQ-0002MC-9c for discuss@apps.ietf.org; Mon, 10 Sep 2007 15:09:24 -0400
Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUodO-0000Ws-TO for discuss@apps.ietf.org; Mon, 10 Sep 2007 15:09:24 -0400
Received: from pc6 (1Cust35.tnt29.lnd3.gbr.da.uu.net [62.188.120.35]) by ranger.systems.pipex.net (Postfix) with SMTP id 9FF6EE000718; Mon, 10 Sep 2007 20:09:14 +0100 (BST)
Message-ID: <017301c7f3d4$d6e9a080$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "der Mouse" <mouse@Rodents.Montreal.QC.CA>, <ietf-http-auth@osafoundation.org>, <discuss@apps.ietf.org>, <saag@mit.edu>, <ietf@ietf.org>, <ietf-http-wg@w3.org>
References: <46E2E54A.2050406@isode.com><8B056441-7E57-46D4-9A2C-5BF7DE0297BF@muada.com> <200709101426.KAA03299@Sparkle.Rodents.Montreal.QC.CA>
Subject: Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
Date: Mon, 10 Sep 2007 16:45:36 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: -102.6 (---------------------------------------------------)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc:
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

----- Original Message -----
From: "der Mouse" <mouse@Rodents.Montreal.QC.CA>
To: <ietf-http-auth@osafoundation.org>rg>; <discuss@apps.ietf.org>rg>; <saag@mit.edu>du>;
<ietf@ietf.org>rg>; <ietf-http-wg@w3.org>
Sent: Monday, September 10, 2007 4:14 PM
Subject: Re: [saag] Next step on web phishing
draft(draft-hartman-webauth-phishing-05.txt)


> > I really dislike the use of "fishing" with creative spelling in a
> > document prepared for an international standards organization.
>
> Perhaps unfortunately, that is *the* word for the behaviour in
> question, at least in English.  It was not invented for the draft, and
> "com[ing] up with something [else]" would be *less* descriptive and
> would render the document cryptic to the people who's been working
> against phishing for years.  Perhaps it's a bad word to use in other
> languages, but that should be addressed by the translator(s) in
> question, not by mangling the original.
>

Stick the word in quotes which conveys the message that we know that this is not
a good piece of terminology, but that we are pragmatic enough to recognise that
using it will convey the right meaning to most people.

But on the other strand under this Subject:, I am with those who think that the
IETF has demonstrated an absence of consensus and that the proposed way forward
to try and achieve it by other means in plain wrong.

Tom Petch