W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2007

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

From: tom.petch <cfinss@dial.pipex.com>
Date: Mon, 10 Sep 2007 19:09:33 +0000
Message-ID: <017301c7f3d4$d6e9a080$0601a8c0@pc6>
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>




----- Original Message -----
From: "der Mouse" <mouse@Rodents.Montreal.QC.CA>
To: <ietf-http-auth@osafoundation.org>; <discuss@apps.ietf.org>; <saag@mit.edu>;
<ietf@ietf.org>; <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
Received on Monday, 10 September 2007 19:25:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:16 GMT