Thu, Aug 21, 2025

.飞利浦 New gTLD Application

Click to view Chinese translation articles.

-----------------------------------

New gTLD Application Submitted to ICANN by: Koninklijke Philips N.V.

 

Application Downloaded On: 05 Oct 2014

 

String: 飞利浦

 

Application ID: 1-1748-14964

 

Applicant Information

 

  1. Full legal name

Koninklijke Philips N.V.

 

  1. Address of the principal place of business

High Tech Campus 5 Eindhoven - 5656AE NL

 

  1. Phone number

+31 40 274 05 52

 

  1. Fax number

+31 40 274 34 89

 

  1. If applicable, website or URL

http://www.philips.com

 

Primary Contact

 

6(a). Name

Ingrid Baele

 

6(b). Title

Vice President Philips Intellectual Property & Standards

 

6(c). Address

 

6(d). Phone Number

+31 40 274 05 52

 

6(e). Fax Number

+31 40 274 34 89

 

6(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Secondary Contact

 

7(a). Name

Wiel Deguelle

 

7(b). Title

Process Manager

 

7(c). Address

 

7(d). Phone Number

+31 622 47 03 30

 

7(e). Fax Number

 

7(f). Email Address

This email address is being protected from spambots. You need JavaScript enabled to view it.

 

Proof of Legal Establishment

 

8(a). Legal form of the Applicant

Naamloze Vennootschap (Public Limited Liability Company)

 

8(b). State the specific national or other jurisdiction that defines the type of entity identified in 8(a).

Laws of The Netherlands, Articles 64 to 174a of Book 2 of the Dutch Civil Code (‘Burgerlijk Wetboek’), Title 4: Naamloze vennootschappen.    http://wetten.overheid.nl/BWBR0003045/Boek2/Titel4/geldigheidsdatum_09-03-2012

 

8(c). Attach evidence of the applicant's establishment.

Attachments are not displayed on this form.

 

9(a). If applying company is publicly traded, provide the exchange and symbol.

New_York_Stock_Exchange / PHG

 

9(b). If the applying entity is a subsidiary, provide the parent company.

 

9(c). If the applying entity is a joint venture, list all joint venture partners.

 

Applicant Background

 

11(a). Name(s) and position(s) of all directors

Name

Position

Francois Adrianus van Houten President and Chief Executive Officer

Pieter Age Johannes Nota Executive Vice President and Chief Executive Officer Consumer Lifestyle

Ron Herawan Wirahadiraksa Executive Vice President and Chief Financial Officer

Stephen Henry Rusckowski Executive Vice President and Chief Executive Officer Healthcare

 

11(b). Name(s) and position(s) of all officers and partners

Name

Position

Eric Paul Coutinho Executive Vice President and Chief Legal Officer

Francois Adrianus van Houten President and Chief Executive Officer

Ron Herawan Wirahadiraksa Executive Vice President and Chief Financial Officer

 

11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares

 

11(d). For an applying entity that does not have directors, officers, partners, or shareholders: Name(s) and position(s) of all individuals having legal or executive responsibility

 

Applied-for gTLD string

 

  1. Provide the applied-for gTLD string. If an IDN, provide the U-label.

飞利浦

 

14A. If applying for an IDN, provide the A-label (beginning with "xn--").

 

xn--kcrx77d1x4a

 

14B. If an IDN, provide the meaning, or restatement of the string in English, that is, a description of the literal meaning of the string in the opinion of the applicant.

 

Philips

 

14C1. If an IDN, provide the language of the label (in English).

 

Chinese

 

14C2. If an IDN, provide the language of the label (as referenced by ISO-639-1).

 

ZH

 

14D1. If an IDN, provide the script of the label (in English).

 

Han

 

14D2. If an IDN, provide the script of the label (as referenced by ISO 15924).

 

Hani

 

14E. If an IDN, list all code points contained in the U-label according to Unicode form.

 

U+98DE U+5229 U+6D66

 

15A. If an IDN, upload IDN tables for the proposed registry.  An IDN table must include:

the applied-for gTLD string relevant to the tables,

the script or language designator (as defined in BCP 47),

table version number,

effective date (DD Month YYYY), and

contact name, email address, and phone number.

Submission of IDN tables in a standards-based format is encouraged.

 

 

15B. Describe the process used for development of the IDN tables submitted, including consultations and sources used.

 

The table for the applied for TLD is based on the .ASIA ZH IDN Language Table and IDN related issues for this TLD have been developed with assistance from DotAsia Organisation.

 

The language table is developed for the implementation of Chinese IDN registrations at a gTLD in coordination with the CDNC (Chinese Domain Name Consortium), based on the CDNC IDN Language tables from CNNIC (zh-CN: http:⁄⁄www.iana.org⁄domains⁄idn-tables⁄tables⁄cn_zh-cn_4.0.html) and TWNIC (zh-TW: http:⁄⁄www.iana.org⁄domains⁄idn-tables⁄tables⁄tw_zh-tw_4.0.1.html) respectively.

 

The Registry understands the importance of maintaining the integrity of Chinese IDN registrations through appropriate implementation of character variants for Simplified Chinese (SC) and Traditional Chinese (TC). Unlike in the case of ccTLDs (e.g. for .CN or .TW) where one form of the Chinese characters is predominantly used, a gTLD is inherently global and requires the consideration of an environment where some of the users will be using SC (e.g. in Mainland China, Singapore, etc.), while others may be using TC (e.g. in Hong Kong, Macau, Taipei, etc.). Therefore, the DotAsia Chinese IDN Language Table implementation combines the 2 zh-CN and zh-TW tables into an integrated table for “ZH”. More specifically, the table integrates the 2 Preferred Variant Columns from: 1. The zh-CN Preferred Variant column --Preferred SC, referenced as (86); and 2. The zh-TW Preferred Variant column --Preferred TC, referenced as (886); into one column.

 

The table is compliant with the RFC3743-defined format, and is in compliance with CDNC policies, and the ICANN Guidelines for IDN registration and for publication in the IANA Repository of IDN Practices.

 

15C. List any variants to the applied-for gTLD string according to the relevant IDN tables.

 

In accordance with the submitted table in 15(a), there is one preferred variant for the applied for gTLD string.

 

U-Label: 飛利浦

A-Label:    xn--kcrx77dsx4a

Code Points: U+98DB U+5229 U+6D66

Language:    Chinese

ISO639-1:    ZH

Script:        Han

ISO15924:    Hani

 

We respectfully request that TLD strings matching the preferred variant above are considered in contention with the application for this TLD.

The application for this TLD is submitted alongside another application for the .philips TLD, a restatement of this TLD in English. We respectfully request that these two applications are not considered to be in contention.

 

  1. Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string. If such issues are known, describe steps that will be taken to mitigate these issues in software and other applications.

 

A number of operational and rendering issues may arise with the delegation, and subsequent operation and use of a new TLD. Some of these issues may be experienced just by the users of one or two particular TLDs, due to the nature or composition of the string itself; whereas other issues (such as software support) may be experienced across all new TLDs.

 

Evaluation of the potential operational and rendering issues for this TLD was delegated to ARI. ARI is experienced with:

– The operational issues of operating TLDs.

– TLDs that offer registrations at the third level (eg .com.au, .net.au) and below.

– The rendering and operational issues surrounding the introduction of IDNs.

 

ARI has executed a suite of tests to evaluate any issues arising from the use of the TLD string. ARI configured a test environment that consisted of DNS software, web server software, and an email server configured for sample domains in this TLD. Where possible, ARI attempted to test many equivalent applications, however the number of and different versions of applications means that testing was limited to the most common environments.

 

The tests executed by ARI indicate that this TLD is subject to the same issues already experienced by TLDs in the root, which are neither new nor unique. A summary of the common issues is provided below:

– Some applications make assumptions about known valid TLDs and fail to recognize new TLDs.

– Some Non-IDN aware applications require the user to provide input in A-labels.

– Some IDN aware applications present the user with the domain name using A-labels instead of U-labels.

– Some IDN aware applications fail to render IRIs in a manner consistent with user expectations.

 

To mitigate these issues, ARI will work with us to ensure that maintainers of applications are made aware of the delegation and operation of this TLD. When relevant, we will refer the maintainers to the verification code produced by ICANN in the area for Universal Acceptance of All Top Level Domains such that operational issues can be mitigated for other TLDs.

 

ARI and us will work with maintainers of applications to provide subject matter knowledge where required, and provide directions to the tools provided by third parties such as the International Components for Unicode project and other groups, that can assist the application maintainer in adding the required support. User education may be required enabling users to configure their applications for correct functioning of this TLD. An informational section on the TLD website will be considered to address questions raised by the Internet community.

 

The steps ARI will take to mitigate these issues are more than adequate. Thus, we do not believe this TLD raises stability concerns and there is no reason that it should be denied on an operational and rendering issues bases.

 

  1. OPTIONAL.

Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).

 

Not provided

 

18A. Describe the mission/purpose of your proposed gTLD.

 

According to the Applicant, the purpose of the applied-for TLD is manifold, as will be further explained below:

  1. Reflect and operate the Chinese version of the Applicant’s key and most distinctive brand (“飞利浦”) at the top level of the DNS hierarchy;
  2. Provide stakeholders of the Applicant and its subsidiaries, including but not limited to their respective suppliers, customers, sponsorships, partners and their respective directors, officers, employees, with a recognizable and trusted identifier on the Internet;
  3. Provide such stakeholders with a secure and safe Internet environment that is mainly or even fully under the control of the Applicant and its subcontractors;
  4. Provide selected stakeholders in PHILIPS brands with the opportunity to create a secure and safe Internet environment that is mainly or even fully under control of the Applicant and⁄or such stakeholders;

 

18B. How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

 

  1. PHILIPS is the Applicant’s most recognized brand, having international exposure. The Applicant is one of the world’s largest diversified companies. In China, the Applicant is using飞利浦as its trademark. The Group has one of the largest international networks with a presence in more than 100 countries, and counts with more than 115,000 employees. The Applicant has key positions in its three core businesses: Healthcare, Lighting and Consumer Lifestyle. The Applicant’s Group is present in geographically diverse markets, and its operations are spread all over the world. The proposed gTLD aims at consolidating the reputation of the Applicant’s brand in China;
  2. From the Applicant’s perspective, .飞利浦will bring a high degree of recognition and specialization to the currently existing name space. Where in most cases the specific connotation that has been initially given to the gTLDs (or even ccTLDs) has disappeared, the .飞利浦top-level domain will be unambiguous as regards the identity of the Registry Operator, the source of the content and services offered under the .飞利浦and⁄or the affiliation between the Registry Operator and the TLD. Furthermore, the飞利浦 TLD can serve as powerful tools for broadening the Internetʹs capacity and accessibility and may help develop awareness in China of distinguishing conterfeit from the genuine products and services from the Applicant;
  3. As mentioned in the vision ⁄ mission statement before, some of the key reasons why Applicant is applying for .飞利浦 are:
  4. Marketing and branding: reflect the Applicant’s key brand飞利浦at the top-level of the DNS’ hierarchy,
  5. Safety and security, given the fact that the TLD and most if not all of the domain names registered therein will be completely or at least partially under the control of the Registry Operator;
  6. Affiliation between the core飞利浦brand and the hundreds of product and service brands registered and⁄or used by PHILIPS and⁄or its subsidiaries in their day-to-day business;
  7. Affiliation between the core飞利浦brand and stakeholders in different profit and non-profit sectors;
  8. The Applicant intends to implement the following policies and procedures with respect to the registration of domain names in the .飞利浦 top-level domain to include but not limited to:
  9. Reservation of domain names in the name of the Applicant. These names include:

 

  1. a) descriptive names, referring to the actual day-to-day business activities of the Applicant and⁄or its subsidiaries;
  2. b) descriptive names, referring to the internal departments of the Applicant;
  3. c) descriptive names, referring to the subsidiaries of the Applicant;
  4. d) product and service brands promoted by the Applicant and⁄or its subsidiaries now and in the future;
  5. e)

 

  1. Launch of the TLD:

 

  1. a) Sunrise: allow physical persons, organizations and entities that meet the eligibility requirements in force at that point in time to choose the domain names that are identical to their trademarks;
  2. b) General availability: other available domain names may be registered by physical persons, organizations and entities that meet the eligibility requirements in force at that point in time to choose the domain names in accordance with the applicable terms and conditions.
  3. c) Depending on the terms and conditions in force at the time of launch of the TLD, these domain names may or may not be registered in the name of the applicant for the domain name or in the name of the Applicant for the TLD (飞利浦). In any case, the Applicant reserves the right to impose additional and other restrictions from time to time at its sole discretion;

 

  1. Given the fact that the Applicant is a company that is established in the Netherlands, it is subject to both national and European privacy and data protection rules and practices, with which the Applicant will comply.

The Applicant’s Group was founded in 1891 by Gerard Philips and his father Frederik as a family business. Philips & Co. started in a modest factory building in Eindhoven (Netherlands) with the production of carbon-filament lamps and other electro-technical products. The Applicant has been trading under the PHILIPS brand ever since, and later under the PHILIPS domain name (philips.com) and 飞利浦 brand. Since its establishment, the Applicant has become a major player at international level, with a worldwide reputation. In 2004, it was ranked by Dow Jones as No. 1 for sustainability in the cyclical goods market for the second year in a row. Therefore, the Applicant has different ways in order to make existing and future clients, visitors and stakeholders aware of the (gradual) move from the Group’s philips.cn domain name to the .飞利浦 TLD, including but not limited to:

  1. Internet advertising campaigns;
  2. having Internet traffic to its key domain names resolving into domain names registered in the .飞利浦 TLD;
  3. email marketing campaigns; etc.

 

18C. What operating rules will you adopt to eliminate or minimize social costs (e.g., time or financial resource costs, as well as various types of consumer vulnerabilities)? What other steps will you take to minimize negative consequences/costs imposed upon consumers?

 

  1. The Applicant will organize the registry operation for the .飞利浦 in such a manner that it will minimize the likelihood of having multiple applications for a particular domain name. This can be achieved in one of the following ways:
  2. Given the fact that, at least prior to the launch of the .飞利浦 top-level domain, the Applicant ⁄ Registry Operator will reserve, delegate and use a large number of domain names that are directly or indirectly relevant to Applicant’s business in its own name. Since quite a number of these domain names will be of a descriptive nature, the chances for qualifying ⁄ eligible applicants ⁄ registrants to register such domain names after the launch will be limited;
  3. The Registry Operator will release available domain names post launch in a highly controlled manner, which also reduces the likelihood that two or more applicants qualify for the registration of the same domain name in the .飞利浦 top-level domain;
  4. As a method of last resort, and subject to the actual domain name registration policy adopted by the Registry Operator and in force at the time of registration, domain names will be allocated on a first-come, first-served basis.

 

  1. The Applicant intends to make the .飞利浦 top-level domain available to qualifying domain name registrants at no cost to them; The Applicant ⁄ Registry Operator may, at its discretion charge a fee for the registration of domain names under the .飞利浦 TLD. Such fee and domain name registration may be part of a larger package of services offered by the Applicant or its subsidiaries.

 

The Applicant ⁄ Registry Operator may at its discretion make contractual commitments to increase or decrease the fees for the registration of domain names under the .飞利浦 TLD.