.BNL New gTLD Application

Click to view Chinese translation articles.

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

New gTLD Application Submitted to ICANN by: Banca Nazionale del Lavoro

String: BNL

Originally Posted: 13 June 2012

Application ID: 1-1257-44806

 

Applicant Information

 

  1. Full legal name

Banca Nazionale del Lavoro

 

  1. Address of the principal place of business

Via V.Veneto,119

Roma  00187

IT

 

  1. Phone number

+39 06 47021

 

  1. Fax number

+39 06 470 20466

 

  1. If applicable, website or URL

http:⁄⁄www.bnl.it

 

Primary Contact

 

6(a). Name

Mr. Luigi Maccallini

 

6(b). Title

Head Communication Retail

 

6(c). Address

 

6(d). Phone Number

+393351880184

 

6(e). Fax Number

+39 06 470 20466

 

6(f). Email Address

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

 

Secondary Contact

 

7(a). Name

Mr. Antonio Di Leva

 

7(b). Title

Direzione Comunicazione

 

7(c). Address

 

7(d). Phone Number

+39 06 470 20419

 

7(e). Fax Number

+39 06 470 20466

 

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

corporation (società per azioni)

 

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

Italy

 

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.

 

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

BNP PARIBAS GROUP

 

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

Antoine Sire Head of Communication BNP Paribas Group

Bernard Lemée Secretary of board of directors

Fabio Gallia CEO and General Manager BNL

François Villeroy De Galhau Administrator

Jean Clamon Managing Director Compliance and Internal control coordination

Jean-Laurent Bonnafé CEO BNP PARIBAS GROUP

Jean-Paul Sabet Head of region Turkey

Luigi Abete Chairman of BNL SpA

Mario Girotti Administrator

Paolo Mazzotto Administrator

Philippe Blavier Administrator

Pierluigi Stefanini Administrator

Pierpaolo Cotone Segr.Cda e Dir.Segr.Org.Statutari

Roger Abravanel Compensation committee coordinator

Sergio Erede Vice President of BNL SpA

Stefano Micossi Chairman of CIR SpA

 

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

Adolfo Pellegrino Direttore DPPO

Angelo Novati CFO

Anna Boccaccio RESPONSABILE SERVIZIO RELAZIONI ISTITUZIONALI

Antonio Marino Head of BNL Real Estate Department

Fabio Gallia CEO

Francesco Chiurco RESPONSABILE SERV.MEDIA RELATIONS

Gabriella Serravalle DIRETTORE PAC

Gianfilippo Pandolfini Head of Human Resources

Giovanni Ajassa Responsabile Servizio Studi

Giuseppe Crescenti Direttore Direzione Compliance

Ilaria Baronti Chief Audit Executive

Lucia Leva Direttore Comunicazione

Luigi Abete Chairman of BNL SpA

Marco Tarantola Responsabile Divisione Retail e Private

Massimo Romagnoli Co-Head Direzione IT

Niccolò Pandolfini Direttore Investment Solutions Italia

Nicola DʹAnselmo HEAD OF CORPORATE AND INVESTMENT BANKING ITALY

Paolo Alberto De Angelis Direttore Corporate

Paolo DʹAmico Responsabile Direzione  Legale

Paul Thysens Direttore IT

Pierfrancesco Latini Direttore Rischi

Pierpaolo Cotone Segr.Cda e Dir.Segr.Org.Statutari

Roberto Fredella RESPONSABILE KEY CLIENTS GROUP

 

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

BNP PARIBAS Group Not Applicable

 

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.

BNL

 

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

 

14(b). 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.

 

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

 

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

 

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

 

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

 

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

 

15(a). If an IDN, Attach IDN Tables for the proposed registry.

Attachments are not displayed on this form.

 

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

 

15(c). List any variant strings to the applied-for gTLD string according to the relevant IDN tables.

 

  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.

To the Applicant’s knowledge, there are no operational or rendering problems concerning the applied-for gTLD string.

 

Hence, the Applicant anticipates the introduction of this TLD without operational or rendering problems. Furthermore, based on a decade of experience launching and operating new TLDs, Afilias, the back-end provider of registry services for this TLD, is confident the launch and operation of this TLD presents no known challenges. The rationale for this opinion includes:

- The string is not complex and is represented in standard ASCII characters and follows relevant technical, operational and policy standards;

 - The string length is within lengths currently supported in the root and by ubiquitous Internet programs such as web browsers and mail applications;

 - There are no new standards required for the introduction of this TLD;

 - No onerous requirements are being made on registrars, registrants or Internet users, and;

 - The existing secure, stable and reliable Afilias SRS, DNS, WHOIS and supporting systems and staff are amply provisioned and prepared to meet the needs of this TLD.

 

 

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

 

Mission/Purpose

 

18(a). Describe the mission/purpose of your proposed gTLD.

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

  1. Reflect and operate Applicant’s key and most distinctive brand (“BNL”) at the top level of the DNS’ hierarchy;
  2. Provide stakeholders of the Applicant, including subsidiaries, and their respective suppliers, customers, sponsorships, 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 BNL 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;

 

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

  1. BNL is the Applicant’s most recognized brand. The Applicant was founded in 1913. Since 2006, the Applicant is part of the BNP Paribas Group, one of the best rated banks in the world (Rated AA- by Standard & Poorʹs) and having one of the largest international networks with operations in 80 countries and counts with nearly 200,000 employees. The proposed gTLD aims at consolidating the reputation of the Applicant’s brand;
  2. From the Applicant’s perspective, .BNL 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 .BNL top-level domain will be unambiguous as regards the identity of the Registry Operator, the source of the content and services offered under the .BNL and⁄or the affiliation between the Registry Operator and the TLD;
  3. As mentioned in the vision ⁄ mission statement before, some of the key reasons why Applicant is applying for ..BNL are:
  4. Marketing and branding: reflect the Applicant’s key brand BNL 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 BNL brand and the hundreds of product and service brands registered and⁄or used by BNL and⁄or its subsidiaries in their day-to-day business;
  7. The Applicant intends to implement the following policies and procedures with respect to the registration of domain names in the .BNL top-level domain to include but not limited to:
  8. 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 or the Applicant, joint ventures and⁄or other forms of entities linked to the Applicant;
  4. d) product and service brands promoted by the Applicant and⁄or its subsidiaries now and in the future;
  5. e) any denomination, subject to the respect of the legal conditions applicable, in order to facilitate the Applicant’s communication and in particular the proximity with its customers;
  6. f) any denomination, subject to the respect of the legal conditions applicable, in order to facilitate the applicant business and in particular the proximity with the customers.
  7. g) reserved names according to specification 5 of the new gTLD Registry Agreement
  8. h) geographic names according to specification 5 of the new gTLD Registry Agreement
  9. i)

 

  1. Launch of the TLD:

 

  1. a) Prior to Sunrise⁄ TLD launch: the registry operator will populate a list of reserved names and will reserve the right to register domain names during the pre launch phase. The list will be made available to sponsoring registrars and potential eligible registrants as an additional procedures to minimize any abusive registrations and other activities that would have a negative impact on Internet users
  2. b) Prior to general availability: The registry operator will ensure a Trademark Claims service during the start-up phase as provided in the registry agreement. These mechanism will be supported by the established Trademark Clearinghouse as indicated by ICANN. The Trademark Claims service provides notice to potential registrants of existing trademark rights, as well as notice to rightsholders of relevant names registered. Registry operators may decide to continue offering the Trademark Claims service after the relevant start-up phases The registry operator will also implement safeguards against allowing unqualified registrations in accordance to, the registry’s eligibility restrictions or policies
  3. c) 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;
  4. d) 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.
  5. e) 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 (BNL). 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 Italy, it is subject to both national and European privacy and data protection rules and practices.
  2.               As an additional data privacy procedure, the registry operator do not plan on selling bulk WHOIS data or contact data in any way. The registry operator will not allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations. The registry operator do not plan on selling DNS query data in a way that is personally identifiable. The registry operator reserve the rights to use registration data in the aggregate for marketing purposes.
  3.             In order to prevent any abusive mining or harvesting of personal data, the registry operator will enforce adequate WHOIS service and access to contact data, such as but not limited to, limit in search returns. WhoIs protection services information can be found in question 26
  4. The Applicant is a known financial institution that has been created in 1913. Since then, the Applicant has been trading under the BNL brand and later on also under the domain name (bnl.it). Since its establishment, the Applicant has become a major player with a reputation across the borders. In 2011, Forbes Global 2000 considered the BNP Paribas Group to which the Applicant belongs to be the number one bank in the eurozone. 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 bnl.it domain name to the .BNL TLD, including but not limited to:
  5. Internet advertising campaigns;
  6. having Internet traffic to its key domain names resolving into domain names registered in the .BNL TLD;
  7. email marketing campaigns;

4                 Offline campaigns; etc.

 

18(c). What operating rules will you adopt to eliminate or minimize social costs?

  1. The Applicant will organize the registry operation for the .BNL 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 .BNL 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 .BNL 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.
  5. The Applicant intends to make the .BNL top-level domain available to qualifying domain name registrants at no cost to them as per the most likely scenario; The Applicant ⁄ Registry Operator may, at its discretion charge a fee for the registration of domain names under the .BNL TLD. Such fee and domain name registration may be part of a larger package of services offered by the Applicant or its subsidiaries.
  6. 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 .BNL TLD.