[DNSOP] Fwd: Third (and final) NomCom 2021-2022 Call for Volunteers

Suzanne Woolf <suzworldwide@gmail.com> Fri, 18 June 2021 18:38 UTC

Return-Path: <suzworldwide@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 99EC63A1DF5 for <dnsop@ietfa.amsl.com>; Fri, 18 Jun 2021 11:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Kpx3vTOCtK3N for <dnsop@ietfa.amsl.com>; Fri, 18 Jun 2021 11:38:35 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A80BB3A1DF2 for <dnsop@ietf.org>; Fri, 18 Jun 2021 11:38:35 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id q16so13202409qkm.9 for <dnsop@ietf.org>; Fri, 18 Jun 2021 11:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:references:to:date; bh=OuduZ5NtbAUcae06FnpMjt5vTfLNmkH3Hrz3Lyxv9Gg=; b=Ttrlq+C5UpqTLOOBuwYjfQdxLEZGFUX/JNUQFSLmH32QkbMCJYScUPodiNB99EglnS KC3LpxRH8KMfJzmpxv4z1VcQEp4ad188LthVDSWEx7Kw40MD5HiuIaJqzePPHrSXFoO4 vsvgskhFcKFsWo7noLWkjePDUYv+0f7GHUI0+U0DSYiz950ON8Mo7kDKGLYsBiKqIeRb +/Ju80H3nyyD/Pp353IgsyGJC10aNPi2H5WYxo6r7EEcWC+CATl55TcxSnGY5OsIRbgX 36XaCHT8FbRb0re8xrqa31pNSJcoTAZrjHStR3m4ejJUPxKkyXFwofTMzt3uTJihdXUh wOaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:references :to:date; bh=OuduZ5NtbAUcae06FnpMjt5vTfLNmkH3Hrz3Lyxv9Gg=; b=JImfmlx3Xb1OvuslJ+oawk2as02zhVlOE8jUEpojBLijqf/RH7hOBM8HQUp6AJBVYc UaOBck692HRdyUX/X+bB/MNBrg2Gx1xvmsx21QKfTAVDvpekd8IOI7dvEQO4u3chQjAn ShmmiNj3o2zwW1Tmm0PKB+IXeSHYAtsNnj7kauZwSz20WmR3MHJLfNIheA0sl4eEjURt NSgvF9MyATw8KKUqdsb8WA0uDhdtmYNoRvjWZfelFkTq5/2zUvlrIK1F3cx9PjBvVsRK 4bfJMdy6WTQaPebGpwYi+U8E5KGLAvTerVc2Tn7artTxKidnDUzcduBzmJx4KSk5DAGx zANA==
X-Gm-Message-State: AOAM532vcEIqDP6TyLJVDWoyeC3sxaPd5zt2aWoePqVFbl5O9nDJhbDP tPGZG+R5gsAcCGgyO6YNMxgFv6uvDnGWtA==
X-Google-Smtp-Source: ABdhPJxj7VBFAGyFSH9D8rvZs/iqaIpjYiwipiQYeN/I2hCBFsBbqPxlvMvUL7EXt7knFr/3UsQyHA==
X-Received: by 2002:a05:620a:4e9:: with SMTP id b9mr10450430qkh.358.1624041513682; Fri, 18 Jun 2021 11:38:33 -0700 (PDT)
Received: from ?IPv6:2601:181:c381:9400:f8aa:2872:31e8:f709? ([2601:181:c381:9400:f8aa:2872:31e8:f709]) by smtp.gmail.com with ESMTPSA id o12sm4579442qki.44.2021. for <dnsop@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Jun 2021 11:38:33 -0700 (PDT)
From: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E48356EF-9BA3-421C-93D8-C6C640F19524"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Message-Id: <8996A979-BB13-487E-A088-B02F27D14476@gmail.com>
References: <162381885123.7148.341152773218568442@ietfa.amsl.com>
To: dnsop@ietf.org
Date: Fri, 18 Jun 2021 14:38:29 -0400
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/aPcT8uM9gFo5AeAkBYO7qWLU97s>
Subject: [DNSOP] Fwd: Third (and final) NomCom 2021-2022 Call for Volunteers
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2021 18:38:41 -0000

If you’ve got opinions about how the IETF is run, and want to influence its priorities and leaders, please consider adding your name to the pool of potential Nomcom members. 

The deadline to volunteer for the 2021-2022 Nomcom is next Wednesday.

See Gabriel’s email below for details, but for those of you who have volunteered before, it’s even easier now— go to the datatracker page, https://datatracker.ietf.org/nomcom/volunteer <https://datatracker.ietf.org/nomcom/volunteer>, or send email to the chair.


> Begin forwarded message:
> From: NomCom Chair 2021 <nomcom-chair-2021@ietf.org>
> Subject: Third (and final) NomCom 2021-2022 Call for Volunteers
> Date: June 16, 2021 at 12:47:31 AM EDT
> To: "IETF Announcement List" <ietf-announce@ietf.org>
> Cc: ietf@ietf.org
> Reply-To: ietf@ietf.org
> Do you want to understand and influence how the IETF leadership is elected? 
> Discuss with the candidates their visions for the different roles, and vote 
> (yes, we vote) on those you believe will benefit the IETF and the Internet 
> the most? 
> Volunteer for the NomCom 2021-2022!
> This is the third and final call for volunteers for the 2021-2022 NomCom. 
> We are only one week away from the end of the volunteer period.
> One click is all it takes to volunteer for NomCom 2021-2022:
> https://datatracker.ietf.org/nomcom/volunteer
> This "volunteer" page will let you volunteer for NomCom 2021-2022 or 
> show you if you have already volunteered.
> It is also reachable via your profile page:
> https://datatracker.ietf.org/accounts/profile/
> …where you will now see a button to volunteer (taking you to the "volunteer" 
> page above) or a message letting you know if you have already volunteered.
> - Of course, you can volunteer by sending me a very short 3 line email 
>   (see below). 
> - Thanks to everyone who has volunteered so far. However, we currently 
>   only have 83 volunteers. 
> We need many more. So, please, please volunteer.
> --------------------------------
> The IETF NomCom appoints people to fill the open slots on the IETF LLC,
> IETF Trust, the IAB, and the IESG.
> Ten voting members for the NomCom are selected in a verifiably random
> way from a pool of volunteers. The more volunteers, the better chance we
> have of choosing a random yet representative cross section of the IETF
> population.
> The details of the operation of the NomCom can be found in BCP 10 (RFC
> 8713). RFC 3797 details the selection algorithm.
> Special for this year RFC 8989 (one-off update to RFC 8713 / BCP 10)
> tells us who is eligible to volunteer as anyone who satisfies any of the
> three following conditions:
> 	Path 1: The person has attended 3 out of the last 5 IETF meetings,
> 	including meetings held entirely online. For the 2021-2022 NomCom, 
> 	the meetings concerned will be IETF 106, 107, 108, 109, and 110
> 	Path 2: The person has been a Working Group Chair or Secretary within
> 	the 3 years prior to the day the first call for NomCom volunteers is sent 
> 	to the community
> 	Path 3: The person has been a listed author or editor (on the front
> 	page) of at least two IETF Stream RFCs within the last 5 years prior to 
> 	the day the call for NomCom volunteers is sent to the community. An 
> 	Internet-Draft that has been approved by the IESG and is in the RFC 
> 	Editor queue counts the same as a published RFC, with the relevant date being
> 	the date the draft was added to the RFC Editor queue. 
> [Normative details are in RFC8989.]
> You can check your eligibility at: https://datatracker.ietf.org/accounts/profile/ 
> …where you will now see a button to volunteer (taking you to the "volunteer" page above) 
> or a message letting you know if you have already volunteered.
> If you qualify, please volunteer by clicking on the volunteer button. Alternatively,
> You can volunteer by sending me an email as explained below. However, please
> remember that anyone appointed to this NomCom will not be considered as
> a candidate for any of the positions that the 2021-2022 NomCom is
> responsible for filling.
> Details of Positions to Be Filled (some details to be finalized)
> An asterisk (*) next to a person's name indicates they do not intend to accept renomination.
> LLC Board (3-year term)
> • Jason Livingood
> IETF Trust (3-year term)
> • Kathleen Moriarty
> IAB (2-year term) 
> • Ben Campbell     
> • Cullen Jennings
> • Mirja Kühlewind
> • Jared Mauch
> • Tommy Pauly
> • Jiankang Yao     
> IESG (2-year term)
> • Murray Kucherawy, ART AD
> • Erik Kline, INT AD
> • Robert Wilton, OPS AD
> • Martin Vigoureux, RTG AD
> • Benjamin Kaduk, SEC AD *
> • Martin Duke, TSV AD
> The primary activity for this NomCom will begin in July 2021 and should
> be completed by January 2022.  The NomCom will have regularly scheduled
> conference calls to ensure progress. There will be activities to collect
> requirements from the community, review candidate questionnaires, review
> feedback from community members about candidates, and talk to
> candidates.
> While being a NomCom member does require some time commitment it is also
> a very rewarding experience.
> As a member of the NomCom it is very important that you be willing and
> able to attend meetings either remotely or in-person during IETF 112
> (Madrid 6-12 November 2021) to conduct interviews. Remote attendance
> will be supported whether or not there are in-person meetings.
> Orientation and setting of the NomCom schedule will be done by
> videoconference during the week 26-30 July (exact time and date to be
> determined after NomCom membership is finalized on July 15), prior to
> IETF 111. 
> Please volunteer by sending me an email before 23:59 UTC on Wednesday
> June 23, 2021, as follows:
> To: nomcom-chair-2021@ietf.org
> Subject: NomCom 2021-22 Volunteer
> Please include the following information in the email body:
> Your Full Name:
>    // as you write it on the IETF registration form
> Current Primary Affiliation:
>    // Typically what goes in the Company field
>    // in the IETF Registration Form
> Emails: 
>   // Email addresses used to register for the past 5 IETF meetings
>   // Preferred email address first
> You should expect an email response from me within 5 business days
> stating whether or not you are qualified.  If you don't receive this
> response, please re-send your email with the tag "RESEND"" added to the
> subject line.
> If you are not yet sure if you would like to volunteer, please consider
> that NomCom members play a very important role in shaping the leadership
> of the IETF.  Questions by email or voice are welcome. Volunteering for
> the NomCom is a great way to contribute to the IETF!
> You can find a detailed timeline on the NomCom web site at:
>    https://datatracker.ietf.org/nomcom/2021/
> Within the next few weeks, I may add more details on the timeline, as
> well as details of the randomness seeds to be used for the RFC 3797
> selection process.
> Thank you!
> Gabriel Montenegro
> nomcom-chair-2021 at ietf dot org
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce