- ALAC-Announce - lists.icann.org

New Public Comment: Draft Final Report of the NomCom2 Review
by ICANN At-Large Staff March 29, 2018

March 29, 2018

Dear All, This is to let you know that the Public Comment on the Draft Final Report of the NomCom2 Review<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> has now gone live. Public comment will end on 07 May 2018 23:59 UTC. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. The wiki workspace for this public comment is https://community.icann.org/x/y4LpB. All pertinent resources can also be found there. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_1694838152]

1 0

New Public Comment: Proposed Revisions to Bylaws Section 11 – Additional Voting Thresholds
by ICANN At-Large Staff March 29, 2018

March 29, 2018

Dear All, This is to let you know that the Public Comment on the Proposed Revisions to Bylaws Section 11 – Additional Voting Thresholds<https://community.icann.org/pages/viewpage.action?pageId=82412214> has now gone live. Public comment will end on 05 May 2018 23:59 UTC. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. The wiki workspace for this public comment is https://community.icann.org/x/toLpB. All pertinent resources can also be found there. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_915080772]

1 0

KSK Rollover on today's ALAC Agenda
by ICANN At-Large Staff March 27, 2018

March 27, 2018

Dear All, Please see the message below sent by Alan Greenberg that includes the information needed for the discussion on the KSK Rollover that will be held on today's ALAC call. This information is being sent via email due to the unavailability of an Adobe Connect Meeting Room. Kind regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png] From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Alan Greenberg Sent: Tuesday, March 27, 2018 12:16 PM To: ALAC <alac(a)atlarge-lists.icann.org> Subject: [ALAC] KSK Rollover on today's ALAC Agenda Here is my last try at summarizing things. What is wrong or missing? ----------------- What I am hearing (extrapolated) is: * Our community understands the need to roll the KSK but is divided on which path to follow at this point. * We want an intense awareness campaign including targetting ISPs, Telcos, Major industries. Use RIRs where they can identify potential DNS providers. * Information packet we can send to our community (ALSes, Individual Members) to get them to prompt their local ISPs or others and which can be similarly used by other constituencies within ICANN. * A holistic review of the situation (including a risk assessment of alternatives) in time for further discussion at ICANN62, including the then current state of whatever data is available and forecast of Sentinal availability. * We would like to better understand under what conditions a rollover date change is possible to avoid doing it at the end of a week.

1 0

Fellowship on today's ALAC Agenda
by ICANN At-Large Staff March 27, 2018

March 27, 2018

Dear All, Please see the message below sent by Alan Greenberg that includes the information needed for the discussion on the Fellowship Community Consultation that will be held on today's ALAC call. This information is being sent via email due to the unavailability of an Adobe Connect Meeting Room. Kind regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png] From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Alan Greenberg Sent: Tuesday, March 27, 2018 12:06 PM To: ALAC <alac(a)atlarge-lists.icann.org> Subject: [ALAC] Fellowship on today's ALAC Agenda 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 group's 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 group's 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

FW: [ALAC] GDPR on today's ALAC Agenda
by ICANN At-Large Staff March 27, 2018

March 27, 2018

Dear All, Please see the message below sent by Alan Greenberg that includes the information needed for the discussion on GDPR that will be held on today's ALAC call. This information is being sent via email due to the unavailability of an Adobe Connect Meeting Room. Kind regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png] From: ALAC [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Alan Greenberg Sent: Tuesday, March 27, 2018 11:50 AM To: ALAC <alac(a)atlarge-lists.icann.org> Subject: [ALAC] GDPR on today's ALAC Agenda 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?

1 0

REMINDER / Meeting Invitation: ALAC Monthly Call on Tuesday, 27 March 2018 at 21:00UTC
by ICANN At-Large Staff March 27, 2018

March 27, 2018

If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> with your preferred number. Please remember that it is now possible to connect your audio via the AC room, without using your telephone. You need a stable internet connection. If you would like a reminder of how to connect please let staff know. Si necesita una llamada a su telefono, por favor póngase en contacto con el personal de At-Large en staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> con su número preferido. Por favor, recuerde que es posible conectar el audio a través de la Adobe Connect, sin necesidad de utilizar su teléfono. Se necesita una conexión a Internet estable. Si desea un recordatorio de cómo conectar por favor que el personal sepa. Si vous avez besoin d'un dial-out, merci de le communiquer au personnel At-Large à staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> avec votre numéro d'appel préféré. Nous vous rappelons que vous pouvez désormais utiliser l'audio de l'Adobe Connect room afin de vous connecter sans utiliser votre ligne téléphonique. Il vous faut une connexion internet stable. Merci de nous confirmer votre participation et dial-out - si nécessaire - ainsi que votre numéro à: staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> *** Please note that Adobe Connect will NOT be used for this meeting as per Göran Marby’s blog<https://www.icann.org/news/blog/issues-with-adobe-connect-at-icann61> & more recently received blog<https://www.icann.org/news/blog/more-information-on-the-adobe-connect-issue> from Ashwin Rangan, SVP Engineering & Chief Information Officer. *** Dear All, The March ALAC Monthly Call is scheduled on Tuesday, 27 March 2018 from 21:00 - 23:00 UTC. For other times: https://tinyurl.com/y7f2w9bb The agenda and call details are available at: https://community.icann.org/x/zi28B Conference ID's: English: 1638 Spanish: 1738 French: 1838 Russian: 2138 Dial-in numbers: http://adigo.com/icann/ <http://adigo.com/icann/> If you are unable to attend the call please send an email indicating your absence and we will note this information on the agenda. If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [cid:image001.png@01D3C605.3E971060]

1 0

ICANN Newsletter -- 23 March 2018
by ICANN At-Large Staff March 27, 2018

March 27, 2018

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> Week ending 23 March 2018 ________________________________ Announcements This Week ICANN63 Fellowship Application Round Now Open[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 20 March 2018 Nomination Period for ICANN Multistakeholder Ethos Award Extended[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 20 March 2018 ICANN Community Onboarding Pilot Program Call for Nominations by SOs/ACs[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 19 March 2018 ________________________________ Upcoming Events [CANN 62 | Panama City] 25 – 28 June 2018: ICANN62 | Policy Forum – Panama City, Panama<https://meetings.icann.org/en/panamacity62> About ICANN ICANN Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Our bylaws are very important to us. They capture our mission of security, stability and accessibility, and compel the organization to be open and transparent. Learn more at www.ICANN.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…>. Strategic Plan, 2016 - 2020[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_planni…> ICANN FY18 Operating Plan and Budget[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_financ…>

1 0

Important - Available Travel Slots for ICANN62 in Panama
by ICANN At-Large Staff March 26, 2018

March 26, 2018

Dear All, The ALAC has several travel slots available for the ICANN62 meeting in Panama, 25-28 June 2018. There are two or more travel slots that will be allocated to At-Large participants who are ACTIVELY involved in some ICANN policy activity, or those with a strong history of such involvement in the past and an interest to restart. Those include gNSO or ccNSO PDPs, CCWGs, ALAC support Working Groups and the At-Large Review (with a lesser emphasis on the latter). Other slots may be opened due to other travellers not being able to attend or not requiring full funding. If you are interested in being considered for one of these travel slots, please complete the following survey: https://goo.gl/forms/E5iDK174rW2k9j3t1[goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_E5iDK174r…> We have a very short time in which to finalize our traveler list, so replies are due no later than 23:59 UTC on Tuesday, 27 March 2018. Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org[atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=D…> Facebook: facebook.com/icann[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…>atlarge[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icann…> Twitter: @[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…>ICANNAtLarge[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLar…> [nown.png]

1 0

UPDATE 1 / At-Large and GNSO Calls / Week of 26 - 30 March 2018
by ICANN At-Large Staff March 24, 2018

March 24, 2018

Dear All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 26 - 30 March 2018. UPDATE 1 Monday Cancelled: 23:00 UTC: LACRALO Monthly Call https://community.icann.org/x/yi68B Tuesday Cancelled: 16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag Monday 26 March 2018 None Tuesday 27 March 2018 18:00 UTC: EURALO Monthly Call https://community.icann.org/x/5i68B 21:00 UTC: ALAC Monthly Call https://community.icann.org/x/zi28B Wednesday 28 March 2018 None Thursday 29 March 2018 06:00 UTC: APRALO Monthly Call https://community.icann.org/x/9C68B 14:00 UTC: (GNSO) CCWG Auction Proceeds Call https://community.icann.org/x/yJXDAw 21:00 UTC: (GNSO) New gTLD Subsequent Procedures Sub Team – Track 2 https://community.icann.org/x/FwSbAw Friday 30 March 2018 None Please confirm your dial-out requests or apology notice to: For GNSO calls: GNSO Secretariats: gnso-secs(a)icann.org For At-Large calls or ALAC: staff(a)atlarge.icann.org For CWG IANA Stewardship: Brenda.Brewer(a)icann.org For CCWG on Enhancing ICANN Accountability: acct-staff(a)icann.org For CCWG-IG: desiree.cabrera(a)icann.org For WS2 Subgroup Topics or IOT calls : mssi-secretariat(a)icann.org Thank you! Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/@ICANNAtLarge> [cid:image001.png@01D3C389.272B95A0]

1 0

At-Large and GNSO Calls / Week of 26 - 30 March 2018
by ICANN At-Large Staff March 23, 2018

March 23, 2018

Dear All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 26 - 30 March 2018. Monday 26 March 2018 23:00 UTC: LACRALO Monthly Call https://community.icann.org/x/yi68B Tuesday 27 March 2018 16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag 18:00 UTC: EURALO Monthly Call https://community.icann.org/x/5i68B 21:00 UTC: ALAC Monthly Call https://community.icann.org/x/zi28B Wednesday 28 March 2018 None Thursday 29 March 2018 06:00 UTC: APRALO Monthly Call https://community.icann.org/x/9C68B 14:00 UTC: (GNSO) CCWG Auction Proceeds Call https://community.icann.org/x/yJXDAw 21:00 UTC: (GNSO) New gTLD Subsequent Procedures Sub Team – Track 2 https://community.icann.org/x/FwSbAw Friday 30 March 2018 None Please confirm your dial-out requests or apology notice to: For GNSO calls: GNSO Secretariats: gnso-secs(a)icann.org For At-Large calls or ALAC: staff(a)atlarge.icann.org For CWG IANA Stewardship: Brenda.Brewer(a)icann.org For CCWG on Enhancing ICANN Accountability: acct-staff(a)icann.org For CCWG-IG: desiree.cabrera(a)icann.org For WS2 Subgroup Topics or IOT calls : mssi-secretariat(a)icann.org Thank you! Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/@ICANNAtLarge> [cid:image001.png@01D3C2B7.FC4DD7C0]

1 0