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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 03 February 2016 02:30 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 21D9C1B31E0 for <ietf@ietfa.amsl.com>; Tue, 2 Feb 2016 18:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.3
X-Spam-Level:
X-Spam-Status: No, score=0.3 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, MANGLED_SEX=2.3, SPF_PASS=-0.001] autolearn=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 lAVr2eE5fqw1 for <ietf@ietfa.amsl.com>; Tue, 2 Feb 2016 18:30:31 -0800 (PST)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 E77A61B31DD for <ietf@ietf.org>; Tue, 2 Feb 2016 18:30:30 -0800 (PST)
Received: by mail-pf0-x231.google.com with SMTP id n128so4758849pfn.3 for <ietf@ietf.org>; Tue, 02 Feb 2016 18:30:30 -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=kuaMdqTgqhdJjTaPzdRYAzb4qg3lRSoICIVyv7GfnxU=; b=O/urTk7HZwfEhRQzhDjnPm2wE4fPiT/QApuHepAFSfMoSuj4RUXfLscySvQrQsAUCW a8UOMPhCHHdOmzkplmw6TUfWXUfFQK9fDMCSIaPQ9iNckIjuNoFPf6nO27U6Vnn6pTJ4 KrbJYte0vZFwIgNuuDW6eBmy8YREEZAnKZB4KtjAMKxa0X0IsJ0QvyhQwoD9ixrHcwI5 zaytE/G+XAEB1DhHA+MGGwVV6R4W+DU/7Z/jrECLpN+pl8/m5IU/yHlA7a4sNRr8KiRR 4Q8gaID59vsc3aXayRWoxeTfWrmBfSvIp0gfPu6GUXJpLbSrzBiX/Tbfad41vKW1t5w/ qhAg==
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=kuaMdqTgqhdJjTaPzdRYAzb4qg3lRSoICIVyv7GfnxU=; b=Byf6ryU3J7+iV/yoXkeYBmCzrzRpK5pIyJGmJTd7NXQzvqLmiqiXxZ1M4ALcpkR/22 hsxsTcQIymJCieuCUvX2O19LWAUBjI1zRqBmatqT/ETDkYEqDkA909PHzLWtfYrqPKt7 8etZ+uR+jtSDu6sHcP9OMteez6OlW/udjyV6z3gmcTWJXxzd7yZHM71E/6DqyaWjzooa 7OLE9zafJEB1SI0xNEtHgJvIKECbbyuytNxxYz7dRxYP7wJf85JhxwwojqVd3xwReVWk h4TwV7mZYeJMHMpPyGCDN92KZJucuHjo0H/Q1KsX1jyJGZhe/wFP9ZZ7pkogJh+I4XJG WxHA==
X-Gm-Message-State: AG10YORlH5qwhE21G23p1t4rAhixhT5Muc/7aFxiEddPngMTOmQfrcNAMpsvY0pSDBt/2w==
X-Received: by 10.98.67.149 with SMTP id l21mr52253365pfi.112.1454466630639; Tue, 02 Feb 2016 18:30:30 -0800 (PST)
Received: from ?IPv6:2406:e007:4103:1:28cc:dc4c:9703:6781? ([2406:e007:4103:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id o90sm5574076pfi.17.2016.02.02.18.30.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 02 Feb 2016 18:30:28 -0800 (PST)
Subject: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt
To: Eliot Lear <lear@cisco.com>, IETF discussion list <ietf@ietf.org>
References: <20160202182036.26498.27650.idtracker@ietfa.amsl.com> <56B10131.7040603@gmail.com> <56B10F59.4030606@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B16646.203@gmail.com>
Date: Wed, 03 Feb 2016 15:30:30 +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: <56B10F59.4030606@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/gbL4Hkwrl_VKBC7FNOHSvBh355U>
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: Wed, 03 Feb 2016 02:30:32 -0000

Hi,

I chose to respond to Eliot's message, but I have read all the other comments so far
as well. My thoughts are below.

On 03/02/2016 09:19, Eliot Lear wrote:
> Hi Brian,
> 
> See below.
> 
> On 2/2/16 8:19 PM, Brian E Carpenter wrote:
>> Hi,
>>
>> I think this draft mixes up two things.
>>
>> (1) A proposal that the IAB Chair's ex officio seat in the IAOC be changed
>> to be a seat for an IAB voting member designated by the IAB. That of course
>> can only be achieved by an RFC that formally updates RFC 4071 and so becomes
>> part of BCP 101.
>>
>> (2) A description of some IAB internal organisational matters, which the IAB
>> is clearly free to arrange how it wants, and publish if it wants. IAB
>> internal arrangements don't need to be BCPs.
>>
>> I've got nothing to say about (2).
>>
>> About (1), I think we should hear the pros and cons, because I doubt if
>> this proposal arose in a vacuum. In particular, how would this help the
>> IAOC be more effective and more responsive to community concerns?
>>
> 
> Pro:  it is best to have the possibility of delegating responsibility to
> someone who really can devote all the time necessary to the role.  You
> may recall that the IAB chair's time is in quite high demand.  The IAOC
> is only one of many matters that can come to her or his attention.  I
> view this as a simple matter of scaling.
> 
> Pseudo-Con (really a pro): the IAB chair keeps substantial context in
> his head, and can bring that to bear when dealing with the IAOC. 
> However, it is better to have the chair share that context with other
> board members, and particular any delegate to this role.  For one thing,
> it reduces the impact when the chair departs the board.

I think that for the specific case of the IAB Chair's IAOC seat, changing
it to be any voting member (except the IETF Chair) is fine, and giving the
IAB Chair a non-voting observer status is fine too. In this case, delegation
is good; I can't see a significant downside, even during the IANA transition
and the other big change that's coming, i.e. the new RFC format.

I think the IETF Chair slot is a different matter. Yes, the IETF Chair is
also the IESG Chair, but I don't believe s/he is in the IAOC on behalf of
the IESG. On the contrary, it's on behalf of the IETF. I think it's
exactly right that the IETF Chair votes in the IAOC, because nobody
else has the same overview, and also because I believe that any IETF Chair
who did not closely track the IAOC's business would be irresponsible.

I think the ISOC President slot is also a different matter, and a bit
tricky. I don't think we can declare our "funding agency" to be a non-voting
member. Also, we (the IETF) don't define ISOC's internal structure or its
methods of appointment. So it's hard for us to define who could replace the
ISOC President as a voting IAOC member and Trustee. However, I'm assuming
we wouldn't want it to be a staff appointment.

   Brian