6,681
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: + + +
no edit summary
"First, an applicant for a .taxi second level domain has to submit proof of his or her affiliation with the taxi industry to the desired registrar. This process does not involve any formalities on the side of TaxiPay GmbH except an official document, such as a taxi license or a commensurate certificate of registration stating the purpose of the company and aligning it with a strong affiliation to the taxi community."<ref>Application 1-1025-18840</ref>
"First, an applicant for a .taxi second level domain has to submit proof of his or her affiliation with the taxi industry to the desired registrar. This process does not involve any formalities on the side of TaxiPay GmbH except an official document, such as a taxi license or a commensurate certificate of registration stating the purpose of the company and aligning it with a strong affiliation to the taxi community."<ref>Application 1-1025-18840</ref>
==Name Collision Issues==
In October 2013 [[ICANN]] released their final assessment and mitigation plan for the [[Name Collision]] issue that was facing the New gTLD program. On 18 November 2013, ICANN announced the applied-for strings that were eligible for an alternative path towards delegation that would allow applicants to proceed without waiting for further mitigation research and plans to be published. 25 strings, including .taxi, were not eligible for the alternative path, and will have to wait for more plans to be published before continuing towards delegation.<ref>[https://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en Announcement 17 Nov 13, ICANN.org] Retrieved 20 Feb 2014</ref>
==References==
==References==