- ALAC-Announce - lists.icann.org

VOTE ANNOUNCEMENT: ALAC Statement on the Consultation on the Source of Policies & User Instructions for Internet Number Resource Requests
by ICANN At-Large Staff Aug. 7, 2013

Aug. 7, 2013

Dear All, Olivier Crépin-Leblond, Chair of the ALAC, has asked that a vote be held by the ALAC on the proposed "ALAC Statement on the Consultation on the Source of Policies & User Instructions for Internet Number Resource Requests<https://community.icann.org/x/Zjh-Ag>" for communication to the relevant parties. ***** Question: Do you support the ratification of the "ALAC Statement on the Consultation on the Source of Policies & User Instructions for Internet Number Resource Requests<https://community.icann.org/x/Zjh-Ag>" for communication to the relevant parties? ***** Additional information on this Statement can be found on the ALAC Consultation on the Source of Policies & User Instructions for Internet Number Resource Requests Workspace<https://community.icann.org/x/Zjh-Ag>. Please note that the poll will be open from 7-August-2013 23:59 UTC to 14-August-2013 23:59 UTC. 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

ICANN News Alert -- Rights Protection Mechanism (RPM) Requirements
by ICANN At-Large Staff Aug. 7, 2013

Aug. 7, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-06aug13-en.htm ________________________________ Rights Protection Mechanism (RPM) Requirements 6 August 2013 Forum Announcement: Comment Period Opens on Date: 6 August 2013 Categories/Tags: * Top-Level Domains * Intellectual Property * Contracted Party Agreements Purpose (Brief): The operational requirements for implementation of the Sunrise and Trademark Claims processes in new gTLDs, and a set of community-proposed revisions, are being posted for comment to give an opportunity for the community to review and provide feedback on these requirements. Public Comment Box Link: http://www.icann.org/en/news/public-comment/rpm-requirements-06aug13-en.htm This message was sent to matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91…>

1 0

URGENT: ATRT2 questions to the ALAC
by ICANN At-Large Staff Aug. 7, 2013

Aug. 7, 2013

Dear All, Please find attached a list of questions that were asked by the ATRT2 to the ALAC. Please submit your responses to these questions via input-to-atrt2(a)icann.org<mailto:input-to-atrt2@icann.org> by Monday 12 August 23:59 UTC. 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

ICANN News Alert -- Addressing the Consequences of Name Collisions
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-3-05aug13-en.htm ________________________________ Addressing the Consequences of Name Collisions 5 August 2013 As directed by the ICANN Board of Directors on 18 May 2013, ICANN commissioned and today releases the results of a study that considers the likelihood and impact of name space collisions between applied-for new gTLD strings and non-delegated TLDs. Additionally, the study also reviewed the possibility of collisions arising from the use of X.509 digital certificates. Background: In a study published in January 2013, ICANN's Security and Stability Advisory Committee (SSAC) identified fact that some certificate authorities issue X.509 certificates for domain names that are not resolvable in the public DNS. Such issues identified in SAC 057, as well as in SAC 045, are symptoms of entities that have local environments that include strong assumptions about the number of top-level domains and/or have introduced local top-level domains in private namespaces that may conflict with names yet to be allocated. These private namespaces sometimes "leak" into the public DNS (either through misconfiguration or the use of old software), meaning that requests for resources on private networks could end up querying the public-facing DNS Root Servers and hence "colliding" with the delegated new gTLD. The Study: On 18 May 2013, the ICANN Board approved a resolution calling for a detailed study of the name collision issue. ICANN contracted with Interisle Consulting Group, LLC to collect and analyze the necessary data on all applied-for strings. The resulting study, Name Collision in the DNS<http://www.icann.org/en/about/staff/security/ssr/name-collision-02aug13-en.…> [PDF, 3.34 MB], identifies three categories of strings by the potential risk of name space collision: * Low Risk: 80% of applied-for strings. * Uncalculated Risk: 20% of applied-for strings. * High Risk: 2 strings (.home, .corp). To minimize the likelihood of any impact, ICANN proposes to the community several mitigation measures to be taken as described in an accompanying staff recommendation paper, New gTLD Collision Risk Management<http://www.icann.org/en/about/staff/security/ssr/new-gtld-collision-mitigat…> [PDF, 166 KB]. They include: * Proceeding with contracting and delegation of those strings categorized as "low risk" (80%) but recommending additional mitigation measures which should not materially impact their timeline for delegation. * Conducting further study on those strings categorized as "uncalculated risk" (20%) anticipated to take 3-6 months to complete. * Delaying contracting and delegation of the two "high risk" strings until mitigation efforts can place them in the "low risk" category. New gTLD Security and Stability: Throughout the development of the New gTLD program, the security and stability of the Domain Name System has remained the paramount concern of the ICANN community. ICANN staff has prepared an information sheet, Secure and Stable Introduction of new gTLDs<http://www.icann.org/en/about/staff/security/ssr/intro-new-gtlds-05aug13-en…> [PDF, 102 KB], that describes the measures ICANN has taken to ensure the introduction of new gTLDs will not jeopardize that commitment. Public Comment: At this time, the mitigation steps outlined in the staff recommendation paper are proposals only and community input is strongly suggested. As a result, ICANN has opened a formal process for soliciting public comment. The form for submitting public comment and the calendar for doing so is available here<http://www.icann.org/en/news/public-comment/name-collision-05aug13-en.htm>. Coordinated Vulnerability Disclosure Process: ICANN takes this opportunity to inform the community that it has updated its risk management procedures for improved reporting and response to any unforeseen issues arising from the delegation of new gTLDs. Members of the community are urged to familiarize themselves with the process available for review here<http://www.icann.org/en/about/staff/security/vulnerability-disclosure-05aug…> [PDF, 628 KB]. This message was sent to matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91…>

1 0

ICANN News Alert -- Proposal to Mitigate Name Collision Risks
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-2-05aug13-en.htm ________________________________ Proposal to Mitigate Name Collision Risks 5 August 2013 Forum Announcement: Comment Period Opens on Date: 5 August 2013 Categories/Tags: * Top-Level Domains * Security/Stability Purpose (Brief): To solicit community comment on proposed efforts to mitigate potential impact resulting from name collisions as New gTLDs are delegated into the root zone. Public Comment Box Link: http://www.icann.org/en/news/public-comment/name-collision-05aug13-en.htm This message was sent to matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91…>

1 0

FW: ICANN News Alert -- Publication of the Dotless Domain Name Study
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-05aug13-en.htm ________________________________ Publication of the Dotless Domain Name Study 5 August 2013 ICANN is pleased to announce the publication of the Dotless Domain Name Security and Stability Study Report<http://www.icann.org/en/groups/ssac/documents/dotless-domain-study-29jul13-…> [PDF, 1.02 MB] by IT Security firm, Carve Systems LLC (Carve Systems). Dotless domain names are those that consist of a single label (e.g., http://example, or mail@example). Dotless names would require the inclusion of, for example, an A, AAAA, or MX, record in the apex of a TLD zone in the DNS (i.e., the record relates to the TLD-string itself). Background On 23 February 2012, the ICANN Security and Stability Advisory Committee (SSAC) published SAC 053: SSAC Report on Dotless Domains<http://www.icann.org/en/groups/ssac/documents/sac-053-en.pdf> [PDF, 182 KB]. In this report, the SSAC stated that dotless domains would not be universally reachable and recommended strongly against their use. As a result, the SSAC recommended that the use of DNS resource records such as A, AAAA, and MX in the apex of a Top-Level Domain (TLD) should be contractually prohibited where appropriate, and strongly discouraged in all cases. On 23 June 2012, the ICANN Board adopted resolution 2012.06.23.09<http://www.icann.org/en/groups/board/documents/resolutions-23jun12-en.htm#1…> tasking ICANN to consult with the relevant communities regarding implementation of the recommendations in SAC053. On 24 August 2012, ICANN staff published the SAC053 Report for public comment<http://www.icann.org/en/news/public-comment/sac053-dotless-domains-24aug12-…> requesting input to consider in relation to implementing the recommendations of the SSAC report. Public Comment period was closed on 5 November 2012. On 27 November 2012 the staff posted a report of the public comments<http://www.icann.org/en/news/public-comment/report-comments-sac053-dotless-…> [PDF, 137 KB] that showed a substantial number of comments both in favor of adopting the SSAC recommendations as well in opposition to the recommendations. In May of 2013 ICANN commissioned a study<http://www.icann.org/en/groups/ssac/documents/dotless-domain-sow-05aug13-en…> [PDF, 85 KB] on the stability and security implications of dotless domain name functionality to help ICANN prepare an Implementation plan for the SAC053 recommendations. On 10 July 2013 the Internet Architecture Board (IAB) released a statement on dotless domain names<http://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-st…>, recommending against the use of dotless domain names for TLDs. On 29 July 2013 Carve Systems delivered their report to ICANN. Consistent with the SSAC report, the Carve Systems report identifies security and stability issues that require mitigation before gTLDs can safely implement dotless domain names. The Carve Systems report identifies several risks, ten (10) of which are considered key risks that dotless domain names pose. Current Status Consistent with SSAC's SAC 053 recommendation, a contracted gTLD wishing to operate as dotless domain name must submit a proposal to be evaluated as part of the standard Registry Services Evaluation Process (RSEP).<http://www.icann.org/en/resources/registries/rsep> Similarly, section 2.2.3.3 of the Applicant Guidebook (AGB) prohibits the use of dotless domain names prior to approval by ICANN, stating that the only permissible DNS Resource Records for the apex in a TLD zone are: Start of Authority (SOA), Name Server (NS), and related DNSSEC records. The same section also states: "An applicant wishing to place any other record types into its TLD zone should describe in detail its proposal in the registry services section of the application. This will be evaluated and could result in an extended evaluation to determine whether the service would create a risk of a meaningful adverse impact on security or stability of the DNS." The ICANN Board New gTLD Program Committee (NGPC) will consider dotless domain names and an appropriate risk mitigation approach at its upcoming meeting in August. Acknowledgements ICANN wishes to thank the SSAC for their efforts in identifying and explaining the issues, and the community for their participation in the public comment process. This message was sent to matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91…>

1 0

ICANN News Alert -- .MOBI Cross-Ownership Removal Request
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-26jul13-en.htm ________________________________ .MOBI Cross-Ownership Removal Request 26 July 2013 Forum Announcement: Comment Period Opens on Date: 26 July 2013 Categories/Tags: Contracted Party Agreements Purpose (Brief): Afilias Limited requests the removal of the cross-ownership restrictions reflected on the .MOBI Registry Agreement dated 10 July 2005. See: http://www.icann.org/en/about/agreements/registries/mobi This request is submitted according to the "Process for Handling Requests for Removal of Cross-Ownership Restrictions on Operators of Existing gTLDs" adopted by the Board on 18 October 2012. See: http://www.icann.org/en/resources/registries/removal-cross-ownership. According to the approved process, in order to lift cross-ownership restrictions, existing gTLD registry operators could either request an amendment to their existing Registry Agreement to remove the cross-ownership restrictions or request to transition to the new form of Registry Agreement for new gTLDs. Any proposed material amendments to gTLD registry agreements would be subject to public comment prior to ICANN approval. The proposed Afilias Limited amendment to can be found here<http://www.icann.org/en/about/agreements/registries/mobi/proposed-mobi-amen…> [PDF, 51 KB]. The redlined agreement can be downloaded here<http://www.icann.org/en/about/agreements/registries/mobi/proposed-mobi-agre…> [PDF, 248 KB]. Public Comment Box Link: http://www.icann.org/en/news/public-comment/mobi-xo-removal-26jul13-en.htm This message was sent to matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91…>

1 0

ICANN News Alert -- .PRO Cross-Ownership Removal Request
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

[http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-2-26jul13-en.htm ________________________________ .PRO Cross-Ownership Removal Request 26 July 2013 Forum Announcement: Comment Period Opens on Date: 26 July 2013 Categories/Tags: Contracted Party Agreements Purpose (Brief): Afilias Limited requests the removal of the cross-ownership restrictions reflected on the .PRO Registry Agreement dated 22 April 2010. See: http://www.icann.org/en/about/agreements/registries/pro This request is submitted according to the "Process for Handling Requests for Removal of Cross-Ownership Restrictions on Operators of Existing gTLDs" adopted by the Board on 18 October 2012. See: http://www.icann.org/en/resources/registries/removal-cross-ownership. According to the approved process, in order to lift cross-ownership restrictions, existing gTLD registry operators could either request an amendment to their existing Registry Agreement to remove the cross-ownership restrictions or request to transition to the new form of Registry Agreement for new gTLDs. Any proposed material amendments to gTLD registry agreements would be subject to public comment prior to ICANN approval. The proposed Afilias Limited amendment to can be found here<http://www.icann.org/en/about/agreements/registries/pro/proposed-pro-amendm…> [PDF, 48 KB]. The redlined agreement can be downloaded here<http://www.icann.org/en/about/agreements/registries/pro/proposed-pro-agreem…> [PDF, 94 KB]. Public Comment Box Link: http://www.icann.org/en/news/public-comment/pro-xo-removal-26jul13-en.htm This message was sent to matt.ashtiani(a)icann.org<mailto:matt.ashtiani@icann.org> from: ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [http://app.icontact.com/images/icontact_tryFree.gif] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=24564788&l=6333&s=BCA3&m=91…>

1 0

VOTE ANNOUNCEMENT: (180) Australian Communications Consumer Action Network (ACCAN)
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

Dear All, The regional advice from APRALO regarding ALS Applicant (180) Australian Communications Consumer Action Network (ACCAN)has been received. The ALAC has decided to conduct a vote on whether to accept the regional advice. The following question has been posed to the ALAC: ***** Question: Should the regional advice from APRALO for ALS Applicant (180) Australian Communications Consumer Action Network (ACCAN)) be accepted? The regional advice was to accept the application. ***** Please note that this vote will be open from 5th August 2013 23:59 UTC until 09th August 2013 23:59 UTC.. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: <https://atlarge-lists.icann.org/mailman/listinfo/alac-announce> staff at atlarge.icann.org<mailto: <https://atlarge-lists.icann.org/mailman/listinfo/alac-announce> staff at atlarge.icann.org> _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org<mailto:ALAC-Announce@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac-announce At-Large Official Site: http://www.atlarge.icann.org<http://www.atlarge.icann.org/>

1 0

VOTE ANNOUNCEMENT: (179) Euro Individuals Association (EIA)
by ICANN At-Large Staff Aug. 6, 2013

Aug. 6, 2013

Dear All, The regional advice from EURALO regarding ALS Applicant (179) Euro Individuals Association (EIA)has been received. The ALAC has decided to conduct a vote on whether to accept the regional advice. The following question has been posed to the ALAC: ***** Question: Should the regional advice from EURALO for ALS Applicant (179) Euro Individuals Association (EIA) be accepted? The regional advice was to accept the application. ***** Please note that this vote will be open from 5th August 2013 23:59 UTC until 09th August 2013 23:59 UTC.. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: <https://atlarge-lists.icann.org/mailman/listinfo/alac-announce> staff at atlarge.icann.org<mailto: <https://atlarge-lists.icann.org/mailman/listinfo/alac-announce> staff at atlarge.icann.org> _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org<mailto:ALAC-Announce@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/alac-announce At-Large Official Site: http://www.atlarge.icann.org<http://www.atlarge.icann.org/>

1 0