IETF Logo Mail Archive

Re: Report out from the NomCom 2016-2017

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 27 March 2017 21:17 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 924B3129690; Mon, 27 Mar 2017 14:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ngfzQJ7n9fm9; Mon, 27 Mar 2017 14:17:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7646312968D; Mon, 27 Mar 2017 14:17:07 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 75224200A3; Mon, 27 Mar 2017 17:40:55 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9208D636E0; Mon, 27 Mar 2017 17:17:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
CC: tools-discuss@ietf.org
Subject: Re: Report out from the NomCom 2016-2017
In-Reply-To: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
References: <149064625785.30521.6221370793035045425.idtracker@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
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-sha256"; protocol="application/pgp-signature"
Date: Mon, 27 Mar 2017 17:17:06 -0400
Message-ID: <10254.1490649426@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dWdaQhRoG_7MqUpCi096ewL5Vzw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 27 Mar 2017 21:17:30 -0000

NomCom Chair 2016 <nomcom-chair-2016@ietf.org> wrote:
    > - Check your status to volunteer for the NomCom --
    > https://www.ietf.org/registration/nomcom.py -- and work with AMS to
    > update your records as needed -- if you qualify, check the NomCom
    > Volunteer box when your register

Maybe these two steps could be combined, and one's nomcom eligility placed
on your registration receipt...



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email