.lpl New gTLD Application

Click to view Chinese translation articles.

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

New gTLD Application Submitted to ICANN by: LPL Holdings, Inc.

 

Application Downloaded On: 28 Apr 2016

 

String: lpl

 

Application ID: 1-1144-53270

 

Applicant Information

 

  1. Full legal name

LPL Holdings, Inc.

 

  1. Address of the principal place of business

One Beacon Street Boston, Massachusetts - 02108 US

 

  1. Phone number

6174233644

 

  1. Fax number

6175564002

 

  1. If applicable, website or URL

 

Primary Contact

 

6(a). Name

Tara Heptinstall

 

6(b). Title

Vice President, Communications

 

6(c). Address

 

6(d). Phone Number

(980) 321-1236

 

6(e). Fax Number

 

6(f). Email Address

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

 

Secondary Contact

 

7(a). Name

Stephanie Brown

 

7(b). Title

Managing Director, General Counsel

 

7(c). Address

 

7(d). Phone Number

6178974340

 

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

Corporation

 

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

Massachusetts Corporation

 

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.

NASDAQ / LPLA

 

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

Allen Russell Thorpe Director

James Sellers Riepe Director

James Steven Putnam Director

Jeffrey Alan Goldstein Director

Jeffrey Earl Stiefler Director

John Joseph Brennan Director

Mark Stephen Casady Chairman of the Board and Chief Executive Officer

Richard Paul Schifter Director

Richard Wallace Boyce Director

 

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

Name

Position

Christopher Francis Feeney Managing Director, Chief Technology Officer

Dan Hogan Arnold Managing Director, Head of Strategy

Esther Marion Stearns President, Chief Operating Officer

John Jerome McDermott, III Managing Director, Chief Risk Officer

Jonathan Galen Eaton Managing Director, Custom Clearing Services

Mark Robert Helliker Managing Director, Broker/Dealer Support Services

Robert Joseph Moore Chief Financial Officer

Stephanie Leigh Brown Managing Director, General Counsel

William Edward Dwyer, III President, National Sales & Marketing

 

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

Name

Position

Hellman & Friedman LLC Not Applicable

TPG Partners, IV, L.P. 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.

lpl

 

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

 

 

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.

 

 

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

 

 

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

 

 

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

 

 

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

 

 

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

 

 

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.

 

 

15C. List any variants 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.

 

As is the case with any new TLD that is added to the DNS root zone, some general technical acceptance issues with the delegation of this TLD are expected. The Registry Service Provider selected by the Applicant has a significant experience in introducing new TLDs to the DNS root, including .EU in 2005 and .SX in 2010.

The applied-for gTLD string consists only of ASCII characters (no IDN), which significantly reduces the risk of introducing confusion for the general public of character similarity

With the Registry Service Provider, the Applicant has carried out a series of tests in order to review whether the applied-for gTLD presented any operational or rendering issues. This included the deployment of a testing infrastructure for the applied-for Registry that operated:

1) a SRS (Shared Registration System) of which the features have been limited to what was strictly necessary to carry out the tests described below

2) a WHOIS system, displaying domain names registered in the test environment

3) an EPP (Extensible Provisioning Protocol) and web interface for Registrars

4) a DNS system, serving authoritative responses for the gTLD

5) a web server on which different basic websites were deployed;

6) an email server with mailboxes linked to various test domain names in the TLD and entered into a limited zone file which was made available through the DNS system referred to above.

The following tests have been carried out, by connecting various clients to the infrastructure described above:

1) logging into the Registry SRS with a Registrar account – using both EPP and Web interfaces

2) performing basic transactions (create, update, delete, transfer, allocate name servers, etc.) with this Registrar test account

3) generating of a test-zone file for this TLD

4) navigating to and within websites using both direct navigation to the respective domain names and navigation through hyperlinks displayed on the web sites that were hosted in the testing environment

5) sending FTP requests to and receiving correct responses from FTP environments matched to domain names registered in the gTLD testing environment

6) sending email messages to and receiving email messages from domain names registered in the TLD’s testing environment.

Within each of the above steps, the Applicant and its selected back-end registry operator reviewed:

1) whether Registrar transactions with respect to these domain names were performed successfully

2) whether the zone file was correctly generated and deployed in the DNS of the test environment

3) whether domain names registered in the TLD displayed correctly in browser address bars and email clients

4) whether email filters, spam detectors, etc. were correctly functioning.

Using web browsers, email and FTP clients, these tests have been carried out successfully. Therefore, to the Applicant’s best knowledge and belief, no specific issues are to be expected as regards the operation and rendering of the applied-for gTLD

 

  1. OPTIONAL.

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

 

 

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

 

The Applicant provides an integrated platform of proprietary technology, brokerage and investment advisory services to over 12,700 independent financial advisors and financial advisors at financial institutions across the United States.  Applicant believes that objective financial guidance is a fundamental need for everyone.  To meet this need, LPL Financial is an enabling partner to independent financial advisors, banks and credit unions, and broker-dealers at leading financial service companies.  

 

Applicant’s customers leverage for our broad range of resources – including independent research, enabling technology, clearing and compliance services, and practice management assistance – to manage the complexity of their business so they may instead focus on creating the trusted, personal, long-term advisor-client relationships that are the foundation for turning life’s aspirations into financial realities.

 

Applicant is excited to have the opportunity to establish its brand on the Internet and looks forward to working with ICANN to launch the .lpl TLD.  We believe that the creation of .lpl TLD will bring us greater brand recognition, not only among our financial advisor customers, but also among our end clients, the retail investors.  This top-level domain (TLD) will bolster our business as we compete with other broker-dealers and investment advisory firms, and will ultimately serve as a way for our retail investors to certify the legitimacy of our financial advisors’ services.

 

Most importantly, however, the .lpl TLD will allow us to provide our financial advisor partners with their own domain, branded with our strong corporate identity.  This technological and marketing support will enable our financial advisors to leverage the trust built around the brand to further bolster the relationships they have with their end-clients.

 

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

 

  1. Applicant was founded with a pioneering vision: to help entrepreneurial financial advisors establish successful businesses through which they may offer independent financial guidance and advice. Through our vision and dedication, Applicant has become a strong and reputable brand within the financial sector.  We believe that the establishment of our gTLD will only serve to enhance this brand recognition in our industry and among our end clients.  

In the past, Applicant has been the victim of internet fraud and misrepresentation that, if not properly managed, may have had an impact on our reputation. Applicant has always been proactive in combatting these abuses in order to ensure that our reputation does not suffer.  We have invested resources and taken measures to protect against these vulnerabilities. Applicant believes that establishing a secure internet environment through a proprietary TLD will not only add value to our brand, but will also create a safe haven for our company, our financial advisors, and our end-clients.

 

  1. The .lpl TLD will give us an edge on our competition. It will set us apart as a “first mover” in our industry, as we believe we will be among the first companies to have acquired its own gTLD.  This fact will convey a positive message to our customers and position us as an innovator in the marketing space.

The .lpl TLD will also allow us to provide our financial advisor partners with their own domain name, branded with our strong corporate identity.  Through the .lpl TLD, Applicant believes the trust that financial advisors place in the its brand will be shared with its end clients. The .lpl  TLD will help our end clients understand that while our financial advisors are independent, they are strongly supported by the brand.

 

Moreover, as we have described above, the financial industry sector is very often the victim of internet security breaches, and we therefore expect to use the TLD as an opportunity to provide a secure internet environment not only for Applicant as a firm, but also for our financial advisors in their ordinary business practices.

 

  1. The .lpl TLD  will guarantee authenticity and security. This is a very important consideration for firms within the financial services sector, because internet users, our financial advisors, and our end clients are often targets of the malicious conduct by third parties who misuse domain names in order to obtain personal and sensitive information.  Through our gTLD, we believe our end-clients will gain certainty and comfort that they are obtaining secure and accurate information from their advisors.

 

Applicant will at all times implement and adhere to any and all consensus policies introduced by ICANN, so as to further the development and stability of the internet and the global Internet community.  Applicant will also create a governance committee that will consists of legal, technical, commercial and business advisors to review and propose policies and ensure that all polices are adhered to.

 

A brief description of our registration polices is summarized below:

 

  • Prior to issuing .lpl domain names, Applicant intends to reserve a number of generic words, phrases, character and⁄or digits as second-level domain and third level that relate specifically to the activities of Applicant. These domain names will be allocated in accordance to the requirements as set out by Applicant. The purpose of these domains is to ensure the continuous operations of the Applicant.

 

  • In addition, Applicant also intends to block  words and phrases which it, in its sole and exclusive discretion, considers to be abusive, obscene and⁄or offensive, thereby preventing any reputational loss to our brand or any user confusion. These domain names will come up as unavailable.

 

  • Similarly, Applicant intends to reserve all two character labels and all country and territory names, taking into account the relevant provisions laid down in Specification 5 of the Registry Agreement. More information in this respect will be provided in our answer to Question 22.

 

Restricted registration: In order to comply with the above strategy, Applicant will, at least initially, restrict the .lpl TLD for corporate use only by Applicant. Going forward, it will allow its financial advisors to apply for a domain name within the .lpl TLD. Furthermore, the Applicant plans to include specific provisions in its registry-registrar agreement in order to ensure that Applicant’s mission and vision outlined above are implemented to their fullest extent possible. By doing so, Applicant will ensure that the restricted policies described above and below are adhered to, allowing for a smoother implementation of the issuance of the domain names.

 

All domain name applications will be presented to Applicant’s marketing department through a centralized, web-based, request system.  The marketing department will determine whether or not the request is approved. Once a particular domain name is approved, the marketing department will request the domain name registration through a Registrar. All domain names  under the .lpl TLD must be linked in a direct way to (i) the services offered under the brand or (ii) services,  products,  trademarks, or company names registered in name of the our financial advisors, our product sponsors, or our affiliates.  In addition all information provided under these domain names will be reviewed through an advertising compliance process led by our marketing department to ensure compliance with our regulatory requirements.

 

Applicant intends to launch  the .lpl TLD in several phases:

 

Phase One: Allocation of domain names that are linked to services specific to Applicant as well as the allocation of domain names that are currently being held directly by Applicant. This phase will last at least for a period of one year. The length of this period will allow us to ensure a smooth transition phase and will provide internal and external users with the opportunity to be familiarized with the transition.

 

Phase Two: In accordance to ICANN’s policies, Applicant will implement a sunrise period for 30 days, enabling its financial advisors to register their corresponding trademarks within .lpl TLD, as discussed in section 29.

 

Phase Three: This phase will not be open to the general public but as provided above will  only be open up to financial advisors, product sponsors, or affiliates of Applicant that  are eligible to register domain names within the .lpl TLD. All domain names will be submitted through a request process prior to registration in order to ensure that i) the domain name applied for corresponds with a trademark, company name, or service and products that are provided by our financial advisors and ii) the domain name complies with the anti- abuse registration polices as set out by our governance committee (see sections 28 and 29).

 

During this phase Applicant plans to adhere to the trademark claim services as set out by ICANN for a period of 60 days from the start of the phase. This allows trademark holders that are connected to the trademark clearinghouse to be informed if any of the domain names being applied for infringe their trademark.

 

  1. The only personal information the will be collected is that which is required to comply with ICANN’s WHOIS standards. In the event that we obtain any other personal information, Applicant shall comply with the applicable U.S. privacy laws and regulations. The Applicant that will ensure compliance with all data privacy laws. In the event that other personal information is collected by the Registrants, we will require that all Registrants and the applicable Registrars adhere to applicable U.S. privacy laws and regulations.

 

  1. Our goal is to achieve greater brand recognition and to increase the recognition of our financial advisors’ services through the .lpl TLD application. In order to reap the benefits from this gTLD, we will plan an appropriate communication to the relevant audience at the time of our application.In order to create awareness about the .lpl TLD, we will make the most of our existing advertising channels. This includes, among others, social media dialoguing, advertising campaigns, interviews, and internal leadership announcements.

 

 

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. In the event that there are multiple applications for a particular domain name, we will resolve this issue through a “first come, first served” process. In no event does the Applicant plan to auction domain names.

 

  1. In line with the mission above and due to our restricted registration policies all of the domain names will be allocated at no cost.

 

  1. As already explained above the purpose of the .lpl TLD is not to sell domain names but merely to create a new innovative portal of service offering.  Hence, we do not intend to implement any price increases.