
From riw@cisco.com  Mon Mar  2 05:42:20 2009
Return-Path: <riw@cisco.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1F3428C0FA for <ietf-nomcom@core3.amsl.com>; Mon,  2 Mar 2009 05:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAmq0D-KJZPG for <ietf-nomcom@core3.amsl.com>; Mon,  2 Mar 2009 05:42:19 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id D2D3C3A6B23 for <ietf-nomcom@ietf.org>; Mon,  2 Mar 2009 05:42:19 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,289,1233532800"; d="scan'208";a="138437940"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-3.cisco.com with ESMTP; 02 Mar 2009 13:42:45 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n22DgjYt018673;  Mon, 2 Mar 2009 08:42:45 -0500
Received: from [127.0.0.1] (rtp-vpn6-1057.cisco.com [10.82.252.37]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n22DgjfK009305; Mon, 2 Mar 2009 13:42:45 GMT
Message-ID: <49ABE24B.8050305@cisco.com>
Date: Mon, 02 Mar 2009 08:42:35 -0500
From: Russ White <riw@cisco.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>
References: <49A8136B.6060404@joelhalpern.com>	<49A300D3.3060501@joelhalpern.com>	<72E1E2EDDBD5CBDD92BF837F@eList-eXpress-LLC.local>	<499F3A1A.7020205@thinkingcat.com>	<51C740C6-2F58-4B5D-BB51-C6C937D5EF35@tcb.net>	<49A2EED1.6000506@thinkingcat.com>	<6509.1235719272@epsilon.noi.kre.to> <8708.1235761553@epsilon.noi.kre.to>
In-Reply-To: <8708.1235761553@epsilon.noi.kre.to>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3275; t=1236001365; x=1236865365; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=riw@cisco.com; z=From:=20Russ=20White=20<riw@cisco.com> |Subject:=20Re=3A=20[ietf-nomcom]=20announcing=20list=20of= 20willing=20candidates |Sender:=20 |To:=20Robert=20Elz=20<kre@munnari.OZ.AU>; bh=hG4XVMQcZYeE116aLWOA9125mvRiHLxjGasHqD48Vs0=; b=QzBDKtoNNsPFzlxkWz2qH+mJrlseJ4BId0dY7gycISZTz3K76ccnnI05/5 ff0AD9uqME0kChxNxxbnPatnguGUZ9gc+Eea/YSWcRU6Ibc1cnw7kvfKRzU6 lbd8qtdp4M;
Authentication-Results: rtp-dkim-2; header.From=riw@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: NomComDiscussion <ietf-nomcom@ietf.org>
Subject: Re: [ietf-nomcom] announcing list of willing candidates
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2009 13:42:21 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Rather than sending a whole bunch of (at least today), supposedly confidential
> to many people, and hoping that some of them do the right thing with it,
> I'd instead send the same list of people the question "would you be prepared
> to provide some confidential information upon a nominee for an IETF
> leadership position, and keep all information supplied confidential?" (in a
> few more words than that probably) - and then wait for the responses.

In which case you would probably receive very little in the way of
feedback, if any at all. There is a reality not addressed here--people
quite often aren't certain of the value of the information they have, or
they have information that is valuable, and aren't asked.

You're assuming here is that either the nomcom will know, with
precision, who to ask for feedback (who has valuable information within
the community). This is a big assumption.

You're also assuming people will honestly report on their own honesty.
It's a bit like asking spammers to set a new "spam" bit in their emails.

> I'd also tend to ask about just one nominee in a message - that is, rather
> than giving a list of nominees and asking "which is best" (or what are the 
> strengths/weaknesses amongst this group), I'd just ask for opinions about a
> single person (nominee), and possibly a blanket final question "and is there
> anyone else you know of who would, or would not be, good for this position?"

This either means each person is going to get a serialized set of
emails, each with one of the candidates in it, or they are only going to
be asked about one or two candidates, which means information they have
about someone they're not asked about won't come out--because they won't
know whether these "other people" are on the list or not.

If this is the reason:

> If there nominee names are never known, that kind of thinking can't
> happen - when asked, the person concerned might even say in their response
> "I can do this if required, but I think Barney Rubble would be a better
> choice" - never knowing if Barney is being considered or not.

It's wrong. Everyone knows at least _one_ candidate for the position,
the person currently holding it. No matter how much you try to keep
confidential, that much is known by everyone. So, we can throw this
reason out with a high degree of confidence, because a large number of
people will not toss their hats in the ring because they are either
happy with the current officeholder, or they don't believe themselves to
be better qualified than that person. Many people will also simply give
you feedback of "I like x, but they won't be any better than the person
currently serving."

The other reason I've heard is to avoid embarrassment. I consider this
reason bogus as well, since we so willingly embarrass people in the
second call for nominees.

Are there any other reasons to keep pretending the list is confidential?

:-)

Russ

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmr4ksACgkQER27sUhU9OSAMACffcwvxEc50okl9NT5wdfcyp+U
GD0AmwQsIEPEcLc2gEEtcoxC8jYr0xUw
=MVi+
-----END PGP SIGNATURE-----

From jwkckid1@ix.netcom.com  Mon Mar  2 11:07:07 2009
Return-Path: <jwkckid1@ix.netcom.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A5333A6A0B for <ietf-nomcom@core3.amsl.com>; Mon,  2 Mar 2009 11:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.077
X-Spam-Level: 
X-Spam-Status: No, score=0.077 tagged_above=-999 required=5 tests=[AWL=1.684,  BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gx+UUpuF05MP for <ietf-nomcom@core3.amsl.com>; Mon,  2 Mar 2009 11:07:00 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id 923A03A6A40 for <ietf-nomcom@ietf.org>; Mon,  2 Mar 2009 11:06:59 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=iFtc8O3cVQBBHw/DybEUBgKnJwQl6ll2foKyJtPTic2rRZ/Dj9JLJeKIz83Xd47H; h=Received:Message-ID:Date:From:Organization:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [4.227.98.153] (helo=ix.netcom.com) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jwkckid1@ix.netcom.com>) id 1LeDTx-00088H-NE; Mon, 02 Mar 2009 14:07:19 -0500
Message-ID: <49AAF644.46E4EC22@ix.netcom.com>
Date: Sun, 01 Mar 2009 12:55:33 -0800
From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
Organization: IDNS and Spokesman for INEGroup
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Russ White <riw@cisco.com>
References: <49A8136B.6060404@joelhalpern.com>	<49A300D3.3060501@joelhalpern.com>	<72E1E2EDDBD5CBDD92BF837F@eList-eXpress-LLC.local>	<499F3A1A.7020205@thinkingcat.com>	<51C740C6-2F58-4B5D-BB51-C6C937D5EF35@tcb.net>	<49A2EED1.6000506@thinkingcat.com>	<6509.1235719272@epsilon.noi.kre.to> <8708.1235761553@epsilon.noi.kre.to> <49ABE24B.8050305@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: c8e3929e1e9c87a874cfc7ce3b1ad11381c87f5e51960688587d286afb9fb3e8ba8565545e0ace66350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.227.98.153
Cc: NomComDiscussion <ietf-nomcom@ietf.org>, Robert Elz <kre@munnari.OZ.AU>
Subject: Re: [ietf-nomcom] announcing list of willing candidates
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2009 19:07:07 -0000

Russ and all,

  Wow good response here Russ!  More specific comments below
interspersed.

Russ White wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> > Rather than sending a whole bunch of (at least today), supposedly confidential
> > to many people, and hoping that some of them do the right thing with it,
> > I'd instead send the same list of people the question "would you be prepared
> > to provide some confidential information upon a nominee for an IETF
> > leadership position, and keep all information supplied confidential?" (in a
> > few more words than that probably) - and then wait for the responses.
>
> In which case you would probably receive very little in the way of
> feedback, if any at all. There is a reality not addressed here--people
> quite often aren't certain of the value of the information they have, or
> they have information that is valuable, and aren't asked.

  How very true, and obviously a problem that can be a circular one
without a resolution that everyone or some would be comfortable with.

>
>
> You're assuming here is that either the nomcom will know, with
> precision, who to ask for feedback (who has valuable information within
> the community). This is a big assumption.

  A huge assumption!

>
>
> You're also assuming people will honestly report on their own honesty.
> It's a bit like asking spammers to set a new "spam" bit in their emails.

  ROFLMAO!  How true!

>
>
> > I'd also tend to ask about just one nominee in a message - that is, rather
> > than giving a list of nominees and asking "which is best" (or what are the
> > strengths/weaknesses amongst this group), I'd just ask for opinions about a
> > single person (nominee), and possibly a blanket final question "and is there
> > anyone else you know of who would, or would not be, good for this position?"
>
> This either means each person is going to get a serialized set of
> emails, each with one of the candidates in it, or they are only going to
> be asked about one or two candidates, which means information they have
> about someone they're not asked about won't come out--because they won't
> know whether these "other people" are on the list or not.

  Yes.  OR, there is always the situation where some information someone
has on someone else is false, or not entirely accurate.

>
>
> If this is the reason:
>
> > If there nominee names are never known, that kind of thinking can't
> > happen - when asked, the person concerned might even say in their response
> > "I can do this if required, but I think Barney Rubble would be a better
> > choice" - never knowing if Barney is being considered or not.
>
> It's wrong. Everyone knows at least _one_ candidate for the position,
> the person currently holding it. No matter how much you try to keep
> confidential, that much is known by everyone. So, we can throw this
> reason out with a high degree of confidence, because a large number of
> people will not toss their hats in the ring because they are either
> happy with the current officeholder, or they don't believe themselves to
> be better qualified than that person. Many people will also simply give
> you feedback of "I like x, but they won't be any better than the person
> currently serving."

  Good point.

>
>
> The other reason I've heard is to avoid embarrassment. I consider this
> reason bogus as well, since we so willingly embarrass people in the
> second call for nominees.

  Also a very valid point.

>
>
> Are there any other reasons to keep pretending the list is confidential?
>
> :-)
>
> Russ
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmr4ksACgkQER27sUhU9OSAMACffcwvxEc50okl9NT5wdfcyp+U
> GD0AmwQsIEPEcLc2gEEtcoxC8jYr0xUw
> =MVi+
> -----END PGP SIGNATURE-----
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom

Regards,

Spokesman for INEGroup LLA. - (Over 284k members/stakeholders strong!)
"Obedience of the law is the greatest freedom" -
   Abraham Lincoln
"YES WE CAN!"  Barack ( Berry ) Obama

"Credit should go with the performance of duty and not with what is
very often the accident of glory" - Theodore Roosevelt

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of Information Network Eng.  INEG. INC.
ABA member in good standing member ID 01257402 E-Mail
jwkckid1@ix.netcom.com
My Phone: 214-244-4827


From spencer@wonderhamster.org  Tue Mar  3 14:19:31 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CC833A68DC for <ietf-nomcom@core3.amsl.com>; Tue,  3 Mar 2009 14:19:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level: 
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_05=-1.11, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyE4inY2s6FI for <ietf-nomcom@core3.amsl.com>; Tue,  3 Mar 2009 14:19:30 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id D853F3A6A96 for <ietf-nomcom@ietf.org>; Tue,  3 Mar 2009 14:19:29 -0800 (PST)
Received: from S73602b (cpe-72-190-78-151.tx.res.rr.com [72.190.78.151]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1Lecxv0AHl-000TXR; Tue, 03 Mar 2009 17:19:56 -0500
Message-ID: <D9279493ABBF4F499F7FE7122EE1E364@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: <ietf-nomcom@ietf.org>
References: <20090220174517.76C3913B906E@newdev.eecs.harvard.edu>
Date: Tue, 3 Mar 2009 16:19:33 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/cmNTUcnH71aXR9eu2RjvJSiFOa8MAmrB4OOH YgskrhMwUlFMiX6Yo2+1HtAvioszHnMwpfk0m1+L2NJs15nrSs medVzSJMt5+1e5ofRKt0QpUyn721AfmkuPmBAEoaaE=
Subject: Re: [ietf-nomcom] past nomcom chair starting next process
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 22:19:31 -0000

Just to let people know - Russ thought this was a good suggested change, so 
I've submitted an 01 version of the draft (at 
http://www.ietf.org/internet-drafts/draft-dawkins-nomcom-dont-wait-01.txt) 
that now assigns the responsibility to the IETF Secretariat.

Thanks for your feedback,

Spencer

> seems to me that a simpler solution is for the IETF Secretariat
> to post that information (what seats are to be decided) whenever
> it would be a good idea to do so - this is known information
>
> one special case is where the IESG decides to add or subtract
> a area - biut the Secretariat can find that out from the IESG
> just as well as the nomcom chair can
>
> Scott 



From galvin@elistx.com  Wed Mar  4 10:01:51 2009
Return-Path: <galvin@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49A173A6BA7 for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 10:01:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8nFlfZXu2ud for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 10:01:50 -0800 (PST)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id 698853A6CB0 for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 10:01:50 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KFZ00A6PU3B9V@elistx.com> for ietf-nomcom@ietf.org; Wed, 04 Mar 2009 13:02:01 -0500 (EST)
Date: Wed, 04 Mar 2009 12:03:18 -0600
From: James M Galvin <galvin@elistx.com>
To: ietf-nomcom@ietf.org
Message-id: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Subject: [ietf-nomcom] a proposed revision to RFC3777 has been posted
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 18:01:51 -0000

At Russ' request I have posted a revision to RFC3777 with "one change". 
The change was have the document also include the IAOC.

As you know, RFC4071 already states RFC3777 is to be used.  In that 
context, we're hopeful this change is non-controversial and thus I 
provided a draft revised document.

However, in the process of making the edits I realized there were three 
things that might be considered "interesting" as opposed to "editorial" 
and so I wanted to call them to your attention.

I should state first that my model when I started the edits is that the 
IAOC should be "equal" to the IESG and IAB in this document.  This 
meant that it was my intention to simply add "IAOC" everywhere that 
"IAB and IESG" appeared.

Here are my comments.

1. RFC4071 states that RFC3777 is to be used to select and confirm two 
members of the IAOC.  This is different than how the IAB and IESG are 
treated since in those cases all members are subject to the selection 
and confirmation process.  In addition, RFC4071 states that all members 
of the IAOC are subject to the recall process in RFC3777.  So, please 
pay attention to this distinction as you review and make sure I covered 
all this correctly.

2. The IESG and the IAB are "required" to provide a liaison to the 
NOMCOM in RFC3777.  In contrast, the ISOC Board of Trustees has the 
option of doing so.  In keeping with the model of the IAOC being 
"equal" to the IESG and IAB, I stated that the IAOC is also required to 
provide a liaison.  This point needs to be brought to the attention of 
the IAOC since they may have an opinion.

3. I shortened the title dramatically to "Operation of the Nominating 
and Recall Committees."

As always, any comments or suggestions are always welcome.

Jim


From galvin@elistx.com  Wed Mar  4 10:04:16 2009
Return-Path: <galvin@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4998928C436 for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 10:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kFF1chtQddc for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 10:04:15 -0800 (PST)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id 2B47028C0E0 for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 10:02:47 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KFZ00A77U4X9V@elistx.com> for ietf-nomcom@ietf.org; Wed, 04 Mar 2009 13:02:58 -0500 (EST)
Date: Wed, 04 Mar 2009 12:04:16 -0600
From: James M Galvin <galvin@elistx.com>
To: ietf-nomcom@ietf.org
Message-id: <521D64E2491B56B31E9E196D@201-131-220-159.icannmeeting.org>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: multipart/mixed; boundary="==========0D5E98B02E46B686BAB0=========="
Subject: [ietf-nomcom] I-D Action:draft-galvin-rfc3777bis-00.txt (fwd)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 18:04:16 -0000

--==========0D5E98B02E46B686BAB0==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



-------- Forwarded Message --------
Date: March 4, 2009 9:45:01 AM -0800
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-galvin-rfc3777bis-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Operation of the Nominating and Recall Committees
	Author(s)       : J. Galvin
	Filename        : draft-galvin-rfc3777bis-00.txt
	Pages           : 41
	Date            : 2009-03-04

<1>
The IETF uses two committees to manage the selection, confirmation,
and recall of some or all of the individuals who serve terms of
membership on the bodies that support its operation.  As of the
publication of this document the list of bodies includes the IESG,
IAB, and the IAOC.  This document is a self-consistent, organized
compilation of the process as it was known at the time of
publication.Discussion of this Draft

<2>
Please direct all comments, suggestions, and questions regarding this
draft to the following mailing list:
<3>

ietf-nomcom@ietf.org

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-galvin-rfc3777bis-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

-------- End Forwarded Message --------


--==========0D5E98B02E46B686BAB0==========
Content-Type: message/rfc822;
 name="I-D Action:draft-galvin-rfc3777bis-00.txt"

Return-path: <i-d-announce-bounces@ietf.org>
Received: from CONVERSION-DAEMON.elistx.com by elistx.com
 (PMDF V6.3-2x2 #31546) id <0KFZ00A01TDWJ6@elistx.com> for
 galvin@msgstore.elistx.com (ORCPT galvin+2Bi-d-announce@elistx.com); Wed,
 04 Mar 2009 12:46:50 -0500 (EST)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
 by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KFZ00A17TDW9V@elistx.com>
 for galvin@msgstore.elistx.com (ORCPT galvin+2Bi-d-announce@elistx.com); Wed,
 04 Mar 2009 12:46:44 -0500 (EST)
Received: from [127.0.0.1] (localhost [127.0.0.1])	by core3.amsl.com (Postfix)
 with ESMTP id 45F9D28C3F0; Wed, 04 Mar 2009 09:45:04 -0800 (PST)
Received: by core3.amsl.com (Postfix, from userid 0)	id 838FF3A6ABF; Wed,
 04 Mar 2009 09:45:01 -0800 (PST)
Date: Wed, 04 Mar 2009 09:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
Subject: I-D Action:draft-galvin-rfc3777bis-00.txt
Sender: i-d-announce-bounces@ietf.org
To: i-d-announce@ietf.org
Errors-to: i-d-announce-bounces@ietf.org
Reply-to: internet-drafts@ietf.org
Message-id: <20090304174501.838FF3A6ABF@core3.amsl.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_Bw2HsEQPPP5m1eGpZXWYLw)"
Precedence: list
Delivered-to: i-d-announce@core3.amsl.com
X-Original-To: i-d-announce@ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
List-Post: <mailto:i-d-announce@ietf.org>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>


--Boundary_(ID_Bw2HsEQPPP5m1eGpZXWYLw)
Content-type: TEXT/PLAIN

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Operation of the Nominating and Recall Committees
	Author(s)       : J. Galvin
	Filename        : draft-galvin-rfc3777bis-00.txt
	Pages           : 41
	Date            : 2009-03-04

<1>
The IETF uses two committees to manage the selection, confirmation,
and recall of some or all of the individuals who serve terms of
membership on the bodies that support its operation.  As of the
publication of this document the list of bodies includes the IESG,
IAB, and the IAOC.  This document is a self-consistent, organized
compilation of the process as it was known at the time of
publication.Discussion of this Draft

<2>
Please direct all comments, suggestions, and questions regarding this
draft to the following mailing list:
<3>

ietf-nomcom@ietf.org

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-galvin-rfc3777bis-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_Bw2HsEQPPP5m1eGpZXWYLw)
Content-type: Message/External-body; name=draft-galvin-rfc3777bis-00.txt;
 site=ftp.ietf.org; access-type=anon-ftp; directory=internet-drafts

Content-Type: text/plain
Content-ID: <2009-03-04094448.I-D@ietf.org>


--Boundary_(ID_Bw2HsEQPPP5m1eGpZXWYLw)
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--Boundary_(ID_Bw2HsEQPPP5m1eGpZXWYLw)--

--==========0D5E98B02E46B686BAB0==========--


From housley@vigilsec.com  Wed Mar  4 12:04:39 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFED43A684E for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:04:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQNwcNwJf50v for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:04:39 -0800 (PST)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 1938728C49D for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 12:04:30 -0800 (PST)
Received: (qmail 28274 invoked by uid 0); 4 Mar 2009 20:04:52 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.144.212) by woodstock.binhost.com with SMTP; 4 Mar 2009 20:04:52 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 04 Mar 2009 15:04:56 -0500
To: ietf-nomcom@ietf.org
From: Russ Housley <housley@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20090304200430.1938728C49D@core3.amsl.com>
Subject: [ietf-nomcom] IETF 74 Wednesday Plenary Discussion
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 20:04:39 -0000

I am dedicating 55 minutes of the Wednesday plenary meeting at IETF 
74 to discussion of NomCom process change.  Here is the agenda:

    NomCom Process Change (1600 to 1655)

    1. Introduction
    2. Presentation of each draft followed by Q&A
        - draft-galvin-rfc3777bis
        - draft-dawkins-nomcom-dont-wait
        - draft-dawkins-nomcom-openlist
    3. Way forward

Russ


From spencer@wonderhamster.org  Wed Mar  4 12:04:40 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D62D3A6D1D for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:04:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.453
X-Spam-Level: 
X-Spam-Status: No, score=-1.453 tagged_above=-999 required=5 tests=[AWL=-0.713, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLy3gZ2ymj-k for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:04:39 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 8CBA528C49E for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 12:04:30 -0800 (PST)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1LexKq26cX-000TiY; Wed, 04 Mar 2009 15:04:59 -0500
Message-ID: <A8E2418472044A25AF0775D7D64AF35D@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "James M Galvin" <galvin@elistx.com>, <ietf-nomcom@ietf.org>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>
Date: Wed, 4 Mar 2009 14:04:31 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/NbG3xc3FqbMVdrHTbYZhZU4ekuewnGKT2cjF WCTOq5i5zQpTdRhDJlG4ht2oNEGuRmzHIfxJkjgPNkSqNlGmf7 8qfjPzfYseenZ1m/LOwWl6Qk3Mqyfn3zWO18PzFSxA=
Subject: Re: [ietf-nomcom] a proposed revision to RFC3777 has been posted
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 20:04:40 -0000

Hi, Jim,

Nice work, for the 00 cutoff :-)

This revision looks pretty much like I would have expected an IAOC revision 
to look (please take that as praise). There were a few things I wondered 
about, as I was comparing against RFC 3777...

I may not understand the way things work, but in the Abstract,

<1>
   The IETF uses two committees to manage the selection, confirmation,
   and recall of some or all of the individuals who serve terms of
   membership on the bodies that support its operation.  As of the
   publication of this document the list of bodies includes the IESG,
   IAB, and the IAOC.  This document is a self-consistent, organized
   compilation of the process as it was known at the time of
   publication.

I'm not sure which two committees you're referring to. Perhaps naming them 
would be clearer?

In the following text,

        If a voting volunteer member is recalled, regardless of the
        circumstances, the committee may choose to proceed with only 9
        voting volunteers at its own discretion.  In all other cases the
        Chair must repeat the random selection process including an
        announcement of the iteration prior to the actual selection as
        stated elsewhere in this document.

3777 talked about a voting volunteer position being VACATED, regardless of 
the circumstances. Was there a reason to force the NomCom Chair to fill 
positions vacated by resignations? I guess I'm wondering if we've ever 
executed this code - I don't remember seeing a NomCom Chair announce that a 
voting member was being added, regardless of the cause, and a quick scan of 
http://www.ietf.org/NomCom.html didn't show anyone as being replaced, 
although your memory is likely better than my archive scan...

In the following text,

<113>
   1.  At any time, at least 20 members of the IETF community, who are
       qualified to be voting members of a nominating committee, may
       request by signed petition (email is acceptable) to the Internet
       Society President the recall of any sitting of a body with
       members to which this document applies.

"recall of any sitting of a body with members to which this document 
applies" doesn't parse for me. The 3777 text was "recall any sitting IAB or 
IESG member", so I'm assuming you meant something like "the recall of any 
sitting member of a body to which this document applies", but I'm just not 
sure.

You might want to (add a reminder to) remove the timeline section in a later 
revision of this draft - it's been obsoleted by RFC 5078.

Nits:

s/committe /committee /
s/are expect to/are expected to/
s/it is also helps/it also helps/ 



From galvin@elistx.com  Wed Mar  4 12:35:35 2009
Return-Path: <galvin@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB06928C180 for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SpfFpZZhVnEg for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:35:34 -0800 (PST)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id 3CB0328C170 for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 12:35:34 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KG000O8H17JTP@elistx.com> for ietf-nomcom@ietf.org; Wed, 04 Mar 2009 15:35:44 -0500 (EST)
Date: Wed, 04 Mar 2009 14:37:04 -0600
From: James M Galvin <galvin@elistx.com>
In-reply-to: <A8E2418472044A25AF0775D7D64AF35D@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>, ietf-nomcom@ietf.org
Message-id: <118C5FD269DC52016D24F436@201-131-220-159.icannmeeting.org>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <A8E2418472044A25AF0775D7D64AF35D@china.huawei.com>
Subject: Re: [ietf-nomcom] a proposed revision to RFC3777 has been posted
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 20:35:36 -0000

-- On March 4, 2009 2:04:31 PM -0600 Spencer Dawkins 
<spencer@wonderhamster.org> wrote regarding Re: [ietf-nomcom] a 
proposed revision to RFC3777 has been posted --

> <1>
>    The IETF uses two committees to manage the selection, confirmation,
>    and recall of some or all of the individuals who serve terms of
>    membership on the bodies that support its operation.  As of the
>    publication of this document the list of bodies includes the IESG,
>    IAB, and the IAOC.  This document is a self-consistent, organized
>    compilation of the process as it was known at the time of
>    publication.
>
> I'm not sure which two committees you're referring to. Perhaps naming
> them would be clearer?

It should be the "Nominating Committee" and the "Recall Committee". 
How about we replace the "." at the end of the first sentence with:

    : Nominating Committee and Recall Committee



> In the following text,
>
>         If a voting volunteer member is recalled, regardless of the
>         circumstances, the committee may choose to proceed with only 9
>         voting volunteers at its own discretion.  In all other cases
> the
>         Chair must repeat the random selection process including an
>         announcement of the iteration prior to the actual selection as
>         stated elsewhere in this document.
>
> 3777 talked about a voting volunteer position being VACATED,
> regardless of the circumstances. Was there a reason to force the
> NomCom Chair to fill positions vacated by resignations? I guess I'm
> wondering if we've ever executed this code - I don't remember seeing
> a NomCom Chair announce that a voting member was being added,
> regardless of the cause, and a quick scan of
> http://www.ietf.org/NomCom.html didn't show anyone as being replaced,
> although your memory is likely better than my archive scan...

Wow.  Good catch!  I'm going to have to go back and diff rfc3777 
against the XML source I've got.

Honestly, I have no immediate answer for this.  I did not change this 
text this time.  I started with the XML I had that was labeled as the 
XML I used to create RFC3777.  I did not confirm this because it was 
the only XML I had.

Apparently there were some edits way back when that did not make it in 
to the final document.  My bad, very bad, obviously.

I'm going to create and review a diff against RFC3777 and see what's up.



> In the following text,
>
> <113>
>    1.  At any time, at least 20 members of the IETF community, who are
>        qualified to be voting members of a nominating committee, may
>        request by signed petition (email is acceptable) to the
> Internet
>        Society President the recall of any sitting of a body with
>        members to which this document applies.
>
> "recall of any sitting of a body with members to which this document
> applies" doesn't parse for me. The 3777 text was "recall any sitting
> IAB or IESG member", so I'm assuming you meant something like "the
> recall of any sitting member of a body to which this document
> applies", but I'm just not sure.

What I had left out was "member" next to "sitting member".  Your text 
is simpler and I will go with it.  I missed this spot when I was trying 
to clean up the 'extra' text I had added during my first edits.  The 
problem was I was over thinking the distinction between only 2 members 
get selected and confirmed in the IAOC and all members can be recalled.



> You might want to (add a reminder to) remove the timeline section in
> a later revision of this draft - it's been obsoleted by RFC 5078.

Another good catch.


Thanks!

Jim


From spencer@wonderhamster.org  Wed Mar  4 12:44:52 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C17FD3A693B for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.28
X-Spam-Level: 
X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=0.319,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRJI4UYEsGiU for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 12:44:51 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 657663A6889 for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 12:44:51 -0800 (PST)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1Lexxt1xk5-000bB1; Wed, 04 Mar 2009 15:45:20 -0500
Message-ID: <F902B240A32641C5B1C94493175CB8A1@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "James M Galvin" <galvin@elistx.com>, <ietf-nomcom@ietf.org>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <A8E2418472044A25AF0775D7D64AF35D@china.huawei.com> <118C5FD269DC52016D24F436@201-131-220-159.icannmeeting.org>
Date: Wed, 4 Mar 2009 14:44:52 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/bbS1gQFcQH7AHJWcauolnFBi3GH+ibOQ2HO3 AlgvgZIGW8wFXu2FTof7qM7au1AtaBR3SMHp3wRiQJJtglbfHY wVO4GZMdAoc6Sq4BiyuOF9ouMBSxDBYTbctw4FmLbY=
Subject: Re: [ietf-nomcom] a proposed revision to RFC3777 has been posted
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 20:44:52 -0000

Hi, Jim,

"works for me..." - and thanks for the quick turnaround. It's always nice 
when I can remember what I was thinking!

Spencer

----- Original Message ----- 
From: "James M Galvin" <galvin@elistx.com>
To: "Spencer Dawkins" <spencer@wonderhamster.org>; <ietf-nomcom@ietf.org>
Sent: Wednesday, March 04, 2009 2:37 PM
Subject: Re: [ietf-nomcom] a proposed revision to RFC3777 has been posted


>
>
> -- On March 4, 2009 2:04:31 PM -0600 Spencer Dawkins 
> <spencer@wonderhamster.org> wrote regarding Re: [ietf-nomcom] a proposed 
> revision to RFC3777 has been posted --
>
>> <1>
>>    The IETF uses two committees to manage the selection, confirmation,
>>    and recall of some or all of the individuals who serve terms of
>>    membership on the bodies that support its operation.  As of the
>>    publication of this document the list of bodies includes the IESG,
>>    IAB, and the IAOC.  This document is a self-consistent, organized
>>    compilation of the process as it was known at the time of
>>    publication.
>>
>> I'm not sure which two committees you're referring to. Perhaps naming
>> them would be clearer?
>
> It should be the "Nominating Committee" and the "Recall Committee". How 
> about we replace the "." at the end of the first sentence with:
>
>    : Nominating Committee and Recall Committee
>
>
>
>> In the following text,
>>
>>         If a voting volunteer member is recalled, regardless of the
>>         circumstances, the committee may choose to proceed with only 9
>>         voting volunteers at its own discretion.  In all other cases
>> the
>>         Chair must repeat the random selection process including an
>>         announcement of the iteration prior to the actual selection as
>>         stated elsewhere in this document.
>>
>> 3777 talked about a voting volunteer position being VACATED,
>> regardless of the circumstances. Was there a reason to force the
>> NomCom Chair to fill positions vacated by resignations? I guess I'm
>> wondering if we've ever executed this code - I don't remember seeing
>> a NomCom Chair announce that a voting member was being added,
>> regardless of the cause, and a quick scan of
>> http://www.ietf.org/NomCom.html didn't show anyone as being replaced,
>> although your memory is likely better than my archive scan...
>
> Wow.  Good catch!  I'm going to have to go back and diff rfc3777 against 
> the XML source I've got.
>
> Honestly, I have no immediate answer for this.  I did not change this text 
> this time.  I started with the XML I had that was labeled as the XML I 
> used to create RFC3777.  I did not confirm this because it was the only 
> XML I had.
>
> Apparently there were some edits way back when that did not make it in to 
> the final document.  My bad, very bad, obviously.
>
> I'm going to create and review a diff against RFC3777 and see what's up.
>
>
>
>> In the following text,
>>
>> <113>
>>    1.  At any time, at least 20 members of the IETF community, who are
>>        qualified to be voting members of a nominating committee, may
>>        request by signed petition (email is acceptable) to the
>> Internet
>>        Society President the recall of any sitting of a body with
>>        members to which this document applies.
>>
>> "recall of any sitting of a body with members to which this document
>> applies" doesn't parse for me. The 3777 text was "recall any sitting
>> IAB or IESG member", so I'm assuming you meant something like "the
>> recall of any sitting member of a body to which this document
>> applies", but I'm just not sure.
>
> What I had left out was "member" next to "sitting member".  Your text is 
> simpler and I will go with it.  I missed this spot when I was trying to 
> clean up the 'extra' text I had added during my first edits.  The problem 
> was I was over thinking the distinction between only 2 members get 
> selected and confirmed in the IAOC and all members can be recalled.
>
>
>
>> You might want to (add a reminder to) remove the timeline section in
>> a later revision of this draft - it's been obsoleted by RFC 5078.
>
> Another good catch.
>
>
> Thanks!
>
> Jim
>
> 



From housley@vigilsec.com  Wed Mar  4 14:36:39 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47D8C3A6CC1 for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 14:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.494
X-Spam-Level: 
X-Spam-Status: No, score=-102.494 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXF+ZL7A6Lnk for <ietf-nomcom@core3.amsl.com>; Wed,  4 Mar 2009 14:36:38 -0800 (PST)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 686A43A6CA9 for <ietf-nomcom@ietf.org>; Wed,  4 Mar 2009 14:36:38 -0800 (PST)
Received: (qmail 20286 invoked by uid 0); 4 Mar 2009 22:36:59 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.144.212) by woodstock.binhost.com with SMTP; 4 Mar 2009 22:36:59 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 04 Mar 2009 17:37:04 -0500
To: James M Galvin <galvin@elistx.com>,
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20090304223638.686A43A6CA9@core3.amsl.com>
Cc: iaoc@ietf.org, ietf-nomcom@ietf.org
Subject: [ietf-nomcom] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 22:36:39 -0000

Jim:

In the past two years, the IAOC has not provided a liaison to 
NomCom.  Based on this precedent, I think the liaison from the IAOC 
should be optional.

Russ

At 01:03 PM 3/4/2009, James M Galvin wrote:
>2. The IESG and the IAB are "required" to provide a liaison to the 
>NOMCOM in RFC3777.  In contrast, the ISOC Board of Trustees has the 
>option of doing so.  In keeping with the model of the IAOC being 
>"equal" to the IESG and IAB, I stated that the IAOC is also required 
>to provide a liaison.  This point needs to be brought to the 
>attention of the IAOC since they may have an opinion.


From galvin@elistx.com  Wed Mar  4 15:23:24 2009
Return-Path: <galvin@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DD9228C39E; Wed,  4 Mar 2009 15:23:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id li-yVPYpNIja; Wed,  4 Mar 2009 15:23:23 -0800 (PST)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id 4682528C3B7; Wed,  4 Mar 2009 15:23:23 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KG000D748Z8XW@elistx.com>; Wed, 04 Mar 2009 18:23:33 -0500 (EST)
Date: Wed, 04 Mar 2009 17:24:53 -0600
From: James M Galvin <galvin@elistx.com>
In-reply-to: <20090304223638.686A43A6CA9@core3.amsl.com>
To: Russ Housley <housley@vigilsec.com>
Message-id: <728D349C317A08AE31C2BBE1@201-131-212-237.icannmeeting.org>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304223638.686A43A6CA9@core3.amsl.com>
Cc: iaoc@ietf.org, ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 23:23:24 -0000

Sure, I could see that.  I wish I had left myself enough time to ask 
the IAOC in advance as to what they would prefer but I didn't do that. 
So, let me do it now.

Would the IAOC want to be required to have a liaison on the NOMCOM, 
similar to the IESG and IAB, or would it prefer to have it be optional, 
similar to the ISOC Board of Trustees?

Jim





-- On March 4, 2009 5:37:04 PM -0500 Russ Housley 
<housley@vigilsec.com> wrote regarding [ietf-nomcom] RFC 3777bis: 
Liaison from IAOC to NomCom --

> Jim:
>
> In the past two years, the IAOC has not provided a liaison to NomCom.
> Based on this precedent, I think the liaison from the IAOC should be
> optional.
>
> Russ
>
> At 01:03 PM 3/4/2009, James M Galvin wrote:
> > 2. The IESG and the IAB are "required" to provide a liaison to the
> > NOMCOM in RFC3777.  In contrast, the ISOC Board of Trustees has the
> > option of doing so.  In keeping with the model of the IAOC being
> > "equal" to the IESG and IAB, I stated that the IAOC is also
> > required  to provide a liaison.  This point needs to be brought to
> > the  attention of the IAOC since they may have an opinion.
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom



From Bob.Hinden@nokia.com  Wed Mar  4 18:40:08 2009
Return-Path: <Bob.Hinden@nokia.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EF4928C20B; Wed,  4 Mar 2009 18:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rx97ST12w3QQ; Wed,  4 Mar 2009 18:40:07 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 36E2B28C201; Wed,  4 Mar 2009 18:40:07 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n252d2WW011756; Wed, 4 Mar 2009 20:40:32 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 5 Mar 2009 04:40:16 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 5 Mar 2009 04:40:16 +0200
Received: from da-niradhcp16039.americas.nokia.com (da-niradhcp16039.americas.nokia.com [10.241.160.39]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id n252drZk009544; Thu, 5 Mar 2009 04:39:55 +0200
From: Bob Hinden <bob.hinden@nokia.com>
To: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20090304224318.974633A6824@core3.amsl.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com>
Message-Id: <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 4 Mar 2009 18:39:53 -0800
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Mar 2009 02:40:16.0500 (UTC) FILETIME=[B78EF340:01C99D3B]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Thu, 05 Mar 2009 08:05:45 -0800
Cc: iaoc@ietf.org, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2009 02:40:08 -0000

Russ,

While don't have a strong opinion here, this might be a good topic for  
the IAOC to discuss.  Overall I think the nomcom has done a fine job  
selecting IAOC members, but I think it is worth some IAOC discussion.

Bob


On Mar 4, 2009, at 2:37 PM, ext Russ Housley wrote:

> Jim:
>
> In the past two years, the IAOC has not provided a liaison to  
> NomCom.  Based on this precedent, I think the liaison from the IAOC  
> should be optional.
>
> Russ
>
> At 01:03 PM 3/4/2009, James M Galvin wrote:
>> 2. The IESG and the IAB are "required" to provide a liaison to the  
>> NOMCOM in RFC3777.  In contrast, the ISOC Board of Trustees has the  
>> option of doing so.  In keeping with the model of the IAOC being  
>> "equal" to the IESG and IAB, I stated that the IAOC is also  
>> required to provide a liaison.  This point needs to be brought to  
>> the attention of the IAOC since they may have an opinion.
>
> _______________________________________________
> IAOC mailing list
> IAOC@ietf.org
> https://www.ietf.org/mailman/listinfo/iaoc


From fred@cisco.com  Thu Mar  5 08:17:52 2009
Return-Path: <fred@cisco.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FC8C3A6A17; Thu,  5 Mar 2009 08:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.458
X-Spam-Level: 
X-Spam-Status: No, score=-106.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G35ezXkD68Kn; Thu,  5 Mar 2009 08:17:51 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 7FB7D3A6A13; Thu,  5 Mar 2009 08:17:51 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,307,1233532800"; d="scan'208";a="261938485"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 05 Mar 2009 16:18:21 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n25GIL15010728;  Thu, 5 Mar 2009 08:18:21 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n25GIL1b007467; Thu, 5 Mar 2009 16:18:21 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 5 Mar 2009 08:18:21 -0800
Received: from [172.17.187.241] ([10.21.124.175]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 5 Mar 2009 08:18:20 -0800
Message-Id: <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>
From: Fred Baker <fred@cisco.com>
To: IAOC Jabberr <iaoc@ietf.org>
In-Reply-To: <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 5 Mar 2009 08:18:19 -0800
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 05 Mar 2009 16:18:20.0687 (UTC) FILETIME=[000381F0:01C99DAE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1824; t=1236269901; x=1237133901; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[IAOC]=20RFC=203777bis=3A=20Liaison=20f rom=20IAOC=20to=20NomCom |Sender:=20; bh=FNSAskdVdTiRxk9L3Ji5KkVcCQ7UDAD4xlR7YwAKqFA=; b=X0izY6sFWsBTW3hGr6yTDn8qyethrJcRe7PcZOKvULdY/H3Q+lCaGDDaDq BMHXio8R3Py8b8W3jXtR50zxUU+OJR8tHkpUXACHyXAyVnYp37GLKIOlRzt5 xmr8kPav7/;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2009 16:17:52 -0000

On Mar 4, 2009, at 6:39 PM, Bob Hinden wrote:

> While don't have a strong opinion here, this might be a good topic  
> for the IAOC to discuss.  Overall I think the nomcom has done a fine  
> job selecting IAOC members, but I think it is worth some IAOC  
> discussion.

I guess my question is what the purpose of the liaison is.

In the IAB and IESG case, they have roles that much of the community  
(and therefore the nomcom in many cases) finds murky, and often have  
knowledge or insight from handling "special" issues that the community  
is not aware of. Since the nomcom is selecting their future  
membership, they want to be available for the nomcom to ask questions  
of. That is not the case with the ISOC Board, as the nomcom doesn't  
select membership there.

In all three cases, they are confirming bodies and often have  
questions for the nomcom, and their bodies will want to ask  
appropriate questions about the nomcom process such as "in your  
opinion did the nomcom come to its conclusions fairly and with  
appropriate reflection?".

So those are the primary roles of the liaisons: confidential  
communication between the nomcom and other bodies.

The IAOC is not a confirming body, but it does have insight that the  
rest of the community doesn't have as much visibility into relating to  
contracts and finances, and the nomcom does select a member for it.

One consideration: adding a person to the nomcom means one more  
person's time, and one more person in every meeting. One person  
doesn't break any banks, but there is an impact there.

That being the case, and given that the nomcom is capable of asking  
questions directly of the IAOC regarding its role, I think I would put  
it in the "optional" category. Willing to be argued out of that.

From jonne.soininen@nsn.com  Fri Mar  6 08:01:10 2009
Return-Path: <jonne.soininen@nsn.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 838B928C2C5; Fri,  6 Mar 2009 08:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level: 
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=-0.856, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMSPEzgxiW-g; Fri,  6 Mar 2009 08:01:09 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id 641783A6D0B; Fri,  6 Mar 2009 08:01:09 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n26G1OkL020613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 6 Mar 2009 17:01:24 +0100
Received: from 201-131-222-217.icannmeeting.org ([10.162.76.7]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n26G1FfA019054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Mar 2009 17:01:22 +0100
Message-ID: <49B148CA.3050700@nsn.com>
Date: Fri, 06 Mar 2009 18:01:14 +0200
From: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: ext Fred Baker <fred@cisco.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>
In-Reply-To: <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 16:01:10 -0000

Hi,

I think this should be a little bit discussed, and I'm going to say my 
opinion now.

I think the level should be _at least_ "optional". Of course, it should 
be the IAOC to decide if they appoint a liaison or not.

I'm thinking what could be won of having a mandatory liaison, but I 
cannot think of anything.

Cheers,

Jonne.
ext Fred Baker wrote:
>
> On Mar 4, 2009, at 6:39 PM, Bob Hinden wrote:
>
>> While don't have a strong opinion here, this might be a good topic 
>> for the IAOC to discuss.  Overall I think the nomcom has done a fine 
>> job selecting IAOC members, but I think it is worth some IAOC 
>> discussion.
>
> I guess my question is what the purpose of the liaison is.
>
> In the IAB and IESG case, they have roles that much of the community 
> (and therefore the nomcom in many cases) finds murky, and often have 
> knowledge or insight from handling "special" issues that the community 
> is not aware of. Since the nomcom is selecting their future 
> membership, they want to be available for the nomcom to ask questions 
> of. That is not the case with the ISOC Board, as the nomcom doesn't 
> select membership there.
>
> In all three cases, they are confirming bodies and often have 
> questions for the nomcom, and their bodies will want to ask 
> appropriate questions about the nomcom process such as "in your 
> opinion did the nomcom come to its conclusions fairly and with 
> appropriate reflection?".
>
> So those are the primary roles of the liaisons: confidential 
> communication between the nomcom and other bodies.
>
> The IAOC is not a confirming body, but it does have insight that the 
> rest of the community doesn't have as much visibility into relating to 
> contracts and finances, and the nomcom does select a member for it.
>
> One consideration: adding a person to the nomcom means one more 
> person's time, and one more person in every meeting. One person 
> doesn't break any banks, but there is an impact there.
>
> That being the case, and given that the nomcom is capable of asking 
> questions directly of the IAOC regarding its role, I think I would put 
> it in the "optional" category. Willing to be argued out of that.
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom


From fred@cisco.com  Fri Mar  6 08:12:25 2009
Return-Path: <fred@cisco.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CCA23A6981; Fri,  6 Mar 2009 08:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.466
X-Spam-Level: 
X-Spam-Status: No, score=-106.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EqSsM8+SWmI1; Fri,  6 Mar 2009 08:12:24 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id AE85B3A68B8; Fri,  6 Mar 2009 08:12:24 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,315,1233532800"; d="scan'208";a="140140429"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 06 Mar 2009 16:12:55 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n26GCt2Z016662;  Fri, 6 Mar 2009 08:12:55 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n26GCtpW021894; Fri, 6 Mar 2009 16:12:55 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Mar 2009 08:12:55 -0800
Received: from [172.17.187.241] ([10.21.77.254]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Mar 2009 08:12:54 -0800
Message-Id: <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
In-Reply-To: <49B148CA.3050700@nsn.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 6 Mar 2009 08:12:54 -0800
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 06 Mar 2009 16:12:54.0944 (UTC) FILETIME=[6844D200:01C99E76]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=856; t=1236355975; x=1237219975; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[ietf-nomcom]=20[IAOC]=20RFC=203777bis= 3A=20Liaison=20from=20IAOC=20to=20NomCom |Sender:=20; bh=QRIvrI8GkBXHajImW8GyxOJr+yRTM96T/CjwTo+EZFE=; b=CmwyJilX/Xl2p8dDZhgidefnfJ9FjOOoANLTqs/zKA2L2mvNa9XEzj+d6Q hGbEPbKtb/aMYZwHO9+CKwpwGVul0I3va9B5mftVPv6r9dwrofTKltHzpkrS cQiL60EXf7Ppaj0r5PpwPcBdCdXQ68Hi097twEVCWcrGuMx8C2yeQ=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 16:12:25 -0000

On Mar 6, 2009, at 8:01 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:

> I think the level should be _at least_ "optional". Of course, it  
> should be the IAOC to decide if they appoint a liaison or not.

Yes.

One thing to consider is whether, having appointed a liaison at all,  
the liaison needs to attend all meetings of the nomcom. If the IAOC  
was a confirming body, we would want the liaison there for all  
meetings so we could ask questions about the process followed - "do  
you believe that it was fair and equitable, or do you believe that  
there was a hatchet mob?" We're not a confirming body, so I think the  
purpose is more of the benefit of the nomcom. One could imagine them  
saying they wanted a liaison present for a stated set of meetings. The  
same rules would apply in terms of confidentiality etc, of course.

From jmh@joelhalpern.com  Fri Mar  6 08:19:33 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4B783A68B8; Fri,  6 Mar 2009 08:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zgow036MLKWi; Fri,  6 Mar 2009 08:19:33 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id F24403A6784; Fri,  6 Mar 2009 08:19:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id E008C43032D; Fri,  6 Mar 2009 08:20:03 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-50-192.clppva.btas.verizon.net [71.161.50.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id A0DFB43031A; Fri,  6 Mar 2009 08:20:02 -0800 (PST)
Message-ID: <49B14D2E.5050709@joelhalpern.com>
Date: Fri, 06 Mar 2009 11:19:58 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com>
In-Reply-To: <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>, IAOC Jabberr <iaoc@ietf.org>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 16:19:33 -0000

Note that one of the subtleties under here is that the usual 
interpretation of the RFC is that for committee votes other than on 
nominee / candidate issues, the liaisons get to vote.  More liaisons, at 
least in principle, means more non-volunteer voters on things like 
procedures for the committee.

Conversely, having a person there to ask "is X important to the IAOC?", 
or "does issue Y really come up?" seems quite valuable.

Yours,
Joel



Fred Baker wrote:
> 
> On Mar 6, 2009, at 8:01 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:
> 
>> I think the level should be _at least_ "optional". Of course, it 
>> should be the IAOC to decide if they appoint a liaison or not.
> 
> Yes.
> 
> One thing to consider is whether, having appointed a liaison at all, the 
> liaison needs to attend all meetings of the nomcom. If the IAOC was a 
> confirming body, we would want the liaison there for all meetings so we 
> could ask questions about the process followed - "do you believe that it 
> was fair and equitable, or do you believe that there was a hatchet mob?" 
> We're not a confirming body, so I think the purpose is more of the 
> benefit of the nomcom. One could imagine them saying they wanted a 
> liaison present for a stated set of meetings. The same rules would apply 
> in terms of confidentiality etc, of course.
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
> 

From jonne.soininen@nsn.com  Fri Mar  6 09:24:04 2009
Return-Path: <jonne.soininen@nsn.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E28A3A6CBE; Fri,  6 Mar 2009 09:24:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.419
X-Spam-Level: 
X-Spam-Status: No, score=-3.419 tagged_above=-999 required=5 tests=[AWL=-0.820, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRupwenI9KN8; Fri,  6 Mar 2009 09:24:03 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id 795C83A6C2A; Fri,  6 Mar 2009 09:24:02 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n26HONKV012862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 6 Mar 2009 18:24:23 +0100
Received: from 201-131-222-217.icannmeeting.org ([10.162.76.7]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n26HOHm7018265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Mar 2009 18:24:21 +0100
Message-ID: <49B15C41.7040507@nsn.com>
Date: Fri, 06 Mar 2009 19:24:17 +0200
From: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: "ext Joel M. Halpern" <jmh@joelhalpern.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com>
In-Reply-To: <49B14D2E.5050709@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 17:24:04 -0000

Joel,

I don't quite understand. What do you mean the liaisons get to vote?

Cheers,

Jonne.
ext Joel M. Halpern wrote:
> Note that one of the subtleties under here is that the usual 
> interpretation of the RFC is that for committee votes other than on 
> nominee / candidate issues, the liaisons get to vote.  More liaisons, 
> at least in principle, means more non-volunteer voters on things like 
> procedures for the committee.
>
> Conversely, having a person there to ask "is X important to the 
> IAOC?", or "does issue Y really come up?" seems quite valuable.
>
> Yours,
> Joel
>
>
>
> Fred Baker wrote:
>>
>> On Mar 6, 2009, at 8:01 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:
>>
>>> I think the level should be _at least_ "optional". Of course, it 
>>> should be the IAOC to decide if they appoint a liaison or not.
>>
>> Yes.
>>
>> One thing to consider is whether, having appointed a liaison at all, 
>> the liaison needs to attend all meetings of the nomcom. If the IAOC 
>> was a confirming body, we would want the liaison there for all 
>> meetings so we could ask questions about the process followed - "do 
>> you believe that it was fair and equitable, or do you believe that 
>> there was a hatchet mob?" We're not a confirming body, so I think the 
>> purpose is more of the benefit of the nomcom. One could imagine them 
>> saying they wanted a liaison present for a stated set of meetings. 
>> The same rules would apply in terms of confidentiality etc, of course.
>> _______________________________________________
>> ietf-nomcom mailing list
>> ietf-nomcom@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>


From jmh@joelhalpern.com  Fri Mar  6 09:32:11 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 852C63A6D27; Fri,  6 Mar 2009 09:32:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.501
X-Spam-Level: 
X-Spam-Status: No, score=-3.501 tagged_above=-999 required=5 tests=[AWL=0.098,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-5ljUFKzqlf; Fri,  6 Mar 2009 09:32:10 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id AABBF3A690E; Fri,  6 Mar 2009 09:32:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id ADA9243033D; Fri,  6 Mar 2009 09:32:41 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-50-192.clppva.btas.verizon.net [71.161.50.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 8003243033E; Fri,  6 Mar 2009 09:32:40 -0800 (PST)
Message-ID: <49B15E34.3000202@joelhalpern.com>
Date: Fri, 06 Mar 2009 12:32:36 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com>
In-Reply-To: <49B15C41.7040507@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 17:32:11 -0000

Exactly what I said.
The nomcom chair defines the basic procedures that the nomcom shall use.
Typically there are a variety of things which are subject to the review 
of the committee.  Such as the dates and times for conference calls, 
etc.  (The exact scope of this varies from committee to committee,)  The 
usual reading of the rules is that liaisons do not vote on nominee 
selection.   But they do vote on all other matters.  (How much this 
matters in practice is hard to tell, and probably varies depending upon 
the committee chair and membership.)

Yours,
Joel

Soininen, Jonne (NSN - FI/Espoo) wrote:
> Joel,
> 
> I don't quite understand. What do you mean the liaisons get to vote?
> 
> Cheers,
> 
> Jonne.
> ext Joel M. Halpern wrote:
>> Note that one of the subtleties under here is that the usual 
>> interpretation of the RFC is that for committee votes other than on 
>> nominee / candidate issues, the liaisons get to vote.  More liaisons, 
>> at least in principle, means more non-volunteer voters on things like 
>> procedures for the committee.
>>
>> Conversely, having a person there to ask "is X important to the 
>> IAOC?", or "does issue Y really come up?" seems quite valuable.
>>
>> Yours,
>> Joel
>>
>>
>>
>> Fred Baker wrote:
>>>
>>> On Mar 6, 2009, at 8:01 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:
>>>
>>>> I think the level should be _at least_ "optional". Of course, it 
>>>> should be the IAOC to decide if they appoint a liaison or not.
>>>
>>> Yes.
>>>
>>> One thing to consider is whether, having appointed a liaison at all, 
>>> the liaison needs to attend all meetings of the nomcom. If the IAOC 
>>> was a confirming body, we would want the liaison there for all 
>>> meetings so we could ask questions about the process followed - "do 
>>> you believe that it was fair and equitable, or do you believe that 
>>> there was a hatchet mob?" We're not a confirming body, so I think the 
>>> purpose is more of the benefit of the nomcom. One could imagine them 
>>> saying they wanted a liaison present for a stated set of meetings. 
>>> The same rules would apply in terms of confidentiality etc, of course.
>>> _______________________________________________
>>> ietf-nomcom mailing list
>>> ietf-nomcom@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>>
> 
> 

From jonne.soininen@nsn.com  Fri Mar  6 10:39:30 2009
Return-Path: <jonne.soininen@nsn.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 295763A6841; Fri,  6 Mar 2009 10:39:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.386
X-Spam-Level: 
X-Spam-Status: No, score=-5.386 tagged_above=-999 required=5 tests=[AWL=1.213,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6xmGfbv-+Iw; Fri,  6 Mar 2009 10:39:29 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [217.115.75.233]) by core3.amsl.com (Postfix) with ESMTP id EAD163A6816; Fri,  6 Mar 2009 10:39:28 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n26IdnQa020419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 6 Mar 2009 19:39:49 +0100
Received: from 201-131-222-217.icannmeeting.org ([10.162.76.7]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n26Idfjw009992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Mar 2009 19:39:47 +0100
Message-ID: <49B16DEC.7000504@nsn.com>
Date: Fri, 06 Mar 2009 20:39:40 +0200
From: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: "ext Joel M. Halpern" <jmh@joelhalpern.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com>
In-Reply-To: <49B15E34.3000202@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 18:39:30 -0000

Joel.
ext Joel M. Halpern wrote:
> Exactly what I said.

I am sorry. I just wasn't able to parse exactly what you meant in your 
last mail. Thus, the further question. I think it is my limited English 
that required the rephrasing to be able to understand the topic.

> The nomcom chair defines the basic procedures that the nomcom shall use.
> Typically there are a variety of things which are subject to the 
> review of the committee.  Such as the dates and times for conference 
> calls, etc.  (The exact scope of this varies from committee to 
> committee,)  The usual reading of the rules is that liaisons do not 
> vote on nominee selection.   But they do vote on all other matters.  
> (How much this matters in practice is hard to tell, and probably 
> varies depending upon the committee chair and membership.)

I have to admit I have yet to serve in a NomCom. I didn't know what 
else, except for the nominee selection, would the nomcom vote on. 
Perhaps, you could give an example of votes where the liaisons would 
vote on.

Cheers,

Jonne.

>
> Yours,
> Joel
>
> Soininen, Jonne (NSN - FI/Espoo) wrote:
>> Joel,
>>
>> I don't quite understand. What do you mean the liaisons get to vote?
>>
>> Cheers,
>>
>> Jonne.
>> ext Joel M. Halpern wrote:
>>> Note that one of the subtleties under here is that the usual 
>>> interpretation of the RFC is that for committee votes other than on 
>>> nominee / candidate issues, the liaisons get to vote.  More 
>>> liaisons, at least in principle, means more non-volunteer voters on 
>>> things like procedures for the committee.
>>>
>>> Conversely, having a person there to ask "is X important to the 
>>> IAOC?", or "does issue Y really come up?" seems quite valuable.
>>>
>>> Yours,
>>> Joel
>>>
>>>
>>>
>>> Fred Baker wrote:
>>>>
>>>> On Mar 6, 2009, at 8:01 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:
>>>>
>>>>> I think the level should be _at least_ "optional". Of course, it 
>>>>> should be the IAOC to decide if they appoint a liaison or not.
>>>>
>>>> Yes.
>>>>
>>>> One thing to consider is whether, having appointed a liaison at 
>>>> all, the liaison needs to attend all meetings of the nomcom. If the 
>>>> IAOC was a confirming body, we would want the liaison there for all 
>>>> meetings so we could ask questions about the process followed - "do 
>>>> you believe that it was fair and equitable, or do you believe that 
>>>> there was a hatchet mob?" We're not a confirming body, so I think 
>>>> the purpose is more of the benefit of the nomcom. One could imagine 
>>>> them saying they wanted a liaison present for a stated set of 
>>>> meetings. The same rules would apply in terms of confidentiality 
>>>> etc, of course.
>>>> _______________________________________________
>>>> ietf-nomcom mailing list
>>>> ietf-nomcom@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>>>
>>
>>


From fred@cisco.com  Fri Mar  6 10:43:36 2009
Return-Path: <fred@cisco.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14AA63A67FC; Fri,  6 Mar 2009 10:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9TgVPdtCYw2L; Fri,  6 Mar 2009 10:43:35 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 2DFE93A6841; Fri,  6 Mar 2009 10:43:35 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,316,1233532800"; d="scan'208";a="140208992"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 06 Mar 2009 18:44:06 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n26Ii6a2031082;  Fri, 6 Mar 2009 10:44:06 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n26Ii4Om003129; Fri, 6 Mar 2009 18:44:06 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Mar 2009 10:44:03 -0800
Received: from dhcp-128-107-165-223.cisco.com ([128.107.165.223]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Mar 2009 10:44:02 -0800
Message-Id: <DB3084A7-D330-4B23-8044-9E54E180227F@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <49B15E34.3000202@joelhalpern.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 6 Mar 2009 10:44:01 -0800
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 06 Mar 2009 18:44:02.0704 (UTC) FILETIME=[85133100:01C99E8B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=288; t=1236365046; x=1237229046; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[ietf-nomcom]=20[IAOC]=20RFC=203777bis= 3A=20Liaison=20from=20IAOC=20to=20NomCom |Sender:=20; bh=kA9bxG6SChFqGvk7UlQn0Um1SbEEHMsVz3yq8+kSZVM=; b=DW55Ch0DTFXsR99PhNaw8dt7LSQmT3yGMXKDW38WGRlNZBIIVUbDGK5l5U ZbzI8oZIgbhJSpinv/QtT551FeYNQR3vHKMyJWkNf4yd+eM5+6wl+A9t7XU7 1FEu4caCPPU3EBvQDRYZoEFybjRPMu06p7dEJaDjP1u+enj9oVPbQ=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>, IAOC Jabberr <iaoc@ietf.org>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 18:43:36 -0000

On Mar 6, 2009, at 9:32 AM, Joel M. Halpern wrote:

> The usual reading of the rules is that liaisons do not vote on  
> nominee selection. But they do vote on all other matters.

I have chaired a nomcom and served as liaison to several. This is  
consistent with my experience.

From jmh@joelhalpern.com  Fri Mar  6 10:47:52 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5AFE3A6A07; Fri,  6 Mar 2009 10:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.503
X-Spam-Level: 
X-Spam-Status: No, score=-3.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbqcaYo76j+2; Fri,  6 Mar 2009 10:47:51 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id EF2803A691F; Fri,  6 Mar 2009 10:47:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 093434303AD; Fri,  6 Mar 2009 10:48:23 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-50-192.clppva.btas.verizon.net [71.161.50.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id B456343035E; Fri,  6 Mar 2009 10:48:21 -0800 (PST)
Message-ID: <49B16FF1.9010301@joelhalpern.com>
Date: Fri, 06 Mar 2009 13:48:17 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com>
In-Reply-To: <49B16DEC.7000504@nsn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 18:47:52 -0000

Sorry Jonne.  I was not criticisng the quesiton (but reading your answer 
I see why it could be seen that way.)
I was trying to say "As unlikely as it sounds, the liaisons need to vote.)

As an example, since the liaisons are required to participate, they need 
a say in the selection of meeting times and conference call times.
There are chairs who have said that the liaisons have a vote in what 
voting procedure will be used for selecting candidates, even though they 
are not permitted to be a voter in the result.

Other things come up.
It should be remembered that what makes the nomcom "interesting", for 
the fictional-Chinese meaning of that word, are the unexpected things.

Yours,
Joel

Soininen, Jonne (NSN - FI/Espoo) wrote:
> Joel.
> ext Joel M. Halpern wrote:
>> Exactly what I said.
> 
> I am sorry. I just wasn't able to parse exactly what you meant in your 
> last mail. Thus, the further question. I think it is my limited English 
> that required the rephrasing to be able to understand the topic.
> 
>> The nomcom chair defines the basic procedures that the nomcom shall use.
>> Typically there are a variety of things which are subject to the 
>> review of the committee.  Such as the dates and times for conference 
>> calls, etc.  (The exact scope of this varies from committee to 
>> committee,)  The usual reading of the rules is that liaisons do not 
>> vote on nominee selection.   But they do vote on all other matters.  
>> (How much this matters in practice is hard to tell, and probably 
>> varies depending upon the committee chair and membership.)
> 
> I have to admit I have yet to serve in a NomCom. I didn't know what 
> else, except for the nominee selection, would the nomcom vote on. 
> Perhaps, you could give an example of votes where the liaisons would 
> vote on.
> 
> Cheers,
> 
> Jonne.
> 
>>
>> Yours,
>> Joel
>>
>> Soininen, Jonne (NSN - FI/Espoo) wrote:
>>> Joel,
>>>
>>> I don't quite understand. What do you mean the liaisons get to vote?
>>>
>>> Cheers,
>>>
>>> Jonne.
>>> ext Joel M. Halpern wrote:
>>>> Note that one of the subtleties under here is that the usual 
>>>> interpretation of the RFC is that for committee votes other than on 
>>>> nominee / candidate issues, the liaisons get to vote.  More 
>>>> liaisons, at least in principle, means more non-volunteer voters on 
>>>> things like procedures for the committee.
>>>>
>>>> Conversely, having a person there to ask "is X important to the 
>>>> IAOC?", or "does issue Y really come up?" seems quite valuable.
>>>>
>>>> Yours,
>>>> Joel
>>>>
>>>>
>>>>
>>>> Fred Baker wrote:
>>>>>
>>>>> On Mar 6, 2009, at 8:01 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:
>>>>>
>>>>>> I think the level should be _at least_ "optional". Of course, it 
>>>>>> should be the IAOC to decide if they appoint a liaison or not.
>>>>>
>>>>> Yes.
>>>>>
>>>>> One thing to consider is whether, having appointed a liaison at 
>>>>> all, the liaison needs to attend all meetings of the nomcom. If the 
>>>>> IAOC was a confirming body, we would want the liaison there for all 
>>>>> meetings so we could ask questions about the process followed - "do 
>>>>> you believe that it was fair and equitable, or do you believe that 
>>>>> there was a hatchet mob?" We're not a confirming body, so I think 
>>>>> the purpose is more of the benefit of the nomcom. One could imagine 
>>>>> them saying they wanted a liaison present for a stated set of 
>>>>> meetings. The same rules would apply in terms of confidentiality 
>>>>> etc, of course.
>>>>> _______________________________________________
>>>>> ietf-nomcom mailing list
>>>>> ietf-nomcom@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>>>>
>>>
>>>
> 
> 

From fred@cisco.com  Fri Mar  6 10:55:57 2009
Return-Path: <fred@cisco.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BF8D3A6AD1; Fri,  6 Mar 2009 10:55:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id js-EZbGvQHMv; Fri,  6 Mar 2009 10:55:56 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 5CE223A691F; Fri,  6 Mar 2009 10:55:56 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,316,1233532800"; d="scan'208";a="138712316"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 06 Mar 2009 18:56:27 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n26IuRB0005255;  Fri, 6 Mar 2009 10:56:27 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id n26IuRiK002041; Fri, 6 Mar 2009 18:56:27 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Mar 2009 10:56:27 -0800
Received: from dhcp-128-107-165-223.cisco.com ([128.107.165.223]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 6 Mar 2009 10:56:26 -0800
Message-Id: <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
In-Reply-To: <49B16DEC.7000504@nsn.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 6 Mar 2009 10:56:25 -0800
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 06 Mar 2009 18:56:26.0563 (UTC) FILETIME=[40731130:01C99E8D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1891; t=1236365787; x=1237229787; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[ietf-nomcom]=20[IAOC]=20RFC=203777bis= 3A=20Liaison=20from=20IAOC=20to=20NomCom |Sender:=20; bh=gSzmPVdIKsTppwDgbBY1mHjMBsR4MWavadQg8UMh92Q=; b=XEy6auFQoIjt6N0D3Zly7eIVq3bPUbLoowKPsXw8mds4qauyZ7Ur7XPziz Te/MpEUNpPb2VztgEQw9YMaQaFo2zLW5Qu+RSZ5KmDwKtkvzFNTpDYy0GovP cdWAcmMjIi;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 18:55:57 -0000

On Mar 6, 2009, at 10:39 AM, Soininen, Jonne (NSN - FI/Espoo) wrote:
> I am sorry. I just wasn't able to parse exactly what you meant in  
> your last mail. Thus, the further question. I think it is my limited  
> English that required the rephrasing to be able to understand the  
> topic.
>
>> The nomcom chair defines the basic procedures that the nomcom shall  
>> use.
>> Typically there are a variety of things which are subject to the  
>> review of the committee.  Such as the dates and times for  
>> conference calls, etc.  (The exact scope of this varies from  
>> committee to committee,)  The usual reading of the rules is that  
>> liaisons do not vote on nominee selection.   But they do vote on  
>> all other matters.  (How much this matters in practice is hard to  
>> tell, and probably varies depending upon the committee chair and  
>> membership.)
>
> I have to admit I have yet to serve in a NomCom. I didn't know what  
> else, except for the nominee selection, would the nomcom vote on.  
> Perhaps, you could give an example of votes where the liaisons would  
> vote on.

The nomcom has to decide on a number of things besides the nominees,  
mostly related to process. How often, in what way, and at what time  
does it meet, specifically what questions should it ask people, should  
it have an extra meeting next Tuesday at 3:00 AM Canary Islands time,  
and so on. Since the liaisons have a role in the process and have to  
attend the meetings, their voices count on that topic. On the other  
hand, their input to discussions on nominees is limited (they may know  
a candidate and be able to point out issues that the nomcom should  
investigate, for example, but such comments get treated much as if  
they were comments posted by IETF participants to the nomcom input  
queue), and no vote on the candidates themselves.

From bernie@ietf.hoeneisen.ch  Sat Mar  7 01:50:22 2009
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BCC53A6883 for <ietf-nomcom@core3.amsl.com>; Sat,  7 Mar 2009 01:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id klMFbqpbDz4b for <ietf-nomcom@core3.amsl.com>; Sat,  7 Mar 2009 01:50:21 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id 17DDB3A6855 for <ietf-nomcom@ietf.org>; Sat,  7 Mar 2009 01:50:20 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1LftBC-00005S-3U for ietf-nomcom@ietf.org; Sat, 07 Mar 2009 10:50:50 +0100
Date: Sat, 7 Mar 2009 10:50:50 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: ietf-nomcom@ietf.org
In-Reply-To: <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com>
Message-ID: <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com> <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Subject: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: Liaison from IAOC to NomCom)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Mar 2009 09:50:22 -0000

Hi,

In past years there were many complaints about liasions taking too much 
influence on the NomCom decisions making process. Influencing the NomCom 
in its descision making process is certainly not the task of a liaison. 
Misusing the position as a liaison is more than disruptive.

However, liaisons have information that is most helpful to the NomCom in 
finding its decisions. Often only liaisons know what is really going on as 
they have the inside view ordinary members of the NomCom normally don't 
have.

Without breaking confidentiality rules, I can say that I particularly 
enjoied how this issue has been handled in the current NomCom. All 
liasions were a great help to the NomCom. Liaisons have not even tried to 
influence the NomCom decision making process by means not appropriate to 
their position. Liasions have used the feedback tool to provide the NomCom 
with personal contributions as everbody else. Joel and the liaisons have 
done a great job that served the NomCom (and the community) most. Thank 
you all!

I suggest to reflect the way this issue has been handled in the current 
NomCom to RFC3777bis to clear out the role of a liaison to any future 
NomCom. Actually, most of it is stated already in RFC3777, but due to the 
fact it was leading to unfortunate situations in the past, it might be 
worth looking at it.

cheers,
  Bernie


On Fri, 6 Mar 2009, Fred Baker wrote:

> The nomcom has to decide on a number of things besides the nominees, mostly 
> related to process. How often, in what way, and at what time does it meet, 
> specifically what questions should it ask people, should it have an extra 
> meeting next Tuesday at 3:00 AM Canary Islands time, and so on. Since the 
> liaisons have a role in the process and have to attend the meetings, their 
> voices count on that topic. On the other hand, their input to discussions on 
> nominees is limited (they may know a candidate and be able to point out 
> issues that the nomcom should investigate, for example, but such comments get 
> treated much as if they were comments posted by IETF participants to the 
> nomcom input queue), and no vote on the candidates themselves.

From bernie@ietf.hoeneisen.ch  Sat Mar  7 02:16:54 2009
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC6433A6A9C; Sat,  7 Mar 2009 02:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GIuft5knImPp; Sat,  7 Mar 2009 02:16:54 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id F06973A6A34; Sat,  7 Mar 2009 02:16:53 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1Lftar-000080-SQ; Sat, 07 Mar 2009 11:17:21 +0100
Date: Sat, 7 Mar 2009 11:17:21 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
In-Reply-To: <49B148CA.3050700@nsn.com>
Message-ID: <alpine.DEB.2.00.0903071113440.32572@softronics.hoeneisen.ch>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Cc: IAOC Jabberr <iaoc@ietf.org>, ietf-nomcom@ietf.org, James M Galvin <galvin@elistx.com>
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Mar 2009 10:16:55 -0000

Hi,

IMHO an optional IAOC liaison makes sense. A mandatory IAOC liaison might 
cause difficulties to the IAOC as not so many IAOC members come into 
question for this post.

cheers,
  Bernie

On Fri, 6 Mar 2009, Soininen, Jonne (NSN - FI/Espoo) wrote:

> Hi,
>
> I think this should be a little bit discussed, and I'm going to say my 
> opinion now.
>
> I think the level should be _at least_ "optional". Of course, it should be 
> the IAOC to decide if they appoint a liaison or not.
>
> I'm thinking what could be won of having a mandatory liaison, but I cannot 
> think of anything.
>
> Cheers,
>
> Jonne.
> ext Fred Baker wrote:
>> 
>> On Mar 4, 2009, at 6:39 PM, Bob Hinden wrote:
>> 
>>> While don't have a strong opinion here, this might be a good topic for the 
>>> IAOC to discuss.  Overall I think the nomcom has done a fine job selecting 
>>> IAOC members, but I think it is worth some IAOC discussion.
>> 
>> I guess my question is what the purpose of the liaison is.
>> 
>> In the IAB and IESG case, they have roles that much of the community (and 
>> therefore the nomcom in many cases) finds murky, and often have knowledge 
>> or insight from handling "special" issues that the community is not aware 
>> of. Since the nomcom is selecting their future membership, they want to be 
>> available for the nomcom to ask questions of. That is not the case with the 
>> ISOC Board, as the nomcom doesn't select membership there.
>> 
>> In all three cases, they are confirming bodies and often have questions for 
>> the nomcom, and their bodies will want to ask appropriate questions about 
>> the nomcom process such as "in your opinion did the nomcom come to its 
>> conclusions fairly and with appropriate reflection?".
>> 
>> So those are the primary roles of the liaisons: confidential communication 
>> between the nomcom and other bodies.
>> 
>> The IAOC is not a confirming body, but it does have insight that the rest 
>> of the community doesn't have as much visibility into relating to contracts 
>> and finances, and the nomcom does select a member for it.
>> 
>> One consideration: adding a person to the nomcom means one more person's 
>> time, and one more person in every meeting. One person doesn't break any 
>> banks, but there is an impact there.
>> 
>> That being the case, and given that the nomcom is capable of asking 
>> questions directly of the IAOC regarding its role, I think I would put it 
>> in the "optional" category. Willing to be argued out of that.
>> _______________________________________________
>> ietf-nomcom mailing list
>> ietf-nomcom@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>

From jwkckid1@ix.netcom.com  Sat Mar  7 11:35:19 2009
Return-Path: <jwkckid1@ix.netcom.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33C4C28C1AC for <ietf-nomcom@core3.amsl.com>; Sat,  7 Mar 2009 11:35:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.217
X-Spam-Level: *
X-Spam-Status: No, score=1.217 tagged_above=-999 required=5 tests=[AWL=0.410,  BAYES_40=-0.185, DATE_IN_PAST_12_24=0.992]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLPZYdxjfKOI for <ietf-nomcom@core3.amsl.com>; Sat,  7 Mar 2009 11:35:18 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id 24E733A68EF for <ietf-nomcom@ietf.org>; Sat,  7 Mar 2009 11:35:18 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=HqZN/YtEJhgTTdPwwqj1KLZpIo0MsUS61S+6mRyjBB125O7b9E+Er8L9e2KNKIz0; h=Received:Message-ID:Date:From:Organization:X-Mailer:X-Accept-Language:MIME-Version:To:CC:Subject:References:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [4.227.102.114] (helo=ix.netcom.com) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <jwkckid1@ix.netcom.com>) id 1Lg2JI-0000MP-OL; Sat, 07 Mar 2009 14:35:49 -0500
Message-ID: <49B1947A.43EF7A8B@ix.netcom.com>
Date: Fri, 06 Mar 2009 13:24:10 -0800
From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
Organization: IDNS and Spokesman for INEGroup
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com> <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com> <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: c8e3929e1e9c87a874cfc7ce3b1ad11381c87f5e51960688ab73190c59a936fd958963b37ec77f4e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.227.102.114
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: Liaison fromIAOC to NomCom)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Mar 2009 19:35:19 -0000

Bernie and all,

  I fully agree with your sentiments here.  However this sort
of thing has been going on for years relatively unabated.  I
believe it is in part due to personal preferences taking precedence
by some or a few vs using unbiased judgment.  But of course I
cannot prove that as a fact.  Yet evidently over very recent years,
governments and government entities have seen or accepted my
and others belief and via regulation/policy making begun taking
a much larger and broader role in "Managing" the Internet at
nearly every level.  I view this as a bad and largely unwanted,
or soon to be unwanted thing.  Yet we largely only have ourselves
to blame.  >:(

Bernie Hoeneisen wrote:

> Hi,
>
> In past years there were many complaints about liasions taking too much
> influence on the NomCom decisions making process. Influencing the NomCom
> in its descision making process is certainly not the task of a liaison.
> Misusing the position as a liaison is more than disruptive.
>
> However, liaisons have information that is most helpful to the NomCom in
> finding its decisions. Often only liaisons know what is really going on as
> they have the inside view ordinary members of the NomCom normally don't
> have.
>
> Without breaking confidentiality rules, I can say that I particularly
> enjoied how this issue has been handled in the current NomCom. All
> liasions were a great help to the NomCom. Liaisons have not even tried to
> influence the NomCom decision making process by means not appropriate to
> their position. Liasions have used the feedback tool to provide the NomCom
> with personal contributions as everbody else. Joel and the liaisons have
> done a great job that served the NomCom (and the community) most. Thank
> you all!
>
> I suggest to reflect the way this issue has been handled in the current
> NomCom to RFC3777bis to clear out the role of a liaison to any future
> NomCom. Actually, most of it is stated already in RFC3777, but due to the
> fact it was leading to unfortunate situations in the past, it might be
> worth looking at it.
>
> cheers,
>   Bernie
>
> On Fri, 6 Mar 2009, Fred Baker wrote:
>
> > The nomcom has to decide on a number of things besides the nominees, mostly
> > related to process. How often, in what way, and at what time does it meet,
> > specifically what questions should it ask people, should it have an extra
> > meeting next Tuesday at 3:00 AM Canary Islands time, and so on. Since the
> > liaisons have a role in the process and have to attend the meetings, their
> > voices count on that topic. On the other hand, their input to discussions on
> > nominees is limited (they may know a candidate and be able to point out
> > issues that the nomcom should investigate, for example, but such comments get
> > treated much as if they were comments posted by IETF participants to the
> > nomcom input queue), and no vote on the candidates themselves.
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom

Regards,

Spokesman for INEGroup LLA. - (Over 284k members/stakeholders strong!)
"Obedience of the law is the greatest freedom" -
   Abraham Lincoln
"YES WE CAN!"  Barack ( Berry ) Obama

"Credit should go with the performance of duty and not with what is
very often the accident of glory" - Theodore Roosevelt

"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing  (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of Information Network Eng.  INEG. INC.
ABA member in good standing member ID 01257402 E-Mail
jwkckid1@ix.netcom.com
My Phone: 214-244-4827




From john-ietf@jck.com  Sun Mar  8 08:04:51 2009
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33B273A6C09 for <ietf-nomcom@core3.amsl.com>; Sun,  8 Mar 2009 08:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.646
X-Spam-Level: 
X-Spam-Status: No, score=-2.646 tagged_above=-999 required=5 tests=[AWL=-0.047, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1YhekJqpV9VT for <ietf-nomcom@core3.amsl.com>; Sun,  8 Mar 2009 08:04:49 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id D06BF3A6C15 for <ietf-nomcom@ietf.org>; Sun,  8 Mar 2009 08:04:48 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1LgKZ6-000JcQ-08; Sun, 08 Mar 2009 11:05:20 -0400
Date: Sun, 08 Mar 2009 11:05:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: galvin+ietf@elistx.com
Message-ID: <FB7DC7A43100696E90296D41@PST.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 09 Mar 2009 08:26:07 -0700
Cc: ietf-nomcom@ietf.org
Subject: [ietf-nomcom] draft-galvin-rfc3777bis-00
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Mar 2009 15:04:51 -0000

Jim,

At the time the recall procedures were changed to require many
signatures on petitions, they were also changed to make the
requirement for signatures nomcom-eligibility.  The specific
text, from Section 7, now reads:

>   1.  At any time, at least 20 members of the IETF community,
> who are qualified to be voting members of a nominating
> committee, may request by signed petition (email is
> acceptable) to the Internet Society President the
> recall of any sitting of a body with members to which
> this document applies.
> 
>    All individual and collective qualifications of
> nominating committee eligibility are applicable,
> including that no more than two signatories may have
> the same primary affiliation.
>...

There is actually an ambiguity in this statement, at least in
your current draft.  One way to read the draft is that, because 

> "15.  Members of the Internet Society Board of Trustees,
> sitting members of IAOC, sitting members of the IAB, and
> sitting members of the IESG may not volunteer to serve on the
> nominating committee."

(from Section 4) that they are not "qualified" and hence cannot
participate in recall petitions.   The statement above can also
be read as indicating that those people are "qualified" to
volunteer if they meet all of the other requirements, they are
just prohibited from actually volunteering.  With the second
reading, they could participate.  My understanding is that the
prevailing reading of 3777 has been that they are not permitted
to participate in recall petitions.

That had a side-effect that many of us believe to have been
unintentional, a view that is reinforced by the ambiguity
mentioned above, namely the disqualification of members of the
IAB, IESG, and IAOC from sponsoring recall petitions.  Whether
it was intentional or not, there are at least two significant
reasons why the leadership folks should be able to sign
petitions and even initiate them:

	-- If there is really a serious problem within one of
	those groups, the members of that group, and perhaps
	members of others, are the ones best positioned to
	understand the nature of the problem and, if it is
	actually due to the consistent behavior of an
	individual, to identify that fact and the individual
	involved.  Under the same circumstances, the broader
	community might well see only a "this isn't working at
	all well" situation.
	
	-- The converse of that need for an internal perspective
	is that, if the petitioners cannot get a single member
	of the relevant body to stand up and say, "yes, she is
	the problem and we haven't been able to fix it", that
	may be important information for others considering
	signing the petition and/or for the recall committee.

When this has been discussed before, the argument has been made
that preventing IAB, IESG, or IAOC members from signing recall
petitions prevents vendettas within those bodies from exploding
into recalls.  I believe that concern is unreasonable and
unfounded.  We had many years when IAB and IESG members were
permitted to initiate recalls.  None ever did, despite, in
retrospect, one or two cases when they should have.   In
addition, the pressures within those groups to not break harmony
and start publicly pointing fingers at one of the members are
immense and it still takes 20 signatures (more than the
membership of any of those bodies).  If someone decides that
initiating a recall is needed, then the community needs to hear
about it and hear about it directly (rather than having IAB,
IESG, or IAOC members recruiting others in private to initiate a
recall without even the option of speaking out themselves.
Whispering campaigns are never of benefit to the IETF.

My hope is that you and others will be sufficiently sympathetic
to the position described above to include it in your draft.  If
not, I'd dust off my ancient draft on the subject and post it so
we can have a separate discussion on the issue.   But, in any
event, the ambiguity should be fixed -- we clearly do not need a
situation in which, were a recall petition to start being
circulated, there would be controversy about who can sign it.

     john




From galvin+ietf@elistx.com  Mon Mar  9 08:48:13 2009
Return-Path: <galvin+ietf@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FF983A6BF3 for <ietf-nomcom@core3.amsl.com>; Mon,  9 Mar 2009 08:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QN6lmIzhgc1d for <ietf-nomcom@core3.amsl.com>; Mon,  9 Mar 2009 08:48:12 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id DD6473A699C for <ietf-nomcom@ietf.org>; Mon,  9 Mar 2009 08:47:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KG8009SHX7WBH@elistx.com> for ietf-nomcom@ietf.org; Mon, 09 Mar 2009 11:47:56 -0400 (EDT)
Date: Mon, 09 Mar 2009 11:49:41 -0400
From: James Galvin <galvin+ietf@elistx.com>
In-reply-to: <FB7DC7A43100696E90296D41@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
Message-id: <C2B6B72AE55FFC2E81352D9C@eList-eXpress-LLC.local>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <FB7DC7A43100696E90296D41@PST.JCK.COM>
X-Mailman-Approved-At: Mon, 09 Mar 2009 08:57:43 -0700
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] sitting members and recall (was: draft-galvin-rfc3777bis-00)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 15:48:13 -0000

-- On March 8, 2009 11:05:19 AM -0400 John C Klensin 
<john-ietf@jck.com> wrote regarding [ietf-nomcom] 
draft-galvin-rfc3777bis-00 --

> At the time the recall procedures were changed to require many
> signatures on petitions, they were also changed to make the
> requirement for signatures nomcom-eligibility.
>
> > ...
>
> There is actually an ambiguity in this statement, at least in
> your current draft.  One way to read the draft is that, because
>
> > "15.  Members of the Internet Society Board of Trustees,
> > sitting members of IAOC, sitting members of the IAB, and
> > sitting members of the IESG may not volunteer to serve on the
> > nominating committee."
>
> ...
> they are not permitted
> to participate in recall petitions.

Speaking personally, I agree with you that sitting members of these 
bodies should be permitted to participate both in recall petitions and 
on the recall committee.



Speaking as editor, past process has been that we don't change this 
document unless there is overwhelming support.  So, if other folks 
agree they need to speak up.  Of course, any discussion of the issue is 
also welcome.

And, of course, if folks don't like that process they should comment on 
that too.

Jim


From jmh@joelhalpern.com  Mon Mar  9 09:18:48 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EDE93A6CA5 for <ietf-nomcom@core3.amsl.com>; Mon,  9 Mar 2009 09:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level: 
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=-0.837, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPRMh07yNgJV for <ietf-nomcom@core3.amsl.com>; Mon,  9 Mar 2009 09:18:47 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 82E063A6C78 for <ietf-nomcom@ietf.org>; Mon,  9 Mar 2009 09:17:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id D589F4302FF for <ietf-nomcom@ietf.org>; Mon,  9 Mar 2009 09:18:28 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.100] (pool-71-161-50-192.clppva.btas.verizon.net [71.161.50.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 4B7D0430397 for <ietf-nomcom@ietf.org>; Mon,  9 Mar 2009 09:18:28 -0700 (PDT)
Message-ID: <49B5414D.1060602@joelhalpern.com>
Date: Mon, 09 Mar 2009 12:18:21 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: NomComDiscussion <ietf-nomcom@ietf.org>
References: <FB7DC7A43100696E90296D41@PST.JCK.COM> <C2B6B72AE55FFC2E81352D9C@eList-eXpress-LLC.local>
In-Reply-To: <C2B6B72AE55FFC2E81352D9C@eList-eXpress-LLC.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [ietf-nomcom] sitting members and recall
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 16:18:48 -0000

I would agree that sitting I* members should be able to sign recall 
petitions.  I am not sure whether this is better done in Jim's document, 
or in a separate document.  (We do need to avoid the endless discussions 
of every change any body wants, just to get the IAOC properly documented 
as excluded.)

Yours,
Joel M. Halpern

From brian.e.carpenter@gmail.com  Mon Mar  9 13:24:01 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F03E3A6BB0 for <ietf-nomcom@core3.amsl.com>; Mon,  9 Mar 2009 13:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwEpXcGpxtVo for <ietf-nomcom@core3.amsl.com>; Mon,  9 Mar 2009 13:24:00 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by core3.amsl.com (Postfix) with ESMTP id 805D33A67B2 for <ietf-nomcom@ietf.org>; Mon,  9 Mar 2009 13:24:00 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id l9so1678209rvb.49 for <ietf-nomcom@ietf.org>; Mon, 09 Mar 2009 13:24:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=RPT1V6QuP5huQuPYVl97nYz2TNZ7bAudJua4JJckc2s=; b=uHexbikK8mIKWAyMhEDR/PzjfKBJeo8kDIZeOaKIlUgMNcJ2sCMXLdn1umQ079Or41 HepeE5apAqn38qVMMmyuXx1dM/Vz7HtR9/avTVeQi+1HVoO+KxBBmvQGbOOgUjVFUUIh Qj19IpwEhoa+Rx3koVIvUJKojuv6JC76SHzYs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=A12QJqFbJcJNuYelxR3e6f4/D7PG4gC0sOx7GbGLisxNsoHuzMPRWBe+7DS5UrdzwO YKh6A9yOdBOIVqp8MimnpELJBA5RNl8C9hXPZxd+3BFtr2QwPCFJtHZ8jNUtuUXZ23pP SrBV8DaVdF+zt8BBKozIDVyFa5cfsjeOkYXus=
Received: by 10.141.52.6 with SMTP id e6mr2316073rvk.133.1236630274840; Mon, 09 Mar 2009 13:24:34 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k37sm7817169rvb.1.2009.03.09.13.24.33 (version=SSLv3 cipher=RC4-MD5); Mon, 09 Mar 2009 13:24:34 -0700 (PDT)
Message-ID: <49B57AFF.2070803@gmail.com>
Date: Tue, 10 Mar 2009 09:24:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <FB7DC7A43100696E90296D41@PST.JCK.COM>	<C2B6B72AE55FFC2E81352D9C@eList-eXpress-LLC.local> <49B5414D.1060602@joelhalpern.com>
In-Reply-To: <49B5414D.1060602@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: NomComDiscussion <ietf-nomcom@ietf.org>
Subject: Re: [ietf-nomcom] sitting members and recall
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2009 20:24:01 -0000

I agree. Even in the worst possible case, where a subset of the I*
had a personal problem with another subset of the I*, I don't see
how allowing them to sign a recall petition would actually make the bad
situation even worse. It would only happen if things were already
beyond the ability of the I* to resolve on its own, and would amount
to a request for mediation.

   Brian

On 2009-03-10 05:18, Joel M. Halpern wrote:
> I would agree that sitting I* members should be able to sign recall
> petitions.  I am not sure whether this is better done in Jim's document,
> or in a separate document.  (We do need to avoid the endless discussions
> of every change any body wants, just to get the IAOC properly documented
> as excluded.)
> 
> Yours,
> Joel M. Halpern
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
> 

From danny@tcb.net  Wed Mar 11 22:25:33 2009
Return-Path: <danny@tcb.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 710AE3A68F3 for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQxMkqC2uKSW for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:25:32 -0700 (PDT)
Received: from sa.aa.arbor.net (unknown [204.181.64.1]) by core3.amsl.com (Postfix) with ESMTP id C191E3A67E9 for <ietf-nomcom@ietf.org>; Wed, 11 Mar 2009 22:25:32 -0700 (PDT)
Received: from localhost (sa.aa.arbor.net [10.1.0.64]) by sa.aa.arbor.net (Postfix) with ESMTP id 8E9B416EC1 for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:04 -0400 (EDT)
X-Virus-Scanned: amavisd-new at arbor.net
Received: from 10-1-15-26.aa.arbor.net (10-1-15-26.aa.arbor.net [10.1.15.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sa.aa.arbor.net (Postfix) with ESMTP id D5C4416EBF for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:03 -0400 (EDT)
Message-Id: <506AD998-84A0-4E51-8353-CE8EB8D11E1A@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: NomComDiscussion <ietf-nomcom@ietf.org>
In-Reply-To: <49B57AFF.2070803@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 11 Mar 2009 21:41:44 -0600
References: <FB7DC7A43100696E90296D41@PST.JCK.COM>	<C2B6B72AE55FFC2E81352D9C@eList-eXpress-LLC.local> <49B5414D.1060602@joelhalpern.com> <49B57AFF.2070803@gmail.com>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [ietf-nomcom] sitting members and recall
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 05:25:33 -0000

On Mar 9, 2009, at 2:24 PM, Brian E Carpenter wrote:

> I agree. Even in the worst possible case, where a subset of the I*
> had a personal problem with another subset of the I*, I don't see
> how allowing them to sign a recall petition would actually make the  
> bad
> situation even worse. It would only happen if things were already
> beyond the ability of the I* to resolve on its own, and would amount
> to a request for mediation.

I agree as well..  As for whether this should happen
in this document or a separate one, I believe it is
reasonable to remove the ambiguity that currently
exists in the draft.

-danny


From danny@tcb.net  Wed Mar 11 22:25:34 2009
Return-Path: <danny@tcb.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D8D73A68F3 for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5gsVHsWEY8Z for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:25:33 -0700 (PDT)
Received: from sa.aa.arbor.net (unknown [204.181.64.1]) by core3.amsl.com (Postfix) with ESMTP id A895E3A67E9 for <ietf-nomcom@ietf.org>; Wed, 11 Mar 2009 22:25:33 -0700 (PDT)
Received: from localhost (sa.aa.arbor.net [10.1.0.64]) by sa.aa.arbor.net (Postfix) with ESMTP id 7DD7B16EC1 for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at arbor.net
Received: from 10-1-15-26.aa.arbor.net (10-1-15-26.aa.arbor.net [10.1.15.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sa.aa.arbor.net (Postfix) with ESMTP id C9CE716EBF for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:04 -0400 (EDT)
Message-Id: <7ABEB8B8-3456-4A07-8F16-74D466D78F56@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: NomComDiscussion <ietf-nomcom@ietf.org>
In-Reply-To: <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 11 Mar 2009 21:52:52 -0600
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com> <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com> <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: Liaison from IAOC to NomCom)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 05:25:34 -0000

On Mar 7, 2009, at 2:50 AM, Bernie Hoeneisen wrote:

> Hi,
>
> In past years there were many complaints about liasions taking too  
> much influence on the NomCom decisions making process. Influencing  
> the NomCom in its descision making process is certainly not the task  
> of a liaison. Misusing the position as a liaison is more than  
> disruptive.
>
> However, liaisons have information that is most helpful to the  
> NomCom in finding its decisions. Often only liaisons know what is  
> really going on as they have the inside view ordinary members of the  
> NomCom normally don't have.
>
> Without breaking confidentiality rules, I can say that I  
> particularly enjoied how this issue has been handled in the current  
> NomCom. All liasions were a great help to the NomCom. Liaisons have  
> not even tried to influence the NomCom decision making process by  
> means not appropriate to their position. Liasions have used the  
> feedback tool to provide the NomCom with personal contributions as  
> everbody else. Joel and the liaisons have done a great job that  
> served the NomCom (and the community) most. Thank you all!

I would observe, however, that because liaisons are privy to
internal NomCom discussions, they may be placed in compromising
positions where they need to provide additional input to specific
deliberations, either via the feedback tool or directly, should
they have first-hand knowledge of some factual event that is
being mis-represented, or mis-interpreted, or other.

I'd prefer that text in this area not be overly prescriptive for
this reason.

-danny


From danny@tcb.net  Wed Mar 11 22:29:26 2009
Return-Path: <danny@tcb.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E380C3A67B1 for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4g0RhM7T6ONe for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:29:26 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 3A5E43A68F3 for <ietf-nomcom@ietf.org>; Wed, 11 Mar 2009 22:29:26 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id 463A12684EA; Wed, 11 Mar 2009 23:30:03 -0600 (MDT)
Received: from jchouinard-sim-103.eng.ellacoya.com (97-122-114-22.hlrn.qwest.net [97.122.114.22]) (authenticated-user danny) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for ietf-nomcom@ietf.org; Wed, 11 Mar 2009 23:30:03 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=97.122.114.22; client-port=53968; syn-fingerprint=65535:55:1:64:M1408,N,W3,N,N,T,S; data-bytes=0
Message-Id: <3A604885-8A3C-451D-AE2B-10EAFB9F1D48@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: NomComDiscussion <ietf-nomcom@ietf.org>
In-Reply-To: <DB3084A7-D330-4B23-8044-9E54E180227F@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 11 Mar 2009 23:30:02 -0600
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org>	<20090304224318.974633A6824@core3.amsl.com>	<23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com>	<9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com>	<49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <DB3084A7-D330-4B23-8044-9E54E180227F@cisco.com>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 05:29:27 -0000

On Mar 6, 2009, at 11:44 AM, Fred Baker wrote:

>
> On Mar 6, 2009, at 9:32 AM, Joel M. Halpern wrote:
>
>> The usual reading of the rules is that liaisons do not vote on  
>> nominee selection. But they do vote on all other matters.
>
> I have chaired a nomcom and served as liaison to several. This is  
> consistent with my experience.

As is my experience on the four NomCom's with which I've
served different roles.

-danny

From danny@tcb.net  Wed Mar 11 22:41:21 2009
Return-Path: <danny@tcb.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E79C3A6973 for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kea-K5okY6qU for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 22:41:20 -0700 (PDT)
Received: from sa.aa.arbor.net (unknown [204.181.64.1]) by core3.amsl.com (Postfix) with ESMTP id AB2223A67A5 for <ietf-nomcom@ietf.org>; Wed, 11 Mar 2009 22:41:20 -0700 (PDT)
Received: from localhost (sa.aa.arbor.net [10.1.0.64]) by sa.aa.arbor.net (Postfix) with ESMTP id 0039E16EFC for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at arbor.net
Received: from 10-1-15-26.aa.arbor.net (10-1-15-26.aa.arbor.net [10.1.15.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sa.aa.arbor.net (Postfix) with ESMTP id 5759716EB4 for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:04 -0400 (EDT)
Message-Id: <C4957E8F-D3F5-498B-B570-11C71EEB0445@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: NomComDiscussion <ietf-nomcom@ietf.org>
In-Reply-To: <alpine.DEB.2.00.0903071113440.32572@softronics.hoeneisen.ch>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 11 Mar 2009 21:48:31 -0600
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <alpine.DEB.2.00.0903071113440.32572@softronics.hoeneisen.ch>
X-Mailer: Apple Mail (2.930.3)
Subject: Re: [ietf-nomcom] [IAOC] RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 05:41:21 -0000

On Mar 7, 2009, at 3:17 AM, Bernie Hoeneisen wrote:

> Hi,
>
> IMHO an optional IAOC liaison makes sense. A mandatory IAOC liaison  
> might cause difficulties to the IAOC as not so many IAOC members  
> come into question for this post.

Agreed..

-danny


From danny@tcb.net  Wed Mar 11 23:41:21 2009
Return-Path: <danny@tcb.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7B313A680D for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 23:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ErgkG1dkUgX for <ietf-nomcom@core3.amsl.com>; Wed, 11 Mar 2009 23:41:21 -0700 (PDT)
Received: from sa.aa.arbor.net (unknown [204.181.64.1]) by core3.amsl.com (Postfix) with ESMTP id 024393A6808 for <ietf-nomcom@ietf.org>; Wed, 11 Mar 2009 23:41:21 -0700 (PDT)
Received: from localhost (sa.aa.arbor.net [10.1.0.64]) by sa.aa.arbor.net (Postfix) with ESMTP id E9E9716F0E for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at arbor.net
Received: from 10-1-15-26.aa.arbor.net (10-1-15-26.aa.arbor.net [10.1.15.26]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sa.aa.arbor.net (Postfix) with ESMTP id 48A4B16EB4 for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 01:26:05 -0400 (EDT)
Message-Id: <A498A738-3364-4BFF-926D-3FC0170D041C@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: NomComDiscussion <ietf-nomcom@ietf.org>
In-Reply-To: <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 11 Mar 2009 22:04:37 -0600
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com> <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com> <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch>
X-Mailer: Apple Mail (2.930.3)
Subject: [ietf-nomcom] Liaison 'term limit and affiliation consideration'
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 06:41:21 -0000

Two other topics for consideration, which Spencer and
I outlined in the 3777 issues draft regarding liaisons
are:

- Textual consideration might be given that stems term
limits for liaisons.  E.g., the ISOC should not appoint
the same liaison to the NomCom during successive terms.
This can't occur for the IAB or IESG, given the biyearly
selection frequency, but the issue was raised during one
of my NomComs with regard to the ISOC IETF NomCom liaison.

- Additionally, affiliation of liaisons might well be
given consideration.  That is, while voting members are
already limited to two members with the same affiliation,
there is no consideration given to liaisons, so you
could theoretically wind up with as many as 7 members
(chair, advisor, 2 voting, 3 liaison) from the same
organization and not violate the current rules.

In practice, I've not ever seen anything to suggest that
either of these issues have ever introduced nomcom
product integrity issues, but perception is worthy of
consideration, and these issues have been brought up
several times.

-danny

From jonne.soininen@nsn.com  Thu Mar 12 07:23:31 2009
Return-Path: <jonne.soininen@nsn.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D09EF3A6A53; Thu, 12 Mar 2009 07:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=-0.906, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjP-0oJe1Y-x; Thu, 12 Mar 2009 07:23:30 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id 5C4753A69D2; Thu, 12 Mar 2009 07:23:30 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n2CEO4Lj019619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 12 Mar 2009 15:24:04 +0100
Received: from demuexc025.nsn-intra.net (demuexc025.nsn-intra.net [10.159.32.12]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n2CEO4QN025168; Thu, 12 Mar 2009 15:24:04 +0100
Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 12 Mar 2009 15:24:04 +0100
Received: from 10.144.22.232 ([10.144.22.232]) by FIESEXC015.nsn-intra.net ([10.159.0.28]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.35]) with Microsoft Exchange Server HTTP-DAV ; Thu, 12 Mar 2009 14:24:03 +0000
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Thu, 12 Mar 2009 16:24:00 +0200
From: "Soininen, Jonne (NSN - FI/Espoo)" <jonne.soininen@nsn.com>
To: ext James M Galvin <galvin@elistx.com>, Russ Housley <housley@vigilsec.com>
Message-ID: <C5DEE7A0.899BB%jonne.soininen@nsn.com>
Thread-Topic: [IAOC] [ietf-nomcom] RFC 3777bis: Liaison from IAOC to NomCom
Thread-Index: AcmjHi+eciuH+VpY20qLLDMSB7MgeQ==
In-Reply-To: <728D349C317A08AE31C2BBE1@201-131-212-237.icannmeeting.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 12 Mar 2009 14:24:04.0437 (UTC) FILETIME=[32430850:01C9A31E]
Cc: IAOC List <iaoc@ietf.org>, ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] [IAOC]  RFC 3777bis: Liaison from IAOC to NomCom
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 14:23:31 -0000

Hi Jim,

We did an official poll on the IAOC, and the IAOC's formal position is that
the IAOC would like to have an option liaison position in the Nomcom.

I guess, it is for the IETF process to see if the wish is granted...

Cheers,

Jonne.


On 3/5/09 1:24 AM, "ext James M Galvin" <galvin@elistx.com> wrote:

> Sure, I could see that.  I wish I had left myself enough time to ask
> the IAOC in advance as to what they would prefer but I didn't do that.
> So, let me do it now.
> 
> Would the IAOC want to be required to have a liaison on the NOMCOM,
> similar to the IESG and IAB, or would it prefer to have it be optional,
> similar to the ISOC Board of Trustees?
> 
> Jim
> 
> 
> 
> 
> 
> -- On March 4, 2009 5:37:04 PM -0500 Russ Housley
> <housley@vigilsec.com> wrote regarding [ietf-nomcom] RFC 3777bis:
> Liaison from IAOC to NomCom --
> 
>> Jim:
>> 
>> In the past two years, the IAOC has not provided a liaison to NomCom.
>> Based on this precedent, I think the liaison from the IAOC should be
>> optional.
>> 
>> Russ
>> 
>> At 01:03 PM 3/4/2009, James M Galvin wrote:
>>> 2. The IESG and the IAB are "required" to provide a liaison to the
>>> NOMCOM in RFC3777.  In contrast, the ISOC Board of Trustees has the
>>> option of doing so.  In keeping with the model of the IAOC being
>>> "equal" to the IESG and IAB, I stated that the IAOC is also
>>> required  to provide a liaison.  This point needs to be brought to
>>> the  attention of the IAOC since they may have an opinion.
>> 
>> _______________________________________________
>> ietf-nomcom mailing list
>> ietf-nomcom@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
> 
> 
> _______________________________________________
> IAOC mailing list
> IAOC@ietf.org
> https://www.ietf.org/mailman/listinfo/iaoc

-- 
Jonne Soininen
Nokia Siemens Networks

Tel: +358 40 527 46 34
E-mail: jonne.soininen@nsn.com



From Andrew.Lange@alcatel-lucent.com  Thu Mar 12 13:14:37 2009
Return-Path: <Andrew.Lange@alcatel-lucent.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 024433A68CF for <ietf-nomcom@core3.amsl.com>; Thu, 12 Mar 2009 13:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoqLEPIkCR4v for <ietf-nomcom@core3.amsl.com>; Thu, 12 Mar 2009 13:14:31 -0700 (PDT)
Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id 525623A685E for <ietf-nomcom@ietf.org>; Thu, 12 Mar 2009 13:14:30 -0700 (PDT)
Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id n2CKF3eE006835; Thu, 12 Mar 2009 14:15:07 -0600
Received: from USDALSMBS02.ad3.ad.alcatel.com ([172.22.216.10]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 12 Mar 2009 15:15:03 -0500
Received: from USDALSMBS05.ad3.ad.alcatel.com ([172.22.216.34]) by USDALSMBS02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 12 Mar 2009 15:15:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9A34F.392CFE26"
Date: Thu, 12 Mar 2009 15:13:22 -0500
Message-ID: <66F9363AB70F764C96547BD8A0A3679E024954A0@USDALSMBS05.ad3.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: Liaisonfrom IAOC to NomCom)
Thread-Index: Acmi0w/2Pn8JBMH6TtSQR7kS6W+s9gAe+5sG
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org><20090304224318.974633A6824@core3.amsl.com><23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com><9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com><49B148CA.3050700@nsn.com><06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com><49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com><49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com><D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com><alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch> <7ABEB8B8-3456-4A07-8F16-74D466D78F56@tcb.net>
From: "LANGE Andrew" <Andrew.Lange@alcatel-lucent.com>
To: "Danny McPherson" <danny@tcb.net>, "NomComDiscussion" <ietf-nomcom@ietf.org>
X-OriginalArrivalTime: 12 Mar 2009 20:15:02.0058 (UTC) FILETIME=[399500A0:01C9A34F]
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
Subject: Re: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: Liaisonfrom IAOC to NomCom)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2009 20:14:37 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9A34F.392CFE26
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I agree with Danny on this, we don't want to over-prescribe liaison =
behavior.  Although there is potential for abuse with liaisons they =
provide can important insights.  Most liaisons are quite respectful of =
the voting members of NomCom.

Andrew


-----Original Message-----
From: ietf-nomcom-bounces@ietf.org on behalf of Danny McPherson
Sent: Wed 3/11/2009 8:52 PM
To: NomComDiscussion
Subject: Re: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: =
Liaisonfrom IAOC to NomCom)
=20

On Mar 7, 2009, at 2:50 AM, Bernie Hoeneisen wrote:

> Hi,
>
> In past years there were many complaints about liasions taking too =20
> much influence on the NomCom decisions making process. Influencing =20
> the NomCom in its descision making process is certainly not the task =20
> of a liaison. Misusing the position as a liaison is more than =20
> disruptive.
>
> However, liaisons have information that is most helpful to the =20
> NomCom in finding its decisions. Often only liaisons know what is =20
> really going on as they have the inside view ordinary members of the =20
> NomCom normally don't have.
>
> Without breaking confidentiality rules, I can say that I =20
> particularly enjoied how this issue has been handled in the current =20
> NomCom. All liasions were a great help to the NomCom. Liaisons have =20
> not even tried to influence the NomCom decision making process by =20
> means not appropriate to their position. Liasions have used the =20
> feedback tool to provide the NomCom with personal contributions as =20
> everbody else. Joel and the liaisons have done a great job that =20
> served the NomCom (and the community) most. Thank you all!

I would observe, however, that because liaisons are privy to
internal NomCom discussions, they may be placed in compromising
positions where they need to provide additional input to specific
deliberations, either via the feedback tool or directly, should
they have first-hand knowledge of some factual event that is
being mis-represented, or mis-interpreted, or other.

I'd prefer that text in this area not be overly prescriptive for
this reason.

-danny

_______________________________________________
ietf-nomcom mailing list
ietf-nomcom@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-nomcom


------_=_NextPart_001_01C9A34F.392CFE26
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: =
Liaisonfrom IAOC to NomCom)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I agree with Danny on this, we don't want to =
over-prescribe liaison behavior.&nbsp; Although there is potential for =
abuse with liaisons they provide can important insights.&nbsp; Most =
liaisons are quite respectful of the voting members of NomCom.<BR>
<BR>
Andrew<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: ietf-nomcom-bounces@ietf.org on behalf of Danny McPherson<BR>
Sent: Wed 3/11/2009 8:52 PM<BR>
To: NomComDiscussion<BR>
Subject: Re: [ietf-nomcom] Role of Liaisons (was Re: RFC 3777bis: =
Liaisonfrom IAOC to NomCom)<BR>
<BR>
<BR>
On Mar 7, 2009, at 2:50 AM, Bernie Hoeneisen wrote:<BR>
<BR>
&gt; Hi,<BR>
&gt;<BR>
&gt; In past years there were many complaints about liasions taking =
too&nbsp;<BR>
&gt; much influence on the NomCom decisions making process. =
Influencing&nbsp;<BR>
&gt; the NomCom in its descision making process is certainly not the =
task&nbsp;<BR>
&gt; of a liaison. Misusing the position as a liaison is more =
than&nbsp;<BR>
&gt; disruptive.<BR>
&gt;<BR>
&gt; However, liaisons have information that is most helpful to =
the&nbsp;<BR>
&gt; NomCom in finding its decisions. Often only liaisons know what =
is&nbsp;<BR>
&gt; really going on as they have the inside view ordinary members of =
the&nbsp;<BR>
&gt; NomCom normally don't have.<BR>
&gt;<BR>
&gt; Without breaking confidentiality rules, I can say that I&nbsp;<BR>
&gt; particularly enjoied how this issue has been handled in the =
current&nbsp;<BR>
&gt; NomCom. All liasions were a great help to the NomCom. Liaisons =
have&nbsp;<BR>
&gt; not even tried to influence the NomCom decision making process =
by&nbsp;<BR>
&gt; means not appropriate to their position. Liasions have used =
the&nbsp;<BR>
&gt; feedback tool to provide the NomCom with personal contributions =
as&nbsp;<BR>
&gt; everbody else. Joel and the liaisons have done a great job =
that&nbsp;<BR>
&gt; served the NomCom (and the community) most. Thank you all!<BR>
<BR>
I would observe, however, that because liaisons are privy to<BR>
internal NomCom discussions, they may be placed in compromising<BR>
positions where they need to provide additional input to specific<BR>
deliberations, either via the feedback tool or directly, should<BR>
they have first-hand knowledge of some factual event that is<BR>
being mis-represented, or mis-interpreted, or other.<BR>
<BR>
I'd prefer that text in this area not be overly prescriptive for<BR>
this reason.<BR>
<BR>
-danny<BR>
<BR>
_______________________________________________<BR>
ietf-nomcom mailing list<BR>
ietf-nomcom@ietf.org<BR>
<A =
HREF=3D"https://www.ietf.org/mailman/listinfo/ietf-nomcom">https://www.ie=
tf.org/mailman/listinfo/ietf-nomcom</A><BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9A34F.392CFE26--

From housley@vigilsec.com  Fri Mar 13 07:00:20 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36D1F28C0DF for <ietf-nomcom@core3.amsl.com>; Fri, 13 Mar 2009 07:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eCmuPNWOJhVz for <ietf-nomcom@core3.amsl.com>; Fri, 13 Mar 2009 07:00:13 -0700 (PDT)
Received: from smtpout.capalon.com (smtpout.capalon.com [63.208.156.20]) by core3.amsl.com (Postfix) with ESMTP id 4553428C108 for <ietf-nomcom@ietf.org>; Fri, 13 Mar 2009 07:00:10 -0700 (PDT)
Received: from localhost (viruscan [8.8.40.174]) by smtpout.capalon.com (Postfix) with ESMTP id BC39C1D02FAC for <ietf-nomcom@ietf.org>; Fri, 13 Mar 2009 09:51:08 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.4.5 (20070130) (Debian) at capalon.com
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by smtpout.capalon.com (Postfix) with SMTP id E07831D03B73 for <ietf-nomcom@ietf.org>; Fri, 13 Mar 2009 09:48:50 -0400 (EDT)
Received: (qmail 6599 invoked by uid 0); 13 Mar 2009 13:58:27 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.144.212) by woodstock.binhost.com with SMTP; 13 Mar 2009 13:58:27 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 13 Mar 2009 09:58:01 -0400
To: Danny McPherson <danny@tcb.net>,NomComDiscussion <ietf-nomcom@ietf.org>
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <A498A738-3364-4BFF-926D-3FC0170D041C@tcb.net>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com> <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com> <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch> <A498A738-3364-4BFF-926D-3FC0170D041C@tcb.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20090313134850.E07831D03B73@smtpout.capalon.com>
Subject: Re: [ietf-nomcom] Liaison 'term limit and affiliation consideration'
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:00:20 -0000

In my view, some guidance on these topics should be included in 
3777bis, even if it is not rules.

Russ

At 12:04 AM 3/12/2009, Danny McPherson wrote:
>Two other topics for consideration, which Spencer and
>I outlined in the 3777 issues draft regarding liaisons
>are:
>
>- Textual consideration might be given that stems term
>limits for liaisons.  E.g., the ISOC should not appoint
>the same liaison to the NomCom during successive terms.
>This can't occur for the IAB or IESG, given the biyearly
>selection frequency, but the issue was raised during one
>of my NomComs with regard to the ISOC IETF NomCom liaison.
>
>- Additionally, affiliation of liaisons might well be
>given consideration.  That is, while voting members are
>already limited to two members with the same affiliation,
>there is no consideration given to liaisons, so you
>could theoretically wind up with as many as 7 members
>(chair, advisor, 2 voting, 3 liaison) from the same
>organization and not violate the current rules.
>
>In practice, I've not ever seen anything to suggest that
>either of these issues have ever introduced nomcom
>product integrity issues, but perception is worthy of
>consideration, and these issues have been brought up
>several times.
>
>-danny
>_______________________________________________
>ietf-nomcom mailing list
>ietf-nomcom@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf-nomcom
>


From spencer@wonderhamster.org  Fri Mar 13 07:07:07 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FB6D28C108 for <ietf-nomcom@core3.amsl.com>; Fri, 13 Mar 2009 07:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level: 
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=0.295,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXBeMG2HnljT for <ietf-nomcom@core3.amsl.com>; Fri, 13 Mar 2009 07:07:00 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 5818F28C114 for <ietf-nomcom@ietf.org>; Fri, 13 Mar 2009 07:06:59 -0700 (PDT)
Received: from S73602b (cpe-72-190-78-151.tx.res.rr.com [72.190.78.151]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1Li82p1CXF-000d3u; Fri, 13 Mar 2009 10:07:30 -0400
Message-ID: <E896E9E8679746A1AB608808A2DA2FD4@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Danny McPherson" <danny@tcb.net>, "NomComDiscussion" <ietf-nomcom@ietf.org>, "Russ Housley" <housley@vigilsec.com>
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org><20090304224318.974633A6824@core3.amsl.com><23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com><9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com><49B148CA.3050700@nsn.com><06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com><49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com><49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com><D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com><alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch><A498A738-3364-4BFF-926D-3FC0170D041C@tcb.net> <20090313134850.E07831D03B73@smtpout.capalon.com>
Date: Fri, 13 Mar 2009 09:07:17 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX193G+KxjHs3MxhxkXW36MS8sQN9Q8S4DLtrI/5 8fNPuWOnSWLuJ2+Ae1x0qP8XT0uAgGAY8vKgT8i3FhHpgC20KL c/4Gr2q66ZPfII3k1Fd81IYM4mIy4VHsN+4IaozAA8=
Subject: Re: [ietf-nomcom] Liaison 'term limit and affiliation consideration'
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:07:07 -0000

This is pointing to Jim's earlier question about whether we fold other 
drafts into 3777bis, or approve them separately.

Russ, were you proposing that we would be putting all the revisions into 
3777bis?

I am concerned about the level of fate-sharing that would lead to (the draft 
would progress at the rate of the least-accepted proposal in the draft), and 
I'm concerned about our ability to cap off new proposals and publish a 
3777bis in the near future, if we keep adding proposals to a single draft.

Thanks,

Spencer


> In my view, some guidance on these topics should be included in 3777bis, 
> even if it is not rules.
>
> Russ
>
> At 12:04 AM 3/12/2009, Danny McPherson wrote:
>>Two other topics for consideration, which Spencer and
>>I outlined in the 3777 issues draft regarding liaisons
>>are:
>>
>>- Textual consideration might be given that stems term
>>limits for liaisons.  E.g., the ISOC should not appoint
>>the same liaison to the NomCom during successive terms.
>>This can't occur for the IAB or IESG, given the biyearly
>>selection frequency, but the issue was raised during one
>>of my NomComs with regard to the ISOC IETF NomCom liaison.
>>
>>- Additionally, affiliation of liaisons might well be
>>given consideration.  That is, while voting members are
>>already limited to two members with the same affiliation,
>>there is no consideration given to liaisons, so you
>>could theoretically wind up with as many as 7 members
>>(chair, advisor, 2 voting, 3 liaison) from the same
>>organization and not violate the current rules.
>>
>>In practice, I've not ever seen anything to suggest that
>>either of these issues have ever introduced nomcom
>>product integrity issues, but perception is worthy of
>>consideration, and these issues have been brought up
>>several times.
>>
>>-danny
>>_______________________________________________
>>ietf-nomcom mailing list
>>ietf-nomcom@ietf.org
>>https://www.ietf.org/mailman/listinfo/ietf-nomcom
>>
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
> 



From galvin@elistx.com  Fri Mar 13 07:25:36 2009
Return-Path: <galvin@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBA773A684A for <ietf-nomcom@core3.amsl.com>; Fri, 13 Mar 2009 07:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ueQKy9g3WVIY for <ietf-nomcom@core3.amsl.com>; Fri, 13 Mar 2009 07:25:30 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id A3AD83A6A3D for <ietf-nomcom@ietf.org>; Fri, 13 Mar 2009 07:25:24 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KGG00A3O81XL7@elistx.com> for ietf-nomcom@ietf.org; Fri, 13 Mar 2009 10:25:10 -0400 (EDT)
Date: Fri, 13 Mar 2009 10:27:14 -0400
From: James M Galvin <galvin@elistx.com>
In-reply-to: <E896E9E8679746A1AB608808A2DA2FD4@china.huawei.com>
To: NomComDiscussion <ietf-nomcom@ietf.org>
Message-id: <650EFA498FE9C7FFD5DFD118@eList-eXpress-LLC.local>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <2D1944E8D1D6F58331EF77CD@201-131-220-159.icannmeeting.org> <20090304224318.974633A6824@core3.amsl.com> <23DA0636-0FF3-48F2-AFD3-D2944FB30238@nokia.com> <9B2DA289-28C9-47ED-96CE-8895D1E7EF64@cisco.com> <49B148CA.3050700@nsn.com> <06CFE121-15C8-49CB-888C-7DC6E0ABA140@cisco.com> <49B14D2E.5050709@joelhalpern.com> <49B15C41.7040507@nsn.com> <49B15E34.3000202@joelhalpern.com> <49B16DEC.7000504@nsn.com> <D105391C-45A1-471D-9AB7-D7D32BAE0C80@cisco.com> <alpine.DEB.2.00.0903070911060.32007@softronics.hoeneisen.ch> <A498A738-3364-4BFF-926D-3FC0170D041C@tcb.net> <20090313134850.E07831D03B73@smtpout.capalon.com> <E896E9E8679746A1AB608808A2DA2FD4@china.huawei.com>
Subject: Re: [ietf-nomcom] Liaison 'term limit and affiliation consideration'
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 14:25:36 -0000

-- On March 13, 2009 9:07:17 AM -0500 Spencer Dawkins 
<spencer@wonderhamster.org> wrote regarding Re: [ietf-nomcom] Liaison 
'term limit and affiliation consideration' --

> I am concerned about the level of fate-sharing that would lead to
> (the draft would progress at the rate of the least-accepted proposal
> in the draft), and I'm concerned about our ability to cap off new
> proposals and publish a 3777bis in the near future, if we keep adding
> proposals to a single draft.

I agree that this can be an issue (as it is for any document in the 
IETF) but if there is the option to progress separate documents as an 
update to 3777bis I think we can manage this.

I would propose that we include as much as we can in 3777bis up to the 
point that we want to publish it and then to continue to progress other 
issues in the timeframe they need to ensure adequate discussion and 
consensus.

Who knows, maybe things will play out in a way that a 3777bisbis will 
make sense rather than a number of separate update documents.

But then again, I'm almost afraid to ask this question but, is this a 
working group or just a discussion group for individual submissions? 
Actually, I know the answer to that question.  The real question is 
what that means to the process we will (or can?) follow?

Jim


From brian.e.carpenter@gmail.com  Sun Mar 15 19:40:41 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F18F3A67A4 for <ietf-nomcom@core3.amsl.com>; Sun, 15 Mar 2009 19:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SUcATA-N3k3F for <ietf-nomcom@core3.amsl.com>; Sun, 15 Mar 2009 19:40:40 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by core3.amsl.com (Postfix) with ESMTP id 989F73A67F2 for <ietf-nomcom@ietf.org>; Sun, 15 Mar 2009 19:40:40 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id l9so2575349rvb.49 for <ietf-nomcom@ietf.org>; Sun, 15 Mar 2009 19:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=E5cJ/fmxgyPcmcwtxW2RNvW9wZpwCVKLjApcipSRsF4=; b=Bz5bfvxe9GbxDa+/hU4X6hF74uvyam0NFWZoulaHwDLdDbnwydBg00jYreM3u33VkP 6if/2mlQ1IPm4HpgWkMZv9ASjJ5+YtzjfUHd2nmoh+cQBmIJPeRtbzxJWZ8oWofXZu6u BDryVoF7E2Y4n/BZYFThioY0YYzZjweUqJz8U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=HGtOSMyg1X+tqzxinbDq7ApPvcDAhHzUBWIl9vAS1oNWb/+6z7fXRmCuvAfXoDNNu+ d5Tx3SLKrtsaUzY1/lwF+SMs8AeK2d4N9FLrPcL6DrdOP11CZdnAh+7gUup59jL02O28 f6IUHnbZyHwCZo6bf7kSDB4rxNIRllJbvs0+Y=
Received: by 10.140.141.16 with SMTP id o16mr2016084rvd.138.1237171281984; Sun, 15 Mar 2009 19:41:21 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k2sm15266000rvb.4.2009.03.15.19.41.20 (version=SSLv3 cipher=RC4-MD5); Sun, 15 Mar 2009 19:41:21 -0700 (PDT)
Message-ID: <49BDBC4F.8030208@gmail.com>
Date: Mon, 16 Mar 2009 15:41:19 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf-nomcom@ietf.org
References: <20090304174501.838FF3A6ABF@core3.amsl.com>
In-Reply-To: <20090304174501.838FF3A6ABF@core3.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [ietf-nomcom] I-D Action:draft-galvin-rfc3777bis-00.txt
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2009 02:40:41 -0000

> <32>
>    3.  One-half of each of the then current positions is selected to be
>        reviewed each year.
> 
>        The intent of this rule to ensure the review of approximately
>        one-half of the sitting members of the bodies to which this
>        document applies.  

Note that as far as the IAOC seats are concerned, this has to be read
along with BCP101 section 4. I think a normative reference would be
useful.

> <33>
...
>        For confirmed candidates of other bodies the terms overlap with
>        the terms of the sitting members for the entire week of the
>        meeting.

This, I fear, actually updates BCP101, which allows for zero overlap,
as far as I can tell. This has legal significance, as far as trusteeship
of the IETF Trust goes, so it needs to be rock solid.

> <39>	
> 			1. The IETF Executive Director informs the nominating committee	
> 			of the open positions to be reviewed.

I observe that there is no such person as the Exec D any more.
Under BCP101, the IAOC's duties include:

>>    o  To designate, in consultation with the IAB and the IESG, the
>>       person or people who carry out the tasks that other IETF process
>>       documents say are carried out by the IETF Executive Director.

At http://iaoc.ietf.org/execd-tasks.html you can find

>> Both occurrences of "Executive Director" are replaced by "Secretariat."

    Brian






From housley@vigilsec.com  Mon Mar 16 06:42:59 2009
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAB0E28C0EB for <ietf-nomcom@core3.amsl.com>; Mon, 16 Mar 2009 06:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZjJCx-HGIAc for <ietf-nomcom@core3.amsl.com>; Mon, 16 Mar 2009 06:42:59 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id EB8713A63EC for <ietf-nomcom@ietf.org>; Mon, 16 Mar 2009 06:42:58 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9DE7F9A474D; Mon, 16 Mar 2009 09:43:47 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id I4g8Hi6nnLda; Mon, 16 Mar 2009 09:43:35 -0400 (EDT)
Received: from THINKPADR52.vigilsec.com (pool-96-255-144-212.washdc.fios.verizon.net [96.255.144.212]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 989AB9A4799; Mon, 16 Mar 2009 09:43:42 -0400 (EDT)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 16 Mar 2009 09:43:32 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <49BDBC4F.8030208@gmail.com>
References: <20090304174501.838FF3A6ABF@core3.amsl.com> <49BDBC4F.8030208@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20090316134342.989AB9A4799@odin.smetech.net>
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] I-D Action:draft-galvin-rfc3777bis-00.txt
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2009 13:42:59 -0000

Brian:

> > <39>
> >                       1. The IETF Executive Director informs the 
> nominating committee
> >                       of the open positions to be reviewed.
>
>I observe that there is no such person as the Exec D any more.
>Under BCP101, the IAOC's duties include:

Not so.  The IETF Executive Director is currently Alexa Morris.

Russ


From brian.e.carpenter@gmail.com  Mon Mar 16 13:28:18 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA7873A684E for <ietf-nomcom@core3.amsl.com>; Mon, 16 Mar 2009 13:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level: 
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WlKKvYoWPKlx for <ietf-nomcom@core3.amsl.com>; Mon, 16 Mar 2009 13:28:18 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by core3.amsl.com (Postfix) with ESMTP id 225E43A6829 for <ietf-nomcom@ietf.org>; Mon, 16 Mar 2009 13:28:18 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id m33so1614588wag.5 for <ietf-nomcom@ietf.org>; Mon, 16 Mar 2009 13:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=N7xNVC8EmXfxY0uSZ+Kn579jBrKtkgXYezZuKhfI37U=; b=LrSOIYa69E9lAJ6yx9XxbPeTJqeS/fKaLz6GChwbY/i6hjIugJgY2h1YwaUzDG3QHn AKExKunajMYXzSnXn5ouGfuZyA4hfW4iHU+pdtShiV3nlxQ3Ge3wrZtX/r9mD2pGlT7m nzPuIusDk5m0RlJGhELJax+Ke359zupTPAYu8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=uOoqd8VyW42y+8JGzLSQiO7OrkMDbumDvSOAXgGqXF8dgnT4MnfXzqED1BuJ+uhBw9 Yg3U/xAjqRahGmkZAJjei9JZyXJ8GWjwanYH0oal0+FTUep1pU36++C1bqdcbpPIe6jY JoJkMTlyV3M0mULP1Yk9mPb9FvljsIQn5K348=
Received: by 10.114.124.1 with SMTP id w1mr3599981wac.135.1237235340265; Mon, 16 Mar 2009 13:29:00 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id j15sm5187908waf.20.2009.03.16.13.28.59 (version=SSLv3 cipher=RC4-MD5); Mon, 16 Mar 2009 13:28:59 -0700 (PDT)
Message-ID: <49BEB689.3090106@gmail.com>
Date: Tue, 17 Mar 2009 09:28:57 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
References: <20090304174501.838FF3A6ABF@core3.amsl.com> <49BDBC4F.8030208@gmail.com> <20090316134342.989AB9A4799@odin.smetech.net>
In-Reply-To: <20090316134342.989AB9A4799@odin.smetech.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] I-D Action:draft-galvin-rfc3777bis-00.txt
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2009 20:28:18 -0000

On 2009-03-17 02:43, Russ Housley wrote:
> Brian:
> 
>> > <39>
>> >                       1. The IETF Executive Director informs the
>> nominating committee
>> >                       of the open positions to be reviewed.
>>
>> I observe that there is no such person as the Exec D any more.
>> Under BCP101, the IAOC's duties include:
> 
> Not so.  The IETF Executive Director is currently Alexa Morris.

Clearly, I have no problem with this, but RFC4071 was written on
the assumption that the job title was OBE. That leaves a small
inconsistency to be cleared up, but not here.

   Brian

From smb@cs.columbia.edu  Sun Mar 22 11:04:51 2009
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 447BA28C16E for <ietf-nomcom@core3.amsl.com>; Sun, 22 Mar 2009 11:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.751
X-Spam-Level: 
X-Spam-Status: No, score=-5.751 tagged_above=-999 required=5 tests=[AWL=-0.641, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5jaSIhrmcIJG for <ietf-nomcom@core3.amsl.com>; Sun, 22 Mar 2009 11:04:50 -0700 (PDT)
Received: from machshav.com (machshav.com [198.180.150.44]) by core3.amsl.com (Postfix) with ESMTP id 2BCB328C180 for <ietf-nomcom@ietf.org>; Sun, 22 Mar 2009 11:04:50 -0700 (PDT)
Received: by machshav.com (Postfix, from userid 512) id 6C1473288B8; Sun, 22 Mar 2009 18:05:36 +0000 (GMT)
Received: from yellowstone.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id 6E44E3288B6 for <ietf-nomcom@ietf.org>; Sun, 22 Mar 2009 18:05:33 +0000 (GMT)
Received: from cs.columbia.edu (localhost [127.0.0.1]) by yellowstone.machshav.com (Postfix) with ESMTP id 7A5C42978B8 for <ietf-nomcom@ietf.org>; Sun, 22 Mar 2009 14:05:28 -0400 (EDT)
Date: Sun, 22 Mar 2009 14:05:27 -0400
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: ietf-nomcom@ietf.org
Message-ID: <20090322140527.70136df8@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64--netbsd)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 23 Mar 2009 08:25:13 -0700
Subject: [ietf-nomcom] IETF jury duty?
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2009 18:04:51 -0000

Perhaps service on the nomcom should be the IETF equivalent of jury
duty -- something that all "citizens" are subject to.

The IETF has no membership, so we can't easily have elections.  If the
leadership controls the nomcom process, the dangers of a
self-perpetuating oligarchy are obvious.  The current scheme, though,
is susceptible to attempts to pack the nomcom, and I've heard rumors of
just that sort of behavior.  Even without that, there is the obvious
problem of too many familiar faces on the selection list.

Instead, I propose a random selection of members from everyone
eligible.  That is, the Secretariat should compile a list of everyone
who meets the criteria -- attendance at M of the last N meetings.
Perhaps it should be augmented by adding the names of authors of WG
drafts from the last K years, though that may be too easily
manipulated.  (I specify "WG drafts" to require some show of
community acceptance of the person's technical competence.)  The current
random selection algorithm would be applied to that list.

Thoughts?  (For the record -- I haven't attended a meeting since
11/2006, nor have I authored any WG drafts since then, so I'm
ineligible by any of these criteria.)


		--Steve Bellovin, http://www.cs.columbia.edu/~smb

From jmh@joelhalpern.com  Mon Mar 23 09:29:57 2009
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D9FC3A6C40 for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 09:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kIK8EDHJdfc for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 09:29:56 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 6A3663A6C3E for <ietf-nomcom@ietf.org>; Mon, 23 Mar 2009 09:29:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id C1AD54303C8; Mon, 23 Mar 2009 09:30:46 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [130.129.17.160] (dhcp-11a0.meeting.ietf.org [130.129.17.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 8BFFF43039E; Mon, 23 Mar 2009 09:30:46 -0700 (PDT)
Message-ID: <49C7B934.2000405@joelhalpern.com>
Date: Mon, 23 Mar 2009 12:30:44 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Steven M. Bellovin" <smb@cs.columbia.edu>
References: <20090322140527.70136df8@cs.columbia.edu>
In-Reply-To: <20090322140527.70136df8@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] IETF jury duty?
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 16:29:57 -0000

My immediate reaction is that this is probably not a good idea.
1) The nomcom is a significant amount of work.  Trying to force someone 
who is unwilling to actually do the work is probably not going to succeed.
2) It does not seem appropriate to demand that someone make themselves 
ineligible for appointment to the IESG/IAB/IAOC.
3) I suspect that some people are not volunteering because they feel 
that they would do a bad job on this sort of activity.  They may well be 
right.  SHould we really force them onto the committee anyway?

It is attractive to force everyone into the pool.  It is tempting to 
suggest an opt-out version of the same idea.  I suspect it still has too 
many negatives, but I do lik ethe idea of getting more volunteers.  (99 
was nice, but it is not really representative of the community.)

Joel

Steven M. Bellovin wrote:
> Perhaps service on the nomcom should be the IETF equivalent of jury
> duty -- something that all "citizens" are subject to.
> 
> The IETF has no membership, so we can't easily have elections.  If the
> leadership controls the nomcom process, the dangers of a
> self-perpetuating oligarchy are obvious.  The current scheme, though,
> is susceptible to attempts to pack the nomcom, and I've heard rumors of
> just that sort of behavior.  Even without that, there is the obvious
> problem of too many familiar faces on the selection list.
> 
> Instead, I propose a random selection of members from everyone
> eligible.  That is, the Secretariat should compile a list of everyone
> who meets the criteria -- attendance at M of the last N meetings.
> Perhaps it should be augmented by adding the names of authors of WG
> drafts from the last K years, though that may be too easily
> manipulated.  (I specify "WG drafts" to require some show of
> community acceptance of the person's technical competence.)  The current
> random selection algorithm would be applied to that list.
> 
> Thoughts?  (For the record -- I haven't attended a meeting since
> 11/2006, nor have I authored any WG drafts since then, so I'm
> ineligible by any of these criteria.)
> 
> 
> 		--Steve Bellovin, http://www.cs.columbia.edu/~smb
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
> 

From sm@resistor.net  Mon Mar 23 10:31:41 2009
Return-Path: <sm@resistor.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AB703A6C5B for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 10:31:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.011,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5C3YgXLIkrSp for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 10:31:40 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 659FE3A6C5A for <ietf-nomcom@ietf.org>; Mon, 23 Mar 2009 10:31:40 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4.Alpha0/8.14.4.Alpha0) with ESMTP id n2NHWBNS010014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Mar 2009 10:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1237829542; x=1237915942; bh=oWgs105gW+nflytIlU0EbV57gpOKOi135Q7/CJAS7Ro=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=yoPsp5eWt1wdhtRycYHwclm/R9dkCxa6d9L9tstYIBBiSYrJHfMwEyNnsDm9LhCMl vfhsIjvQUsHa1YkwAgTnpKWlDTePOUSC/N0yghe1XnwlOv6tnpJ21TiDCoU2ZSqL24 cjT721AsAjPCUmvZWOsONi80qU758yZ9lCxXic1g=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=rI//o7L7YAo9EW26BKn5kaFdFbo3BQaCPIkjpNIWfDf4FbhboVLVjLPiVY57k5DNI qu2MeIOhHHAeFa4KDn1TKLChe22AF/X76wwNEdMN/rJZe8t9+1y/HDoYOxo89pddIqq 0k7B5HpT4ePLn92iHlDkdxrqBNNZsha/26jZtXY=
Message-Id: <6.2.5.6.2.20090323100150.02fc4768@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 23 Mar 2009 10:32:00 -0700
To: "Steven M. Bellovin" <smb@cs.columbia.edu>
From: SM <sm@resistor.net>
In-Reply-To: <20090322140527.70136df8@cs.columbia.edu>
References: <20090322140527.70136df8@cs.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] IETF jury duty?
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 17:31:41 -0000

At 11:05 22-03-2009, Steven M. Bellovin wrote:
>Perhaps service on the nomcom should be the IETF equivalent of jury
>duty -- something that all "citizens" are subject to.
>
>The IETF has no membership, so we can't easily have elections.  If the
>leadership controls the nomcom process, the dangers of a
>self-perpetuating oligarchy are obvious.  The current scheme, though,
>is susceptible to attempts to pack the nomcom, and I've heard rumors of
>just that sort of behavior.  Even without that, there is the obvious
>problem of too many familiar faces on the selection list.

People find excuses to escape jury duty.  Making nomcom "service" 
mandatory might avoid rumors of "pack the nomcom" at the expense of 
having volunteers who are prepared to put in the time and effort.

>Instead, I propose a random selection of members from everyone
>eligible.  That is, the Secretariat should compile a list of everyone
>who meets the criteria -- attendance at M of the last N meetings.
>Perhaps it should be augmented by adding the names of authors of WG
>drafts from the last K years, though that may be too easily
>manipulated.  (I specify "WG drafts" to require some show of
>community acceptance of the person's technical competence.)  The current
>random selection algorithm would be applied to that list.

What you are proposing here is to increase the size of the pool for 
nomcom eligibility.  Take a look at the distribution of documents by 
company.  If you are using authorship as a criteria, that might 
encourage "author bloat".

Regards,
-sm 


From smb@cs.columbia.edu  Mon Mar 23 10:58:38 2009
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 283AC3A6B03 for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 10:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.453
X-Spam-Level: 
X-Spam-Status: No, score=-6.453 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5RDrbr68jDpo for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 10:58:37 -0700 (PDT)
Received: from machshav.com (machshav.com [198.180.150.44]) by core3.amsl.com (Postfix) with ESMTP id 091FE3A69AF for <ietf-nomcom@ietf.org>; Mon, 23 Mar 2009 10:58:37 -0700 (PDT)
Received: by machshav.com (Postfix, from userid 512) id 624D4328EB5; Mon, 23 Mar 2009 17:59:24 +0000 (GMT)
Received: from yellowstone.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id 24DA43284B8; Mon, 23 Mar 2009 17:59:23 +0000 (GMT)
Received: from cs.columbia.edu (localhost [127.0.0.1]) by yellowstone.machshav.com (Postfix) with ESMTP id 27CE7297931; Mon, 23 Mar 2009 13:59:22 -0400 (EDT)
Date: Mon, 23 Mar 2009 13:59:22 -0400
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: SM <sm@resistor.net>
Message-ID: <20090323135922.45e8945b@cs.columbia.edu>
In-Reply-To: <6.2.5.6.2.20090323100150.02fc4768@resistor.net>
References: <20090322140527.70136df8@cs.columbia.edu> <6.2.5.6.2.20090323100150.02fc4768@resistor.net>
Organization: Columbia University
X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; x86_64--netbsd)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] IETF jury duty?
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 17:58:38 -0000

On Mon, 23 Mar 2009 10:32:00 -0700
SM <sm@resistor.net> wrote:

> >Perhaps it should be augmented by adding the names of authors of WG
> >drafts from the last K years, though that may be too easily
> >manipulated.  (I specify "WG drafts" to require some show of
> >community acceptance of the person's technical competence.)  The
> >current random selection algorithm would be applied to that list.
> 
> What you are proposing here is to increase the size of the pool for 
> nomcom eligibility.  Take a look at the distribution of documents by 
> company.  If you are using authorship as a criteria, that might 
> encourage "author bloat".

You'll note that I said "perhaps"...


		--Steve Bellovin, http://www.cs.columbia.edu/~smb

From galvin@elistx.com  Mon Mar 23 18:03:12 2009
Return-Path: <galvin@elistx.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3050228C1CE for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 18:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vg0fRZQh7mSe for <ietf-nomcom@core3.amsl.com>; Mon, 23 Mar 2009 18:03:11 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.154.239.222]) by core3.amsl.com (Postfix) with ESMTP id AC5913A6A43 for <ietf-nomcom@ietf.org>; Mon, 23 Mar 2009 18:03:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31546) with ESMTP id <0KGZ00D6BK7XP2@elistx.com> for ietf-nomcom@ietf.org; Mon, 23 Mar 2009 21:02:23 -0400 (EDT)
Date: Mon, 23 Mar 2009 18:05:17 -0700
From: James M Galvin <galvin@elistx.com>
In-reply-to: <49BDBC4F.8030208@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf-nomcom@ietf.org
Message-id: <E77F12A235ACF44033DE5911@dhcp-51f2.meeting.ietf.org>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <20090304174501.838FF3A6ABF@core3.amsl.com> <49BDBC4F.8030208@gmail.com>
Subject: Re: [ietf-nomcom] I-D Action:draft-galvin-rfc3777bis-00.txt
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2009 01:03:12 -0000

-- On March 16, 2009 3:41:19 PM +1300 Brian E Carpenter 
<brian.e.carpenter@gmail.com> wrote regarding Re: [ietf-nomcom] I-D 
Action:draft-galvin-rfc3777bis-00.txt --

> >        For confirmed candidates of other bodies the terms overlap
> >        with the terms of the sitting members for the entire week of
> >        the meeting.
>
> This, I fear, actually updates BCP101, which allows for zero overlap,
> as far as I can tell. This has legal significance, as far as
> trusteeship of the IETF Trust goes, so it needs to be rock solid.

BCP101 only speaks explicitly to when terms end, not to when terms 
begin.  So, I would not agree that it "allows for zero overlap."

However, if there is a legal issue then we should get legal advice.  I 
don't see any issue with stating whatever the "overlap" or 
"non-overlap" needs to be for the IAOC, according to whatever our legal 
advice dictates.

Jim



From spencer@wonderhamster.org  Tue Mar 31 15:20:52 2009
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36D453A6860 for <ietf-nomcom@core3.amsl.com>; Tue, 31 Mar 2009 15:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.385
X-Spam-Level: 
X-Spam-Status: No, score=-1.385 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_20=-0.74, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NBA-YJxjuCkM for <ietf-nomcom@core3.amsl.com>; Tue, 31 Mar 2009 15:20:51 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 6F0733A6AD8 for <ietf-nomcom@ietf.org>; Tue, 31 Mar 2009 15:20:51 -0700 (PDT)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1LomL714gB-000fka; Tue, 31 Mar 2009 18:21:50 -0400
Message-ID: <802A89216BB2497B846B0364BD33C01F@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "NomComDiscussion" <ietf-nomcom@ietf.org>
Date: Tue, 31 Mar 2009 17:21:32 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX18BxJlZWif6+/tFYX6iFkQfgq24l4m4zQvgfzw Fw2kwPG6ZCrr2i4m8vr58nXTORT9AvaCpFbVyj2oyhPDWw3cGY Ql28tQas5jzI/3peDxdyGw2FWjhBIlzdfVPgtkziDY=
Subject: [ietf-nomcom] "Lobbying"
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2009 22:20:52 -0000

So ... Russ will be posting the notes from last Wednesday's plenary, but I'd 
like to kick off one topic where I'm not excited about the direction we 
might be going... this was the only hum that surprised me.

Russ gets to make the consensus calls, but I'm pretty sure that I saw more 
people humming for "saying something about what is acceptable NomCom 
behavior", than humming against it, during discussion of 
http://tools.ietf.org/html/draft-dawkins-nomcom-openlist-02.

I'm pretty sure that we do have some community norms that nominees might 
thank us for pointing out ("sending out e-mail that says Company X endorses 
Candidate Y is, at best, unproductive and might be counterproductive"), but 
I'm concerned that trying to specify what is/is not acceptable NomCom 
behavior in some detail probably underestimates the ability of IETF 
participants to devise unacceptable behaviors...

:-(

As author (on an individual draft), I was OK with just assuming that the 
community could provide appropriate back pressure (unacceptable NomCom 
behaviors are counterproductive and don't work), but am now wondering if the 
concern is that people may devise behaviors that aren't acceptable, BUT SEEM 
TO WORK? If that's the concern, I can go there, too, but if it's not, I'd 
rather not try to specify acceptable behavior in a lot of detail.

Thoughts?

Thanks,

Spencer 



From fred@cisco.com  Tue Mar 31 15:36:11 2009
Return-Path: <fred@cisco.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B9163A6A4A for <ietf-nomcom@core3.amsl.com>; Tue, 31 Mar 2009 15:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.365
X-Spam-Level: 
X-Spam-Status: No, score=-106.365 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nku61Xdj--vW for <ietf-nomcom@core3.amsl.com>; Tue, 31 Mar 2009 15:36:10 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 7A04C3A67B4 for <ietf-nomcom@ietf.org>; Tue, 31 Mar 2009 15:36:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.39,304,1235952000"; d="scan'208";a="69780828"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-5.cisco.com with ESMTP; 31 Mar 2009 22:37:10 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n2VMbAM1017205;  Tue, 31 Mar 2009 15:37:10 -0700
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id n2VMbAb1012771; Tue, 31 Mar 2009 22:37:10 GMT
From: Fred Baker <fred@cisco.com>
To: "Spencer Dawkins" <spencer@wonderhamster.org>
In-Reply-To: <802A89216BB2497B846B0364BD33C01F@china.huawei.com>
X-Priority: 3
References: <802A89216BB2497B846B0364BD33C01F@china.huawei.com>
Message-Id: <8F582746-B9D6-4082-B122-BA37E18D5D92@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 31 Mar 2009 15:37:09 -0700
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2835; t=1238539030; x=1239403030; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[ietf-nomcom]=20=22Lobbying=22 |Sender:=20; bh=LI3Si7J2pIMeqtyiv23jkKIcx2538009SwywFthAMaE=; b=S0hVUF9Je5HFLpNRI4M6a0wrUxsPylnH0jIOLS1PC/QDxoNx0NP3F9yySm bMCtWxVf5dzBpYlK9b78ehshgmlTrFSbJ/OIhJTlFmfcIIHaGh2ZN96eA1D8 oB/SXULFaV;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: NomComDiscussion <ietf-nomcom@ietf.org>
Subject: Re: [ietf-nomcom] "Lobbying"
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2009 22:36:11 -0000

My general observation in law is that we don't define what is "good",  
we define what is "bad". What is not "bad" is arguably "good", and if  
we discover that we missed a point we pass a new law.

The counterpoint to that is the Scout Law: (http://www.scouting.org/Media/FactSheets/02-503a.aspx 
). I have visions of having folks in the plenary raise their right  
hands and say "An IETF participant is trustworthy, loyal, ..."

I like the idea of specifying the goal and shunning those that are  
clearly not headed in that direction. If I were to recommend anything  
of that ilk, I would find myself talking about the Golden Rule and  
corporate policy - if you would like to be treated a certain way  
yourself, act that way, and if you company would not find it  
acceptable for you to act a certain way toward its CEO, don't treat  
other IETFers that way.

Like you, I don't relish the thought of outlawing hot-button-du-jour.  
Do we need a dress code, for example? "Only folks wearing Birkenstocks  
may enter the room; ties will be cut off at the door and nailed to the  
wall".

Ugg. No, Uggs.

On Mar 31, 2009, at 3:21 PM, Spencer Dawkins wrote:

> So ... Russ will be posting the notes from last Wednesday's plenary,  
> but I'd like to kick off one topic where I'm not excited about the  
> direction we might be going... this was the only hum that surprised  
> me.
>
> Russ gets to make the consensus calls, but I'm pretty sure that I  
> saw more people humming for "saying something about what is  
> acceptable NomCom behavior", than humming against it, during  
> discussion of http://tools.ietf.org/html/draft-dawkins-nomcom-openlist-02 
> .
>
> I'm pretty sure that we do have some community norms that nominees  
> might thank us for pointing out ("sending out e-mail that says  
> Company X endorses Candidate Y is, at best, unproductive and might  
> be counterproductive"), but I'm concerned that trying to specify  
> what is/is not acceptable NomCom behavior in some detail probably  
> underestimates the ability of IETF participants to devise  
> unacceptable behaviors...
>
> :-(
>
> As author (on an individual draft), I was OK with just assuming that  
> the community could provide appropriate back pressure (unacceptable  
> NomCom behaviors are counterproductive and don't work), but am now  
> wondering if the concern is that people may devise behaviors that  
> aren't acceptable, BUT SEEM TO WORK? If that's the concern, I can go  
> there, too, but if it's not, I'd rather not try to specify  
> acceptable behavior in a lot of detail.
>
> Thoughts?
>
> Thanks,
>
> Spencer
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom


From danny@tcb.net  Tue Mar 31 15:38:16 2009
Return-Path: <danny@tcb.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF3343A6869 for <ietf-nomcom@core3.amsl.com>; Tue, 31 Mar 2009 15:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.166
X-Spam-Level: 
X-Spam-Status: No, score=0.166 tagged_above=-999 required=5 tests=[AWL=-1.131,  BAYES_40=-0.185, DNS_FROM_RFC_BOGUSMX=1.482]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Liim00JIDlD for <ietf-nomcom@core3.amsl.com>; Tue, 31 Mar 2009 15:38:16 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 1A70C3A6860 for <ietf-nomcom@ietf.org>; Tue, 31 Mar 2009 15:38:16 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id A610A26866A; Tue, 31 Mar 2009 16:39:15 -0600 (MDT)
Received: from jchouinard-sim-102.eng.ellacoya.com (97-122-114-19.hlrn.qwest.net [97.122.114.19]) (authenticated-user danny) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Tue, 31 Mar 2009 16:39:15 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=97.122.114.19; client-port=63744; syn-fingerprint=65535:55:1:64:M1408,N,W3,N,N,T,S; data-bytes=0
From: Danny McPherson <danny@tcb.net>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <8F582746-B9D6-4082-B122-BA37E18D5D92@cisco.com>
X-Priority: 3
References: <802A89216BB2497B846B0364BD33C01F@china.huawei.com> <8F582746-B9D6-4082-B122-BA37E18D5D92@cisco.com>
Message-Id: <9AFED4BC-20D7-4A5C-9FCB-2BC62F286ADE@tcb.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 31 Mar 2009 16:39:14 -0600
X-Mailer: Apple Mail (2.930.3)
Cc: NomComDiscussion <ietf-nomcom@ietf.org>
Subject: Re: [ietf-nomcom] "Lobbying"
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2009 22:38:16 -0000

On Mar 31, 2009, at 4:37 PM, Fred Baker wrote:

> Like you, I don't relish the thought of outlawing hot-button-du- 
> jour. Do we need a dress code, for example? "Only folks wearing  
> Birkenstocks may enter the room; ties will be cut off at the door  
> and nailed to the wall".

Agreed, me either...

-danny

