- ALAC-Announce - lists.icann.org

ICANN News Alert -- ICG Charter Open for Public Comments
by ICANN At-Large Staff Aug. 9, 2014

Aug. 9, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-08-08-en ________________________________ ICG Charter Open for Public Comments 8 August 2014 On July 18, the IANA Stewardship Transition Coordination Group (ICG) produced a draft charter<https://www.icann.org/en/system/files/files/draft-charter-coordination-grou…> [PDF, 43.7 KB] that defines its own tasks. The ICG views defining the broad outlines of its charter as important, but it views finalizing the charter and moving on to the real work of the transition planning to be of equal importance. Thus the ICG is opening up a short public comment period on the charter to determine if there are any major objections to the current draft that the ICG has not already taken into account. The charter is open for public comment until August 15, 2014 at 23:59 UTC. Public comments are considered to be for the public record, and for the information and consideration of all participants in this process, not just for the ICG. Everyone is encouraged to review any public comments that may be submitted via the process below. Public comment submission process links: Comment submission: icg-forum(a)icann.org<mailto:icg-forum@icann.org> List of comments submitted via this site: http://forum.icann.org/lists/icg-forum Charter: https://www.icann.org/en/system/files/files/draft-charter-coordination-grou… [PDF, 43.7 KB] Deadline: August 15, 2014 at 23:59 UTC

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to Mailclub SAS
by ICANN At-Large Staff Aug. 9, 2014

Aug. 9, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-5-2014-08-07-en ________________________________ ICANN Grants Data Retention Waiver to Mailclub SAS 7 August 2014 DATA RETENTION WAIVER MAILCLUB SAS MAILCLUB SAS ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request. Registrar's Waiver Request cites the previous data retention waiver granted by ICANN to OVH SAS, on the basis of OVH SAS's contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in France. See <https://www.icann.org/news/announcement-2014-03-12-en> Registrar and OVH SAS are both Société par actions simplifiée domiciled in France and subject to French law, and ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waiver previously granted to OVH SAS. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees that, following Registrar's execution of the 2013 RAA, for purposes of assessing Registrar's compliance with the data retention requirement of Paragraph 1.1 of the Data Retention Specification in the 2013 RAA, the period of "two additional years" in Paragraph 1.1 of the Data Retention Specification will be deemed modified to "one additional year." 2. In all other respects the terms of the Data Retention Specification will remain AS-IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in the Paragraphs 1.1.1 through 1.1.8 inclusive of the Data Retention Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar.

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to 1API GmbH
by ICANN At-Large Staff Aug. 9, 2014

Aug. 9, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-4-2014-08-07-en ________________________________ ICANN Grants Data Retention Waiver to 1API GmbH 7 August 2014 DATA RETENTION WAIVER 1API GmbH 1API GmbH ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of Registrar's contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA (the "Specification") violates applicable law in Germany. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

ICANN News Alert -- ICG Announces Second Conference Call
by ICANN At-Large Staff Aug. 9, 2014

Aug. 9, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2014-08-07-en ________________________________ ICG Announces Second Conference Call 7 August 2014 The IANA Stewardship Transition Coordination Group (ICG) will hold its next conference call on 19 August 2014, 12:00-14:00 UTC. For time zone conversions, please see here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=2nd+Conference+Cal…>. The community is welcome to attend by way of a listen-only mode Virtual Meeting Room<https://icann.adobeconnect.com/icg/> through which audio of the call will be streamed. In addition, translations into the 5 UN languages plus Portuguese will be available through relevant Adigo Bridge dial-in numbers and Conference ID codes. A list of country dial-in numbers can be found here<http://adigo.com/icann/>. In the case that there is no appropriate dial-in number for an interested participant, ICANN will provide a dial-out service to that individual. Correspondingly, language service Conference ID numbers are listed below: * Français – Conference ID: 75929475 * Español – Conference ID: 68385764 * 中文 – Conference ID: 825702 * Pусский – Conference ID: 345720 * العربية – Conference ID: 82855066 * Português – Conference ID: 759752 For more information about the ICG and the IANA Stewardship Transition, please visit the NTIA IANA Functions' Stewardship Transition Microsite<https://www.icann.org/stewardship>.

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to RegistryGate GmbH
by ICANN At-Large Staff Aug. 9, 2014

Aug. 9, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-08-07-en ________________________________ ICANN Grants Data Retention Waiver to RegistryGate GmbH 7 August 2014 DATA RETENTION WAIVER RegistryGate GmbH Registry Gate GmbH ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of Registrar's contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA (the "Specification") violates applicable law in Germany. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

UPDATED GNSO and At-Large calls - week of 11 August 2014
by ICANN At-Large Staff Aug. 8, 2014

Aug. 8, 2014

Dear all, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of the 11 August 2014. Updates will follow as Doodles close. Monday 11 August 14:00 UTC: At-Large Technology Taskforce call: https://community.icann.org/x/tZrbAQ 14:00 UTC: GNSO New gTLDs Subsequent Rounds Discussion: https://community.icann.org/x/OrXhAg 15:00 UTC : GNSO IRTP D https://community.icann.org/x/B4JwAg 16:00 UTC: Joint BCEC/BMSPC WG call: https://community.icann.org/x/IMHhAg 16:00 UTC: New IGO-INGO Access to Curative Rights Protection Mechanisms Working Group: https://community.icann.org/x/37rhAg 19:00 UTC: NARALO Monthly call: https://community.icann.org/x/6o0i Tuesday 12 August 14:00 UTC: GNSO PPSAI WG https://community.icann.org/x/9iCfAg Wednesday 13 August 19:00 UTC: GNSO Policy and Implementation WG https://community.icann.org/x/y1V-Ag Thursday 14 August 13:00 UTC: GNSO Translation and transliteration Contact Information PDP WG: https://community.icann.org/x/FTR-Ag Friday 15 August None at this time Please confirm your dial-out requests For GNSO calls: GNSO Secretariats gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> For At-Large calls: At-Large Staff : staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Kind regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge>

1 1

CALL FOR COMMENTS: ALAC Statement on the Introduction of Two-Character Domain Names in the New gTLD Namespace
by ICANN At-Large Staff Aug. 8, 2014

Aug. 8, 2014

Dear All, Olivier Crépin-Leblond, Chair of the ALAC, has asked that a call for comments be made on the draft ALAC Statement on the Introduction of Two-Character Domain Names in the New gTLD Namespace<https://community.icann.org/x/VqzhAg> in preparation for the start of the ALAC ratification process. The current draft, as well as additional information on the Public Comment, can be found on the At-Large Introduction of Two-Character Domain Names in the New gTLD Namespace Workspace<https://community.icann.org/x/VqzhAg>. Please submit any comments on the workspace using the comments function by 11 August 2014 20:00 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: <mailto:staff@atlarge.icann.org%3cmailto:staff@atlarge.icann.org> staff(a)atlarge.icann.org<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org>

1 0

ICANN Newsletter -- 1 August 2014
by ICANN At-Large Staff Aug. 6, 2014

Aug. 6, 2014

[ICANN]<http://www.icann.org/> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/Week ending 1 August 2014 ________________________________ Announcements This Week Board Extends Term of ICANN President<https://www.icann.org/news/announcement-4-2014-08-01-en> The ICANN Board has extended by two years the contract of President and Chief Executive Officer Fadi Chehadé. It will now run until 30 June 2017. 1 August 2014 Join Us for a Webinar on the Name Collision Occurrence Management Framework<https://www.icann.org/news/announcement-3-2014-08-01-en> ICANN will be holding a webinar to provide information regarding the Name Collision Occurrence Management Framework. There will be two sessions to accommodate different time zones. 1 August 2014 ICANN Approves Name Collision Occurrence Management Framework | Special IP Address (127.0.53.53) Alerts System Administrators of Potential Issue<https://www.icann.org/news/announcement-2-2014-08-01-en> ICANN today announced the approval of the Name Collision Occurrence Management Framework by the ICANN Board New gTLD Program Committee (NGPC). The framework implementation requirements were developed with input from many sources including the ICANN community, a report published by JAS Global Advisors LLC, and advice from the Security and Stability Advisory Committee (SSAC). 1 August 2014 ICANN Tells U.S. Court That ccTLDs Are Not "Property" | Files Motion to Quash in U.S. Legal Action Aimed at Seizing Top-Level Domains<https://www.icann.org/resources/press-material/release-2014-07-30-en> Washington, DC... The Internet Corporation for Assigned Names and Numbers (ICANN) has told a U.S. federal court in the District of Columbia, that a country code Top-Level Domain (ccTLD) cannot be considered "property," and thus cannot be attached by plaintiffs in a lawsuit, who are trying to obtain the assets of countries that they argued have supported terrorism. 30 July 2014 ICANN Approves Investment Policy Statement Update for 2014<https://www.icann.org/news/announcement-2014-08-01-en> As part of ICANN's responsibility to perform periodic reviews of the ICANN Investment Policy Statement, a revised policy has been approved by ICANN's Board of Directors implementing a number of minor changes. 30 July 2014 Registry Services Technical Evaluation Panel (RSTEP) Report on Public Interest Registry's Request to Implement Technical Bundling in .NGO and .ONG<https://www.icann.org/news/announcement-2014-07-29-en> To obtain community input on the Registry Services Technical Evaluation Panel (RSTEP) report regarding Public Interest Registry's (PIR) request to implement technical bundling of second level domains for .NGO and .ONG. PIR defines technical bundling as a set of two different gTLDs, with identical second level labels for which certain parameters are shared. 29 July 2014 ________________________________ Upcoming Events 12-16 October 2014: 51st International Public ICANN Meeting - Los Angeles<http://la51.icann.org/en/> 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 FY14 Operating Plan and Budget<http://www.icann.org/en/financials/budget-opplan.htm>

1 0

ICANN News Alert -- You are Invited to Attend the GNSO Review 360 Assessment Webinar!
by ICANN At-Large Staff Aug. 5, 2014

Aug. 5, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-08-04-en ________________________________ You are Invited to Attend the GNSO Review 360 Assessment Webinar! 4 August 2014 You are invited to attend a webinar regarding the 360 Assessment of the Generic Names Supporting Organization (GNSO)<https://www.icann.org/news/announcement-2-2014-08-04-en>. This briefing will provide the ICANN community with an overview of what the 360 Assessment is, how to participate and how it fits into the GNSO Review process. Date: Tuesday, 12 August 2014 Time: 19:00-19:30 UTC (time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Review+360+As…) Date: Wednesday, 13 April 2014 Time: 14:00-14:30 UTC (time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Review+360+As…) The webinar will be recorded and available for those who may not be able to join the sessions. The Generic Names Supporting Organization (GNSO<http://gnso.icann.org/>) serves an important function – it is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. The GNSO Review is part of ICANN's commitment to continuous improvement, accountability and transparency. It uses mechanisms and measures to maintain public confidence in the viability, reliability and accountability of ICANN. ICANN's Bylaws<https://www.icann.org/resources/pages/bylaws-2012-02-25-en>1 require that its structures, including the GNSO, be reviewed on a five-year cycle. The purpose of the review is to evaluate organizational effectiveness of the GNSO, acknowledge areas that are working well, identify areas that need improvement and affect needed changes. The quality, validity and acceptance of the GNSO Review and the resulting improvements depend on relevant and useful feedback from a diverse and representative group of people. This is the cornerstone of ICANN's bottom-up multistakeholder model. View the video of Jennifer Wolfe, GNSO Councilor and Chair of the GNSO Review Working Party<https://www.youtube.com/watch?v=1BcvYFcO-cM> The 360 Assessment, a new component within the organizational reviews, is designed to gather data for an independent examiner, Westlake Governance<https://www.icann.org/news/announcement-3-2014-06-23-en>, to use in the review process and may also inform GNSO self-improvement efforts. The 360 Assessment is an easy-to-use online tool for the GNSO community, other ICANN structures and community members, the Board and staff to provide valuable feedback to the independent examiner. To participate in this survey and make your voice heard, please click here: https://www.surveymonkey.com/s/GNSOREVIEW360SURVEY.. The 360 Assessment will be live from 4-August-2014 23:59 UTC to 10-September-2014 23:59 UTC. Webinar Details Please join the webinar on Tuesday, 12 August 2014 Time: 19:00-19:30:30 UTC (time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Review+360+As…) or on Wednesday, 13 April 2014 Time: 14:00-14:30 UTC (time converter: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Review+360+As…) The two sessions are duplicates, scheduled to accommodate different time zones. The webinars will be run in an Adobe Connect room with a brief slide presentation to frame interactive discussion, along with a dial-in conference bridge for audio. The session will be conducted in English. If you cannot join the live session, the recording of the session will be made available shortly after the meeting. Please register via email to charla.shambley(a)icann.org<mailto:charla.shambley@icann.org> by Tuesday, 11 August 2014 – 23:59 UTC to receive the dial-in details. A reminder with log-in and dial-in details will be sent to you prior to the call. Additional Information – GNSO Review 2014 * GNSO Review 2014 Workspace<https://community.icann.org/x/OJLhAg> * GNSO Review Frequently Asked Questions and Answers (FAQs)<https://community.icann.org/x/zbXhAg> * GNSO Review Background Information<https://community.icann.org/x/XZLhAg> Webinar Materials Tuesday, 12 August 2014: * AC Recording – To be provided following the webinar * Audio Recording – To be provided following the webinar * Transcript – To be provided following the webinar * Chat Transcript – To be provided following the webinar * Presentation – To be provided following the webinar Wednesday, 13 August 2014: * AC Recording – To be provided following the webinar * Audio Recording – To be provided following the webinar * Transcript – To be provided following the webinar * Chat Transcript – To be provided following the webinar * Presentation – To be provided following the webinar ________________________________ 1 Article X<https://www.icann.org/resources/pages/bylaws-2012-02-25-en#X> of ICANN Bylaws provides further detail. ICANN's Bylaws<https://www.icann.org/resources/pages/bylaws-2012-02-25-en> require that its structures, including the GNSO, be reviewed on a five-year cycle. According to the Bylaws, the goal of the review is "to determine (i) whether that organization has a continuing purpose in the ICANN structure, and (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness."

1 0

ICANN News Alert -- ICANN Approves Name Collision Occurrence Management Framework | Special IP Address (127.0.53.53) Alerts System Administrators of Potential Issue
by ICANN At-Large Staff Aug. 4, 2014

Aug. 4, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2014-08-01-en ________________________________ ICANN Approves Name Collision Occurrence Management Framework | Special IP Address (127.0.53.53) Alerts System Administrators of Potential Issue 1 August 2014 ICANN today announced the approval of the Name Collision Occurrence Management Framework<https://www.icann.org/en/system/files/files/name-collision-framework-30jul1…> [PDF, 634 KB] by the ICANN Board New gTLD Program Committee (NGPC). The framework implementation requirements were developed with input from many sources including the ICANN community, a report published by JAS Global Advisors LLC, and advice from the Security and Stability Advisory Committee (SSAC). The framework is designed to mitigate the impact of name collisions in the domain name system (DNS), which typically occur when fully qualified domain names conflict with similar domain names used in private networks. When this occurs, users can be taken to an unintended Web page or encounter an error message. To address this issue, the framework calls for registry operators to use a technique called "controlled interruption" to alert system administrators that there may be an issue in their network. Specifically, an IPv4 address - 127.0.53.53 - will appear in system logs, enabling a quick diagnosis and remediation. "We now have a well-defined methodology for mitigating name collisions for delegated top-level domain names and a path forward for registries to unblock certain second-level domains in their list," said Akram Atallah, president of ICANN's Global Domains Division. "These operational processes, which were developed in conjunction with the multistakeholder community, will help to ensure the security of the domain name system." Atallah went on to note that ICANN will provide information to and work with the Generic Names Supporting Organization (GNSO) to consider whether policy work on developing a long-term plan to manage gTLD name collisions issues should be undertaken. ICANN will be holding webinars<https://www.icann.org/news/announcement-3-2014-08-01-en> to discuss details of the Name Collision Occurrence Management Framework and answer questions on 12 August 2014 - Session 1 will take place at 01:00-02:30 UTC and Session 2 will be from 15:00-16:30 UTC. Overview: Name Collision Occurrence Management Framework Implementation ICANN registry operators are obligated to comply with requirements in the Name Collision Occurrence Management Framework, which include: * Acting on name collision reports from ICANN within two hours of receipt of the report during the first two years of the life of the top-level domain (TLD), measured from the time of delegation of the TLD; * Implementing continuous controlled interruption for a 90-day period. ICANN obligations include: * Monitoring the registry's implementation of the controlled interruption to ensure compliance with contractual requirements; * Coordinating an emergency response for name collision reports only where there is a reasonable belief that the name collision presents a clear and present danger to human life; and * Working within the Internet Engineering Task Force (IETF) and with other relevant technical communities to identify a mechanism for IPv6 IP addresses that provides similar functionality to that being used in IPv4 (the loopback IP address 127.0.53.53). The Name Collision Occurrence Management Framework also calls for the delegation of .CORP, .HOME, and .MAIL to be deferred indefinitely. ICANN will collaborate with the technical and security communities to determine the best way to handle these strings in the long term. For more information on name collisions please visit https://www.icann.org/namecollision<https://www.icann.org/resources/pages/name-collision-2013-12-06-en>. About ICANN ICANN's mission is to ensure a stable, secure and unified global Internet. To reach another person on the Internet you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN coordinates these unique identifiers across the world. Without that coordination we wouldn't have one global Internet. ICANN was formed in 1998. It is a not-for-profit public-benefit corporation with participants from all over the world dedicated to keeping the Internet secure, stable and interoperable. It promotes competition and develops policy on the Internet's unique identifiers. ICANN doesn't control content on the Internet. It cannot stop spam and it doesn't deal with access to the Internet. But through its coordination role of the Internet's naming system, it does have an important impact on the expansion and evolution of the Internet. For more information please visit: www.icann.org<https://www.icann.org/>. [UPDATE: The date of the Session 1 webinar on the Name Collision Occurrence Management Framework has changed. It will now take place from 01:00-02:30 UTC on 12 August 2014.]

1 0