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

Michael StJohns <mstjohns@comcast.net> Sat, 06 February 2016 20:47 UTC

Return-Path: <mstjohns@comcast.net>
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 4866A1B337E for <ietf@ietfa.amsl.com>; Sat, 6 Feb 2016 12:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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, RP_MATCHES_RCVD=-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 WNi8-JCcO91i for <ietf@ietfa.amsl.com>; Sat, 6 Feb 2016 12:47:44 -0800 (PST)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 339FB1B335F for <ietf@ietf.org>; Sat, 6 Feb 2016 12:47:44 -0800 (PST)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-03v.sys.comcast.net with comcast id F8nC1s0032PT3Qt018nj9y; Sat, 06 Feb 2016 20:47:43 +0000
Received: from [IPv6:2601:148:c000:48c8:c8f0:67e5:88b1:2975] ([IPv6:2601:148:c000:48c8:c8f0:67e5:88b1:2975]) by resomta-ch2-14v.sys.comcast.net with comcast id F8ni1s00B4K7ncF018nirW; Sat, 06 Feb 2016 20:47:43 +0000
Subject: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 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>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <56B65BF4.4070604@comcast.net>
Date: Sat, 06 Feb 2016 15:47:48 -0500
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: <56B64445.6070406@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1454791663; bh=8AT2fyHGFymBrdnEzoa79iYUSh0e0hdgoOkadSFmY9Y=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=MkqLzXC+Wek7kCiCCNRj+4GZnsQLXbUwOLGHP9UgAFnLqCfP1vVW7RHmQqx+hDa0W /NkUn2s4GRGM3yUKqAoFSm24L5TaFF0FNeqqe5sfOp1odxqis3mhbRLNYIo8jOHqpG gb9bkYLTe7L67v+zkngSss98Wtfwy25+kaMaPLzfc8k5IErMizoNiUiy/Gs6SRIDDL QUGAQADXcl6UopU58ByzcHTMUpYDST3vSKnADVQDHfxPb6PzzvYBDHLbbavR1CBQrA sQYkAPRPkTsnq2eNLjVYrDmaK6Ty9NiRfep1qm9qDmM4n1nIGqOYAq3QW0COlK+cUA xZnqmWKBiUxkA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/UQsO6LpXGeHL4wTXcd9mxuJQpP0>
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: Sat, 06 Feb 2016 20:47:49 -0000

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.]


Later, Mike