- Bc-gnso - lists.icann.org

ICANN Issues Advice to IT Professionals on Name Collision Identification and Mitigation
by Benedetta Rossi Dec. 6, 2013

Dec. 6, 2013

Dear BC Members, Please find below an ICANN Announcement regarding ICANN's issuing advice to IT Professionals on name collision identification & mitigation, an announcement of particular interest to business. Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org https://community.icann.org/display/gnsobc/Home www.bizconst.org <https://us.vocuspr.com/Publish/523509/vcsPRAsset_523509_86940_57ca243f-d7b1 -4920-86be-f143d373b689_0.jpg> FOR IMMEDIATE RELEASE 6 December 2013 ICANN Issues Advice to IT Professionals on Name Collision Identification and Mitigation Los Angeles, California.ICANN today issued comprehensive advice to IT professionals worldwide on how to proactively identify and manage private name space leakage into the public Domain Name System (DNS) and thus, eliminate the causes of name collisions as new Top Level Domains (TLDs) are added to the DNS. In a report titled Name Collision Identification and Mitigation for IT Professionals, ICANN explains the nature and causes of name collision and proposes a range of possible solutions. Domain name collisions are not new. However the report addresses some concerns that a number of applied-for new TLDs may be identical to names used in private name spaces." The report explains how DNS queries leak into the global DNS from private name spaces and how these leaks can have unintended consequences. The report shows that private networks will consistently, stably, and reliably perform name resolution when they use Fully Qualified Domain Names (FQDNs) and resolve them from the global DNS, and proposes methods to migrate to FQDNs. "While it appears that name collisions won't affect significant numbers of corporate network operators or Internet users, ICANN considers it essential that it does everything possible to minimize potential impact and to offer clear advice on dealing with the issue," said Paul Mockapetris, Global Domains Division Security Advisor. The report recommends that every organization that is not already using FQDNs from the public DNS should consider the following strategy: * Monitor name services, compile a list of private TLDs or short unqualified names you use internally, and compare the list you create against the list of new TLD strings. * Formulate a plan to mitigate causes of leakage. * Prepare users for the impending change in name usage by notifying them in advance or providing training * Implement your plan to mitigate the potential collision The release of today's advice to IT professionals is the result of several months of diligent work by ICANN's staff, subject matter experts, the ICANN Executive Team and the Board of Directors. "The report we've issued today offers IT professionals, whether they work in large organizations or small companies, comprehensive advice and suggested remedies that can be simple to implement," said Dave Piscitello, Vice President of Security and ICT Coordination. "While other interim or makeshift solutions may exist, migration using FQDNs has lasting value - once you've done this, you are good to go for now and future new TLD delegations." The report, along with additional useful information and resources, can be found at: http://www.icann.org/en/help/name-collision. ### MEDIA CONTACTS: Brad White Director Global Media Affairs Washington, D.C. Tel: +1.202.570.7118 E: brad.white(a)icann.org James Cole ICANN Global Media Coordinator Washington, D.C. Tel. +1 202.570.7240 E: james.cole(a)icann.org Andrew Robertson Edelman Public Relations London, U.K. Tel. + 44 (7811) 341 945 E: andrew.robertson(a)edelman.com About ICANN: ICANN's mission is to ensure a stable, secure and unified global Internet. To reach another person on the Internet you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN coordinates these unique identifiers across the world. Without that coordination we wouldn't have one global Internet. ICANN was formed in 1998. It is a not-for-profit public-benefit corporation with participants from all over the world dedicated to keeping the Internet secure, stable and interoperable. It promotes competition and develops policy on the Internet's unique identifiers. ICANN doesn't control content on the Internet. It cannot stop spam and it doesn't deal with access to the Internet. But through its coordination role of the Internet's naming system, it does have an important impact on the expansion and evolution of the Internet. For more information please visit: <http://www.icann.org> www.icann.org. If you would rather not receive future communications from ICANN, let us know by clicking here. <http://ICANN.pr-optout.com/OptOut.aspx?523509x19831x97619x1x3785396x24000x6 &Email=david.olive%40icann.org> ICANN, 12025 Waterfront Drive Suite 300, Los Angeles, CA 90094-2536 United States

1 0

Policy & Implementation - Request for Input
by Benedetta Rossi Dec. 6, 2013

Dec. 6, 2013

Dear BC Members, Please find below an ICANN call for input for the Policy & Implementation WG. Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org https://community.icann.org/display/gnsobc/Home www.bizconst.org Dear SG/Constituency Chair: We are the Chairs of the newly constituted Policy & Implementation Working Group. This Working Group (WG) has been tasked with providing the GNSO Council with a set of recommendations on the following issues: * A set of principles that would underpin any GNSO policy implementation related discussions, taking into account existing GNSO procedures; * A process for developing gTLD policy, perhaps in the form of "Policy Guidance," including criteria for when it would be appropriate to use such a process (for a process developing something other than "Consensus Policy") instead of the GNSO Policy Development Process; * A framework for implementation related discussions associated with GNSO Policy recommendations; * Criteria to be used to determine when an action should be addressed by a policy process and when it should be considered implementation; and * Further guidance on how GNSO Implementation Review Teams, as defined in the PDP Manual, are expected to function and operate. As part of the effort, the WG wants to reach out at the beginning of our efforts to the various GNSO Stakeholder Groups and Constituencies as we have already done to other Supporting Organizations and Advisory Committees to gain input to assist us in our efforts. In this regard, we would ask for your organization to consider the following questions which are set out in the WG's Charter and provide us with your input on any of these issues by 31 January 2014. 1. What guidance do the ICANN core values (Bylaws Article 1, Sec. 2) directly provide with regard to policy development work and policy implementation efforts? (e.g., multi-stakeholder participation). 2. What guidance do other ICANN core values provide that relate indirectly to policy development and policy implementation? (e.g., effective and timely process). 3. "Questions for Discussion" contained in the Policy versus Implementation Draft Framework prepared by ICANN staff. (See, http://www.icann.org/en/news/public-comment/policy-implementation-31jan13-en .htm). 4. What lessons can be learned from past experience? a. What are the consequences of action being considered "policy" vs. "implementation"? b. Does it matter if something is "policy" or "implementation"? If so, why? c. Under what circumstances, if any, should the GNSO Council make recommendations or state positions to the Board on matters of policy and implementation as a representative of the GNSO as a whole? d. How do we avoid the current morass of outcome-derived labeling (i.e., I will call this "policy" because I want certain consequences or "handling instructions" to be attached to it?) e. Can we answer these questions so the definitions of "policy" and "implementation" matter less, if at all? 5. What options are available for policy ("Consensus Policy" or other) and implementation efforts and what are the criteria for determining which should be used? a. Are "policy" and "implementation" on a spectrum rather than binary? b. What are the "flavors" of policy and what consequences should attach to each "flavor? c. What happens if you change those consequences? 6. Who determines the choice of whether something is "policy" or "implementation"? a. How is policy set/recommended/adopted and do different paths lead to different "flavors"? b. How is the "policy" versus "implementation" issue reviewed and approved? c. What happens if reviewing bodies come to a deadlock? 7. What is the process by which this identification, analysis, review and approval work is done? a. How are "policy and implementation" issues first identified (before, during and after implementation)? b. What is the role of the GNSO in implementation? c. In order to maintain the multi-stakeholder process, once policy moves to implementation, how should the community be involved in a way that is meaningful and effective? d. Should policy staff be involved through the implementation process to facilitate continuity of the multi-stakeholder process that already occurred? Alternatively, if you would prefer to set up an exchange of views by teleconference, the Working Group would welcome such an approach as well. Finally, we would like to remind you that the WG is open to the full community and we welcome any additional members from your organization that my wish to participate in this work. To review the current membership, please see https://community.icann.org/x/81V-Ag. Thank you in advance for your consideration. Please do not hesitate to reach out to either of us if you have any questions or if you require any additional information. Kind regards. Chuck Gomes (cgomes(a)verisign.com) J. Scott Evans (jscottevans(a)outlook.com)

1 0

GNSO Translation and Transliteration of Contact Information PDP Webinar Invitation
by Benedetta Rossi Dec. 4, 2013

Dec. 4, 2013

Dear BC Members, Please find below an invitation to the GNSO Translation and Transliteration of Contact Information PDP Webinar taking place on Tuesday, December 10th, 2013 and Wednesday, Dec. 11th, 2013. If you would like to take part in one of these two webinars, please follow the RSVP instructions in the message below. Thank you, Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org https://community.icann.org/display/gnsobc/Home www.bizconst.org GNSO Translation and Transliteration of Contact Information PDP Webinar Invitation Tuesday, 10 December 2013, 12 noon UTC; Wednesday, 11 December 18.00 UTC In order to participate, please RSVP via email to the GNSO Secretariat gnso-secs(a)icann.org You are invited to participate in an Introductory Webinar for the GNSO Working Group (WG) on Translation and Transliteration of Contact Information Policy Development Process (PDP). This Webinar is run to provide potential Working Group volunteers with relevant information prior to the launch of this WG. The presentation will cover some background on the GNSO Policy Development Process, the general expectancy with read to WG workload and deliverables. In addition, it will provide background information on the issue of Translation and Transliteration of Contact Information and give an overview of the WG's Charter. In the final section, will also explain the content and purpose of the related, staff-initiated feasibility study, the result of which are expected to feed into the WG's deliberations. Please note that the two sessions, on Tuesday 10 December 12.00 UTC and Wednesday 11 December at 18.00 UTC, are duplicates, scheduled to accommodate different time zones. Each session, scheduled to run for sixty (60) minutes, will be conducted in English only. The meeting will be run in Adobe Connect with a slide presentation along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may also be submitted using the chat function of Adobe Connect. If you are not able to participate in either of the live sessions, the recording of the session will be made available shortly after the meeting. The policy staff is always available to answer any questions that you email to policy-staff(a)icann.org. In order to participate, please RSVP via email to the GNSO Secretariat (gnso.secs(a)icann.org) to receive the call details. Please indicate which call you would like to join on Tuesday 10 December 2013, 12.00-13.00UTC - local times: http://tinyurl.com/m2suev5, or Wednesday 11 December 2013, 18.00-19.00UTC - local times http://tinyurl.com/kyk5lej. We will send you an email reminder before the event with log-in and dial-in details. Please, DO NOT RSVP to any other ICANN staff.

1 0

Policy calendar for 8-Aug-2013 BC member call
by Steve DelBianco Dec. 4, 2013

Dec. 4, 2013

There's a lot happening so I prepared a Policy Calendar for tomorrow's BC call. Channel 1. BC participation in ICANN Public Comment process: ICANN Public Comment page is <http://www.icann.org/en/news/public-comment> <http://www.icann.org/en/news/public-comment> here<https://www.icann.org/en/news/public-comment>. Selected comment opportunities below: 1. Draft report of expert working group (EWG) on next generation directory services (new WHOIS) (comments close 12-Aug). Current working draft is attached. I started with Stephane, J Scott and Bill Smith's version fmor 5-Aug and added the two paragraphs by Marie Pattullo on 6-Aug. Let's discuss on the call. Issues on the table include: Are Bill and others okay with Marie's language to express concerns about SSR? Are we comfortable with Stephane's gentle suggestion that this could apply to ccTLDs, too? Should "Commercial entities" be prevented from using privacy/proxy services? 2. Renewal of .org registry agreement (reply comments close 12-Aug) 3. Draft report on universal acceptance of IDN TLDs (reply comments close 16-Aug) 4. Postponement of GNS review (reply comments close 29-Aug) 5. .mobi and .pro request to remove cross-ownership restrictions (initial comments by 16-Aug) 6. Locking of domain name subject to UDRP proceeding (PDP), board recommendation (initial comments by 23-Aug) 7. Proposal to mitigate name collision risks from new gTLD delegations (initial comments by 27-Aug) 8. Rights Protection Mechanism (RPM) requirements (initial comments by 27-Aug) 9. Charter amendment process for GNSO Structures (initial comments by 28-Aug) Note: BC members are encouraged to submit individual / company comments. The BC selects topics on which to submit official positions based on member interest. Geographic Indicator Debate On 1-Aug a discussion thread was begun by J Scott Evans regarding the "Geographic Indicator Debate at Durban", including broader issue of GAC's role. There is no firm deadline for this issue and ICANN has not posted GAC Advice for public comment. We have offers to draft from J Scott Evans, Stephane, and Sarah Deutsch so far. Would the volunteer drafters be willing to circulate a letter for member consideration? --- Channel 2. Support for discussion and votes of our representatives on GNSO Council John Berard and Zahid Jamil, BC Councilors Report on Council telecon meeting held 1-Aug-2013. (agenda<http://gnso.icann.org/en/meetings/agenda-council-01aug13-en.htm>) Next Council telecon meeting is 5-Sep-2013, 15:00 UTC --- Channel 3. Supporting discussion/voting on matters before the Commercial Stakeholders Group (CSG) Marilyn Cade, CSG Liaison --- Channel 4. BC statements and responses during public meetings (outreach events, public forum, etc.)

14 21

MSI Panel: A Call to Action
by Benedetta Rossi Dec. 3, 2013

Dec. 3, 2013

Dear BC Members, Please find below an announcement for a call for action for volunteers for the MSI Panel (ICANN Strategy Panel on Multistakeholder Innovation). Thank you, Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org https://community.icann.org/display/gnsobc/Home www.bizconst.org <https://gallery.mailchimp.com/1a990feb5c/images/logo_icann_ideascale_3_.png > Designing a 21st Century ICANN Hello! The <http://www.icann.org/en/about/planning/strategic-engagement/multistakeholde r-innovation> ICANN Strategy Panel on Multistakeholder Innovation (the MSI Panel) and <http://thegovlab.org/> The Governance Lab @ NYU (The GovLab) recently launched an online engagement effort aimed at helping to design a 21st century Internet Corporation for Assigned Names and Numbers (ICANN) - the public interest organization responsible for coordinating the Internet's Domain Name System (DNS). We are writing to request your participation in this important initiative and to help us spread the word! The MSI Panel has been charged with: . Proposing new models for international engagement, consensus-driven policymaking and institutional structures to support such enhanced functions; and . Designing processes, tools and platforms that enable the global ICANN community to engage in these new forms of participatory decision-making. The Panel is a small group of seven with no monopoly on the best ideas for what ICANN should or should not do to coordinate the DNS in the public interest. All suggestions to make ICANN more effective and more democratic - whether constitutional, structural, legal, procedural or technological - will be welcome. While we cannot decide for ICANN, the aim of the MSI Panel is to use its authority to push for real change. Thus, we want ideas that are concrete and specific for innovative processes, structures, platforms, and techniques to design a 21st century ICANN. To gather and organize your input - we're launching this campaign in three stages: Stage 1: Idea Generation - Starting November 19th and running for six weeks via an ideation platform, Ideascale. You can access our <http://bit.ly/1dS9sLp> MSI Panel community page here. On the page, you can submit any and all concrete ideas you have. You can rate and rank others' for importance and practicality. November 19 - December 31. Stage 2: Proposal Development - Submissions will be grouped into general proposals and opened to discussion using a blog with line-by-line annotation features. This phase will be designed to take ideas closer to implementation. January 14 - January 21. Stage 3: Collaborative Drafting - Using a wiki, we will invite collaborative drafting on specific proposals that the Panel will submit to the ICANN CEO, Board and community. January 28 - February 11. To help us spread the word, we ask you to do any of the following: . Submit ideas and encourage members of your network/community to contribute to the Ideascale community site by providing them with the link: <http://thegovlab.ideascale.com/> http://thegovlab.ideascale.com/. . Broadcast our "Call To Action," for this initiative, which is online <http://bit.ly/HWNxrW> here, as widely as possible within your networks. Feel free to link to this post or repost on your website edited to fit your needs. . Share this information within your community and network via mailing lists and listservs. . Use social media platforms such as Facebook or Twitter to spread the word about the campaign. Don't forget to use the hashtag #WeCANN. . To inspire participation and learn how to contribute, watch and share a <http://bit.ly/185t28Q> video The GovLab has made for the launch of this distributed brainstorm. . Host your own brainstorming forum and share ideas generated with the MSI Panel on our Ideascale community page. For more information, visit The GovLab at <http://www.thegovlab.org/> www.thegovlab.org. Thanks and best, The MSI Panel & The GovLab

1 0

Budgets under scrutiny as the trademark tipping point comes to gTLDs - Blog - World Trademark Review
by Phil Corwin Nov. 29, 2013

Nov. 29, 2013

FYI. http://www.worldtrademarkreview.com/daily/detail.aspx?g=05620c0d-6c9c-4e26-… Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/Cell Twitter: @VLawDC "Luck is the residue of design" -- Branch Rickey Sent from my iPad

1 0

Call for Volunteers GNSO Policy Translation and Transliteration PDP Working Group
by Benedetta Rossi Nov. 27, 2013

Nov. 27, 2013

Dear BC Members, Please find below a call for volunteers for the GNSO Policy Translation and Transliteration PDP Working Group. Kind Regards, Benedetta Rossi BC Secretariat bc-secretariat(a)icann.org https://community.icann.org/display/gnsobc/Home www.bizconst.org Call for Volunteers GNSO Policy Translation and Transliteration PDP Working Group In Brief The Generic Names Supporting Organization (GNSO) Council is seeking volunteers to serve on the PDP Working Group (WG) on Translation and Transliteration of Contact Information. This WG is expected to make recommendations to the GNSO Council on whether it is desirable to translate or transliterate contact information. In this context, translation is the process of conveying the meaning of text from on language into another; transliteration is the process of representing the characters of one alphabetical or syllabic system of writing by the characters of another, conversion alphabet. Introductory Webinar To provide potential volunteers with an idea of the PDP Process including Working Group procedures and also some background information on the WG's substantive issues, an Introductory Webinar will be held at the following times: Tuesday 10 December 2013, 12.00-13.00UTC - local times: <http://tinyurl.com/m2suev5> http://tinyurl.com/m2suev5 Wednesday 11 December 2013, 18.00-19.00UTC - local times <http://tinyurl.com/kyk5lej> http://tinyurl.com/kyk5lej To join the webinar please RVSP to gnso-secs(a)icann.org First meeting If you are interested in joining the Working Group, please contact gnso-secs(a)icann.org. The first meeting of the Working Group is currently foreseen to take place in the week of 16 December - a doodle poll will be send out the week prior to determine a convenient meeting time. Background . Following the Recommendations of the Final Report <http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf> of the Internationalized Registration Data Working Group, a Final Issue Report <http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13 -en.pdf> on Translation and Transliteration of Contact Information was submitted to the GNSO Council on 21 March 2013 . GNSO Council's initiated <https://community.icann.org/display/gnsocouncilmeetings/Motions+13+June+201 3> a Policy Development Process (PDP) on the translation and transliteration of contact information on 13 June 2013; Drafting Team was formed and Charter <http://gnso.icann.org/en/drafts/transliteration-contact-charter-06nov13-en. pdf> submitted to GNSO Council and approved <http://gnso.icann.org/en/group-activities/calendar#nov> on 20 November 2013. . As part of its deliberations on this issue, Charter stipulates several questions for the PDP WG to consider, including (but not limited to): - Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script. - Who should decide who should bear the burden translating contact information to a single common language or transliterating contact information to a single common script. * For more detailed, consult the WG's Charter <http://gnso.icann.org/en/drafts/transliteration-contact-charter-06nov13-en. pdf> and the GNSO Policy Development Process <http://gnso.icann.org/en/node/31379/> . Note GNSO Council also requested ICANN to commission a study on the commercial feasibility of translation or transliteration systems for internationalized contact data, which is expected to be completed in time to help inform the PDP Working Group in its deliberations. Relevant Documents . Charter Translation and Transliteration of Contact Information PDP Working Group (WG) Charter - http://gnso.icann.org/en/drafts/transliteration-contact-charter-06nov13-en.p df . Final Issue Report on Translation and Transliteration of Contact Information (http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13 -en.pdf). . Final Report of the Internationalized Registration Data Working Group (http://gnso.icann.org/en/issues/ird/final-report-ird-wg-07may12-en.pdf) . GNSO Working Group Guidelines, including charter guidelines ( <http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf> http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf)

1 0

FILED: BC Comments on Study of Whois Privacy/Proxy Abuse
by Steve DelBianco Nov. 26, 2013

Nov. 26, 2013

As confirmed at the BC meeting in Buenos Aires last week, we filed comments on ICANN’s latest study of Whois Privacy/Proxy abuse. See link<http://forum.icann.org/lists/comments-whois-pp-abuse-study-24sep13/msg00013…> and below. Thanks to Elisa Cooper and Susan Kawaguchi for drafting. -- The Business Constituency (BC) supports the conclusions of the study as being consistent with our long-held belief that a significant portion of bad actors are using privacy and proxy services to facilitate abuse that harms business and consumer interests. The BC encourages the ICANN community to move forward with accreditation of privacy and proxy services in order to help the business community address abuse through increased access to accurate registrant information. The study examined and supported the hypothesis that “a significant percentage of the domain names used to conduct illegal or harmful Internet activities are registered via privacy and proxy services to obscure the perpetrator’s identity.” It provides important information for the ICANN community, as Whois accuracy and completeness is a primary goal at this time. The conclusions clearly demonstrate that an overhaul of the system is not only warranted, but necessary. The BC recognizes that there are legitimate uses for privacy and proxy services, such as shielding the identity of those engaged in non-commercial free speech, or the launch of a new product and/or service in the business community. However, the information contained in the study, which illustrates widespread abuse detrimental to consumers and businesses alike, clearly demonstrates the need to proactively restrict the use of privacy and proxy services to organizations and individuals that are using them for legitimate purposes. The BC also recognizes that stopping privacy and proxy service abuse is not the only way to stop abusive behavior online. When domain names are registered with the intent of conducting illegal or harmful Internet activities, a range of different methods are used to avoid providing viable contact information. The BC looks forward to addressing all of these issues in the community-led development stage of the Aggregated Registration Directory Service. In the meantime, the BC encourages the ICANN to give attention to the issues that can be addressed immediately. We note that although this study covered 5 TLDs, .com names dominated the datasets — only 10% were from the other 4 gTLDs. Given that, one possible approach may be for the .com registry to implement privacy and proxy services guidelines as an interim measure. This could be much faster than having ICANN make rules for all gTLDs. We would still want the proxy/privacy vendors accredited, but there may be an interim solution with the registry itself. The BC looks forward to participating in the GNSO RAA Remaining Issues Policy Development Process on Privacy and Proxy Services, to develop an accreditation system which restricts the shielding of registrant data to legitimate, non-commercial, non-abusive websites. The BC thanks ICANN and the NPL for this comprehensive study. These comments were drafted by Elisa Cooper and Susan Kawaguchi, and were approved in accord with our charter. -- Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

1 0

Pub Forum topic breakdown
by Steve DelBianco Nov. 21, 2013

Nov. 21, 2013

Here’s what Crocker just said: WE COLLECTED 14 TOPICS, SUGGESTIONS. WE'VE GROUPED THEM INTO THREE GROUPS. LET'S SEE. IS THERE A SLIDE THAT HAS -- NO, OKAY. SO THE FIRST GROUP IS ON MULTISTAKEHOLDERISM AND TRUST ISSUES. WHAT ELSE DID WE SAY ABOUT THAT? THERE WILL BE A COLLECTION OF TOPICS THERE. I SHOULD PULL THESE UP IN JUST A SECOND. THE SECOND GROUPING WILL BE AROUND THE gTLD PROGRAM AND THE SPECIFIC ISSUES THERE. AND THEN IN THE THIRD, AS PART OF BUT NOT THE ENTIRETY OF THE LAST SESSION A SERIES OF FOUR TOPICS AND WITH APOLOGIES, I OWE YOU WHAT THAT LIST IS. I WILL HAVE IT FOR YOU MOMENTARILY HERE. HEARING, MULTISTAKEHOLDER MODEL, ACCOUNTABILITY AND TRUST, STRENGTHENING AND BROADENING THE BOTTOM OF THE MULTISTAKEHOLDER PROCESS, UNIVERSAL ACCEPTANCE, ACCOUNTABILITY OF PARTIES ACCEPTED BY ICANN TOWARD INTERNET USERS AND THEIR COMMUNITIES, ICANN'S ROLE AND RESPONSIBILITIES TO THE INTERNET, WHAT ICANN SHOULD DO BEYOND DNS, AND HOW TO REPAIR THE TRUST IN THE MULTISTAKEHOLDER MODEL IN LIGHT OF THE SNOWDEN REVELATIONS. OLGA MADRUGA-FORTI WILL MODERATE THIS SESSION. AND WE WILL START WITH THAT. THE NEW gTLD PROGRAM ISSUES WILL ENCOMPASS ICANN CONTRACTS VERSUS LOCAL LAW, STRING CONFUSION AND NEW gTLDs, BULK ACCEPTANCE OF WHOIS INACCURACY AND COMPLAINTS, NEW gTLD PROGRAM, WAS IT A SUCCESS OR FAILURE. NAME COLLISIONS, ICANN ACTING IN THE PUBLIC INTEREST, AND THEN UNDER THE THIRD SESSION, GONZALO NAVARRO WILL MODERATE THE SECOND SESSION -- AND UNDER THE LAST SESSION WHICH BERTRAND DE LA CHAPELLE WILL MODERATE, ICANN GOVERNMENT POLICY CONTROL IN THE ROOT, CONTROL OVER THE ROOT, THE MALVENIS, NOMCOM AND CONDUCTING OF THE PUBLIC FORUM.

1 0

Buenos Aires GAC communique
by Steve DelBianco Nov. 21, 2013

Nov. 21, 2013

Here it is. -- Steve DelBianco Executive Director NetChoice http://www.NetChoice.org and http://blog.netchoice.org +1.202.420.7482

1 0