[RSSAC Caucus] Nomination Period: RSSAC Delegate to the ICANN Nominating Committee

Wed Apr 3 18:30:54 UTC 2024

Erum,

The Nomcom selects people to serve on the upper management levels of the
ICANN system, i.e. the board of directors, the GNSO Council, etc.  Your
experience with the technology and operations of key parts of the Internet
is clear and admirable.  How much experience do you have evaluating
directors of $150MM+/yr, 400 person organizations?

Thanks,

Steve

On Wed, Apr 3, 2024 at 2:21 PM Erum Welling <erumwelling at gmail.com> wrote:

> Dear fellow RSSAC Caucus members,
>
>
>
> I would like to nominate myself for the RSSAC Delegate position to the
> 2025 ICANN Nominating Committee (NomCom). My background is DNS and other
> technology and policy hands-on and leadership roles. For the last 10+ years
> I have worked with ICANN and RSSAC, promoting and supporting a
> multistakeholder and collaborative approach to the DNS/internet governance.
> Most recently, I have been actively engaging in and contributing to the
> work efforts of the RSSAC GWG, RSSAC Caucus Security Incident Reporting
> Working Party, and the ICANN Continuous Improvement Program/Community
> Coordination Group (CIP CCG). I feel I am ready to serve as the RSSAC
> Delegate, working in partnership with all of you. I hope you will kindly
> support my nomination.
>
>
>
> Best regards,
>
>
>
> Erum Welling
>
> On Tue, Apr 2, 2024 at 6:26 AM Ozan Sahin <ozan.sahin at icann.org> wrote:
>
>> Dear RSSAC Caucus members,
>>
>>
>>
>> It is time to begin the selection process for the RSSAC Delegate to the
>> 2025 ICANN Nominating Committee (NomCom). The role is a one-year term
>> beginning at the conclusion of the Annual General Meeting to be held during
>> ICANN81 in November 2024. Please refer to this page
>> <https://www.icann.org/nomcom2024> for more information about
>> the Nominating Committee. I have also copied below the relevant sections
>> from “RSSAC000v8: Operational Procedures” for your reference.
>>
>>
>>
>> With this notice, a four-week nomination period via this distribution
>> list is now open. Nominations or self-nominations will be accepted and
>> require a second. Nominees must then accept or decline their nomination and
>> may provide a statement with more context for their decision. The
>> nomination period will close at *23:59 UTC on Monday, 2**9 April 2024*.
>> The RSSAC will then consider the slate of candidates during its May
>> teleconference.
>>
>>
>>
>> As you may recall, ICANN Board approved some of the recommendations
>> coming from the second organizational review of the ICANN NomCom and
>> updated the ICANN Bylaws in October 2023. As a result, RSSAC appointee to
>> the 2025 NomCom will be a voting delegate. In addition, NomCom delegates
>> will serve two-year terms moving forward; *however, RSSAC is among the
>> groups that will start with a one-year term in 2025 NomCom for the purposes
>> of staggering delegate terms* - see section 27.5(a)
>> <https://www.icann.org/resources/pages/governance/bylaws-en/#article27>.
>> Finally, according to the Section 27.5(d) of ICANN Bylaws, “no person who
>> served either or both of the two prior Nominating Committees (with terms
>> ending at the ICANN Annual General Meeting in 2023 and 2024) is eligible
>> for appointment to the Nominating Committee term commencing at the
>> conclusion of the ICANN Annual General Meeting in 2024.” RSSAC appointed
>> Hiro Hotta and Naveed bin Rais to 2023 and 2024 ICANN NomCom,
>> respectively. Naveed’s one-year term will conclude by ICANN81, the
>> Annual General Meeting.
>>
>>
>>
>> The RSSAC Leadership appreciates your consideration. Please do not
>> hesitate to contact the RSSAC Chair and Vice Chair or support staff with
>> any questions or concerns.
>>
>>
>>
>> Best,
>>
>> Ozan Sahin on behalf of
>>
>> Jeff Osborn, RSSAC Chair and Ken Renard, RSSAC Vice Chair
>>
>>
>>
>>
>>
>> *1.2.7.6 Outgoing RSSAC Delegate to the ICANN Nominating Committee*
>>
>>
>>
>> The outgoing RSSAC Delegate to the ICANN Nominating Committee is
>> specified in the ICANN Bylaws. The term for the outgoing RSSAC Liaison to
>> the ICANN Nominating Committee shall be two years. No individual may serve
>> as a delegate for more than two terms. In addition, no individual may serve
>> in consecutive terms. An individual will only be eligible to serve a second
>> term as a delegate on the Nominating Committee if a minimum of two years
>> has elapsed between the end of their term and the beginning of the term for
>> which they are being selected. The RSSAC must elect the outgoing RSSAC
>> Liaison to the ICANN Nominating Committee according to the outgoing RSSAC
>> liaisons election procedure (Section 1.2.7.9) from the members of the RSSAC
>> Caucus. The outgoing RSSAC Liaison to the ICANN Nominating Committee acts
>> as a conduit between the RSSAC and the ICANN Nominating Committee reporting
>> on matters that need to be coordinated or communicated between the two
>> bodies. The role requires discretion, management skills, and considerable
>> time commitment.
>>
>>
>>
>> *1.2.7.9 Outgoing RSSAC Liaison Election Procedure*
>>
>>
>>
>> One month prior to each election, nominations will be accepted for the
>> outgoing liaison position and announced on the RSSAC distribution list.
>> During the meeting that includes election of an outgoing liaison position
>> on its announced agenda, additional nominations will be accepted, and all
>> nominees will indicate their intentions: to accept or to decline their
>> nomination.
>>
>> The RSSAC uses ranked choice voting, as outlined in Section 1.4.3 for
>> electing outgoing liaison positions. In the event that only one candidate
>> is standing for election, the RSSAC may elect the new outgoing liaison by
>> acclamation.
>>
>> The RSSAC Chair will forward the name of the outgoing liaison-elect to
>> the reciprocating body.
>>
>> If a vacancy exists in an outgoing liaison role, the RSSAC will elect a
>> new outgoing liaison through this process.
>>
>>
>> _______________________________________________
>> rssac-caucus mailing list
>> rssac-caucus at icann.org
>> https://mm.icann.org/mailman/listinfo/rssac-caucus
>>
>> _______________________________________________
>> By submitting your personal data, you consent to the processing of your
>> personal data for purposes of subscribing to this mailing list accordance
>> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
>> the website Terms of Service (https://www.icann.org/privacy/tos). You
>> can visit the Mailman link above to change your membership status or
>> configuration, including unsubscribing, setting digest-style delivery or
>> disabling delivery altogether (e.g., for a vacation), and so on.
>>
> _______________________________________________
> rssac-caucus mailing list
> rssac-caucus at icann.org
> https://mm.icann.org/mailman/listinfo/rssac-caucus
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.

-- 
Sent by a Verified
[image: Sent by a Verified sender]
<https://wallet.unumid.co/authenticate?referralCode=tcp16fM4W47y>
sender
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/rssac-caucus/attachments/20240403/3b81e11c/attachment-0001.html>