- ALAC - lists.icann.org

Re: [ALAC] At-Large Review Feasibility Study
by Alan Greenberg Aug. 19, 2017

Aug. 19, 2017

That is "Organizational" Effectiveness Committee... Alan At 19/08/2017 12:06 PM, Alan Greenberg wrote: >Please find attached the At-Large Review Feasibility Study to be >submitted to the Board Operational Effectiveness Committee. > >This Documents will be a major focus of DISCUSSION and DECISION >during the ALAC meeting this coming Tuesday. > >The decision will be on this document IN PRINCIPLE. The document >still needs some additional sections (history and timeline) to be >drafted and an overall cleanup, but will not change in substance. > >This document is largely based on the last response to the Draft >At-Large Review Report approved by the ALAC, and has been subject to >significant community feedback and input, culminating in a very well >attended Webinar last week. The input received during that Webinar >has now been integrated. > >Please review this document one final time in preparation for the >discussion on Tuesday. > >I wish to thank all who have contributed to this and give a special >vote of thanks to Cheryl, Holly and Maureen for their work on the >final editing. > >Alan

1 0

Re: [ALAC] At-Large Review Feasibility Study
by Alan Greenberg Aug. 19, 2017

Aug. 19, 2017

Thanks Evan. This is just the start of a long process to actually implement what we are agreeing to do, but it is good to finally get to this stage. Alan At 19/08/2017 12:33 PM, Evan Leibovitch wrote: >Very nice work. Clear and direct. >Thanks to all involved in its development. > > >On 19 August 2017 at 12:06, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Please find attached the At-Large Review Feasibility Study to be >submitted to the Board Operational Effectiveness Committee. > >This Documents will be a major focus of DISCUSSION and DECISION >during the ALAC meeting this coming Tuesday. > >The decision will be on this document IN PRINCIPLE. The document >still needs some additional sections (history and timeline) to be >drafted and an overall cleanup, but will not change in substance. > >This document is largely based on the last response to the Draft >At-Large Review Report approved by the ALAC, and has been subject to >significant community feedback and input, culminating in a very well >attended Webinar last week. The input received during that Webinar >has now been integrated. > >Please review this document one final time in preparation for the >discussion on Tuesday. > >I wish to thank all who have contributed to this and give a special >vote of thanks to Cheryl, Holly and Maureen for their work on the >final editing. > >Alan >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > > > >-- >Evan Leibovitch >Toronto, Canada >Em: evan at telly dot org >Sk: evanleibovitch >Tw: el56

1 0

At-Large Review Feasibility Study
by Alan Greenberg Aug. 19, 2017

Aug. 19, 2017

Please find attached the At-Large Review Feasibility Study to be submitted to the Board Operational Effectiveness Committee. This Documents will be a major focus of DISCUSSION and DECISION during the ALAC meeting this coming Tuesday. The decision will be on this document IN PRINCIPLE. The document still needs some additional sections (history and timeline) to be drafted and an overall cleanup, but will not change in substance. This document is largely based on the last response to the Draft At-Large Review Report approved by the ALAC, and has been subject to significant community feedback and input, culminating in a very well attended Webinar last week. The input received during that Webinar has now been integrated. Please review this document one final time in preparation for the discussion on Tuesday. I wish to thank all who have contributed to this and give a special vote of thanks to Cheryl, Holly and Maureen for their work on the final editing. Alan

2 1

Re: [ALAC] 2017-2018 ALAC Leadership Team
by Alan Greenberg Aug. 19, 2017

Aug. 19, 2017

Thanks for the kind words Rinalia. Alan At 18/08/2017 02:35 PM, Rinalia Abdul Rahim wrote: >Hello, ALAC! > >Congratulations to the ALAC and to the new Leadership Team! > >The information on the new team has been shared with the Board and >it is very warmly received. > >I have no doubt that the ALAC and its new leadership will enhance >the impact of the At-Large in ICANN. > >I am heartened by all the soul-searching and hard work that the >At-Large has engaged in to ensure improvements for a stronger >community that represents end user interest. I know there is still >quite a bit of work left and I can see that Alan is rolling up his >sleeve to get it done. His leadership and contributions to ICANN are >acknowledged and appreciated by the Board and the CEO. > >I would like to take the opportunity to thank the outgoing team. >They have done a tremendous service to the community. > >You all continue to make me extremely proud to be the At-Large >selected director. > >With best wishes for the future, > >Rinalia > > >On Thu, 10 Aug 2017 at 8:32 PM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Nominations for the 2017-2018 ALT closed on 08 August 2017. Four >nominations had been received, one per region: > >AFRALO: Seun Ojedeji >APRALO: Maureen Hilyard >EURALO: Bastiaan Goslings >LACRALO: Bartlett Morgan > >All four have accepted the nomination. In accordance with our RoP >16.3: "If, following the close of the acceptance period or after all >nominations have been accepted, there is only one candidate for a >given position, or if as the process continues one or more >candidates withdraw leaving only one remaining candidate, the sole >candidate will be declared the winner by acclamation without the >need for a decision of the ALAC.", all four are declared to have >been appointed by acclamation to the serve on the 2017-2018 ALT. > >There were no explicit nominations for Vice-Chair. As specified in >the Call for Nominations, in such a case, the incoming Chair may >select the Vice-Chairs. I have asked Maureen and Bastiaan to serve >in this capacity and they have both accepted. > >I thank Sean, Maureen, Bastiaan and Bartlett for agreeing to serve >the ALAC and At-Large in this way. I am delighted with this team, >and look forward to working with them. > >Alan >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;CY4PR03MB2709;27:5Y4ntrtZGjNsc8AqJEM3og6BPiyw5RGFJFlz13OJlat89TxCkmw2x12U+40sGVG76ayGPdvU5dBmFUMOQWHDOdUy4pKj5EveIovxaB+glVCYIKGJAA1B/WcRTQnIruuS >X-Microsoft-Antispam-Mailbox-Delivery: > >ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095); > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

1 0

2017-2018 ALAC Leadership Team
by Alan Greenberg Aug. 18, 2017

Aug. 18, 2017

Nominations for the 2017-2018 ALT closed on 08 August 2017. Four nominations had been received, one per region: AFRALO: Seun Ojedeji APRALO: Maureen Hilyard EURALO: Bastiaan Goslings LACRALO: Bartlett Morgan All four have accepted the nomination. In accordance with our RoP 16.3: "If, following the close of the acceptance period or after all nominations have been accepted, there is only one candidate for a given position, or if as the process continues one or more candidates withdraw leaving only one remaining candidate, the sole candidate will be declared the winner by acclamation without the need for a decision of the ALAC.", all four are declared to have been appointed by acclamation to the serve on the 2017-2018 ALT. There were no explicit nominations for Vice-Chair. As specified in the Call for Nominations, in such a case, the incoming Chair may select the Vice-Chairs. I have asked Maureen and Bastiaan to serve in this capacity and they have both accepted. I thank Sean, Maureen, Bastiaan and Bartlett for agreeing to serve the ALAC and At-Large in this way. I am delighted with this team, and look forward to working with them. Alan

22 21

Re: [ALAC] Consensus Call: ALAC Liaisons for 2017-18
by Alan Greenberg Aug. 16, 2017

Aug. 16, 2017

Answers embedded below. At 16/08/2017 02:51 AM, Seun Ojedeji wrote: >Hello Alan, > >Am not sure I understand why we will be >selecting more than 1 person for Maureen to >mentor since only one person will serve as >replacement of her. Selecting more than 1 will >also make travel difficult to allocate. We may not select more than 1, but that will depend on the people who put their names forward. We don't want to waste people's time or other resources, but it may not be obvious at the start who the best candidate is. If there is more than one, travel could be an issue (depending on whether the person is already funded or not) and that will surely be a consideration, but only one of them. >Secondly I think it's important to be clear from >start the maximum number of months that this >mentorship will take so whoever is selected will >be able to assume his/her role. My personal opinion is it will be several months, covering at least one and perhaps two ICANN meetings. That will depend on whether the initial selection is made prior to ICANN60, whether the candidates will be in Abu Dhabi, and just how quickly it goes. I am sure that Maureen will do this as quickly as practical, and she may have some comments to add. In my mind, the ABSOLUTE limit is the 2018 AGM, but I surely hope the transition is complete prior to then. >Lastly I hope the selection of the replacement >will be done by/before Abu dhabi so those that >were selected will then have the opportunity to >start attending next ICANN meeting. I am optimistic that we will have completed out initial selection for the SSAC prior to Abu Dhabi. I cannot address whether the SSAC Membership Committee and the SSAC will have completed their part by then. For the ccNSO, it is pretty clear it will not be done by then. If we really though that these selections could be made before the meeting, there would be no need to reappoint Maureen and Julie on an interim basis. Alan >Regards >Sent from my mobile >Kindly excuse brevity and typos > >On Aug 16, 2017 3:51 AM, "Alan Greenberg" ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Following consultation with ALAC Members and >with our current Liaisons, this is Consensus >Call on how to address our Liaisons to the GNSO, >ccNSO, SSAC and GAC for the year beginning at >the end of ICANN60 to be held in Abu Dhabi. > >Our current Liaisons are: > >GNSO: Cheryl Langdon-Orr >GAC: YrjÃ¶ LÃ¤nsipuro >ccNSO: Maureen Hilyard >SSAC: Julie Hammer > >All four are serving the ALAC well. Cheryl and >YrjÃ¶, both having served just one term (plus >several months for YrjÃ¶) and have agreed, with >the support of the ALAC, to continue in their >roles. Maureen and Julie have both indicated >that they wish to step down from their Liaison >roles. In the case of the ccNSO, we expect the >identification and training of a replacement to >take a significant number of months, during >which time Maureen will stay on as Liaison. In >the case of the SSAC, as Julie will become the >new Vice-Chair of the SSAC in January, she would >like to step down as soon as practical, but has >agreed to serve for the first months of the >ICANN year if a replacement has not been named by then. > >In all four cases and in accordance with ALAC >RoP 18.2 (See ><http://tinyurl.com/ALAC-RoP-2016-09>http://tinyurl.com/ALAC-RoP-2016-09 >and reproduced at the end of this message), I am >proposing that the ALAC re-appoint the current Liaisons. > >In parallel with this we will also begin the >process of identifying a replacement for both Maureen and Julie. > >ccNSO: > >A set of qualifications will be assembled and a >call will be issued for volunteers interested in >serving as the ALAC Liaison to the ccNSO. >Depending on the number of candidates, either >Maureen will work with the candidates (with the >permission of the ccNSO) and ultimately makes a >recommendation or set of recommendations on the >future ccNSO Liaison. If there are too many >candidates, the ALAC Appointee Selection >Committee (AASC) working with Maureen will >select a sub-set for Maureen to mentor. This >process will continue into the coming year, but >the success we had with a similar process last >time there was a change in ccNSO Liaison >indicates that it is worth the time and effort. > >SSAC: > >A set of qualifications will be assembled and a >call will be issued for volunteers. The list of >candidates will go to the AASC who, with Julie's >assistance, will select no more than two >potential candidates. Those selected will be >forwarded to the SSAC (ratified by the ALAC). If >the SSAC decides to admit one person to the >SSAC, that person is our SSAC Liaison. If the >SSAC selects more than one, this subset of >people returns the AASC for final selection. Due >to the number of steps and the requirement for >the SSAC Membership Committee and the SSAC to >meet, this may or may not happen prior to the end of ICANN60. > >With this message, I am initiating a Consensus >Call of the ALAC to ratify the above recommendations. > >This Consensus Call will end at 23:59 UTC on Monday, 21 August 2017. > >If there are any questions of comments, please >direct them to either this list or to me directly. > >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). > >Alan > >======================= > >ALAC Rules of Procedure > >18.1 Appointments of At-Large Appointees to >various bodies both inside and outside of ICANN >will be made by the ALAC. Such appointments will >normally be initiated by a call for volunteers, >posted by the Chair/Staff to the Approved >Distribution Lists, and on other lists if >appropriate, allowing at least seven days for >people to volunteer. The decision regarding >appointments is typically made via Consensus. >However, the Chair will initiate a secret ballot >to determine which candidate is to be appointed >if Consensus cannot be reached or if this is requested by any ALAC Member. > >18.2 By the decision of the ALAC, a current >Appointee who is willing to continue in that >role may be reconfirmed instead of initiating a new selection process. > >18.3 In the case of selections requiring complex >criteria evaluation, the ALAC may choose to form >a sub-committee to carry out the analysis and to >make recommendations to the ALAC based on that analysis. > >18.4 For situations where the ALAC is not >empowered to make appointments but rather to >endorse one or more candidates, essentially the >same process as described here for appointments >should be used, but with the outcome being an endorsement. > >_______________________________________________ >ALAC mailing list ><mailto:ALAC@atlarge-lists.icann.org>ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org >ALAC Working Wiki: ><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… > > >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;DM5PR03MB2714;27:j8abEXqxo1uo9d8H86iikCyhqV8rEmtkun8UrVHYHy+vFvIHi3T/SuqUfrGOJGto99HrI0OClLrp2q0QDgQFPrIKtqz8jfZGs5Z8psSPJ7HfuWq6KaMagRm7v6EvxpDs >X-Microsoft-Antispam-Mailbox-Delivery: > >ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095); > >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org >ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL…

2 1

Consensus Call: ALAC Liaisons for 2017-18
by Alan Greenberg Aug. 16, 2017

Aug. 16, 2017

Following consultation with ALAC Members and with our current Liaisons, this is Consensus Call on how to address our Liaisons to the GNSO, ccNSO, SSAC and GAC for the year beginning at the end of ICANN60 to be held in Abu Dhabi. Our current Liaisons are: GNSO: Cheryl Langdon-Orr GAC: Yrjö Länsipuro ccNSO: Maureen Hilyard SSAC: Julie Hammer All four are serving the ALAC well. Cheryl and Yrjö, both having served just one term (plus several months for Yrjö) and have agreed, with the support of the ALAC, to continue in their roles. Maureen and Julie have both indicated that they wish to step down from their Liaison roles. In the case of the ccNSO, we expect the identification and training of a replacement to take a significant number of months, during which time Maureen will stay on as Liaison. In the case of the SSAC, as Julie will become the new Vice-Chair of the SSAC in January, she would like to step down as soon as practical, but has agreed to serve for the first months of the ICANN year if a replacement has not been named by then. In all four cases and in accordance with ALAC RoP 18.2 (See <http://tinyurl.com/ALAC-RoP-2016-09>http://tinyurl.com/ALAC-RoP-2016-09 and reproduced at the end of this message), I am proposing that the ALAC re-appoint the current Liaisons. In parallel with this we will also begin the process of identifying a replacement for both Maureen and Julie. ccNSO: A set of qualifications will be assembled and a call will be issued for volunteers interested in serving as the ALAC Liaison to the ccNSO. Depending on the number of candidates, either Maureen will work with the candidates (with the permission of the ccNSO) and ultimately makes a recommendation or set of recommendations on the future ccNSO Liaison. If there are too many candidates, the ALAC Appointee Selection Committee (AASC) working with Maureen will select a sub-set for Maureen to mentor. This process will continue into the coming year, but the success we had with a similar process last time there was a change in ccNSO Liaison indicates that it is worth the time and effort. SSAC: A set of qualifications will be assembled and a call will be issued for volunteers. The list of candidates will go to the AASC who, with Julie's assistance, will select no more than two potential candidates. Those selected will be forwarded to the SSAC (ratified by the ALAC). If the SSAC decides to admit one person to the SSAC, that person is our SSAC Liaison. If the SSAC selects more than one, this subset of people returns the AASC for final selection. Due to the number of steps and the requirement for the SSAC Membership Committee and the SSAC to meet, this may or may not happen prior to the end of ICANN60. With this message, I am initiating a Consensus Call of the ALAC to ratify the above recommendations. This Consensus Call will end at 23:59 UTC on Monday, 21 August 2017. If there are any questions of comments, please direct them to either this list or to me directly. 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). Alan ======================= ALAC Rules of Procedure 18.1 Appointments of At-Large Appointees to various bodies both inside and outside of ICANN will be made by the ALAC. Such appointments will normally be initiated by a call for volunteers, posted by the Chair/Staff to the Approved Distribution Lists, and on other lists if appropriate, allowing at least seven days for people to volunteer. The decision regarding appointments is typically made via Consensus. However, the Chair will initiate a secret ballot to determine which candidate is to be appointed if Consensus cannot be reached or if this is requested by any ALAC Member. 18.2 By the decision of the ALAC, a current Appointee who is willing to continue in that role may be reconfirmed instead of initiating a new selection process. 18.3 In the case of selections requiring complex criteria evaluation, the ALAC may choose to form a sub-committee to carry out the analysis and to make recommendations to the ALAC based on that analysis. 18.4 For situations where the ALAC is not empowered to make appointments but rather to endorse one or more candidates, essentially the same process as described here for appointments should be used, but with the outcome being an endorsement.

3 2

Julie Hammer
by Alan Greenberg Aug. 15, 2017

Aug. 15, 2017

I am absolutely delighted to report that Julie Hammer has been selected as the new Vice-Chair of SSAC. Rod Rasmussen has been selected as the incoming Chair. For those who don't know him, Rod is a very respected expert in cyber security, has been headily involved the Anti-Phishing Working Group, and within ICANN, in WHOIS-RDS activities. Both appointments, which must be confirmed by the ICANN Board in Abu Dhabi, take effect 01 January, 1918. Although losing Julie as our Liaison to SSAC will be difficult for us, it is a marvellous confirmation that we are not alone in our respect and admiration for Julie. Alan

24 23

RDS-WHOIS2 Review Team
by Alan Greenberg Aug. 15, 2017

Aug. 15, 2017

I am not sure if I have mentioned this or not, but I was recently named as the Interim Chair of the RDS-WHOIS2 Review Team. Whether or not I will continue will be decided during a face-to-face meeting at the beginning of October. I do not expect the workload from this to be particularly onerous and should be less than that associated with the CCWG-Accountability Work Steam 2 groups that I have been active in, and which are rapidly ramping down now. There may, of course be the occasional conflict during ICANN meetings, but that is nothing unusual. Alan

1 0

ALS decertification
by Alan Greenberg Aug. 14, 2017

Aug. 14, 2017

There are four ALS decertifications that have been pending for quite some time. The motion to formalize the decertifications is below. The decertifications will be carried out in a single vote unless there is a request for any of them to be done individually (allowing a different vote from the rest). Decertifications are normally carried out with a open vote, but a non-public ballot may be used if requested by any ALAC Member. If a non-public ballot is used, how ALAC Members vote is not publicly displayed but is still visible to the Chair and staff to allow a rationale to be determined for the decertification in the case of an appeal. Request to split the vote or use a non-public vote may be made on this list or privately to me and staff. Any such requests must be received no later than 23:59 UTC on Friday 11 August 2017. The vote or votes will begin soon thereafter. Alan >Whereas the ALAC Rules of Procedures and the >associated Adjunct Document 04 At-Large >Structure Framework allows the ALAC to decertify an At-Large Structure (ALS); > >Whereas, as documented at ><https://community.icann.org/display/atlarge/ISOC+Luxembourg+A.S.B.L.+%28EUR…>https://community.icann.org/display/atlarge/ISOC+Luxembourg+A.S.B.L.+%28EUR…, >ISOC Luxembourg A.S.B.L. either no longer exists >or no longer satisfies the requirements to be an >ALS as identified in the At-Large Structure >Framework, and/or the ALS requirements as outlined in the RALOâs rules; > >Whereas, as documented at ><https://community.icann.org/pages/viewpage.action?pageId=64072319>https://community.icann.org/pages/viewpage.action?pageId=64072319, >AsociaciÃ³n Costarricense de Derecho >InformÃ¡tico either no longer exists or no >longer satisfies the requirements to be an ALS >as identified in the At-Large Structure >Framework, and/or the ALS requirements as outlined in the RALOâs rules; > >Whereas, as documented at ><https://community.icann.org/display/atlarge/N-CAP+%28NARALO%29+Decertificat…>https://community.icann.org/display/atlarge/N-CAP+%28NARALO%29+Decertificat…, >N-CAP either no longer exists or no longer >satisfies the requirements to be an ALS as >identified in the At-Large Structure Framework, >and/or the ALS requirements as outlined in the >RALOâs rules; the ALS has also informed the >ALAC that it no longer desires to be an ALS; > >Whereas, as documented at ><https://community.icann.org/display/atlarge/Association+for+Community+Netwo…>https://community.icann.org/display/atlarge/Association+for+Community+Netwo…, >Association for Community Networking (AFCN) >either no longer exists or no longer satisfies >the requirements to be an ALS as identified in >the At-Large Structure Framework, and/or the ALS >requirements as outlined in the RALOâs rules; > >It is resolved that the ALAC decertifies the >following organizations as ICANN At-Large >Structures: ISOC Luxembourg A.S.B.L., >AsociaciÃ³n Costarricense de Derecho >InformÃ¡tico, N-CAP, and Association for Community Networking (AFCN). > >Such decertification is subject ICANN Board >Reconsideration as per Article IV, Section 2 of >the ICANN Bylaws and is done without prejudice >to any future re-application of this >organization for certification as an ALS, or the >application for ALS certification of any other group bearing the same name.

4 4