Re: Spam in the IETF's name?
John C Klensin <john-ietf@jck.com> Thu, 20 October 2005 17:39 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESeNf-0006bw-UH; Thu, 20 Oct 2005 13:39:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESeNe-0006ab-5v for ietf@megatron.ietf.org; Thu, 20 Oct 2005 13:39:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02488 for <ietf@ietf.org>; Thu, 20 Oct 2005 13:38:56 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESeZb-00027E-TT for ietf@ietf.org; Thu, 20 Oct 2005 13:51:29 -0400
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1ESeNS-0003iK-6E; Thu, 20 Oct 2005 13:38:54 -0400
Date: Thu, 20 Oct 2005 13:38:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, Brian E Carpenter <brc@zurich.ibm.com>
Message-ID: <62E9EA464959C69379D2CC82@scan.jck.com>
In-Reply-To: <8C1D3011ABF32F7AEB3D8477@svartdal.hjemme.alvestrand.no>
References: <ECB22632E1E1FAD19E47FFAB@B50854F0A9192E8EC6CDA126> <43576C59.1090802@zurich.ibm.com> <1115CFE58B1D40A44FA946E8@scan.jck.com> <4357B321.6010906@zurich.ibm.com> <8C1D3011ABF32F7AEB3D8477@svartdal.hjemme.alvestrand.no>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Spam in the IETF's name?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
--On Thursday, 20 October, 2005 17:17 +0200 Harald Tveit Alvestrand <harald@alvestrand.no> wrote: > --On torsdag, oktober 20, 2005 17:09:21 +0200 Brian E > Carpenter <brc@zurich.ibm.com> wrote: > >> We do, however, pay quite close attention to ensuring that >> meetings that *haven't* been sanctioned by an AD don't use >> the IETF's name inappropriately. But statements such as "we >> are meeting in the same hotel as the IETF" are factual, and >> we can't complain at factual statements. Right. But "meeting at the IETF" or "meeting at the IETF meeting" are, intentionally or not, deceptive in ways that "meeting in the same hotel as the IETF" or "meeting near the IETF" or "meeting at the same time as the IETF" are not. I read the material Harald posted, as well as the material that touched off a similar controversy around our Paris meetings, as much closer to the first two statements than to the others. And I am suggesting only that organizations or groups whose lists we choose to recognize, whom we give access to IETF mailing lists for distribution of announcements, etc., should, in turn, be required to take on an affirmative obligation to be extra-careful to avoid confusion with IETF-approved activities. This really has nothing to do with whether statements are factual or not, only with whether the statements are presented in a form that is likely to create confusion with IETF activities while using IETF facilities or resources. > In the case of this particular person, he was using "we" quite > a lot, and without mentioning any organization but the IETF. > I think anyone who wasn't an "IETF insider" would assume that > the writer spoke on behalf of the IETF - >... And, again, I believe that a group that uses _any_ IETF facilities or that expects any IETF recognition, needs to take on an affirmative obligation to avoid that sort of confusion whether it is deliberate or not... and that we have some obligation to make that expectation, and models of ways to avoid the confusion, clear. john _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Spam in the IETF's name? Harald Tveit Alvestrand
- Re: Spam in the IETF's name? Brian E Carpenter
- Re: Spam in the IETF's name? Harald Tveit Alvestrand
- Re: Spam in the IETF's name? John C Klensin
- RE: Spam in the IETF's name? Hallam-Baker, Phillip
- RE: Spam in the IETF's name? John C Klensin
- Re: Spam in the IETF's name? Brian E Carpenter
- Re: Spam in the IETF's name? Harald Tveit Alvestrand
- Re: Spam in the IETF's name? RL 'Bob' Morgan
- Re: Spam in the IETF's name? Frank Ellermann
- Re: Spam in the IETF's name? John C Klensin
- Re: Spam in the IETF's name? Jeroen Massar
- Re: Spam in the IETF's name? Brian E Carpenter
- Re: Spam in the IETF's name? Brian E Carpenter
- Re: Spam in the IETF's name? John C Klensin
- When to announce a new mailing list on ietf-annou… Dave Crocker
- Re: When to announce a new mailing list on ietf-a… Brian E Carpenter
- Re: Spam in the IETF's name? Brian E Carpenter
- Re: When to announce a new mailing list on ietf-a… Dave Crocker
- Re: When to announce a new mailing list on ietf-a… John C Klensin