Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 07 February 2016 00:29 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEEB81A8864 for <ietf@ietfa.amsl.com>; Sat, 6 Feb 2016 16:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 MF9tllki6fQJ for <ietf@ietfa.amsl.com>; Sat, 6 Feb 2016 16:29:09 -0800 (PST)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (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 04C511A885A for <ietf@ietf.org>; Sat, 6 Feb 2016 16:29:09 -0800 (PST)
Received: by mail-pa0-x230.google.com with SMTP id cy9so54157872pac.0 for <ietf@ietf.org>; Sat, 06 Feb 2016 16:29:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=rCZ6k35/nBqMpxgmeuVdv6KMBQ4oHVGssWX2JK+/T80=; b=qKqJjramZa8jyYxSZlmgxb2VHnCmOGVpuYx0RTNsaEeHbsFgQc0RVYtAEuaXY1Gt+P EIOB+Vh0CDftzNBNmWO1L634et7euLpk6FXucS5NXSxBqDRQx8Gnd7yDIhp/Gxorq3Da SwmOeMO1Bda7Qju385yFH1LxvdzoSbyyiNqwVp72qYLJWOHKClo7QhtZYR8wzNx7v+Yw 91pzyf3CITe8CRIKiN69v5jPyzYjwpPQ1A+L5Y6ctiO09fiWbNi0kkQ/R4ZsI/I5dhXT TezBW9odyEKw8iW08x2CrN8iaj0zCcgvZbf0hE9xnu6kXq+3NsZCSH5TOmx+Nd8mOGKN km/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=rCZ6k35/nBqMpxgmeuVdv6KMBQ4oHVGssWX2JK+/T80=; b=hch8K8llDjzA5XehGRWGsBg7iKxV4V1UQQcRRfycAeNWw8H6ZmBPxKikzk6WwjWbbg 5d0tOcBcEk/k4u/NhqKWOOGu6IS5Toj/nmK2mmXJ6TypTHhaJrM3Rt/ONSSFEtKaKcQy A6aJowJKm+84VHKy0kGh4SrsWuf+2/Z3zocEOpv3y1v0eJeW1rlRRhlPi9CqxeUMMJxz Pv3pGin7OGUjZSnSnONvEQFobtPkImHI6DclVOC8X0LzxZT5waDZXL5vjwCEjBDSZxdG +eHTSbI5QWNuuo++DjQEPhejM09QnxNAq/a/sEHVS/2VL3Xh/MnCxQ4ptCXxrUKRb4E/ VPTg==
X-Gm-Message-State: AG10YORIDqjbjzszZysYxfnjkvT2xYYdt+Y0Q/gAOLOtzjW+nlU8Hr2cBTh26ZWETmmuxA==
X-Received: by 10.66.222.129 with SMTP id qm1mr30967612pac.10.1454804948585; Sat, 06 Feb 2016 16:29:08 -0800 (PST)
Received: from ?IPv6:2406:e007:74c2:1:28cc:dc4c:9703:6781? ([2406:e007:74c2:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id t29sm33664959pfi.8.2016.02.06.16.29.05 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 06 Feb 2016 16:29:06 -0800 (PST)
Subject: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt
To: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
References: <20160202182036.26498.27650.idtracker@ietfa.amsl.com> <56B10131.7040603@gmail.com> <2DBB9F0D-0965-4562-9D9D-8183A0010071@gmail.com> <20160203223346.GQ27830@mx2.yitter.info> <56B292E2.4060702@dcrocker.net> <20160204013901.GS27830@mx2.yitter.info> <56B2C602.4060708@comcast.net> <20160206002649.GY31001@mx2.yitter.info> <56B61E79.2010909@comcast.net> <56B64445.6070406@gmail.com> <56B65BF4.4070604@comcast.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B68FCF.4000401@gmail.com>
Date: Sun, 07 Feb 2016 13:29:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B65BF4.4070604@comcast.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/gNrTNVmwa5k-1SPIp2-kxufj8AM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 07 Feb 2016 00:29:10 -0000

Sorry to prolong this correspondence but I have a couple of comments below on Mike's
comments.

As background, here is what I consider to be a key extract from RFC 4071:

"3.3.  Relationship of the IAOC to Existing IETF Leadership

   The IAOC is directly accountable to the IETF community for the
   performance of the IASA.  However, the nature of the IAOC's work
   involves treating the IESG and IAB as major internal customers of the
   administrative support services.  The IAOC and the IAD should not
   consider their work successful unless the IESG and IAB are also
   satisfied with the administrative support that the IETF is receiving."

I suspect that this is why giving the IESG and IAB each an ex officio
seat and the power to appoint one member seemed natural in 2004/2005.

On 07/02/2016 09:47, Michael StJohns wrote:
> See below
> 
> On 2/6/2016 2:06 PM, Brian E Carpenter wrote:
>> Mike,
>>
>> The IAB has oversight responsibility for the RFC Editor. The IAOC oversees
>> the IAD, who manages contracts for the community, including the RFC editing
>> contracts. I therefore believe that having a voting IAB member among the voting
>> members of the IAOC is appropriate. Otherwise the IAB doesn't have a clear
>> "chain of command" (or, alternatively, "the buck stops here") linkage to
>> that aspect of the RFC Editor.
>>
>> A similar argument shows why the IAB should be directly linked to the
>> IETF Trust, which holds the rights in RFCs and may come to hold the rights in
>> IANA data.
>>
>> Neither argument shows that the person needs to be the IAB Chair, IMHO.
>>
>> I regard this as quite disjoint from how the ordinary members of the IAOC
>> are appointed. Splitting that job between the IESG, the IAB and the Nomcom
>> was a fairly arbitrary choice, but I think the Nomcom has a big enough
>> job already.
>>
>>      Brian
>>
>>
> 
> Hi Brian -
> 
> IMO, I think you've made a good argument for retaining at least one IAB member on the IAOC, an incomplete argument for why that
> member need not be the IAB chair and a very poor argument as to why the IAB should continue to appoint a second person.
> 
> WRT the incomplete argument I'd ask the current (and past members) of the IAOC to comment on the following questions (to
> paraphrase Leslie's note quite a bit):
> 
>     Are there specific benefits to the IAOC to having the IAB chair continue as a member of the IAOC that would not be met if
> he/she were replaced by another member of the IAB?
>     Are there specific issues the IAOC might encounter if the IAB chair were not a member of the IAOC and how could those issues
> be mitigated?
>     [If you were still on the IAOC,] Would you object to the change and for what reasons?
> 
> So far I *think* I haven't seen anyone currently on the IAOC comment on the above.
> 
> For the poor argument related to why the IAB should continue to appoint a second person - seriously??  "The Nomcom has a big
> enough job already".   I might find this a reasonable argument if (and pretty much only if) the Nomcom weren't already required
> to (advertise for and interview and ) appoint an IAOC member every term.   AFAICT, having the Nomcom change that to two (or even
> three) per year and removing the need for the other two (or three - not quite sure about ISOC) bodies to advertise, interview,
> and select would reduce the workload on the IAB, IESG and maybe ISOC without actually increasing the workload of the Nomcom much
> if at all. [This is based on the observation that the same people will probably apply to the IAB, IESG and Nomcom solicitations
> and if all three bodies are doing their jobs in a complete manner similar to what the Nomcom should be doing, that seems like a
> lot of redundancy in the process.]

That's a valid point. In fact, iirc, it quickly proved necessary to have some
private communication, made tricky by the confidentiality of the Nomcom process,
to avoid oversights in the IAOC selection process. I'm not against opening
up that discussion, but we'd need to hear what several past Nomcom Chairs think
about it. It is of course orthogonal to the draft under discussion.

    Brian