March 2014 - council - lists.icann.org

ICANN & NTIA
by Avri Doria March 21, 2014

March 21, 2014

Hi, I know it is too late for a motion, but will there be an opportunity to get 'sense of the council/gnso' on support for ICANN in this NTIA process? Personally I would like to see Jonathan able to support the ongoing work, without committing to any particular endpoint, but in the name of the GNSO of which he is chair. I know we have an agenda of very important issues, but I beleive we cannot afford to ignore this milestone in Internet governance without push ourselves further into irrelevancy. avrti

8 8

FW: Protections of IGO acronyms
by Jonathan Robinson March 21, 2014

March 21, 2014

All, Please see the attached. Jonathan From: Cherine Chalaby [mailto:cherine.chalaby@icann.org] Sent: 20 March 2014 18:30 Subject: Protections of IGO acronyms Dear Jonathan, Attached please find a letter regarding protections for IGO acronyms. This letter describes the proposal shared with the GAC and acknowledges some potential differences with GNSO policy. It is therefore important that the GNSO receives this letter prior to the official launch of the Singapore meeting. Please let me know if you have any questions or concerns. Best regards, Cherine

2 2

EWG - Singapore Workshop - time & room change
by Glen de Saint Géry March 20, 2014

March 20, 2014

Dear All, We want to alert you to a time and room change for the the Expert Working Group (EWG) on Next-generation gTLD Registration Directory Services (RDS) Singapore workshop: Exploring Replacements for WHOIS - The Next Generation Directory Services<http://singapore49.icann.org/en/schedule/mon-gtld-directory-services>. It will be held on Monday, 24 March at 16:30-17:30 SGT in room Bras Basah. This open workshop will feature an update on EWG activities and a preliminary discussion about potential risks and benefits that might result if ICANN were to replace WHOIS by a next-generation system. All interested parties are invited to participate in this workshop and to continue the dialogue post-Singapore through an on-line RDS Risk Survey<http://tiny.cc/risk-ewg-survey> and interactive webinars that will be scheduled to gather broad community input on this topic. RDS Risk survey/webinar results will inform the EWG as it refines its recommendations for a next generation RDS. The EWG looks forward to hearing your thoughts and perspectives at their Singapore session (see http://singapore49.icann.org/en/schedule/mon-gtld-directory-services for further details and remote participation information). An announcement of the RDS Risk survey and webinars will be posted on the ICANN website and circulated on this list. The EWG may be reached at: input-to-ewg(a)icann.org<mailto:input-to-ewg@icann.org> (public list) should you have comments you would like to submit on the EWG's Status Update Report<http://www.icann.org/en/groups/other/gtld-directory-services/status-update-…>. We apologize for any inconvenience the workshop time change may have caused. The EWG decided to change the time (and to add webinars) to accommodate the community's participation in other key sessions that are being held simultaneously on Monday, 24 March. Thank you for your understanding. Regards, ICANN staff on behalf of the Expert Working Group

3 5

GNSO Draft schedule for Singapore meetings 2014
by Glen de Saint Géry March 20, 2014

March 20, 2014

Dear All, Please find the latest GNSO Schedule for the Singapore meetings. *There have been slight changes, mostly to the timing if meetings on Saturday and Sunday. The annotated Wiki agendas for Saturday and Sunday are found on the Full meeting schedule: http://singapore49.icann.org/en/schedule-full Saturday http://singapore49.icann.org/en/schedule/sat-gnso-working https://community.icann.org/display/gnsocouncilmeetings/GNSO+Working+Sessio… Sunday http://singapore49.icann.org/en/schedule/sun-gnso-working https://community.icann.org/display/gnsocouncilmeetings/GNSO+Working+Sessio… Thank you and please let me know if you have any questions. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

can somebody remind me what the "Teresa Swinehart Update" item is on Sunday?
by Mike O'Connor March 20, 2014

March 20, 2014

this is mostly aimed at David Cake or Jonathan. but any/all are welcome to help out. i’m looking at that Teresa Swinehart Update item on Sunday morning just before the Strat Panel section. i can’t remember what she’s updating us *about* can somebody remind me? sorry to be so dense, mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)

6 6

GNSO schedule in Singapore
by Glen de Saint Géry March 20, 2014

March 20, 2014

Dear All, Please find the updated GNSO Singapore Public Draft Agenda. Please note that the joint ccNSO/GNSO Council meeting has been moved from Monday to Wednesday 17:45 - 18:45 in Sofia. Please note that the GNSO Constituency /Stakeholder interaction on Tuesday has been moved to 19:00-20:00 so as not to conflict with the SO/AC cocktail with the CEO. If you have any questions, please let us know. Thank you. Kind regards Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

FInal Reports for last two Whois Studies published
by Mary Wong March 19, 2014

March 19, 2014

Dear all, You and your constituents/groups may be interested to know that we have just published the Final Reports on Whois Privacy & Proxy Abuse and on Whois Misuse on the GNSO website: http://gnso.icann.org/en/group-activities/other/whois/studies. The Final Report on Privacy and Proxy Abuse can be accessed at http://whois.icann.org/sites/default/files/files/pp-abuse-study-final-07mar1 4-en.pdf, and that for Whois Misuse at http://whois.icann.org/sites/default/files/files/misuse-study-final-13mar14- en.pdf. As you know, the preliminary reports for both studies were published in September and November 2013 respectively for public comment. A substantial number of comments were received, all of which were considered by both research teams (NPL & Dr. Richard Clayton for Privacy & Proxy; CMU's Cylab for Misuse). Both teams' Final Reports include additions and comments that address the public comments that were received. As you also know, the publication of these two reports means that the series of studies commissioned by the GNSO Council that were intended to gather objective data regarding various aspects of Whois are now complete. The GNSO Council can now beginning with the planned update session in Singapore start to consider possible next steps in relation to these studies, in the broader context of the other policy work that is now going on with respect to Whois. Cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names & Numbers (ICANN) Telephone: +1 603 574 4892 Email: mary.wong(a)icann.org * One World. One Internet. *

1 0

Proposed Agenda for the GNSO Council Public Meeting in Singapore, 26 March 2014 at 13:00 Local time Singapore
by Glen de Saint Géry March 18, 2014

March 18, 2014

Dear All, Please find the draft agenda for the GNSO Council Public Meeting in Singapore, 26 March 2014 at 132:00 UTC (05:00 UTC) posted on the Wiki at https://community.icann.org/display/gnsocouncilmeetings/Agenda+26+March+2014 and the motions are posted at: https://community.icann.org/display/gnsocouncilmeetings/Motions+26+March+20… Proposed Agenda for the GNSO Council Public Meeting in Singapore, 26 March 2014 This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf > For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Times 05:00 UTC http://tinyurl.com/q9vvomd Coordinated Universal Time 05:00 UTC 22:00 Los Angeles (Tuesday 25 March); 01:00 Washington; 05:00 London; 06:00 Paris; 13:00 Pert; 13:00 Singapore Dial-in numbers will be sent individually to Council members. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Administrative matters (5 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council meeting 27 February 2014 will be posted as approved on xxxx 2014 Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (5 mins) Item 4: MOTION - To approve the Charter for a GAC-GNSO Consultation Group on GAC Early Engagement in GNSO Policy Development Processes There is wide agreement on the need to engage the GAC early within the GNSO policy development process. This is something that has been highlighted on a number of occasions including through the Accountability and Transparency Review process. Accordingly, the GAC and the GNSO have formed a Consultation Group to work on the principles and mechanics of improved future early engagement. Here the GNSO Council will vote on whether to approve the charter for the GAC-GNSO Consultation Group. 4.1 - Review the motion 4.2 - Discussion 4.3 - Vote Item 5: MOTION - To close the Joint IDN Working Group and next steps for certain IDN-related Issues The Joint IDN Working Group (JIG) was chartered<https://community.icann.org/download/attachments/16843360/jiwg-charter.pdf?…> by the ccNSO and GNSO Councils in 2009 to discuss issues of common interest between the two Supporting Organizations in relation to Internationalized Domain Names (IDNs). The JIG identified three issues of common interest, viz. single character IDN TLDs, IDN Variant TLDs, and Universal Acceptance of IDN TLDs and went on to prepare a series of reports on these. Recognizing that further work needed to be done in relation to IDNs, in particular IDN variants and universal acceptance of IDNs, the ccNSO and GNSO Councils requested in November 2013 that the JIG put forward suggestions on how to deal with these issues and deliver these suggestions to the Councils by the ICANN Singapore Meetings in March 2014. Members of the JIG now support the ICANN staff recommendations that the ccNSO and GNSO Councils should each continue to monitor ICANN's community efforts to resolve issues relating to single character IDN TLDs, IDN Variant TLDs and Universal Acceptance of All TLDs (including IDN TLDs). Here the Council will vote to formally close the JIG and commit to the ongoing monitoring work. 5.1 - Review the motion 5.2 - Discussion 5.3 - Vote Item 6: MOTION - To approve the charter for a cross community working group to develop a finalised framework of operating principles for future CWGs The GNSO Council previously approved<http://gnso.icann.org/en/council/resolutions#201203> a set of initial draft principles<http://gnso.icann.org/drafts/draft-principles-for-cwgs-23dec11-en.pdf> relating to the formation and operation of cross community working groups (CWGs) and directed<http://gnso.icann.org/en/council/resolutions#201203> ICANN staff to solicit feedback on the principles from the other ICANN Supporting Organizations and Advisory Committees (SO/ACs). The GNSO Council then approved<http://gnso.icann.org/en/council/resolutions#201310> the formation of a Drafting Team to develop a Charter for a new CWG to take forward and synthesize the initial work of the GNSO and ccNSO feedback, and to develop a final framework of operating principles that can function effectively across all SO/ACs relating to the formation, operation, decision making and termination of future CWGs (the "Final Framework"). The Drafting Team, co-chaired by the ccNSO and GNSO, has now completed its work on a proposed charter for this new CWG. Here the Council will vote on whether to approve the proposed charter. 6.1 - Review the motion 6.2 - Discussion 6.3 - Vote Item 7: MOTION - To adopt the charter for a cross community working group to develop a framework for the use of country and territory names as TLDs The ccNSO Study group on the use of Names for Country and Territory published its Final Report in September 2013 (http://ccnso.icann.org/node/42227 ). One of the two recommendations of the Study Group to the ccNSO Council was to establish a cross community working group. The ccNSO Council adopted the recommendation and, as the objective of the proposed Working Group is considered to be of common interest to the broader community, the GNSO, in addition to other Supporting Organisations (SOs), Advisory Committees (ACs) and others, is invited to participate in the working group on equal footing. The ccNSO submitted a proposed charter [link] for this Cross-Community Working Group, which the GNSO Council has reviewed and discussed. Here the GNSO Council will vote on whether to adopt the proposed charter and to issue a call for volunteers to the CWG. 7.1 - Review the motion 7.2 - Discussion 7.3 - Vote Item 8: UPDATE & DISCUSSION - International Internet Governance Issues Discussions and activity relating to international Internet Governance issues are attracting a great deal of attention in ICANN and related groups. This item is on the agenda to provide an opportunity for discussion within the Council about how this impacts the role and work of the Council and mindful of the scope and remit of the Council, what action the Council should or could be taking. 8.1 - Status update 8.2 - Discussion 8.3 - Next steps Item 9: UPDATE & DISCUSSION - GNSO Engagement with the work of the ICANN Strategy Panels (15 mins) Here the Council will receive an update on any relevant interaction with and output from the strategy panels and discuss any appropriate action going forward. 9.1 - Status update 9.2 - Discussion 9.3 - Next steps Item 10: UPDATE & DISCUSSION - Forthcoming review of the GNSO (10 mins) As part of a periodic review process that is built into the ICANN model, ICANN board initiated reviews of the GNSO (and the GNSO Council and related functions) are expected. In order to be informed and effectively prepared for this work, we have begun to engage with the body that commissions such reviews (the structural improvements committee) through its chair, Ray Plazk. The Council will track the planning work of the SIC and, where appropriate; provide relevant input to the process. We will also prepare to undertake a form of self-review in a similar format to that which we expect to arise out of the work of the SIC. A self-review will ensure that we are not only prepared for the board initiated work but also able to flag areas for potential improvement in as timely as possible a manner. 10.1 - Update (Jennifer Wolfe) 10.2 - Discussion 10.3 - Next steps Item 11: Any Other Business (10 mins) * ICANN Board Seat 14 - NCPH - Additional Council meeting Thursday, 10 April 2014 at 14:00 UTC Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 05:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+0DST 22:00 (Tuesday 25 March) Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+0DST 00:00 New York/Washington DC, USA (EDT) UTC-4+0DST 01:00 Rio de Janiero, Brazil (BRST) UTC-3+0DST 02:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 02:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 02:00 London, United Kingdom (BST) UTC+0DST 05:00 Bonn, Germany (CET) UTC+1+0DST 06:00 Stockholm, Sweden (CET) UTC+1+0DST 06:00 Cairo, Egypt, (EET) UTC+2+0DST 07:00 Istanbul, Turkey (EEST) UTC+2+0DST 07:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 07:00 Beijing/Hong Kong, China/Singapore (HKT ) UTC+8+0DST 13:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 13:00 Singapore (SGT) UTC+8+0DST 13:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/q9vvomd Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Singapore Agenda Item: New gTLDs, Subsequent Application Rounds
by Bret Fausett March 18, 2014

March 18, 2014

Dear Councillors, I would like to propose that we add some time on our Singapore agenda for discussing next steps in preparation for Round 2 of the new gTLD launch. As you may know, in the Applicant Guidebook, ICANN wrote the following about subsequent new gTLD rounds: 1.1.6 Subsequent Application Rounds ICANN’s goal is to launch subsequent gTLD application rounds as quickly as possible. The exact timing will be based on experiences gained and changes required after this round is completed. The goal is for the next application round to begin within one year of the close of the application submission period for the initial round. ICANN has committed to reviewing the effects of the New gTLD Program on the operations of the root zone system after the first application round, and will defer the delegations in a second application round until it is determined that the delegations resulting from the first round did not jeopardize root zone system security or stability. It is the policy of ICANN that there be subsequent application rounds, and that a systemized manner of applying for gTLDs be developed in the long term. The "the close of the application submission period for the initial round” was May, 2012, so the goal for the launch of Round 2 has already been missed, by a material amount of time. I think we all would agree that many aspects of the program, from the application process to the review and implementation, should be reviewed and revisited. Let’s spend some time discussing “subsequent application rounds" and see if we can come to a shared understanding of what the proper next steps would be, including the role of the Council and the GNSO in the review process. I’m looking forward to seeing everyone in Singapore. Bret -- Bret Fausett, Esq. • General Counsel, Uniregistry, Inc. 12025 Waterfront Drive, Suite 200 • Playa Vista, CA 90094-2536 310-496-5755 (T) • 310-985-1351 (M) • bret(a)uniregistry.com — — — — — -- Bret Fausett, Esq. • General Counsel, Uniregistry, Inc. 12025 Waterfront Drive, Suite 200 • Playa Vista, CA 90094-2536 310-496-5755 (T) • 310-985-1351 (M) • bret(a)nic.sexy — — — — —

6 8

FW: Joint SO/AC/SG Leaders' Statement on the IANA Globalization Progress?
by Jonathan Robinson March 18, 2014

March 18, 2014

All, FYI. There is a proposal to prepare a joint statement on IANA globalisation on behalf of the ICANN SO & ACs.. This is currently being looked into / worked on within the GNSO and co-ordinated at the SG / Constituency leadership level. Jonathan From: David Olive [mailto:david.olive@icann.org] Sent: 17 March 2014 13:59 Subject: Re: Joint SO/AC/SG Leaders' Statement on the IANA Globalization Progress? Dear SO/AC/SG Leaders: Just to ad to my earlier note. Attached is a rough draft which may help to facilitate a joint statement. Comments are welcomed. Regards, David -- David A. Olive Vice President, Policy Development Support General Manager, ICANN Regional Headquarters Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Hakki Yeten Cad. Selenium Plaza No:10/C K:5 34349 Fulya, Besiktas, Istanbul, Turkey Tel: +90.212.381.8727 - Fax: +90.212.381.8731 - Mobile: +1. 202.341.3611 From: David Olive <david.olive(a)icann.org> Date: Sunday, March 16, 2014 10:42 PM To: Lars-Johan Liman <liman(a)netnod.se>, Byron Holland <byron.holland(a)cira.ca>, "Drazek, Keith" <kdrazek(a)verisign.com>, "Olivier MJ Crepin-Leblond (ocl(a)gih.com)" <ocl(a)gih.com>, "Kristina Rosette (krosette(a)cov.com)" <krosette(a)cov.com>, William Drake <wjdrake(a)gmail.com>, Rafik Dammak <rafik.dammak(a)gmail.com>, "Elisa Cooper (elisa.cooper(a)markmonitor.com)" <elisa.cooper(a)markmonitor.com>, Jun Murai <junsec(a)wide.ad.jp>, Patrik Fältström <paf(a)netnod.se>, "adiel(a)afrinic.net" <adiel(a)afrinic.net>, "louie(a)louie.net" <louie(a)louie.net>, Jonathan Robinson <jonathan.robinson(a)ipracon.com>, tony holmes <tonyarholmes(a)btinternet.com>, Heather Dryden <Heather.Dryden(a)ic.gc.ca>, marie-laure Lemineur <mllemineur(a)gmail.com>, Michele Neylon - Blacknight <michele(a)blacknight.com> Subject: Joint SO/AC/SG Leaders' Statement on the IANA Globalization Progress? Dear SO/AC/SG Leaders: In light of our recent conversations about this announcement, might it be appropriate for a short joint SO/AC/SG leaders' statement welcoming the US Government's announcement of the suggested changes related to the IANA functions contract. Such a statement could be an impressive demonstration of ICANN's multistakeholder Community working together and willing to be involved in next steps. This document could be shared in Singapore, maybe at the Monday session. An example might be found in the statement by the "Internet Technical Leaders Welcome IANA Globalization Progress" - attached. Please let me know if there would be any support for drafting such a statement. I would be ready to assist you in this task, if needed. Regards, David -- David A. Olive Vice President, Policy Development Supportthe General Manager, ICANN Regional Headquarters Istanbul Internet Corporation for Assigned Names and Numbers (ICANN) Hakki Yeten Cad. Selenium Plaza No:10/C K:5 34349 Fulya, Besiktas, Istanbul, Turkey Tel: +90.212.381.8727 - Fax: +90.212.381.8731 - Mobile: +1. 202.341.3611

2 1