- ALAC-Announce - lists.icann.org

ICANN News Alert -- New gTLD Collision Occurrence Management Plan Frequently Asked Questions
by ICANN At-Large Staff Dec. 4, 2013

Dec. 4, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-03dec13-en.htm ________________________________ New gTLD Collision Occurrence Management Plan Frequently Asked Questions 3 December 2013 ICANN's mission and core values call for ICANN to preserve and enhance the operational stability, reliability, security, and global interoperability of the Internet's system of unique identifiers (names, IP numbers and protocol parameters). In pursuing these goals and following the direction of its Board of Directors as well as taking into consideration the advice of the Security and Stability Advisory Committee, ICANN commissioned a study on the potential security impacts of the applied-for new-gTLD strings. The study was to consider whether name collisions might occur between applied-for new gTLD strings and domain names that may be in use in private namespaces ("non-delegated TLDs"). The study was also to review the possibility of name collision occurrences arising from the use of internal names for which X.509 digital certificates have been issued. A name collision occurs when users unknowingly access a name that has been delegated in the public DNS when the user's intent was to access a resource identified by the same name in a private network. Circumstances like these, where the administrative boundaries of private and public namespaces overlap and name resolution yields unintended results, present concerns and should be avoided if possible. However, the collision occurrences themselves are not the concern, but whether such collisions cause unexpected behavior or harm, the nature of the unexpected behavior or harm and the severity of consequence. On 5 August 2013, ICANN published and made available a name collision study <http://www.icann.org/en/about/staff/security/ssr/name-collision-02aug13-en.…> [PDF, 3.34 MB] (the "Study") that identifies categories of strings according to the occurrences of queries, as observed in root server log samples obtained from the "Day in the Life of the Internet" (DITL) initiative from DNS-OARC. The Study used as input: 1) samples of DNS requests transmitted to root servers (from the DITL initiative), complemented with 2) information from Certificate Authorities regarding the issuance of internal name certificates (e.g., TLS/SSL certificates for non-delegated names). A full description of the methodology of the Study can be found in section 3.4 of the Study. The Study also included options to mitigate the risks; however, it did not make specific recommendations for each of the categories. Based on the Study, ICANN staff published for public comment from 5 August to 17 September 2013 <http://www.icann.org/en/about/staff/security/ssr/new-gtld-collision-mitigat…> [PDF, 166 KB] a proposal to manage the risk of name collision. On 7 October 2013, the ICANN Board New gTLD Program Committee adopted a revised proposal <http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-07oct13…> that describes a plan to manage name collision occurrences between new gTLDs and existing private uses of the same strings. The below are frequently issued questions that have been asked regarding the plan and ICANN's answers. 1. How did ICANN compile the list of Second-Level Domain Names (SLDs) to block for the Alternate Path to Delegation? For each TLD its list of SLDs to block is composed of the SLDs that were queried for the TLD during the DITL samples of 2006 to 2013, and the 2010 DNSSEC rollout datasets. 2. What were the criteria used to consider a new gTLD ineligible for the Alternate Path to Delegation? Those new gTLDs that showed an outlier behavior in terms of additions to their list of queried SLDs from year to year were considered ineligible. In other words, ICANN considers a new TLD ineligible for the Alternate Path to Delegation in cases where the list of SLDs changes frequently and widely. The sources of data used to compile the variation in SLD lists are composed of yearly captures of DNS query data from 2006 to 2012. The 2013 dataset was not included since the strings were already known by then (and various activities or studies conducted on the known strings might bias any analysis). For these strings, the year-over-year increase of the number of SLDs queried is an outlier as compared to the population of proposed gTLDs in: (a) at least one of the year-to-year comparisons, and (b) 2012 (indicates churn is currently occurring). For example, a TLD that only is an outlier in the 2006-2007 comparisons will still be considered eligible. However, a TLD that is an outlier in the 2009-2010 and in the 2011-2012 comparisons will not be eligible for the alternate path to delegation. 3. Will the second-level-domain-name (SLD) block list be amended as a result of using other datasets while working on the Name Collision Occurrence Management Framework? There is no plan to amend the SLD block list for new gTLDs as a result of the development of the Framework. However, if there were a new discovery during the development of the Framework it will be taken into consideration. 4. Is source code for the creation of the block lists available? The process to create the blocking list is explained in detail in each of the Alternate Path to Delegation reports for every new gTLD that has signed an agreement and is considered eligible. For example see http://www.icann.org/en/about/agreements/registries/luxury/luxury-apd-repor… The code used to create the lists is based on the code published at https://github.com/JASdevteam/dns-oarc 5. How long should the SLDs in the block list be blocked? The blocking should be in effect until the mitigation measures described in the respective Name Collision Occurrence Assessment have been applied. 6. For a particular TLD, if the SLD "nic" appears in the DITL data (indicating that there might be a name collision issue there), why is "nic" allowed in the gTLD, and why is this risk more acceptable than the risk of any other name collision? The only name that is required to be used by contract is "whois.nic.<tld>" for the purpose of offering registry WHOIS service, i.e., "whois.nic.<tld>". Balancing the risk of using this name with the usability of having the WHOIS service available at a well-known location, ICANN decided to not include "nic" in the list of SLDs to be blocked by any new gTLD. However, the name collision response mechanism <http://www.icann.org/en/help/name-collision> is available to be used by an affected party to report significant harm caused by such domain name. Also note that the name is only available to the registry operator itself, which means that the registry has total control over the SLD. 7. Is ICANN going to update the list of blocked SLDs to include the year in which the names were queried? ICANN does not plan to update the list of blocked SLDs or to add the year in which the SLDs were queried. However, if there is interest from the community ICANN will consider adding this data when resources are available. 8. What should be done with the names in the SLD block list when they are released in regards to TMCH Sunrise and Claims? Names in the SLD block list for a TLD must be included in the Sunrise and Claims, subject to the registry's usual policies, but cannot be activated until the mitigation measures have been implemented. If a registry operator allocates names from the SLD block list during Sunrise or Claims period, it must inform the registrant that the name cannot be activated and may never be activated subject to the TLD's Name Collision Occurrence Assessment. This is a clarification to the language in section 3.2 of the Name Collision Occurrence Management Plan. The intention of the block list is to retain the behavior before a new gTLD is delegated (i.e., an NXDOMAIN response in DNS); that result is achieved by not activating the names in the list, irrespective of allocation. 9. What constitutes harm that warrants deactivation of a second-level domain name causing collisions? It is possible that name collision occurrences of some second-level names that did not appear in the dataset used for the SLD block list might occur after the applied-for gTLD begins operation. To mitigate this risk, ICANN has implemented a process to enable an affected party to report and request the temporary blocking of a recently activated domain name that causes demonstrably severe harm as a consequence of name collision. ICANN will act as the initial single point of contact for these reports, and will coordinate the notification with the relevant registry operator to ensure that the report is acted upon in an expedited manner. The assessment of harm will initially be done by ICANN in a case-by-case basis until the work on the Framework defines uniform criteria. 10. Is there going to be a name collision portal? ICANN is planning a portal to display the information available on this topic. 11. Are different types of trial delegations within the scope of the Name Collision Occurrence Management Framework? Yes, trial delegations at both TLD level (for the TLDs not eligible for the alternate path to delegation), and at the second level for SLDs under all new gTLDs, are going to be considered during the development of the Framework. If adopted, it is expected that the Framework will specify the trial delegation applicable for a particular type of collision. Additionally, during its meeting in Buenos Aires the ICANN Board passed a resolution directing staff to evaluate SSAC's SAC 062 recommendations, which explicitly asks for ICANN to consider trial delegations. 12. What is the process to consider the work being done to develop a Name Collision Occurrence Management Framework and decide whether to adopt it? The lead contractor is expected to work on a draft Framework in cooperation with the community as explained at <http://www.icann.org/en/news/announcements/announcement-2-11nov13-en.htm>. The draft Framework is then going to be published for public comment. After the public comment period has ended, comments will be summarized and the draft Framework will be updated based on public input. Finally, the New gTLD Program Committee of the ICANN Board will consider the final Framework for adoption. 13. Where can people participate in the development of the Name Collision Occurrence Management Framework? Anyone is welcome to participate in the development of the Framework. The Framework will be discussed in the public mailing list at <https://lists.dns-oarc.net/mailman/listinfo/collisions>. 14. Is the management of name collisions going to be extended to ccTLDs? The issue of name collisions was first reported to ICANN in reference to the new gTLD program. Given the number of new gTLDs that are expected, the priority of the work has been focused on new gTLDs. We recognize the issue is not unique to gTLDs; therefore ICANN is raising this issue with the Board Risk Committee to identify how to address this issue.

1 0

ICANN Newsletter -- 29 November 2013
by ICANN At-Large Staff Dec. 3, 2013

Dec. 3, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/ Week ending 29 November 2013 ________________________________ Announcements This Week Study on Whois Misuse<http://www.icann.org/en/news/announcements/announcement-2-27nov13-en.htm> This study, conducted by Carnegie Mellon University's Cylab (CMU), examines the extent to which public Whois contact information for gTLD domain names is misused (i.e. harmful actions such as spam, phishing, identity theft or data theft are taken using gTLD registration data). 27 November 2013 Protection of IGO and INGO Identifiers in All gTLDs (PDP) Recommendations for Board Consideration<http://www.icann.org/en/news/announcements/announcement-27nov13-en.htm> To obtain community input on the recommendations recently adopted by the GNSO Council concerning the Protection of IGO and INGO Identifiers in All gTLDs Policy Development Process prior to their consideration by the ICANN Board of Directors. 27 November 2013 ________________________________ Upcoming Events 23-27 March 2014: 49th International Public ICANN Meeting – Singapore<http://singapore49.icann.org/> About ICANN ICANN Bylaws<http://www.icann.org/en/general/bylaws.htm> Our bylaws are very important to us. They capture our mission of security, stability and accessibility, and compel the organization to be open and transparent. Learn more at www.ICANN.org<http://www.icann.org/>. Strategic Plan, 2012 - 2015<http://www.icann.org/en/planning/> Adopted FY13 Operating Plan and Budget<http://www.icann.org/en/financials/budget-opplan.htm>

1 0

ICANN News Alert -- Protection of IGO and INGO Identifiers in All gTLDs (PDP) Recommendations for Board Consideration
by ICANN At-Large Staff Dec. 3, 2013

Dec. 3, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-27nov13-en.htm ________________________________ Protection of IGO and INGO Identifiers in All gTLDs (PDP) Recommendations for Board Consideration 27 November 2013 Forum Announcement: Comment Period Opens on Date: 27 November 2013 Categories/Tags: * Contracted Party Agreements * Policy Processes Purpose (Brief): To obtain community input on the recommendations recently adopted by the GNSO Council concerning the Protection of IGO and INGO Identifiers in All gTLDs Policy Development Process prior to their consideration by the ICANN Board of Directors. Public Comment Box Link: http://www.icann.org/en/news/public-comment/igo-ingo-recommendations-27nov1…

1 0

ICANN News Alert -- Study on Whois Misuse
by ICANN At-Large Staff Dec. 3, 2013

Dec. 3, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-2-27nov13-en.htm ________________________________ Study on Whois Misuse 27 November 2013 Forum Announcement: Comment Period Opens on Date: 27 November 2013 Categories/Tags: Policy Processes Purpose (Brief): This study, conducted by Carnegie Mellon University's Cylab (CMU), examines the extent to which public Whois contact information for gTLD domain names is misused (i.e. harmful actions such as spam, phishing, identity theft or data theft are taken using gTLD registration data). The findings from the study provide empirical data needed by the ICANN community to assess community concerns about misused Whois contact information, identify the most common forms of misuse, and highlight the effectiveness of anti-harvesting measures in reducing misuse. The findings will also inform future policy development by ICANN and the GNSO in relation to improvements to the Whois system. Public Comment Box Link: http://www.icann.org/en/news/public-comment/whois-misuse-27nov13-en.htm

1 0

Meeting invitation/ ALAC monthly - Tuesday 17 December at 1500 UTC
by ICANN At-Large Staff Dec. 3, 2013

Dec. 3, 2013

Dear All, Due to the holiday season, the December ALAC Monthly call is scheduled on Tuesday 17 December at 1500 UTC for 2 hours. For other times: http://tinyurl.com/lc6pwkx The agenda (to be updated) and call details are available at: https://community.icann.org/x/ACqfAg Adobe Connect Room: http://icann.adobeconnect.com/alac If you are unable to attend the call please send an email indicating your absence and we will note this information on the agenda. If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine, Julia Charvolen ICANN At-Large Staff E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

Updated GNSO and At-Large calls - Week of 02 December
by ICANN At-Large Staff Dec. 3, 2013

Dec. 3, 2013

Dear all, Please find hereafter the At-Large and GNSO calls for the week of 02 December. We will update this list as and when calls are added. Tuesday 3rd December 1500 UTC; Privacy and Proxy PDP WG - https://community.icann.org/x/9iCfAg 20:00 UTC: SCI - https://community.icann.org/x/TCOfAg Wednesday 4th December 06:00 UTC: APRALO Singapore Showcase OC - https://community.icann.org/x/LSmfAg 1830 UTC: AFRALO Monthly - https://community.icann.org/x/7yefAg 2000 UTC: Policy and Implementation WG - https://community.icann.org/x/y1V-Ag 2100UTC: Metrics and Reporting WG - https://community.icann.org/x/myt-Ag Thursday 5th December 1300 UTC: ATLAS II WG - https://community.icann.org/x/aymfAg 16:00 UTC: IRTP D subteam Friday 6th December 1600 UTC: ATLAS II Events call - https://community.icann.org/x/BBWfAg Thank you, Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

MSI Panel: A Call to Action
by ICANN At-Large Staff Dec. 2, 2013

Dec. 2, 2013

[https://gallery.mailchimp.com/1a990feb5c/images/logo_icann_ideascale_3_.png] Designing a 21st Century ICANN Hello! The ICANN Strategy Panel on Multistakeholder Innovation<http://www.icann.org/en/about/planning/strategic-engagement/multistakeholde…> (the MSI Panel) and The Governance Lab @ NYU<http://thegovlab.org/> (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 MSI Panel community page here<http://bit.ly/1dS9sLp>. 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/. * Broadcast our "Call To Action," for this initiative, which is online here<http://bit.ly/HWNxrW>, 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 video<http://bit.ly/185t28Q> 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 www.thegovlab.org<http://www.thegovlab.org/>. Thanks and best, The MSI Panel & The GovLab

1 0

GNSO and At-Large calls - 2 December week
by ICANN At-Large Staff Dec. 2, 2013

Dec. 2, 2013

Dear all, Please find hereafter the At-Large and GNSO calls for the week of 02 December. We will update this list as and when calls are added. Monday 2nd December 1600 UTC: IRTP D - https://community.icann.org/x/B4JwAg 2000 UTC: PI I Definition Subteam - https://community.icann.org/x/_yifAg Tuesday 3rd December 1500 UTC; Privacy and Proxy PDP WG - https://community.icann.org/x/9iCfAg 20:00 UTC: SCI - https://community.icann.org/x/TCOfAg Wednesday 4th December 06:00 UTC: APRALO Singapore Showcase OC - https://community.icann.org/x/LSmfAg 1600 UTC: ATLAS II Events call - https://community.icann.org/x/BBWfAg - Date to be changed 1830 UTC: AFRALO Monthly - https://community.icann.org/x/7yefAg 2000 UTC: Policy and Implementation WG - https://community.icann.org/x/y1V-Ag 2100UTC: Metrics and Reporting WG - https://community.icann.org/x/myt-Ag Thursday 5th December 1300 UTC: ATLAS II WG - https://community.icann.org/x/aymfAg 16;00 UTC: IRTP D subteam Thank you, Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

1 0

GNSO and At-Large week calls - Week of 02 December
by ICANN At-Large Staff Nov. 30, 2013

Nov. 30, 2013

Dear all, Please find hereafter the At-Large and GNSO calls for the week of 02 December. Updates to follow. Monday 02 December 16:00 UTC: IRTP D: https://community.icann.org/x/B4JwAg 20:00 UTC: Policy and Implementation Definitions Sub Team: https://community.icann.org/x/_yifAg Tuesday 3rd December 15:00 UTC: Privacy and Proxy PDP WG: https://community.icann.org/x/9iCfAg 20:00 UTC: GNSO SCI: https://community.icann.org/x/5ILT Wednesday 4th December 06:00 UTC: APRALO Singapore Showcase OC: https://community.icann.org/x/LSmfAg 1830 UTC: AFRALO Monthly: https://community.icann.org/x/7yefAg 20:00 UTC: Policy and Implementation WG https://community.icann.org/x/y1V-Ag 21:00 UTC: GNSO Metrics and Reporting WG: https://community.icann.org/x/myt-Ag Thursday 5th December 16:00 UTC: IRTP D Sub Team TRDP meeting: https://community.icann.org/x/B4JwAg Thank you, Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen

1 0

Call for Volunteers GNSO Policy Translation and Transliteration PDP Working Group
by ICANN At-Large Staff Nov. 27, 2013

Nov. 27, 2013

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 Wednesday 11 December 2013, 18.00-19.00UTC - local times http://tinyurl.com/kyk5lej To join the webinar please RVSP to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> First meeting If you are interested in joining the Working Group, please contact gnso-secs(a)icann.org<mailto:gnso-secs@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…> 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+2013> 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.…> 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.…> 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.… * Final Issue Report on Translation and Transliteration of Contact Information (http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13…) * 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)

1 0