Re: Updating BCP 10 -- NomCom

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 09 January 2015 00:36 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 C5D281A701A for <ietf@ietfa.amsl.com>; Thu, 8 Jan 2015 16:36:04 -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 8_fnVAOduSKq for <ietf@ietfa.amsl.com>; Thu, 8 Jan 2015 16:36:02 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0BC41A6FF9 for <ietf@ietf.org>; Thu, 8 Jan 2015 16:36:02 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id y13so14174804pdi.3 for <ietf@ietf.org>; Thu, 08 Jan 2015 16:36:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=x/7qfOsGAH1e0uk6yTOZoKuKd3LFPUzxp42msIPu4Yk=; b=RlijZYiWekcKUkXGsyoIlBr+YPJjsUi+o59iR4d2jacR4NH3FvkASnIiWRHVll71Md WnwTwSgNHQh5nzppVoxX8gEgXM0ED6nQWmUnV34Ah95SFKlZCuMx89UUIr3urk2nKjMg 0LW4hVmuQyH2xug8VhniI7ijP30JieGP0W0VQmUyGz+fzhVTD0PKyIn6w5USKiwbYeWp QnAQt1Svewvut6xnrEwMIx6bMGaq1J1WdFe3sf0gO+pH35IQz8A5G4USgcH6ZRekGROa LwUxkhTa0YKnKoXW009QqRzoB0VACLHFYvyrVVjkf4Tf2rEqf/wJH2WKpE4+phB8jAmK Dosg==
X-Received: by 10.70.44.66 with SMTP id c2mr19199373pdm.51.1420763761947; Thu, 08 Jan 2015 16:36:01 -0800 (PST)
Received: from ?IPv6:2406:e007:4640:1:28cc:dc4c:9703:6781? ([2406:e007:4640:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id i9sm5447089pdj.27.2015.01.08.16.35.58 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jan 2015 16:36:00 -0800 (PST)
Message-ID: <54AF2288.7030200@gmail.com>
Date: Fri, 09 Jan 2015 13:36:24 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>, Russ Housley <housley@vigilsec.com>
Subject: Re: Updating BCP 10 -- NomCom
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <D54C3DE17A3E5C7B032F6FB4@JcK-HP8200.jck.com> <BC1A05C1-6198-4325-8F46-8E5AB9D0DFCF@cs.georgetown.edu> <20038FAABC32083290783A97@JcK-HP8200.jck.com> <F3782236-1AF7-4F9C-8A15-2F9CC8BC8795@cs.georgetown.edu> <54AED784.2070402@gmail.com> <246EBEB9-EA10-4E55-BD94-0161BBEF92E7@vigilsec.com> <7414012C-01C2-4139-98DB-16C6FB52F9DF@gmail.com>
In-Reply-To: <7414012C-01C2-4139-98DB-16C6FB52F9DF@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_Z7-UnYNr3SeOMijJN8-wGkflGk>
Cc: Klensin John <john-ietf@jck.com>, Eric Burger <eburger@cs.georgetown.edu>, IETF <ietf@ietf.org>
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: <http://www.ietf.org/mail-archive/web/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: Fri, 09 Jan 2015 00:36:04 -0000

On 09/01/2015 11:30, Bob Hinden wrote:
> The IAOC and ISOC Board have given their liaisons similar instructions.  
> 
> Bob
> 
>> On Jan 8, 2015, at 11:34 AM, Russ Housley <housley@vigilsec.com>; wrote:
>>
>> For several years now, the IESG and IAB have given their liaisons careful instructions.  Each year, those instructions are reviewed with feedback from the previous year liaison.  In my opinion, this is the right place for the annual review of the instructions.  However, I do think that there can be a bit more guidance in BCP 10 that applies to all of the liaisons.  I have a few thoughts:
>>
>> 1.  The liaison is expected to act in the best interest of the IETF.
>>
>> 2.  During NomCom calls and meetings, the liaison is expected to represent the views of the leadership body rather than personal opinion.
>>
>> 3.  The liaison may provide personal feedback to NomCom, but they should only do so using communication channels available to all IETF participants.
>>
>> To me, these are consistent with the language that is already present in RFC 3777:
>>
>>     Liaisons are expected to represent the views of their respective
>>     organizations during the deliberations of the committee.  They
>>     should provide information as requested or when they believe it
>>     would be helpful to the committee.
>>
>> Russ

That's all good. However, I think the Nomcom (Chair) needs some guidance,
even if it's a very general statement that the liaisons should have
sufficient access to Nomcom materials and discussions so as to execute
all their duties under http://tools.ietf.org/html/rfc7437#section-4.7 .

After all, the only restriction placed on liaisons is a single line:
"Liaisons do not vote on the selection of candidates."

   Brian