- Gnso-impl-thickwhois-rt - lists.icann.org

CL &D policy
by Metalitz, Steven Oct. 4, 2016

Oct. 4, 2016

Dennis, The link you put in the chat on today’s call (https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en) is to the CL&D policy as originally posted in July. I was asking about the revised policy that you asked every single person on the call today to approve. Can you send me the link to that? As I noted it does not appear on the wiki page (https://community.icann.org/display/TWCPI/Documentation ). Is there any change to the posted policy other than to drop paragraph 12? Thanks. Steve Metalitz [image001] Steven J. Metalitz | Partner, through his professional corporation T: 202.355.7902 | met(a)msk.com<mailto:met@msk.com> Mitchell Silberberg & Knupp LLP | www.msk.com<http://www.msk.com/> 1818 N Street NW, 8th Floor, Washington, DC 20036 THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS. THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU. From: gnso-impl-thickwhois-rt-bounces(a)icann.org [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Tuesday, October 04, 2016 1:05 PM To: Joyce Lin; gtheo; Chris Pelling Cc: gnso-impl-thickwhois-rt(a)icann.org Subject: [Gnso-impl-thickwhois-rt] Alternative method: Re: Questions from last meeting, Alternative method and some comments. Separating the email trail for Alternative method. Hi Joyce, To be clear, as you say “registry go ahead to have the alternative mechanism available by Aug. 1, 2017 regardless” is the intention. The reason being that Chris has confirmed the need for it along with other registrars already. Thanks Dennis Chang On 10/4/16, 9:35 AM, "Joyce Lin" <jlin(a)007names.com<mailto:jlin@007names.com>> wrote: Hi Dennis, If you meant to drop 2.2 completely, your combined paragraph states that by August 1, 2017 the registry's EPP and alternative bulk transfer have to be deployed > 2.1. Registry Operator MUST deploy an EPP mechanism and an alternative > bulk transfer mechanism by 1 August 2017 for registrars to migrate > registration data for Existing Domain Names... Then what is the deadline for those registrars who need to use alternative bulk transfer option to apply ? Don't we need a separate deadline for those registrars to apply so the registry can tell if there is indeed a need to develop and deploy the alternative mechanism? Or do we want the registry go ahead to have the alternative mechanism available by Aug. 1, 2017 regardless? Joyce ----- Original Message ----- From: "Dennis Chang" <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> To: "gtheo" <gtheo(a)xs4all.nl<mailto:gtheo@xs4all.nl>>; "Chris Pelling" <chris(a)netearth.net<mailto:chris@netearth.net>> Cc: <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Sent: Monday, October 03, 2016 12:56 PM Subject: Re: [Gnso-impl-thickwhois-rt] Questions from last meeting, Alternative method and some comments. > Thanks Chris for following through on your action regarding the Registrar’s > request for the alternative solution. > Since your email to the IRT satisfies the triggers for the “request” in > section 2.2, > We can simplify the policy by combining 2.2 with 2.1 using the same date. > Btw, 1 August 2017 provides the 6-month duration that Marc had requested > for development. > > Below if my proposed change. > > From: > 2.1. Registry Operator MUST deploy an EPP mechanism by 1 August 2017 for > registrars to migrate registration data for Existing Domain Names (i.e., > transition from Thin to Thick). > 2.2. Registry Operator MUST upon request provide an alternative bulk > transfer mechanism by 1 February 2018 for registrars to migrate data for > Existing Domain Names (i.e., transition from Thin to Thick). The request > MUST be made by 1 August 2017. > > To: > 2.1. Registry Operator MUST deploy an EPP mechanism and an alternative > bulk transfer mechanism by 1 August 2017 for registrars to migrate > registration data for Existing Domain Names (i.e., transition from Thin to > Thick). > > > As for your question about the draft privacy memo to GNSO Council, the IRT > had agreed the implementation project will continue in parallel to any > activity related to the memo. This was agreed upon when the subject was > broached at the Helsinki ICANN meeting and again in subsequent meetings. > Our plan to continue with the implementation work including the Public > Comment has not changed. It is the goal of our implementation team to > press forward as best we can to meet the 1 February 2017 Announcement Date > per the project schedule we’ve agreed upon. > > Thanks for your support and look forward to our meeting tommorrow. > Dennis Chang > > On 10/3/16, 5:11 AM, "gtheo" <gtheo(a)xs4all.nl<mailto:gtheo@xs4all.nl>> wrote: > > Thanks Chris, for posting on the RrSG distribution list and engage with > our members. > > Theo > > Chris Pelling schreef op 2016-10-02 01:46 PM: > > Good afternoon all, > > > > First and foremost we have had ten registrars (including myself) > > interested in the alternative solution, so day one there will be at > > least 1 triggering it - as that will be me. > > This being just the RrSG folks, once ICANN reach out to all registrar > > from GDD, I am positive you will find more. But, as mentioned - I > have > > had active requests for the alternative to be created. > > > > Further questions: > > > > 1. The Verisign/GNSO memo, does this need to go directly to GNSO, or, > > via ICANN legal first, I assume this will happen before the public > > comment period? > > > > 2. Alan G. said that a legal review by ICANN legal is needed (I > > mentioned to include EU lawyers) because the original legal review in > > 2015 did not include Safe Harbor, nor contemplating that Safe Harbor > > would be invalidated, where are we on this and I assume this will > > happen before the public comment period? > > > > 3. Implementation notes state there is a procedure for handling whois > > conflicts. However, the current method for handling WHOIS conflicts > is > > not working, and the WHOIS IAG version is at the GNSO and still does > > not include an effective procedure as EU privacy regulators are not > > giving statements to trigger the procedure. So this kind of sits at > a > > stalemate, is ICANN going to remove this? (I would assume they can't, > > but we do need more info/guidance) > > > > The above points 1 and 2, will these happen before the public comment > > period or after? Please note if you state afterwards, we are all > > potentially sitting here wasting time, as once those 2 legals come > > back, it is more than likely we will all end up reviewing those and > > going for a second public comment period based on new findings and > > changes to existing work - I am just trying to save time here (and > > everyone's sanity) :-) > > > > Kind regards, > > > > Chris > > _______________________________________________ > > Gnso-impl-thickwhois-rt mailing list > > Gnso-impl-thickwhois-rt(a)icann.org<mailto:Gnso-impl-thickwhois-rt@icann.org> > > https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt<https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt> > > > > _______________________________________________ > Gnso-impl-thickwhois-rt mailing list > Gnso-impl-thickwhois-rt(a)icann.org<mailto:Gnso-impl-thickwhois-rt@icann.org> > https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt<https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt> _______________________________________________ Gnso-impl-thickwhois-rt mailing list Gnso-impl-thickwhois-rt(a)icann.org<mailto:Gnso-impl-thickwhois-rt@icann.org> https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt<https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt>

2 1

Alternative method: Re: Questions from last meeting, Alternative method and some comments.
by Dennis Chang Oct. 4, 2016

Oct. 4, 2016

Separating the email trail for Alternative method. Hi Joyce, To be clear, as you say “registry go ahead to have the alternative mechanism available by Aug. 1, 2017 regardless” is the intention. The reason being that Chris has confirmed the need for it along with other registrars already. Thanks Dennis Chang On 10/4/16, 9:35 AM, "Joyce Lin" <jlin(a)007names.com> wrote: Hi Dennis, If you meant to drop 2.2 completely, your combined paragraph states that by August 1, 2017 the registry's EPP and alternative bulk transfer have to be deployed > 2.1. Registry Operator MUST deploy an EPP mechanism and an alternative > bulk transfer mechanism by 1 August 2017 for registrars to migrate > registration data for Existing Domain Names... Then what is the deadline for those registrars who need to use alternative bulk transfer option to apply ? Don't we need a separate deadline for those registrars to apply so the registry can tell if there is indeed a need to develop and deploy the alternative mechanism? Or do we want the registry go ahead to have the alternative mechanism available by Aug. 1, 2017 regardless? Joyce ----- Original Message ----- From: "Dennis Chang" <dennis.chang(a)icann.org> To: "gtheo" <gtheo(a)xs4all.nl>; "Chris Pelling" <chris(a)netearth.net> Cc: <gnso-impl-thickwhois-rt(a)icann.org> Sent: Monday, October 03, 2016 12:56 PM Subject: Re: [Gnso-impl-thickwhois-rt] Questions from last meeting, Alternative method and some comments. > Thanks Chris for following through on your action regarding the Registrar’s > request for the alternative solution. > Since your email to the IRT satisfies the triggers for the “request” in > section 2.2, > We can simplify the policy by combining 2.2 with 2.1 using the same date. > Btw, 1 August 2017 provides the 6-month duration that Marc had requested > for development. > > Below if my proposed change. > > From: > 2.1. Registry Operator MUST deploy an EPP mechanism by 1 August 2017 for > registrars to migrate registration data for Existing Domain Names (i.e., > transition from Thin to Thick). > 2.2. Registry Operator MUST upon request provide an alternative bulk > transfer mechanism by 1 February 2018 for registrars to migrate data for > Existing Domain Names (i.e., transition from Thin to Thick). The request > MUST be made by 1 August 2017. > > To: > 2.1. Registry Operator MUST deploy an EPP mechanism and an alternative > bulk transfer mechanism by 1 August 2017 for registrars to migrate > registration data for Existing Domain Names (i.e., transition from Thin to > Thick). > > > As for your question about the draft privacy memo to GNSO Council, the IRT > had agreed the implementation project will continue in parallel to any > activity related to the memo. This was agreed upon when the subject was > broached at the Helsinki ICANN meeting and again in subsequent meetings. > Our plan to continue with the implementation work including the Public > Comment has not changed. It is the goal of our implementation team to > press forward as best we can to meet the 1 February 2017 Announcement Date > per the project schedule we’ve agreed upon. > > Thanks for your support and look forward to our meeting tommorrow. > Dennis Chang > > On 10/3/16, 5:11 AM, "gtheo" <gtheo(a)xs4all.nl> wrote: > > Thanks Chris, for posting on the RrSG distribution list and engage with > our members. > > Theo > > Chris Pelling schreef op 2016-10-02 01:46 PM: > > Good afternoon all, > > > > First and foremost we have had ten registrars (including myself) > > interested in the alternative solution, so day one there will be at > > least 1 triggering it - as that will be me. > > This being just the RrSG folks, once ICANN reach out to all registrar > > from GDD, I am positive you will find more. But, as mentioned - I > have > > had active requests for the alternative to be created. > > > > Further questions: > > > > 1. The Verisign/GNSO memo, does this need to go directly to GNSO, or, > > via ICANN legal first, I assume this will happen before the public > > comment period? > > > > 2. Alan G. said that a legal review by ICANN legal is needed (I > > mentioned to include EU lawyers) because the original legal review in > > 2015 did not include Safe Harbor, nor contemplating that Safe Harbor > > would be invalidated, where are we on this and I assume this will > > happen before the public comment period? > > > > 3. Implementation notes state there is a procedure for handling whois > > conflicts. However, the current method for handling WHOIS conflicts > is > > not working, and the WHOIS IAG version is at the GNSO and still does > > not include an effective procedure as EU privacy regulators are not > > giving statements to trigger the procedure. So this kind of sits at > a > > stalemate, is ICANN going to remove this? (I would assume they can't, > > but we do need more info/guidance) > > > > The above points 1 and 2, will these happen before the public comment > > period or after? Please note if you state afterwards, we are all > > potentially sitting here wasting time, as once those 2 legals come > > back, it is more than likely we will all end up reviewing those and > > going for a second public comment period based on new findings and > > changes to existing work - I am just trying to save time here (and > > everyone's sanity) :-) > > > > Kind regards, > > > > Chris > > _______________________________________________ > > Gnso-impl-thickwhois-rt mailing list > > Gnso-impl-thickwhois-rt(a)icann.org > > https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt > > > > _______________________________________________ > Gnso-impl-thickwhois-rt mailing list > Gnso-impl-thickwhois-rt(a)icann.org > https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt

1 0

Re: [Gnso-impl-thickwhois-rt] Thick Whois Transition Policy draft v4
by Anderson, Marc Oct. 3, 2016

Oct. 3, 2016

Dennis, Thank you for sending out this updated version. In preparation for our upcoming call I have a couple items. · Section 2.2 pertains to Registries providing an (alternative) bulk method for the backfill of contact data. I’d like to propose an update to the language in this section. Could I have some time during the meeting to present? · At the last meeting I brought up the billing contact and agreed to propose clarifying language. I suggest adding a section 2.11 that states: The “Billing” contact is optional. Registry Policy may define if it is required, optional or not supported. If supported the Billing contact information must be displayed as described in the “Advisory: Clarifications to the Registry Agreement, and the 2013 Registrar Accreditation Agreement (RAA) regarding applicable Registration Data Directory Service (Whois) Specifications” (section 22). I’d also like to get the IRT’s thoughts on the Billing contact in general. My sense is that no one is really concerned if the billing contact is present or not and that in order to facilitate the transition from thin to thick it would be easiest to not include it. · Finally, can we add an agenda item to talk about Escrow of contact data? It was a topic considered during the PDP deliberations but we haven’t touched on it as part of the IRT deliberations. Thank you, Marc Anderson From: gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Thursday, September 22, 2016 12:22 PM To: gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org> Subject: [Gnso-impl-thickwhois-rt] Thick Whois Transition Policy draft v4 Dear Thick Whois IRT, Attached are the Transition Policy drafts from our review this week. A clean and redlined provided for your further review. Three key updates are 1) Adapted the alternate definition of Thick 2) Incorporated the requirements to the body of policy per sections rather than the definition 3) Removed sections referring to RDAP Please provide your comments prior to the meeting if possible so that we may continue to discuss on line and prepare better for the team meeting next week. Agenda for the next meeting will be provided to you in a separate email which you may also comment on. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> "One World, One Internet"

7 12

[UPDATE] Meeting Recording and Chat Transcript Available (27 Sep 2016)
by Aysegul Tekce Oct. 3, 2016

Oct. 3, 2016

Dear Colleagues, The transcript from our meeting on 27 September is now available and posted on the IRT Meeting's workspace: https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minutes Thank you for your attention. Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227 From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Aysegul Tekce <aysegul.tekce(a)icann.org> Date: Wednesday 28 September 2016 at 09:40 To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: [Gnso-impl-thickwhois-rt] Meeting Recording and Chat Transcript Available (27 Sep 2016) Dear Colleagues, The recording and chat transcript from our latest meeting (Tuesday 27 September) are now available on the IRT Meeting's workspace: https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minutes We will post the meeting transcript once it is available. Thank you for your attention. Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227

1 0

Thick Whois IRT Meeting Agenda for 4 October 2016 Meeting
by Dennis Chang Oct. 1, 2016

Oct. 1, 2016

Dear Thick Whois IRT, Agenda for our next meeting has been posted on the IRT wiki: https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minute… Provide below for your convenience. Agenda: * Revised CL&D Consensus Policy (Dennis Chang email: 21 September 2016) * Transition from Thin to Thick * Draft Consensus Policy document review - Draft Version 5 * Public Comment readiness * Draft memo to GNSO Council regarding Privacy (Mark Anderson email 26 August 2016) * WHOIS Privacy Conflicts Procedure (Theo Geurtz email 4 September 2016) * https://www.icann.org/resources/pages/whois-privacy-conflicts-procedure-200… * Next Steps — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

2 2

Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration
by Dennis Chang Sept. 29, 2016

Sept. 29, 2016

Dear IRT members, As you know, on 7 February 2014, the ICANN Board adopted GNSO consensus policy recommendations regarding the provision of “Thick” Whois by all gTLD registries. In consultation with the consensus policy Implementation Review Team (IRT), the implementation team identified two expected outcomes in the policy development process (PDP) recommendations: * The consistent labeling and display of WHOIS output for all gTLDs * The transition from Thin to Thick WHOIS for .COM, .NET and .JOBS The first outcome was published as a consensus policy, the Registry Registration Data Directory Services Consistent Labeling and Display Policy<https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en> (CL&D Policy), on 26 July 2016. In August 2016, the Registry Stakeholder Group (RySG) submitted a Request for Reconsideration<https://www.icann.org/resources/pages/reconsideration-16-10-rysg-request-20…> (RfR) regarding the CL&D Policy. The RfR objects to the inclusion of RDAP as part of the Consensus Policy as RDAP was not contemplated or referenced in the policy recommendations. To resolve this matter, ICANN proposes the following path forward for the IRT: 1. ICANN to issue a revised CL&D Policy to all registry operators, removing provision 12. For your reference, provision 12 states: “The implementation of an RDAP service in accordance with the "RDAP Operational Profile for gTLD Registries and Registrars<https://www.icann.org/rdap-gtld-profile>" is required for all gTLD registries in order to achieve consistent labeling and display.” Additionally, I have attached the proposed revised CL&D Policy. 2. Issue a revised notification to registry operators regarding implementation of the CL&D Policy, clearly indicating what has changed in the revised CL&D Policy. 3. Set the revised CL&D Policy effective date to allow for full 6-month implementation from the date of the revised notice. 4. Update the published CL&D Policy on the ICANN website, noting a change has been made. Note: The revised CL&D Policy would not be subject to another Public Comment process. 5. Rescind the notification sent to registrars to implement RDAP. ICANN intends to issue notices for registries and registrars to implement RDAP after further dialogue with the community. Please let us know if you have comments or concerns by responding to this list. Unless we hear otherwise, we intend to move forward with the plan outlined above on 4 October 2016. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

5 8

Meeting Recording and Chat Transcript Available (27 Sep 2016)
by Aysegul Tekce Sept. 28, 2016

Sept. 28, 2016

Dear Colleagues, The recording and chat transcript from our latest meeting (Tuesday 27 September) are now available on the IRT Meeting's workspace: https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minutes We will post the meeting transcript once it is available. Thank you for your attention. Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227

1 0

Thick Whois IRT Meeting Agenda - 27 October 2016 Meeting
by Dennis Chang Sept. 28, 2016

Sept. 28, 2016

Dear Thick Whois IRT, Agenda for the 27 October 2016 meeting has been posted on the IRT Wiki page. https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minute… Provided here for your convenience. 27 September 2016 ________________________________ * Agenda: * Revised CL&D Consensus Policy (Dennis Chang email: 21 September 2016) * Transition from Thin to Thick * Draft Consensus Policy document review - Draft Version 4 (Dennis Chang email 22 September 2016) * Public Comment readiness * Draft memo to GNSO Council regarding Privacy (Mark Anderson email 26 August 2016) * WHOIS Privacy Conflicts Procedure (Theo Geurtz email 4 September 2016) * https://www.icann.org/resources/pages/whois-privacy-conflicts-procedure-200… * Next Steps Please feel free to provide your comments on the meeting agenda. — Kind Regards, Dennis S. Chang GDD Services & Engagement Program Director +1 213 293 7889 Skype: dennisSchang www.icann.org "One World, One Internet"

3 2

ICANN New Adobe Connect Rooms
by Aysegul Tekce Sept. 28, 2016

Sept. 28, 2016

Dear all, ICANN has implemented new Adobe Connect (AC) rooms. This will have little immediate impact on community members. Our Adobe room URL for Thick Whois IRT meetings has changed. It is no longer https://icann.adobeconnect.com/thick-whois-irt/ and this URL is now replaced by https://participate.icann.org/thick-whois-irt This will of course be reflected immediately on all email and calendar invitations. Reminders of the change will be made clear on all conference call communications from today onwards. If you have any questions, please send email to me. Kind regards, Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227

1 0

[UPDATE] Meeting Recording and Chat Transcript Available (20 Sep 2016)
by Aysegul Tekce Sept. 24, 2016

Sept. 24, 2016

Dear Colleagues, The transcript from our meeting on 20 September is now available and posted on the IRT Meeting's workspace: https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minutes Thank you for your attention. Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227 From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Aysegul Tekce <aysegul.tekce(a)icann.org> Date: Thursday 22 September 2016 at 19:32 To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: [Gnso-impl-thickwhois-rt] Meeting Recording and Chat Transcript Available (20 Sep 2016) Dear Colleagues, The recording and chat transcript from our latest meeting (Tuesday 20 September) are now available on the IRT Meeting's workspace: https://community.icann.org/display/TWCPI/IRT+Meetings%3A+Agenda+and+Minutes We will post the meeting transcript once it is available. Thank you for your attention. Aysegul Tekce Registry Services & Engagement Manager ICANN – Internet Corporation for Assigned Names and Numbers Istanbul, Turkey T: +90 212 999 6227

1 0