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

**Reminder** Meeting Invitation: Observers GNSO Temp Spec gTLD RD EPDP - Phase 2 call / Tuesday, 13 August 2019 at 14:00 UTC
by Julie Bisland Aug. 12, 2019

Aug. 12, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Tuesday, 13 August 2019 at 14:00 UTC for 90 minutes. 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Wednesday) 00:00 Melbourne AEST For other times: https://tinyurl.com/y2gfw3rq [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y2gfw3rq&d…> Agenda Wiki: https://community.icann.org/x/14LkBg The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> Meeting Audio Cast (for observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream02 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> If needed, an option to join via telephone has been added for this meeting. Passcode: EPDP Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL RIO DE JANEIRO: 55-21-40421490 0800-7610651 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751 Thank you. Kind Regards, Terri

1 0

upcoming use case review
by Sarah Wyld Aug. 9, 2019

Aug. 9, 2019

Hello team, We want to clarify the order in which the use cases will be reviewed, so that our team can work in advance to get comments ready to go before our plenary meetings. In the attached doc, we see that first readings of IP5 and SSAC1 are both set for August 15, however it's a bit confusing because IP5 is also set for a second reading on August 15. Could Staff please provide an updated calendar for use case review? Also, the IP5 use case on the EPDP team wiki <https://community.icann.org/display/EOTSFGRD/d.+Use+Cases?preview=/11138687…>seems to be a blank template, could that be updated to show the correct use case doc? Thanks -- Sarah Wyld Domains Product Team Tucows +1.416 535 0123 Ext. 1392

3 2

Re: [Gnso-epdp-team] Experts for the lunch time presentations during the LA f2f meeting
by LEWIS-EVANS, Christopher Aug. 9, 2019

Aug. 9, 2019

OFFICIAL Mark I think it would be helpful before if you can make it happen as then it will give everyone the ability to get more information for the face to face. We all used to be free on a Tuesday so how about a webinar the Tuesday before the face to face? Thanks Chris From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org] On Behalf Of Mark Svancarek (CELA) via Gnso-epdp-team Sent: 07 August 2019 23:25 To: gnso-epdp-lead(a)icann.org; 'EPDP' Subject: Re: [Gnso-epdp-team] Experts for the lunch time presentations during the LA f2f meeting (resending to correct list) Thanks to everyone for your feedback. The impetus for a DCU presentation came from a (very) brief exchange between myself and Farzi at the end of a recent meeting. We considered that since we encounter questions which can’t be answered during a meeting (e.g. “How does a Doe suit proceed and why is it problematic to a particular use case?”), it would be helpful to interact with a subject matter expert able to answer the many questions we all have regarding these investigations in the real world. I admitted at the time that it might not be popular due to our time constraints, but that I could make it happen at some TBD future date if we collectively agreed that it would be valuable. Along the way, it turned into a proposal tied to the LA face-to-face meeting, which in retrospect wasn’t a great idea. The remaining alternatives are a webinar (before or after LA) or a presentation/Q&A during a regularly scheduled THU meeting a la Steve Crocker’s BBQ presentation – or to drop the idea entirely. Of these, I think the webinar idea is best, if we can find a timeslot that works for the majority of EPDP members who are interested in the topic and able to bring tough questions for discussion. Please let me know how you’d like to proceed. /marksv From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of Anderson, Marc via Gnso-epdp-team Sent: Tuesday, August 6, 2019 10:53 AM To: alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com>; icann(a)ferdeline.com<mailto:icann@ferdeline.com>; gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Cc: gnso-epdp-lead(a)icann.org<mailto:gnso-epdp-lead@icann.org> Subject: Re: [Gnso-epdp-team] Experts for the lunch time presentations during the LA f2f meeting I would also be interested in hearing from the Microsoft Digital Crimes Unit, but I don’t feel the LA face to face is the right venue. So far we received one external briefing during a regular weekly call and two during the lunch block at Marrakesh. Of those, I thought the one during our weekly call worked better and didn’t think there was anything covered in Marrakesh that required face to face interaction. My preference would be to invite them to present at a future weekly call. Thank you to Mark Sv for the offer to invite the Microsoft Digital Crimes Unit to speak to us. I admit it’s not immediately clear to me from the original email from Janis how this ties to our work, but I assume that Mark would not have suggested this if it didn’t relate to developing policy recommendations on access to non-public registration data. I also want to echo one of Milton’s points about non-working lunches. In phase 1 we struggled to move forward until we had the LA face to face. In my view the ability to talk between formal facilitated sessions and over lunch was key to the success in LA and laid the groundwork for much of the work we would later accomplish. We need to bake in time for those all important side conversations that allow those with opposing positions to talk, share views and develop common positions that can achieve consensus support. Best, Marc From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of Alex Deacon Sent: Tuesday, August 6, 2019 12:58 PM To: Ayden Férdeline <icann(a)ferdeline.com<mailto:icann@ferdeline.com>> Cc: gnso-epdp-lead(a)icann.org<mailto:gnso-epdp-lead@icann.org>; gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Subject: [EXTERNAL] Re: [Gnso-epdp-team] Experts for the lunch time presentations during the LA f2f meeting I would be interested in hearing from the Microsoft DCU team and having the opportunity to ask them questions on how they do what they do. However I also appreciate Ayden’s strongly held feelings so perhaps we should consider a happy hour presentation at the end of our day allowing us to take full advantage of the facilitators and our time together during the day. What could be more fun than learning about digital crimes investigation while enjoying a cocktail or three? Alex On Mon, Aug 5, 2019 at 4:14 PM Ayden Férdeline <icann(a)ferdeline.com<mailto:icann@ferdeline.com>> wrote: I'm sorry, I really do not understand why this would be useful for our face-to-face meeting. I do not oppose having special webinars so that experts can share with us additional information and field our questions. But I worry it would be information overload having these presentations at the face-to-face meeting as well. And if we have external facilitators in Los Angeles next month, I think it would be a better use of this resource to spend what little time we do have in a face-to-face environment focusing on our core work plan, and not having briefings from external presenters that may or may not be relevant to what we have to deal with then. I feel very strongly about this. I am afraid I did not leave the presentations we had in Marrakech from external presenters with any inputs that I have been able to take forward, be it here in this working group or elsewhere at ICANN. Best wishes, Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 3 August 2019 10:45, Hadia Abdelsalam Mokhtar EL miniawi <Hadia(a)tra.gov.eg<mailto:Hadia@tra.gov.eg>> wrote: > I totally agree with having presentations during lunch time. Certainly we shall have other opportunities for networking and it does not matter if the information is neutral or not, all members of the EPDP team are intelligent people who can decide which information to consider and which to simply disregard. To have the opportunity to learn more is always good and Milton you had your experience with them already because of a research you were conducting, its a good opportunity for the rest of us to develop our own. > > Best > > Hadia > > From: Gnso-epdp-team gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org> on behalf of Mueller, Milton L milton(a)gatech.edu<mailto:milton@gatech.edu> > Sent: 03 August 2019 05:20 > To: Alan Greenberg > Cc: gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org>; gnso-epdp-lead(a)icann.org<mailto:gnso-epdp-lead@icann.org> > Subject: Re: [Gnso-epdp-team] Experts for the lunch time presentations during the LA f2f meeting > > First, it’s not true that working lunches haven’t accomplished much - they have > > Second, how about a bloody non-working lunch? Or two? Where we can chat and informally network? We will be working intensively for 8 hours at least. > > Third, it is simply not true that routing useful > Info through epdp team members requires “extraordinary time” nor is it true that you save time doing it the other way (indeed, that’s obviously a self-contradictory position.) We are discussing use cases at length and any information or arguments made in those discussions should not be given a privileged status, they come in via team members. > > Milton L Mueller > Professor, School of Public Policy > Georgia Institute of Technology > > On Aug 2, 2019, at 19:29, Alan Greenberg <alan.greenberg@mcgill.camailto:alan.greenberg@mcgill.ca<mailto:alan.greenberg@mcgill.ca>> wrote: > > I disagree. Working lunch meetings rarely accomplish much, so scheduling what may be an interesting presentation, even if from a particular perspective (and known to be) can be both informative and useful. Those who choose to just eat and not pay attention are free to do so. > > The suggestion to route any useful information through a EPDP member presumes we will be willing to give a member a significant and extraordinary time slot to do so and I would not advocate doing that. > > We have three lunch slots and I would welcome other presentations of interest/use for the other two days. > > Alan > > At 02/08/2019 06:55 PM, Mueller, Milton L wrote: > > Janis, > Much as I would love to hear more about MSFTâ€™s digital crimes unit (I already have seen some of their presentations and weâ€™ve interviewed one of their botnet fighters in connection with research we are doing) I think after our not-so-great experiences with external presentations in Marrakech the group really needs to â€œjust say noâ€� to any additional presentations of this sort. Please, letâ€™s not encourage these requests anymore, letâ€™s put an end to this precedent. > > We have to be aware of the fact that these presentations are not neutral and purely informational, they come from serious players with a stake in the process. Microsoft is represented on the EPDP and through the BC. IF they can bring useful information to bear on our discussions of use cases they can do it through their EPDP representative in line with our regular discussions, in which we all have equal status. > > Dr. Milton L Mueller > Georgia Institute of Technology > School of Public Policy > > From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.orgmailto:gnso-epdp-team-bounces@icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of Ayden FÃ©rdeline > Sent: Friday, August 2, 2019 6:58 AM > To: Janis Karklins <karklinsj@gmail.commailto:karklinsj@gmail.com<mailto:karklinsj@gmail.com>> > Cc: gnso-epdp-lead@icann.orgmailto:gnso-epdp-lead@icann.org<mailto:gnso-epdp-lead@icann.org>; gnso-epdp-team@icann.orgmailto:gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org> > Subject: Re: [Gnso-epdp-team] Experts for the lunch time presentations during the LA f2f meeting > > It is a very short face-to-face meeting, and I imagine we will have a lot on the agenda and hopefully the excellent external facilitators present. I would prefer that we not have any additional, external presenters during the face-to-face - though I am certainly happy to join a webinar over the coming weeks to hear what anyone has to say. > > Best wishes, > Ayden FÃ©rdeline > > â€�â€�â€�â€�â€�â€�â€� Original Message â€�â€�â€�â€�â€�â€�â€� > On Friday, 2 August 2019 05:30, Janis Karklins <karklinsj@gmail.commailto:karklinsj@gmail.com<mailto:karklinsj@gmail.com>> wrote: > > Dear team members, > > I am writing to you in inform that I have received offer from Mark Svancarek to bring an expert from Microsoftâ€™s Digital Crimes Unit and to make a (lunch time) presentation of their routine practices in investigating cases of concern to Microsoft. I think such a presentation would help us foster understand challenges facing digital wrongdoing investigators from private companies. > > I also would like to ask if there would be any other experts who could make lunchtime presentations either onsite or remotely. > > I would be grateful for your thoughts on the proposal above. > > Thank you > JK > > Gnso-epdp-team mailing list > Gnso-epdp-team@icann.orgmailto:Gnso-epdp-team@icann.org<mailto:Gnso-epdp-team@icann.org> > https://mm.icann.org/mailman/listinfo/gnso-epdp-team<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…> > > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy ( https://www.icann.org/privacy/policy<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>) and the website Terms of Service ( https://www.icann.org/privacy/tos<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. > > Gnso-epdp-team mailing list > Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> > https://mm.icann.org/mailman/listinfo/gnso-epdp-team<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…> > > By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>) and the website Terms of Service (https://www.icann.org/privacy/tos<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…> _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>) and the website Terms of Service (https://www.icann.org/privacy/tos<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -- ___________ Alex Deacon Cole Valley Consulting alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com> +1.415.488.6009 ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ This information is supplied in confidence by NCA, and is exempt from disclosure under the Freedom of Information Act 2000. It may also be subject to exemption under other UK legislation. Onward disclosure may be unlawful, for example, under data protection legislation. Requests for disclosure to the public must be referred to the NCA FOI single point of contact, by email on PICUEnquiries(a)nca.gov.uk. All E-Mail sent and received by NCA is scanned and subject to assessment. Messages sent or received by NCA staff are not private and may be the subject of lawful business monitoring. E-Mail may be passed at any time and without notice to an appropriate branch within NCA, on authority from the Director General or their Deputy for analysis. This E-Mail and any files transmitted with it are intended solely for the individual or entity to whom they are addressed. If you have received this message in error, please contact the sender as soon as possible.

5 4

New RySG representative
by Anderson, Marc Aug. 9, 2019

Aug. 9, 2019

All, Some of you may have noticed that Matt Crossman formally replaced Kristina Rosette as one of the RySG representatives on today's ePDP2 plenary meeting. I was hoping to do this on the call but let me take a moment to go on the record and thank Kristina for her time and contributions to the ePDP and to welcome Matt to the team. Best, Marc

3 2

EPDP-P2 Project Management and Workplan Package
by mail＠berrycobb.com Aug. 9, 2019

Aug. 9, 2019

Hi EPDP Project Team, I apologize up front for the document explosion. I'm sending these working drafts now, but we will use dedicated time on next Tuesday for me to present this package. We will specifically review the Gantt chart/project plan pages. As you know, we have to obtain Council approval of our plan and we are targeting the 22 Aug 2019 Council meeting. As Janis mentioned on the today's call however, we will reassess the plan based on outcomes of the Los Angeles face-to-face. You'll recall that we need an approved plan to request final resources from the ICANN Board that will allow the EPDP to fulfill its charter. One final thing to consider when reviewing the plan at a high-level and as communicated in Marrakech, an aspirational target was set for Dec 2019 to launch an Initial Report for public comment. You'll see this represented in the work products that make up this package. I'd like to reinforce the notion that this plan attempts to allocate tasks based on the number of hours it takes for the group to deliberate the policy topics and agree on some sort of outcome. While the project plan is represented on a 5 business day work week, in reality that only translates to 4 or 6 hours of conference calls per week. So, it is important to think of tasks being resourced in those terms instead of being driven only by calendar dates. As an example and assuming we do not take any breaks, considering plenary calls are 2 hours and secondary/LC calls are 1.5 hours, and finally considering total hours for the face-to-face in LA, it only equates to a total of 38 hours to deliberate topics verbally through 11 Sep 2019. Lastly, the full project plan on pages 5 to 8 is subject to change as I continue to refine individual tasks, durations and dependencies in preparation for Tuesday. I wanted to allow enough time for the group to become familiar with the package so that we can spend more time on the detailed tasks that define the critical path. EPDP-P2 Project and Work Plan Package: * The general intent is this will be compiled and reviewed once per month in preparation for our planning/progress, but also to prepare for updates required by the GNSO Council. Individual work products will be updated more frequently and as necessary to meet the project communication and planning requirements. * Page 1 - Simple Gantt, mostly for external communications; note the far right will need to be confirmed and updated after agreement is reached on the full project plan. * Page 2- Fact sheet, we've all seen this before. I'll just note that the % complete will be derived from the four primary phases of the project plan further down. * Page 3 - Project SitRep, this is also a part of the GNSO Council Project list, but it can also be used to communicate a more detailed status externally. Note, the Status/Condition codes feature can change as a result of negative impacts to the project. Based on PDP3.0 implementations, this may trigger interactions with the GNSO Council leadership and the full GNSO Council as necessary. * Page 4 - Collapsed version of the Gantt Project Plan; I suspect this will be the ultimate work product we take to the GNSO Council for approval. It is rows 35-189 that we need to give the most attention over the next few weeks. * Pages 5 - 8 - represent the full expanded version of the project plan. * For the most part, what we've accomplished so far as a group is what I've attempted to represent as actual tasks and durations (rear-view mirror planning of sorts). * Rows 35 - 73 is the work that is ahead of us going to LA around the use cases and a few of the topics the group will likely focus on shortly after LA. * For now, (46-109) I've used a repeatable template that covers the topic over a duration of 4 weeks that includes a 1st and 2nd reading with some sort of outcome. * For the most part, Priority 2 topics are decoupled from the Initial Report; we'll need to spend some time figuring out how these influence our overall plan. * Row 171 is a parking lot of sorts for items we need to circle back on or unplanned events. Unplanned work of course has a chance to severely impact our schedule. Think of this section a project scope radar. We should investigate any other potential topics that can influence our scope. * The Key Events section (Row 194 - 262) is mostly work behind the scenes to prepare for face-to-face events but placed here to track overall project activities. It is not connected to the critical path. * The Initial and Final Reports sections: I don't think we need to change the tasks so much (mostly template form) but we do have flexibility in adjusting duration and delivery dates. The real work resides in the EPDP Deliberations section where the critical path lives. * Post EPDP activities are tasks after the EPDP is delivered to the Council but placed there as the Policy department owns the project up and until the Board takes action. * Page 9 is an initial draft of our work plan inherited Marika's use case calendar. It will be updated each week with the tasks from the project plan so that the group focuses only on what is front of us. This will be migrated to Google Sheets. It also contains a link to the Action Items list that is located on the wiki. I suggest we migrate this to a Google Doc as well. It will allow for easier management of the items and we can report easier from it over the wiki. Happy reading. I'll be glad to answer any initial questions over the list until we meet on Tuesday. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant

1 0

For your review: Priority 2 next steps table
by Caitlin Tubergen Aug. 8, 2019

Aug. 8, 2019

Dear EPDP Team: Per the action item from today’s EPDP Team call, please find attached the Phase 2 Priority 2 updated table, which links to all relevant work sheets and includes the outlined next steps provided by the small teams who contributed to the Priority 2 calls. If you have any concerns with the outlined next steps for any of the Priority 2 topics, please provide them on the list by COB Thursday, 15 August. Thank you. Best regards, Marika, Berry, and Caitlin

1 0

Notes and action items - EPDP Phase 2 Meeting #12 - 8 August 2019
by Caitlin Tubergen Aug. 8, 2019

Aug. 8, 2019

Dear EPDP Team,Please find the notes and action items from today’s EPDP meeting below.As a reminder, there will be an optional meeting for those wishing to review the project plan in detail on Tuesday, 13 August at 14:00 UTC.Best regards,Marika, Berry, and Caitlin--EPDP Phase 2 - Meeting #12Thursday, 8 August 2019 at 14.00 UTCAction Items Action: EPDP Team to review Priority 2 Next Steps table for final review and comment by Thursday, 15 August. Action: Greg and SSAC Team to propose edits to the use case based on comments received today as well as outstanding comments received this week and next week on the Google Doc. Following the fine-tuning of the document, a final reading will occur at a later meeting. Action: Hadia and ALAC Team to propose edits to the use case based on comments received today as well as outstanding comments received this week and next week on the Google Doc. Following the fine-tuning of the document, a final reading will occur at a later meeting. Notes EPDP Phase 2 - Meeting #12Thursday, 8 August 2019 at 14.00 UTCThese 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/ZwPVBQ. Roll Call & SOI Updates (5 minutes) Confirmation of agenda (Chair) No objections to the agenda. 3. Welcome and housekeeping issues (Chair) (10 minutes) a. Early input review – reminder to review. To be added to the agenda for next week’s meeting. Per a previous suggestion, the Team will discuss early input received from other groups at the next meeting. Are groups prepared to discuss this next week? No objections from the Team; therefore, the Leadership Team will add early input discussion to the agenda next week. b. Experts for lunch time presentations during F2F meeting Mark Sv. proposed a presentation by the Microsoft cybercrime unit. A proposal was received to have the presentation during lunch at the F2F, but this was objected to by multiple team members. Would Team members agree to a webinar presentation on this topic? As there were no objections, EPDP Leadership will coordinate with Microsoft to schedule a webinar presentation. c. Priority 2 small team meetings update Accuracy and WHOIS ARS (see https://docs.google.com/document/d/1pS9Pibanj-Hp6LztZpeERtxdoLsnp4y_-do0vU5… [docs.google.com] Input received on other priority 2 items from RrSG (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-June/002174.html) Leadership to recommend next steps via mailing list. Action: EPDP Staff Support to send the Priority 2 materials to the Team for review today. EPDP to send comments and proposed edits (if any) by Thursday, 15 August. d. Update from Legal Committee Legal Team has been reviewing questions related to SSAD (EPDP Team Priority 1 work). Legal Team has approved one question for final sign-off by the EPDP Team. Pending no objections, this question will be forwarded to Bird & Bird. The next call will be Tuesday, 20 August, and the Team will continue to discuss outstanding questions. Will the Team be sending questions in batches or as they individually come in? The LC will discuss this question at its next meeting. 4. Use case – second / final reading: Investigation of criminal activity where domain names are used. Typical specific example: phishing attack (45 minutes)a. Overview of updated version in which EPDP Team input has been considered and addressed (Greg Aaron) In this use case, it is mainly 6(1)(f) legal basis, but there may be other legal bases that are relevant in other use cases, which is why other legal bases are included. In terms of the accuracy of contact data, one thing to consider is that registrants have the contractual obligation to provide accurate contact information. However, it is common to see domain names registered to streets that do not exist or vacant lots. When reporting an issue to a registrar, a requester needs to report the specifics of the problem and substantiate it. The SSAC felt obligated to put information into the safeguards section, noting that safeguards will likely come later in the working group discussions. SSAC would like to go through a real-life use case to illustrate these principles: This is an example of a phishing URL that came to an SSAC rep during ICANN65. There are other phishing URLs on that domain name - one targeting GA Tech and one targeting Microsoft users Based on the WHOIS information for this domain name and what we can tell from it - it’s registered at OVH, the creation date on the name is about one week before the phishing took place. This is not determinative. There is no contact information for the name, but there is a country code associated with it - DZ - for Algeria. Again, this is not determinative, but not many gTLD names are registered in Algeria. By looking at DNS records, you can see what other names are hosted at this IP address. In this example, there are other similar-looking names to the name the phish came from. It’s helpful to know what other domain names the phishers have registered - without the contact information, this is hard to tell. In this example, there was phishing on the set of domain names before and after this Georgia Tech phish. In this particular case, contact information/attribution would have been very useful for reporting and preventing additional harm. GDPR Recital 49 provides looking at information for this purpose is legitimate. b. Feedback from EPDP Team This example demonstrates that just b/c a requester asks for contact data does not mean it hasn’t tried other avenues before. NCSG provided comments on the document yesterday - what would be the preferred way of handling the concerns noted in the document? It may be helpful for SSAC to respond in the Google Doc. Law enforcement’s job is to provide attribution and this work is regulated by criminal procedure. Law enforcement has a framework of accountability for dealing with this, while private companies do not. Attribution by researchers and security professionals is important in many instances. Attribution is not only for law enforcement - it is often done by private parties. No one is challenging the concept that more data points allow for a more comprehensive investigation of harm. Can pseudonymized data be used for this? Unlike law enforcement, there are no credentials to check that the security organization is who they say they are. Registrars need to mitigate potential harms of over-blocking names or releasing too much information. Pseudonymized data is an interesting topic, but it does pose challenges that could be discussed at a later time. With respect to this example, major providers of access have phishing issues at large scale/high volume. This is not something that can be solved by LEA only. Attribution is important because when so many domain names are involved, attribution will show you where to focus your resources and who to go after. As this team creates the WHOIS policy, the team should not prohibit accredited cyber security professionals from getting high volume, quick access to data to prevent harm. This example looks like a civil case, not a criminal case. Many of these cases do start with private investigators since LEA may not have the resources. The questions posed highlight why a webinar from Microsoft may be helpful. Pseudonymization may be helpful in some cases, but not all cases. In terms of attribution to individuals vs. states, the attribution was to a criminal gang, not a state actor. Microsoft got a court order to investigate as they found the domain names - the judge gave them the approval on an ongoing basis. This could be a civil or criminal issue. Phishing is a criminal activity, but could also be pursued by a private party. What a law enforcement agency would like to see is some scale of impact to a number of victims, LEA would have more to go on. Pseudonymization could apply in this case, but you could perhaps look at if the data is fake/compromised host. This Team needs to make sure the policy is within the law. The initial search may be a 6(1)(f), but the court may provide the ability to data under a different legal basis. If looking to Section B to all tasks performed, is there any violent opposition to these tasks? No objection. Section C - data elements - not all data elements would be required on a systematic basis. Any objections? No comments. Section D: no comments. Section E: have a problem with 6(1)(d). Before you get to a threat to life situation, you are likely acting on another legal basis before. For this final reading, NCSG’s comments were not addressed and cannot do the final review without the comments being addressed. Final reading will occur later. Legal basis may need further revision once advice has been provided by Bird & Bird. This use case about private actors doing investigations is slipping over into law enforcement. It would be helpful to keep these distinct. Do not agree with 6(1)(c) being applicable in this use case. 6(1)(f) is likely the only applicable lawful basis in this use case. Response: SSAC will take these comments into consideration. There are various legal obligations in place. Section F: How do we interpret safeguards for disclosing entities? The safeguards should protect the data subject. In this use case specifically, the safeguards facilitate disclosure. These safeguards represent the input to build the Team’s understanding of the action of the requester and the actions of the requestee. Section N: This is a core legal question that needs to be answered, and it will be helpful to defer to Bird & Bird on this. Legal analysis should provide this answer, so this text should not be asserted - it should be qualified c. Confirm next steps Action: Greg and SSAC Team to work in response to comments on the Google Doc. Following the fine-tuning of the document, a final reading can occur at a later meeting. 5. Use case – first reading continued: Online buyers identifying and validating the source or services/ Internet users validating the legitimacy of an email or a website to protect themselves (45 minutes)a. Continue introduction of use case (ALAC) The issue of legal vs. natural persons is an issue this team needs to come back to. The use case presumes that there is no change to the legal vs. natural policy recommendation. There is no question that a data requester that is not identifiable Section E: lawful basis 6(1)(f) - it’s important to note that this is to prevent fraud, so it happens before the fraud occurs. Actual case - credit card has not been deducted for an airline ticket purchased online. The purchaser receives an email asking for a copy of the ID. A purchaser may provide the information or not - if not, the purchaser may seek information access to information to see who is behind the website. For this use case, no accreditation or automation is sought, but ALAC does believe a means for a consumer to verify its activity is necessary. b. Input from EPDP Team – questions, concerns, proposed modifications Generally, the use case described is consumer trust, consumer confidence and/or verifying the integrity of a website. This is out of scope for this team - this use case represents websites, but RDS does not link contact information to websites; it links to domain names. There is not a one-to-one relationship between websites and domain names. This is not a case where RDS is a useful tool; SSL, BBB, or Yelp could be better tools in this case. There are two types of individuals that would be engaged in this - curious users would not have access to personal information, or groups that have legal authority to pursue this. Curious users does not rise to the level of a legitimate use case, and therefore this use case is redundant and unnecessary. It is profoundly irresponsible for ICANN to attempt to step in here for what goes on with a domain name after it is allocated. To encourage consumers to look to the WHOIS directory or WHOIS data to determine the reliability of a website when the ecosystem is so multilayered is irresponsible. In this use case, there are a variety of ways to determine the integrity of a website. Under GDPR, necessity is the key, and this case does not demonstrate necessity. It should therefore be deleted. The ICANN bylaws are not as restrictive as some Team members have noted. Perhaps this could be limited to legal persons. When a registrar is receiving a request, the registrar can look at the info to determine if it is a natural or legal person. There is an ability to do the balancing test when it is a commercial website, so the use case should be kept. Skeptical of this use case where it applies to curious users - it’s really only applicable when there is a reputation service going on. The ICANN bylaws note that during a policy making process, we do have to consider the global public interest - what is useful for the public. There is a division of thought as to what that involves, but it is different than public policy. Looking at this use case is a legitimate thing to do. GDPR does not protect legal persons. If the team resolves the legal/natural distinction differently, this use case would not be applicable. The contracted party may look at the use case and decide whether to grant access. A registrar claims it would never grant access based on this, but that may be incorrect. There may be cases where the controller determines this is a reasonable request. c. Confirm next steps Action: Hadia and ALAC Team to respond to comments received today as well as outstanding comments received this and next week on the Google Doc. Following the finetuning of the document, a final reading will occur at a later meeting 6. Any other business (5 minutes)7. Wrap and confirm next EPDP Team meeting:a. For those interested, an additional meeting will be held on Tuesday 13 August at 14.00 UTC – presentation of leadership-proposed EPDP work plan for submissions to GNSO Council Tomorrow morning, EPDP Support Staff will distribute the project management package. b. Next plenary meeting will be held Thursday 15 August 2019 at 14.00 UTC c. Confirm action itemsd. Confirm questions for ICANN Org, if any

1 0

Meeting Invitation: Observers GNSO Temp Spec gTLD RD EPDP - Phase 2 call / Tuesday, 13 August 2019 at 14:00 UTC
by Terri Agnew Aug. 8, 2019

Aug. 8, 2019

**Reminder, the next meeting will take place on Thursday, 08 August 2019. Meeting invite below is being sent now to get it on everyone’s calendar. As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Tuesday, 13 August 2019 at 14:00 UTC for 90 minutes. 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Wednesday) 00:00 Melbourne AEST For other times: https://tinyurl.com/y2gfw3rq Agenda Wiki: https://community.icann.org/x/14LkBg The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> Meeting Audio Cast (for observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream02 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> If needed, an option to join via telephone has been added for this meeting. Passcode: EPDP Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL RIO DE JANEIRO: 55-21-40421490 0800-7610651 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751 Thank you. Kind Regards, Terri

1 1

Post Call | GNSO Temp Spec gTLD RD EPDP – Phase 2 | Thursday, 08 August 2019 at 14:00 UTC
by Terri Agnew Aug. 8, 2019

Aug. 8, 2019

Dear all, All recordings for the GNSO Temp Spec gTLD RD EPDP – Phase 2 held on Thursday, 08 August 2019 at 14:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/nKajBg> (attendance included) and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript As a reminder only members and alternates can join the call, observers can join via audio cast, listen to the recordings and read the transcript afterwards. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-team/> and the main wiki page<https://community.icann.org/x/IYEpBQ>. Thank you. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

**Call starts in 15 minutes** Meeting Invitation: Observers GNSO Temp Spec gTLD RD EPDP - Phase 2 call / Thursday, 08 August 2019 at 14:00 UTC
by Andrea Glandon Aug. 8, 2019

Aug. 8, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Thursday, 08 August 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 00:00 Melbourne AEST For other times: https://tinyurl.com/y6t69fj5 [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y6t69fj5&d…> Agenda Wiki: https://community.icann.org/x/nKajBg The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> Meeting Audio Cast (for observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream02 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> If needed, an option to join via telephone has been added for this meeting. Passcode: EPDP Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL RIO DE JANEIRO: 55-21-40421490 0800-7610651 BRAZIL SAO PAULO: 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7878-2631 0066-33-132439 JAPAN TOKYO: 81-3-6868-2631 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 VIETNAM 120-11751 Thank you. Kind Regards, Terri

1 0