November 2015 - Npoc-discuss

Request for Proposal: Study About the Domain Name System (DNS) Industry and Business in Africa
by Rudi Vansnick Nov. 30, 2015

Nov. 30, 2015

The message below is sent to you for your information. If you have any questions, please contact us. News Alert https://www.icann.org/news/announcement-2015-11-30-en <https://www.icann.org/news/announcement-2015-11-30-en> Request for Proposal: Study About the Domain Name System (DNS) Industry and Business in Africa 30 November 2015 The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking a provider to conduct a study on the domain name industry in Africa. The goal of this study is to identify and define the strengths and weaknesses in the industry ecosystem within the region and develop recommendations on how to advance the industry and bring it closer to the opportunities available. The ICANN's Africa Strategic Plan, reviewed in 2014, defined four key areas of interest as strategic focus for the region. Two of those, namely Capacity Building and Outreach and Economic Concerns consider the different areas and opportunities available to further develop the domain name industry in Africa. The study at a minimum will: Investigate the current state of the Internet and the domain name industry in the region Define best practices that have made an impact in domain name market growth Look at the broader ecosystem of the Internet infrastructure and online services and describe the impact of such elements on the overall evolution of the domain name industry Describe the business potential in the domain name industry in Africa, and Provide suggestions on how to develop the industry and what business models can be adopted in the entire industry chain. The study will include data, analysis, and recommendations. The final report of the study is to be delivered no later than 30th April 2016. An intermediary report should be provided in March 2015 For additional information and instructions for submitting responses please click here <https://community.icann.org/display/gseafrcawkspc/RFP+documents>. Proposals should be submitted to Yaovi.atohoun(a)icann.org <mailto:Yaovi.atohoun@icann.org> by 23:59 UTC on 05 December 2015. Rudi Vansnick Chair Non-for-Profit Operational Concerns Constituency (NPOC) www.npoc.org <http://www.npoc.org/> rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32

1 0

Fwd: [liaison6c] FYI Public comments open for second-level IDN reference tables
by Olévié Kouami Nov. 30, 2015

Nov. 30, 2015

The message below is sent to you for your information. If you have any questions, please contact us. ---------- Forwarded message ---------- From: Glen de Saint Géry <Glen(a)icann.org> Date: 2015-11-23 23:13 GMT+00:00 Subject: [liaison6c] FYI Public comments open for second-level IDN reference tables To: liaison6c <liaison6c(a)gnso.icann.org> Dear Council members, Please be so kind as to circulate the following information to your groups and communities. As there is a clear need to ensure consistency of the end user experience, it is important to develop either common language-based or script-based Internationalized Domain Name (IDN) tables. Based in large part on experience during the New gTLD Program implementation, ICANN is developing reference IDN tables in machine readable format, called Label Generation Rulesets (LGRs) for the second level, for use in Pre-Delegation Testing (PDT) and the Registry Service Evaluation Process (RSEP). The first step in this process is the release of the proposed Guidelines for Developing of Reference LGRs for the Second Level ( https://www.icann.org/en/system/files/files/lgr-guidelines-second-level-30o…) A public comment forum on these Guidelines is now open, closing on 15 December: https://www.icann.org/public-comments/comments-lgr-second-level-2015-11-05-… . ICANN staff involved in developing, reviewing and further updating these Guidelines based on community feedback will greatly welcome input from the GNSO community, especially affected parties and users. If you have any questions, please feel free to contact Sarmad Hussain directly ( sarmad.hussain(a)icann.org) or I will also be happy to forward the questions on your or your group’s behalf. Thank you. Cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names & Numbers (ICANN) Telephone: +1 603 574 4889 Email: mary.wong(a)icann.org -- *Olévié Ayaovi Agbenyo KOUAMI* *Directeur-Adjoint de O and K IT SOLUTIONS sarl (Editeur de logiciels de gestion SIGE (http!//www.oandkit.com <http://www.oandkit.com>)* *Président/CEO de l'INTIC4DEV (Institut des TIC pour le développement)* *SG de ESTETIC - Association Togolaise des professionnels des TIC (http://www.estetic.tg <http://www.estetic.tg>)* *ICANN-GNSO-NCSG-NPOC Communications Committee Chair (http://www.npoc.org/ <http://www.npoc.org/>)Membre du FOSSFA (www.fossfa.net <http://www.fossfa.net>) et Membre de Internet Society (www.isoc.org <http://www.isoc.org>) * *Skype : olevie1 FB : @olivier.kouami.3 Twitter : #oleviek Lomé – Togo* ICANN - Fellow & Alumni *Membre fondateur du RIK-Togo (Réseau Interprofessionnel du Karité au Togo)*

1 0

Actions coming week in GNSO :
by Rudi Vansnick Nov. 29, 2015

Nov. 29, 2015

The message below is sent to you for your information. If you have any questions, please contact us. Actions coming week in GNSO : Tuesday 01 December 2015 12:00 UTC: CCWG on Enhancing ICANN Accountability https://community.icann.org/x/ogDxAg <https://community.icann.org/x/ogDxAg> 14:30 UTC: GNSO PPSAI WG https://community.icann.org/x/9 iCfAg <https://community.icann.org/x/9%20iCfAg> Rudi Vansnick Chair Non-for-Profit Operational Concerns Constituency (NPOC) www.npoc.org <http://www.npoc.org/> rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32

2 1

ICANN Policy update
by Rudi Vansnick Nov. 28, 2015

Nov. 28, 2015

The message below is sent to you for your information. If you have any questions, please contact us. ASO <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#ANSO> | ccNSO <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#ccNSO> | GNSO <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#GNSO> | ALAC <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#ALAC> | GAC <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#GAC> | RSSAC <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#RSSAC> | SSAC <applewebdata://705BBF22-B065-4D47-89D2-40A8CF66681E#SSAC> Community Recognizes Leaders as Work Continues <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> Community-driven work is at the core of ICANN's mission. Our community members spend countless hours in working groups, on leadership teams, and in a variety of other activities across our Supporting Organizations and Advisory Committees. This commitment of time, energy, and brainpower advances important policy development and advisory work. As one simple indicator of this level of activity commitment, community members participated in a total of 185 working sessions at ICANN54 alone. At ICANN54, 43 community leaders from the At-Large, RSSAC, ASO, ccNSO, and GNSO communities and the Nominating Committee were recognized for their contributions to ICANN's work. The full list and a link to the resolution by the Board of Directors are published in this month's issue. Of course, we cannot recognize community leaders without acknowledging the ongoing, extraordinary efforts of the IANA Stewardship Transition process and the Enhancing ICANN Accountability effort. Collectively, more than 300 community leaders have contributed substantially to proposals and working groups in the past 20 months. My colleagues and I are grateful for our community and the opportunities they give us to help support their work. ICANN's growth and evolution as a multistakeholder organization depends on the sustained engagement of you all. Best regards, David Olive Senior Vice President, Policy Development Support General Manager, Istanbul Hub Office Policy Across ICANN Issues Currently Open for Public Comment <http://icann.us3.list-manage1.com/track/click?u=818d573897ed5ea25ee71ebc1&i…> ICANN Recognizes 43 Community Leaders <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> Supporting Organizations (SOs) ASO Nurani Nimpuno Elected to ASO Address Council <http://icann.us3.list-manage1.com/track/click?u=818d573897ed5ea25ee71ebc1&i…> Open, Inclusive RIPE Policy Development Process Works for Governments and Non-ISP Enterprises <http://icann.us3.list-manage1.com/track/click?u=818d573897ed5ea25ee71ebc1&i…> Regional Internet Registries Number Resource Policy Discussions <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> GNSO GNSO Council Adopts Data and Metrics for Policymaking Working Group Recommendations <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> ICANN Learn Course, "Introduction to the GNSO," Launches <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> GNSO Organizes 61 Sessions during ICANN54 <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> Advisory Committees (ACs) ALAC ALAC/At-Large Achievements at ICANN54 <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> RALO Activities at ICANN54 <http://icann.us3.list-manage1.com/track/click?u=818d573897ed5ea25ee71ebc1&i…> GAC GAC Public Safety Working Group Gains Traction <http://icann.us3.list-manage1.com/track/click?u=818d573897ed5ea25ee71ebc1&i…> GAC Concludes Meeting at ICANN54 <http://icann.us3.list-manage.com/track/click?u=818d573897ed5ea25ee71ebc1&id…> SSAC SSAC Publishes Advisory on Registrant Protection: Best Practices for Preserving Security and Stability in the Credential Management Lifestyle <http://icann.us3.list-manage1.com/track/click?u=818d573897ed5ea25ee71ebc1&i…> Rudi Vansnick Chair Non-for-Profit Operational Concerns Constituency (NPOC) www.npoc.org <http://www.npoc.org/> rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32

1 0

Fwd: Civil society and non-commercial engagement in ICANN - new draft approach
by Maryam Bakoshi Nov. 13, 2015

Nov. 13, 2015

Dear All, Please find below. Many thanks, -- Maryam Bakoshi Secretariat Support - NCSG, NCUC, NPOC Internet Corporation for Assigned Names and Numbers (ICANN) Email: maryam.bakoshi(a)icann.org<mailto:maryam.bakoshi@icann.org> Mobile: +44 7737 698036 Skype: maryam.bakoshi.icann Begin forwarded message: From: Adam Peake <adam.peake(a)icann.org<mailto:adam.peake@icann.org>> Date: November 12, 2015 at 4:08:23 PM GMT-3 To: Tapani Tarvainen <tapani.tarvainen(a)effi.org<mailto:tapani.tarvainen@effi.org>>, Klaus Stoll <kdrstoll(a)GMAIL.COM<mailto:kdrstoll@gmail.com>>, William Drake <william.drake(a)uzh.ch<mailto:william.drake@uzh.ch>>, Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>> Cc: Rafik Dammak <rafik.dammak(a)gmail.com<mailto:rafik.dammak@gmail.com>>, Jean-Jacques Sahel <jean-jacques.sahel(a)icann.org<mailto:jean-jacques.sahel@icann.org>>, Heidi Ullrich <Heidi.Ullrich(a)icann.org<mailto:Heidi.Ullrich@icann.org>> Subject: Civil society and non-commercial engagement in ICANN - new draft approach Dear Tapani, Alan, Bill, Klaus: The civil society engagement strategy has been updated to reflect comments received up to and during the ICANN Dublin meeting. New version of the draft approach is online at https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlB…<https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlB…> I would be grateful if you would forward the message below and attachments to the NSCG, NPOC, NCUC and relevant At Large lists. The covering note below is long, but I hope useful. Many thanks, Adam Adam Peake Senior Manager, Civil Society Engagement ICANN Hi Everyone, Thank you for the comments on the civil society engagement strategy. We have just published as revised google doc https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlB…<https://docs.google.com/document/d/1xC5pxWr4uzkU_Uoi3guGFEFrP9LHYk_KV11mRlB…> This doc reflects comments on the first version, comments made during the webinar, meetings with civil society organizations and individuals over the past few months and meetings at ICANN Dublin. We also considered how ICANN's business engagement team and regional engagement teams have developed contacts and content over the past few years. In the new document you will see some text in square brackets. We have used this when there is a word or phrase that has not received clear agreement, comment or support. We would welcome thoughts from the community on whether to include or remove in each case. If no comments are received in support we will remove the text in bracket by default. 3 files attached: the original document made available for comment as a google doc in July (clean original), a document tracking changes between the original and the version online now, and a copy of the google doc with comments (copy made at the end of the Dublin ICANN meeting.) The following provide an explanation of how changes were made. Notes: There was a suggestion to include "global" public interest, as the term isn't defined in ICANN, reverted to the more commonly used public interest, and also retaining global community as common ICANN usage. Editorial changes made to emphasize that ICANN will strengthen diversity. This emphasis is carried forward in a number of places in the document. A new second paragraph added to explain the goal of strategy, and reflecting various comments received. Addition of reference to representatives of noncommercial individual Internet users and academia with interest in Internet-related policy added. Intent is to give clarity to the definition of civil society within ICANN. "Representatives of" is in square brackets, in this context it refers to At Large Structures (ALS), suggested as a more precise way to refer to individual Internet users, and it should be those ALS that self-select as being civil society. Include or not? * We are be interested in comments on whether the strategy should also include individuals or remain focuses on organizations? The new sentence added to clarify that not-for-profit organizations serving the interests of commercial organizations, for example trade associations, would not be eligible for consideration as civil society under this definition. There was a comment about specific instances and organizations. We suggest that the NCSG's and At Large's respective membership processes judge whether or not an individual organization is/is not appropriately civil society. National situations lead to different organizational arrangements, charitable and not-for-profit status, etc. Within ICANN responsibility for academia is divided between two ICANN staff groups: The Development and Public Responsibility Department (DPRD) is responsible primarily for education activities, organizing courses and such like, the global stakeholder group is responsible for engagement. Editorial changes to remove the use of "our" and "we", etc. in the document. In the section long term goals, the bullet "To increase awareness…" moved to the first position and "DNS and Internet governance ecosystem" added. Clarification on mission relevance included, plus some minor editorial changes. We expect to develop graphics showing how civil society is organized in ICANN and how it contributes to the policy processes. Section1, structured approach: In addition to the broad civil society engagement plan, support will also be available from the staff team for NCSG and relevant At Large Structures to sustain their communications and outreach plans. Staff is aware of comments that better coordination is required between At-Large and the Global Stakeholder Engagement teams in their outreach efforts and participation in local events. Section 2, tailored content and communications: Emphasis added recognizing the importance of activities that focus on awareness raising for civil society organizations not yet engaged with ICANN. There should be a balance between information that serves existing ICANN civil society organizations and those that are outside the ICANN circle. Need to develop content that clearly distinguishes between the missions of the ICANN civil society groups, this should be finalized after ICANN55. The examples of content and communications listed were suggested mainly during discussions with civil society organizations, and also from members of the GSE team based on their experience of engagement with all stakeholders and regionally. Suggestions for other activities/communications types welcome. Please make suggestions about prioritization of these activities. Section 3 engagement activities: Acknowledging the comments received about the importance of ICANN Fellows and NextGen program participants, who should be encouraged to join and contribute to their relevant ICANN constituencies. In-reach will also be a focus of engagement strategy, this should include training and further support for ICANN volunteers. Propose that when ICANN staff participate in national/regional IGFs they present a consistent message civil society involvement. This should describe how civil society works in ICANN, civil society's focus areas, etc, and nor try to represent civil society opinions. Internal organization: A comment about coordination between the Asia-Pacific and Middle East regions noted. It was suggested that a small group of people from NCSG (NCUC/NPOC), At Large, and Fellows/NextGen if they wish, might form a small working party to help develop the strategy approach, working through monthly calls. This contact group would bring information to the process from the broader community. Volunteers for this group would be welcomed. Annex: Roadmap of external activities for partnership in FY16 will be maintained as a separate document and online calendar. The calendar will be one of the functions available in a new constituency membership management system, expected to be available soon. Thanks to NARALO for a list of events, these will be included in the overall events listing. The community can share events relevant to civil society interested in ICANN and Internet policy, and suggestions for events where ICANN might organize a session or contribute in some way would be helpful. The new membership management system will provide better visibility of current members, and their areas of interest and expertise. There were comments about the need to translate some materials. Suggestions as to key documents for translation, and into which languages would be welcomed. Thank you, Adam

1 0

Taking Stock As We Enter the Final Stretch
by Rudi Vansnick Nov. 12, 2015

Nov. 12, 2015

The message below is sent to you for your information. If you have any questions, please contact us. Taking Stock As We Enter the Final Stretch <https://www.icann.org/news/blog/taking-stock-as-we-enter-the-final-stretch#> <https://www.icann.org/news/blog/taking-stock-as-we-enter-the-final-stretch#> <https://www.icann.org/news/blog/taking-stock-as-we-enter-the-final-stretch#> <https://www.icann.org/news/blog/taking-stock-as-we-enter-the-final-stretch#> <https://www.icann.org/news/blog/taking-stock-as-we-enter-the-final-stretch#> <https://www.icann.org/news/blog/taking-stock-as-we-enter-the-final-stretch#> As many could have predicted, the IANA Stewardship Transition and Enhancing ICANN Accountability topics remained center stage for the ICANN54 meeting in Dublin. As we reach the latest stretch post-Dublin, both the IANA Stewardship Transition Coordination Group (ICG) and Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) have hosted almost 70 hours of meetings, including working sessions and engagement sessions, plus presentations on behalf of their groups to numerous SOs and ACs through the week. As a result, both groups reached significant milestones. Notably, the ICG finalized their IANA Stewardship Transition Proposal, dependent upon the outstanding dependencies between the naming community's CWG-Stewardship and the CCWG-Accountability. You can find the IANA Stewardship Transition final report and full announcement of progress here <https://www.icann.org/news/announcement-2015-10-29-en>. In addition, the CCWG-Accountability progressed on many of their outstanding recommendations, notably deciding upon a Sole Designator as the enforcement mechanism for their new community powers. For a full update on their progress, please read their co-Chairs report here <https://www.icann.org/news/blog/cross-community-working-group-on-enhancing-…>. As we acknowledge this significant progress, I think it's important to note and just a glimpse of the participation and engagement details that got us to this point: Calls and Meetings: The working groups have held over 360 group calls and 9 face-to-face meetings. The time spent in these calls and meetings totals more than 600 hours, and that does not include the countless hours of drafting, prep/debrief calls, document finalization, public comment assessment and information sharing. Mailing List Exchanges: The working groups have exchanged more than 26,000 emails through more than 35 publicly archived community mailing lists dedicated to discussions of the transition and accountability processes. In the CCWG-Accountability alone, almost 9,000 emails have been exchanged since December 2014, whether amongst the full group or within one of 14 sub-groups debating methods for enhancing ICANN's accountability. As noted, the mailing lists are open to join, and publically archived, making them available to anyone to engage and follow the discussions, whether they chose to post to the list or not. Global Discussions: At ICANN itself, we have calculated that staff and Board members have participated in an estimated 860+ events around the world where the IANA Stewardship Transition or Enhancing ICANN Accountability processes were discussed, debated, organized or planned between March 2014 and October 2015 — That is the equivalent of almost 45 events per month. Of these events, roughly 520 were joined through global webinars or calls, while an additional 345 were attended in-person spanning over 87 countries around the world. Of course, all operational organizations, and partners, have held and participated in discussions – the global discussions are extensive. While we are able to track more closely the number of events that ICANN staff and Board have participated in, there have been countless people around the world who have participated in both the numbering resources processes, coordinated by the Regional Internet Registries (RIR) and the protocol parameters processes coordinated by the IETF, via email and meetings and phone calls. These global discussions reflect the breadth of participation in the process. To view all of these statistics in one place, view our latest infographic here <http://www.slideshare.net/icannpresentations/supporting-global-discussion-i…>. <https://www.icann.org/sites/default/files/assets/iana-stewardship-enhancing…> In addition to this remarkable community involvement in the processes, it is important to note that engagement in the transition has proven to be much broader than just the ICANN community. Whether exhibited by submitting public comments, attending webinars, or asking for and receiving updates, it is apparent that there is no shortage of effort dedicated to this historic undertaking. We encourage the community to stay involved in this process as we enter the final stretch. Theresa Rudi Vansnick Chair Non-for-Profit Operational Concerns Constituency (NPOC) www.npoc.org <http://www.npoc.org/> rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32

1 0

Proposed implementation of GNSO Policy Development Process Recommendations on Inter-Registrar Transfer Policy (IRTP) Part D
by Rudi Vansnick Nov. 12, 2015

Nov. 12, 2015

The message below is sent to you for your information. If you have any questions, please contact us. > News Alert > > https://www.icann.org/news/announcement-2015-11-10-en <https://www.icann.org/news/announcement-2015-11-10-en> > Proposed implementation of GNSO Policy Development Process Recommendations on Inter-Registrar Transfer Policy (IRTP) Part D > 10 November 2015 > > Forum Announcement: Public Comment Period opens on Date: 10 November 2015 > Categories/Tags: > Contracted Party Agreements > Policy Processes > Purpose (Brief): The public comment proceeding seeks to obtain community input on the proposed implementation of the Generic Names Supporting Organization (GNSO) Policy Development Process (PDP) recommendations on the Inter-Registrar Transfer Policy (IRTP) Part D. > Public Comment Box Link: https://www.icann.org/public-comments/irtp-d-implementation-2015-11-10-en <https://www.icann.org/public-comments/irtp-d-implementation-2015-11-10-en> Rudi Vansnick Chair Non-for-Profit Operational Concerns Constituency (NPOC) www.npoc.org <http://www.npoc.org/> rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32

1 0

Boletín ICANN LAC | Septiembre-Octubre 2015
by Eduardo Monge Gutierrez Nov. 11, 2015

Nov. 11, 2015

Dear NPOC members: For your information, see below a link to the latest ICANN LAC newsletter in Spanish: Boletín ICANN LAC | Septiembre-Octubre 2015 · "Buscando el trébol de cuatro hojas" Lito Ibarra, miembro de la Junta Directiva, ICANN · Novedades desde ICANN · Novedades desde la región o La ICANN y la OEA trabajarán en conjunto para mejorar la ciberseguridad a nivel regional o La Universidad Nacional de Asunción y la ICANN trabajan en forma conjunta para mejorar la infraestructura de Internet en Latinoamérica o ¿Dónde estuvimos? El mapa muestra los países visitados en los meses de septiembre y octubre. Le sigue una lista de los eventos. · Novedades del Plan Estratégico de LAC o Taller del comité directivo de la estrategia LAC Montevideo, Uruguay | 15-16 de septiembre 2015 o LAC-i Roadshow Sudamérica Asunción, Paraguay| 22-23 de septiembre 2015 o LAC-i Roadshow región andina Bogotá, Colombia | 28 de septiembre 2015 o 5to seminario en línea GAC-LAC para ICANN 54 o Observatorio del Sistema de Nombres de Dominio (DNS) o Espacio LAC en Dublín Lunes, 19 de octubre 2015 · Políticas y comentarios públicos o Cuestiones actualmente abiertas para la recepción de comentarios públicos o Primera etapa de la evaluación de los efectos del Programa de Nuevos gTLD en materia de competitividad o Documento para debate acerca de los ingresos obtenidos mediante subastas de nuevos gTLD o Informe inicial del Grupo Asesor de Implementación (IAG) y revisiones propuestas para el procedimiento vigente en la ICANN para dirimir conflictos entre el sistema de WHOIS y las leyes sobre privacidad o Remoción del servicio de WHOIS explorable del Acuerdo de Registro de .MEET o Nuevo curso en la plataforma ICANN Learn: Introducción a la GNSO o El Consejo de la GNSO adopta las recomendaciones del Grupo de Trabajo sobre uso de datos y métricas para la creación de políticas o El SSAC publica un documento se asesoramiento sobre protección a los registratarios · Comunidad: "Le damos la palabra" o Agustina Callegari - Argentina NextGen@ICANN Ambassador - ICANN54 · Nuevos GTLDS delegados · Destacados medios · Próximos eventos http://campaign.r20.constantcontact.com/render?ca=ca616fb8-8c80-4f6d-b428-2… Regards, Eduardo Monge Omar Dengo Foundation Costa Rica

1 0

Fwd: [Internet Policy] IGF 2015 / INVITATION - Workshop #13: Keeping your credentials secure online: A roundtable
by Olévié Kouami Nov. 10, 2015

Nov. 10, 2015

Bonjour à toutes et à tous, PVI, svp. -Olévié- ---------- Forwarded message ---------- From: Robert Guerra <rguerra(a)privaterra.org> Date: 2015-11-09 18:43 GMT+00:00 Subject: [Internet Policy] IGF 2015 / INVITATION - Workshop #13: Keeping your credentials secure online: A roundtable To: internetpolicy(a)elists.isoc.org I would like to to invite members of this list to the following roundtable that is being organized by ICANN’s Security and Stability Advisory Committee (SSAC) tomorrow at the IGF in Joao Pessoa Workshop #13: Keeping your credentials secure online: A roundtable Date/Time: Tuesday Nov 10 - 9:00 - 10:30 (J Pessoa is 2hrs ahead of EST) Location: Workshop Room 4 Following the live stream: - Live Webcast for Workshop Room 4 http://webcast.igf2015.br/index.php/workshop-room-4/ Webcasts are also available at http://youtube.com/igf The remote participation @ https://goo.gl/9sqJKK Description: Hackers realize the power of stealing credentials to crack open systems and gain access to critical information. And, because many organizations do an inadequate job of protecting their systems—despite patching, hardening, and firewalls—stealing credentials is an easy hacker target. Many compromises tie directly into issues relating to credential management. A cornerstone of all security strategies is an organization’s ability to control access to data and systems. Virtually all access controls rely on the use of credentials to validate the identities and permissions of users, applications, and devices. The roundtable will invite experts who have insights into the way in which the problems of credential management, which have so often proven intractable in practice despite reams of good advice from security professionals, have been addressed in real world environments and scenarios. These insights will come from civil society; the academic community; the financial sector; the technology sector; companies from the DNS and domain name management industry; operating system, browser, and games and apps developers; and social media companies. The roundtable will focus on the presentation of practical problems faced day to day, well publicized incidents, impacts on reputation and privacy, direct actions efforts taken, and measures to implement practical solutions that incorporate best practices for credential management. practical problems that exist to implement and improve a security and emerging best practices. Session format: The workshop will be organized as a facilitated dialogue. Led by the moderator, subject experts will debate and discuss the key questions and issues. Subject experts will give opening comments, after which the moderator will turn to those attending the session and invited experts in the audience to engage in facilitated dialogue. SSAC Advisory #074 on Registrant Protection: Best Practices for Preserving Security and Stability in the Credential Management Lifecycle was published last week as a background document for discussion during the session. It is attached FYI _______________________________________________ To manage your ISOC subscriptions or unsubscribe, please log into the ISOC Member Portal: https://portal.isoc.org/ Then choose Interests & Subscriptions from the My Account menu. -- *Olévié Ayaovi Agbenyo KOUAMI* *Directeur-Adjoint de O and K IT SOLUTIONS sarl (Editeur de logiciels de gestion SIGE (http://www.oandkit.com <http://www.oankit.com>)* *Président/CEO de l'INTIC4DEV (Institut des TIC pour le développement)* *SG de ESTETIC - Association Togolaise des professionnels des TIC (http://www.estetic.tg <http://www.estetic.tg>)* *ICANN-GNSO-NCSG-NPOC Communications Committee Chair (http://www.npoc.org/ <http://www.npoc.org/>)Membre du FOSSFA (www.fossfa.net <http://www.fossfa.net>) et Membre de Internet Society (www.isoc.org <http://www.isoc.org>) * *Skype : olevie1 FB : @olivier.kouami.3 Twitter : #oleviek Lomé – Togo* ICANN - Fellow & Alumni *Membre fondateur du RIK-Togo (Réseau Interprofessionnel du Karité au Togo)*

1 0

GNSO PDP T&T has been approved by the ICANN board
by Rudi Vansnick Nov. 8, 2015

Nov. 8, 2015

Dear NPOC members, During the period 2014-2015 all over about 16 months I have been co-chair of the GNSO PDP working group on Translation and Transliteration of Contact Information. The final report with 7 recommendations was approved and unanimous voted by the GNSO Council during the Buenos Aires meeting. So we will enter into the last phase of this PDP in a few weeks with the implementation of the proposed recommendations. I welcome any NPOC member during the process of putting together the WG team. GNSO Council Recommendations Translation and Transliteration of Contact Information Whereas, on 13 June 2013, the GNSO Council launched a Policy Development Process (PDP) on the Translation and Transliteration, addressing two charter questions, set forth at http://gnso.icann.org/en/issues/gtlds/transliteration-contact-charter-20nov… [PDF, 185 KB]. Whereas, the PDP followed the prescribed PDP steps as stated in the Bylaws, resulting in a Final Report delivered on 12 June 2015. Whereas, the Translation and Transliteration of Contact Information Working Group (WG) reached consensus on its first recommendation and full consensus on its remaining six recommendations.1 Whereas, the GNSO Council reviewed, and discussed the recommendations of the Translation and Transliteration of Contact Information WG, and adopted the Recommendations on 24 June 2015 by a unanimous vote (see: http://gnso.icann.org/en/council/resolutions#20150624-3) Whereas, the GNSO Council vote met and exceeded the required voting threshold (i.e. supermajority) to impose new obligations on ICANN contracted parties; and Whereas, after the GNSO Council vote, a public comment period was held on the approved recommendations, and the comments have been summarized and considered (https://www.icann.org/public-comments/transliteration-contact-recommendatio…) Resolved (2015.09.28.02), the Board adopts the GNSO Council Policy Recommendations concerning the translation and transliteration of contact information as presented in the Final Report. Resolved (2015.09.28.03), the CEO, or his authorized designee(s), is directed to develop and complete an implementation plan for these Recommendations and continue communication and cooperation with the GNSO Implementation Review Team and community on the implementation work. Rationale for Resolutions 2015.09.28.02 – 2015.09.28.03 Why the Board is addressing the issue now? The continued internationalization of the domain name systems means that an ever-larger share of Internet users do not use (or are not even familiar) with US ASCII, the technical term for the Latin-based script used in English and many other western European languages. Accuracy and consistency of contact information data are crucial to make it a useful source to those seeking information regarding domain name registrants. This PDP WG has considered the important issue of whether translated and/or transliterated data or data submitted in the script best known to the registrant is more likely to deliver these requirements, bearing also in mind the amount of requests for such data and the costs associated with blanket translation or transliteration. The Translation and Transliteration PDP Final Report received consensus support on its first recommendation and full consensus on the remaining six others. It also received unanimous support from the GNSO Council. Following the closing of the public comment period, the next step as outlined in Annex A of the ICANN Bylaws is consideration by the ICANN Board of the recommendations. What is the proposal being considered? The following policy recommendations are being adopted: Recommendation #1 The Working Group recommends that it is not desirable to make transformation of contact information mandatory. Any parties requiring transformation are free to do so on an ad hoc basis outside Whois or any replacement system, such as the Registration Data Access Protocol (RDAP). If not undertaken voluntarily by registrar/registry (see Recommendation #5), the burden of transformation lies with the requesting party. Recommendation #2 Whilst noting that a Whois replacement system should be capable of receiving input in the form of non-ASCII script contact information, the Working Group recommends its data fields be stored and displayed in a way that allows for easy identification of what the different data entries represent and what language(s)/script(s) have been used by the registered name holder. Recommendation #3 The Working Group recommends that the language(s) and script(s) supported for registrants to submit their contact information data may be chosen in accordance with gTLD- provider business models. Recommendation #4 The Working Group recommends that, regardless of the language(s)/script(s) used, it is assured that the data fields are consistent to standards in the Registrar Accreditation Agreement (RAA), relevant Consensus Policy, Additional Whois Information Policy (AWIP) and any other applicable polices. Entered contact information data are validated, in accordance with the aforementioned Policies and Agreements and the language/script used must be easily identifiable. Recommendation #5 The Working Group recommends that if the transformation of contact information is performed, and if the Whois replacement system is capable of displaying more than one data set per registered name holder entry, these data should be presented as additional fields (in addition to the authoritative local script fields provided by the registrant) and that these fields be marked as transformed and their source(s) indicated. Recommendation #6 The Working Group recommends that any Whois replacement system, for example RDAP, remains flexible so that contact information in new scripts/languages can be added and expand its linguistic/script capacity for receiving, storing and displaying contact information data. Recommendation #7 The Working Group recommends that these recommendations are coordinated with other Whois modifications where necessary and are implemented and/or applied as soon as a Whois replacement system that can receive, store and display non-ASCII characters, becomes operational. Finding in relation to second Charter question Based on recommendations #1-#7, the question of who should decide who should bear the burden of translating or transliterating contact information to a single common script is moot. Recommendation 1 was accompanied by a Minority Statement, reading as follows: Working Group member Petter Rindforth, in line with the position taken by his Constituency, the Intellectual Property Constituency (ICP),2 recommends mandatory translation and/or transliteration (transformation) of contact information in all generic top-level domains (gTLDs). Although he agrees that there are situations where the contact information in the local language of the registrant is the primary version, such as to identify the registrant in preparation for a local legal action, there are a number of situations where a global WHOIS search, providing access to data in as uniform a fashion as possible, is necessary for the data registration service to achieve its goals of providing transparency and accountability in the DNS. See also 5.1.1 [of the Final Report] explaining the Working Group's arguments supporting mandatory transformation of contact information in all generic top-level domains. Which stakeholders or others were consulted? Regular consultation with stakeholders took place during the lifetime of this PDP, specifically during three ICANN meetings (ICANN 49, 50 and 51), as well as public comment periods for the Preliminary Issues Report, the Initial Report and prior to Board consideration. What concerns or issues were raised by the community? The main concern that was raised by the Community was that a multi-script / multi-language database will lead to less transparency because scripts other than Latin might be less comprehensible for a majority of internet users. It would also reduce the search-ability of data. It was also feared that fraudulent registrants could hide their identity behind different scripts/languages. What significant materials did the Board review? The Board reviewed the Final Report, the GNSO Council Recommendations Report to the Board, as well as the summary of public comments and Staff's response to those comments. What factors did the Board find to be significant? The recommendations were developed following the GNSO Policy Development Process as outlined in Annex A of the ICANN Bylaws and have received the unanimous support from the GNSO Council. As outlined in the ICANN Bylaws, the Council's supermajority support for the motion (the Council voted unanimously in favor) obligates the Board to adopt the recommendation unless by a vote of more than two-thirds, the Board determines that the policy is not in the best interests of the ICANN community or ICANN. In addition, continuing the internationalization of the domain name system is an important area of work for ICANN. The recommendations have the potential to improve user-friendliness and accuracy of contact information data throughout a truly globalized DNS. Are there positive or negative community impacts? Some of the positive impacts identified in the Final Report include (but are not limited to): • Registrants not familiar with US-ASCII will be able to register domain names using the script they are most familiar with; • Registrars are not forced to translate or transliterate data but they have to validate data regardless of which script they support – the decision on which ones those are will be regulated by demand and supply; • Registration costs will not increase because requiring registrars to translate or transliterate all contact information data into one script3 will inevitably lead to costs that could be passed on to registrants; • Allowing registrants to use the language/script they are most familiar with when registering domains will have a positive impact on data accuracy. Some of the negative impacts identified in the Final Report are that: • Those seeking to search contact information data and operating in US-ASCII might have to translate or transliterate data to be able to contact registrants (though that is true for those seeking information but not familiar with US-ASCII even if translation or transliteration were mandatory). Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, budget); the community; and/or the public? There are no fiscal impacts on ICANN. Those members of the community and wider public might have to pay for professional translation or transliteration of contact information. However, these costs stand in stark contrast to the potential costs that would occur if under a blanket requirement every contact that is provided in a script other than US-ASCII would have to be translated or transliterated. Are there any security, stability or resiliency issues relating to the DNS? The current WHOIS protocol is not designed for scripts other than US-ASCII. However, the Registration Data Access Protocol (RDAP) is currently being rolled out as the WHOIS replacement and it [the RDAP] is fully compatible with different scripts. Once the RDAP is implemented – or any another replacement that is capable of dealing with scripts other than US-ASCII – there will be no security, stability, or resiliency issues related to the DNS if the Board approves the proposed recommendations. Rudi Vansnick Chair Non-for-Profit Operational Concerns Constituency (NPOC) www.npoc.org <http://www.npoc.org/> rudi.vansnick(a)npoc.org Tel : +32 (0)9 329 39 16 Mobile : +32 (0)475 28 16 32

3 2