Re: IAB agendas now public

Bob Hinden <bob.hinden@gmail.com> Thu, 06 September 2018 15:38 UTC

Return-Path: <bob.hinden@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 79749130E25 for <ietf@ietfa.amsl.com>; Thu, 6 Sep 2018 08:38:37 -0700 (PDT)
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_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=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 rC3d4V67KkXt for <ietf@ietfa.amsl.com>; Thu, 6 Sep 2018 08:38:36 -0700 (PDT)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 A1CC112F1A2 for <ietf@ietf.org>; Thu, 6 Sep 2018 08:38:35 -0700 (PDT)
Received: by mail-ed1-x529.google.com with SMTP id a20-v6so9256029edd.4 for <ietf@ietf.org>; Thu, 06 Sep 2018 08:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=CYrGlL3guiJ4D9YzGea4v/b3FNTvRh390w7wz42qUPk=; b=agMG1IXVx+bAhJ3lJHwQnmvMLqZcCs6LijiiQ0b3T9P853oeantI3LslcgHVq53U87 Y7C0oJR3RFx/Bqr6a5Ir5Qah3SXi4uq38k8EQdbDY0q+DvO5+FCr3r5fgVj94puLzFNd iP8n/QZ+a4ZrlYYunKkvaxT4fB8UEaq40u4OOXvLhVhWY+0GVMoF6TbNmEonqKf39+WO NVK0ss/Bn9TfX2UtO6yhns9F0rPoa2wZeAyYAM6F1ehxPhrtFAx7sHnHUlhf0cFDRrMQ lbzW78hZW1jSHCUNvMByynJMvsx3Lg8Gy1W7r236tEs2f6rnjYjBhAVdiuKgSWJHGI7b crJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=CYrGlL3guiJ4D9YzGea4v/b3FNTvRh390w7wz42qUPk=; b=bLtnUyXO7DCrn95fqnHVOP20gvjq7uPaoltuVSGZJ4VpFU7zaIBf6vBUyNI18m6y7R 3IejSfEikx5r/XvSx7pHjicXILRhaeDOz/9I4stMN23Z1Ok4VVxxVwGvQvURo6X6akBJ /W5u8kaddWI8MU4upsVzLnSrBBcE9iMObTu/R+GIuE90D2hoAxvW5yvxlUQi9OxPVwPP JL+hyaFg8mSfuK6MEAiDZSwOn0LsZot9h77bYYPsRO/ync7e+t3bNgl71+wwQmPtc0+x Zsb+b3VFXKXXEc51LhPXBXAcGYKqpxXwB9Up4wL6kUZGn7UJMz/FLwuXXIrpFUhJyIhE Vexg==
X-Gm-Message-State: APzg51DVDWZEDngipmP4e4soWBeY3or8hZgiUap7vQFstBRoSyl7p5no YdEV3J9aoNhqZ5IaGUee1X4=
X-Google-Smtp-Source: ANB0VdZORS3DEj6u28jEeuTFgv91vF2+UiIAA1MNdFwWEt6d6rfrQzG8orjO+u4TiHwEc3/oWJWodQ==
X-Received: by 2002:a50:baae:: with SMTP id x43-v6mr4275554ede.65.1536248314161; Thu, 06 Sep 2018 08:38:34 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:f3a:5ce3:e39c:b4c1:99f9? ([2601:647:4d01:f3a:5ce3:e39c:b4c1:99f9]) by smtp.gmail.com with ESMTPSA id s41-v6sm5155858edd.61.2018.09.06.08.38.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Sep 2018 08:38:33 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <94D1DA3E-C280-40D9-ADCF-ED8ADDDCB57B@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E95BD13D-4CB3-488B-9CEB-70F2B3DDEC03"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAB agendas now public
Date: Thu, 06 Sep 2018 08:38:30 -0700
In-Reply-To: <m2o9dau7ti.wl-randy@psg.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Christian Huitema <huitema@huitema.net>, IETF <ietf@ietf.org>
To: Randy Bush <randy@psg.com>
References: <b4afddcc-e8dc-9bd8-03d3-6374c29c4749@iab.org> <m2a7ownhl0.wl-randy@psg.com> <BC35696A-D4A6-47EA-A85C-EB472E42596E@lucidvision.com> <CA+9kkMCGNpFQGwEYZzn3CcOAdz_-GGMCP-N4jX_YuJ8tri0Bxw@mail.gmail.com> <fffabcb8-ee6f-d90b-f661-9011088b892b@gmail.com> <m2a7ovmzgk.wl-randy@psg.com> <9FA1C537-0B62-431F-B059-03C0813890CE@lucidvision.com> <m28t4fmyop.wl-randy@psg.com> <f4a99017-5483-2744-5f35-17620e123743@gmail.com> <3aed4068-a822-c5e6-c21d-b472f3e30373@huitema.net> <m2o9dau7ti.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ob88SkKuEt7EXTd6maEDeqPRCQU>
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: Thu, 06 Sep 2018 15:38:38 -0000

Randy,

> On Sep 6, 2018, at 5:30 AM, Randy Bush <randy@psg.com> wrote:
> 
>>> Yes. And I didn't mean that all politics should be in executive
>>> session. It's just that if the IAB needs to discuss how it should
>>> respond to external politically charged events, the discussion would
>>> happen in one of three ways:
>>> 
>>> 1. In an open session, in which case the IAB would be showing its
>>> weaknesses to the other parties.
>>> 
>>> 2. In an executive session.
>>> 
>>> 3. If #2 is not an option, in a secret meeting.
>>> 
>>> I like #3 less than #2. So if there's to be a new dispensation,
>>> I think the IAB needs to be able to hold executive sessions about
>>> external (non-I*TF) matters as well as the usual HR/legal matters.
>>> In general, I don't see why internal I*TF matters would need
>>> secrecy.
>> 
>> The IAB does a lot of discussions with external partners. Sometimes that
>> involves bargaining, and bargaining often involves a part of bluff. One
>> of the concerns is that if the IAB entirely discusses its bargaining
>> positions in open meetings, then the other party will effectively see
>> through the bluff, and the IAB/IETF negotiation position will be much
>> weakened.
> 
> so holding a secret meeting within a closed meeting to discuss a bof on
> the rfc series is
>  o perfectly fine
>  o a lapse of judgement (of course i have none of those :)
>  o a lapse of process
>  o your ad goes here?

If the IAB decided it needed to discuss an IETF BOF proposal in executive session something is seriously wrong.   This was not a personal matter, nor negotiating with another group, nor discussing individuals being considered for an open position.

This is very broken.

Bob