- Gnso-epdp-team - lists.icann.org

Suggestion to facilitate writing and review replacement language for Section 4.4
by Mark Svancarek (CELA) Aug. 31, 2018

Aug. 31, 2018

Dear Kurt and Team: To get us started on the daunting task of drafting replacement language for Section 4.4 of the Temp Spec, we propose to split the processing topics of section 4.4 into categories which parallel the structure of GDPR. The two processing categories we propose are: 1. Those which support the purposes of controllers and others related to the performance of their contracts (registrars, registries, and ICANN) 2. Those which support the purposes of third parties under applicable legal grounds (performance of contract, consent, and legitimate interest) Some items in Section 4.4 of the existing Temp Spec will apply to both categories; some will apply to only one. Even when an item applies to both categories, we propose to discuss the appropriate language separately and in the context of the specific category only. By removing conflation of purposes between parties, this split will facilitate discussion and lead to a more productive drafting process. Further discussion will determine whether ICANN needs to be uniquely broken into its own third category, or whether this two-way split will suffice. A "strawman" breakdown is as follows: Section of existing Temp Spec Processing to achieve the purposes of Controllers Processing to achieve the purposes of Third Parties 4.4.1 Yes - 4.4.2 Yes Yes 4.4.3 Yes Yes 4.4.4 Yes - 4.4.5 Yes Yes 4.4.6 Yes - 4.4.7 Yes - 4.4.8 Yes Yes 4.4.9 Yes Yes 4.4.10 Yes Yes 4.4.11 Yes - 4.4.12 Yes Yes 4.4.13 Yes - /marksv

1 0

FW: [Ext] ICANN News Alert -- ICANN Releases its Second Report on Global Legislative and Regulatory Developments
by Marika Konings Aug. 31, 2018

Aug. 31, 2018

For your information. From: ICANN News Alert <no-reply(a)external.icann.org> Reply-To: "no-reply(a)external.icann.org" <no-reply(a)external.icann.org> Date: Thursday, August 30, 2018 at 17:46 To: Marika Konings <marika.konings(a)icann.org> Subject: [Ext] ICANN News Alert -- ICANN Releases its Second Report on Global Legislative and Regulatory Developments [ICANN][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-08-30-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ ICANN Releases its Second Report on Global Legislative and Regulatory Developments 30 August 2018 ISTANBUL - 30 August 2018 - The Internet Corporation for Assigned Names and Numbers (ICANN) published today the second report [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 214 KB] l highlighting a limited list of recent and pending legislative and regulatory initiatives on privacy/data protection and cybersecurity across the world. The report is a continuation of the initiative launched earlier this April, to identify legislative efforts across the globe early-on to raise awareness within ICANN and consider potential impacts, including how these legislative initiatives may have unintended consequences, which may be avoided. As a result of the community discussions over the past year or so leading up to the GDPR going into full effect, ICANN CEO and President Göran Marby committed to identify key legislative efforts around the globe while in their earlier stages. To this end, ICANN org initiated [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> reporting efforts on global legislative and regulatory developments during the third quarter of FY18. The first report [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 97 KB] was a limited list of some recent legislative and regulatory initiatives around the world that relate to privacy/data protection and cybersecurity issues and that could impact ICANN's mission, operations or issues within ICANN's remit. It was the first product of a realization that ICANN, as both an org and a community, must pay closer attention to potential legislative efforts of interest across the world. The initial report received wide attention with a viewership of over six hundred unique visits. The community feedback on the report was positive, which paved the way for the continuation of the report on a quarterly basis. We would like to take this opportunity to thank everyone who has reviewed and provided feedback on the first report. We look forward to hearing from you about any high-impact developments in the e-privacy and cybersecurity ecosystem that should be tracked in future reports. You can send your comments and/or information about new developments in your region to trackingfeedback(a)icann.org<mailto:trackingfeedback@icann.org>. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to 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 and a community with participants from all over the world. Manage Your Subscription [app.icontact.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__app.icontact.com_icp_mm…> This message was sent to marika.konings(a)icann.org from no-reply(a)external.icann.org ICANN News Alert ICANN 12025 Waterfront DriveSuite 300 Los Angeles, CA 90094-2536 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [iContact - Try it for FREE][icontact.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icontact.com_signu…>

1 0

Notes and action items from today's EPDP Team Meeting - 30 August 2018
by Caitlin Tubergen Aug. 31, 2018

Aug. 31, 2018

Dear All, Below, please find notes and action items from today’s EPDP Team Call. As a reminder, our next meeting will be Tuesday, 4 September, 13:00 UTC. Best regards, Marika, Berry, and Caitlin EPDP Team Meeting #9 Thursday, 30 August 2018 High-Level Notes and Action Items Regarding progress on the Purposes for Processing Data: Registrars will rewrite section 4.4 to align the purposes for data processing with current data collection processes and the domain name lifecycle. It is requested that the draft be completed in time for the meeting on Tuesday, 4 Sept so that the rest of the team can review it. For sections 4.4.2, 4.4.8 and 4.4.9, it was agreed to take those purposes for accessing data out from under the heading, “Purposes for Processing Data” and place it in another section of the Policy that is being developed. The Support Team will recommend alternatives for identifying those access needs in the new Policy in time for the 4 September meeting. The support team will facilitate the creation of a team to consider a re-drafting of section 4.4.8. Several team members volunteered to participate, and Alex Deacon and Amr Elsadr volunteered to lead. The Support Team will develop the time requirements for this team to finish its work, taking into account the project plan and delivery requirements. The team will have a “narrow remit,” i.e., to draft the purpose for data disclosure for the reasons set out in section 4.4.8. Regarding other sub-sections of 4.4 the following team members offered to propose revised language for the below-mentioned sections: § 4.4 (introductory paragraph): Alex Deacon § 4.4.2: Amr Elsadr § 4.4.9: Ashley Heineman, Kavouss Arasteh Regarding Appendix C, Data Processing Requirements: Alan Woods will provide a draft recommendation to ICANN that the subject matter be taken out from consideration by this group and folded into current CPH-ICANN negotiations regarding registration data elements of the RAA and RA. This writing should address Margie’s intervention that certain elements of Appendix C remain under the purview of this group, e.g., Disclosure of non-public RDDS/WHOIS to third parties. Additionally, Alex Deacon will compose amendments to Appendix C, section 2, Lawfulness of Processing, that includes all GDPR mechanisms that allow processing of data. Other items: Support Team to adapt Thomas’s spreadsheet to aid in future discussion of data elements. We will also re-affirm the timing of this discussion to ensure it is prioritized. Question for ICANN Org: Language in the preamble is similar but different from the GDPR. What was the thinking in writing it this way? Notes These high-level notes are designed to help the EPDP Team navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/2IpHBQ. 1. Roll Call & SOI Updates Attendance will be taken from Adobe Connect Please remember to mute your microphones when not speaking, and state your name before speaking for transcription purposes. Please remember to review your SOIs on a regular basis and update as needed. Updates are required to be shared with the EPDP Team. 2. Welcome and Updates from EPDP Team Chair Triage report - planning to create an updated, truncated version of the report to be distributed shortly Please ensure that any chat during the meeting is relevant to the discussion and does not distract from the speaker. 3. Review proposed next steps and action items on 4.4 a. Consider any input form the EPDP team that would include specific recommendation for amendments to the temporary specification for: 1. Registrar / Registry / ICANN processing of data: clarifying the elements proposed in the ICANN-developed specification 2. Third party processing where more specificity was requested At the end of the preamble, some suggested the text, "and only for the following legitimate purposes", may be unduly restrictive because of (1) potential new privacy laws in the future; and (2) updated advice from courts/DPAs. Accordingly, a proposed tweak may be, "and for legitimate interests not outweighed by the fundamental rights of relevant data subjects, consistent with GDPR." Feedback from EPDP Team: The point of the comment is when only focusing on legitimate interests, we are leaving out other lawful processing described in Article 6(1) of the GDPR - such as 6(1)(b), 6(1)(c), and 6(1)(f). Action item: Alex to propose updated language. Problem with 4.4.2 and 4.4.8 and 4.4.9 is that this is an access issue, not an ICANN purpose issue. The legitimate interest list is trying to incorporate third party legitimate interests into purpose definitions. If you try to accommodate access concerns by incorporating this into ICANN purposes, this is making the conflation DPAS explicitly warned against. Accordingly, this needs to be separated. If these sections are not in the correct part of the Temp Spec, where would these sections go? These sections appropriately belong in the access section. Clarifying question: we transitioned out of the welcome message into the substantive discussion. We are beginning on a wording issue, seemingly based on triage comments. What is the objective here? Are we trying to edit 4.4 and 4.4.2? This was an experiment is see if the language was an easy fix the team could agree to. It appears we are commingling purposes and legitimate interests for access, and we can explore separating these sections. We cannot provide access later, unless we have the data to start with. We may need to lower the rhetoric -- comments like "we will never agree to something" is unhelpful for forward progress. When we speak of data processing, we do not have to go through what a legitimate interest is. For data processing, we need to come up with what we mean by data processing at this stage. Are we talking about data collection? If so, this needs to be very narrowly defined - it needs to be based on ICANN's mission and purpose. Re: Thomas' email which mentions slicing and dicing, there are paths to obtain information. We must remember that payment information is collected for other registrar/registry purposes. We have to make a distinction making access to the data separate. We should focus now on collecting/processing of the data, and put access aside for now. We may need to add a few qualifiers to the text, such as ICANN's legal basis for processing this data. When we’re looking at bylaws references in the Temp Spec and any successor, we need to look at what the bylaws actually say and what they mean. This entire section appears to be hastily written. We might consider rewriting this from scratch, rather than tweaking current language. In the previous meeting and here, we need to bifurcate the sections in 4.4 et. seq. and create the first list for data processing for Ry/Rr. In reading through the triage comments, registrars frequently objected to this section, as there is a set of data collected for the purpose of dealing with the registrant, and this list may not be the correct list for dealing with these issues. Instead, we might consider rewriting this entire section to better align with Ry/Rr purposes. Kurt asked contracted parties to come up with a better way of looking at this type of data. Action item: Registrars to to rewrite section 4.4 in an attempt to align the text with actual business practices. The Temp Spec was written as a reaction to GDPR. It’s not written as policy recommendations. The intent here was to bolt on GDPR compliance to the existing system. Taking what is there and redlining it will be an unsuccessful endeavor. The starting point here is to make sure the entire group has a common understanding of what it means to deliver the service of a domain name registration to a registrant, as that will be the starting point of the purposes. There may be other purposes involved, but the first purpose is the delivery of the service of a domain name registration to a registrant. What clarification or direction is needed from the EPDP team for registrars to move forward with a conversation with your stakeholder group? Registrars will put pen to paper and circulate to the group. Perhaps we do not start with purposes, we start with what it means to deliver the service to avoid the problems the RDS group experienced. Re: ICANN Contractual Compliance, what does this mean, and what activities are involved? Like a third party, ICANN would have to demonstrate a legal basis to access this information. ICANN is a data controller, and ICANN collects data from contracted parties based on the RA and RAA. ICANN just needs to vet out their purposes and their legal basis to access this information. ICANN has solid purposes, but they need to be clear in what those purposes are. ICANN as a controller and as a party to the contract has a performance of contract purpose that is under GDPR. It is written in the bylaws and a commitment ICANN made during the transition. It is inappropriate to limit what ICANN can get access to for the purposes of enforcing the contract. We talked about whether ICANN has access to the data, and I believe the Temp Spec took away ICANN’s right to thick WHOIS, but only thin WHOIS. The Temp Spec did remove thick data transition, but that data is part and parcel of our discussions. There is still disagreement over § 4.4.8. This data disclosure does not belong under the purposes. Should the group rewrite these access questions? Where in our policy should these sections go so that we can preserve this right away? One option would be to move it to Appendix A, Section 4. Thinking about earlier comments, we may want to consider using a tool such as Thomas’s spreadsheet or concrete input from Rys/Rrs, and other groups would assist in drafting something so that when we come together next time, we are focused on specifics. The spreadsheet deals with data elements that support each purpose. Thoughts on path forward – flesh out purposes of data processing first and then identify data required to fulfill those purposes. If we can get the feedback from the RrSG to furnish the aforementioned homework quickly, we can move to the discussion on data elements shortly. Action: Alex as lead to clarify 4.4 Action: GAC as lead to rewrite section 4.4.9 We do not have a framework for investigation of cybercrime. We do have an obligation to support investigation of cybercrime, but it is not our framework, and this is an overreach in Section 4.4.8. This needs to be separated out and reworded. This discussion appears to be jumping around a bit. How are we going to reach a final product? Our end goal here is policy recommendations. Ad hoc debate of various sections of the temp spec may not help us reach our end goal. We’re talking about Section 4.4 today because we agreed to talk about purposes for processing first. However, we can use a spreadsheet as a tool to have a concrete discussion about data. To close this out, for third party uses of data, does anyone think these need to be adjusted? 4. Begin discussion on Appendix C For each section, we will refer to the Triage survey and meeting comments as a guide for considering to amend the specification section. We might then form a rough consensus for the content of edits and assign a small team (1-3) people to create a revised version for the next meeting. Breaking the Appendix into its parts: a. Preamble EPDP Team Feedback: Appendix C includes a chart which includes gTLD processing activities We can guide the discussion of what was capture in the triage EPDP Team Feedback: Amend the preamble, then amend the table. Take these in order. In reference to the preamble, some of the comments note that restating the GDPR (but not precisely) is not helpful. Should this match the GDPR, or should it be removed? Question for ICANN Org: Language in the preamble is similar but different from the GDPR. What was the thinking in writing it this way? Perhaps this should be handed back to ICANN Legal for review – send the chart back to ICANN and have that married with the other discussion on what other processing needs to take place. Should this be examined with the domain name lifecycle as a reference? When you put a point on discussion in the debate, it would be helpful to have one or two leads to put pen to paper and then share with the group for discussion. b. gTLD Processor Activity Chart c. Section 1 (Principles for Processing) Section 2 (Lawfulness of Processing) EPDP Team Feedback: Should the reference to applicable laws and regulations be removed? Should Section 1 in principles for processing might include principles from GDPR other than 6.6? Should it reference data principles more broadly? In Section 2, should there be an LEA carve out for the balancing test? Should we go back once we have agreed upon legitimate interests, should we go do an Article 4 code of conduct referral? How do we move this forward? Should we post these questions online and ask for responses? Proposal to change each controller “shall observe” instead of “will observe” On Section 2, it focuses on legitimate process and does not include other lawful purpose, so it needs to be changed similar to Section 4. The LEA carve out could then be removed. We have to have a discussion on the critical part – we are allowed to consider the needs of others if we have a justification. Are we allowed to look at others’ needs in WHOIS or not? There seems to be a copy/paste of Article 28 of the GDPR. This should be a suggestion to the GNSO that it should be added to the contract, not in here. This is a contractual matter and should not be in the policy. The feedback is not that we not consider other legitimate interest, but rather, to not conflate the legitimate interests of third parties with ICANN’s purposes. This Appendix may not be necessary once the agreement is re-negotiated with the contracted parties, though certain elements may still be necessary. It is not that we cannot consider third party interests, it is that they should not be conflated with ICANN’s interests. The fact that we take third party interests in the data into consideration does not mean that we collect data with third party interests in mind. Cooperation is the key here. · d. Deliberate on Sections 3.1, 3.1.1 – 3.1.6 (Specific Controller Processing requirements) e. Deliberate on 3.2 – 3.11 (Specific Controller Processing requirements) Discuss next steps for dealing with input on Appendix C 5. Confirm action items and questions for ICANN Org, if any Question for ICANN Org: Language in the preamble is similar but different from the GDPR. What was the thinking in writing it this way? 6. Wrap and confirm next meeting to be scheduled for Tuesday 4 September at 13.00 UTC.

3 4

Recordings, Attendance & AC chat from the GNSO Temp Spec gTLD RD EPDP held Thursday, 30 August 2018
by Andrea Glandon Aug. 30, 2018

Aug. 30, 2018

Dear all, Please find the attendance and AC chat attached to this email. The MP3 and AC recording below from the GNSO Temp Spec gTLD RD EPDP call held on Thursday, 30 August 2018 at 13:00 UTC. These have also been posted on the agenda wiki page: MP3: https://audio.icann.org/gnso/gnso-epdp-gtld-registration-data-specs-30aug18… <https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> AC Recording: https://participate.icann.org/p7roeo6r513/<https://participate.icann.org/p7roeo6r513/?OWASP_CSRFTOKEN=1878425a032e0b15…> ** Please let me know if your name has been left off the list ** Mailing list archives of the GNSO Temp Spec gTLD RD EPDP : https://mm.icann.org/pipermail/gnso-epdp-team/ Main wiki page for the working group: https://community.icann.org/x/IYEpBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you. Kind Regards, Andrea Glandon

1 0

Meeting Invitation / Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Tuesday, 04 September 2018 at 13:00 UTC
by Andrea Glandon Aug. 30, 2018

Aug. 30, 2018

Dear all, Non-members can follow the EPDP call taking place on Tuesday’s and Thursday’s at 13:00 UTC via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Agenda wiki page: https://community.icann.org/x/0gONBQ Kind Regards, Andrea Glandon

1 0

Project plan posted on wiki
by Marika Konings Aug. 30, 2018

Aug. 30, 2018

Dear All, Several of you asked about the project plan – the latest version has now been posted on the related wiki page: https://community.icann.org/x/2opHBQ. As further updates may be made over time, any updates will be posted on this page. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Slicing and dicing
by Thomas Rickert Aug. 30, 2018

Aug. 30, 2018

All, A few points below that I committed to send to the list. Data matrix During our last call, we have discussed a proposed methodology to slice and dice the work and document what data elements can be processed for what purpose based on what legal basis with what rationale. I have attached an attempt to capture that. This only covers the framework for capturing the collection of data by the registrar and the transfer from registrar to registry. The table would need to be extended to cover the additional processing activities, but at this stage it shall serve only to illustrate an approach where we could all feed our ideas into one document with a level of granularity that prevents us from conflating issues. 4.4.8. Also, when we discussed 4.4.8. I proposed we also discuss the purpose in concrete terms. Milton asked me to give an example. 4.4.8 reads: Supporting a framework to address issues involving domain name registrations, including but not limited to: consumer protection, investigation of cybercrime, DNS abuse, and intellectual property protection only. Many in the group think this is too broad. So let’s take IP protection. If the purpose included the publication of all data of potential cybersquatters, including their payment data to allow for investigators to do their work efficiently, I think we would all agree that that would go too far. Yet, one could think that such action was covered by the purpose of 4.4.8.. On the other hand, if in the case of a UDRP proceeding, the data of the registrant shall be disclosed to the dispute resolution provider, we would probably (not to say hopefully) all agree that this would be fine. So my plea is that when we are talking about all those issues that could fall under 4.4.8. - let’s come up with concrete suggestions as to what the parties involved are supposed to do. We should all put some thought into that. What shall be done in the area of consumer protection e.g.? Are we talking about collection of additional data elements? Disclosing them to third parties? Retaiing them for a longer period? In other work, what could or should consumer protection entail in the gTLD world? Same for the other aspects in 4.4.8. Playbook Mark asked during the last call to send a link to the eco Playbook. Here it is: eco GDPR Domain Industry Playbook <https://www.eco.de/wp-content/uploads/2018/02/eco-domain-industry-playbook-…> We have gone through a lot of the exercises that this group will need to go through, so I encourage you to take a look at it. Maybe we can reuse parts of it to expedite our work. Don’t get me wrong - I am not trying to sell you the approach in the Playbook, but I think it can be a good basis to argue over certain questions. Finally, I happen to be one of the authors. The good sentences have likely been written by others. The things you might not like surely come from me. Best, Thomas

6 6

Proposed Agenda - EPDP Team Meeting #9 - 30 August at 13.00 UTC
by Caitlin Tubergen Aug. 29, 2018

Aug. 29, 2018

Dear All, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday, 30 August at 13.00 UTC. Additionally, please find the discussion summary index for Appendix C attached. Best regards, Marika, Berry, and Caitlin EPDP Meeting #9 Agenda Thursday, 30 August 2018 Roll Call & SOI Updates Welcome and Updates from EPDP Team Chair Review proposed next steps and action items on Section 4.4 - Lawfulness and Purposes of Processing gTLD Registration Data For Registrar-Registry-ICANN Contract Purposes (for collection), all, but registrars specifically, are asked to provide input on whether there are additional legitimate reasons why ICANN may need to require contracted parties to collect data from registrants? Should these purposes be re-grouped in some way to better capture their relevance, necessity and the data needed to support them? For Third Party Purposes (for access), the EPDP Team is expected to weigh in on whether the purposes enumerated here are valid and legitimate? Do those purposes have a corresponding legal basis? Do these purposes need to be reviewed for clarity? Note that any discussion on the safeguards and limitations in relation to access necessary to ensure GDPR compliant disclosures would happen after the gating questions have been answered. Once step 2 and 3 have been completed, the EPDP Team will need to review how this separation of purposes is to be reflected in 4.4 and what updates, if any, need to be made to the preceding sections (4.1 – 4.3), if these are still deemed necessary and relevant in light of the separation. Begin review of data elements table Begin discussion on Appendix C – Data Processing Requirements Deliberate on Preamble Deliberate on Section 1 (Principles for Processing) Deliberate on Section 2 (Lawfulness of Processing) Deliberate on Sections 3 – 3.1.6 (Specific Controller Processing requirements) Deliberate on 3.2 – 3.7 (Specific Controller Processing requirements) Deliberate on Sections 3.8 – 3.11 (Specific Controller Processing requirements) Discuss next steps for dealing with input on Appendix C Confirm action items and questions for ICANN Org, if any Wrap and confirm next meeting to be scheduled for Tuesday, 4 September at 13.00 UTC.

2 1

ALAC Early Input
by Alan Greenberg Aug. 29, 2018

Aug. 29, 2018

The ALAC wishes to support SAC 101 as submitted by the SSAC and as noted on https://community.icann.org/display/EOTSFGRD/Request+for+Early+Input+-+1+Au…. Alan

1 0

***REMINDER*** Meeting Invitation / Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Thursday, 30 August 2018 at 13:00 UTC
by Julie Bisland Aug. 29, 2018

Aug. 29, 2018

Dear all, Non-members can follow the EPDP call taking place on Tuesday’s and Thursday’s at 13:00 UTC via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Agenda wiki page: https://community.icann.org/x/VRhpBQ Kind Regards, Andrea Glandon

1 0