.餐厅

Q2.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO, and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE) of the applying entity, the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC2.2-1.1 - As of the submission date of the application, the applying entity is a current registry operator or an affiliated entity of a current registry operator with one or more active Registry Agreements (RA). SC2.2-1.2 - The applying entity and/or a QPE will fund the startup and long-term operation of all of the applying entity’s current gTLDs and applied-for gTLD strings. SC2.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.

Answered with a document. Attachments are not published by ICANN.

Q2.3-1 - Provide a document with a list of all of the applying entity’s current gTLDs and a list of all gTLDs for entities affiliated with the applying entity (if applicable).

Answered with a document. Attachments are not published by ICANN.

Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Answered with a document. Attachments are not published by ICANN.

Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Answered with a document. Attachments are not published by ICANN.

Script of String

Chinese (Han)

As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.

true

Applied-for Primary String (U-Label)

餐厅

Applied-for Primary String (Code Points)

U+9910 U+5385

Script of Variant String

Chinese (Han)

Is this variant string for an existing gTLD that is already operated by the applying entity or for a newly applied-for string in the 2026 Round?

Existing TLD

What is the meaning/definition of the variant string?

restaurant

Explain how the primary applied-for and variant strings are considered the same, including the meaning, by the relevant user communities.

The primary string 餐厅 (Simplified Chinese) and variant string 餐廳 (Traditional Chinese) are universally recognized as identical in meaning, pronunciation, and industry reference by all Chinese-speaking user communities (Mainland China, Hong Kong, Macau, Taiwan, and overseas Chinese). They are standard script variants of the same term (referring to “restaurant/catering establishment”), differing only in written form—not in semantic value. This equivalence is rooted in linguistic norms, real-world usage, and legal precedents across Chinese regions. Three Bona-Fide Examples 1. ICANN-Recognized IDN Variant Precedent ICANN’s IDN Variant Framework explicitly classifies Chinese Simplified/Traditional pairs (e.g., 澳门 / 澳門, 中国 / 中國) as semantically identical variantsICANN. The 餐厅 / 餐廳 pair follows the same linguistic rule: both denote “catering/restaurant” and are treated as interchangeable in root zone label generation (RZ-LGR) and user experience. This is a formal industry standard for Chinese IDN gTLDs. 2. Trademark & Legal Precedent in Catering Industry Chinese judicial practice uniformly holds that Simplified/Traditional character pairs are identical for trademark and service identification. For example: • Courts ruled that 小龍坎 (Traditional) and 小龙坎 (Simpl) are identical trademarks for hot pot catering services—no confusion in meaning or source. • In catering disputes, 外婆橋 / 外婆桥 and 全築 / 全筑 are deemed equivalent service identifiers, with 繁简差异 not negating identity. This confirms 餐廳 / 餐厅 are legally and commercially the same to catering users and registrants. 3. Real-World Business & User Usage Global catering enterprises and Chinese-speaking users treat 餐厅 / 餐廳 as interchangeable: • Major chains (e.g., 海底捞 / 海底撈，麦当劳 / 麥當勞) use both forms in branding, menus, and domains—users recognize them as the same business. • In Hong Kong/Taiwan/overseas communities, 餐廳 is the standard term; in Mainland China, 餐厅 is used. Both refer to the same catering service, with zero semantic difference for consumers, businesses, and industry institutions. • Domain systems (e.g., CNNIC) resolve 餐厅。中国 and 餐廳。中國 to the same website, proving user-perceived identity. Conclusion All relevant Chinese user communities recognize 餐厅 and 餐廳 as the same term—only differing in script, not meaning. The three examples (ICANN IDN rules, legal precedents, real-world business usage) conclusively validate this equivalence.

Explain the benefits and the user communities who will benefit from the introduction of the applied-for variant string(s).

1. Why one label is insufficient and two labels are necessary A single label is insufficient because Simplified Chinese and Traditional Chinese are distinct writing systems used in separate major regions with long-standing linguistic, cultural, and usage conventions. • 餐厅 (Simplified) is the standard in mainland China. • 餐廳 (Traditional) is the standard in Hong Kong, Macau, Taiwan, and most overseas Chinese communities. Using only one script would create usability barriers, lower user recognition, and reduce trust among communities accustomed to their native writing system. Two labels are necessary to fully serve all Chinese speaking users equally, respect regional linguistic preferences, and ensure intuitive, culturally appropriate access to the catering industry namespace. 2. User communities served by the primary and variant TLDs Primary TLD: 餐厅 (Simplified Chinese) Serves users in: • Mainland China • Platforms and users primarily using Simplified Chinese • Domestic catering businesses, consumers, tourism platforms, and industry users Variant TLD: 餐廳 (Traditional Chinese) Serves users in: • Hong Kong, Macau, Taiwan • Global overseas Chinese communities • International catering chains, regional users, and businesses operating in Traditional Chinese environments 3. How user community needs are reflected in the IDN tables The IDN tables for the primary 餐厅 and variant 餐廳 TLDs are structurally identical and semantically aligned, reflecting shared user needs across Chinese speaking communities: • Both use the same set of valid characters, registration rules, and eligibility policies. • Both support the same industry purpose (catering and restaurant services). • The only difference is the script form (Simplified vs. Traditional), which directly matches the linguistic needs of each regional user group. This design ensures consistent security, policy, and user experience while accommodating cultural and regional writing preferences. The IDN tables thus reflect both shared core needs and linguistic diversity across the global Chinese user community.

Describe the steps that the applying entity will take to minimize the operational and management complexities of variant gTLDs and variant domain names that impact registrars, resellers and/or registrants.

To minimize operational and management complexities associated with the variant gTLD pair 餐厅 (Simplified) and 餐廳 (Traditional), the applicant will implement a series of unified, consistent, and streamlined administrative and technical measures across both TLDs. These measures reduce burdens for registrars, resellers, and registrants as follows: Unified Registry Platform and Single Point of Operation Both the primary TLD and variant TLD will be operated on the same technical backend platform, with shared systems for domain registration, renewal, modification, suspension, and revocation. Registrars will only need to maintain one set of integration connections and operational workflows, avoiding duplicate configuration or separate system access. Consistent Policies, Rules, and Eligibility Criteria All policies, including registration eligibility, verification standards, naming policies, anti-abuse rules, and dispute resolution mechanisms, will be fully identical between 餐厅 and 餐廳. No separate policy documents or review processes will apply to the variant string, ensuring registrars and registrants face no confusion or additional compliance burden. Unified WHOIS/RDAP Service and Data Structure Registration data output, query format, and RDAP/WHOIS display will follow a unified structure for both TLDs. Consistent data fields and output formats simplify system integration for registrars, resellers, and third-party service providers. Synchronized Launch, Sunrise, and Rights Protection Mechanisms Sunrise periods, trademark claims periods, registration phases, and rights protection mechanisms will run in parallel for both TLDs. This synchronization eliminates scheduling complexity and allows registrars to prepare and promote only one launch plan. Unified Pricing, Billing, and Registrar Settlement Pricing structure, billing cycles, discount policies, and financial settlement procedures will be identical for both TLDs. Registrars will manage only one set of price lists and financial processes, rather than separate arrangements for each string. Shared Customer Support and Service Framework A unified support system will handle inquiries, troubleshooting, and compliance matters for both TLDs. Registrants and registrars will receive consistent guidance and services, with no need to distinguish between the primary and variant string for assistance. Simplified Reseller Management and Channel Tools Reseller management systems, API interfaces, control panels, and promotional materials will be designed to support both TLDs simultaneously. Channel partners will use a single set of tools and materials, reducing operational workload and training costs. Unified Reporting, Compliance, and ICANN Reporting All regulatory reports, compliance data, statistics, and ICANN-mandated submissions will be compiled on a combined basis. The applicant will avoid separate reporting for each variant, reducing internal and external administrative overhead. Through the above measures, the applicant ensures that the operation of the variant TLD 餐廳 introduces minimal additional complexity. The unified architecture, policies, and processes protect registrars, resellers, and registrants from duplication, inconsistency, or unnecessary operational burden. These commitments will be formally incorporated into the Registry Agreement to ensure long-term stable and simplified management.

This applied-for TLD is not a “generic string” using the definition of "generic string" in Section 3(d) of Specification 11 of the Base RA (as described in Question 121).

true

Applied-for Variant(s)

xn--3zto70k

Variant String (U-Label)

餐廳

Variant String (Code Points)

U+9910 U+5EF3

By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

true

By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

true