October 2016 - At-Large - lists.icann.org

Fwd: ATLAS II Recommendations Implementation
by Olivier MJ Crepin-Leblond Oct. 7, 2016

Oct. 7, 2016

FYI --- please comment. -------- Forwarded Message -------- Subject: ATLAS II Recommendations Implementation Date: Fri, 7 Oct 2016 16:03:15 +0100 From: Olivier MJ Crepin-Leblond <ocl(a)gih.com> To: ALAC Working List <alac(a)atlarge-lists.icann.org> Dear ALAC, as you know, the second At-Large Summit, aka ATLAS II, brought together 150 At-Large Structures to the ICANN meeting in London in June 2014. One of the outputs of that meeting was an ATLAS II Declaration, ratified by our community by acclamation and transmitted to the ICANN Board. But recommendations are one thing. Implementation of these recommendations are another. The ATLAS II Implementation Task Force picked up the Declaration, fleshed it out, coordinated action items with At-Large working groups, task forces, sub-committees, RALOs and individuals, as well as other ICANN departments, to expand the recommendations, file them and implement them. The results are very impressive: out of 43 recommendations, 34 (80%) have been addressed and implementation has taken place or is in the process of taking place. 9 (20%) are either unsuitable for implementation or require further clarification, consultation, and follow-up with relevant parties. This is all thanks to the amazing amount of work that has been furnished over the past two years by a few working groups and individuals, so kudos to them! We plan to be sending the final report on implementation of the recommendations to the Board very soon, possibly for ICANN 57 in Hyderabad. Please be so kind to therefore review the draft document on: https://docs.google.com/document/d/19sgzpi6DnDfrTjRG6_tl4dHwn1xlkIfTIQRKde0… The ATLAS II Implementation Task Force has already reviewed this document, so once the ALAC and At-Large members are fine with it, (and the ALAC has ratified it?) the ALAC can proceed forward with transmitting it officially to the Board. Kindest regards, Olivier

1 0

Re: [At-Large] Cruz' revenge
by Michele Neylon - Blacknight Oct. 7, 2016

Oct. 7, 2016

Roberto ICANN’s meeting team has backups of all the configurations so once they replace the hardware it’s relatively straightforward to deploy the software / configuraitons to them. Having extra hardware than what they already have would be pointless – they already have spares / extras anyway. The only things impacted by this issue aren’t “critical”. 1 – the cache stuff from Akamai – sure, it’s nice to have, but not having it won’t have any real impact on anyone 2 – the “interactive” hubs – they were only used for some sessions in the main hall. The remote hubs aren’t impacted beyond that as far as I know Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blacknight.blog/ http://www.blacknight.press - get our latest news & media coverage http://www.technology.ie Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Social: http://mneylon.social Random Stuff: http://michele.irish ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: <at-large-bounces(a)atlarge-lists.icann.org> on behalf of Roberto Gaetano <roberto_gaetano(a)hotmail.com> Date: Monday 3 October 2016 at 18:18 To: At-Large Worldwide <at-large(a)atlarge-lists.icann.org> Subject: [At-Large] Cruz' revenge http://domainincite.com/21067-ship-explosion-takes-icann-gear-out-of-action Two questions: · We always talk about disaster recovery, duplication of resources, etc. Why did we not put in place these measures? The question will now be “if those folks cannot secure their own equipment, how can they be trusted to take care of the Internet?” · What will be the real impact for the meeting? I cannot believe that we do not have backup solutions, as Murphy implies. We live in interesting times indeed. Brings me back to 1998, when CORE servers were stolen. Cheers, R

1 0

Cruz' revenge
by Roberto Gaetano Oct. 7, 2016

Oct. 7, 2016

http://domainincite.com/21067-ship-explosion-takes-icann-gear-out-of-action Two questions: * We always talk about disaster recovery, duplication of resources, etc. Why did we not put in place these measures? The question will now be "if those folks cannot secure their own equipment, how can they be trusted to take care of the Internet?" * What will be the real impact for the meeting? I cannot believe that we do not have backup solutions, as Murphy implies. We live in interesting times indeed. Brings me back to 1998, when CORE servers were stolen. Cheers, R

7 9

Weekly posting summary for at-large@atlarge-lists.icann.org
by narten＠us.ibm.com Oct. 7, 2016

Oct. 7, 2016

Total of 19 messages in the last 7 days. script run at: Fri Oct 7 00:53:02 EDT 2016 Messages | Bytes | Who --------+------+--------+----------+------------------------ 31.58% | 6 | 36.91% | 219179 | roberto_gaetano at hotmail.com 10.53% | 2 | 15.73% | 93413 | svg at milathan.ltd 10.53% | 2 | 11.66% | 69230 | cveraq at gmail.com 10.53% | 2 | 5.92% | 35163 | seun.ojedeji at gmail.com 5.26% | 1 | 6.90% | 40986 | ariel.liang at icann.org 5.26% | 1 | 6.44% | 38259 | jjs at dyalog.net 5.26% | 1 | 4.86% | 28843 | alan.greenberg at mcgill.ca 5.26% | 1 | 4.79% | 28451 | vanda at uol.com.br 5.26% | 1 | 3.71% | 22063 | asoto at ibero-americano.org 5.26% | 1 | 1.65% | 9805 | narten at us.ibm.com 5.26% | 1 | 1.43% | 8500 | johnl at iecc.com --------+------+--------+----------+------------------------ 100.00% | 19 |100.00% | 593892 | Total

1 0

Re: [At-Large] I: [ALAC-Announce] CALL FOR NOMINATIONS: ALAC Liaisons
by Ariel Liang Oct. 3, 2016

Oct. 3, 2016

Hello Roberto and all, All At-Large members can nominate eligible At-Large members for those positions. We will record your support for Jean-Jacques. Thank you, Ariel From: <at-large-bounces(a)atlarge-lists.icann.org> on behalf of Roberto Gaetano <roberto_gaetano(a)hotmail.com> Date: Friday, September 30, 2016 at 5:27 AM To: "at-large(a)atlarge-lists.icann.org" <at-large(a)atlarge-lists.icann.org> Subject: [At-Large] I: [ALAC-Announce] CALL FOR NOMINATIONS: ALAC Liaisons Dear all, I am not sure whether non-voting members like myself can nominate members to these positions – I have browsed the web site but have been unable to find the answer to this question. If I can, please accept my nomination for Jean-Jacques Subrenat. I have witnessed his diplomatic ability (he is a former Ambassador), his command of foreign languages (even Mandarin Chinese) and his strong multicultural attitude in particular while we were working together on the ICANN Board. I am sure that these qualities and experiences are of the upmost importance for the ALAC Liaison to a body like the GAC. If, on the other hand, I cannot nominate candidates, please disregard this email. Cheers, Roberto Da: alac-announce-bounces(a)atlarge-lists.icann.org [mailto:alac-announce-bounces@atlarge-lists.icann.org] Per conto di ICANN At-Large Staff Inviato: venerdì 23 settembre 2016 22:23 A: alac-announce(a)atlarge-lists.icann.org; alac(a)atlarge-lists.icann.org Oggetto: [ALAC-Announce] CALL FOR NOMINATIONS: ALAC Liaisons Priorità: Alta Dear All, The ALAC Appointee Selection Committee[community.icann.org] recommended for a full call for nominations for ALAC Liaisons for the 2016-2017 term. Thus, this is a call for nominations for the following ALAC Liaisons. The current Liaison is shown in brackets. - GNSO (Olivier Crepin-Leblond) - ccNSO (Maureen Hilyard) - SSAC (Julie Hammer) - GAC (Yrjö Länsipuro) -.MOBI (Murray McKercher) The one year terms will start at the close of ICANN 57 and end at the close of ICANN 60. The schedule for this call for Liaisons is: Call issued Friday, 23 September Call closes: Monday, 3 October at 23:59 UTC Acceptances due: Friday, 7 October at 23:59 UTC ALAC Appointee Selection Committee Teleconference: week of 10 October ALAC Vote (if multiple candidates from Selection Committee): As soon as practical after Selection Committee announces recommendations Please review the General Liaison requirements and responsibilities located in the revised RoP[tinyurl.com] Section 7. Of particular importance, please note the following: - (As per RoP 7.3) Liaisons to AC/SOs need not be ALAC Members, but they will normally be current or past ALAC Members, or otherwise familiar with the ALAC and At-Large and the TG to whom they will liaise. - (As per RoP 7.8) When representing the ALAC, Appointees have an obligation to solicit ALAC and At-Large views on the matter where practical and possible. Appointees should be selected knowing that in many instances such consultation may not be possible or practical and thus the ALAC needs to select people who understand the philosophies or guiding values and principles of the ALAC and At-Large. - Liaisons should be selected based on their familiarity with the group to which they are appointed. Having worked extensively with them before in some capacity (such as on multiple WGs) is a strong asset. - A level of trust between a Liaison and the group to which they are appointed is mandatory for success and must already exist or it should be demonstrable how or why it may exist in the future. - Liaisons to AC/SOs require a MAJOR time commitment over and above other At-Large responsibilities. - For the SSAC Liaison position, the ALAC only makes a recommendation. The Liaison is a full SSAC Member and must satisfy SSAC criteria and follow SSAC processes for admission to the AC. - For the GAC Liaison position, the potential candidate must be approved by GAC Leadership. - For .MOBI, the prime issue not as much mutual respect and trust, but ensuring that the Liaison understands the business of .MOBI and is well versed in mobile technologies. Liaison reports may be seen here[community.icann.org]. Liaisons are asked to provide monthly reports which summarize activities in the organization to which they are the Liaison. Process for Nomination and Selection: Nominations should be sent to the ALAC list the cc’ing Alan Greenberg and At-Large staff by Friday, 03 October at 23:59 UTC. For nominations made by people without access to the ALAC list, Staff will post to the ALAC list. All Nominees, in their acceptance or self-nomination, must provide an Expression of Interest including sufficient information about their background and experience to allow the ALAC Appointment Selection Committee to review the nominations and decide on whether to forward their candidacy to the ALAC. The Selection Committee may choose to forward one or more candidates to the ALAC for each position. The Selection Committee or its Chair may choose to ask follow-up questions, but it is not obliged to, so submissions should be as complete as possible. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org Website: atlarge.icann.org[atlarge.icann.org] Facebook: facebook.com/icann[facebook.com]atlarge[facebook.com] Twitter: @[twitter.com]ICANNAtLarge[twitter.com]

6 7