Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
John C Klensin <john-ietf@jck.com> Wed, 22 August 2012 11:16 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379BF21F861B for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 04:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level:
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-1eYyuY29qH for <ietf@ietfa.amsl.com>; Wed, 22 Aug 2012 04:16:02 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 90DAE21F84CD for <ietf@ietf.org>; Wed, 22 Aug 2012 04:16:02 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1T48uf-000LJk-Dr; Wed, 22 Aug 2012 07:15:53 -0400
Date: Wed, 22 Aug 2012 07:15:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: Some thoughts about draft-leiba-3777upd-eligibility-02.txt
Message-ID: <F6CE6B7895D4FCF5B9F8AB5D@JcK-HP8200.jck.com>
In-Reply-To: <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
References: <133201cd7f85$325f59a0$971e0ce0$@olddog.co.uk> <ABDF3549-3C24-4AD5-985C-5E1560A80D83@gmail.com> <CALaySJ+nogfk2n8u10PyaBLOhytnsXtB7Cj+DNBFaO7r4BJ3Jg@mail.gmail.com> <7FE6283A-6066-497B-9767-3E09D18F952B@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: draft-leiba-3777upd-eligibility@tools.ietf.org, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Aug 2012 11:16:03 -0000
--On Tuesday, August 21, 2012 15:10 -0700 Bob Hinden <bob.hinden@gmail.com> wrote: >> In particular: should bullet 15,2 (and its supporting text >> elsewhere) be removed? > > 15,2 should probably say "People employed in the IETF > Secretariat….". > > I would leave it in. My thinking is that the IESG, IAB, and > IAOC have oversight roles over the Secretariat and RFC Editor. > Having people employed by these organizations be directly > involved in the selection of the IESG, IAB, and IAOC would be > odd. Bob, There is a slippery slope of trying to make hair-splitting rules here that I've very reluctant to see the community to start down. However, if one were trying to write such rules based on real risk of inappropriate behavior --rather than leaving those risks in place and focusing on the appearance of oddity-- it seems to me that the focus might better be on those who bid on or obtain short-term contracts to do specific work, such as specification-writing or implementation, for the IETF. Precisely because they are short-term (in both the RFP-> Contract Award -> Performance period) and because they apparently often involve working much more closely with a few IAOC or IESG members (although I'm not aware of its being done in recent years, presumably anyone hired by the IAB to write a workshop report would be in the same category), those contractors have much more potential for "you scratch my back, I'll scratch yours" relationships than individuals who are not subject to direct supervision from the I* leadership. I want to stress that I'm not aware of even the suspicion of anything improper occurring in this area in the past. I continue to believe that we would be better off with general guidance that people who are significantly dependent financially on the IETF via ISOC or equivalent funding for IETF activities should avoid volunteering for the Nomcom than with trying to establish rules that are exactly right and avoid all loopholes in them. In practice, I'm much more concerned about the potential for companies (or closely-aligned groups of companies) to "pack" the Nomcom than I am for abuse from groups of people who have generally avoided volunteering for the Nomcom in the past. But, if we need to try to write precise rules, let's try to identify and sweep in all of the important cases, not just obvious ones with bad optics but little practical risk. best, john john
- Re: Some thoughts about draft-leiba-3777upd-eligi… Bob Hinden
- Some thoughts about draft-leiba-3777upd-eligibili… Adrian Farrel
- Re: Some thoughts about draft-leiba-3777upd-eligi… Barry Leiba
- Re: Some thoughts about draft-leiba-3777upd-eligi… Donald Eastlake
- RE: Some thoughts about draft-leiba-3777upd-eligi… Adrian Farrel
- Re: Some thoughts about draft-leiba-3777upd-eligi… Barry Leiba
- Re: Some thoughts about draft-leiba-3777upd-eligi… Barry Leiba
- Re: Some thoughts about draft-leiba-3777upd-eligi… S Moonesamy
- Re: Some thoughts about draft-leiba-3777upd-eligi… Bob Hinden
- Re: Some thoughts about draft-leiba-3777upd-eligi… Barry Leiba
- Re: Some thoughts about draft-leiba-3777upd-eligi… John C Klensin
- Re: Some thoughts about draft-leiba-3777upd-eligi… Margaret Wasserman