Re: "An open letter" signed by some IAB members

Mark Nottingham <mnot@mnot.net> Tue, 19 November 2019 09:18 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6211F120C1C for <ietf@ietfa.amsl.com>; Tue, 19 Nov 2019 01:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=ugp1KjDB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=iKm6V3eZ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ql5Sy6-ZqZ6 for <ietf@ietfa.amsl.com>; Tue, 19 Nov 2019 01:18:51 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07A08120BE7 for <ietf@ietf.org>; Tue, 19 Nov 2019 01:18:50 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 15A052208A; Tue, 19 Nov 2019 04:18:49 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 19 Nov 2019 04:18:49 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=u TKarSCvjJ/D+2cwOYiN/rp7hegvC0wnmO+AiYaJxMU=; b=ugp1KjDBZY5PpMEmn koatADvztrJXllkfSHzLkj/JpGpSb16uBKmR9qWLyPR35eYPu5VdhocAtNnFbHib cN387xrtwQMkSRja8OKkSCfzhRGaq7YQeAYohaaPguVF5AhM/gQclb/nfDS/jRaY xFm8YXq9NRP/JnKz0j1lmyyXlF++QQNnDcmRPG/7tVVa561KFHktPDhBcMl38DE7 MtdoLClsZ5axDD7e4s0b3+/8UXqoDnrgYoo9C8hTg7cE2x82UaAKIvnUr2X9n5o6 ag4py9AhgPxFUhK6QaUy+9HnW+/xnP2qrk1zW1elRNY66uVZ9bAMf2S0FZVcIXo8 8BKcQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=uTKarSCvjJ/D+2cwOYiN/rp7hegvC0wnmO+AiYaJx MU=; b=iKm6V3eZ+GI3wpckuKC2sABhABYNRijUyZuEO7XZcxa0UFDzG7KIirMWw ywrBLHL0DxPMBPjUjmY+9wdE+YPPPkzDWQlJhMjbhQvjnDMWQChNUjcQ8U8Bxkxm SbJAnvPxVSctA7EwYcnM6NRjyMJ/A2XGCLNzSkipsrVH/j5AZ58GBYMJeHOewnns iYnye8LvMHDbs0DxWHkamw43Pq+JwFYl/ieX5rWGRHQ0ZwEyhxFse8EbUmveFKSw U95p9LdBNHz3e7p5+YLkzViRNaTh7ftuPAiLoa7ryxRSPCdxtAY6Jjedkkcqy1ut pyXnIcwZqwsp/JfLyGzdlLspdAHKw==
X-ME-Sender: <xms:drPTXf20jvdcdvv1uFAwkMSL5AhwlI2splQjbnvF-0-zZeHwUv5faQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudegkedgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh epmhhnohhtrdhnvghtpdhmvgguihhumhdrtghomhdpthhhvghiphhviegtohhmphgrnhih rdgtohhmnecukfhppeefuddrudeffedrudehtddrudegfeenucfrrghrrghmpehmrghilh hfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:drPTXVvWUdWuMRwsXExlvdr0JOI6mOCgqQ8Wuw6rBmnYeV3Ht-AcFg> <xmx:drPTXQEOG_ZK5srfoJvq2KoVtsn1xADXvACdiZ82ucS09F3bU4cTzw> <xmx:drPTXc3Bx0W-ic8055Nsa28ORCU781lMkEN9pbJCndE4WVoIiUyk4g> <xmx:ebPTXVVGAkHT5nu6U_2Kj8u4z2J_cCKsOy5m8xT6FNzWYvl9UG8oFw>
Received: from dhcp-968f.meeting.ietf.org (dhcp-968f.meeting.ietf.org [31.133.150.143]) by mail.messagingengine.com (Postfix) with ESMTPA id ABC27306005B; Tue, 19 Nov 2019 04:18:45 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: "An open letter" signed by some IAB members
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <683EF30F-7EB0-424F-AFC7-F342BFB59642@consulintel.es>
Date: Tue, 19 Nov 2019 17:18:41 +0800
Cc: IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8691CFF-C683-4159-AD70-E1A4E4701A39@mnot.net>
References: <CALaySJJN23vFf-k2VqU0Mx+sOWV8wJiTBBkDGopjK7vOtYyDyA@mail.gmail.com> <0F893F23-FDEF-45F0-9A5B-839A1E4DB0E8@consulintel.es> <6964E3F0-06EC-4770-A0B2-E572E0240D59@mnot.net> <683EF30F-7EB0-424F-AFC7-F342BFB59642@consulintel.es>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/84GsDsIWQzClvcjPYrhjOeFkjRU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2019 09:18:59 -0000

Hi Jordi,

Yes, I agree that clarity here is good. However, "Member of IAB" is pretty specific, just as "Member of Parliament" is specific; it is clearly distinguishing the part from the whole.

There are mitigating factors here (as discussed) where it could have been more clear, and I appreciate the need for honest attempts to be as clear as possible. What I was trying to get at was that I suspect that a large part of the problem is that a letter that is only signed by members of a board can easily give the impression that it's from that board -- something that others have noticed too. Avoiding that impression is good, but that doesn't mean we should generalise this instance into a rule about all mentions of affiliation.

Cheers,


> On 19 Nov 2019, at 5:09 pm, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> 
> Hi Mark,
> 
> I know is not always easy. I use some times my company name and even email instead of a private one even if I'm speaking on my own personal capacity ... I feel that we all in general, should clear state in which capacity we are speaking. Is good, nice and convient to say "I work here and volunteer here" as well, of course, but if clarified if it is an IAB (in this case) view of personal one.
> 
> However, in all the cases that you mention, the solution that I mention, makes it very clear. In case all the folks that sign are on their own, a footnote "stating it" or alternatively a similar text, below each of the signatures (when there is mixture of cases).
> 
> Regards,
> Jordi
> @jordipalet
> 
> 
> 
> El 19/11/19 17:00, "ietf en nombre de Mark Nottingham" <ietf-bounces@ietf.org en nombre de mnot@mnot.net> escribió:
> 
>    I suspect part of the issue here is that the letter is signed *only* by IAB members, not mixed with others - and so I agree that such a clarification would have been helpful.
> 
>    Question: Would people have felt such a clarification were necessary if it these names were mixed in with non-IAB (and non-IETF) names and affiliations?
> 
>    And, would people have had an issue if it were signed only by one person who used their affiliation (as a *member* of the IAB, not the whole)?
> 
>    To put it another way -- sometimes I give talks and mention that I'm a member of the IAB, and sometimes I omit other affiliations that I hold or have held (for example, it's rare that I need to trot out that I served as president of my local primary school for several years). Are people seriously suggesting that this is out of line?
> 
>    Cheers,
> 
> 
>> On 19 Nov 2019, at 4:48 pm, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
>> 
>> While I believe that anyone has the right to state his position at any organization, never mind is paid or not (unless a contractual clause disallows that), I think that when it is not an official position of that organization, it should be done stating clearly "that is a personal opinion".
>> 
>> Something in the line of a footnote clearly indicating that this letter is not the "official position of the IAB" (for this specific case).
>> 
>> Otherwise, tomorrow, a few of us can sign a similar letter showing below our names "Member, IETF", and who is reading it, probably will not recognize that we aren't "empowered" to sign as IETF, as we are just a bunch of participants, but not speaking from the IETF.
>> 
>> And so, clearly agree with Barry here.
>> 
>> 
>> Regards,
>> Jordi
>> @jordipalet
>> 
>> 
>> 
>> El 19/11/19 14:42, "ietf en nombre de Barry Leiba" <ietf-bounces@ietf.org en nombre de barryleiba@computer.org> escribió:
>> 
>>   Perhaps some of you have seen that Ted Hardie posted an open letter on
>>   the Hong Kong high court’s injunction on Internet speech:
>>   https://medium.com/@ted.ietf/an-open-letter-on-the-hong-kong-high-court-injunction-on-internet-speech-7f0048df2f54
>>   The letter is signed by Ted and is co-signed by three other IAB
>>   members, each signing as an individual: the letter is not from the IAB
>>   and doesn’t claim to be.
>> 
>>   Nevertheless, note that all signatories identify themselves as
>>   “Member, Internet Architecture Board”, and three of the four do not
>>   list their company affiliations.  This has two effects:
>> 
>>   1. By being signed by four IAB members who are identified primarily as
>>   IAB members, the letter *appears* to be from the IAB.  I have passed
>>   this by three non-IETF friends, asking them who they think the letter
>>   is from, and all three said, “The Internet Architecture Board.”
>> 
>>   2. By using “Member, Internet Architecture Board” this way, those
>>   signing the letter are effectively (whether by intent or not) using
>>   their IAB positions to gain credibility for their personal opinions.
>> 
>>   I think this is wildly inappropriate.  I think those of us in IETF
>>   leadership should be scrupulously careful NOT to call out our IETF
>>   affiliations this way unless we are speaking for the organization.
>>   The fact that the letter refers to things that have been published
>>   with IAB consensus doesn’t change the fact that the *letter* does not
>>   have IAB consensus, and we must be careful not to give the impression
>>   that it does.
>> 
>>   I’ve discussed this with Ted, who thinks that there’s nothing wrong
>>   with how the letter was signed and posted.  That disturbs me.  I tried
>>   to let it go, but I’m sufficiently bothered by it that I felt the need
>>   to take it to the community.  This is that.  Ted tells me that all IAB
>>   members were invited to co-sign the letter, and that none brought up a
>>   concern about the use of the “Member, IAB” affiliation.
>> 
>>   As you think about this and — I hope — discuss it, please keep this in mind:
>> 
>>   - I’m NOT talking about the content of the message and whether I do or
>>   don’t agree with it.  That’s not the point.  I hope that as we discuss
>>   this we do NOT go into the content, the politics, and so on.  Let’s
>>   please keep this highly charged issue out of IETF discussions.
>> 
>>   - I’m NOT looking to beat Ted up here; what I want is for this not to
>>   happen again, and I hope the ensuing discussion supports that.
>> 
>>   -- 
>>   Barry
>> 
>> 
>> 
>> 
>> 
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.theipv6company.com
>> The IPv6 Company
>> 
>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
>> 
>> 
>> 
> 
>    --
>    Mark Nottingham   https://www.mnot.net/
> 
> 
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 

--
Mark Nottingham   https://www.mnot.net/