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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 19 November 2019 23:44 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 75CF212089B for <ietf@ietfa.amsl.com>; Tue, 19 Nov 2019 15:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UV2dXDosIt-k for <ietf@ietfa.amsl.com>; Tue, 19 Nov 2019 15:44:16 -0800 (PST)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 A4F5C12009E for <ietf@ietf.org>; Tue, 19 Nov 2019 15:44:16 -0800 (PST)
Received: by mail-pf1-x430.google.com with SMTP id s5so13204937pfh.9 for <ietf@ietf.org>; Tue, 19 Nov 2019 15:44:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=TBo0UwgBqeH+tGBa59V4pJ6Uy1l9M4EGCtBuW26PFuY=; b=XHYcutHZQ2hVxLtBNXj1fY6hqG7fh/3NhXD4iQj9Tz865LGpdW35F8UPgGOJfHUiyN /Q4aASQoKtVvwixopvcOupI4zd8FiMdZ5Vk8YqFheZPFpECXOeiCkVDHXsK/NfpRHX89 eDJNZliMExobI2v/KNLMRz/V3MPOyLaXN7BF74a6tV1KoIIPnqHjKS7YcyFKx87GGJxa /G7g/W4iLBPJQ3iwxi3FvKcXt4OqXMnJ+xe9dAPj+R59+dTAq9XQXQ6f9nJFwHfmLkhM O2GzHvPqUt77HLbOmdZghf3ygaoNj8NXZLogvSIUqhGYmHbqfGkREW6RItRNZn0Ob5BH EWeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=TBo0UwgBqeH+tGBa59V4pJ6Uy1l9M4EGCtBuW26PFuY=; b=coswUtnfDXDN3hgDXHyE5U2UzAF2UHf7G2972wSNDXF4qY+7MERA2FlSp46fnM5bU/ vGuUThnqynYygTRVYkXukIkOVBRlrmUT84QNAONOvEYHDAjVjsItIeS2KcCoH6Ypjurb Gz18evpYXpgYRo3Pw9u9mKhx9JskV9cAAByYMNDo9tamDS8WzcweOtU8cQA0KU313u7T fr0aAaUnNPd+R1xCSQgyn7Q+43uwyTr2TsSE+MXWZ0DsbafEjR7wb7vX3IhH5qV7kOt2 HL++TVOfgT015X8BcnXjlKdnRBYDoLE2fAzcdMqZDZQrTK0FiHMwye54phdOx+VbxMh7 gPSg==
X-Gm-Message-State: APjAAAVMezELkMPlUPr6El+5e2FoEC7OtINFryoiz7NKtfZMiwBQJkBs Jn5RyUgHURKbRUKYg4LMAl4gzFc7
X-Google-Smtp-Source: APXvYqxse9mZbmLLnkcTK3uDlmSwwQ+rm6wV/+Y8+amd6pQB112TnspoDRHmli7JMlJUNa0Sl2Dvfg==
X-Received: by 2002:a62:e914:: with SMTP id j20mr283667pfh.245.1574207055694; Tue, 19 Nov 2019 15:44:15 -0800 (PST)
Received: from [31.133.158.74] (dhcp-9e4a.meeting.ietf.org. [31.133.158.74]) by smtp.gmail.com with ESMTPSA id v189sm27177970pfv.133.2019.11.19.15.44.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 15:44:14 -0800 (PST)
Subject: Re: "An open letter" signed by some IAB members
To: Nico Williams <nico@cryptonector.com>
Cc: IETF discussion list <ietf@ietf.org>
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> <F8691CFF-C683-4159-AD70-E1A4E4701A39@mnot.net> <20191119183144.GA26241@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <98efc3ee-640f-4d74-3726-cc2ecc37c881@gmail.com>
Date: Wed, 20 Nov 2019 12:44:13 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20191119183144.GA26241@localhost>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jz3PYHTyxMN3D20HaPJZQEex78U>
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 23:44:20 -0000

Nico,

On 20-Nov-19 07:31, Nico Williams wrote:
> On Tue, Nov 19, 2019 at 05:18:41PM +0800, Mark Nottingham wrote:
>> 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.
> 
> Excellent and clarifying analogy.  MPs and such often speak publicly for
> themselves while using their membership of whatever august/lame body
> they are members of, yet no one mistakes their speech for that of the
> larger body.
> 
> Since the IAB does not speak for the community, ISTM that the only ones
> with authority to object are the IAB itself, and maybe its chartering
> authority.

The chartering body is the IETF, since the IAB charter is a BCP.

> That doesn't mean that IETF participants can't object to IAB members
> using their IAB membership as a credential, but it does deny those
> objections weight.

The IETF as a whole could legitimately object, presumably by way of
persuading the IESG to call a rough consensus to do so. So Barry's
objection could have been signed "Barry, an IETF participant", but
it wasn't. It did not request any action by the IAB or the IESG, or
ask for support for Barry's viewpoint. Comment is free.

It's certainly better to keep the underlying issues out of IETF
debates, except when we tread with great care as we did for RFC1984,
RFC2804 and RFC7258. Using those RFCs in civil society debates is
more ISOC's job than the IETF's, IMHO. I do agree with the idea
that when speaking in public on such sensitive matters, it is wise
to be very precise about the role in which one is speaking, e.g.
"IAB member, writing in my private capacity" or something like that.

  Brian Carpenter, an IETF participant, writing IMNSHO