Historical Resolution Tracking Feature » 2007-01-16 - Two Character New Registry Service Proposal from .NAME Registry

Important note: The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.

2007-01-16 - Two Character New Registry Service Proposal from .NAME Registry


Resolution of the ICANN Board
Topic: 
Global Name Registry (GNR) RSEP request to implement Limited Release of Initially Reserved Two-Character Names service
Summary: 

Board authorizes the President and General Counsel to enter into an amendment to the .NAME Registry Agreement to implement the proposed registry service.

Category: 
gTLDs
Meeting Date: 
Tue, 16 Jan 2007
Resolution Number: 
07.03
Status: 
Complete
Implementation Actions: 
  • Execute amendment to Agreement.
    • Responsible entity: ICANN Staff
    • Due date: None specified
    • Completion date: 30 January 2007
Resolution Text: 

Whereas, ICANN conducted its review of the request and determined that although there were no significant competition issues, ICANN did not have sufficient information to conclude there are no significant security and stability issues and referred the proposal to the Registry Services Technical Evaluation Panel for further evaluation.

Whereas, on 4 December 2006, the Registry Services Technical Evaluation Panel review team completed its report on the proposal <http://www.icann.org/registries/rsep/RSTEP-GNR-proposal-review-team-report.pdf>. The review team determined that the proposal does not create a reasonable risk of a meaningful adverse effect on security and stability. The report was posted for public comment during the ICANN Annual Meeting in Sao Paulo, Brazil.

Whereas, based on the report of the Registry Services Technical Evaluation Panel, internal experts and other public comments, ICANN has concluded that there are no significant security and stability issues related to introduction of the proposal.

Resolved (07.03), the President and General Counsel are authorized to enter into an amendment of the .NAME Registry Agreement to implement the proposed registry service.

Additional Information: 
  • The GNR request was the second request after the implementation of the Registry Services Evaluation Policy (RSEP) (Effective Date of the Policy is 15 August 2006) that was referred to the Registry Services Technical Evaluation Panel (RSTEP) for review and assessment. The RSEP provides that in the event that ICANN reasonably determines during the 15 calendar day "preliminary determination" period that the proposed Registry Service might raise significant Stability or Security issues, ICANN will refer the proposal to the Registry Services Technical Evaluation Panel within five business days of making its determination.
  • The RSTEP conducted their evaluation of the proposed service and in their report dated 4 December 2006 stated, "Our technical evaluation of this proposed registry service with respect to the likelihood and materiality of effects on security and stability concludes that it does not create a reasonable risk of a meaningful adverse effect on security and stability."
  • The RSEP also provides that following receipt of the RSTEP report, which will be posted and available for public comment, the ICANN Board will have 30 days to reach a decision. In the event the ICANN Board reasonably determines that the proposed Registry Service creates a reasonable risk of a meaningful adverse effect on Stability or Security, Registry Operator will not offer the proposed Registry Service.
  • The RSEP request information is available at http://www.icann.org/en/registries/rsep/.
  • .NAME Registry Agreement: http://www.icann.org/en/tlds/agreements/name/
  • The resolution does not address funding for the items identified therein.