gTLD	Full Legal Name	E-mail suffix	Detail
.SFR	Societe Francaise du Radiotelephone - SFR	sfr.com	View

SFR SA intends to organize the registry operation for .SFR in such a manner that it will minimize the likelihood of having multiple applications or registration requests for a particular domain name.

According to SFR SA, this can be achieved in any of the following ways, which likely needs to be further refined following ICANN’s award and delegation of the .SFR gTLD to SFR SA:

i. SFR is the Applicant’s distinctive and most recognized household brand;

ii. From the Applicant’s perspective, .SFR may 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 gTLDs (or even ccTLDs) has disappeared, the .SFR top-level domain is currently intended to be unambiguous as regards:

• the identity of SFR SA as the Registry Operator;
• the source of the content and services offered under the .SFR gTLD;
• the affiliation between the Registry Operator and the gTLD; and
• in term, and at the discretion of SFR SA, the affiliation between the Registry Operator and any third party that is authorized by SFR SA to register and⁄or use one or more domain name registrations in the .SFR gTLD.

iii. As mentioned in the vision and mission statement above, the key reasons why the Applicant is applying for .SFR include, but are not limited to:

1. Securing and protecting the SFR brand as a generic top-level domain;

SFR SA holds various registered trademarks for SFR. The main reason for which SFR SA submits this application for the .SFR gTLD is that it wants to prevent third parties from securing the gTLD that is identical to SFR SA’s highly distinctive and reputable brand.

2. Marketing and branding: reflecting the Applicant’s key brand SFR at the top-level of the DNS’ hierarchy;

3. Safety and security; and

4. Implementing measures – in the near or distant future – to mitigate counterfeiting and piracy.

iv. The Applicant intends to implement the following policies and procedures with respect to the registration of domain names in the .SFR top-level domain:

(i) reservation and registration of domain names in the name of SFR SA. It is likely that this will be the scenario that SFR SA will put in place during the first months or even years of operation of the .SFR gTLD.

These names may include, but are not limited to:
a. descriptive names, referring to the actual day-to-day business activities of the Applicant or its Affiliates;
b. descriptive names, referring to the internal departments of the Applicant;
c. descriptive names, referring to the subsidiaries, affiliates and⁄or joint ventures of the Applicant; and
d. various trademarks or variants thereof registered and⁄or used by SFR;
e. potentially also names relating to other stakeholders of SFR SA, to be determined by SFR SA following ICANN’s award and delegation of the .SFR gTLD to SFR SA.

(ii) launch of the TLD: if and when implemented by the Registry Operator, this is likely going to be a gradual process, whereby selected third parties that meet certain criteria, which SFR SA will be entitled to set at its own discretion, may register domain names in the .SFR gTLD. These processes may include the following:

a. Sunrise: allow physical persons, organizations and entities that meet the eligibility requirements determined by SFR SA at that point in time to choose and, where allowed by SFR SA, to register the domain names that are identical to their trademarks; and

b. Land rush and 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.

Depending on the terms and conditions in force at the time of launch of the gTLD, 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 Registry Operator of the gTLD (i.e., SFR SA). In any case, SFR SA reserves the right to impose additional and other restrictions from time to time at its sole discretion.

v. Given the fact that the Applicant is a company that is established in France, it is subject to national privacy and data protection rules and practices. In particular, given the fact that the French and European data protection authorities have issued strict guidelines, SFR SA will at all times be obliged to carefully consider and, where applicable, implement these policies, and this prior to and during the operation of the .SFR gTLD.

vi. The Applicant is a corporation that has been established in and has been trading under the SFR brand since 1988).

At this stage, SFR SA has not developed concrete and tangible plans in order to move its online activities from SFR.fr and many other active domain names used by SFR SA and its subsidiaries, affiliates and joint ventures. However, the Applicant has different ways to make existing and future customers, visitors and stakeholders aware of the (gradual) development of a new online environment under the .SFR TLD, including but not limited to:

a. Direct and indirect marketing and branding initiatives;
b. Brochures and advertisements in newspapers, magazines, etc.;
c. Internet advertising campaigns, including paid search, pay-per-click advertising, etc.;
d. Having Internet traffic to the SFR.fr or other domain names resolving into domain names registered in the .SFR gTLD, which builds awareness with Internet users that the .SFR gTLD exists; and
e. Email marketing campaigns.

gTLD	Full Legal Name	E-mail suffix	Detail
.booking	Booking.com B.V.	markmonitor.com	View

Booking.com intends to organize the registry operation for the .booking gTLD in such a manner that it will minimize the likelihood of having multiple applications or registration requests for a particular domain name.

According to the Applicant, Booking.com, this can be achieved in any of the following ways, which likely needs to be further refined following ICANN’s award and delegation of the .booking gTLD to Booking.com:

i. From the Applicant’s perspective, .booking may 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 .booking top-level domain is currently intended to be unambiguous as regards:

* the identity of the Booking.com as the Registry Operator;
* the source of the content and services offered under the .booking gTLD;
* the affiliation between the Registry Operator and the . Booking gTLD; and
* in term, and at the discretion of Booking.com, the affiliation between the Registry Operator and any third party that is authorized by the Booking.com to register and⁄or use one or more domain name registrations in the .booking gTLD.

ii. As mentioned in the vision and mission statement above, the key reasons why Applicant is applying for .booking include but are not limited to:

1. Securing and protecting the BOOKING.COM brand as a generic top-level domain.

Booking.com holds various registered trademarks for BOOKING.COM. The main reason for which Booking.com submits this application for the .booking gTLD is that it wants to prevent third parties from securing a gTLD that is identical or confusingly similar to Booking.com’s highly distinctive and reputable brand.

2. Marketing and branding: reflect the most distinctive element out of Applicant’s key brand (“BOOKING”) at the top-level of the DNS’ hierarchy;

3. Safety and security; and

4. Implement measures – in the near or distant future – to mitigate counterfeiting and piracy.

iii. The Applicant intends to implement the following policies and procedures with respect to the registration of domain names in the .booking top-level domain:

(i) reservation and registration of domain names in the name of Booking.com. It is likely that this will be the scenario that Booking.com will put in place during the first months or even years of operation of the .booking gTLD.

These names may include, but are not limited to:
a. descriptive names, referring to the actual day-to-day business activities of the Applicant;
b. descriptive names, referring to the internal departments of the Applicant;
c. descriptive names, referring to the subsidiaries, business affiliates and⁄or partners of the Applicant;
d. potentially also names relating to other stakeholders of Booking.com, to be determined by Booking.com following ICANN’s award and delegation of the .booking gTLD to Booking.com.

(ii) launch of the TLD: if and when implemented by the Registry Operator, this is likely going to be a gradual process, whereby selected third parties that meet certain criteria, which Booking.com will be entitled to set at its own discretion, may register domain names in the .booking gTLD. These processes may include the following:

a. Sunrise: allow physical persons, organizations and entities that meet the eligibility requirements determined by Booking.com at that point in time to choose and, where allowed by Booking.com, to register the domain names that are identical to their trademarks;

b. Land rush and 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.

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 Registry Operator of the TLD (i.e., Booking.com). In any case, Booking.com reserves the right to impose additional and other restrictions from time to time at its sole discretion. These restrictions will be mainly inspired by the following elements and factors:

a. protecting and safeguarding the Applicant’s brand and reputation and

b.the Applicants plan to provide users of the .booking gTLD with a safe and secure experience.

iv. Given the fact that the Applicant is a company that is established in the Netherlands, it is subject to both European and national privacy and data protection rules and practices. In particular, given the fact that the European and Dutch data protection authorities have issued strict guidelines, Booking.com will at all times be obliged to carefully consider and, where applicable, implement these policies, and this prior to and during the operation of the .booking gTLD.

v. As indicated above, BOOKING.COM is Applicant’s most recognized brand, having a global exposure, and a truly international clientele. The Applicant is a corporation that has been established in 1996 and has been trading under the BOOKING.COM brand since 2006.

At this stage, Booking.com has not developed concrete and tangible plans in order to move its online activities from its BOOKING.COM and many other active domain names used by Booking.com and its subsidiaries and affiliates. However, the Applicant has different ways in order to make existing and future customers, visitors and other stakeholders aware of the (gradual) development of a new online environment under the .booking TLD, including but not limited to:

a. Direct and indirect marketing and branding initiatives;
b. By way of brochures ;
c. Internet advertising campaigns, including paid search, pay-per-click advertising, etc.;
d. Having Internet traffic to the BOOKING.COM or other domain names resolving into domain names registered in the .booking TLD, which builds awareness with Internet users that the .booking gTLD exists;
e. Email marketing campaigns.