<html>
<body>
Indeed, thus the last sentence of #1 and #6 as well as time requirement
to attend At-Large calls. As the EPDP runs, there will no doubt be many
details to be defined, but the overall guidance will be to look at what
maximizes the benefits to Internet users and what minimizes the potential
harms.<br><br>
Alan<br><br>
At 07/07/2018 05:38 PM, Jonathan Zuck wrote:<br>
<blockquote type=cite class=cite cite="">Ideally, there’s a phase where
the ALAC forms some consensus on positions to carry to the EPDP<br>
<br>
<b>From:</b> ALAC
[<a href="mailto:alac-bounces@atlarge-lists.icann.org" eudora="autourl">
mailto:alac-bounces@atlarge-lists.icann.org</a>] <b>On Behalf Of </b>Alan
Greenberg<br>
<b>Sent:</b> Saturday, July 7, 2018 11:54 AM<br>
<b>To:</b> ALAC <alac@atlarge-lists.icann.org><br>
<b>Subject:</b> Re: [ALAC] Consensus Call: EDPD - Proposed way
forward<br>
<br>
In #6, it should be "EPDP Members and Alternates" instead of
"ALAC Members and Alternates". Thanks to Sebastien for catching
this.<br><br>
Alan<br><br>
At 07/07/2018 12:41 AM, Alan Greenberg wrote:<br><br>
<dl>
<dd>There have been no further comments to the message I sent to the ALAC
yesterday (modified to correct two issues identified by Ricardo) on the
process associated with the selection of the GNSO Expedited Policy
Development Process (EPDP) to put policy in place to replace the
Temporary Specification for gTLD Registration Data adopted by the ICANN
Board effective 25 May 2018.<br>
<dd>I therefore am recommending, with the full support of the ALT, to use
the following process:<br>
<dd>1. Very shortly, we will send out an request for Expressions of
Interest with a very short window (48-72 hours). The EoI will be an
online GoogleDocs Form and will ask for information on the candidates
past involvement/knowledge with WHOIS issues, the ability and willingness
to participate, and understanding of the EPDP participation criteria.
Membership and participation will be on behalf of the ALAC and not
representing personal views.<br>
<dd>2. The ALAC will have access to the EoI and all Members are expected
to review the EoIs and ranks them. This is review is CONFIDENTIAL and
neither the contents of the EoIs nor the ALAC comments may be
discussed/presented outside of this group. ALAC Members will have a very
short time to review these EoI, likely 48 hours.<br>
<dd>3. The ALAC Chair, in conjunction with the ALT will summarize the
evaluations and make a final selection, ordered to allow for changes in
the final charter, ensuring that the final selection meets the overall
criteria and ensures a reasonable level of diversity and balance.<br>
<dd>4. The ALAC Chair will transmit the final selection to the GNSO
Council or GNSO Chair as appropriate as well as to the ALAC, in
sufficient time to meet the GNSO requested timeline. [CORRECTION: cc:
ALAC]<br>
<dd>5. At the time of the transmittal, the Chair will announce the number
and demographics of the applicants.<br>
<dd>6. Once the proposed ALAC Members and Alternates are selected, a
meeting will be convened of the Members and Alternates prior to the
EPDP's first meeting to ensure that everyone has the same understanding
of what we will be doing.<br>
<dd>Barring issues that elongate this process, the proposed timeline is:
<dd>- EoI issued Monday, 09 July;
<dd>- ALAC evaluation of responses begins Thursday, 12 July;
<dd>- ALT synthesis of evaluation and final selection Saturday, 14 July -
Monday, 16 July;
<dd>- Announcement and scheduling of EPDP prospective Members/Alternates
Tuesday, 17 July.
<dd>With this message, I am initiating a Consensus Call of the ALAC to
ratify the above recommendation. <br>
<dd>Due to tight time constraints, this Consensus Call will end at 23:59
UTC on Wednesday, 11 July 2018. The call for EoIs will run in parallel
with this Consensus Call, but no further action will be taken before
ratification.<br>
<dd>If there are any questions of comments, please direct them to either
this list or to me directly. <br>
<dd>Although messages indicating support are welcome, they are not
necessary. This Consensus Call will be deemed to have succeeded in the
absence of significant opposition (greater than 20% as specified by ALAC
RoP 12.3.3.1).<br>
<dd>Alan <br>
<br>
<br>
<br><br>
<dl>
<dd>Date: Thu, 05 Jul 2018 19:46:04 -0400
<dd>To: ALAC
<<a href="mailto:alac@atlarge-lists.icann.org">
alac@atlarge-lists.icann.org</a>>
<dd>From: Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
>
<dd>Subject: URGENT: EDPD - Proposed way forward<br>
<dd>As you all know, the GNSO is chartering an Expedited Policy
Development Process (EPDP) to put policy in place to replace the
Temporary Specification for gTLD Registration Data that the Board
adopted. Since the temporary specification must be replaced by 25 May
2019, the EPDP will have to proceed VERY quickly, with a draft policy
published by ICANN 63 in Barcelona (about 3 months from now).<br>
<dd>The GNSO is expected to adopt the EPDP Charter on 19 July and convene
the EPD very soon after. That is 2 weeks from today. <br>
<dd>At this point, it looks like each sub-group of the GNSO and other
AC/SOs will each have three Members and three Alternates (the Alternates
can "listen/read" but can only actively participate in the
absence of a Member). The current details can be found at
<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-epdp-membership-structure-temp-spec-27jun18-en.pdf">
https://gnso.icann.org/sites/default/files/file/field-file-attach/proposed-epdp-membership-structure-temp-spec-27jun18-en.pdf</a>
. This is subject to change before the Charter is adopted, but at this
point it is a major victory that they are discussing parity with the GNSO
groups. If this comes to be, there are a few people to whom we will owe a
huge debt of gratitude. Without doubt we will have SOME formal presence
on the EPDP which was not a certainty just a few days ago.<br>
<dd>Membership in the EPDP is expected to require up to 30 hours per
week, starting immediately and at least for the first 4 months, and
probably a lower but still significant commitment until mid-2018
[CORRECTION: 2019]. The GNSO is also setting some very specific criteria
for participation. Although the list may change, the current requirements
are appended to this message. <br>
<dd>You will recall that in Panama, we decided that the evaluation of
possible candidates is sufficiently important that it should be done at
the first level by the ALAC, but clearly we do not have a lot of time to
do so. Moreover, we will have to ensure that the selected candidates
balance skills, availability and an understanding of user issues.<br>
<dd>The ALT discussed this at our meeting on Friday and are proposing the
following path forward:<br>
<dd>1. Very shortly, we will send out an request for Expressions of
Interest with a very short window (48-72 hours). The EoI will be an
online GoogleDocs Form and will ask for information on the candidates
past involvement/knowledge with WHOIS issues, the ability and willingness
to participate, and understanding of the EPDP participation criteria.
Membership and participation will be on behalf of the ALAC and not
representing personal views.<br><br>
<dd>2. The ALAC will have access to the EoI and all Members are expected
to review the EoIs and ranks them. This is review is CONFIDENTIAL and
neither the contents of the EoIs nor the ALAC comments may be
discussed/presented outside of this group. ALAC Members will have a very
short time to review these EoI, likely 48 hours.<br>
<dd>3. The ALAC Chair, in conjunction with the ALT will summarize the
evaluations and make a final selection, ordered to allow for changes in
the final charter, ensuring that the final selection meets the overall
criteria and ensures a reasonable level of diversity and balance.<br>
<dd>4. The ALAC Chair will transmit the final selection to the GNSO
Council or GNSO Chair as appropriate as well as the ALAC, in sufficient
time to meet the GNSO requested timeline. [CORRECTION: cc: ALAC]<br>
<dd>5. At the time of the transmittal, the Chair will announce the number
and demographics of the applicants.<br>
<dd>6. Once the proposed ALAC Members and Alternates are selected, we
will need to convene a meeting of them prior to the EPDP's first meeting
to ensure that everyone has the same understanding of what we will be
doing.<br>
<dd>Barring issues that elongate this process, the proposed timeline is:
<dd>- EoI issued Monday, 09 July;
<dd>- ALAC evaluation of responses begins Thursday, 12 July;
<dd>- ALT synthesis of evaluation and final selection Saturday, 14 July -
Monday, 16 July;
<dd>- Announcement and scheduling of EPDP prospective Members/Alternates
Tuesday, 17 July.<br>
<dd>This process will be the subject of a short ALAC Consensus Call most
likely starting Friday (tomorrow for me). The Consensus call will overlap
with the EoI submission process.<br>
<dd>Alan<br>
<dd>========================<br><br>
<dd>EPDP Charter Membership Criteria
<dd>Have sufficient and appropriate motivation, availability and
expertise to participate in the substance of the work of the EPDP Team.
Appropriate experience could, for example, include experience with the
previous RDS/WHOIS policy development processes, task forces, or
implementation review teams, or participation in EWG efforts;
<dd>Commit to abide by the EPDP Team Commitment Statement, and to accept
the consequences of non-compliance as may be determined by the EPDP
leadership or appointing group;
<dd>Commit to build consensus on issues within the scope of this EPDP;
<dd>Commit to actively participate in the activities of the EPDP on an
on-going and long-term basis, for a period of no less than one-year, with
the highest intensity expected in the first six to eight months;
<dd>Solicit and communicate (where appropriate) the views and concerns of
individuals in the group that appoints them;
<dd>Commit to abide to the charter when participating in the EPDP Team;
<dd>Understand the needs of the Internet communities that ICANN serves
(standards, domains and numbers);
<dd>Commit to attend any provided introductory training courses, e.g.,
privacy, trademarks, registrar operations, DNS, etc.
<dd>Understand the broader ecosystem (the Internet Community) in which
ICANN operates and the needs of those working on other aspects of the
Internet industry.
</dl>
<dd>_______________________________________________
<dd>ALAC mailing list
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)
</dl></blockquote></body>
</html>