Position Description for ALAC Members and ALAC Liaisons

*1.0 Nominees for membership in the At-Large Advisory Committee, as well as those seeking a position as an ALAC Liaison, should be accomplished persons of integrity, objectivity, sound judgment and intelligence who have:*

1.1 A commitment to ICANN's mission and its core values as expressed in the ICANN Bylaws;

1.2 An understanding of the potential impact of ICANN decisions on the global Internet-using community, and the Internet end-user community in particular.

1.3 An understanding of the Domain Name System (DNS) and the basics of IP addressing. This is not to say that candidates should be technical DNS experts, but a minimal understanding of the DNS is needed to effectively function on the ALAC. For example, candidates for the ALAC should know the answer to a question such as "Do you know what happens in the DNS when you send an email, or access a webpage?" This requires an understanding of the general process of name resolution.

1.4 Demonstrated capacity for thoughtful group decision-making and sound judgment, and a track record of working to build consensus with a diverse set of interests working together on complex policy issues.1.5 ALAC members and liaisons, along with the At-Large community of which it is a part, are charged with representing the interests of the entire

1.5 billion Internet end-users of the world in ICANN’s processes. As a result, candidates for ALAC membership or a liaison post should have a demonstrated capacity to represent the views of others effectively, and generally refrain from advocating in support of personal opinions. *(AP,AG: Move to top of list. ALAC members should act as conduits in both directions) (AG,PVW,CS,CA: Remove 1.5b and soften)

*1.6 The ability to effectively chair meetings and provide leadership and support for work teams or committees.

1.7 A willingness to serve as a volunteer, without compensation other than the reimbursement of certain expenses.

1.8 In accordance with the recent ALAC review recommendations as adopted by the ICANN Board, members of ALAC must have proficiency in written and spoken English to allow the committee to function effectively and to allow ALAC members to interact effectively within the overall ICANN environment.

...

2.1 Additionally, each ALAC member leads, co-leads, or participates in one or more working groups on policy issues, which will involve an additional average 10 hours per month in reading documents, drafting proposed responses, and attending teleconferences and participating in email and other electronic correspondence related to those working groups.

*2.2 The ALAC has minimum participation requirements that all members are expected to meet, and members’ participation statistics are published for the At-Large community and the rest of ICANN to review. Expectations for participation include the following:*

2.3 Attend and actively participate in monthly ALAC teleconferences, not missing more than one-third of these meetings in any rolling six-month period; * (AG,EL,PVW,CS,CA,GS: Delete 2nd phrase)

*2.4 Participate actively in policy issues and other working groups. Each ALAC member is expected to help lead at least one working group composed of members of At-Large working on policy issues. A current listing of working group and the remit of each may be found at http://st.icann.org/working-groups. *(AG,AP,PVW: replace is expected to with will typically) (AG,AP: use more general statement) (EL,CS,GS: keep as is, add required to report at ALAC meetings) (AG: not everyone is a leader, add admin responsibilities)*

2.5 Voting regularly in ALAC ballots on various subjects (at a minimum, in ¾ of all ballots conducted). ALAC vote results are published and publication includes a record of how each member voted, excepting where the balloting relates to election of ALAC officers or liaisons. (AG,EL,AP,PVW,CS,CA,GS: Remove explicit target) (AP,AG:Vote in ALAC ballots to adopt policy statements and other work of the ALAC, and the elections of officers and other positions.} {PVW: Voting for ALAC not Liaisons)*

2.6 Attend ICANN's three face-to-face meetings each year, which generally run about 7 days with Committee members having extensive responsibilities on most days. It is understood that events may transpire to prevent attendance in person from time to time, in which case participation remotely via two-way telephonic links is strongly encouraged. There may occasionally be additional face-to-face interim meetings or regional meetings.

2.7 Reading and commenting in At-Large’s mailing lists and other communications media. *(AG,AP,PVW: ALAC and At-Large mailing lists)*

2.8 For elected ALAC members, participation at monthly teleconferences and intercessional activities of the At-Large community in the region that elected him or her is expected. For Nominating Committee-appointed ALAC members, participation in the monthly teleconferences and intercessional activities of the region the ALAC member was appointed by the NomCom for is expected. *(AG,PVW: for NomCom appointed, participation is optional but highly recommended) (EL,AP,CS,CA,GS: As is)

*2.9 ALAC Liaisons are expected to attend and participate in ALAC meetings, provide updates on their activities as liaisons, attend the meetings of the body they are a liaison to (the “receiving body”), participate effectively as an advocate for At-Large in the receiving body, and where necessary propose responses from the ALAC to the receiving body on policy or other questions. *(BB: Board liaison should not put forward personal opinions)
(PVW: ALAC and Liaison should represent ALAC, At-Large and their positions in non-ICANN environments)(AG: perhaps encourage but not require - not everyone is a salesman)

...