- Category: (replace this text with one of the following categories: Administration/Budget, Board, ccTLD, gTLD, IP, ICANN Structure, International Agreement, Root Zone) gTLDs
- Topic: (replace this text with a keywords from title) Tralliance RSEP Request to implement Search.travel (wildcard) Service
- Board meeting date: 22 November 2006
- Resolution number: 06.85
- URL for Board minutes/resolution: http://www.icann.org/en/minutes/minutes-22nov06.htm
- Status: (replace this text with: Completed, Ongoing, Suspended) Completed
Summary
Board agrees (replace this text with the a one-sentence summary of the resolution)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.
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.
...
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.
Implementation Actions
- (replace this text with specific Action Item) None (replace this text with any additional notes related to this resolution, i.e. funding considerations)
- Responsible entity: (replace this text with the responsible entity: ICANN department, ICANN Community Structure, Board, U.S. Department of Commerce)
- Due date: (replace this text with Due Date)
- Completion date: (replace this text with Date action was implemented)
- (replace this text with specific Action Item)
- Responsible entity: (replace this text with the responsible entity: ICANN department, ICANN Community Structure, Board, U.S. Department of Commerce)
- Due date: (replace this text with Due Date)
- Completion date: (replace this text with Date action was implemented)
Other Related Resolutions
- (replace this text with links to related resolutions)
Additional Information
- None
- Due date: None provided
- Completion date: None
Other Related Resolutions
- Resolutions 04.86 and 04.87 - Board authorizes President and General Counsel to enter negotiations relating to proposed commercial and technical terms for .TRAVEL sTLD with applicant: http://www.icann.org/en/minutes/resolutions-18oct04.htm
- Resolutions 05.23 and 05.24 - Approval of .TRAVEL sTLD approved subject to amendment of Appendix 6 of proposed sponsored TLD registry agreement; President authorized to implement agreement: http://www.icann.org/en/minutes/minutes-08apr05.htm
- Other resolutions TBD
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.
Explanatory text does not modify or override Resolutions. See Board Resolutions Page for more information.
Note: The "Add Comment" box below is for sharing information about implementation of this resolution. Off-topic comments will be removed.