Blog from July, 2016
https://www.icann.org/news/announcement-2-2016-07-28-en
28 July 2016
On 27 July 2016, Power Auctions LLC, ICANN's authorized auction service provider, conducted a New Generic Top-Level Domain (gTLD) Program auction to resolve contention for .WEB and .WEBS. Auction serves as the method of last resort for determining which applicant may operate a gTLD when several entities have applied for the same or confusingly similar gTLDs. This method was defined through ICANN's bottom-up, multistakeholder process.
Eight applicants completed the requirements for participating in the .WEB/.WEBS auction. NU DOT CO LLC prevailed in the auction for the price of $135 million to operate the .WEB gTLD, and Vistaprint Ltd prevailed with a price of $1 for the .WEBS gTLD.
Auction Proceeds
The proceeds from New gTLD Program auctions, which will total more than $230 million, are being reserved. The multistakeholder community will develop proposals for how these proceeds could be distributed. A community-based drafting team is currently working on a charter for a Cross-Community Working Group that will create recommendations for Board consideration. Learn more about this work.
"New gTLD Program auctions are the community-established, last resort method to help determine which applicant will have the opportunity to operate a particular new generic top-level domain, when multiple entities vied for the same or confusingly similar domains." said Akram Atallah, president of ICANN's Global Domains Division. "We look forward to seeing the community's recommendations for the use of these proceeds."
Auctions and the New gTLD Applicant Guidebook
The Internet community spent nearly three years developing a playbook for rolling out new gTLDs under the New gTLD Program, known as the New gTLD Applicant Guidebook. The guidebook outlines measures for addressing a variety of circumstances that could occur throughout the gTLD application and evaluation processes, including instances where multiple applicants applied for the same or confusingly similar new gTLDs. Only one entity can operate a given new gTLD, so contention must be resolved. Applicants can resolve contention among themselves, and ICANN encourages them to do so. However, this isn't always possible. The ICANN stakeholder community helped develop methods for resolving contention, and it decided that auction should serve as the method of last resort. ICANN is responsible for implementing auctions in accordance with the rules defined in the New gTLD Applicant Guidebook.
There are two different types of contention sets: direct and indirect. Direct contention occurs when multiple applicants are vying for the same or confusingly similar gTLDs. Indirect contention exists when two or more applications are in direct contention with a third application, but not with one another. .WEB/.WEBS was an indirect contention set consisting of one application for .WEBS and seven applications for .WEB. In this case, the application for .WEBS prevailed along with one application for .WEB. For a more detailed description of auction and indirect contention, see Module 4 of New gTLD Program Applicant Guidebook.
More Information
- Contention Set Status: 218 of 234 contention sets are now resolved. The majority have self-resolved, but 16 sets resolved via ICANN auction.
- Auction Results: Reports on this page of the New gTLD Microsite provide additional information on each auction outcome.
- Auction Proceeds and Costs: A detailed summary of the proceeds and costs of each auction through July 2016. This information will be updated within seven days of each auction.
- Auction Schedule [PDF, 263 KB]: Updated as of 28 July 2016.
- General New gTLD Program Auctions information.
About ICANN
ICANN's mission is to help 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 helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org.
https://www.icann.org/news/announcement-2016-07-28-en
28 July 2016
51 fellows from 35 countries have been selected to participate in ICANN's Fellowship program at the 57th Public Meeting in Hyderabad, India 3-9 November 2016. Of those fifty-two selected, 17 are returning fellows from at least one previous meeting and various experience levels, 10 of whom will be coaches to the 34 attending as first time fellows. The selected fellows represent all sectors of society including civil, government, ccTLD Operations, academia, facets of the business community, technical, security and end user groups.
An independent selection committee assessed the 319 fellowship applications received for this meeting; 76 of those met minimum requirements for possible selection. Priority is given to applicants who not only meet minimum program requirements, but who are current residents of developing and least developed nations and who are interested in participating in ICANN and its supporting organizations, advisory committees, stakeholder and constituency groups.
Click here to see the list of selected candidates and learn more about the fellowship program: http://www.icann.org/en/about/participate/fellowships
https://www.icann.org/news/announcement-2016-07-27-en
27 July 2016
In Brief
The Generic Names Supporting Organization (GNSO) Council adopted the Charter [PDF, 565 KB] of the GNSO Review Working Group during its meeting on 21 July 2016. This Working Group is tasked to develop an implementation plan for the GNSO Review recommendations [PDF, 407 KB] which were recently adopted by the ICANN Board. This is the Call for Volunteers to join this Working Group. Anyone interested in the GNSO Review and contributing to the development of the implementation plan and subsequent implementation is encouraged to volunteer.
What This Working Group Will Do
Per the GNSO Review Working Group Charter [PDF, 565 KB] the GNSO Review Working Group will be responsible for developing an implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome for the GNSO Review recommendations adopted by the ICANN Board (thirty-four (34) recommendations of the Final Report [PDF, 727 KB] of the Independent Examiner (i.e. all recommendations excluding recommendations 23 and 32). This implementation plan is to be submitted for approval to the GNSO Council, followed by consideration by the ICANN Board. Following the approval of the implementation plan, the Working Group is also expected to execute and oversee the implementation of the GNSO Review recommendations unless specified differently in the implementation plan.
The GNSO Review Working Group will also be responsible for considering any new requests1 by the GNSO Council concerning issues related to the GNSO Council processes and procedures and to Working Group guidelines that have been identified either by the GNSO Council, or a group chartered by the GNSO Council, as needing discussion. However, the first priority of the Working Group will be the development of an implementation plan and the subsequent implementation of the GNSO Review recommendations.
Timeline and Deliverables
The GNSO Review Working Group is expected to deliver the implementation plan to the GNSO Council for consideration at the GNSO Council meeting at ICANN57 at the latest in order to meet the Board set objective of 'an implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome, shall be submitted to the Board as soon as possible, but no later than six (6) months after the adoption of this resolution'2 i.e., December 2016.
How to Join
Each GNSO Stakeholder Group and/or Constituency will identify one primary and one alternate member to serve on the GNSO Review Working Group. In addition to these appointed members, anyone interested will be able to join this working group as a participant or observer. Please note that participants are expected to attend conference calls and to actively participate in online discussions. They also must submit a Statement of Interest per Section 5.0 of the GNSO Operating Procedures [PDF, 1.31 MB]. Observers can follow the group's work on the mailing list but can neither send to the mailing list nor participate actively in the calls.
Interested participants and observers are requested to complete the sign-up sheet by Friday, 19 August 2016.
Next steps
It is anticipated that the GNSO Review Working Group will convene online for the first time in the last week of August 2016. Following that, regular online meetings will be scheduled in accordance with the Working Group's work plan, which it is expected to develop as one of its first tasks.
Further information and preparation
For those interested in volunteering for this effort, you are encouraged to review the following materials:
- GNSO Review Recommendations [PDF, 407 KB]
- Independent Examiner Final Report [PDF, 727 KB]
- Frequently Asked Questions
Background
The second independent review of the GNSO commenced in 2014. The Final Report of the independent examiner was published on 15 September 2015 (see https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf [PDF, 1.99 MB]) and contained 36 recommendations in the areas of: participation & representation, continuous development, transparency and alignment with ICANN's future. The GNSO Council adopted the GNSO Review Recommendations Feasibility and Prioritization analysis (see: http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb16-en.pdf [PDF, 407 KB]) on 14 April 2016 with the modification of Recommendation 21, that the council recommends staff working with the GNSO to institute methods of information sharing of highly relevant research related to gTLDs to help the GNSO community members increase their knowledge base (low priority).
On 25 June, the ICANN Board accepted the Final Report from the independent examiner, taking into account the GNSO Working Party's Feasibility and Prioritization Analysis of the GNSO Review Recommendations, adopted with modifications by the GNSO Council. The Board adopted thirty-four (34) recommendations of the Final Report (i.e. all recommendations excluding recommendations 23 and 32). Furthermore, the Board requested that the GNSO Council convene a group that oversees the implementation of Board-accepted recommendations.
Per the motion adopted on 21 July 2016, the GNSO Council adopted the Charter [PDF, 565 KB] of the GNSO Review Working Group and directed staff to send a Call for Volunteers for the Working Group.
1 For items that are submitted for review 'on request', the GNSO Review WG expects to receive detailed input from the group affected by the process/operational change concerned. See request template at: https://community.icann.org/download/attachments/14713135/GNSO-SCI-ReviewRequest-yyymmdd_template.docx?version=1&modificationDate=1469143165000&api=v2 [DOCX, 102 KB].
2 The Board resolution was adopted on 25 June 2016
Hello All,
Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 25 July- 29 June 2016.
Update 2: Wednesday added
14:00U UTC: At-Large Review Working Party call https://community.icann.org/x/5Q6bAw
Updates will follow as Doodles close.
Monday 25 July 2016
None
Tuesday 26 July 2016
13:00 UTC: GNSO Working Group Communication Tools Classroom Please RSVP via this form for call details (by 25 July 2016)
16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag
18:00 UTC: (At-Large) EURALO Monthly call https://community.icann.org/x/hwObAw
21:00 UTC: ALAC Monthly call https://community.icann.org/x/JAmbAw
Wednesday 27 July 2016
12:00 UTC: (GNSO) New gTLD Auction Proceeds CCWG Charter Drafting Team https://community.icann.org/x/px6AAw
14:00U UTC: At-Large Review Working Party call https://community.icann.org/x/5Q6bAw
20:0 0UTC: ALAC Leadership Team (ALT) Monthly Call https://community.icann.org/x/GA2bAw
21:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw
Thursday 28 July 2016
14:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg
16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg
23:00 UTC: LACRALO-GSE Capacity Building Webinar on the topic “ Next-Generation gTLD Registration Directory Services (RDS) to replace WHOIS (WHOIS PDP)” https://community.icann.org/x/bw_bAw
Friday 29 July 2016
None
Please confirm your dial-out requests or apology notice to:
For GNSO calls: GNSO Secretariats gnso-secs@icann.org
For At-Large calls or ALAC :staff@atlarge.icann.org
For CWG IANA Stewardship Brenda.Brewer@icann.org
For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org
For CCWG-IG desiree.cabrera@icann.org
Thank you.
Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar
ICANN Policy Staff in support of the At-Large Community
E-mail: staff@atlarge.icann.org
Website: atlarge.icann.org
Facebook: facebook.com/icannatlarge
Twitter: @ICANNAtLarge
https://www.icann.org/news/announcement-2016-07-26-en
26 July 2016
ICANN today announced that gTLD contracted parties must update their Registration Data Directory Services (RDDS) by 1 February 2017. Registries and registrars are required to implement the new Registration Data Access Protocol (RDAP) gTLD Profile. Registries must also implement the data specifications defined in the Registry Registration Data Directory Services Consistent Labeling and Display Policy.
The RDAP gTLD Profile and the RDDS Consistent Labeling and Display Policy are the products of community efforts to improve the current system used to discover who controls a domain name. This system comprises data retrieval protocols – WHOIS and a web-based version of WHOIS – and databases controlled by registries and registrars that contain domain registration information.
ICANN has notified contracted parties that they are responsible for modifying their systems within six months. ICANN consulted these parties when defining the new requirements and implementation plans.
Background
The Registration Data Access Protocol was developed by the Internet Engineering Task Force to eventually replace the WHOIS protocol. This new protocol is superior to WHOIS in terms of data access security, support for international characters, extensibility, and in the standardization of query, response and error messages. The RDAP gTLD Profile maps ICANN policy and contractual requirements onto technical requirements in order to standardize directory services across gTLD contracted parties.
The RDDS Consistent Labeling and Display Policy is a Consensus Policy developed and adopted in accordance with ICANN Bylaws. The policy is the result of recommendations adopted by the GNSO Council after the completion of the Thick WHOIS Policy Development Process. The ICANN board adopted these recommendations on 7 February 2014.
The goal of the RDDS Consistent Labeling and Display Policy is to align the way registries and registrars label and display registration data outputs. The policy uses the output specifications found in the 2013 Registrar Accreditation Agreement as the standard, thus only registries need to update their systems. Changes might include renaming or re-ordering fields and displaying additional data, such as registrar abuse contact information.
For more information on these topics, visit:
- Registration Data Access Protocol gTLD Profile
- Registry RDDS Consistent Labeling and Display Policy
- Thick WHOIS Policy Implementation
- Policy Implementation at ICANN
About ICANN
ICANN's mission is to help 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 helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org.
Hello All,
Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 25 July- 29 June 2016.
Update 1: Thursday added
23:00 UTC: LACRALO-GSE Capacity Building Webinar on the topic “ Next-Generation gTLD Registration Directory Services (RDS) to replace WHOIS (WHOIS PDP)” https://community.icann.org/x/bw_bAw
Updates will follow as Doodles close.
Monday 25 July 2016
None
Tuesday 26 July 2016
13:00 UTC: GNSO Working Group Communication Tools Classroom Please RSVP via this form for call details (by 25 July 2016)
16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag
18:00 UTC: (At-Large) EURALO Monthly call https://community.icann.org/x/hwObAw
21:00 UTC: ALAC Monthly call https://community.icann.org/x/JAmbAw
Wednesday 27 July 2016
12:00 UTC: (GNSO) New gTLD Auction Proceeds CCWG Charter Drafting Team https://community.icann.org/x/px6AAw
20:0 0UTC: ALAC Leadership Team (ALT) Monthly Call https://community.icann.org/x/GA2bAw
21:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw
Thursday 28 July 2016
14:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg
16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg
23:00 UTC: LACRALO-GSE Capacity Building Webinar on the topic “ Next-Generation gTLD Registration Directory Services (RDS) to replace WHOIS (WHOIS PDP)” https://community.icann.org/x/bw_bAw
Friday 29 July 2016
None
Please confirm your dial-out requests or apology notice to:
For GNSO calls: GNSO Secretariats gnso-secs@icann.org
For At-Large calls or ALAC :staff@atlarge.icann.org
For CWG IANA Stewardship Brenda.Brewer@icann.org
For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org
For CCWG-IG desiree.cabrera@icann.org
Thank you.
Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar
ICANN Policy Staff in support of the At-Large Community
E-mail: staff@atlarge.icann.org
Website: atlarge.icann.org
Facebook: facebook.com/icannatlarge
Twitter: @ICANNAtLarge
https://www.icann.org/news/announcement-2016-07-25-en
25 July 2016
25 July 2016 – ICANN today announced the publication of the Draft Report of the Independent Review of the Trademark Clearinghouse. Specific considerations related to the matching criteria, Trademark Claims service and Sunrise period are assessed in the review, conducted by Analysis Group.
Read the report [PDF, 1.15 MB].
The report is available for public comment through 3 September 2016. Feedback will be incorporated into a revised report.
Comment on the Draft Report of the Independent Review of the Trademark Clearinghouse.
Key Findings:
Expanding Matching Criteria to include non-exact matches may be of limited benefit: The dispute rate of completed registrations that are variations of trademark strings is very low.
Extending the Trademark Claims Service may have diminishing value: Registrations of names matching trademarks decline after the required 90-day Claims service period ends.
Few trademark holders utilize the Sunrise period: Most users of the Trademark Clearinghouse submit proof of use to gain access to the Sunrise period. However, across eligible trademark holders, fewer than 20 percent have used the Sunrise period to date.
Additional Information
An independent review of the Trademark Clearinghouse was recommended [PDF, 110 KB] by the GAC in May 2011 to be completed after the launch of the New gTLD Program. The review is informed by an analysis of Trademark Clearinghouse and third-party data sources, including data collected from stakeholders via interviews and surveys.
About ICANN
ICANN's mission is to help 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 helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org.
ICANN Weekly Newsletter
News from the Internet Corporation for Assigned Names and Numbers
Week ending 22 July 2016
Announcements This Week
Auction for 1 Contention Set Slated for 27 July 2016
22 July 2016
ICANN Publishes Plans for Upcoming Key Signing Key Rollover
22 July 2016
Notice of Preliminary Determination To Grant Registrar Data Retention Waiver Request
21 July 2016
Proposed Guidelines for the Second String Similarity Review Process
20 July 2016
ICANN Publishes gTLD Marketplace Health Index (Beta) for Community Feedback
19 July 2016
Release of Country and Territory Names within the .SOFTBANK, .ART and .CARAVAN TLDs
19 July 2016
Revised Report on DNS Abuse and New gTLD Program Safeguards Now Available
18 July 2016
Upcoming Events
3-9 November 2016: 57th International Public ICANN Meeting – Hyderabad
About ICANN
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.
https://www.icann.org/news/announcement-2-2016-07-22-en
22 July 2016
An auction will be facilitated by Power Auctions LLC on 27 July 2016 to resolve string contention for one new generic top-level domain (gTLD) contention set: .WEB/.WEBS. This set is an indirect contention set consisting of both the WEB and WEBS strings. An indirect contention set is when two applications are both in direct contention with a third application, but not with one another. Eight applicants have completed all necessary prerequisites to participate in the “method of last resort” auction, and the auction will proceed on 27 July 2016.
Within seven days after the completion of the auction, the results, including a results report, will be posted to the Auction Results page of the New gTLD Microsite. In addition, the Auction Proceeds page will be updated within seven days to reflect the proceeds and costs related to the Auction.
For additional information regarding New gTLD Program auctions, please view the Auctions landing page.
https://www.icann.org/news/announcement-2016-07-22-en
22 July 2016
ICANN today published plans outlining the operational processes required to change or "roll" the Root Zone Key Signing Key (KSK). The plans can be found here.
The KSK is a cryptographic public-private key pair, the public portion of which serves as the trusted starting point for Domain Name System Security Extensions (DNSSEC) validation. ICANN, in its role as the IANA Functions Operator, will change the current KSK which was originally created via processes defined in cooperation with the other Root Zone Management Partners: Verisign, who acted as the Root Zone Maintainer, and the U.S. Department of Commerce's National Telecommunications and Information Administration (NTIA), as the Root Zone Administrator.
The rollover plans detail implementation, monitoring, testing, and contingency processes designed to maintain operational stability and minimize end-user impact of the KSK rollover. The Root Zone Management Partners developed the plans that incorporate the Root Zone KSK Rollover Design Team recommendations [PDF, 1.01 MB].
For more information about the plans and operational processes involved in the KSK rollover, read this blog from ICANN's Chief Technology Officer or access the Root Zone KSK Rollover page.
Hello All,
Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 25 July- 29 June 2016.
Updates will follow as Doodles close.
Monday 25 July 2016
None
Tuesday 26 July 2016
13:00 UTC: GNSO Working Group Communication Tools Classroom Please RSVP via this form for call details (by 25 July 2016)
16:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag
18:00 UTC: (At-Large) EURALO Monthly call https://community.icann.org/x/hwObAw
21:00 UTC: ALAC Monthly call https://community.icann.org/x/JAmbAw
Wednesday 27 July 2016
12:00 UTC: (GNSO) New gTLD Auction Proceeds CCWG Charter Drafting Team https://community.icann.org/x/px6AAw
20:0 0UTC: ALAC Leadership Team (ALT) Monthly Call https://community.icann.org/x/GA2bAw
21:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw
Thursday 28 July 2016
14:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg
16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg
Friday 29 July 2016
None
Please confirm your dial-out requests or apology notice to:
For GNSO calls: GNSO Secretariats gnso-secs@icann.org
For At-Large calls or ALAC :staff@atlarge.icann.org
For CWG IANA Stewardship Brenda.Brewer@icann.org
For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org
For CCWG-IG desiree.cabrera@icann.org
Thank you.
Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar
ICANN Policy Staff in support of the At-Large Community
E-mail: staff@atlarge.icann.org
Website: atlarge.icann.org
Facebook: facebook.com/icannatlarge
Twitter: @ICANNAtLarge
https://www.icann.org/news/announcement-2016-07-21-en
21 July 2016
ICANN has made a preliminary determination that it is prepared to grant data retention waiver requests submitted by registrars World4 You Internet Service GmbH and LEDL.NET GmbH (the "Registrar") under the 2013 Registrar Accreditation Agreement (the "2013 RAA"). Section 2 of the Data Retention Specification (the "Specification") of 2013 RAA provides that prior to granting any exemption under the Specification, ICANN will post its determination on the ICANN website for a period of thirty (30) calendar days.
Pursuant to Section 2 of the Specification, Registrar submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of the Registrar's contention that compliance with the data collection and/or retention requirements of the Specification violates applicable law.
The Waiver Request was originally accompanied by the letter of the Article 29 Working Party dated 6 June 2013 (Statement on the data protection impact of the revision of the ICANN RAA). The Waiver Request was later supplemented by a legal opinion of Austrian counsel asserting that compliance with the data collection and/or retention requirements of the Specification violates various applicable provisions of Austrian data protection and telecommunications law.
The Waiver Request originally concerned Sections 1.1 and 1.2 of the Specification and sought to exclude any of these data elements from the retention obligation. In subsequent correspondence and good faith discussions it has been acknowledged that legitimate purposes may exist for the retention of data elements specified in the Specification; provided that ICANN submits a comprehensive list of legitimate purposes and recipients or categories of recipients for which/whom the data elements need to be retained, so that the Austrian registrars will be able to determine whether the data collection and/or retention requirements of the Specification constitute a so called standard application (Standardanwendung) which does not need to be notified with or authorized by the Austrian Data Protection Authority (the "Authority"). Should this not be the case, each Austrian registrar will have to notify the Authority on an individual basis of the data collection and/or retention requirements of the Specification based upon the comprehensive list of legitimate purposes and recipients or categories of recipients to be provided by ICANN or apply for authorization of such data collection and/or retention, where provided for under applicable Austrian law. Irrespective whether the data collection and/or retention requirements of the Specification constitute a so called standard application or not, the registrars will be required to respect claims of data subjects for deletion or correction, to the extent provided for under applicable Austrian law.
Furthermore, the legal opinion of Austrian counsel accompanying the Waiver Request cited Article 6 para. 1 nos. 2 and 5 of the Austrian Data Protection Act (Datenschutzgesetz 2000). These sections provide as follows (the following is an unofficial translation from German):
Article 6 para. 1 no. 2
"Data shall only … be collected for the specific, explicit and legitimate purposes and not further processed in a way incompatible with those purposes; …."
Article 6 para. 1 no. 5
"Data shall only … be kept in a form which permits identification of data subjects as long as this is necessary for the purposes for which the data were collected; a longer period of storage may be laid down in specific laws, particularly laws concerning archives."
The Registrar is therefore seeking a waiver with respect to Sections 1.1.1 through 1.1.8 of the Specification that seeks to reduce from two years to one year the period for which these specified data elements must be retained after the Registrar's sponsorship of the Registration ends.
Against the background of the foregoing issues, ICANN has determined on a preliminary basis that it is prepared to grant the Waiver Request in a limited scope as outlined below. ICANN is posting this preliminary determination for a period of thirty (30) days to seek feedback and input from the community on the proposed data retention waiver. After the thirty (30) day period following this posting has expired, ICANN will consider all feedback and input received before making a final determination on whether to grant the Waiver Requests.
The scope of the proposed waiver would be to permit the Registrar to maintain the information specified in Sections 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of one (1) additional year thereafter rather than two (2) additional years thereafter. The specific change to the Specification would be that, for the duration of the waiver, the retention requirement of Section 1.1 of the Data Retention Specification would be changed from "two additional years" to "one additional year."
Apart from that, the Registrar shall remain obliged to retain all data elements specified in Sections 1.1 and 1.2 of the Specification for the periods specified therein; provided that ICANN submits a comprehensive list of legitimate purposes and recipients or categories of recipients for which/whom the data elements need to be retained. ICANN hereby declares the " legitimate purposes for collection / retention and recipients or categories of recipients " contained in the "Description of 2013 RAA Data Retention Specification - Data Elements, Legitimate Purposes for Collection/Retention and Recipients of Data" (available at https://www.icann.org/en/system/files/files/raa-data-retention-elements-10aug15-en.pdf [PDF, 295 KB]) (the "Description") to constitute such comprehensive list of legitimate purposes and recipients or categories of recipients, subject to further changes.
If additional or other legitimate purposes for collection / retention or recipients or categories of recipients become relevant in the future, ICANN will publicly notify thereof and change the Description accordingly. If changing the purposes or recipients or categories of recipients requires the (additional) notification of or authorization by the Authority, the Registrar will conduct such notification or apply for such authorization accordingly.
ICANN shall provide reasonable additional information regarding the legitimate purposes or recipients or categories of recipients if and as reasonably requested by the Authority within the scope of such notification or application for authorization.
If and insofar as the Authority rules that the collection / retention of certain data for certain purposes and / or recipients or categories of recipients violate applicable law ICANN and the Registrar will determine in good faith whether and to what extent the Description can be changed to accommodate the concerns of the Authority. The rules of the Waiver Request procedure described in Sections 2, 3, and 4 of the Specification shall apply accordingly in this case and written notice of the Authority's rejection decision to ICANN will be deemed to constitute a further Waiver Request.
Furthermore, it is acknowledged that data elements which are subject to claims of data subjects for correction or deletion are excepted from the collection and/or retention requirements of the Specification, if and to the extent they are founded under applicable Austrian law.
In all other respects the terms of the Specification would remain AS-IS.
If ICANN does make a final determination to grant the Waiver Request sought by the Registrars, the provisions of Section 3 of the Specification would apply to similar waivers requested by other registrars located in the same jurisdiction. Section 3 of the Specification provides as follows:
If (i) ICANN has previously waived compliance with the requirements of any requirement of this Data Retention Specification in response to a Waiver Request from a registrar that is located in the same jurisdiction as Registrar and (ii) Registrar is subject to the same applicable law that gave rise to ICANN's agreement to grant such wavier, Registrar may request that ICANN to grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request, in which case Registrar may thereafter make an Wavier Request pursuant to Section 2 of this Data Retention Specification.
A public comment period will remain open until 23:59 UTC, 22 August, 2016. Public comments will be available for consideration by ICANN staff and the ICANN Board.
The Registrar's Waiver Request and supporting documents are available here: https://www.icann.org/en/system/files/files/waiver-request-ledlnet-gmbh-21jul16-en.pdf [PDF, 2.92 MB].
Comments can be posted to: comments-ledlnet-gmbh-21jul16@icann.org.
Comments can be viewed at: https://forum.icann.org/lists/comments-ledlnet-gmbh-21jul16/.
Hello All,
Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 18 July- 22 June 2016.
Update 1:
Thursday added:
21:00 UTC: At-Large Capacity Building Program 2016 – Seventh Webinar on the Topic: “Work Stream 2 Topics” https://community.icann.org/x/VQmbAw
Updates will follow as Doodles close.
Monday 18 July 2016
22:00 UTC (GNSO) New gTLD Subsequent Procedures Working Group https://community.icann.org/x/Jgp1Aw
23:00 UTC: (At-Large) LACRALO Monthly call https://community.icann.org/x/aQObAw
Tuesday 19 July 2016
14:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg
Wednesday 20 July 2016
05:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag
16:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw
19:00 UTC: CWG IANA Stewardship Meeting DT-O https://community.icann.org/x/37fhAg
Thursday 21 July 2016
06:00 UTC: (At-Large) APRALO Monthly call https://community.icann.org/x/cwabAw
06:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg
16:00 UTC: (GNSO) IGO-INGO Access to Curative Rights Protection Mechanisms Working Group https://community.icann.org/x/37rhAg
21:00 UTC: At-Large Capacity Building Program 2016 – Seventh Webinar on the Topic: “Work Stream 2 Topics” https://community.icann.org/x/VQmbAw
Friday 22 July 2016
None
Please confirm your dial-out requests or apology notice to:
For GNSO calls: GNSO Secretariats gnso-secs@icann.org
For At-Large calls or ALAC :staff@atlarge.icann.org
For CWG IANA Stewardship Brenda.Brewer@icann.org
For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org
For CCWG-IG desiree.cabrera@icann.org
Thank you.
Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar
ICANN Policy Staff in support of the At-Large Community
E-mail: staff@atlarge.icann.org
Website: atlarge.icann.org
Facebook: facebook.com/icannatlarge
Twitter: @ICANNAtLarge
https://www.icann.org/news/announcement-2-2016-07-19-en
19 July 2016
Today, ICANN published the gTLD Marketplace Health Index (Beta) [PDF, 2.37 MB] for community feedback. ICANN invites the community to review this report and submit comments on it no later than 6 September.
The gTLD Marketplace Health Index presents statistics and trends related to generic top-level domains. ICANN intends to publish these statistics biannually to track progress against its goal of supporting the evolution of the domain name marketplace to be robust, stable, and trusted.
Following the close of the public comment period, ICANN will work with a group of community volunteers to further refine the Index. If you would like to volunteer for this community Advisory Panel, visit https://mm.icann.org/mailman/listinfo/gtldmarketplace to subscribe to the Advisory Panel email list.
For more information about tracking gTLD marketplace health, read the blog.
https://www.icann.org/news/announcement-2016-07-18-en
18 July 2016
18 July 2016 - ICANN today announced that the "Revised Report on New gTLD Program Safeguards to Mitigate DNS Abuse" has been published.
Read the report [PDF, 101 KB].
The report, written by ICANN staff, explores methods for measuring the effectiveness of safeguards to mitigate Domain Name System (DNS) abuse that were implemented as part of the New gTLD Program. It explores which activities may constitute DNS abuse and provides a preliminary literature review examining rates of abuse in new gTLDs and the DNS as a whole.
The New gTLD Program Safeguards Against DNS Abuse report is intended to help inform the Competition, Consumer Trust and Consumer Choice (CCT) Review Team's analysis of how well program safeguards prevent DNS abuse.
The initial draft of the DNS Abuse Review report was published for comment on 15 March 2016. The revised version available today incorporates suggestions received during the public comment period on potential research methodologies and metrics to assess safeguard effectiveness. The CCT Review Team is considering this report and the feedback received as it continues to design and execute its review of New gTLD Program safeguards.
The report of public comments [PDF, 469 KB], which includes summary and analysis of the comments received regarding the draft report, was published and provided to the CCT Review Team on 17 June 2016.
New gTLD Program Reviews
ICANN's New gTLD Program has enabled hundreds of new top-level domains to enter into the Internet's root zone since the first delegations occurred in October 2013. Comprehensive reviews of the program are currently underway in a number of areas, including competition, consumer trust and choice, security and stability, rights protection and other areas. Along with commissioning third-party analyses, ICANN is capturing stakeholder experiences regarding the effects of the New gTLD Program.
About ICANN
ICANN's mission is to help 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 helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org.
