Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice

Ted Hardie <ted.ietf@gmail.com> Thu, 27 September 2012 18:41 UTC

Return-Path: <ted.ietf@gmail.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 0FAC821F8658 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:41:24 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ynQggny3rCx for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:41:23 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6FABB21F8671 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:41:23 -0700 (PDT)
Received: by vcbfl11 with SMTP id fl11so2588687vcb.31 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BKqG+d08O/gUAZMHR3q80c58fmTO0pWLqyeBMLr8ITA=; b=JHnkJofVNsh3OJKmH9BZxKEWKOp9T6B6Zzu+WcD3GKk+iTI6UD/6CNk2I8GpAuQL2r 1utErkTOYKNXtJjbhmutdxtA+cz2zF0BoBsuTC3B7yoAGNDF7VpgMXQ3aiqck1gaMM32 1VROpl5fMA2DTDVvp4lTlrAe9bdAsSHcYP1ZbeNk1zQkp4xnoSYB6QlohoD+sWADkkP/ yu/tqAklxjLMezbsT+YhlIRnd0DKokkMEH5wK0uW9oVT0ot04K/uJ0jSyb8mGJwjA0lp IafPWAo43jACxorwsr++th8pc/3D3A1xmZELTuvOKVszt+i+58sT6xJwBl7tqUYBrlK6 z/3Q==
MIME-Version: 1.0
Received: by 10.220.238.148 with SMTP id ks20mr2727679vcb.5.1348771282598; Thu, 27 Sep 2012 11:41:22 -0700 (PDT)
Received: by 10.58.245.39 with HTTP; Thu, 27 Sep 2012 11:41:22 -0700 (PDT)
In-Reply-To: <50649932.6050801@bbiw.net>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com> <50647C77.5070805@dcrocker.net> <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@vigilsec.com> <50649932.6050801@bbiw.net>
Date: Thu, 27 Sep 2012 11:41:22 -0700
Message-ID: <CA+9kkMDVOevcpzejaMsj5+Y=j9j7-XGW6W1PBTxJiGdqOG4UEw@mail.gmail.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
From: Ted Hardie <ted.ietf@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: 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: Thu, 27 Sep 2012 18:41:24 -0000

On Thu, Sep 27, 2012 at 11:21 AM, Dave Crocker <dcrocker@bbiw.net> wrote:

>
> So, to provide a specific example, you would be OK with having someone from
> AMS on Nomcom?
>
>
> d/
>

If they met the NomCom eligibility requirements by being a _registered
attendee_ for the requisite number of meetings, then yes.  After all,
they operate an organization that uses some of the protocols we
develop and might have technical input into working groups related to
the web, or authorization, or messaging; in those cases they might
well choose to attend and participate as individual technical
contributors.  If they attend only as staff, then I don't think the
situation is the same, and perhaps we need to clarify 3777 to say that
the confirmation of attendance include a confirmation of registration
(though I have always assumed this was included in the confirmation of
eligibility).

As you may recall, when Neustar provided this service we had other
folks from Neustar who remained technical contributors (and held IETF
leadership positions).  I honestly don't recall if any of them served
on the NomCom as well, but a blanket prohibition on Neustar folks
serving would have seemed wrong to me at that point.

regards,

Ted Hardie