ICANN Resolutions » Renewal of .TRAVEL Registry Agreement
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.
President and CEO, or his designee(s), is authorized to take such actions as appropriate to finalize and execute the Agreement.
Whereas, ICANN commenced a public comment period from 12 May 2015 to 5 July 2015 on a proposed renewal Registry Agreement for the .TRAVEL TLD .
Whereas, the proposed .TRAVEL renewal Registry Agreement includes modified provisions to bring the .TRAVEL Registry Agreement into line with the form of the New gTLD Registry Agreement.
Whereas, the public comment forum on the proposed renewal Registry Agreement closed on 5 July 2015, with ICANN receiving fifteen (15) comments, both by individuals and organizations/groups. A summary and analysis of the comments were provided to the Board.
Whereas, the Board has determined that no revisions to the proposed .TRAVEL renewal Registry Agreement are necessary after taking the comments into account.
Resolved (2015.09.28.05), the proposed renewal .TRAVEL Registry Agreement [PDF, 621 KB] is approved, and the President and CEO, or his designee(s), is authorized to take such actions as appropriate to finalize and execute the Agreement.
Why the Board is addressing the issue now?
ICANN and Tralliance Registry Management Company, LLC (the "Registry Operator") entered into a Registry Agreement on 5 May 2005 for operation of the .TRAVEL top-level domain. The current .TRAVEL Registry Agreement expires on 19 October 2015. The proposed renewal Registry Agreement (the "Renewal Registry Agreement" or "Agreement") was posted for public comment between 12 May 2015 and 5 July 2015. At this time, the Board is approving the Renewal Registry Agreement for the continued operation of .TRAVEL TLD by the Registry Operator.
What is the proposal being considered?
The Renewal Registry Agreement approved by the Board includes modified provisions to make the Agreement in line with the form of the New gTLD Registry Agreement. The modifications include: updating technical specifications; requiring the inclusion of certain GAC safeguards as public interest commitments (which are subject to enforcement by the Public Interest Commitment Dispute Resolution Procedure); requiring the use of registrars under the 2013 Registrar Accreditation Agreement after a certain threshold is reached; and updating the registry fees.
In order to account for the specific nature of the .TRAVEL TLD, a Sponsored TLD, relevant provisions in the 5 May 2005 Sponsored TLD Registry Agreement have been included in the Renewal Registry Agreement. Specifically, provisions in the Charter outlining the sectors of the travel industry that are within the meaning of the community and eligible for registration are identified in Specification 12. The Renewal Registry Agreement also reflects previous approvals concerning reserved names.
Which stakeholders or others were consulted?
ICANN conducted a public comment period on the proposed .TRAVEL renewal Registry Agreement from 12 May 2015 through 5 July 2015, following which time the comments were summarized and analyzed. Additionally, ICANN engaged in bilateral negotiations with the Registry Operator to agree to the package of terms to be included in the Renewal Registry Agreement posted for public comment.
What concerns or issues were raised by the community?
Fifteen (15) members of the community participated in the public comment period. Members of the community raised two key concerns in their comments:
Transition of legacy TLDs to the form of the New gTLD Registry Agreement: Some public comments expressed concern regarding ICANN's process to use the new gTLD registry agreement as the starting point for renewal RAs for legacy gTLDs. These commenters suggest that taking such a position has the effect of transforming the New gTLD Post-Delegation Dispute Resolution Procedures (e.g., the Trademark Post-Delegation Dispute Resolution Procedure and the Public Interest Commitments Dispute Resolution Procedure) and the Uniform Rapid Suspension (URS) into de facto Consensus Policies without following the procedures laid out in ICANN's Bylaws for their creation. On the other hand, other comments supported ICANN's seeking consistency across registry agreements and noted that transitioning to the new form of agreement is part of permissible bilateral negotiations.
Inclusion of Uniform Rapid Suspension (URS) and Trademark Dispute Resolution Procedure (PDDRP) in legacy TLD renewals without going through a Policy Development Process (PDP): most of the comments received expressed their objection to the inclusion of the URS to the proposed renewal of .TRAVEL Registry Agreement, claiming that the URS can become a consensus policy only after a full policy development process (PDP) engaged in by the entire ICANN community of stakeholders. These commenters also suggested that imposing URS on a legacy gTLD via the contracting process is an unacceptable staff intervention into the policymaking process. On the other hand, some comments expressed their support of inclusion of the URS in the Renewal Registry Agreement, stating that registries are free to go above and beyond the minimum rights protections and do not require a PDP.
What significant materials did the Board review?
As part of its deliberations, the Board reviewed various materials, including, but not limited to, the following materials and documents:
The proposed .TRAVEL renewal Registry Agreement and its Appendices .
Summary and analysis of public comments [PDF, 473 KB]
IRT Report: https://archive.icann.org/en/topics/new-gtlds/irt-final-report-trademark... [PDF, 299 KB]
STI Report: https://www.icann.org/news/announcement-2-2009-12-17-en
Current .TRAVEL Registry Agreement
Base Registry Agreement – Updated 09 January 2014 [PDF, 651 KB]
GNSO Working Session 21 June 2015 at ICANN53 in Buenos Aires (GDD Update to the GNSO:
What factors has the Board found to be significant?
The Board carefully considered the public comments received for Renewal Registry Agreement, along with the summary and analysis of those comments. The Board also considered the terms agreed to by the Registry Operator as part of the bilateral negotiations with ICANN. While the Board acknowledges the concerns expressed by some community members regarding the inclusion of the URS in the Renewal Registry Agreement, the Board notes that the inclusion of the URS in the Renewal Registry Agreement is based on the bilateral negotiations between ICANN and the Registry Operator, where Registry Operator expressed their interest to renew their registry agreement based on the new gTLD Registry Agreement.
The Board notes that the URS was recommended by the Implementation Recommendation Team (IRT) as a mandatory rights protection mechanism (RPM) for all new gTLDs. The GNSO was asked to provide its view on whether certain proposed rights protection mechanisms (which included the URS) were consistent with the GNSO's proposed policy on the introduction of New gTLDs and were the appropriate and effective option for achieving the GNSO's stated principles and objectives. The STI considered this matter and concluded that "Use of the URS should be a required RPM for all New gTLDs." That is, the GNSO stated that the URS was not inconsistent with any of its existing policy recommendations.
Although the URS was developed and refined through the process described here, including public review and discussion in the GNSO, it has not been adopted as a consensus policy and ICANN has no ability to make it mandatory for any TLDs other than new gTLD applicants who applied during the 2012 New gTLD round.
Accordingly, the Board's approval of the Renewal Registry Agreement is not a move to make the URS mandatory for any legacy TLDs, and it would be inappropriate to do so. In the case of .TRAVEL, inclusion of the URS was developed as part of the proposal in bilateral negotiations between the Registry Operator and ICANN.
Additionally, the Board considered the comments regarding transitioning legacy gTLDs to the new form of the registry agreement. The Board notes that existing registry agreement calls for presumptive renewal of the agreement at its expiration so long as certain requirements are met. The renewal agreement is subject to the negotiation of renewal terms reasonably acceptable to ICANN and the Registry Operator. The renewal terms approved by the Board are the result of the bilateral negotiations called for in the current registry agreement, and transitioning to the new form of the registry agreement would not violate established GNSO policy. As described below, the new form of the registry agreement provides some operational advantages, in addition to benefits to registrants and the Internet community including public interest commitments, requiring the use of registrars under the 2013 RAA, and the ability for ICANN to designate an emergency interim registry operator in the event that emergency thresholds for critical registry services is reached.
Are there positive or negative community impacts?
As part of the renewal process, ICANN conducted a review of Registry Operator's recent performance under the current .TRAVEL Registry Agreement. The Registry Operator was found to have substantially met its contractual requirements.
The Board's approval of the Renewal Registry Agreement also offers positive technical and operational benefits. Pursuant to Renewal Registry Agreement, in the event that any of the emergency thresholds for registry functions is reached, Registry Operator agrees that ICANN may designate an emergency interim registry operator of the registry for the TLD, which would mitigate the risks to the stability and security of the Domain Name System. Also, technical onboarding of the Registry Operator to comply with the provisions in the new gTLD agreement will allow the Registry to use uniform and automated processes, which will facilitate operation of the TLD. The Renewal Registry Agreement also includes safeguards in the form of public interest commitments in Specification 11.
There will also be positive impacts on registrars and registrants. Transition to the new gTLD Registry Agreement will provide consistency across all registries leading to a more predictable environment for end-users and also the fact that the proposed renewal Registry Agreement requires that the Registry Operator uses ICANN accredited registrars that are party to the 2013 Registrar Accreditation Agreement (RAA) only will provide more benefits to registrars and registrants.
Protection of Rights holders: The new gTLD agreement will allow Registry Operator to adopt additional rights protection mechanisms to protect rights holders.
Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, budget); the community; and/or the public?
There is no significant fiscal impact expected if ICANN approves the proposed .TRAVEL renewal Registry Agreement. It should be noted however that as a result of approval of the Renewal Registry Agreement, the projected annual registry fees decrease from $46,000USD to $25,000USD. The nominal fiscal impact is offset by the additional benefits to registrants and the Internet community including public interest commitments, requiring the use of registrars under the 2013 RAA, and the ability for ICANN to designate an emergency interim registry operator in the event that emergency thresholds for critical registry services is reached.
Are there any security, stability or resiliency issues relating to the DNS?
There are no expected security, stability, or resiliency issues related to the DNS if ICANN approves the proposed .TRAVEL renewal Registry Agreement. The proposed renewal Registry Agreement in fact includes terms intended to allow for swifter action in the event of certain threats to the security or stability of the DNS. As part of ICANN's organizational administrative function, ICANN posted the draft renewal Registry Agreement for public comment on 12 May 2015.