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

REMINDER: ICANN63: GNSO Sessions How to Get Organized and Remote Participation Details
by Terri Agnew Oct. 16, 2018

Oct. 16, 2018

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings' team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN63 Meeting Schedule [63.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__63.schedule.icann.org_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/nxVpBQ> Step 1 - Create a profile and your personalized ICANN63 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you've added all your chosen meetings to "My Schedule" go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the ICANN63 Meeting Schedule [63.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__63.schedule.icann.org_…> and on the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/nxVpBQ>) will provide audio streaming only, Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/nxVpBQ> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for "ICANN63" in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Barcelona to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Julie Bisland Secretariat Operations Coordinator for the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting the GNSO Newcomer pages [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_g…>

1 1

EPDP Team F2F meeting (4 of 4)
by ICANN Policy Calendar Oct. 16, 2018

Oct. 16, 2018

1 0

EPDP Team F2F Meeting (3 of 4)
by ICANN Policy Calendar Oct. 16, 2018

Oct. 16, 2018

1 0

EPDP Team F2F Meeting (2 of 4)
by ICANN Policy Calendar Oct. 16, 2018

Oct. 16, 2018

1 0

EPDP Team F2F meeting (1 of 4)
by ICANN Policy Calendar Oct. 16, 2018

Oct. 16, 2018

1 0

Two docs for 16 Oct meeting
by Berry Cobb Oct. 16, 2018

Oct. 16, 2018

Hi All, For today's meeting and given a few are not in the AC room, please find attached two PDFs I will review. These are not consider in final form and act as a working example. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Fwd: Nonpublic registrant data for ...
by Benedict Addis Oct. 16, 2018

Oct. 16, 2018

Dear RegistrarSEC (a wholly-owned subsidiary of Facebook), I write on behalf of Stichting Registrar of Last Resort Foundation (RoLR) to request the registrant of the following domain name: rr-facebook.com The mailserver at mail.rr-facebook.com is being used to send silly automated emails like the one below. I am seeking to identify the registrant so I can give them a jolly good talking-to over some delicious tapas in Barcelona. 1 The information above should be provided by exactly Thu Oct 18 16:17:05 UTC 2018 in order to faciliate a timely restaurant reservation. I’m pretty sure that this is a lawful request under the European Working Lunch Directive. Failure to comply with this request will involve absolutely no further action, because (let’s be honest) Compliance have enough on their plate already. Yours faithfully, Benedict Addis. -- 1 RoLR reserves the right to choose type and quantity of tapas, but is partial to pa amb tomàquet. > Begin forwarded message: > > From: whoisrequest(a)rr-facebook.com > Subject: Nonpublic registrant data for ... > Date: 16 October 2018 at 05:17:05 BST > To: abuse(a)rolr.eu > > To Stichting Registrar of Last Resort Foundation > > I write on behalf of Facebook [and its affiliated companies] to request a single domain registration record as identified below.1 We have become aware that the below-identified domain name misuses one or more of the following trademarks held by Facebook [and/or its affiliated companies]: > > > Trademark > > US Trademark Reg. # > > EU Trademark Reg. # > > WHATSAPP > > 4083272 > > 1A > > 009986514 > > EUTM > > WHATSAPP > > 3939463 > > 1A > > 0099865149 > > EUTM > > OCULUS RIFT > > 4863585 > > 1A > > 012983854 > > EUTM > > OCULUS > > 4891157 > > 1A > > 012983854 > > > OCULUS VR > > 4424543 > > 1A > > 012983854 > > EUTM > > INSTAGRAM > > 4146057 > > 1A > > 012111746 > > EUTM > > INSTAGRAM > > 4170675 > > 1A > > 012111746 > > EUTM > > FB > > 4659777 > > 1A > > 8981383 > > EUTM > > FACEBOOK > > 4643774 > > 1A > > 005722392 > > EUTM > > > The fame and recognition of the above marks entitle Facebook to broad legal protection globally. > > In order to investigate and prevent intellectual property infringement and contact infringing parties and relevant service providers, we request information regarding the following domain name: > > [snipped some random DGA domain entirely unconnected with these trademarks] > We seek the following information1 consistent with the principles enumerated under Section 4 of the Temporary Specification for gTLD Registration Data adopted by ICANN on May 18, 2018: > > Registrant name, address, phone, fax number, and email address > > Technical contact name, address, phone, fax number, and email address > > Administrative name, address, phone, fax number, and email address > > To the extent that the requested information is believed to be subject to the European Union’s General Data Protection Regulation (Commission Regulation (EU) 2016/679), we submit this request pursuant to Article 6(1)(f) of that Regulation. The information requested is necessary for the purposes of our legitimate interests, namely (1) identifying the registered holder of a domain name and their contact information to investigate and respond to potential trademark infringement and (2) enforcing legal claims. > > We seek this information by Thu Oct 18 04:17:05 GMT 2018 in order to facilitate immediate legal action against the registrant. Please provide the requested information by responding to this email. NOTE: Please do not change the CASE in the subject line. > > > Facebook (transmitted by AppDetex Managed Services) > > > 1. [Facebook [and its affiliated companies] reserves all of its legal rights in relation to this request and by making this request with respect to the domain name referenced above does not waive any and all rights it may have to request additional information regarding other domain names registered by the registrant or the contacts reflected in the WHOIS record.] >

1 0

Small team updated Purpose A description
by Caitlin Tubergen Oct. 16, 2018

Oct. 16, 2018

Dear All, Below, please find the Purpose A Small Team’s tentative agreement regarding an updated description of Purpose A: Proposed Update to Purpose A: “Establish the rights of a Registered Name Holder in a Registered Name and ensuring that the Registered Name Holder may exercise its rights in respect of the Registered Name. Specifically, subject to applicable terms and conditions posted by the registrar, including applicable policies from the registrar, registry, and ICANN, a Registered Name Holder has the following rights with respect to its domain name(s): The right to exclusive use, and to benefit from use; The right to transfer (i.e., the right to sell, gift, sub delegate to others; The right to renew and restore; The right to transfer the name(s) to the registrar of its choice from among registrars authorized to sell domain names in the gTLD of interest; The right to choose its registrar from among registrars authorized to sell domain names in the gTLD of interest.” In answering the question, “[w]hich data elements must be transferred from a registrar to a registry in order for a registrant to exercise each specific right?”, the small team noted the following: With respect to all above-referenced rights, Name Server and Domain Name must be transferred from a registrar to a registry, and is lawful under Art. 6(1)(b) of the GDPR. The registry processes (collection, storage and use) the same registration data under Art. 6(1)(f), and a transfer of the registration data from registrar to registry, where the registry operates a “thick whois,” is lawful under Art. 6(1)(f) of the GDPR. (Note: some members of the small team requested additional information over the precise definition on registration data in this context if it differs from Name Server and Domain Name.) Full registrant data CAN be requested by the Ry based Art. 6(1)(f); Processing for the purpose of administering the application of a Registry Acceptable Use Policy (AUP) (or equivalent); such processing is considered justifiable under the Art. 6(1)(f) balancing test when considering the nature of the data, the envisaged limited use of the data, and the likelihood of the impact on the privacy rights of the Registered Name Holder when weighed against the safety and integrity of the zone. Eligibility requirements, where validated by the Ry can be a reason for Rr Ry transfer based on Art. 6(1)(b). There are cases where the Ry actually does the validation or lets it do by third party at the Rr level, but that would then still be a Ry responsibility. Where Validation is done by the Rr only and commissioned by the Rr, no data transfer based on 6(I)(b). Thank you again to the small team for all of your hard work! Best regards, Marika, Berry and Caitlin

1 0

External google drive for EPDP Team materials
by Marika Konings Oct. 15, 2018

Oct. 15, 2018

Dear All, You should shortly be receiving an email notifying you that you have been given access to an external google drive. Staff plans to use this drive to post all preparatory materials for ICANN63 to facilitate your preparation. Do note that you will need a google account to be able to access this drive. If you do not have a google account, you can either create a temporary one, or alternatively staff can email you the documents. We plan to have all relevant documents up by tomorrow, Tuesday, end of day at the latest. 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

***REMINDER*** Meeting Invitation / Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Tuesday, 16 October 2018 at 13:00 UTC
by Julie Bisland Oct. 15, 2018

Oct. 15, 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/LwWrBQ Thank you. Kind Regards, Andrea Glandon

1 0