- ALAC - lists.icann.org

ICANN Fellowship Program Community Consultation
by Maureen Hilyard March 29, 2018

March 29, 2018

Hi everyone I have put the first draft of the Fellowship Consultation <https://community.icann.org/pages/viewpage.action?pageId=79441341> online. Please identify any typos for me and add any further comments you think might be helpful You have until the end of Saturday to comment before it is finalised and submitted to Ergys. Regards Maureen

2 1

URGENT: Proposal for a motion for the ALAC
by Olivier MJ Crépin-Leblond March 28, 2018

March 28, 2018

Dear Alan, the European At-Large Organisation (EURALO) has held its call a moment ago and after holding a 1 minute silence in memory of Stéphane van Gelder who has left us in tragic circumstances, participants on the call fully supported the proposal of a motion to be made by an ALAC member, for the ALAC to decide to nominate Stéphane van Gelder for the ICANN Ethos Award. The Ethos Award nomination period has been extended to 28 March 2018, so any vote of support should take place today. https://www.icann.org/news/announcement-2018-03-20-en In the meantime, I am also sending a 24H consensus call for support of this motion to the EURALO mailing list. Stéphane was a EURALO individual member and will be greatly missed. Please be so kind to consider this motion even though it is arriving at such short notice before the ALAC call. Kindest regards, Olivier MJ Crépin-Leblond EURALO Chair

8 7

GDPR on today's ALAC Agenda
by Alan Greenberg March 28, 2018

March 28, 2018

Attached and in the body of this message are the notes for today's discussion of GDPR on the ALAC Call. ----------------------------- ALAC Meeting 27 March 2018 GDPR Discussion The ALAC and At-Large are divided on whether the proposed Interim Model meets the requirements of the GDPR and specifically whether the rationales for collecting various data items are specified in sufficient detail and are sufficiently compelling. There are also differing views on whether the transport of data to Registries in compliance with "thick WHOIS" rules is GDPR compliant. In the absence of concerns over privacy, ICANN has previously determined that the thick WHOIS model is the one that should be used and we should not re-litigate that here. We have similarly decided that single points of failure must be avoided and all data must be escrowed in case of any of multiple forms of failure. All data items have proven useful in the past (that was the result of ICANN's earlier work). Whether it can be justified in the current situation is the question. All of these issues will need to be judged by DPAs and to the extent that they make clear statements, we will have to abide by them. The ALAC has the responsibility to look at all issues from and end-user perspective. We also have concerns for registrant issues, but where they differ we support users. 1. Must registrars continue to collect the contact details for administrative and technical contacts and transmit them to the registry and escrow provider? 2. Should anonymized e-mail addresses should be substituted for the e-mail addresses for registrant, administrative, and technical contacts in public WHOIS? 3. Should registries and registries be permitted to optionally apply the model on a global basis? 4. Should the model apply to contact details supplied by registrants who are legal persons? 5. Which elements of WHOIS data should be published in public WHOIS while an accreditation program for layered/tiered access is being developed? 6. How many levels should the "tiered" access mechanism support? 7. Bulk access should it be allowed?

3 2

Re: [ALAC] Stephane van Gelder
by Vanda Scartezini March 27, 2018

March 27, 2018

I support too. It was a tragic destiny and his memory deserves some recognition from the community he had served for so many years. Vanda Scartezini Polo Consultores Associados Av. Paulista 1159, cj 1004 01311-200- Sao Paulo, SP, Brazil Land Line: +55 11 3266.6253 Mobile: + 55 11 98181.1464 Sorry for any typos. From: ALAC <alac-bounces(a)atlarge-lists.icann.org> on behalf of wafa DAHMANI <wafa(a)ati.tn> Date: Tuesday, March 27, 2018 at 16:52 To: Barrack Otieno <otieno.barrack(a)gmail.com> Cc: 'ALAC List' <alac(a)atlarge-lists.icann.org> Subject: Re: [ALAC] Stephane van Gelder Dear all, He definitely deserves it, I strongly support the idea RIP Stephane ________________________________ De: "Barrack Otieno" <otieno.barrack(a)gmail.com> À: "Carlton Samuels" <carlton.samuels(a)gmail.com> Cc: "ICANN ALAC list" <alac(a)atlarge-lists.icann.org> Envoyé: Mardi 27 Mars 2018 20:45:16 Objet: Re: [ALAC] Stephane van Gelder Hi Evan, hi colleagues, Indeed he deserves the Multi Stakeholder Ethos award albeit posthumously. Regards On Tue, Mar 27, 2018 at 8:51 PM, Carlton Samuels <carlton.samuels(a)gmail.com<mailto:carlton.samuels@gmail.com>> wrote: +1. He was a good man. Had a minute of conversation at SJU, even taking the time to encourage me to consider NomCom. May he RIP. I support his nomination for the Ethos award, especially for reasons outlined by Evan. -Carlton ============================== Carlton A Samuels Mobile: 876-818-1799 Strategy, Planning, Governance, Assessment & Turnaround ============================= On Tue, Mar 27, 2018 at 12:03 PM, Evan Leibovitch <evan(a)telly.org<mailto:evan@telly.org>> wrote: Hello all, I am informed that Stephane died last weekend in a traffic accident. Stephane had been active in the GNSO and Nominating Committee and is was Chair of the GNSO during my time as ALAC Vice-Chair. While we didn't agree on everything, Stephane was one of the few members of the domain industry who had both the interest and capacity to work towards broad consensus. His presence at ICANN will be clearly missed. I have been aware of growing interest in the GNSO to support Stephane's posthumous nomination for the ICANN ethos award. I would support this. -- Evan Leibovitch Toronto, Canada Em: evan at telly dot org Sk: evanleibovitch Tw: el56 _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org<mailto:ALAC@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… _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org<mailto:ALAC@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… -- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A _______________________________________________ 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

Stephane van Gelder
by Evan Leibovitch March 27, 2018

March 27, 2018

Hello all, I am informed that Stephane died last weekend in a traffic accident. Stephane had been active in the GNSO and Nominating Committee and is was Chair of the GNSO during my time as ALAC Vice-Chair. While we didn't agree on everything, Stephane was one of the few members of the domain industry who had both the interest and capacity to work towards broad consensus. His presence at ICANN will be clearly missed. I have been aware of growing interest in the GNSO to support Stephane's posthumous nomination for the ICANN ethos award. I would support this. -- Evan Leibovitch Toronto, Canada Em: evan at telly dot org Sk: evanleibovitch Tw: el56

6 5

Fellowship on today's ALAC Agenda
by Alan Greenberg March 27, 2018

March 27, 2018

Attached and in the body of this message are the notes for today's discussion of the Fellowship on the ALAC Call. ----------------------------- ALAC Meeting 27 March 2018 Fellowship Questionnaire Program Goals and Vision 1. What does your group believe should be the objective of the Fellowship Program? How would the success of this objective be measured? > Integration of "graduates" into the > various constituent parts of ICANN as active participants in ICANN activities 2. The Fellowship Program was established to provide access to ICANN meetings to individuals from underserved and underrepresented communities. In your groups opinion, how effective is the Fellowship Program at fulfilling its current goal? > It is moderately effective in getting > people to know about ICANN. Although there have > been a number of notable successes, it is more > effective at raising awareness than in generating workers. 3. In your groups opinion, is this goal still a priority for ICANN, given the new bylaws? If not, what new goals would your group propose for the program? > Yes, it must still be a goal but with > a target of measurable success as measured by the AC/SOs. Assessment of Program Impact on your SO/AC group 4. Have Fellows contributed to the work of your group? If so, where do you think they have added the most value? What might be changed about the Fellowship Program to enhance participation of Fellows in your group? > At-Large has had a number of great > successes with Fellowship alumni. The greatest > value has come from the relatively few who have > chosen to devote time and energy to ICANN post-Fellowship. 5. Does your group make efforts to involve, educate, and/or inform Fellows about your work? If so, please describe these efforts. > Yes, but it is rather haphazard. We > engage at ICANN meetings, but there is no > concerted effort to draw people into our activities. 6. How willing would your group (SO/AC/SG/C) be to participate and take ownership for selecting and developing fellows, including giving them assignments, assigning mentors, etc? > We are willing to participate. Mentors > are possible, but that would presume filtering > candidates who have a particular interest in our areas. Selection Processes 7. Are you aware of the Fellowship selection process? What changes, if any, would you suggest for the selection process? > Yes, we are willing. Returning Fellows > should come with a specific AC/SO/Const in mind > and these must be balanced over the > organization. This shouldbe accompanied by the > identification of coaches from the appropriate group. > > The effectiveness of fellows returning > as mentors and coaches should be evaluated. > > Prospective fellows must be willing to > take intro courses on ICANN Learn. If there are > not suitable courses there that will provide > the needed background, they should be created. > > It should be clear that this is not > tourism, but a path towards active engagement. > > One of the problems may be the > categories used in the selection process. > At-Large fits best into "civil society" but we > do not comfortably fit into the typical model of "civil society". > > And lastly, as long as we still have > fellows at the public meeting asking questions > why ICANN doing nothing to regulate dangerous > content, we are clearly not getting the selection/preparation right. 8. An individual can be awarded a Fellowship up to three times. Do you suggest retaining or revising this number? Why? >We would like to see a study of who (and with >how many trips) actually becomes active in ICANN >on an ongoing basis prior to addressing this. 9. For Policy Forum Meetings, currently only Fellowship Alums can apply. Do you support continuing with this approach? If not, what changes would you suggest? >We support it IF there is data to demonstrate >that these people participate in the policy >activities and do so across the community. Program Size 10. Considering your responses to previous questions, would you suggest making the program larger, smaller, or maintaining the current size? >30 was a very effective group and At-Large >supported increasing it. It may be that 60 was >overreaching and there are not sufficient >available resources (throughout the community) to integrate them. 11. If the program were to be reduced in size, what would your group deem as the priorities for the program with a smaller cohort? >Migration of Fellows to active participation. >This is too expensive a program to use it as >purely dissemination of information about ICANN. Program Structure 12. When you interact with Fellows at an ICANN Meeting, do you find that they are sufficiently knowledgeable about ICANN? If not, what skills or areas of knowledge would you suggest increasing focus on for pre-Meeting preparation? > It depends on whether they are new or have been to prior meetings. 13. Do you think that Fellows spend sufficient time in working sessions with your group during the course of an ICANN meeting? If not, what would changes would your group propose? > No, but it would be good to have us > submit a list of sessions that would prove useful to them. 14. Do you feel that you have enough time to engage with Fellows at an ICANN meeting? > Sadly, no. Information Available on Program 15. Is the information currently available clear and sufficient for your community members to understand the Fellowship Program? If not, which elements could be improved and how? > A presentation either via > teleconference or at an ICANN meeting would be a good start. 16. Are your community members aware of the differences between the Fellowship and NextGen@ICANN Programs? If not, please state what type of clarification would be useful. > Yes, I believe so. General Questions 17. The Fellowship Program seeks to engage participants who will go on to participate actively in the ICANN community. What skills, attributes and backgrounds have provided the most successful and active participation in your SO/AC/SG/C? What skillsets and backgrounds would your group see as desirable for candidates for the Fellowship Program? > At-Large focuses on issues that impact > end-users. A passionate consideration for > end-users, those without the knowledge of ICANN, is the key. 18. With which elements of the Fellowship Program is your group most satisfied? What changes or improvements would your group most want to see implemented to the program? > We are most satisfied with the > relatively small number of people who have gone > on to make At-Large their home and productively > work with us. We would like to see more! 19. Do you have any other questions or comments about the Fellowship Program?

1 0

Fwd: [ALAC-Announce] ICANN News Alert -- ICANN Community Onboarding Pilot Program Call for Nominations by SOs/ACs
by Judith Hellerstein March 27, 2018

March 27, 2018

3 2

ALAC NomCom delegates
by Alan Greenberg March 27, 2018

March 27, 2018

Selections/elections are coming soon. There has been a lot of individual discussion recently about exactly what characteristics we are looking for in the delegates we send to the NomCom. This year, I think we need to be VERY clear in what we are looking for. I would like to put together a small drafting team of people who have NomCom and related experience to propose such a statement. Please contact me privately if you are interested in participating. The deadline for having such a statement for inclusion in the call for volunteers is mid-April. Alan

1 0

SSR2 RT
by Alan Greenberg March 22, 2018

March 22, 2018

For your information, appended here is a letter sent from the SO/AC Chairs to the OEC and the SSR2-RT last week (slightly modified to reflect a wording that was confusing in the original message). I have asked our RT members for their thoughts on this plan and for confirmation that they will be staying on the RT. Alan >Date: Tue, 13 Mar 2018 14:08:40 -0400 >To: Khaled Koubaa <khaled.koubaa(a)board.icann.org> >Cc: Board Calendaring <board-caucus-ssr2(a)icann.org>, > SO-AC Chairs List <soac-chairs(a)icann.org>, ssr2-review(a)icann.org >Subject: SSR2-RT > >Dear Khaled, > >Thank you for your reply on behalf of the Board OEC to our request >for support in the appointment of an external facilitator to enable >the re-start of SSR2-RT. In this message, while ICANN61 is underway, >we hope to answer the questions you have raised to make tangible >progress during this meeting and immediately provide the RT members >and the broader community with much-needed action and clarity. In >short, to the extent that a procure process is necessary, we ask >that it commence immediately. The appointment of the facilitator and >all new members (already in progress within the SO/ACs) will signal >the formal "un-pause" or "re-start" of the SSR2-RT. > >Our overarching aim is to empower the RT members to come together as >a group and progress their work. To that end, it is absolutely >imperative that the RT members be involved in this discussion. Our >responses here should be interpreted as guidance from the community >rather than a top-down mandate. We therefore have included the RT >members in this reply, and ask that going forward our communications >include them, and that they contribute to these recommendations. > >To guide the procurement process (specific details for which are set >out below) we wish to explain in more detail the intended role of >the facilitator. Our email of 15 February stated: "The primary aim >of the external facilitator would be to facilitate this transition >process, with a view to winding facilitation down when RT members >and leaders consider that issues are satisfactorily resolved to >continue their work." We consider the role of the facilitator to be >a) onboarding new members who have joined since the "pause" and >agreeing on leadership from within the then current membership; b) >helping the group to work through concerns around membership and >scope as identified in a confidential survey conducted by the SO/AC >Chairs shortly after the pause; and c) helping the RT to identify >ways to reach consensus. Specifically in response to the procurement practice: > * Skill set requirements: To most effectively fulfil a), b) and > c) above, the facilitator should be external to ICANN, with > expertise in group dynamics and empowering group members with > divergent views and experience to coalesce around a common goal. > The SO/AC Chairs will provide the confidential responses received > to the survey conducted following ICANN60 which sought RT member > input on issues relating to membership and scope, and which > generated quite divergent responses. The facilitator must therefore > establish a safe space in which the broad range of views on > membership and scope can be discussed and common positions > identified, with agreement on moving forward in an agreed statement > of scope and list of members. > * Experience requirements: As appropriate to meet skill set > requirements above > * Scope of work: a) helping the group to coalesce around > leadership and onboarding new members who have joined since the > "pause"; b) helping the group to work through concerns around > membership and scope as identified in a confidential survey > conducted by the SO/AC Chairs shortly after the pause; c) helping > the RT to identify ways to reach consensus. > * Timing and duration: Facilitation ends when all expected > deliverables (below) are completed. > * Expected deliverables: a) confirmation of membership list of > RT going forward, with chair/s identified; b) an agreed statement > of scope; and c) if considered necessary by the RT members, a > request from the RT for additional or different resources (ie, more > members with particular skills, refinements to staff support), with > a clear statement as to how any such request is necessary to and > directly supportive of the RT's work. >We appreciate your positive response to our initial request, and are >prepared to respond promptly to any further questions this week, in >order that the procurement process can commence immediately. We ask >further that this be prioritised by the OEC so that the >facilitator's appointment - and thus the re-start of SSR2-RT - can >take place as soon as possible, and no later than 1 May for >scheduling to take full advantage of face to face time at ICANN62. > >Kind regards, on behalf of, > >SO/AC Chairs

1 0

ALAC Meeting next week
by Alan Greenberg March 22, 2018

March 22, 2018

The main focus of the ALAC meeting on Tuesday will be to come to closure on: - KSK Rollover Statement (https://community.icann.org/x/dw28B) - Issues to raise in the GDPR statement (https://community.icann.org/x/Ay68B) - Fellowship statement (https://community.icann.org/x/vS28B) PLEASE SUBMIT YOUR COMMENTS/THOUGHTS BY THE END OF SUNDAY so they can be summarized for discussion on Tuesday. Alan

1 0