At-Large New gTLD Board Committee Consideration of GAC Safeguard Advice Workspace

Comment / Reply Periods (*)

Comment Open Date: 

23 April 2013

Comment Close Date: 

14 May 2013 - 23:59 UTC

Reply Open Date: 

15 May 2013

Reply Close Date: 

4 June 2013 - 23:59 UTC

Important Information Links

Public Comment Announcement

To Submit Your Comments (Forum)

View Comments Submitted

Brief Overview

Originating Organization: 

New gTLD Board Committee

Categories/Tags: 

• Contracted Party Agreements
• Second-Level Domains
• Top-Level Domains

Purpose (Brief): 

To solicit input on how the New gTLD Board Committee should address GAC advice regarding safeguards applicable to broad categories of New gTLD strings.

Current Status: 

GAC Beijing Communiqué issued on April 11, 2013 includes GAC Advice on New gTLDs.

Next Steps: 

New gTLD Board Committee will consider how to address GAC advice on New gTLD safeguards.

Staff Contact: 

Jamie Hedlund

Email Staff Contact

Detailed Information

Section I: Description, Explanation, and Purpose: 

On 11 April 2013, the Governmental Advisory Committee issued its Beijing Communiqué in which it provided advice on New gTLDs. The Board New gTLD Committee, acting on behalf of the full Board, will now consider how to address the GAC Advice. To help inform this process, the Committee has directed staff to solicit comment on how it should address one element of the advice: safeguards applicable to broad categories of NewgTLD strings. Accordingly, ICANN seeks public input on how the Board New gTLD Committee should address section IV.1.b and Annex I of the GAC Beijing Communiqué.

Section II: Background: 

One of ICANN's key responsibilities is introducing and promoting competition in the registration of domain names, while ensuring the security and stability of the domain name system (DNS). Below are major milestones in the program leading up to the GAC Beijing Communiqué:

• ICANN's Generic Names Supporting Organization (GNSO) begins a policy development process to consider the introduction of new gTLDs in 2005
• The "GAC Principles Regarding New gTLDs" is presented to the ICANN Board in 2007
• ICANN Board adopted 19 specific GNSO policy recommendations for implementing new gTLDs in 2008
• ICANN undertakes implementation process to address stakeholder concerns, such as the protection of intellectual property and community interests, consumer protection, and DNS stability during 2008-2011. This work includes public consultations, review, and input on multiple draft versions of the Applicant Guidebook
• The Governmental Advisory Committee (GAC) and the ICANN Board engage in intensive consultations regarding the GAC's "scorecard" advice on new gTLDs during first half of 2011
• In June 2011, ICANN's Board of Directors approved the Guidebook incorporating most of the GAC's scorecard advice and authorized the launch of the New gTLD Program
• ICANN opens the New gTLD application window on January 12, 2012. On June 11, 2012, ICANNreveals the 1,930 New gTLD applications received and posted them for public comment
• On October 12, 2012, the GAC issues its Toronto Communiqué, indicating that "[t]he statements and commitments detailed in individual gTLD applications are a critical input to the GAC's work" and advised the ICANN Board "that it is necessary for all of these statements of commitment and objectives to be transformed into binding contractual commitments, subject to compliance oversight by ICANN."
• On November 20, 2012, the GAC files and publicly posts 242 Early Warnings on individual NewgTLD applications.
• On February 5, 2013, in response to advice provided in the Toronto GAC Communiqué, the NewgTLD Program Board Committee approves a public comment period on a proposed "Public Interest Commitments Specification" as a mechanism to transform application statements into binding contractual commitments, as well as to give applicants the opportunity to voluntarily submit to heightened public interest commitments. On March 6. 2013, ICANN posts the 499 PIC Specifications submitted by applicants.

The GAC met during the ICANN Beijing Meeting and provided additional advice to the ICANN Board regarding the New gTLD program. Relevant to this public forum is Section IV.1.b of the GAC Beijing Communiqué, which states, "To reinforce existing processes for raising and addressing concerns the GAC is providing safeguard advice to apply to broad categories of strings." The safeguard advice appears in Annex I of the Beijing Communiqué.

ICANN officially notified applicants of the publication of GAC Advice on April 18, 2013, triggering the 21-day applicant response period per the Applicant Guidebook Module 3.1. The applicants' responses and the input received in this Public Comment Forum will serve as important inputs to the New gTLD Board Committee's consideration of the GAC Advice.

Section III: Document and Resource Links: 

• ICANN Announcement on GAC Advice Issued on New gTLDs
• GAC Beijing Communiqué [PDF, 156 KB]

Section IV: Additional Information: 

N/A

---

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

FINAL VERSION TO BE SUBMITTED IF RATIFIED

Please click here to download a copy of the PDF below.

 

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

ALAC Statement on the New gTLD Board Committee Consideration of GAC Safeguard Advice

The At-Large Advisory Committee (ALAC) supports the intent of what is requested in the New gTLD safeguards outlined within the GAC Communiqué issued during the ICANN 46th meeting in Beijing.

We find it regrettable that these safeguards were not introduced by the GAC during the design of the New gTLD program or much earlier in the implementation process.  An early intervention would have successfully imprinted strong public interest requirements on the program.  In addition, it would have allowed sufficient time for ICANN to develop more effective and enforceable mechanisms to address community and public interest concerns.

The contents coupled with the late timing of the GAC intervention highlight the challenge of understanding and grappling with the full implication of an extremely complex program on the interests that the GAC represents.  We feel that it is important for the ICANN Board to note that different stakeholder groups in the ICANN ecosystem have different consultation requirements to come to an agreed position.  Some (like the GAC and the ALAC) may require more time to provide meaningful, representative and consultative feedback.

The GAC advice carries tremendous value in terms of consumer protection, which the ALAC fully appreciates.  We recognize that the intervention creates a high level of uncertainty regarding the implementation and viability of the new gTLD program.  We thus call on the ICANN board to address the concerns raised by the GAC with urgency to restore public confidence in the program while striving to re-establish certainty parameters for the new gTLD applicants.

Safeguards Applicable to All New gTLDs

Safeguards applicable to all new gTLDs: The ALAC supports all of the safeguards in principle.

We understand that the introduction of the safeguards at this point in time may place an unreasonable burden on new registries, including additional legal and financial liabilities.  These additional requirements may jeopardize the success of new enterprises and create a significantly uneven playing field between them and the legacy gTLDs.  To enhance choice and competition in the gTLD space, we urge ICANN to do everything possible within its remit to lessen the impact of the liabilities including through the use of contractual tools.

Safeguard for WHOIS verification and checks: We believe the term “statistically significant” needs to be carefully defined so as to set clear expectations and eliminate misunderstanding in implementation.

Category 1 / Consumer Protection, Sensitive Strings, and Regulated Markets

Sub-Items 1-4: We find these additional safeguards to be reasonable and support them fully.

Sub-Item 5: we find the requirement of providing contact details for regulatory bodies to be excessive, particularly for many TLD classes cited.

Non-Exhaustive Strings Identified for Safeguard Application: We find the list of TLDs to be over-reaching.  The references to “non-exhaustive” imply that at some undefined point in the future, new TLDs may be added to the list, which will affect program certainty for gTLD applicants or later operating registries.

Sub-Items 6-8:  The reference to "some of the above strings may require further targeted safeguards" is far too vague. Requirements for authorization and credentials and registry verification and re-verification of them are certainly justifiable for a limited set of TLDs. However, when taken in the context of the 180+ Category TLDs, such controls would put these new registries at a significant disadvantage to competing domain alternatives and would exercise control that is virtually unheard of in other forms of media.

Exclusive Access: We support the requirement that exclusive registry access should serve a public interest goal.  However, we feel that the requirement as stated is too general and requires greater specificity for enforceability.

Public Interest Commitments

Although this Public Comment Period is specifically focused on the safeguards identified in Annex I of the GAC Communiqué, the ALAC feels it important to highlight Annex II as well.

The GAC has issued as set of questions related to the Public Interest Commitments (PIC) Specification for new gTLD registries. The ALAC shares the GAC’s interest in the PIC as a mechanism for addressing community and public interest concerns.  The ALAC urges the ICANN Board to ensure that the questions posed by the GAC, as well as those concerns identified in the ALAC Statement on the PICDRP, are addressed urgently, and that clarification on the enforceability of the PIC be relayed clearly and comprehensively to the ICANN community by the time the ICANN 47th meeting is convened in Durban.

 

FIRST DRAFT SUBMITTED

The ALAC supports the intent of much of what is requested in the Safeguards on New gTLDs within the GAC Communiqué issued during the ICANN meeting in Beijing.

The ALAC regrets that many of these safeguards were not included as a matter of course during the design of the New gTLD program, and barring that, that the GAC had not requested such safeguards much earlier. Either would have demonstrated ICANN’s concern for the public interest far better than the position that we now find ourselves in and allowed ICANN and TLD applicants to move forward with certainty.

On the specific safeguards, the ALAC offers the following comments:

Safeguards Applicable to all New gTLDs.

The ALAC supports all of the safeguards in principle, but is concerned that their introduction at this point and with the full onus on the new registries may place an unreasonable burden on these new registries, and may additionally add unreasonable legal and financial liabilities on these registries. Both impacts may serve to jeopardize the success of these new enterprises and create a significantly uneven playing field between them and the legacy gTLDs.

ICANN should do whatever possible to lessen these impacts and liabilities, both contractually, and to the extent possible, assuming some of these responsibilities within ICANN. Moreover, terms such as “statistically significant” will need to be carefully defined so as to set clear expectations and eliminate misunderstandings.

Consumer Protection, Sensitive Strings, and Regulated Markets:

Safeguards 1-4 are reasonable and the ALAC supports them fully. Safeguard 5, to provide abuse point-of-contact and contact details for regulatory bodies appears to be excessive, particularly for many of the classes of TLDs cited.

Moreover, the ALAC finds that the list of included TLDs is somewhat over-reaching. The references to “non-exhaustive” imply that at some undefined point in the future, new TLDs may be added, again decreasing certainty for gTLD applicants or later operating registries.

Safeguards 6-8 on credential validation although theoretically attractive would seem to place an unreasonable burden on many of the TLD registries. Moreover, the identification of which TLDs this advice would apply to is far too vague to be directly implementable. The ALAC recommends that this be clarified.

On the requirement for Exclusive Access strings, the requirement that “exclusive registry access should serve a public interest goal” is admirable but sadly lacking in any degree of specificity or enforceability.