Re: Updating BCP 10 -- NomCom

Russ Housley <housley@vigilsec.com> Thu, 08 January 2015 19:34 UTC

Return-Path: <housley@vigilsec.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 E366F1A9079 for <ietf@ietfa.amsl.com>; Thu, 8 Jan 2015 11:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 7hERjwRbtKsX for <ietf@ietfa.amsl.com>; Thu, 8 Jan 2015 11:34:36 -0800 (PST)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0B11A9069 for <ietf@ietf.org>; Thu, 8 Jan 2015 11:34:36 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id B59D89A400B; Thu, 8 Jan 2015 14:34:25 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id YHzG47H710PW; Thu, 8 Jan 2015 14:34:25 -0500 (EST)
Received: from [192.168.2.101] (pool-173-79-205-14.washdc.fios.verizon.net [173.79.205.14]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 19A0D9A401D; Thu, 8 Jan 2015 14:34:25 -0500 (EST)
Subject: Re: Updating BCP 10 -- NomCom
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <54AED784.2070402@gmail.com>
Date: Thu, 8 Jan 2015 14:34:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <246EBEB9-EA10-4E55-BD94-0161BBEF92E7@vigilsec.com>
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>
To: Brian Carpenter <brian.e.carpenter@gmail.com>, Klensin John <john-ietf@jck.com>, Eric Burger <eburger@cs.georgetown.edu>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nGycnpEcMLvwi5OKzC5TN0hmF_o>
Cc: 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: Thu, 08 Jan 2015 19:34:38 -0000

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