ICANN Resolutions » 2006-11-22 - Review of .TRAVEL Wildcard Proposal

Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. 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.

2006-11-22 - Review of .TRAVEL Wildcard Proposal


Resolution of the ICANN Board
Topic: 
Tralliance RSEP Request to implement Search.travel (wildcard) Service
Summary: 

Board agrees (with the RSTEP evaluation of the proposed service) that the Tralliance Corporation search.travel wildcard proposal creates a reasonable risk of a meaningful adverse effect on security and stability and directs staff to inform Tralliance that the proposal is not approved.

Category: 
gTLDs
Meeting Date: 
周三, 22 十一月 2006
Resolution Number: 
06.85
Status: 
Complete
Implementation Actions: 
  • None
    • Responsible entity: None
    • Due date: None provided
    • Completion date: None
Resolution Text: 

Vint Cerf introduced the proposed new registry service from Trailliance and reviewed the findings of the RSTEP Report. The Board members discussed the report. Kurt Pritz raised the issue that the public comment period had commenced but had not completed and noted the previous public comment periods relating to the matter.

Following the board's discussion of this matter, Alejandro Pisanty moved for a resolution to disapprove the proposed service, and Susan Crawford seconded.

Whereas, Tralliance Corporation submitted a request for a new registry service called search.travel under the Registry Services Evaluation Policy . The proposed service would insert a wildcard into the .TRAVEL zone.

Whereas, ICANN conducted its review of the request and determined that although there were no significant competition issues, the proposal might raise significant security and stability issues and referred the proposal to the Registry Services Technical Evaluation Panel for further evaluation.

Whereas, on 2 November 2006, the Registry Services Technical Evaluation Panel review team completed its report on the search.travel proposal. The report was posted for public comment.

Whereas, based on the report of the Registry Services Technical Evaluation Panel, input from the Security and Stability Advisory Committee, At-Large Advisory Committee and other public comments, ICANN has concluded that the proposal creates a reasonable risk of a meaningful adverse effect on security and stability.

Resolved, (06.85) that the Board agrees that the Tralliance Corporation search.travel wildcard proposal creates a reasonable risk of a meaningful adverse effect on security and stability and directs staff to inform Tralliance that the proposal is not approved.

The resolution was received the unanimous support of all 11 board members present, with no abstentions. In addition to the board members who were not present during any of the meeting, Hagen Hultzsch and Rita Rodin were not present for the vote.

Additional Information: 
  • The Tralliance request was the first 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 2 November 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 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.
  • Why Top Level Domains Should Not Use Wildcard Resource Records, 10 November 2006, available at: http://cai.icann.org/en/node/714
  • 6 December 2006 Transcript of Security and Stability Advisory Committee public presentation on Tralliance's request to add a wild card to the .travel domain: http://www.icann.org/en/meetings/saopaulo/captioning-ssac-openmeeting-06dec06.htm
  • .TRAVEL sponsored TLD Registry Agreement and Amendment: http://www.icann.org/en/tlds/agreements/travel/
  • 24 March 2005: ICANN Completes Negotiations with Applicants for .JOBS and .TRAVEL
  • The resolution does not address funding for the items identified therein.