18(b) How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?
|gTLD||Full Legal Name||E-mail suffix||Detail|
|.JPMORGANCHASE||JPMorgan Chase & Co.||markmonitor.com||View|
i. The applied-for gTLD is a recognized brand of the Applicant. The applied-for gTLD aims to protect, develop, and maintain the reputation of the Applicant’s brand in the financial services industry.
ii. From the Applicant’s perspective, the applied-for gTLD 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 applied-for top-level domain is currently intended to be unambiguous as regards: the identity of the Registry Operator; the source of the content and services offered under the applied-for gTLD; the affiliation between the Registry Operator and the gTLD; and the affiliation between the Registry Operator and any third party that is authorized by the Applicant at its discretion to register and⁄or use one or more domain names in the applied-for gTLD.
iii. As mentioned in 18(a), key reasons why Applicant seeks delegation of the applied-for gTLD include, but are not limited to:
1. Securing and protecting the Applicant’s brand as a gTLD. The Applicant seeks to protect its brand from third parties, who may wish to trade on the good name of the Applicant’s brand by securing the applied-for gTLD. The Applicant also seeks to avoid any confusion that may result from another entity holding the applied-for gTLD. This is particularly beneficial for users. Securing the applied-for gTLD is a logical extension of the Applicant’s continued investment in protecting and promoting its brand both offline and online.
2. Reflecting and operating the Applicant’s brand at the top-level of the DNS’ hierarchy. The ease with which users will be able to locate the Applicant’s brand at the top-level of the DNS’ hierarchy is also beneficial to users.
3. Trust, safety and security for users. The gTLD 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.
iv. The Applicant intends to implement the following policies and procedures with respect to the registration of domain names in the applied-for top-level domain:
1. Reservation and registration of domain names in the name of the Applicant. It is likely that this will be the scenario that the Applicant will put in place during the first months or even years of operation of the applied-for gTLD. The names may include, but are not limited to:
a) descriptive names, referring to the actual day-to-day business activities of the Applicant and⁄or its subsidiaries;
b) descriptive names, referring to the internal departments of the Applicant;
c) descriptive names, referring to the subsidiaries of the Applicant; and
d) product and service brands promoted by the Applicant and⁄or its subsidiaries now and in the future.
2. Launch of the gTLD. 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 the Applicant will be entitled to set at its own discretion, may register domain names in the gTLD. These processes may include the following.
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.
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.
c) 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., the Applicant). In any case, the Applicant 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 operates in more than 60 countries including the United States, it is subject to both federal and state, privacy and data protection laws and privacy and data protection laws, rules and⁄or practices in other jurisdictions. The Applicant will at all times be obliged to carefully consider and, where applicable, implement privacy, data protection and confidentiality measures during operation of the applied-for gTLD.
vi. At this stage, the Applicant has not developed concrete and tangible plans in order to establish online activities on the applied-for gTLD or move online activities from one or more of its active domain names to the applied-for gTLD. However, the Applicant could implement different initiatives to make stakeholders aware of the development of a new online environment under the applied-for gTLD, including but not limited to:
1. advertisements in newspapers and magazines;
2. Internet advertising campaigns;
3. resolving Internet traffic to one or more of the Applicant’s active domain names into domain names registered in the applied-for gTLD; and
4. email marketing campaigns.
Similar gTLD applications: (4)
|gTLD||Full Legal Name||E-mail suffix||z||Detail|
|.JPMORGAN||JPMorgan Chase & Co.||markmonitor.com||�||Compare|
|.CHASE||JPMorgan Chase & Co.||markmonitor.com||�||Compare|
|.FARMERS||Farmers Insurance Exchange||markmonitor.com||∞||Compare|
|.AETNA||Aetna Life Insurance Company||AETNA.com||∞||Compare|