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

Terry Manderson <terry@terrym.net> Tue, 19 November 2019 07:04 UTC

Return-Path: <terry@terrym.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 BE95B12089D for <ietf@ietfa.amsl.com>; Mon, 18 Nov 2019 23:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=terrym-net.20150623.gappssmtp.com
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 CcGD4jgPzv06 for <ietf@ietfa.amsl.com>; Mon, 18 Nov 2019 23:04:13 -0800 (PST)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C67D120C67 for <ietf@ietf.org>; Mon, 18 Nov 2019 23:03:48 -0800 (PST)
Received: by mail-pg1-x533.google.com with SMTP id e6so2919278pgi.11 for <ietf@ietf.org>; Mon, 18 Nov 2019 23:03:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=terrym-net.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=hBS8ySW7DtXwuOYO+jka1Y42dIisUeLF9VElPwve18U=; b=Lz3YobWKC8v9dVyPiuO3LxDlPuMXEKZXmahHt0xIrj4nkKqJltSL0Cbbb+j3qAUV5D +BOj7Q2wWQo7gvHUGEG7eIGWcWQXNoWXDgfINPs4o6GCyYiwa49fgKiY747EvWt752BY otZjRkTuaL4wCPHvaCXQqc8+vyEWTRTtyJoW4izdD/BsCXUfkrC6m+SWHB94sXz7DfjL EqGRo4x4beI8VHqYnm+8970FaTjLqbvhPyd1fXKscIgJ876KJUcLgzm+2tO6XpIGMA7u X+peqRdlcVI+3a9osDsI5zxR4kYsUaFFlHv12yncJz9HG7/uBbonpe5j+SYohcp3uL2Q 3LYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=hBS8ySW7DtXwuOYO+jka1Y42dIisUeLF9VElPwve18U=; b=an6ChbPC4Pds3LrsE7nUOhBkHQfaZqnMmQtSuyaVnq4Jrpjd8lG8q0gC/szJkRqq0z 0VTwoAXzowZEazWxM4uZPU8V/9w0/WkoL24DjxCX+ZqD/11dNOGIj54rgDWvfCYQXmss ApODCK+CrDtSEf8TEJLnUQ83yd9K9+x2732sr7J+i6KJqdRBxKdDkqsMhNczgwWTy6eV hnpKRl85cJOehWKN23ZupDCy6Qyf8YSyH7SV+NhrusaP0N2lP9HMk/C6ZDgZuPMXeUJl kpN1pNa7XNfkShnT1BrEZpQ6sT0oxIAiKP11Ds18DBXE5Bsahuv1979tHoN8cmQ2iSF6 VByA==
X-Gm-Message-State: APjAAAWh98GqcnHAjVhCVbrd6rW5p48s0iufhDhmKDBeP+xzBaelRYZ1 55J+hu+7KzMW7IK79SRQEY5t1hJ4XiM=
X-Google-Smtp-Source: APXvYqztPky/iX3P7LLBsmdfH1A/yBFGcesiDeDPgBYhfajdJbx/l5UubnRWVYZ+LDu6Nx8VE/af1Q==
X-Received: by 2002:a63:2057:: with SMTP id r23mr3784625pgm.357.1574147028008; Mon, 18 Nov 2019 23:03:48 -0800 (PST)
Received: from [31.133.150.49] (dhcp-9631.meeting.ietf.org. [31.133.150.49]) by smtp.gmail.com with ESMTPSA id u7sm1885614pjx.19.2019.11.18.23.03.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Nov 2019 23:03:47 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: "An open letter" signed by some IAB members
From: Terry Manderson <terry@terrym.net>
In-Reply-To: <CALaySJJN23vFf-k2VqU0Mx+sOWV8wJiTBBkDGopjK7vOtYyDyA@mail.gmail.com>
Date: Tue, 19 Nov 2019 15:03:46 +0800
Cc: IETF discussion list <ietf@ietf.org>
Message-Id: <2616945B-2066-4AF3-A412-4B70D1A185F0@terrym.net>
References: <CALaySJJN23vFf-k2VqU0Mx+sOWV8wJiTBBkDGopjK7vOtYyDyA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: iPad Mail (17B84)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HoF7C7PbzIDqkeKrViIGBJdy7MY>
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 07:04:26 -0000

> On 19 Nov 2019, at 2:42 pm, Barry Leiba <barryleiba@computer.org> wrote:
> 
> 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.
> 

Wildly? I don’t share that view. Generally inappropriate - yes.

> happen again, and I hope the ensuing discussion supports that.
> 

The answer here, in my opinion, is fairly simple. 

If the IAB make a statement, we know what that looks like.

If a collective of individuals choose to make a statement then it is done with ALL of their credentials (with permission), or none of their credentials. If a company (as a part of their credentials list) decides to not allow someone to not include them, then I feel that person shouldn’t use any credentials aside from their own academic honorific.

This is something that was drummed into me years ago by a brilliant legal rep.
Simply; “you don’t speak for them, nor can you imply it, unless you have their express permission - removing some, but keeping others associates weight of support from an organisation” I remember those words so clearly.

Of course, YMMV.

Cheers,
Terry