<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.43 (Ruby 3.2.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-rsalz-gih-nomcom-2years-00" category="bcp" consensus="true" submissionType="IETF" updates="8713" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.18.0 -->
  <front>
    <title abbrev="NomCom-2years">Two-year terms for NomCom volunteers</title>
    <seriesInfo name="Internet-Draft" value="draft-rsalz-gih-nomcom-2years-00"/>
    <author initials="G." surname="Huston" fullname="Geoff Huston">
      <organization>APNIC</organization>
      <address>
        <email>gih@apnic.net</email>
      </address>
    </author>
    <author initials="R." surname="Salz" fullname="Rich Salz">
      <organization>Akamai Technologies</organization>
      <address>
        <email>rsalz@akamai.com</email>
      </address>
    </author>
    <date year="2023" month="September" day="26"/>
    <area>General</area>
    <workgroup>GENDISPATCH Working Group</workgroup>
    <keyword>NomCom</keyword>
    <abstract>
      <?line 34?>

<t>Each year the NomCom process is actually two processes -- finding out anew
how to be a NomCom and conduct its business, and then undertaking the
work of the NomCom in selecting individuals to undertake the various roles
for which the NomCom has responsibility. This applies to both the chair and
to the voting volunteer members of the NomCom.</t>
      <t>The inclusion of the past chair into the NomCom as a non-voting member
mitigates this to some extent, but the past chair is constrained as to the
level of advice that can be offerred.  This acts an impediment to making
concrete changes for future incarnations of the Nomcom that would improve
the overall Nomcom process.</t>
      <t>The NomCom process could benefit from greater levels of continuity from year-to-year
to reduce the amount of time taken to by the new Nomcom to define its intended mode
of operation and allow the operation each incarnation of the Nomcom with a greater level
of consistency.</t>
      <t>This document changes the term of office for NomCom voting volunteers from
one to two years.  It also changes the term of office for the NomCom Chair
from two to three.</t>
    </abstract>
    <note removeInRFC="true">
      <name>Discussion Venues</name>
      <t>Source for this draft and an issue tracker can be found at
    <eref target="https://github.com/richsalz/nomcom-changes"/>.</t>
    </note>
  </front>
  <middle>
    <?line 57?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Each year the IETF Nomincations Committee ("NomCom")
process <xref target="RFC8713"/> is actually two processes -- finding out anew
how to be a NomCom and conduct its business and then secondly performing the
work of the NomCom in selecting individuals to undertake the various roles
for which the NomCom has responsibility. This applies to both the Chair and
to the voting volunteer members of the NomCom.</t>
      <t>The inclusion of the past Chair into the NomCom as a non-voting member
mitigates this to some extent, but the past Chair is constrained as to the
level of advice that can be offerred. Even with such an arrangement, the
degree with which the previous chair can advocate adoption of previously
used processes (and supporting tools) that benefit the efficient operation
of the Nomcom is limited by being a single voice within the Nomcom.
Each incarnation of the Nomcom is prone to repeating the same behaviours
each year, with only a limited opportunity to benefit from previous experience.</t>
      <t>The NomCom could benefit from greater levels of continuity from year-to-year
to assist the NomCom to get over the bootstrap period of operational process
definition each year.</t>
      <t>This document changes the term of office for NomCom voting volunteers from
one to two years.  It also changes the term of office for the NomCom Chair
from two to three.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t><xref target="RFC8713"/> documents how the IETF Nominations Committee
operates. That document refers to the meetings by ordinals; for ease of
understanding, this document uses March, July, and November instead of
First, Second, Third, respectively.</t>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="changes">
      <name>Changes</name>
      <t>The voting volunteers serve for two years.
The selection are to be staggered (see below) so that after the bootstrap
five new members are chosen each year.</t>
      <t>The NomCom chair serves for three years, each year is known as
Incoming Chair, Chair, and Past Chair.
The voting rules for Chair and Past Chair do not change.
The Incoming Chair does not vote and does not count for quorum in
Nomcom meetings.</t>
      <ul empty="true">
        <li>
          <t><strong>ISSUE</strong> Is that last sentence what we want?</t>
        </li>
      </ul>
      <ul empty="true">
        <li>
          <t><strong>GH</strong> Yes, I think so!</t>
        </li>
      </ul>
    </section>
    <section anchor="implementation">
      <name>Implementation</name>
      <t>To commence this process, the ISOC President selects an individual as the
designated Chair, and an individual as the Incoming Chair.
The order and method of selection is left to the discretion of the ISOC
President.
This document recommends that the Incoming Chair be announced before
the current chair has made any public announcements. In suceeding years the
ISOC President selects an individual as the Incoming Chair.</t>
      <t>The voting volunteers for the first year of operation of this process need to be selected in two
separate groups - five are picked for a one-year term, and five are picked
for a two-year term. In order to prevent the Chair from having undue
influence, <xref target="RFC3797"/> or its successor should be used. The seed material
for both groups can be the same, with an additional seed provided that
distinguishes them. For example, an additional lottery equivalent with
"1, 2, 3, 4, 5, 6" as the numbers for the first group and
"7, 8, 9, 10, 11, 12" as the numbers for the second group could be used.</t>
      <t>A single list of eligible volunteers is used for both volunteer groups
in the first year of operation of this process.</t>
      <t>In suceeding years the selection process will name five individuals to serve a two year
term as a Nomcom member.</t>
      <t>If someone is unwilling, unreachable, or otherwise unable to serve,
the next person for that group should be chosen.</t>
    </section>
    <section anchor="diversity-considerations">
      <name>Diversity Considerations</name>
      <ul empty="true">
        <li>
          <t><strong>RS</strong> This comes from some other correspondence and I think there
are some valid points here.</t>
        </li>
      </ul>
      <artwork><![CDATA[
I hope that proposal draft explicitly addresses the problem that,
perhaps because of the increased workload, the NomCom is already
less diverse and less representative of the community than one
might reasonably wish for.  I see it as a tradeoff, rather than
fatal but, unless there are other remedies, the longer commitment
of more time seems likely to further reduce diversity, perhaps to
the point that the typical NomCom member becomes someone with
good organizational support (perhaps from organizations/
companies with ulterior motives) and little significant
involvement in the IETF's technical work (aka "too much time on
their hands").

I don't have a strong opinion about what you should say on the
subject, but I believe not addressing the issue would be a
mistake.

]]></artwork>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The security considerations of <xref section="9" sectionFormat="of" target="RFC8713"/> are still applicable.</t>
      <t>One possible concern is that organizations with an agenda now have two years to
exercise it, and in their second year will be more competent to use their
influence with respect to that agenda. Maintaining the requirement that at
most two people can be from the same organization as defined in
<xref section="4.17" sectionFormat="of" target="RFC8713"/> should help mitigate that.</t>
      <t>In addition, since the term of office for the Chair and the voting volunteers
is being extended by a year, all will be participants in more than one
NomCom "session."
It seems obvious that this will make it harder to maintain confidentiality.
For example, a participant in years <em>N</em> and <em>N+1</em> will have to ensure
that they do not discuss <em>N+1</em> items with someone who was a participant
in <em>N</em> and <em>N-1</em>.</t>
      <ul empty="true">
        <li>
          <t><strong>GH</strong> I am not sure that the last 2 sentences are the case,</t>
        </li>
      </ul>
      <t>Note, however, that the key goal of this document is to introduce greater
continuity across NomComs.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
    <section anchor="llc-considerations">
      <name>LLC Considerations</name>
      <t>The LLC is requested to provide free registration for the NomCom Chair
(and only the current Chair) and
the voting volunteers for the November meeting as that is when most of
the candidate interviews are done.</t>
      <ul empty="true">
        <li>
          <t><strong>GH</strong> Really? If the nomcom folk need free rego to to attend an IETF then
the wheels have fallen off in my view!</t>
        </li>
      </ul>
      <ul empty="true">
        <li>
          <t><strong>RS</strong> Since most of the November meeting could be spent interviewing, for
diversity/inclusion it makes sense to me.  But TBD.</t>
        </li>
      </ul>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
      <name>Normative References</name>
      <reference anchor="RFC8713">
        <front>
          <title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</title>
          <author fullname="M. Kucherawy" initials="M." role="editor" surname="Kucherawy"/>
          <author fullname="R. Hinden" initials="R." role="editor" surname="Hinden"/>
          <author fullname="J. Livingood" initials="J." role="editor" surname="Livingood"/>
          <date month="February" year="2020"/>
          <abstract>
            <t>The process by which the members of the IAB and IESG, some Trustees of the IETF Trust, and some Directors of the IETF Administration LLC (IETF LLC) are selected, confirmed, and recalled is specified in this document. This document is based on RFC 7437. Only those updates required to reflect the changes introduced by IETF Administrative Support Activity (IASA) 2.0 have been included. Any other changes will be addressed in future documents.</t>
            <t>This document obsoletes RFC 7437 and RFC 8318.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="10"/>
        <seriesInfo name="RFC" value="8713"/>
        <seriesInfo name="DOI" value="10.17487/RFC8713"/>
      </reference>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
      <reference anchor="RFC3797">
        <front>
          <title>Publicly Verifiable Nominations Committee (NomCom) Random Selection</title>
          <author fullname="D. Eastlake 3rd" initials="D." surname="Eastlake 3rd"/>
          <date month="June" year="2004"/>
          <abstract>
            <t>This document describes a method for making random selections in such a way that the unbiased nature of the choice is publicly verifiable. As an example, the selection of the voting members of the IETF Nominations Committee (NomCom) from the pool of eligible volunteers is used. Similar techniques would be applicable to other cases. This memo provides information for the Internet community.</t>
          </abstract>
        </front>
        <seriesInfo name="RFC" value="3797"/>
        <seriesInfo name="DOI" value="10.17487/RFC3797"/>
      </reference>
    </references>
    <?line 221?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>None so far.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA9VZ7XIbtxX9j6dAmB+xVZKxbLeO1TSOLH+xY8uuJU8n0+lk
wF2QRLW7YIBdyYwneZY+S5+s51xgl6Qs92MmmWl/aChisRe4X+eeezmZTFTr
2soe6dH5lZ9srAm6taGOeuGDPvX1ia/1pa+6prU2xJEy83mwl9ienk3u8hWs
l75oTA05ZTCLdhKiqX6cLN1q0vi6GPZN7txRhWnt0ofNkZ4Xa9WtS3yPR/qr
B4f3lIrdvHYxOt+0mzWkzZ6eP1M47p5y63Ck29DF9u6dOw/v3FUmWHOkn9vG
BlOpKx8ulsF3ayw9PX0yO3tzfH7yQv8Zy65Z6ud8pC7sBvvKI6UnWTec2Jqm
/N5UvsFxGxtVrE1ov/+h83Ktxitlunblg7zlGqw9n+oXuIdvlNY6af3c+sVi
Z9WHpWncj6aFJkf6+M3p7ITLtjauOtKwy7dm3bhi2th2EPt2qs9gta3Qt65Y
DUvXJF4YiNLntlg1vvJLh4tv5Yv1vzWyZ1pQy8aHGq9e2iOlXLPY+aYmk4k2
89gGU7RKPTU4M4XByvYBsA6+sDFqFzU2daaqNrq98v26jRoyFq4paWrftdo0
9kqt/JVuvZ5bbXpBMLUufFN2RatdG/W8i66BhLE8wYmN7prShtaI17AgjtV+
sXsd1+hoK1u03MNTL12JS0We1r9u5YVLE5zvog6+goEY0lcrGnVH2MrgsY1r
30Q3d5VrN1N9vqKm63UFs4oKvk3vFCvjAu+qsCoHeLnEkCG6tvUcibJ/46lS
5/jimqLqGNv907WJbZbpmiyxtxQugOBrJvmEJFfVrnVLJgz2Orlb9LXV9n1r
m3YMe7YfCY60ON0LS5eUmw5Slb20FW9iyktX0F4G75iGDkMw2xBsOdXZFgWc
hUeuXtvS1TiLUmrxkoL4IthWrNMsbYKORdd2QVQ2oZGg3bUJYjKdd+W7qqTY
4C+t4lN8Ip+rflcOsWzBa/FYyNtzQMDCtXoR8GgJVACAadFOjsT1YMEOjk07
GNyTNmEd3Qg1uyKFi6k93Cj3hJKaYdSI/zfyGEE9XN7rEoc2VsIYzrOIu1LX
vrQKr/s1lKDSEtdQh6lA5YZ1yzzbsc4141w5RJzZ10YlZaKLOK3YiEngGyBv
Jx7pzU8xxHCKhCPp2z0w34/YKFZRgD8JDGS1IDU8P0MeV9H/O7k7QXvCiFNi
ZQqSQAvWThPI1K4sK6vU53rWtMETBKD4dcgh4lMebZPCBpIR9rirvpWrzui2
6kPgw4fP3j47YfH46adfD5+28BQtn0M+PEkY/Z+EqZNfAaZOfi2YOvklYOrp
JXwjSRM7GA6PTQgM21oOpKDSIpts2rQ17xpsRmyf0JKCcZAnScE/ft3nZr+v
2qgu4oLb0LrF2Ijdeu2DmKD1voq30z17aOJJlinjmKgDCqj9pIcNKgfTQTwQ
Z24pzWhE4LKiC6k9b4+42r40TenzaSSBUNw1ZXewa+BJDlkdQTJwyspQsRCV
7fNwnIzkG4S5Ga7kRcOuIZBK2uyg7mBF+x66QcnC7iP2L4LUJhL7dsMPi0vb
Ss2Q5bn3LWNozfR0vtS7WGyq3mtKsNttgZgn/F/h6edAxQYxnxCSEfhkUCkq
tYeKvUJRr3IZ2mLsdYhVyVo2El0QwIMxgl1Qt5z9tbXUOjJOQaghp4q/l9tb
E5mXSgBOuDX2jRMMDMI65s0rE4rVWP+xqzaJ/p3CjUQPsuHWGjpPPXMQMtZn
grpjIl7AB4GQuIrA2eQ4A7XX5PZRj169OzsfjdOnPn0t/799+qd3s7dPn/D/
sxfHL18O/6i84+zF63cvn2z/27558vrVK7QU6WWs6r0lNXp1/N0oaTB6/eZ8
9vr0+OVIS5Lu6ox2JVcbsoWwJmMiziEWYxHcHF/wzuOTN//4++H9XNbuHh4+
hAOzNw8f3MeXK1ShdJrkZ/oKn2wUKgGLKKSQPxVm7Vq4ZUwsjfB8o1c2MHYO
/kLL/PVIf40G7PD+N3mBCu8t9jbbWxSbfbzy0cvJiDcs3XDMYM299WuW3r/v
8Xd733u77yx+/agiPZscfvXoGyUJk9IuhcvHWRttuMwJOOSsbM01nFxucCEC
e7mENUt9K1qCKAjebdS4hPpogK/jkVogWIVA9pWXwoqVj/Y6BG0xUyqS3Ctm
ZGABk6uNty8R4S8a+hfBNGsKL5xEoGPcfzBc3gzFdrprgtBVWfzAGna2In5R
3nssTC/un4EdeJ97INDK68NKIXSastFOh46USOWy1CMIVP5GHxzMzs7ePT04
0LOYTFjxBrANmS6qnrQK+DRN+yi98PwFdn9nYYgZE625gPU/E25Zryup+qnC
qnMALtBN5EhG5howTkh49vpEvwGeuJJJmnydWp2BsAkZEQIR3RKICa/vmPWm
rddMlMwGcLLJvLVtV6k2bWOLtd8u2h5gSxfZU+2Uc95UDTedXqtVwSYly2y/
jy8hPLdp4JGC/MLCK6nhKjpQqKZvF8kza1NyLzhuN69cMbwmRWQKuSRZ1gqb
lmgU8/wXpvzIPp/Iyb4cLlgFUrDvNVdimq1LkV9QLWeoHJ9AFQmtol0bFjYt
QyI0BFoyklm4dsUFNvIwA1C12ylY8vC1jSptbHfHZWKU5ODWCxuSFnmg4lLC
SbSgHypjZzmEqToG5TjD+70HDx8A3iGbjQcMTI3wDdCdqBOrZsmyTOXYa5I9
OVPJfYT6Z9UyOe4pXmZzQmxLl4mQSGDT7di2MmQUQo7271xcJXICrZ6xor83
TKnxNQmVB18IG21/6Nylqagvz1Gjw7G+O9b3xvr+WP92rH836p3edAn59r0q
l5ZeZfRgrL8a64djfXgHf5BzePeTL6c+LL9d7JlIqeOeNFfki4gSW7mlmwuL
HoILcSNMfjDftjtKhlSZaP+H0Ydzb86MnSzvA/XKoUJzyJeC61pzmEqRGQqR
EpYordaAnrQGT1xIZ0W2SX0aChbC1TWBFcLM6TloCAVtuHIgZ13DxeGcsUqj
jfctOXPEJZOJTe+abQCmciXs8wmuHSKZ+gk70jLbJCZwfnsGcBaAwmVtYsSp
A5RrYDWkXrYUWGaS9SjO55az3bQfkeUQqN4JfU385eeff4biILPr3A3Cqmsf
EZMye2YPAtRyLbuXsgypS0u9nofmafI0VtB2ZZAuc1uYTkirbHIcZhkGBlv6
yptyvNfUwwsVNpQbdKbwZCmGSDrIAnosHJnqz+UgleicWydUUqIMeuTlisBt
YHN4BFQOmUfjs1VgggIIktNBIErOl0F8jdiPMtTCgN6xlaaz5WixnSBVMnMA
YpfO5lJXeVTwIDdxLaGc3WftyWk47MKBNfvPC1tJf7foQhYi47Gyd/hY94Zr
vYSOOGdbddoNYNJUvb1SpNLIEgl9sApULD2r4M5cm8CUGml9qz9FYmd3U/xS
QdYa321M0NZVREJEbe1pczTf4g00NIhz1myH5grUAQmNHL+UOqZzcrMV+gK6
cJAu95ZBzi1zYfQInbyuOU4QA4FM4AUpkSizo9vMPhTg5ouWyM58BdPzHDCt
0YiRLs45ahLusvFdn0fRoGWSs/ljx98ADGkeMiOLdJYsEcwpB27fqrsYO5uH
pazjCJ7I6VGfDZ+zQ+rCTfmY6kV+WOw9ZHB++HCWsekhv267RknBljglE6aC
oIHjXjf0OG5GDOHk1wYhL+L/PTdty84SvIRToqtkqIFfM4LsexsKwpJrU7VN
fhHiKwgvuCt4CcUlXOl92+YZNDNX9m8rajo494iJUJGUyy2maDsRrvjrTRtY
wEKKibSxVbXnmIEDROvX1DNV1NSI95OTXWWZp2keTAXU1qj3p4cP9u2aw2Bl
q7Xux2RycKoffYUds4TlsfQnhgRbvn7TiA/lK+YZkozdyjRVMnnCwxaxtyqY
UQvARErJLDuDQo9TOZFH0crvctORmrUZLfw8TX1y8rtc2GrONR3TomdEdTY6
I2Yh/BDEhTNMtc8wdq/Cm6QwOTg9EDUPTn9zeJCOSIHktW1iJzw2oc+m71fI
n7sY8yuu5W3TeLAHoJVHOxH3j2TF3x42OTyY7jQbM21qkc0Tt3gnncrdoVdJ
jZ1APorIWMF8LTRD/43UDuPtexxYLL2pBhoxcPk0MHV5Rm77QZnaGY+ZIiAH
M8ZGqciz49PjG5J/VzC5fePTTiPxmV59+fLkRtjguouSITa2iVpnzohcsMyd
pWN7K6F+4+zq1jCo2G015NntNKD+l8R/GAnldjGxQSM24uRDS6b6RWpkOGzi
r8lpwnLp7FXyBkDa7nryreUvBI/0LNXm9As1zqwuUgfR65Ymbh6IwPwhlMng
jL8DyIG4ASeXEosLiLTkhAvJoI3m8Z/t0KEzSed835uVG2gskEviP2shhA4m
UUMR/nI7o0eeMd84wGii5ERtwSAeo6ScP36Sf3qZm+KCnj4uOCmobLmUXk59
OEq82pZ/GEGDaEc/MWIbsi+oBIb5T0eObD0iIAAA

-->

</rfc>
