Re: draft-klensin-iaoc-member-01 (was: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt)

Michael StJohns <> Tue, 16 February 2016 02:53 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D00A21B330D for <>; Mon, 15 Feb 2016 18:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.005
X-Spam-Status: No, score=-2.005 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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1SGTXECROIEN for <>; Mon, 15 Feb 2016 18:53:38 -0800 (PST)
Received: from ( [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6A5D41B3347 for <>; Mon, 15 Feb 2016 18:53:36 -0800 (PST)
Received: from ([]) by with comcast id JqsB1s0012LrikM01qtbgl; Tue, 16 Feb 2016 02:53:35 +0000
Received: from [] ([]) by with comcast id Jqta1s00H3Em2Kp01qtbR7; Tue, 16 Feb 2016 02:53:35 +0000
Subject: Re: draft-klensin-iaoc-member-01 (was: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt)
References: <> <>
From: Michael StJohns <>
Message-ID: <>
Date: Mon, 15 Feb 2016 21:53:22 -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: <>
Content-Type: multipart/alternative; boundary="------------050105030009020707030604"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=q20140121; t=1455591215; bh=1Z4Pib93MiN+eCx0MbO5x4gU1ErwdS0lI0LP+Grasn0=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=gsegVW6JNXnRCrWcZtmk+BVB3emQnVakZD+LL9LglsEH7FvwYBn4KiU85TzPd6mGY aiqSeo6DAc+0Q96oCyhiRELYOOHUAnFEQJgr6n8YgIKA/kfNR9sCWpSGuVDnCPFdXL TcIXyCvY1siVHrb6edksMyMds94xZs6hObXr7boOW8DZm9VBiXXnZ3qrKJErdsjVV3 w9hjhiRqK1vH+hc7klNZFHiwZ+MO6V+o5qUnG+YJ9KQnCkW6K0z7OT/6r/SfNQP5wW GoZS1FY8phGiUsabPn74OCQ/4iF1ezKJ05CxYacD2Zj+Uni6APb/v23n+6kFRHYXsK ujsleBcJHorIg==
Archived-At: <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 16 Feb 2016 02:53:42 -0000

On 2/15/2016 7:05 PM, Brian E Carpenter wrote:
> The question is, is the IETF Chair in the IAOC as "IETF Chair",
> "IESG Chair", or both? John's analysis is quite right as far as the
> IESG Chair is concerned. For example, consider the IAOC's job of
> overseeing the IAD's job of ensuring that tools such as the tracker
> are in good shape. IESG input there is essential, but it could be
> conveyed by any Area Director. However, for some other matters,
> especially policy matters handled by the Trust, the IESG has no
> special role - they are community matters, where ultimately it's
> the IETF Chair who calls consensus.
> So I see a case for the IETF Chair being in the IAOC ex officio as
> today, and that is*orthogonal*  to the question of an IESG liaison.

Hi Brian -

I think your analysis is pretty on target.  Given the above and the 
discussion on the IAB chair I would probably do this:

Have the IAOC consist of

o The IETF Chair (ex-officio)
o One member of the IESG selected by and from its membership for a 1 or 
2 year term
o One member of the IAB selected by and from its membership for a 1 or 2 
year term
o One member of the ISOC BOT selected by and from its membership for a 
minimum 2 year term with an option to extend year to year.
o Four members selected by the Nomcom for 2 year terms - confirmed by 
both the IAB and IESG (alternately 3 or 6 members with three year terms)
o The ISOC BOT Chair and the IAB Chair as observers if they aren't 
otherwise appointed.

The term lengths for the IAB and IESG would be variable to allow 
different "entering classes" to serve on the IAOC. A member would 
expected to serve at least two years and would be automatically 
reappointed to the IAOC for an additional year if they are re-upped to 
the IAB or IESG  and have served less than two years.    After that, 
their appointing organization can continue them year to year as long as 
they retain their slot on the IESG or IAB.

The term lengths for the ISOC BOT are to deal with their three year term 
length - the BOT would have to appoint someone that has at least two 
years left on their ISOC BOT term, but could then extend their 
appointment by a year at a time.  That gives the IAOC some stability in 
ISOC participation.

The NOMCOM selected members are currently confirmed by the IESG.  If we 
make the above changes, then we require anyone appointed by the Nomcom 
to be acceptable to both the IAB and IESG, but we take away the IAB and 
IESG's current appointment power for the two other at large members.   
Given that the IAB, IESG, ISOC and Nomcom are all pulling candidates 
from mostly the same pool, it does not make a lot of sense to have 4 
different groups appointing at-large members.

The benefit of staying with the current ex-officio model is to not have 
to figure out how to deal with varying term lengths amongst the 
ex-officio replacements.  But, if you change the model, then you have to 
figure out how to give the IAOC *at least* the same level of stability 
that it currently has in membership terms.