July 2018 - ALAC-Announce - lists.icann.org

Call for comments
by Alan Greenberg July 12, 2018

July 12, 2018

As I hope you are all aware, due to the European General Data Protection Regulations (GDPR), access to some gTLD Domain Name registrant information (WHOIS) is being restricted. Traditionally, for a registrant who did not use a proxy service a WHOIS Query would reveal their full name, address, phone number and e-mail address. If you do a lookup for one of my addresses today you will see almost nothing! Try looking up alangreenberg.org at https://whois.icann.org. This increases privacy for some registrants and also makes information harder to access for those who currently use WHOIS. There are serious monetary fines associated with GDPR, so compliance is important. In addressing the new regulations, there has been a lot of discussion within ICANN over the last year. A GNSO Policy Development Process (PDP) started about 2 years ago which should have provided a new system (now called a Registration Directory Service (RDS) instead of WHOIS), but unfortunately that process has not completed in sufficient time. As a result, to meet the GDPR deadline of 25 May 2018, the ICANN Board implemented a Temporary Specification Policy to allow us and our contracted parties (Registrars and Registries) to be GDPR-compliant. That temporary policy must be replaced by a permanent one within one year - a VERY short time for ICANN policy development. The GNSO is starting an Expedited PDP which can complete faster than a regular PDP. The ALAC is being given two Members in the this group. We need to establish what our guiding principles are. Please visit https://community.icann.org/x/_YlHBQ, read what others think, and contribute your thoughts on what positions we should be taking. Alan

1 0

Re: [ALAC-Announce] Call for Volunteers: GNSO Expedited PDP on Temporary Specification for gTLD Registration Data
by Alan Greenberg July 12, 2018

July 12, 2018

Please note that as expected, the Criteria have been revised. Also, a new Required Statement of Participation has been added. See https://community.icann.org/x/yYlHBQ. The ALAC Quota has been reduced from three Members and three Alternates to two of each. The EoI application period closes in about 27 hours Alan At 10/07/2018 07:51 PM, Alan Greenberg wrote: >In light of the European General Data Protection Regulations (GDPR), >the ICANN Board enacted a temporary policy governing WHOIS (now know >as Registration Data) effective 25 May 2018. This temporary policy >must be replaced by a permanent policy within one year. To take this >action, the GNSO has initiated and Expedited Policy Development >Policy. The Charted for this process is expected to be approved by >the GNSO on 19 July 2018, and a group convened to develop the policy >will be convened soon after. > >Although the membership quotas of this group will not be >definitively known until the charter is approved, at this point we >expect that the ALAC will be given three Members and three >Alternates. It is expected that Alternates may only actively >participate if a Member is not available, but would be expected to >be prepared to participate if needed. > >Members and Alternates representing the ALAC will work as a team to >develop an ALAC position and strive to appropriately effect the >policy effort. There will be regular consultation with the ALAC and At-Large. > >Since the policy must be in place by 25 May 2019, it is expected >that a draft policy will be prepared in time for the ICANN63 meeting >in late October 2018. > >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. >The GNSO is also setting some very specific criteria for >participation. Although the list may change, the current >requirements are as follows: > > * 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; > * 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; > * Commit to build consensus on issues within the scope of this EPDP; > * 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; > * Solicit and communicate (where appropriate) the views and > concerns of individuals in the group that appoints them; > * Commit to abide to the charter when participating in the EPDP Team; > * Understand the needs of the Internet communities that ICANN > serves (standards, domains and numbers); > * Commit to attend any provided introductory training courses, > e.g., privacy, trademarks, registrar operations, DNS, etc. > * Understand the broader ecosystem (the Internet Community) in > which ICANN operates and the needs of those working on other > aspects of the Internet industry. > >Membership and participation will be on behalf of the ALAC and not >representing personal views. > >Expressions of Interest will be accepted until 23:59 UTC on Friday, >13 July 2018. > >The EoI may be found at https://tinyurl.com/ALAC-EPDP-EoI. If you >complete the EoI more than once, the last version will be the one used.

1 0

Sunday, July 15: Call for Comments: Draft Community Travel Support Guidelines
by ICANN At-Large Staff July 12, 2018

July 12, 2018

Dear All, Please note the first draft ALAC Statement on Draft Community Travel Support Guidelines<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> is ready for your review. Please comment by Sunday, 15 July 2018. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/hCkFBQ. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function. You will need to log in to the wiki to use the comment function. If you don’t have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. 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_2106689505]

1 0

Call for Comments: Draft Proposal of the New Fellowship Program Approach
by ICANN At-Large Staff July 12, 2018

July 12, 2018

Dear All, Please note the first draft ALAC Statement on Draft Proposal of the New Fellowship Program Approach<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> is ready for your review. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/FYMpBQ. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function. You will need to log in to the wiki to use the comment function. If you don’t have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. 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_933407407]

1 0

ICANN News Alert -- Root Server System Advisory Committee Review: Final Report Now Available
by ICANN At-Large Staff July 11, 2018

July 11, 2018

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2018-07-10-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Root Server System Advisory Committee Review: Final Report Now Available 10 July 2018 LOS ANGELES – 10 July 2018 – Today, Interisle Consulting Group, LLC, the independent examiner performing the second Root Server System Advisory Committee (RSSAC) Review, published its final report. Read the report [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 2.58 MB]. The final report includes an assessment of the RSSAC with eight principal findings and six principal recommendations for improving its operations. The recommendations focus on RSSAC purpose, effectiveness, and accountability. The final report published today considers comments on the draft final report published [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> on 1 May 2018, input provided during the public webinar [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> on 9 May 2018 and any other feedback Interisle may have received. Next Steps The RSSAC Review Work Party [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> (RWP) will prepare a feasibility assessment and initial implementation plan (FAIIP) based on the final report. This will include an analysis of recommendations in the final report for usability and prioritization, provisional budget implications, anticipated resources and the proposed implementation timeline. Interisle and the RWP respectively will then present the final report and the FAIIP to the ICANN Board's Organizational Effectiveness Committee (OEC). The OEC will make a recommendation to the Board on next steps. Background An independent review of the RSSAC is mandated by ICANN's Bylaws [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> and is part of ICANN's commitment to its own evolution and improvement, accountability and transparency. Interisle was selected to perform the review and began its work in September 2017 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…>. The purpose of the RSSAC review, according to the Bylaws, is to determine (i) whether the RSSAC has a continuing purpose in the ICANN structure, (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness and (iii) whether the RSSAC is accountable to its constituencies, stakeholder groups, organizations and other stakeholders. The review also includes an assessment of the implementation state of RSSAC's prior review [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 234 KB]. Additional Resources * Visit the RSSAC Review wiki [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> and the RSSAC Review page on ICANN.org [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> for more information and resources related to the review. * Visit the RSSAC page on ICANN.org [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_groups_r…> to learn more about the RSSAC. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

1 0

Call for Volunteers: GNSO Expedited PDP on Temporary Specification for gTLD Registration Data
by Alan Greenberg July 10, 2018

July 10, 2018

In light of the European General Data Protection Regulations (GDPR), the ICANN Board enacted a temporary policy governing WHOIS (now know as Registration Data) effective 25 May 2018. This temporary policy must be replaced by a permanent policy within one year. To take this action, the GNSO has initiated and Expedited Policy Development Policy. The Charted for this process is expected to be approved by the GNSO on 19 July 2018, and a group convened to develop the policy will be convened soon after. Although the membership quotas of this group will not be definitively known until the charter is approved, at this point we expect that the ALAC will be given three Members and three Alternates. It is expected that Alternates may only actively participate if a Member is not available, but would be expected to be prepared to participate if needed. Members and Alternates representing the ALAC will work as a team to develop an ALAC position and strive to appropriately effect the policy effort. There will be regular consultation with the ALAC and At-Large. Since the policy must be in place by 25 May 2019, it is expected that a draft policy will be prepared in time for the ICANN63 meeting in late October 2018. 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. The GNSO is also setting some very specific criteria for participation. Although the list may change, the current requirements are as follows: * 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; * 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; * Commit to build consensus on issues within the scope of this EPDP; * 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; * Solicit and communicate (where appropriate) the views and concerns of individuals in the group that appoints them; * Commit to abide to the charter when participating in the EPDP Team; * Understand the needs of the Internet communities that ICANN serves (standards, domains and numbers); * Commit to attend any provided introductory training courses, e.g., privacy, trademarks, registrar operations, DNS, etc. * Understand the broader ecosystem (the Internet Community) in which ICANN operates and the needs of those working on other aspects of the Internet industry. Membership and participation will be on behalf of the ALAC and not representing personal views. Expressions of Interest will be accepted until 23:59 UTC on Friday, 13 July 2018. The EoI may be found at https://tinyurl.com/ALAC-EPDP-EoI. If you complete the EoI more than once, the last version will be the one used.

1 0

ICANN Newsletter -- 6 July 2018
by ICANN At-Large Staff July 10, 2018

July 10, 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 6 July 2018 ________________________________ Announcements This Week Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4) [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 3 July 2018 Expressions of Interest Sought for Chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 2 July 2018 ________________________________ Upcoming Events [CANN 62 | Panama City] 20 – 25 October 2018: ICANN63 | Annual General – Barcelona, Spain<https://meetings.icann.org/en/barcelona63> 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 FY19 Operating Plan and Budget [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>

1 0

VOTE ANNOUNCEMENT: ALS Application (284) Red ElDerechoInformatico
by ICANN At-Large Staff July 9, 2018

July 9, 2018

Dear All, The regional advice from LACRALO regarding the ALS Application (284) Red ElDerechoInformatico has been received. The following question has been posed to the ALAC: ***** Question: Does the ALAC wish to accredit the ALS Application (284) Red ElDerechoInformatico? The regional advice was to accept the application. ***** Please note that this vote will close 16 July 2018 23:59 UTC. 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_11531860]

1 0

Meeting Invitation: ALAC Monthly Call on Tuesday, 24 July 2018 at 21:00 UTC
by ICANN At-Large Staff July 9, 2018

July 9, 2018

Dear All, The July ALAC Monthly Call is scheduled for Tuesday, 24 July 2018 from 21:00 – 23:00 UTC. For other times: https://tinyurl.com/ycdtcd9r The agenda (to be updated) and call details are available at: https://community.icann.org/x/woRHBQ Conference ID’s: English: 1638 Spanish: 1738 French: 1838 Russian: 2138 Dial-in numbers: 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<applewebdata://037026B5-B5A1-4167-985F-406A347D8A0E/staff@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> 

1 0

REMINDER - New Public Comment: ICANN Seeking Community Feedback on Proposed Unified Access Model
by ICANN At-Large Staff July 9, 2018

July 9, 2018

Dear All, This is a reminder that the Public Comment on the ICANN Seeking Community Feedback on Proposed Unified Access Model<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+ICA…> is live. Public comment is requested as soon as possible. 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/wwA5BQ. All pertinent resources can also be found there. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/12105. 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_272506430]

1 0