Re: [irtf-discuss] [arch-d] [Aid-workshop-pc] Why closed IAB workshops ? Re: Call for Papers: Workshop on Analyzing IETF Data (AID), 2021

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 31 August 2021 14:59 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C033A180F for <irtf-discuss@ietfa.amsl.com>; Tue, 31 Aug 2021 07:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 38hodWIGQaKl for <irtf-discuss@ietfa.amsl.com>; Tue, 31 Aug 2021 07:59:42 -0700 (PDT)
Received: from mail-yb1-f175.google.com (mail-yb1-f175.google.com [209.85.219.175]) (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 4E0613A1811 for <irtf-discuss@irtf.org>; Tue, 31 Aug 2021 07:59:42 -0700 (PDT)
Received: by mail-yb1-f175.google.com with SMTP id k78so32340261ybf.10 for <irtf-discuss@irtf.org>; Tue, 31 Aug 2021 07:59:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pE/iHbQBlDdga671BP/pnf3mTU7gk/+GjpsnVdH2sB0=; b=bM6qangnHDrJuHAmmmBTVwZx3lPX1DnlmL238OjaTVZchJifok4ANlBStjZRg2bZM8 VejnC28PJrOJ8y5+84Y9piHifJANG4sDIZq3R0YR4nGxpHnoMtZKM2jVZrHRYSl2r3PM +IJaB6J61YzC8mwgeer8j72bwRCKiwvpqZmbsAKwy3VOIOF+dSq4uEhGe8JXE7rMjFGW dglqQWL3PG5c0Fr46WO0x5lgLPTTwbg3fWdSqb6tz0dHEF9gUGPD4K5QDh4g9W/5Zmt9 XsEgUTVWAx4/fVXKgDkqV4RUA0sxD3cfjnS8KY8eF26bgX9MnU9tVZZ14b3wrt04kd8m GavA==
X-Gm-Message-State: AOAM532DPTsRc0kfTx94/zaxyBMMA+iyDkIYCHMVOO5WJtODDCKd7cxG pnJT4SMBWsK69mA39mK6D7bhhLv1JL+OMTptnU03OwRMJnddCA==
X-Google-Smtp-Source: ABdhPJwIyUp/p2AUNFfZ+ReJZ7C/lvuzeQSn8yOQWsB5PY63ImTtdW8m+YGRzEwRiwBV9pCXO2VAqw3ZPXXmweokGSw=
X-Received: by 2002:a25:5246:: with SMTP id g67mr2903775ybb.56.1630421981486; Tue, 31 Aug 2021 07:59:41 -0700 (PDT)
MIME-Version: 1.0
References: <CBAEDD86-0AE5-4765-98BE-8543F660F1E3@gmail.com> <39EBCAC2-D929-4E58-986F-EBDAFAD25BAA@kuehlewind.net> <44E8C862-AA4C-4372-92FC-0C0555613758@akamai.com> <33c21710-ea73-baee-ed11-9c40d735c559@gmail.com> <5C915492-FB9F-4C8D-B93D-E6840A32B9A0@akamai.com> <249F05BB-AB49-41FC-B404-B642818CFCBB@gmail.com> <CAHw9_iKTJBCHrLwZctawoAdiP0OxsC3j-hPLB2fjmD0d-dBPJQ@mail.gmail.com>
In-Reply-To: <CAHw9_iKTJBCHrLwZctawoAdiP0OxsC3j-hPLB2fjmD0d-dBPJQ@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 31 Aug 2021 10:59:30 -0400
Message-ID: <CAMm+Lwh9DO5brbjsYb4wDOpJz9teiNzQ7CSUnAHJQDJ+i+A+ZQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Cc: Bob Hinden <bob.hinden@gmail.com>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "aid-workshop-pc@iab.org" <aid-workshop-pc@iab.org>, IETF <ietf@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, "iab@iab.org" <iab@iab.org>, "Mirja Kühlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary="0000000000000a613005cadc33f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/i4Qc2pGSv3H-59_HDwzsyfXLnfA>
X-Mailman-Approved-At: Tue, 31 Aug 2021 09:04:04 -0700
Subject: Re: [irtf-discuss] [arch-d] [Aid-workshop-pc] Why closed IAB workshops ? Re: Call for Papers: Workshop on Analyzing IETF Data (AID), 2021
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2021 14:59:44 -0000

I have attended many meetings under Chatham house rules, I can't remember
doing an IETF meeting under one but would have no problem with that. I
would much prefer we had Chatham House than humming.

There are many reasons for holding Chatham House and not necessarily the
ones people assume. It is really not about attribution. First thing you
learn at corporate spokesperson school is there is no such thing as off the
record. If I go off the record with a journalist, it is for the specific
purpose of explaining something to them that I have already discovered they
are confused on and want to attempt to unconfuse them.

The real advantage of Chatham House it allows people to say something that
is incredibly stupid and get reactions.


I can't say what or who of course, but lets say that a person retired from
a very senior position says something that is 'could this start a nuclear
war' level stupid.

So a hypothetical is then given in about 20 words which the next person
reduces to 'redlines require immediately perfect attribution'.

And that counter argument is exactly what the original speaker was looking
for in the first place: a concise argument against framing information
engagement in the same terms as the nuclear deterrence strategy the
participants had developed.


One of the many pathologies of IETF meetings is that they are constructed
so that we spend rather too much time arguing for our positions and not
enough looking to find the right position.

>