Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Comment Close
Date
Statement
Name 

Status

Assignee(s) and
RALO(s)

Call for
Comments
Call for
Comments
Close 
Vote
Announcement 
Vote OpenVote
Reminder
Vote CloseDate of SubmissionStaff Contact and EmailStatement Number
14.05.2013New gTLD Board Committee Consideration of GAC Safeguard AdviceCommentingAdopted
13Y, 0N, 0A 
and 31.05.201304.0306.2013
12:00 UTC 
0410.06.20130410.06.20130709.06.20130914.06.201304.06.2013

Jamie Hedulnd
jamie.hedlund@icann.org 

TBC
AL-ALAC-ST-0613-03-00-EN
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

...

FINAL VERSION TO BE SUBMITTED IF RATIFIED

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

PDF
nameAL-ALAC-ST-0613-01-00-EN.pdf

The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote. 

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.

 The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.

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.

...