- ALAC - lists.icann.org

Re: [ALAC] [IDN-WG] [APAC-Discuss] The Problem of IDNs
by Rinalia Abdul Rahim May 21, 2014

May 21, 2014

Hello, everyone. I trust that you have seen the CircleID article on Universal Acceptance of All TLDs by Stephane Van Gelder and the APTLD Oman meeting report on IDN, which I circulated earlier today. Next milestones to move the agenda forward on this issue for the At-Large: 1. ATLAS II Summit - the frame of the agenda could not be changed at this point for Saturday and Sunday (21-22 June). I would suggest that the issue be brought up by community members from the floor in relevant sessions so that others can be made aware of what this issue means to users of the global Internet. 2. A 30 mins briefing and discussion will be held on Monday 23rd June 2014 during the ALAC Meeting Hot Topic 3 - Universal Acceptance of IDNs - with Edmon Chung and Rinalia Abdul Rahim (16:45-17:15) (Moderator: Olivier Crépin-Leblond). 3. ICANN-staff organized session on the topic of Universal Acceptance - I expect a session will be held in London. Do attend that session as well to provide input to ICANN from the end user's perspective. Best regards, Rinalia

2 5

Update on IANA Stewardship Transition Work
by Rinalia Abdul Rahim May 20, 2014

May 20, 2014

Latest from Fadi on IANA Stewardship Transition. http://blog.icann.org/2014/05/transition-from-u-s-government-has-four-work-… Rinalia

1 0

Universal Acceptance of All TLDs
by Rinalia Abdul Rahim May 20, 2014

May 20, 2014

FYI > http://www.circleid.com/posts/20140519_universal_acceptance_of_all_tlds_now/ > > > > A piece by Stéphane Van Gelder on Universal Acceptance of TLDs. > > > > > > Universal acceptance of top level domains hasn't really meant much to most Internet users up until now. As long as .COM was basically the default TLD, there wasn't much of an issue. > > > > No longer. With 263 delegated strings (according to ICANN's May 12, 2014 statistics) adding to the existing 22 gTLDs that were already live on the net after the 2004 round of Internet namespace expansion, the problem of universal acceptance gets very real. > > > > What is the issue? Being able to use any TLD with any browser (Safari, Chrome, Firefox...) or email client (outlook, Apple mail...), no matter what the environment (Mac, Windows...). Non-ASCII Internationalized Domain Names (IDNs) have made the issue even more crucial because universal acceptance is needed to fulfil their promise: giving millions of people who use different keyboards and scripts access to an "own language" Internet use they've never been able to experience up until now. > > > > Non-Latin script TLDs are considered one of the most important Internet naming innovations of the last decade because they are key to reducing the digital divide between those who are comfortable typing ASCII web addresses and those who are not. Those whose native alphabets are Chinese, Arabic, Cyrillic or others have jumped at the chance to type their own scripts into the address bars. The high registration volumes reached by IDN ccTLDs like .рф (Romanised as .RF for Russian Federation) or more recently the Chinese character new gTLDs launched by TLD Registry .在线 (.ONLINE) and .中文网 (.WEBSITE) are clear indications of the pent-up demand for non-Latin script web addresses. > > > > > > Ensuring new web addresses can be used everywhere, by everyone > > > > Because they are that important, ICANN's new gTLD program has given deliberate priority to IDNs. The 104 applications for non-Latin script TLDs were allowed a faster track through the evaluation and delegation process if they wanted it. > > > > Despite that, most new gTLDs that have gone live so far are of the traditional ASCII kind. But as TLD Registry's suffixes show, the Internet is not going to stay all-Latin for long. Others also have ambitious plans to bring Internet navigation to new audiences using different alphabets. Stable Tone is one such registry operator. It will soon be launching 世界, (.WORLD in Chinese) with an innovative plan to bring international brands to Chinese audiences. > > > > Without universal acceptance, those plans will suffer. The products will be out there, but their intended audiences won't actually be able to use them. Why? Because in many ways, the Internet still works as if there had never been an expansion of its namespace. There are 3 main issues. > > > > Internet browsers tend to carry out summary checks when a destination is typed into their address bars. Some browsers will actually filter out anything that doesn't resemble the "classic" TLDs. Type www.example.guru, one of the new TLDs that is already proving very popular, and browsers expecting .COM or something similar will either tack that suffix on the end and search for www.example.guru.com, or take the user to a search engine to try and "help". > > > > The rate of expansion is also an issue. In 2004, only a very limited number of TLDs were added to the Internet root. So as suffixes like .BIZ and .INFO came online, browser developers had time to adjust. But the new gTLD program means an increase of several orders of magnitude for the number of TLDs becoming valid Internet namespaces. How can developers of browser, email and other Internet services keep up? > > > > IDNs have brought a third universal acceptance issue. Users must be able to type, and see, their URLs in the intended native script. If it's a Chinese address, you should be able to type that in as easily as if it was ASCII. Having to resort to some kind of encoder to get the Chinese script complicates the user experience to such an extent that there's a risk users simply won't bother. And that could ultimately mean the failure of IDN TLDs that, ironically, Internet users actually want. > > > > There's a fourth, slightly separate but equally important issue: mobile device use. Browsing and emailing environments tend to be even more technically limited on smartphones and tablets than they are on desktop computers. Yet those are the devices which the next billion Internet users, those that stand to benefit from new TLDs and especially IDNs, are most likely to use. > > > > All that leads to a situation where currently, there is a lack of universal acceptance for these new TLDs. Take those mentioned earlier. A web address like 房地产.在线 (RealEstate.online) simply isn't reachable using the majority of web browsers running on PCs and mobile devices in China. A part-ASCII address like nic.在线 has the same issues. > > > > Chinese data shows that around 50% of the browsers used in the country are not compatible with Chinese IDN gTLDs and that on mobile devices, tha vast majority of the browsers available aren't compatible. > > > > > > Single focus > > > > So what to do? Awareness of the problem isn't new. ICANN, for instance, has been working on it since 2004, when it opened a discussion forum on universal acceptance, and even before. Technically there are no major hurdles to universal acceptance. For example, the technology needed to correctly render IDN web addresses was developed even before the new gTLD program, when work was being done on the IDN ccTLD program designed to give a path to non-ASCII country codes to countries such as Russia, where .рф is considered the second national suffix after the ASCII .RU. > > > > The major stumbling block for universal acceptance today is probably coordination. And let's face it, that's an area where organisations like ICANN have traditionally not been very strong. ICANN, the technical community's IETF, and others, are very good at taking on a variety of problems at once. They are not so good at focusing their collective energies on a single problem. > > > > Yet that's exactly what's needed to guarantee universal acceptance. Across-the-board efforts targeting all aspects of this one problem. For example, if technical operators such as browser developers are not made sufficiently aware of new gTLDs by the governance community, then how can they be expected to adapt their products to suit? > > > > It's incumbent on the technical and governance communities to ensure that demand is met. Disappoint these non-ASCII hopefuls now, and new gTLDs as a whole will suffer the consequences.

1 0

Report from the High Level Panel
by Rinalia Abdul Rahim May 20, 2014

May 20, 2014

FYI > > Global Panel Announces New Approach to Managing Future of the Internet | Final Report Addresses Growing Interests in Internet Governance > > Click here to view the report » [PDF, 2.7 MB] > > The Panel on Global Internet Cooperation and Governance Mechanisms—a global Panel of prominent stakeholders from diverse organizations and governments—today released key recommendations on how to evolve the Internet governance (IG) ecosystem to accommodate global needs for collaboration, interconnectivity and Internet growth. The report also presents a roadmap and timeline for the future management of the Internet. > > The report follows the Panel's third and final meeting, hosted by the World Economic Forum in Dubai on 4-5 May. It adopts the IG principles established at NETmundial, the recent Global Multistakeholder Meeting on the Future of Internet Governance in São Paulo, Brazil. The Panel believes these principles— human rights, culture and linguistic diversity, security and stability, and open unfragmented space, among others—are fundamental to implementing a 21st century model of Internet governance. > > "It has been an honor to serve as the chair of this distinguished Panel, representing a diverse group of global stakeholders from government, civil society, the private sector, the technical community and international organizations," said Toomas Hendrik Ilves, President of Estonia and chairman of the Panel. "We intend for the Panel's work to contribute to the global discussion on how to preserve freedom of expression of the Internet." > > For the past six months, the Panel has worked to characterize key components for promoting a collaborative, decentralized IG ecosystem—one that can effectively meet the burgeoning needs and interests of Internet users globally, while ensuring networks' security and stability. The Panel identified needed Enablers—including forums and dialogues, expert communities and toolkits—to foster communication, legitimacy and effectiveness throughout the IG process, which the Panel defined in four elements: issue identification, solution mapping, solution formulation and solution implementation. > > "The Internet is an indispensable resource for its 3 billion users all around the world. Ensuring that it remains open and interoperable and that decision-making processes are carried out with the involvement of all stakeholders is critical to the future of the Internet and its continued success," said Vint Cerf, vice-chair of the Panel. > > "There is broad interest in how the Internet will be governed and by whom," said ICANN's President and CEO Fadi Chehadé. "The discussions at NETmundial reaffirmed the support and desire for a multistakeholder model of governance and served as an inspiration for the Panel's recommendations." > > To achieve a collaborative, decentralized IG ecosystem, the Panel recommends next steps mapped against a three-year timeline that include coalescing and supporting broad multistakeholder alliances; developing new and strengthening existing IG mechanisms; and progressing collaborative decision-making. Recognizing the evolving IG dialogue and process, the Panel also identified specific additional questions that will need answers moving forward, and encouraged the global community to weigh in with its responses. > > The Panel was convened by ICANN and the World Economic Forum (WEF), with assistance from The Annenberg Retreat at Sunnylands. It met during a series of virtual and in-person meetings between November 2013 to May 2014 in London, Rancho Mirage, Calif., and Dubai. The Panel encourages the global community to refine its roadmap through ongoing discussions and forums, including the upcoming Global Commission on Internet Governance. > > Click here to learn more about the London meeting » > > Click here to learn more about the Sunnylands meeting » > > "In the spirit of WEF's global citizenship, it has been important to partner with the Panel on the timely and momentous issue of Internet governance," said Alan Marcus, senior director and head of Information Technology and Telecommunications Industries at the WEF. "The Internet will continue to grow exponentially in the years to come, and it will be necessary to chart a path forward that allows for equitable opportunity for current and future users." > > Members of The Panel on Global Internet Cooperation and Governance Mechanisms include: > > Mohamed Al Ghanim, Founder and Director General of the UAE Telecommunications Regulatory Authority; former Vice-Chair, UAE Information and Communications Technology Fund; Chairman of WCIT-12 > Virgilio Fernandes Almeida, Member of the Brazilian Academy of Sciences; Chair of Internet Steering Committee; National Secretary for Information Technology Policies > Dorothy Attwood, Senior Vice President of Global Public Policy, Walt Disney Company > Mitchell Baker, Chair, Mozilla Foundation; Chair and former CEO, Mozilla Corporation > Kathy Brown, President and CEO, Internet Society > Francesco Caio, CEO of Avio; former CEO, Cable and Wireless and Vodafone Italia; Founder of Netscalibur; broadband advisor in UK and Italy; Government Commissioner for Digital Agenda > Vint Cerf, Vice President and Chief Internet Evangelist for Google; former Chairman, ICANN; Co-Founder of the Internet Society > Fadi Chehadé, CEO and President of ICANN; Founder of Rosetta Net; technology executive > Nitin Desai, Indian economist and diplomat; former UN Undersecretary General; convener of Working Group on Internet Governance (WGIG) > Anriette Esterhuysen, Executive Director, Association for Progressive Communications > Byron Holland, President and CEO of the Canadian Internet Registration Authority > Toomas Hendrik Ilves, President of Estonia; former diplomat and journalist; former Minister of Foreign Affairs; former Member of the European Parliament > Ivo Ivanovski, Minister of Information Society and Administration, Macedonia; Commissioner to the UN Broadband Commission for Digital Development > Thorbjørn Jagland, Secretary General of the Council of Europe; former Prime Minister and Foreign Minister of Norway > Omobola Johnson, Minister of Communication Technology of Nigeria > Olaf Kolkman, Director of NLnet Labs; "Evangineer" of the Open Internet; former Chair of the Internet Architecture Board > Frank La Rue, labor and human rights lawyer; UN Special Rapporteur on the Promotion and Protection of the Right to Freedom of Opinion and Expression; Founder, Center for Legal Action for Human Rights (CALDH) > Robert M. McDowell, former U.S. Federal Communications Commissioner; Visiting Fellow, Hudson Institute's Center for Economics of the Internet > Andile Ngcaba, Chairman and Founder, Convergence Partners; Executive Chairman, Dimension Data Middle East and Africa; former South African Government Director General of Communications > Liu Qingfeng, CEO and President of iFLYTEK; Director of National Speech & Language Engineering Laboratory of China; Member of Interactive Technology Standards working group > Christoph Steck, Director Public Policy & Internet, Telefonica > Jimmy Wales, Founder and Promoter of Wikipedia; Member of the Board of Trustees of Wikimedia Foundation > Won-Pyo Hong, President, Media Solution Center, Samsung Electronics > > For more information on the Panel, please contact: Holli Holsan at Holli.Holsan(a)edelman.com or visit: www.internetgovernancepanel.org.

1 0

Fwd: [icann-board] Fwd: FYI, blog published
by Rinalia Abdul Rahim May 20, 2014

May 20, 2014

ALAC, >From Steve Crocker: http://blog.icann.org/2014/05/feedback-encouraged-on-icanns-draft-five-year… Best regards, Rinalia

2 1

Re: [ALAC] ICANN Compliance serves breach notice on BizCN registrar
by Garth Bruen May 19, 2014

May 19, 2014

I want to thank everyone for helping move this along, especially Alan who dug into the details. This took THREE YEARS to get to. Yes, the first complaint about this issue with BizCn was June 2011. The complaints were repeatedly dismissed by Compliance. While it may seem a victory for them to finally get a breach notice, it was a shameful process getting here. While ICANN may argue that things have changed, nothing has changed in terms of facts, only the attitude of the organization has changed. We can cheer this, but there are bigger problems underneath. The way I see it there are two big questions: 1. Why, from June 2011 to March 2013 did they refuse to investigate the facts of the case, even going so far as to say the data had been verified? 2. Will the Ombudsman re-open the investigation into the matter? The failure of this office to conduct a factual investigation points to a grave loss of accountability within ICANN. Sincerely, Garth -----Original Message----- From: alac-bounces(a)atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Alan Greenberg Sent: Thursday, May 8, 2014 11:44 PM To: Dev Anand Teelucksingh; ALAC Working List Subject: Re: [ALAC] ICANN Compliance serves breach notice on BizCN registrar Note that the non-compliant issues 1, 2 and 3 are all associated with an audit to ensure that registries comply with the Expired Registration Recovery Policy, the result of the PEDNR PDP that ALAC initiated and saw through. Compliance has been citing a number of registrars in recent days over these issues. It is worthy of note that for some of the Whois accuracy issues that we raised, they fixed these by moving the "proxy service" from non-existent French addresses and non-existent e-mail addresses to a new address is Moscow (probably valid based on Google) and a new e-mail address that at least has a valif domain name. All "interesting" to say the least. One thing I noted that we may want to act on. The e-mail domain address associated with this Russian proxy service is registered via the same proxy service. Holly: Should this be allowed under the new P/P rules being developed. Or even registering their contact address via ANOTHER P/P service. Shoe we make an additional statement to the WG? Alan At 08/05/2014 10:06 PM, Dev Anand Teelucksingh wrote: >Dear All, > >BizCN registrar, the focus of many of the compliance related issues >raised by the ALAC in the past few months has been served with a breach notice. >See >http://www.icann.org/en/news/correspondence/serad-to-guanghui-08may14-e >n.pdf > >Many of the concerns raised by the ALAC regarding this particular >registrar appear to have been included in the breach notice, including >the systemic Whois inaccuracy complaints. > >Kudos to all those involved that worked hard on this to get some results. > >Kind Regards, > >Dev Anand Teelucksingh >_______________________________________________ >ALAC mailing list >ALAC(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac > >At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: >https://community.icann.org/display/atlarge/At-Large+Advisory+Committee >+(ALAC) _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA C)

3 3

NGPC rejects Amazon applications
by Alan Greenberg May 18, 2014

May 18, 2014

https://new.icann.org/resources/board-material/resolutions-new-gtld-2014-05… Alan

2 1

Resolutions from the ICANN Board's new gTLD Program Committee meeting on 14 May 2014
by Rinalia Abdul Rahim May 18, 2014

May 18, 2014

Dear ALAC, The items on .amazon and review mechanism for inconsistent expert determination on string confusion objection may be of interest. Where there is no resolution taken is due to the need for more discussion. Attached doc provides a better overview of the NGPC decisions from its meeting on Wednesday May 14th. Best regards, Rinalia > > > http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-14may14… > > > > 1.Consent Agenda: > > a. Approval of Minutes > > Resolved (2014.05.14.NG01), the ICANN Board New gTLD Program Committee (NGPC) approves the minutes of the 22 March, 26 March and 3-4 April 2014 NGPC meetings. > > > > 2. Main Agenda: > > a. Remaining Items from Beijing, Durban, Buenos Aires, and Singapore GAC Advice > > Whereas, the GAC met during the ICANN 46 meeting in Beijing and issued a Communiqué on 11 April 2013 ("Beijing Communiqué"). > > Whereas, the GAC met during the ICANN 47 meeting in Durban and issued a Communiqué on 18 July 2013 ("Durban Communiqué"). > > Whereas, the GAC met during the ICANN 48 meeting in Buenos Aires and issued a Communiqué on 20 November 2013 ("Buenos Aires Communiqué"). > > Whereas, the GAC met during the ICANN 49 meeting in Singapore and issued a Communiqué on 27 March 2014, which was amended on 16 April 2014 ("Singapore Communiqué"). > > Whereas, the NGPC adopted scorecards to respond to certain items of the GAC's advice, which were adopted on 4 June 2013, 10 September 2013, 28 September 2013 and 5 February 2014. > > Whereas, the NGPC has developed another iteration of the scorecard to respond to certain remaining items of GAC advice in the Beijing Communiqué, the Durban Communiqué, the Buenos Aires Communiqué, and new advice in the Singapore Communiqué. > > Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. > > Resolved (2014.05.14.NG02), the NGPC adopts the scorecard titled "GAC Advice (Beijing, Durban, Buenos Aires and Singapore): Actions and Updates" (14 May 2014), attached as Annex 1 [ http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1…] to this Resolution, in response to open items of Beijing, Durban, Buenos Aires and Singapore GAC advice as presented in the scorecard. > > > b. GAC Advice on .AMAZON (and related IDNs) > > Whereas, the GAC met during the ICANN 47 meeting in Durban and issued a Communiqué on 18 July 2013 ("Durban Communiqué"). > > Whereas, the GAC advised the ICANN Board in its Durban Communiqué that the GAC reached "consensus on GAC Objection Advice according to Module 3.1 part I of the Applicant Guidebook on the following applications: [t]he application for .amazon (application number 1-1315-58086) and related IDNs in Japanese (application number 1-1318-83995) and Chinese (application number 1-1318-5591)." This item of GAC advice is identified in the GAC Register of Advice as 2013-07-18-Obj-Amazon. > > Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. > > Resolved (2014.05.14.NG03), the NGPC accepts the GAC advice identified in the GAC Register of Advice as 2013-07-18-Obj-Amazon, and directs the President and CEO, or his designee, that the applications for .AMAZON (application number 1-1315-58086) and related IDNs in Japanese (application number 1-1318-83995) and Chinese (application number 1-1318-5581) filed by Amazon EU S.à r.l. should not proceed. By adopting the GAC advice, the NGPC notes that the decision is without prejudice to the continuing efforts by Amazon EU S.à r.l. and members of the GAC to pursue dialogue on the relevant issues. > > > > c. Perceived Inconsistent String Confusion Objection Expert Determinations – Review Mechanism > > No resolution taken. > > > d. New gTLD Auction Rules > > No resolution taken. > > > e. New gTLD Program Financial Update > > Item not considered. > > > Published on 16 May 2014 >

1 0

Fwd: On the ALS application of ISOC Venezuela - ISOC LAC chapters
by Olivier MJ Crepin-Leblond May 16, 2014

May 16, 2014

Dear all, Please be so kind to find the message from Alejandro Pisanty below. You may use your favourite translate tool re: Spanish -> English translation. Kindest regards, Olivier -------- Original Message -------- Subject: On the ALS application of ISOC Venezuela - ISOC LAC chapters Date: Mon, 12 May 2014 12:21:37 -0500 From: Alejandro Pisanty <apisanty(a)gmail.com> To: Olivier Crépin-Leblond <ocl(a)gih.com>, Fatima Cambronero <fatimacambronero(a)gmail.com>, Dev Anand Teelucksingh <admin(a)ttcsweb.org>, León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx>, Alberto Soto <asoto(a)ibero-americano.org>, Humberto Carrasco <hcarrascob(a)gmail.com> Olivier, Fatima, Dev, Leon, Alberto, Humberto, the following communication has been agreed upon by 7 ISOC Chapters of Latin America and the Caribbean, all of them ALS's and LACRALO members, in support of the ISOC Venezuela application. We stand ready to discuss further information and criteria if needed: "Posicion sobre la acreditación de ISOC Venezuela como ALS en ALAC >> >> De nuestra mayor consideración: >> >> Los capítulos de ISOC abajo firmantes expresan su respaldo a la >> postulación como miembro ALS del Capitulo de ISOC Venezuela al ALAC, >> basados en los criterios establecidos por el ALAC, que son: >> >> "• Comprometerse a respaldar la participación informada en la ICANN >> de los usuarios individuales. Esto se llevará a cabo por medio de >> la distribución de información a los miembros >> individuales/constituyentes sobre las actividades y hechos relevantes >> de la ICANN, ofreciendo mecanismos vía Internet para que los miembros >> individuales/constituyentes puedan intercambiar ideas sobre una o más >> de estas actividades o hechos, y participen en el desarrollo, la >> discusión y las decisiones de políticas relevantes a la ICANN. >> • Organizarse de tal modo que la participación de usuarios >> individuales, quienes son ciudadanos o residentes de países de la >> región geográfica en la cual tenga su sede esa ALS, será predominante >> en las operaciones de la ALS. La ALS puede permitir la >> participación adicional de otros que compartan los intereses de los >> usuarios individuales de esa región. >> • Ser autosuficiente (no depender de la ICANN para financiamiento). >> • Anunciar en Internet (en el sitio Web del Comité At-Large - ALAC o >> en algún otro sitio) información actual y accesible al público >> acerca de las metas, la estructura, la descripción de los grupos >> constituyentes/miembros, mecanismos de trabajo, liderazgo y contactos >> de la ALS. >> • Ayudar a la RALO en la ejecución de sus funciones.” [1] >> >> Al momento, más de 40 capítulos de ISOC alrededor del mundo son ALS >> certificadas, con diferente tipología de membresia; Siendo que ISOC >> Argentina, ISOC Mexico, ISOC Peru, ISOC Ecuador, ISOC Trinidad y >> Tobago e ISOC Costa Rica, ya son miembros del ALAC, y por ende del >> LACRALO, en el mismo principio anterior debería ser aceptada la >> solicitud de ISOC Venezuela por compartir estructura, principios, >> fines y objetivos similares a los otros capítulos que actualmente >> forman parte de ALAC. >> >> Es importante señalar que los criterios de acreditación para la >> conformación de un capítulo de ISOC son similares a los del ALAC, por >> lo cual un capitulo ser un capitulo ISOC garantiza el cumplimiento de >> dichos criterios [2]. >> >> De igual modo sobre la relevancia de ISOC Venezuela, y de su >> membrecia, diversos miembros de ISOC VE han contribuido a >> la información útil para todos con mediciones de tráfico de las que >> no sería posible disponer de otra manera, conjuntando así >> competencia tecnológica y visión de servicio a los usuarios >> >> Siendo los criterios expuestos los que determinan la admisión de una >> organización como ALS, el Capitulo ISOC Venezuela cumple con >> los mismos, y en irrestricto respeto del principio de igualdad y no >> discriminación su aplicación debe ser aceptada. >> >> Atentamente, >> >> ISOC Argentina >> ISOC Costa Rica >> ISOC Ecuador >> ISOC Mexico >> ISOC Paraguay >> ISOC Peru >> ISOC Trinidad y Tobago" >> >> Yours, Alejandro Pisanty -- - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico +52-1-5541444475 FROM ABROAD +525541444475 DESDE MÉXICO SMS +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---->> Unete a ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . .

1 0

Schedule for Thursday during the London ICANN meeting
by Alan Greenberg May 14, 2014

May 14, 2014

Don't think I saw this circulated. If it was, I apologize for the duplicate. Alan From: http://blog.icann.org/2014/05/thursday-in-london/ Thursday In London by Steve Crocker on May 12, 2014 When we last met in Singapore, the NTIA announcement on transitioning stewardship of the IANA functions was still very fresh and we adjusted our meeting schedules to begin constructive discussions in response. The processes governing these discussions are now in motion, and we want to support them with open dialogue with as many stakeholders as possible. For ICANN 50 in London, we will carve out a substantial amount of quality time to continue meaningful dialogue on both the transition of the IANA stewardship process and the ICANN Accountability process at the stages those processes will be in late June. We also want to support these processes as much as possible by maximizing remote participation from around the world. To the latter, we are exploring the possibility of setting up a series of remote hubs similar to what was used last month during NETmundial and to great acclaim. As for the schedule, we are reshuffling the planned Thursday, June 26 agenda for this meeting only. Here is the expected schedule: â¾8:00a 10a: Complete all group sessions â¾10a 12p: ICANN Accountability Forum â¾12p 1p: Lunch â¾1p 3:30p: IANA Stewardship Transition Forum â¾4p 6p: Public Forum â¾6p 7p: Board Meeting â¾7p : Cocktails I hope that two hours for the Public Forum during this particular meeting will be adequate as discussions on the transition and on accountability would likely, under normal circumstances, take up a good chunk of that time. Shortening the Public Forum was not an easy decision. I, and Iâm sure I speak for the other Board members, always look forward to the abundance of input the community shares and the passion by which you can do so at the end of a long week. However, some sort of change was necessary this time, and we consulted with the leaders of the Advisory Committees and Supporting Organizations to choose this approach. The feedback was remarkably supportive. My hope is that this change in the meeting schedule, and again for this meeting only, is made with enough notice so that we all can adjust accordingly. The meetings team will do its best to identify alternative slots for any Thursday session disrupted by this change in schedule. Thanks for your attention to this and I look forward to seeing you in London.

1 0