Re: Transparency of IAOC

Ted Lemon <mellon@fugue.com> Tue, 12 April 2016 20:34 UTC

Return-Path: <mellon@fugue.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 69EC012D553 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.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 HXjFJ0pI5zT9 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:34:17 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 8585B12B044 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:34:17 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id j11so41804219lfb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:34:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vuuG4JxzuTf1mo7c30avGcgzlEcLGyf0/Zuh9BSaMh8=; b=JvJ9vczj4xZyvgbcs7ryLgIqfkB5HIrNcRXJXwJIeH/g+y5vR9XEflIR8Sl8YCKuP4 P08yR5K0ITg3E6D9wAo2Xxovmyp52MVRZa0+9Jk3SxKk+/NiHcxepQ8Sk0uSCsJIBPNZ 54KMa8XtwbU6zJYotyQnBWnLhLOnaE/Q8YPFm8OIZZQMEFnAtFwhxaQN4TyksIhZ9Fel 7SsZXEh1F70GvFWkprclf8R4bMbBVk3RdkX+nJSYPFDv4gEmzQT2dBcuwc0juu/0JRMP bhqZppH6/xtxmRKIRiCDdQBG6jCR00GAzOVO7/CXq4wzssNK/ORP6WsJS+UqmdV7F4c9 MPyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vuuG4JxzuTf1mo7c30avGcgzlEcLGyf0/Zuh9BSaMh8=; b=m81gxVqpXB6QqNvpyQH9QW7FX9lTOCIGqKEUm8TWyDCNGyIZXO2mR5FbRe8B29Vhjl rf2mT6ESWLnkvcJj8la/RSzCL40GB9wl9zepnhS44Rhslrm0aCqI6C3SxXt2ynF+0Y84 Dv+o1ba8gRv2QOrtd9QZADPIPMlDVNs6IG+8W17FNDz3IuSTJSvm0CseHJcJVzMHx/rU m7boRLnIYvVI1aEQzu4Fcjpsax8HMUwxhmx5mNCHVX1Zd5DjiIHz4rrgSXaFOwHedHXE SnBjUitSQjnkx7XaTYWPuAr2UuGDFlCz6WavbB0uiS+e2LN0LA0RdDHFSj+Di9kbRbyt gQig==
X-Gm-Message-State: AOPr4FWzIJJAV+njy4OUVQ/WxECijGYzalJeC0V/+hCsF04CkPfwr680Uogm52oZ72zRDCNcF0WK8qFwVU35ag==
X-Received: by 10.112.143.40 with SMTP id sb8mr2273310lbb.83.1460493255700; Tue, 12 Apr 2016 13:34:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 13:33:36 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 16:33:36 -0400
Message-ID: <CAPt1N1kVbJdFH-XYpD7FREOooQOn3BYu20tvWSZFR7TrROMP4g@mail.gmail.com>
Subject: Re: Transparency of IAOC
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=089e011832bab407ac05304f952e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nKoEVNO_0Ysun4xE8_YqGyKREaU>
Cc: Dave Crocker <dcrocker@bbiw.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Apr 2016 20:34:19 -0000

On Tue, Apr 12, 2016 at 4:00 PM, SM <sm@resistor.net> wrote:

> Is it appropriate to ask questions to the IAOC?  I don't see people who
> have been part of the "leadership" doing that.  Maybe, it will be viewed as
> politically incorrect and it is not good for a person's IETF career.  In
> other words, it is a matter of perception.
>

I feel I can speak as an authority on this topic when I say that there is
zero chance that this is a problem.   If the IAOC do not always do what we
want, it is because (a) that is impossible, since there is no "we" that is
both in agreement and also representative of the wishes of all IETF
participants and (b) I know everybody on the IAOC and they just don't
behave as if they think complaining by IESG people is a problem.   Granted,
that's not necessarily always a good thing, but IESG people say plenty of
things to the IAOC about stuff like this, and I have never seen them act in
the slightest bit impatient about it.   Not only that, but we had a BoF in
BA about this topic.

Importantly, while the IESG is officially the host for IETFs, and therefore
obviously should have some say in this sort of thing, if we want more
transparency from the IAOC, it is we, the participants in the IETF, who are
responsible for asking for it, not the IESG, except to the extent that like
us, they are participants.