Re: Updating BCP 10 -- NomCom ELEGIBILITY

Michael Richardson <> Thu, 12 February 2015 02:56 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7AFB11A1B70 for <>; Wed, 11 Feb 2015 18:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tzWl6zevP6Ox for <>; Wed, 11 Feb 2015 18:56:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1830B1A1B35 for <>; Wed, 11 Feb 2015 18:56:39 -0800 (PST)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id D0F5D203CD; Wed, 11 Feb 2015 22:04:05 -0500 (EST)
Received: by (Postfix, from userid 179) id 9D6E763A21; Wed, 11 Feb 2015 21:56:37 -0500 (EST)
Received: from (localhost []) by (Postfix) with ESMTP id 7C8A4637F4; Wed, 11 Feb 2015 21:56:37 -0500 (EST)
From: Michael Richardson <>
To: Brian E Carpenter <>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
In-Reply-To: <>
References: <> <> <> <> <> <>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 11 Feb 2015 21:56:37 -0500
Message-ID: <>
Archived-At: <>
Cc: ietf <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 12 Feb 2015 02:56:43 -0000

Brian E Carpenter <> wrote:
    > For me there is an over-arching consideration: a relatively simple
    > script must be able to generate the list of all qualified volunteers
    > from existing databases. Otherwise the whole process will be
    > impractical.

I note that we have no such script today.

The nomcom chair takes a list of volunteers, and submits them to a web site
one at a time.  Then if the person isn't eligible, contacts them to find out
if they have any other emails that they registered with (such as because they
changed companies), adds that, and iterates.

Except that I wrote some perl to drive this from a CSV file, and screen
scrape the result, and I've asked that it be made into an API.

The registration database is presently not integrated into the datatracker;
the datatracker actually knows a reasonable history of people's email
addresses, or at least, if we integrated things better, then the registration
system could link things better.

One of the reasons I wrote the list the way I did is because I know that the
datatracker can generate that list; the list of attendees is actually the
hardest part to automate.

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-