Before you are eligible to register .travel domains you must first apply for registration ID through an authentication provider ( either your association or the non-association provider, DnB )
The URL provided with take you to their resprctive authentication form.

TTPC Authentication Providers

TTPC Authentication Providers
ABA - American Bus Association http://www.buses.org/home/
ABTA - Association of British Travel Agents http://www.abta.com/
ACTA - Association of Canadian Travel Agents http://www.acta.ca/index_en.htm
AFTA - Australian Federation of Travel Agents http://www.afta.com.au/www/index.cfm?pageid=1
AHA - Australian Hotel Association http://www.aha.org.au/home.html
AH&LA - American Hotel & Lodging Association http://www.ahla.com/
ANVR - Algermeen Nederlands Verbond van Reisondernemingen http://www.anvr.nl/anvr/
ARTA - Association of Retail Travel Agents http://www.artaonline.com/
ASTA - American Society of Travel Agents http://www.astanet.com/
ASTOI - Associazione Tour Operator Italiani http://www.astoi.com/
ATTA - Adventure Travel Trade Association http://www.adventuretravel.biz/
CHA - Caribbean Hotel Association http://www.caribbeanhotels.org/
CLIA - California Lodging Industry Association http://www.clia.org/
ETOA - European Tour Operators Association http://www.etoa.org/
HAC - Hotel Association of Canada http://www.hotelassociation.ca/
IACVB - International Association of Convention & Visitors Bureaus http://www.iacvb.org/iacvb/index.asp
IATA - International Air Transport Association http://www.iata.org/index.htm
IH&RA - International Hotel & Restaurant Association http://www.ih-ra.com/
IMG - International Motor Coach Group http://www.imgcoach.com/
ISTC - International Student Travel Confederation http://www.aboutistc.org/
MATTA - Malaysian Association of Tour and Travel Agents http://www.matta.org.my/mattav2b/index.cfm
NACTA - National Association of Commissioned Travel Agents Inc http://www.nacta.com/
NATAS - National Association of Travel Agents Singapore http://www.natas.org.sg/
NBTA - National Business Travel Association http://www.nbta.org/
NTA - National Tour Association http://www.ntaonline.com/
OSSN - Outside Sales Support Network http://www.ossn.com/
PATA - Pacific Asia Travel Association http://www.pata.org/
TBCSA - Travel Business Council of South Africa http://www.tbcsa.org.za/
TIAC - Tourism Industry Association of Canada http://www.tiac-aitc.ca/
TIANZ - Tourism Industry Association of New Zealand http://www.tiac-aitc.ca/
UFTAA - United Federation of Travel Agents' Association http://www.uftaa.org/en/sommaire.php3
UMA - United Motorcoach Association http://www.uma.org/
USTOA - United States Tours Operators Association http://www.ustoa.com/
WACVB - Western Association of Convention & Visitors Bureaus http://www.wacvb.com/
WTTC - World Travel & Tourism Council http://www.wttc.org/




If your Association is not displayed above or are not a member of any Association but work in travel industry you can apply through a Non-Associated Authentication Provider

D&B - Dun and Bradstreet https://eupdate.dnb.com/requestoptions.html?cmid=EOE100537%20

Who is eligible to register a .travel name?
Any business, organization or individual whose primary activity is within one of eighteen business sectors of the travel industry is eligible to register a name.


What are the eighteen industry sectors?
They are:
Airlines
Attractions/Theme Parks
Bed & Breakfast Houses
Bus/Taxi/Limousine Operators
Camp Facility Operators
Car Rental Companies
Computer Reservation/Travel Technology Provider
Convention & Visitor's Bureaus
Cruise Lines
Ferries
Hotels/Resorts/Casinos
National Tourism Offices
Passenger Rail Lines
Restaurants
Tour Operators
Travel Agents
Travel Media
Travel-Consumer and Market Research Organizations


Can I register any name I want?
No. You can only register a name that is publicly used by, or associated with, your organization. The names that can be registered are:
Incorporation (legal) Name/Partnership Name/Individual Name
Doing Business As; Trade Name; or; Usual Business Name; or Usual Business
Name as used in a URL
Trade Mark
Service Mark
Club or Association Name
Vessel Name
Competition/Event Name
Division Name
Subsidiary Name
Acronym (Acronyms must be only the first letter of the primary words of the name, not including words such as: the (unless the first word of the name), and, as, of, &, or. Contractions or short forms of words , such as “Chas” for “Charles” or “Bros” for “Brothers” are not permitted as acronyms.
What is pre-authentication?
All potential holders of a .travel name must be approved to hold that name by having their eligibility reviewed. That review of eligibility is called “authentication”. .travel is giving members of selected travel associations the chance to have their authentication reviewed by their association and others to have their authentication reviewed by third party authentication providers, prior to registration. Pre-authentication will speed the registration of a name when .travel begins to take name registrations later in 2005. The information on third party authentication providers will be released shortly.
How will .travel know that I’ve been pre-authenticated?
All pre-authentication will be confirmed by .travel. You will be sent a Unique Identifying Number (UIN) by .travel. You will use that number when you register any .travel names in the future. Your UIN is permanent and will not change. It may be revoked if your eligibility changes.


Is my authentication valid forever?
No. Organizations can change. Your organization might merge, be sold or sell assets during the time you hold a .travel. For that reason, you will be required to confirm annually that your authentication information has not changed.
Does pre-authentication let me choose and guarantee a name?
No. Pre-authentication gives .travel the information to determine that you are eligible. At the same time, you will be asked to indicate any names that you currently use other than your legal name. These other names might be a trade name, or a usual business name, and so on. If you list a name other than your legal name you will also have to supply your Authentication Provider with a document that supports identification of that name as one you are eligible to register.


What are the steps in pre-authentication?
There are just four steps: 1. Collect the information you need. 2. Go to the association member site or Tralliance web site and a link will take you to the authentication data form. 3. Fill in the form and click the “submit” button. 4. When your association or the third party authentication provider completes its review and confirms your eligibility you will automatically receive the UIN by email or fax.


What authentication information will I have to supply?
You are required to supply your legal name and your contact information. Optionally, you may supply any names that you use, other than your legal name. These might be trademarks or your usual business name, if it is other than your legal name. If you enter these optional names you will be required to send supporting documents to the association to confirm your use of the name.
You can see an online mockup of authentication data on the Tralliance website.
Just follow the instructions you find on that page.
When will .travel domain names be available for registration?
Tralliance is currently completing contracting with ICANN. When contracting is completed registration will begin shortly thereafter. Tralliance is currently developing the directory and registration technology to test the name registration, data collection and searching processes in order to initiate all services at the planned date, which is the end of the second quarter of 2005.

Registered Name Holder shall: Indemnify to the maximum extent permitted by law, defend and hold harmless Registry Operator, and its directors, officers, employees and agents from and against any and all claims, damages, liabilities, costs and expenses, including reasonable legal fees and expenses, arising out of or relating to the Registered Name Holder’s domain name registration and or use, and this indemnification obligation survive the termination or expiration of the registration agreement; (3.7) Indemnify, defend and hold harmless Registry Services Provider, its subsidiaries and affiliates, and the directors, officers, employees and agents or each of them, from and against any and all claims, damages, liabilities, costs and expenses, including reasonable legal fees and expenses, arising out of or relating to the Registered Name Holder’s domain name registration and or use, and indemnification obligation survive the termination or expiration of the registration agreement; (3.7.1) Acknowledge and agree that notwithstanding anything in this Agreement to the contrary, mTLD Top Level Domain Ltd. (“dotMobi”), the Registry Operator of the .mobi TLD, is and shall be an intended third party beneficiary of this Agreement. As such, the parties to this Agreement acknowledge and agree that the third party beneficiary rights of dotMobi have vested and that dotMobi has relied on its third party beneficiary rights under this Agreement in agreeing to Safenames Ltd being a registrar for the .mobi top-level domain. Additionally, the third party beneficiary rights of dotMobi shall survive any termination or expiration of this Agreement. (3.8.3) Comply with ICANN requirements, standards, policies, procedures, and practices for which Registry Operator has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; (3.8.1) Comply with operational standards, policies, procedures, and practices for the Registry TLD established from time to time by Registry Operator in a non-arbitrary manner as Registry Policies, applicable to all registrars and/or Registered Name Holders, and consistent with the Registry Agreement shall be effective upon thirty days notice by Registry Operator to Registrar; (3.8.2) Consent to the use, copying, distribution, publication, modification and other processing of Registered Name Holder's Personal Data by Registry Operator and its designees and agents in a manner consistent with the purposes specified pursuant to Subsection 2.6 and with relevant mandatory local data protection, laws and privacy; (3.8.4) Submit to proceedings commenced under ICANN's Uniform Domain Name Dispute Resolution Policy ("UDRP"); (3.8.5) Immediately correct and update the registration information for the registered Name during the registration term for the Registered Name; (3.8.6) Acknowledge and agree to be bound by the terms and conditions of the initial launch and general operations of the Registry TLD, including without limitation the Limited Industry Launch, the Sunrise Period, the Land Rush Period, the Sunrise Dispute Resolution Policy, the Premium Name Allocation Process, and the General Registration Period , and further to acknowledge that Registry Operator and the Registry Service Provider has no liability of any kind for any loss or liability resulting from the proceedings and processes relating to the Limited Industry Launch, the Sunrise Period, the Land Rush Period, the Sunrise Dispute Resolution Policy, the Premium Name Allocation Process, and the General Registration Period including, without limitation: (a) the ability or inability of a registrant to obtain a Registered Name during these periods, and (b) the results of any dispute made during the limited industry launch or over a Sunrise Registration. (3.8.7) Acknowledge and agree that the Registry and Registry Services Provider, acting in consent with the Registry, reserves the right to deny, cancel or transfer any registration that it deems necessary, in its discretion (i) to protect the integrity and stability of the registry; (ii) to comply with all applicable laws, government rules or requirements, requests of law enforcement, in compliance with any dispute resolution process; (iii) to avoid any liability, civil or criminal, on the part of the Registry as well as its affiliates, subsidiaries, officers, directors, representatives, employees, and stockholders; (iv) for violations of the terms and conditions herein; or (v) to correct mistakes made by the Registry or any registrar in connection with a domain name registration, and the Registry also reserves the right to freeze a Registered Name during resolution of a dispute. (3.8.8.) Acknowledge and agree that they must comply with the requirements, standards, policies, procedures and practices set forth in the dotMobi Style Guide (www.mtld.mobi) and consent to the monitoring of the website as described in the dotMobi Style Guide monitoring guidelines (www.mtld.mobi) for compliance with the Style Guide. Furthermore, Registrant acknowledges and agrees that this Style Guide is subject to modification by the Registry with any such changes appearing at the previously designated URL, and that Registrant must promptly comply with any such changes in the time allotted. (3.8.9) Acknowledge and agree that Proxy or Proxy Registrations will not be allowed during the Sunrise Period, the Limited Industry Launch and the Premium Name Allocation and Auction Period, and in such an instance will constitute a material breach to this contract. (3.9.1). Sunrise Challenge Policy 1. Purpose. This Sunrise Registration Challenge Policy (the “Policy”) has been adopted by Mobile Top Level Domain, Ltd (“mTLD”) and is incorporated by reference into the Sunrise registration agreement (the “Registration Agreement”) between you (as the “Registrant”) and us (as the “Registrar”). Thus, the Policy applies to all domain names registered during the Sunrise Registration Period, i.e. between Monday, May 22, 2006 and Monday, August 21, 2006, whether or not such names were subsequently transferred. The Policy sets forth the terms and conditions that will apply in the event of a dispute between you and any party other than us or mTLD regarding the compliance of your registration of a .mobi top-level domain name (the “Domain Name”) with the Sunrise Registration Conditions set forth in the Registration Agreement and reproduced in Paragraph 4(c) of this Policy (“Sunrise Registration Conditions”). mTLD may itself also initiate challenges in connection with Sunrise registrations appearing to be made in violation of the Sunrise Registration Conditions (“Registry Challenges”); such Registry Challenges may also be submitted after the conclusion of the Sunrise Challenge Period, which begins Monday August 28, 2006, one week following the conclusion of the Sunrise Registration Period, and ends Friday, December 15, 2006. The footnotes to this Policy are an integral part thereof. Proceedings under Paragraph 4 of this Policy will be conducted pursuant to the Rules for Sunrise Registration Challenge Policy (the “Rules”), which are available online at [www.mtld.mobi]. 2. Registrant Representations. By applying to register a Domain Name in accordance with the Sunrise Registration Conditions, you hereby represent and warrant to us that (a) the statements that you made in your Registration Agreement are complete and accurate; (b) the registration of the Domain Name complies with the Sunrise Registration Conditions; (c) to your knowledge, neither the registration nor the use of the Domain Name will infringe upon or otherwise violate the rights of any third party; (d) you are not registering the Domain Name for an unlawful purpose; and (e) you will not knowingly use the Domain Name in violation of any applicable laws or regulations. It is your responsibility to determine whether your Domain Name registration infringes or violates someone else’s rights and complies with the terms and conditions of the Registration Agreement. mTLD reserves the right to cancel, at any time, a domain name registered in violation of any of the above-mentioned conditions. 3. Cancellations, Transfers, and Changes. We will cancel, transfer or otherwise make changes to a domain name registration that is subject to this Policy under the following circumstances: a. Subject to the provisions of Paragraph 5, our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action; and/or b. Our receipt of an order from a court or arbitral tribunal, in each case of competent jurisdiction, requiring such action; and/or c. Our receipt of a decision requiring such action in any administrative proceeding to which you were a party and which was conducted under this Policy or a later version of this Policy adopted by mTLD. mTLD may also cancel, transfer or otherwise make changes to a domain name registration in accordance with the terms of the Registration Agreement or other legal requirements. 4. Mandatory Administrative Proceeding. This Paragraph sets forth the type of disputes for which you are required to submit to a mandatory administrative proceeding. These proceedings will be administered by the World Intellectual Property Organization Arbitration and Mediation Center (the “Center”). a. Applicable Disputes. You are required to submit to a mandatory administrative proceeding in the event that a third party (the “Challenger”) asserts to the Center, in compliance with the Rules, that: (i) at the time of your registration of the Domain Name, no current (non-expired) trademark or service mark was registered in your name;1 or (ii) the Domain Name is not identical to the textual or word elements of the trademark or service mark registration on which the registration of your Domain Name is based;2 or (iii) the trademark or service mark registration on which the registration of your Domain Name is based is not of national effect;3 or (iv) the trademark or service mark on which the registration of your Domain Name was based was not registered or applied for, prior to July 11, 2005, with the trademark authority with which the mark is registered4. 1 The trademark or service mark registration must be in the name of the Domain Name registrant. A trademark license will not be considered sufficient, nor will a registration in the supplemental register of the United States Patent and Trademark Office. Unregistered trademark or service marks, or other rights in distinctive signs (such as trade names, personal names, geographical indications etc.), do not meet the Sunrise Registration Conditions. 2 Identity will be deemed to exist also where there is a space between the textual or word elements of the mark (e.g., “service mark”) and, in the Domain Name, a hyphen is used or the elements are combined (e.g., service-mark.mobi or servicemark.mobi). Identity will also be deemed to exist when special characters in the trademark or service mark (such as ~ @ # $ % ^ & * ( ) + = < > { } [ ] | \ / ) , spaces, and punctuation (such as : ; “ ‘ , . ?), are, in the Domain Name, eliminated entirely (no space), replaced with hyphens within a domain name or transcribed in a conventionally accepted way. For example, if you own a trademark registration for “Service & Mark” and qualify to register in .mobi, you may apply for servicemark.mobi, service-mark.mobi, or serviceandmark.mobi. If the trademark contains letters which contain additional elements that for technical reasons cannot be reproduced in the domain name, such as ä, é or ñ, the letters concerned must, in the Domain Name, be reproduced without these elements (such as a, e, n), or must be replaced by conventionally accepted spellings (such as ae for ä). In all other respects, the Domain Name must be identical to the textual or word elements of the mark. 3 For instance, European Community trademarks meet the condition of national effect, but United States state trademarks or service marks do not. 4 The trademark or service mark must have been registered in the name of the domain name registrant prior to July 11, 2005. It will also be considered sufficient if the Domain Name registrant had applied for the trademark or service mark before that date, provided that the mark is registered by the time of the Domain Name registration. All challenges under this Policy (except for any Registry Challenges) must be submitted, no later than December 15, 2006 at 23:59 UTC. Proceedings under the Uniform Domain Name Dispute Resolution Policy (UDRP) shall not be brought against a Domain Name, as long as such Domain Name is, or can be, subject to a challenge under this Sunrise

Challenge Policy. b. Challenger’s Compliance with the Sunrise Registration Conditions. A Challenger seeking transfer of the Domain Name is required to demonstrate, as part of the administrative proceeding and as a condition for such transfer, the Challenger’s own compliance with the Sunrise Registration Conditions. c. How to Demonstrate Compliance with the Sunrise Registration Conditions. In order to demonstrate compliance with the Sunrise Registration Conditions, a Party must submit, as further specified in the Rules, an original or a copy, certified as correct by the issuing trademark authority, of a trademark or service mark certificate establishing that: (i) at the time of the registration of the Domain Name, a trademark or service mark was registered in the name of the Party, and was current (non-expired), as evidenced by the date(s) set forth in the certificate itself;5 and (ii) the textual or word elements of the trademark or service mark registration are identical to the Domain Name;6 and (iii) the trademark or service mark registration is of national effect;7 and (iv) the trademark or service mark was registered or applied for, prior to July 11, 2005, with the trademark authority with which the mark is registered8. d. Multiple Challenges. In the event more than one challenge is submitted to the Center regarding the same Domain Name, the Center will process only the first challenge received. Any further challenges will not be processed and no challenger’s fee will be charged by the Center. The Center is under no obligation to communicate concerning any such further challenges. However, if a challenge is terminated without a determination by the Center regarding the Respondent’s and/or the Challenger’s compliance with the Sunrise Registration Conditions, the Center will process the next-filed challenge, provided that this challenge was also filed during the Sunrise Challenge Period. e. Decision. The challenge will be decided upon by the Center as set out in Subparagraphs (i) to (iii) below. The Center’s decision of whether the Sunrise Registration Conditions are met will be based on a prima facie examination of any trademark or service mark certificates submitted, in relation to the information contained in the relevant mTLD Whois database. The Center’s decision is of an administrative nature and shall be final. The Center shall not be required to state reasons for its decision. 5 Reference is made to footnote 1. 6 Reference is made to footnote 2. 7 Reference is made to footnote 3. 8 Reference is made to footnote 4. (i) If the Center finds that you have registered the Domain Name in compliance with the Sunrise Registration Conditions, the Center will dismiss the Challenge. (ii) If the Center is unable to find that you have registered the Domain Name in compliance with the Sunrise Registration Conditions, the Challenge will be granted. If the Challenger has requested transfer, the transfer will be subject to a decision by the Center that the challenge complies with the Sunrise Registration Conditions, failing which Subparagraph (iii) shall apply. (iii) If a prevailing Challenger sought a cancellation, or if neither Party established compliance with the Sunrise Registration Conditions, the Center shall order that the Domain Name be cancelled. f. Fees. In accordance with the Rules, the submission of a challenge under this Policy (subject to any other arrangements that may apply to the submission of Registry Challenges) is subject to the payment of a Challenger’s fee in the amount of USD 750, subject to the provisions of Rules, Paragraph 13. All payments are to be made by credit card. If a challenge is submitted, but the Challenger’s fee is not paid in accordance with the Rules, the challenge will be dismissed. g. Our Involvement in Administrative Proceedings. We do not, and will not, participate in the administration or conduct of any proceeding before the Center under this Policy. In addition, we will not be liable as a result of any decisions rendered by the Center. mTLD reserves the right to bring Registry Challenges, as set forth in Paragraph 1. h. Remedies. The remedies available to a Challenger shall be limited to requiring the cancellation of your Domain Name registration or the transfer of your Domain Name registration to the Challenger. i. Notification. The Center shall notify us and mTLD of any decision made under this Policy with respect to a Domain Name you have registered with us in accordance with the Rules. The outcomes of all administrative proceedings under this Policy shall be published in accordance with the Rules, except as determined otherwise by mTLD with regard to Registry Challenges. j. Availability of Court Proceedings. The mandatory administrative proceeding requirements set forth in Paragraph 4(a) shall not prevent either party from submitting the dispute to a court of competent jurisdiction for independent resolution. Such submission shall not preclude the Center from processing any challenge. 5. Transfers During a Dispute. a. Transfers of a Domain Name to a New Holder. You may not transfer your Domain Name registration that is subject to this Policy to another holder before the end of the Sunrise Challenge Period and until any challenges brought pursuant to this Policy in relation to this Domain Name have been resolved, except that a transfer may be made to the Challenger in a pending administrative proceeding under this Policy (e.g., in the event of a settlement of the dispute), provided that the Center has decided that the challenge complies with the Sunrise Registration Conditions. Any registration pursuant to such transfer will be subject to the Sunrise Registration Conditions. b. Changing Registrars. You may not transfer your Domain Name registration that is subject to this Policy to another registrar before the end of the Sunrise Challenge Period and until any challenges brought pursuant to this Policy in relation to this Domain Name have been resolved. 6. Policy Modifications. mTLD reserves the right to modify this Policy at any time. We will post any revisions of this Policy online at www.mtld.mobi at least seven (7) days prior to its effective date. Unless this Policy has already been invoked by the submission of a challenge to the Center, in which event the version of the Policy in effect at the time it was invoked will apply to you until the challenge has been resolved, all such changes will be binding and apply to all challenges filed on or after the effective date of the modified Policy. In the event that you object to a change in this Policy, your sole remedy is to cancel your Domain Name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel your Domain Name registration.