8(b). State the specific national or other jursidiction that defines the type of entity identified in 8(a).
8(c). Attach evidence of the applicant's establishment.
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.
The Northwestern Mutual Life Insurance Company
9(c). If the applying entity is a joint venture, list all joint venture partners.
11(a). Name(s) and position(s) of all directors
11(b). Name(s) and position(s) of all officers and partners
11(c). Name(s) and position(s) of all shareholders holding at least 15% of shares
The Northwestern Mutual Life Insurance Company
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
Conrad Carlton York
Member of the Management Committee
Michael Gerard Carter
Member of the Management Committee
Raymond Joseph Manista, Jr.
Member of the Management Committee
Applied-for gTLD string
13. Provide the applied-for gTLD string. If an IDN, provide the U-label.
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.
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.
16. 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.
Northwestern Mutual MU TLD Registry, LLC foresees no known rendering issues in connection with the proposed .MUTUAL gTLD for which it is applying. This answer is based upon consultation with Northwestern Mutual MU TLD’s Registry, LLC’s selected back-end provider, Neustar, which has successfully launched a number of new gTLDs over the last decade. In reaching this determination, Neustar analyzed the following data:
-ICANN’s Security Stability Advisory Committee (SSAC) entitled Alternative TLD Name Systems and Roots: Conflict, Control and Consequences (SAC009);
-IAB - RFC3696 “Application Techniques for Checking and Transformation of Names”
-Known software issues which Neustar has encountered during the last decade launching new gTLDs;
-Character type and length;
-ICANN supplemental notes to Question 16; and
-ICANN’s presentation during its Costa Rica regional meeting on TLD Universal Acceptance.
17. (OPTIONAL) Provide a representation of the label according to the International Phonetic Alphabet (http://www.langsci.ucl.ac.uk/ipa/).
18(a). Describe the mission/purpose of your proposed gTLD.
Mission and Purpose of .MUTUAL
The Northwestern Mutual Life Insurance Company (“Northwestern Mutual”) is a mutual company serving the insurance and investment needs of more than three million clients, offering a variety of financial services throughout the United States. Northwestern Mutual’s online content is viewable in the .COM, .NET, .BIZ, .INFO, .JOBS, .TEL, .MOBI, and .ORG gTLDs, and also in the .US ccTLD. In order to apply for the .MUTUAL gTLD, Northwestern Mutual has selected its subsidiary company, Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”), as the entity to file this application and bring the .MUTUAL gTLD to market. Northwestern Mutual MU TLD Registry is a wholly owned subsidiary of Northwestern Mutual.
Ranked 112 on the Fortune 500, Northwestern Mutual is the largest direct provider of individual life insurance in the United States and has received the highest possible financial strength ratings awarded to any life insurer by four of the major credit rating agencies. Northwestern Mutual’s portfolio of financial services includes: life insurance, long-term care insurance, disability insurance, annuities, mutual funds, and employee benefit services, among others.
The intended future mission and purpose of the .MUTUAL gTLD is to serve as a trusted and intuitive namespace provided by Northwestern Mutual MU TLD Registry for Northwestern Mutual, its subsidiaries, and its current and future clients and policyowners. However, to date there has not been enough time, and currently there is not enough market information available, to fully analyze and evaluate all potential use case options.
Northwestern Mutual will be analyzing general market adoption to determine short- and long-term potential best-in-class use case options to most effectively serve and enhance Northwestern Mutual’s online strategy.
The goal of the .MUTUAL gTLD is to protect Northwestern Mutual’s online presence and identity; expand its marketing and promotion efforts; provide a secure channel for online products and services; and offer a platform through which to consolidate many of the intellectual property activities of Northwestern Mutual.
Northwestern Mutual MU TLD Registry intends to initially limit registration and use of domain names within the .MUTUAL gTLD to Northwestern Mutual and its qualified subsidiaries and affiliates. This initial limited use will allow Northwestern Mutual MU TLD Registry to establish its operations and achieve full sustainability. This limited distribution, coupled with the other requirements set forth in Specification 9 of the template Registry Agreement, is intended to exempt Northwestern Mutual MU TLD Registry from its annual Code of Conduct Compliance requirements.
After Stage Two (see below), Northwestern Mutual MU TLD Registry and Northwestern Mutual will evaluate whether opportunities exist to carry out the business strategy for the gTLD through expansion that continues the registry’s sustainable operations through fee-based registrations to parties other than Northwestern Mutual and its qualified subsidiaries and affiliates.
Northwestern Mutual MU TLD Registry currently plans a four-stage rollout for the .MUTUAL gTLD. The dates of these stages are subject to change depending upon business, strategic, and industry factors at the time.
1. Stage One The initial stage of implementation of the gTLD will involve Northwestern Mutual registering a limited number of .MUTUAL second-level domain names.
This initial use will provide Northwestern Mutual’s IT and security personnel the time to run a number of tests to ensure seamless and secure access using the .MUTUAL gTLD domain names, interoperability with various software and Web-based applications, and unbroken and secure use of all names. This initial allocation will also allow the appropriate Northwestern Mutual MU TLD Registry staff to coordinate with the internal and external staff responsible for the delegation and setup phases of the .MUTUAL gTLD to ensure a proper transition from delegation to full operation.
2. Stage Two Once all testing has been successfully completed, Northwestern Mutual MU TLD Registry will begin allocating domain names in .MUTUAL to Northwestern Mutual and potentially its qualified subsidiaries and affiliates for more widespread internal corporate use. During this same period of time, Northwestern Mutual will begin evaluating strategies to potentially migrate traffic away from its current patchwork network of second-level domain names, which are registered in a variety of TLDs, to the .MUTUAL gTLD.
It is also in Stage Two that Northwestern Mutual will evaluate expanding the operations of the gTLD to permit registration by other registrants such as licensees or strategic partners. Should an assessment of its expansion strategy lead to a decision to extend registration rights to other parties, this expansion is currently planned to take place during Stage Three. However, any expansion would be conditioned upon a review of Specification 9 (Registry Code of Conduct) set forth in the template Registry Agreement to ensure compliance with Northwestern Mutual MU TLD Registry’s business model.
3. Stage Three Depending on the analysis of the evaluations undertaken in Stage Two, Northwestern Mutual MU TLD Registry may implement the permanent migration of Internet traffic away from the TLDs in which Northwestern Mutual’s domain names are currently registered, and toward the .MUTUAL gTLD. It is in this stage that Northwestern Mutual MU TLD Registry also may implement Northwestern Mutual’s decision to extend registration rights to licensees or strategic parties, depending upon compliance with Specification 9 as noted above.
After consideration of the following factors: analysis of Northwestern Mutual’s existing domain name portfolio; internal analysis of marketing initiatives; and the fact that Northwestern Mutual will have full control over the number of registrations in the .MUTUAL gTLD namespace, Northwestern Mutual MU TLD Registry is confident that the number of domain name registrations will be less than 10,000 in the first five years of operation.
4. Stage Four Based on its experience with any expansion implemented in Stage Three, Northwestern Mutual MU TLD Registry and Northwestern Mutual will assess whether the business plan and expansion strategy should be augmented by extending registration rights to a broader class of licensees, including potential clients and policyowners of Northwestern Mutual. It is anticipated by Northwestern Mutual that changes to the domain name industry, and particularly the impact of .GENERIC gTLDs, will take at least five years to be realized and assessed. Any decision to expand the gTLDs beyond corporate, qualified subsidiary⁄affiliate, and licensee use will take into account this experience as well as the technical analysis of potential expansion.
Utilizing current projections based upon Northwestern Mutual’s existing businesses, future business plans, current domain name portfolio, and other strategic factors, Northwestern Mutual MU TLD Registry estimates second-level domain name registrations to be in line with the projections set forth in the response to Question 46 of this application.
18(b). How proposed gTLD will benefit registrants, Internet users, and others
18.2 How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?
Northwestern Mutual MU TLD Registry believes that the proposed .MUTUAL gTLD has the potential to offer the following benefits to Internet users and consumers:
-Establish a trusted source of information and online marketplace for consumers or third parties nationwide who seek information about Northwestern Mutual’s products and services; for consumers or third parties to identify nearby offices or representatives; and for the general Internet user population;
-Provide Northwestern Mutual and its qualified subsidiaries and affiliates with short and memorable Internet addresses; provide increased navigation to products, services, advertising campaigns, events, public interest content, etc.;
-Minimize the cost and need for defensive registrations because domain names will only initially be allocated by Northwestern Mutual MU TLD Registry to Northwestern Mutual and its qualified subsidiaries and affiliates for internal company use; and
-Develop a potential platform for the secure access to, purchase of, and distribution of Northwestern Mutual products and information to consumers, in order to minimize the potential for counterfeit or infringing goods.
Also, through the adoption of new gTLDs by the wider Internet user community, consumers may benefit from lower incidents of phishing and malware often associated with mistypes of domain names in the .COM space that are owned by cybersquatters, since they will be navigating to domain names in the .MUTUAL gTLD.
18.2.1 What is the goal of your proposed gTLD in terms of areas of specialty, service levels, or reputation?
The primary mission and purpose of the .MUTUAL gTLD is to provide a trusted, hierarchical, secure, and intuitive online marketplace to deliver Northwestern Mutual’s content and services, as well as information on Northwestern Mutual’s business and focus. As Northwestern Mutual continues to expand, it is the company’s desire to pursue and develop opportunities to market and distribute its online content to consumers, on various platforms, including the Internet and mobile devices, among others. Given that consumers increasingly request access to Northwestern Mutual brands through a variety of channels, which include domain names, Northwestern Mutual MU TLD Registry believes that the .MUTUAL gTLD has the potential to provide an innovative, virtual avenue to Northwestern Mutual online content that will deepen and broaden its relationship with consumers.
Most importantly, Northwestern Mutual will be able to provide access to its online content in a namespace devoid of piracy, cybersquatting, and other malicious activities. Providing consumers with a trusted experience is paramount to Northwestern Mutual and the .MUTUAL gTLD will be used to further that goal.
While companies such as Northwestern Mutual fight a never-ending battle to protect their valuable intellectual property from piracy on the Internet, the .MUTUAL gTLD would offer consumers a safe and intuitive means of accessing authorized content from Northwestern Mutual and its qualified subsidiaries and affiliates.
18.2.2 What do you anticipate your proposed gTLD will add to the current space, in terms of competition, differentiation, or innovation?
The primary driving factors of the .MUTUAL gTLD are differentiation and innovation. The number of domain names registered will not measure the success of the gTLD, but rather success will be judged by the levels of consumer recognition and trust that are placed in the .MUTUAL gTLD. Using this benchmark, Northwestern Mutual will strive to build consumer recognition and trust through the usage of the .MUTUAL gTLD that rise to the levels of those found in the .EDU and .GOV gTLDs.
As noted above, Northwestern Mutual is a leading mutual company that leverages numerous distribution channels and emerging technologies to deliver its online content to its consumers throughout the United States. The .MUTUAL gTLD has the potential to augment this online strategy, if the potential benefits that ICANN has projected become a reality.
Northwestern Mutual MU TLD Registry believes that the .MUTUAL gTLD will provide a trusted ecosystem experience for the millions of consumers nationwide who purchase Northwestern Mutual’s products and services, as well as those who seek information that Northwestern Mutual provides. In addition to providing consumers with short, memorable, and intuitive domain names, consumers will know that all domains and content are owned and controlled by Northwestern Mutual, and thus that they are protected from potential infringing, counterfeit, and other harmful content.
The initial use of the .MUTUAL gTLD will involve Northwestern Mutual registering a limited number of second-level domain names. This initial use will provide Northwestern Mutual MU TLD Registry with the ability to ensure seamless and secure access to the Northwestern Mutual websites and interoperability with various software and Web-⁄mobile-based applications. Once appropriate security and stability issues have been satisfactorily addressed, Northwestern Mutual MU TLD Registry will likely begin allocating domain names for internal corporate use at Northwestern Mutual and may redirect .MUTUAL domain names to preexisting content. This phased rollout will likely take place over a multi-year period, subject to change depending upon a range of external factors.
At the same time, Northwestern Mutual will evaluate potential strategies to migrate traffic away from its current network of second-level domains, which are registered in various TLDs, to the .MUTUAL gTLD, which offers the potential to provide consumers with a single, trusted online source for Northwestern Mutual branded products and services.
After consideration of the following factors: analysis of Northwestern Mutual’s existing domain name portfolio; internal analysis of marketing initiatives; and the fact that Northwestern Mutual MU TLD Registry will have full control over the number of registrations in the .MUTUAL gTLD namespace, Northwestern Mutual MU TLD Registry reasonably assumes that the number of domain name registrations will be less than 10,000 in the first five years of operation.
18.2.4 Provide a complete description of the applicant’s intended registration policies in support of the goals listed above.
Northwestern Mutual MU TLD Registry currently intends for the .MUTUAL gTLD to be used exclusively by Northwestern Mutual and its qualified subsidiaries and affiliates. Because of this condition, and because the Northwestern Mutual mark is a valuable brand, the protection of which is paramount to Northwestern Mutual, Northwestern Mutual MU TLD Registry intends to address registration and use requirements in its qualified subsidiary and affiliate agreements that exist between those qualified affiliates and subsidiaries and Northwestern Mutual, rather than in a domain name registration agreement.
Notwithstanding these concerns, Northwestern Mutual MU TLD Registry will incorporate all required ICANN consensus policies and other legal⁄policy requirements imposed on new gTLD applicants into the terms and conditions of the domain name registration agreements that each qualified subsidiary and affiliate of Northwestern Mutual will execute.
18.2.5 Will your proposed gTLD impose any measures for protecting the privacy or confidential information of registrants or users? If so, please describe any such measures.
As a nationally recognized insurance company, Northwestern Mutual respects the privacy of its policyowners, clients, and other consumers. The company employs a variety of physical, electronic, contractual, and managerial safeguards to protect personal and confidential information in its possession and on its websites. Northwestern Mutual MU TLD Registry will take similar precautions to protect registrant and user data associated with the .MUTUAL gTLD. Furthermore, given that every domain name will initially be registered to Northwestern Mutual or its qualified subsidiaries and affiliates, Northwestern Mutual has a vested interest to ensure that accurate and current domain name information is readily available in connection with each .MUTUAL domain name.
In addition, Northwestern Mutual MU TLD Registry intends to incorporate contractual language in its Registry-Registrar Agreement (RRA) modeled after language that has been included in the template Registry Agreement and that has been successfully utilized by existing ICANN gTLD Registry Operators.
The template Registry Agreement states, “Registry Operator shall (i) notify each ICANN-accredited registrar that is a party to the registry-registrar agreement for the TLD of the purposes for which data about any identified or identifiable natural person (“Personal Data”) submitted to Registry Operator by such registrar is collected and used under this Agreement or otherwise and the intended recipients (or categories of recipients) of such Personal Data, and (ii) require such registrar to obtain the consent of each registrant in the TLD for such collection and use of Personal Data. Registry Operator shall take reasonable steps to protect Personal Data collected from such registrar from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator shall not use or authorize the use of Personal Data in a way that is incompatible with the notice provided to registrars.ʺ
18.2.6 Describe whether and in what ways outreach and communications will help to achieve your projected benefits.
As noted above, Northwestern Mutual MU TLD Registry’s driving factor in securing the .MUTUAL gTLD in ICANN’s first round is precautionary in nature, and while Northwestern Mutual MU TLD Registry and Northwestern Mutual see the potential for this gTLD to be able to play a large role in Northwestern Mutual’s future online strategic initiatives, there are a number of unanswered questions concerning consumer recognition, the adoption of new gTLDs, and the response from search engines in the marketplace that will influence the usage of the gTLD and communication about that usage.
Notwithstanding this, Northwestern Mutual plans to start using .MUTUAL domains initially as redirects to existing .COM domains. As the aforementioned questions are answered over time, Northwestern Mutual may decide to initiate a targeted, pilot rollout using select gTLD domains as primary addresses and, after careful analysis and study of this rollout, Northwestern Mutual may plan to engage in a broader initiative should the results be satisfactory and in accordance with Northwestern Mutual’s overall strategic goals, both in the online space and in its office operations. The actual usage of .MUTUAL domain names will dictate what public communications and consumer outreach is done to encourage navigation to .MUTUAL domain names. This may include, but is not limited to, advertising, media outreach, in-store communications, email campaigns, etc.
18(c). Describe operating rules to eliminate or minimize social costs or financial resource costs, various types of consumer vulnerabilities.
18.3 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)?
Northwestern Mutual MU TLD Registry’s proposed operating rules to initially limit registration to Northwestern Mutual and its qualified subsidiaries and affiliates will provide a trusted online environment for consumers to access Northwestern Mutual’s online content, and by default will minimize social costs. This verified ecosystem provides consumers with a single, trusted source for Northwestern Mutual products and services with a substantially lower risk of fraud and⁄or scams. Northwestern Mutual MU TLD Registry does not anticipate consumer vulnerabilities. Therefore, one example of how costs are mitigated is that there is no need for other trademark and brand owners to defensively register second-level domains in the .MUTUAL gTLD. In total, Northwestern Mutual MU TLD Registry’s expectation is that the usage of the .MUTUAL gTLD will eliminate many of the vulnerabilities that Northwestern Mutual consumers face in the Internet today.
18.3.1 What other steps will you take to minimize negative consequences⁄costs imposed upon consumers?
Northwestern Mutual MU TLD Registry believes that the proposed operation of the .MUTUAL gTLD as set forth in this application has no known negative consequences or cost implications to consumers. On the contrary, the proposed operation of this registry will likely lead to direct and quantifiable benefits to consumers.
18.3.2 How will multiple applications for a particular domain name be resolved, for example, by auction or on a first-come⁄first-serve basis?
Northwestern Mutual MU TLD Registry does not envision multiple applicants for the same domain name, as domain names will initially only be allocated to Northwestern Mutual and its qualified subsidiaries and affiliates, at least for the first three years of operation. Depending on a number of evaluations, Northwestern Mutual MU TLD Registry may expand registrations so as to include Northwestern Mutual partners as potential registrants in the future.
18.3.3 Explain any cost benefits for registrants you intend to implement (e.g., advantageous pricing, introductory discounts, bulk registration discounts).
Northwestern Mutual MU TLD Registry does not envision any advantageous pricing, introductory discounts, or bulk registration discounts because these marketing⁄commercial initiatives are inconsistent with the mission and purpose of the .MUTUAL gTLD as a trusted online source identifier. Moreover, it is the current intention of Northwestern Mutual MU TLD Registry to provide domain name registrations to Northwestern Mutual and its qualified subsidiaries and affiliates at no cost, though the company reserves the right to reevaluate this decision and may alter it in the future.
18.3.4 Note that the Registry Agreement requires that registrars be offered the option to obtain initial domain name registrations for periods of one to ten years at the discretion of the registrar, but no greater than ten years. Additionally, the Registry Agreement requires advance written notice of price increases. Do you intend to make contractual commitments to registrants regarding the magnitude of price escalation? If so, please describe your plans.
Northwestern Mutual MU TLD Registry is committed to providing the domain name registration periods set forth in the Registry Agreement. However, as noted above, the registration and use of .MUTUAL domain names is conditioned upon a separate relationship with Northwestern Mutual. Therefore, providing contractual commitments in a domain name registrant agreement regarding the magnitude of price escalations does not seem relevant or appropriate. Additionally, as noted above, the current business model envisions Northwestern Mutual MU TLD Registry initially providing domain name registrations to Northwestern Mutual and its qualified subsidiaries and affiliates at no cost.
Northwestern Mutual MU TLD Registry acknowledges that the current template Registry Agreement requires that the Registry Operator “shall offer registrars the option to obtain registration periods for one to ten years at the discretion of the registrar.” However, Northwestern Mutual and its qualified subsidiaries and affiliates, as the sole registrants within the .MUTUAL gTLD will only be registering domain names on an annual basis. This is done to better account for costs on an annual basis as well as to provide for more concise financial statements in Question 46, i.e., no multi-year registration or deferred revenue.
19. Is the application for a community-based TLD?
20(a). Provide the name and full description of the community that the applicant is committing to serve.
20(b). Explain the applicant's relationship to the community identified in 20(a).
20(c). Provide a description of the community-based purpose of the applied-for gTLD.
20(d). Explain the relationship between the applied-for gTLD string and the community identified in 20(a).
20(e). Provide a description of the applicant's intended registration policies in support of the community-based purpose of the applied-for gTLD.
20(f). Attach any written endorsements from institutions/groups representative of the community identified in 20(a).
21(a). Is the application for a geographic name?
Protection of Geographic Names
22. Describe proposed measures for protection of geographic names at
the second and other levels in the applied-for gTLD.
22.1 Northwestern Mutual MU TLD Registry has Properly Researched this Topic
Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) is keenly aware of the sensitivity of national governments in connection with protecting country and territory identifiers in the Domain Name System (DNS). In preparation for answering this question, Northwestern Mutual MU TLD Registry reviewed the following relevant background material regarding the protection of geographic names in the DNS:
-ICANN Board Resolution 01-92 regarding the methodology developed for the reservation and release of country names in the .INFO top-level domain, see http:⁄⁄www.icann.org⁄en⁄minutes⁄minutes-10sep01.htm; -ICANN’s Proposed Action Plan on .INFO Country Names, see http:⁄⁄www.icann.org⁄en⁄meetings⁄montevideo⁄action-plan-country-names-09oct01.htm; -“Report of the Second WIPO Internet Domain Name Process: The Recognition and Rights and the Use of Names in the Internet Domain Name System,” Section 6, Geographical Identifiers, see http:⁄⁄www.wipo.int⁄amc⁄en⁄processes⁄process2⁄report⁄html⁄report.html; -ICANN’s Governmental Advisory Committee (GAC) Principles Regarding New gTLDs, see https:⁄⁄gacweb.icann.org⁄download⁄attachments⁄1540128⁄gTLD_principles_0.pdf?version=1&modificationDate=1312358178000; and -ICANN’s Generic Names Supporting Organization Reserved Names Working Group – Final Report, see http:⁄⁄gnso.icann.org⁄issues⁄new-gtlds⁄final-report-rn-wg-23may07.htm.
22.2 Initial Reservation of Country and Territory Names
Northwestern Mutual MU TLD Registry is committed to initially reserving the country and territory names contained in the internationally recognized lists described in Article 5 of Specification 5 attached to New gTLD Applicant Guidebook at the second level, and at all other levels within the .MUTUAL gTLD at which Northwestern Mutual MU TLD Registry will provide registrations. Specifically, Northwestern Mutual MU TLD Registry will reserve:
1.The short form (in English) of all country and territory names contained on the ISO 3166-1 list, as updated from time to time, including the European Union, which is exceptionally reserved on the ISO 3166-1 list, and its scope extended in August 1999 to any application needing to represent the name European Union, see http:⁄⁄www.iso.org⁄iso⁄support⁄country_codes⁄iso_3166_code_lists⁄iso-3166-1_decoding_table.htm#EU;
2.The United Nations Group of Experts on Geographical Names Technical Reference Manual for the Standardization of Geographical Names, Part III Names of Countries of the World; and
3. The list of United Nations member states in six official United Nations languages prepared by the Working Group on Country Names of the United Nations Conference on the Standardization of Geographical Names.
22.3 Fair & Non-Misleading Use of Geographical Identifiers
Northwestern Mutual MU TLD Registry’s parent company, The Northwestern Mutual Life Insurance Company (“Northwestern Mutual”), is the United States’ largest direct provider of individual life insurance, offering financial services including life insurance, long-term care insurance, disability insurance, annuities, mutual funds, and employee benefit services. Northwestern Mutual’s online content is viewable in the .COM, .BIZ, .TEL, .MOBI, .ORG, .NET, and .INFO gTLDs, and also in the .US ccTLD.
In providing online information and access to products, Northwestern Mutual uses geographic identifiers in domain names to provide online visitors with an intuitive namespace to navigate for relevant content. A representative sample of these websites includes:
The above representative list of examples demonstrates fair and non-misleading use of geographical identifiers by Northwestern Mutual. As such, Northwestern Mutual believes that a .MUTUAL gTLD can provide an online single source-identifying location for its current and future subsidiaries, clients, and policyowners around the country, enhancing and supplementing the current brand and geographic-specific domain names that Northwestern Mutual has used in different markets throughout the United States.
Given this geographic approach to finding localized Northwestern Mutual content, Northwestern Mutual MU TLD Registry intends to explore the option of providing a hierarchical and intuitive framework for the .MUTUAL namespace by using geographical identifiers as second-level domain names. This use of geographical identifiers to the left of the TLD and as part of the domain name itself is believed to have a direct and material impact on search engine algorithms and their corresponding query results. In addition, such naming conventions are intuitive and practiced by direct navigation Internet users (those that type their intended destination into address bars, as opposed to search engines). Northwestern Mutual MU TLD Registry would like to see if this type of hierarchical and intuitive use of second-level domain names within a gTLD provides increased consumer functionality and innovation, as premised by ICANN.
22.4 The Legal Protection of Geographical Identifiers
One of the more authoritative resources on the current state of the law in connection with the protection of geographical identifiers was authored by the World Intellectual Property Organization (WIPO) in its 2001 “Report of the Second WIPO Internet Domain Name Process: The Recognition of Rights and the Use of Names in the Internet Domain Name System.” Section six of this report was devoted exclusively to the protection of geographical identifiers.
In analyzing the well-established framework against the misuse of geographical identifiers at the international, regional, and national levels, WIPO identified the following two elements for the protection of geographical identifiers: (i) a prohibition of false descriptions of the geographical source of goods; and (ii) a more extensive set of rules prohibiting the misuse of one class of geographical source indicators, known as geographical indications (see “Report of the Second WIPO Internet Domain Name Process,” Paragraphs 206 and 210). Neither false descriptions of the geographical source of goods, nor misuse of geographical indications, is present in Northwestern Mutual’s current or Northwestern Mutual MU TLD Registryʹs proposed use of geographical identifiers.
Notwithstanding WIPO’s recommendation that the protection of geographical identifiers is “a difficult area on which views are not only divided, but also ardently held” (Paragraph 237), national governments within the ICANN Governmental Advisory Committee (GAC) and other international fora have continued to advocate for increased safeguards to protect against the misuse of geographical identifiers within the domain name system.
Northwestern Mutual MU TLD Registry’s parent company, Northwestern Mutual, as a responsible business, seeks to minimize any potential business practices that might mislead consumers. However, at the same time, it believes that it is important to be able to use geographical identifiers in a fair and non-misleading manner, if such use can benefit Internet users as proposed in Northwestern Mutual MU TLD Registry and Northwestern Mutual’s business model.
22.5 Samples of Fair & Non-Misleading Use of Geographical Identifiers
In undertaking a thorough research of this subject matter prior to filing this application, Northwestern Mutual MU TLD Registry’s subject matter experts were able to uncover the following representative sampling of fair and non-misleading use of geographical identifiers used in the existing gTLD domain name space:
Fair Use of National Geographical Identifiers
AUSTRALIA.COOP – Is operated by Co-operatives Australia, the national body for State Co-operative Federations, and provides a valuable resource about cooperatives within Australia UK.COOP – Is operated by Co-operatives UK, the national trade body that campaigns for cooperation, and works to promote, develop, and unite cooperative enterprises within the United Kingdom MALDIVIAN.AERO – Is the dominant domestic air carrier in Maldives, and provides a range of commercial and leisure air transport services.
Fair Use Regional⁄Local Geographical Identifiers
TEXAS.JOBS – Is operated by a joint effort between DE, the Texas Workforce Commission, and the National Labor Exchange to connect job seekers with approximately 96,000 job openings. An additional domain name operated by this joint effort was WORKINTEXAS-VETERANS.JOBS, a resource devoted to helping Texas veterans translate their military skills to jobs in the civil marketplace. HYDERABAD.AERO – Is operated by the Hyderabad International Airport and provides a range of interactive services and information for both business and leisure travelers. SACRAMENTO.AERO – Is a portal website operated by Sacramento County to provide links to each of the airports serving the Sacramento area: Sacramento International Airport (SMF), Mather Airport (MHR), Executive Airport (SAC), and Franklin Field (F72).
22.6 Protection of Regional and Local Geographic Names for Non-Misleading Use
Northwestern Mutual MU TLD Registry and Northwestern Mutual have stated their intention to consider using non-reserved geographic identifiers as part of a hierarchical and intuitive framework in a fair and non-misleading manner to help consumers navigate the .MUTUAL namespace. Northwestern Mutual MU TLD Registry is committed to operating .MUTUAL in a manner that minimizes potential consumer confusion, and will actively work with others in the ICANN community regarding any future policy development in this area.
22.7 Potential Future Release of Initially Reserved Names
Northwestern Mutual MU TLD Registry and Northwestern Mutual look forward to collaborating with other new gTLD registry operators in potentially working with ICANN’s GAC to explore processes that could permit the release of initially reserved country names (including ISO 3166 two-characters). Specifically, Northwestern Mutual MU TLD Registry is interested in exploring other Registry Service Evaluation Processes (RSEP) that have been filed by existing gTLD Registry Operators in releasing previously reserved domain names.
22.8 Dispute Resolution
Northwestern Mutual MU TLD Registry does not envision any potential disputes from governments or public authorities in connection with the registration and use of geographic names within the .MUTUAL gTLD based upon its proposed use set forth in response to Question 18 of this application.
However, Northwestern Mutual MU TLD Registry is committed to working with governments, public authorities, or IGOs that may have a concern regarding the registration of names with national or geographic significance at the second level within .MUTUAL. Therefore, should any potential disputes arise, Northwestern Mutual MU TLD Registry will undertake an immediate policy development process as identified below.
22.9 Creation and Updating the Policies
If there should arise some future need for the creation or updating of the policies regarding this class of domain names, Northwestern Mutual MU TLD Registry and Northwestern Mutual will act in an open and transparent manner consistent with their prior practices to develop such a policy and⁄or recommendation.
Northwestern Mutual MU TLD Registry is also committed to continually reviewing and updating these lists to prevent the misleading use of geographical identifiers. Consistent with this commitment, Northwestern Mutual MU TLD Registry intends to remain an active participant in any ongoing ICANN policy discussions regarding the protection of geographic names within the DNS.
23. Provide name and full description of all the Registry Services to be provided.
23.1 Introduction Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) has elected to partner with Neustar, Inc. (“Neustar”) to provide back-end services for the .MUTUAL registry. In making this decision, Northwestern Mutual MU TLD Registry recognized that Neustar already possesses a production-proven registry system that can be quickly deployed and smoothly operated over its robust, flexible, and scalable world-class infrastructure. The existing registry services will be leveraged for the .MUTUAL registry. The following section describes the registry services to be provided. 23.2 Standard Technical and Business Components Neustar will provide the highest level of service while delivering a secure, stable and comprehensive registry platform. Northwestern Mutual MU TLD Registry will use Neustar’s Registry Services platform to deploy the .MUTUAL registry, by providing the following Registry Services (none of these services are offered in a manner that is unique to .MUTUAL: Registry-Registrar Shared Registration Service (SRS) Extensible Provisioning Protocol (EPP) Domain Name System (DNS) WHOIS DNSSEC Data Escrow Dissemination of Zone Files using Dynamic Updates Access to Bulk Zone Files Dynamic WHOIS Updates IPv6 Support Rights Protection Mechanisms Internationalized Domain Names (IDN) The following is a description of each of the services: SRS Neustar’s secure and stable SRS is a production-proven, standards-based, highly reliable, and high-performance domain name registration and management system. The SRS includes an EPP interface for receiving data from registrars for the purpose of provisioning and managing domain names and name servers. The response to Question 24 provides specific SRS information. EPP The .MUTUAL registry will use the Extensible Provisioning Protocol (EPP) for the provisioning of domain names. The EPP implementation will be fully compliant with all RFCs. Registrars are provided with access via an EPP API and an EPP based Web GUI. With more than 10 gTLD, ccTLD, and private TLDs implementations, Neustar has extensive experience building EPP-based registries. Additional discussion on the EPP approach is presented in the response to Question 25. DNS Northwestern Mutual MU TLD Registry will leverage Neustar’s world-class DNS network of geographically distributed nameserver sites to provide the highest level of DNS service. The service utilizes “Anycast” routing technology, and supports both IPv4 and IPv6. The DNS network is highly proven, and currently provides service to over 20 TLDs and thousands of enterprise companies. Additional information on the DNS solution is presented in the response to Questions 35. WHOIS Neustar’s existing standard WHOIS solution will be used for the .MUTUAL. The service provides supports for near real-time dynamic updates. The design and construction is agnostic with regard to data display policy and is flexible enough to accommodate any data model. In addition, a searchable WHOIS service that complies with all ICANN requirements will be provided. The following WHOIS options will be provided: Standard WHOIS (Port 43) Standard WHOIS (Web) Searchable WHOIS (Web) DNSSEC An RFC compliant DNSSEC implementation will be provided using existing DNSSEC capabilities. Neustar is an experienced provider of DNSSEC services, and currently manages signed zones for three large top level domains: .BIZ, .US, and .CO. Registrars are provided with the ability to submit and manage DS records using EPP, or through a web GUI. Additional information on DNSSEC, including the management of security extensions is found in the response to Question 43. Data Escrow Data Escrow will be performed in compliance with all ICANN requirements in conjunction with an approved Data Escrow provider. The Data Escrow service will: Protect against data loss Follow industry best practices Ensure easy, accurate, and timely retrieval and restore capability in the event of a hardware failure Minimizes the impact of software or business failure. Additional information on the Data Escrow service is provided in the response to Question 38. Dissemination of Zone Files using Dynamic Updates Dissemination of zone files will be provided through a dynamic, near real-time process. Updates will be performed within the specified performance levels. The proven technology ensures that updates pushed to all nodes within a few minutes of the changes being received by the SRS. Additional information on the DNS updates may be found in the response to Question 35. Access to Bulk Zone Files Northwestern Mutual MU TLD Registry will provide third-party access to the bulk zone file in accordance with Specification 4, Section 2 of the Registry Agreement. Credentialing and dissemination of the zone files will be facilitated through the Central Zone Data Access Provider. Dynamic WHOIS Updates Updates to records in the WHOIS database will be provided via dynamic, near real-time updates. Guaranteed delivery message oriented middleware is used to ensure each individual WHOIS server is refreshed with dynamic updates. This component ensures that all WHOIS servers are kept current as changes occur in the SRS, while also decoupling WHOIS from the SRS. Additional information on WHOIS updates is presented in response to Question 26. IPv6 Support The .MUTUAL registry will provide IPv6 support in the following registry services: SRS, WHOIS, and DNS⁄DNSSEC. In addition, the registry supports the provisioning of IPv6 AAAA records. A detailed description on IPv6 is presented in the response to Question 36. Required Rights Protection Mechanisms Northwestern Mutual MU TLD Registry will provide all ICANN required Rights Mechanisms, including: Trademark Claims Service Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) Registration Restriction Dispute Resolution Procedure (RRDRP) UDRP URS Sunrise service More information is presented in the response to Question 29. Internationalized Domain Names (IDN) IDN registrations are provided in full compliance with the IDNA protocol. Neustar possesses extensive experience offering IDN registrations in numerous TLDs, and its IDN implementation uses advanced technology to accommodate the unique bundling needs of certain languages. Character mappings are easily constructed to block out characters that may be deemed as confusing to users. A detailed description of the IDN implementation is presented in response to Question 44. 23.3 Unique Services The only unique service that Northwestern Mutual MU TLD Registry is considering at this time is the potential imposition of an annual cost recovery based fee to validate registrars that will be providing domain name registration services in the .MUTUAL gTLD.
An additional service which applicant may offer, commonly used in the marketplace today, is the use of RFPs (Request for Proposals) and Auctions to determine string allocation in appropriate circumstances. 23.4 Security or Stability Concerns All services offered are standard registry services that have no known security or stability concerns. Neustar has demonstrated a strong track record of security and stability within the industry.
Demonstration of Technical & Operational Capability
24. Shared Registration System (SRS) Performance
24.1 Introduction Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) has partnered with Neustar, Inc. (“Neustar”) an experienced TLD Registry Operator, for the operation of the .MUTUAL registry. Northwestern Mutual MU TLD Registry is confident that the plan in place for the operation of a robust and reliable Shared Registration System (SRS) as currently provided by Neustar will satisfy the criterion established by ICANN. Neustar built its SRS from the ground up as an EPP-based platform and has been operating it reliably and at scale since 2001. The software currently provides registry services to five TLDs (.BIZ, .US, TEL, .CO, and .TRAVEL) and is used to provide gateway services to the .CN and .TW registries. Neustar’s state-of-the-art registry has a proven track record of being secure, stable, and robust. It manages more than 6 million domains, and has over 300 registrars connected today. The following describes a detailed plan for a robust and reliable SRS that meets all ICANN requirements including compliance with Specifications 6 and 10. 24.2 The Plan for Operation of a Robust and Reliable SRS High-level SRS System Description The SRS to be used for .MUTUAL will leverage a production-proven, standards-based, highly reliable and high-performance domain name registration and management system that fully meets or exceeds the requirements as identified in the New gTLD Applicant Guidebook. The SRS is the central component of any registry implementation and its quality, reliability, and capabilities are essential to the overall stability of the TLD. Neustar has a documented history of deploying SRS implementations with proven and verifiable performance, reliability, and availability. The SRS adheres to all industry standards and protocols. By leveraging an existing SRS platform, Northwestern Mutual MU TLD Registry is mitigating the significant risks and costs associated with the development of a new system. Highlights of the SRS include: State-of-the-art, production-proven, multi-layer design; Ability to rapidly and easily scale from low to high volume as a TLD grows; Fully redundant architecture at two sites; Support for IDN registrations in compliance with all standards; Use by over 300 Registrars; EPP connectivity over IPv6; Performance being measured using 100% of all production transactions (not sampling); and SRS Systems, Software, Hardware, and Interoperability. The systems and software that the registry operates on are a critical element to providing a high quality of service. If the systems are of poor quality, if they are difficult to maintain and operate, or if the registry personnel are unfamiliar with them, the registry will be prone to outages. Neustar has a decade of experience operating registry infrastructure to extremely high service level requirements. The infrastructure is designed using best of breed systems and software. Much of the application software that performs registry-specific operations was developed by the current engineering team and as a result, the team is intimately familiar with its operations. The architecture is highly scalable and provides the same high level of availability and performance as volumes increase. It combines load-balancing technology with scalable server technology to provide a cost effective and efficient method for scaling. The registry is able to limit the ability of any one registrar from adversely impacting other registrars by consuming too many resources due to excessive EPP transactions. The system uses network layer 2 level packet shaping to limit the number of simultaneous connections registrars can open to the protocol layer. All interaction with the registry is recorded in log files. Log files are generated at each layer of the system. These log files record at a minimum: The IP address of the client; Timestamp; Transaction Details; and Processing Time. In addition to logging of each and every transaction with the SRS, Neustar maintains audit records, in the database, of all transformational transactions. These audit records allow the registry, in support of Northwestern Mutual MU TLD Registry, to produce a complete history of changes for any domain name. SRS Design The SRS incorporates a multi-layer architecture that is designed to mitigate risks and easily scale as volumes increase. The three layers of the SRS are: Protocol Layer; Business Policy Layer; and Database. Each of the layers is described below. Protocol Layer The first layer is the protocol layer, which includes the EPP interface to registrars. It consists of a high availability farm of load-balanced EPP servers. The servers are designed to be fast processors of transactions. The servers perform basic validations and then feed information to the business policy engines as described below. The protocol layer is horizontally scalable as dictated by volume. The EPP servers authenticate against a series of security controls before granting service, as follows: The registrar’s host exchanges keys to initiates a TLS handshake session with the EPP server. The registrar’s host must provide credentials to determine proper access levels. The registrar’s IP address must be preregistered in the network firewalls and traffic-shapers. Business Policy Layer The Business Policy Layer is the “brain” of the registry system. Within this layer, the policy engine servers perform rules-based processing as defined through configurable attributes. This process takes individual transactions, applies various validation and policy rules, persists data, and dispatches notification through the central database in order to publish to various external systems. External systems fed by the Business Policy Layer include back-end processes such as dynamic update of DNS, WHOIS, and Billing. Similar to the EPP protocol farm, the SRS consists of a farm of application servers within this layer. This design ensures that there is sufficient capacity to process every transaction in a manner that meets or exceeds all service level requirements. Some registries couple the business logic layer directly in the protocol layer or within the database. This architecture limits the ability to scale the registry. Using a decoupled architecture enables the load to be distributed among farms of inexpensive servers that can be scaled up or down as demand changes. The SRS today processes over 30 million EPP transactions daily. Database The database is the third core component of the SRS. The primary function of the SRS database is to provide highly reliable, persistent storage for all registry information required for domain registration services. The database is highly secure, with access limited to transactions from authenticated registrars, trusted application-server processes, and highly restricted access by the registry database administrators. A full description of the database can be found in response to Question 33. See attachment: Figure 24-1, which depicts the overall SRS architecture including network components. This multi-layer architecture is EPP-compliant, meets all applicable RFCs, and its development follows industry best-practices. Number of Servers As depicted in the SRS architecture diagram above, Neustar operates a high availability architecture where at each level of the stack there are no single points of failures. Each of the network level devices run with dual pairs, as do the databases. For the .MUTUAL registry, the SRS will operate with 8 protocol servers and 6 policy engine servers. These expand horizontally as volume increases due to additional TLDs, increased load, and through organic growth. In addition to the SRS servers described above, there are multiple back-end servers for services such as DNS and WHOIS. These are discussed in detail within those respective response sections. Description of Interconnectivity with Other Registry Systems The core SRS service interfaces with other external systems via Neustar’s external systems layer. The services that the SRS interfaces with include: WHOIS; DNS; Billing; and Data Warehouse (Reporting and Data Escrow). Other external interfaces may be deployed to meet the unique needs of a TLD. At this time there are no additional interfaces planned for .MUTUAL. The SRS includes an “External Notifier” concept in its business policy engine as a message dispatcher. This design allows time-consuming back-end processing to be decoupled from critical online registrar transactions. Using an External Notifier solution, the registry can utilize “control levers” that allow it to tune or to disable processes to ensure optimal performance at all times. For example, during the early minutes of a TLD launch, when unusually high volumes of transactions are expected, the registry can elect to suspend processing of one or more back-end systems in order to ensure that greater processing power is available to handle the increased load requirements. This proven architecture has been used with numerous TLD launches, some of which have involved the processing of over tens of millions of transactions in the opening hours. The following are the standard three External Notifiers used the SRS: WHOIS External Notifier The WHOIS External Notifier dispatches a work item for any EPP transaction that may potentially have an impact on WHOIS. It is important to note that, while the WHOIS External Notifier feeds the WHOIS system, it intentionally does not have visibility into the actual contents of the WHOIS system. The WHOIS External Notifier serves just as a tool to send a signal to the WHOIS system that a change is ready to occur. The WHOIS system possesses the intelligence and data visibility to know exactly what needs to change in WHOIS. See response to Question 26 for greater detail. DNS External Notifier The DNS External Notifier dispatches a work item for any EPP transaction that may potentially have an impact on DNS. Like the WHOIS External Notifier, the DNS External Notifier does not have visibility into the actual contents of the DNS zones. The work items that are generated by the notifier indicate to the dynamic DNS update sub-system that a change occurred that may impact DNS. That DNS system has the ability to decide what actual changes must be propagated out to the DNS constellation. See response to Question 35 for greater detail. Billing External Notifier The Billing External Notifier is responsible for sending all billable transactions to the downstream financial systems for billing and collection. This External Notifier contains the necessary logic to determine what types of transactions are billable. The financial systems use this information to apply appropriate debits and credits based on registrar. Data Warehouse The Data Warehouse is responsible for managing reporting services, including registrar reports, business intelligence dashboards, and the processing of Data Escrow files. The Reporting Database is used to create both internal and external reports, primarily to support registrar billing and contractual reporting requirement. The Data Warehouse databases are updated on a daily basis with full copies of the production SRS data. Frequency of Synchronization between Servers The External Notifiers discussed above perform updates in near real-time, well within the prescribed service level requirements. As transactions from registrars update the core SRS, update notifications are pushed to the external systems such as DNS and WHOIS. These updates are typically live in the external system within 2-3 minutes. Synchronization Scheme (e.g., hot standby, cold standby) Neustar operates two hot databases within the data center that is operating in primary mode. These two databases are kept in sync via synchronous replication. Additionally, there are two databases in the secondary data center. These databases are updated in real time through asynchronous replication. This model allows for high performance while also ensuring protection of data. See response to Question 33 for greater detail. Compliance with Specification 6 Section 1.2 The SRS implementation for .MUTUAL is fully compliant with Specification 6, including section 1.2. EPP Standards are described and embodied in a number of IETF RFCs, ICANN contracts and practices, and Registry-Registrar Agreements. Extensible Provisioning Protocol or EPP is defined by a core set of RFCs that standardize the interface that make up the registry-registrar model. The SRS interface supports EPP 1.0 as defined in the following RFCs shown in Table 24-1. See attachment: Table 24-1. Additional information on the EPP implementation and compliance with RFCs can be found in the response to Question 25. Compliance with Specification 10 Specification 10 of the New TLD Registry Agreement defines the performance specifications of the TLD, including service level requirements related to DNS, RDDS (WHOIS), and EPP. The requirements include both availability and transaction response time measurements. As an experienced Registry Operator, Neustar has a long and verifiable track record of providing registry services that consistently exceed the performance specifications stipulated in ICANN agreements. This same high level of service will be provided for the .MUTUAL registry. The following section describes Neustar’s experience and its capabilities to meet the requirements in the new agreement. To properly measure the technical performance and progress of TLDs, Neustar collects data on key essential operating metrics. These measurements are key indicators of the performance and health of the registry. Neustar’s current .BIZ SLA commitments are among the most stringent in the industry today, and exceed the requirements for new TLDs. Table 24-2 compares the current SRS performance levels compared to the requirements for new TLDs, and clearly demonstrates the ability of the SRS to exceed those requirements. See attachment: Table 24-2. Their ability to commit and meet such high performance standards is a direct result of their philosophy towards operational excellence. See response to Question 31 for a full description of their philosophy for building and managing for performance. 24.3 Resourcing Plans The development, customization, and on-going support of the SRS are the responsibility of a combination of technical and operational teams, including: Development⁄Engineering; Database Administration; Systems Administration; and Network Engineering. Additionally, if customization or modifications are required, the Product Management and Quality Assurance teams will be involved in the design and testing. Finally, the Network Operations and Information Security play an important role in ensuring the systems involved are operating securely and reliably. The necessary resources will be pulled from the pool of operational resources described in detail in the response to Question 31. Neustar’s SRS implementation is very mature, and has been in production for over 10 years. As such, very little new development related to the SRS will be required for the implementation of the .MUTUAL registry. The following resources are available from those teams: Development⁄Engineering – 19 employees Database Administration – 10 employees Systems Administration – 24 employees Network Engineering – 5 employees The resources are more than adequate to support the SRS needs of all the TLDs operated by Neustar, including the .MUTUAL registry.
25. Extensible Provisioning Protocol (EPP)
25.1 Introduction Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) back-end registry operator, Neustar, Inc. (“Neustar”) has over 10 years of experience operating EPP-based registries. They deployed one of the first EPP registries in 2001 with the launch of .BIZ. In 2004, they were the first gTLD to implement EPP 1.0. Over the last ten years Neustar has implemented numerous extensions to meet various unique TLD requirements. Neustar will leverage its extensive experience to ensure Northwestern Mutual MU TLD Registry is provided with an unparalleled EPP-based registry. The following discussion explains the EPP interface, which will be used for the DELL registry. This interface exists within the protocol farm layer as described in Question 24 and is depicted in Figure 25-1. See attachment: Figure 25-1. The protocol layer is responsible for ensuring transactions comply with the appropriate protocol. 25.2 EPP Interface Registrars are provided with two different interfaces for interacting with the registry. Both are EPP-based, and both contain all the functionality necessary to provision and manage domain names. The primary mechanism is an EPP interface to connect directly with the registry. This is the interface registrars will use for most of their interactions with the registry. However, an alternative web GUI (Registry Administration Tool) that can also be used to perform EPP transactions will be provided. The primary use of the Registry Administration Tool is for performing administrative or customer support tasks. The main features of the EPP implementation are: Standards Compliance: The EPP XML interface is compliant to the EPP RFCs. As future EPP RFCs are published or existing RFCs are updated, Neustar makes changes to the implementation keeping in mind of any backward compatibility issues. Scalability: The system is deployed keeping in mind that it may be required to grow and shrink the footprint of the Registry system for a particular TLD. Fault-tolerance: The EPP servers are deployed in two geographically separate data centers to provide for quick failover capability in case of a major outage in a particular data center. The EPP servers adhere to strict availability requirements defined in the SLAs. Configurability: The EPP extensions are built in a way that they can be easily configured to turn on or off for a particular TLD. Extensibility: The software is built ground-up using object-oriented design. This allows for easy extensibility of the software without risking the possibility of the change rippling through the whole application. Auditable: The system stores detailed information about EPP transactions from provisioning to DNS and WHOIS publishing. In case of a dispute regarding a name registration, the Registry can provide comprehensive audit information on EPP transactions. Security: The system provides IP address-based access control, client credential-based authorization test, digital certificate exchange, and connection limiting to the protocol layer. 25.3 Compliance with RFCs and Specifications The registry-registrar model is described and embodied in a number of IETF RFCs, ICANN contracts and practices, and registry-registrar agreements. As shown in Table 25-1, EPP is defined by the core set of RFCs that standardize the interface that registrars use to provision domains with the SRS. As a core component of the SRS architecture, the implementation is fully compliant with all EPP RFCs. See attachment: Table 25-1. Neustar ensures compliance with all RFCs through a variety of processes and procedures. Members from the engineering and standards teams actively monitor and participate in the development of RFCs that impact the registry services, including those related to EPP. When new RFCs are introduced or existing ones are updated, the team performs a full compliance review of each system impacted by the change. Furthermore, all code releases include a full regression test that includes specific test cases to verify RFC compliance. Neustar has a long history of providing exceptional service that exceeds all performance specifications. The SRS and EPP interface have been designed to exceed the EPP specifications defined in Specification 10 of the Registry Agreement and profiled in Table 25-2. Evidence of Neustar’s ability to perform at these levels can be found in the .biz monthly progress reports found on the ICANN website. See attachment: Table 25-2. EPP Toolkits Toolkits, under open source licensing, are freely provided to registrars for interfacing with the SRS. Both Java and C++ toolkits will be provided, along with the accompanying documentation. The Registrar Tool Kit (RTK) is a software development kit (SDK) that supports the development of a registrar software system for registering domain names in the registry using EPP. The SDK consists of software and documentation as described below. The software consists of working Java and C++ EPP common APIs and samples that implement the EPP core functions and EPP extensions used to communicate between the registry and registrar. The RTK illustrates how XML requests (registration events) can be assembled and forwarded to the registry for processing. The software provides the registrar with the basis for a reference implementation that conforms to the EPP registry-registrar protocol. The software component of the SDK also includes XML schema definition files for all Registry EPP objects and EPP object extensions. The RTK also includes a “dummy” server to aid in the testing of EPP clients. The accompanying documentation describes the EPP software package hierarchy, the object data model, and the defined objects and methods (including calling parameter lists and expected response behavior). New versions of the RTK are made available from time to time to provide support for additional features as they become available and support for other platforms and languages. 25.3 Proprietary EPP Extensions The .MUTUAL registry will not include proprietary EPP extensions. Neustar has implemented various EPP extensions for both internal and external use in other TLD registries. These extensions use the standard EPP extension framework described in RFC 5730. Table 25-3 provides a list of extensions developed for other TLDs. Should the .MUTUAL registry require an EPP extension at some point in the future, the extension will be implemented in compliance with all RFC specifications including RFC 3735. See attachment: Table 25-3. The full EPP schema to be used in the .MUTUAL registry is attached in the document titled “EPP Schema.” 25.4 Resourcing Plans The development and support of EPP is largely the responsibility of the Development⁄Engineering and Quality Assurance teams. As an experience registry operator with a fully developed EPP solution, on-going support is largely limited to periodic updates to the standard and the implementation of TLD specific extensions. The necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. The following resources are available from those teams: Development⁄Engineering – 19 employees Quality Assurance – 7 employees. These resources are more than adequate to support any EPP modification needs of the .MUTUAL registry.
26.1 Introduction Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) recognizes the importance of an accurate, reliable, and up-to-date WHOIS database to governments, law enforcement, intellectual property holders, and the public as a whole and is firmly committed to complying with all of the applicable WHOIS specifications for data objects, bulk access, and lookups as defined in Specifications 4 and 10 of the Registry Agreement. Northwestern Mutual MU TLD Registryʹs back-end registry services provider, Neustar, Inc. (“Neustar”), has extensive experience providing ICANN and RFC-compliant WHOIS services for each of the TLDs that it operates both as a Registry Operator for gTLDs and ccTLDs, and as a back-end registry services provider. As one of the first “thick” Registry Operators in the gTLD space, Neustar’s WHOIS service has been designed from the ground up to display as much information as required by a TLD and to respond to a very stringent availability and performance requirement. Some of the key features of .MUTUAL’s solution include: Fully compliant with all relevant RFCs including 3912; Production proven, highly flexible, and scalable with a track record of 100% availability over the past 10 years; Exceeds current and proposed performance specifications; Supports dynamic updates with the capability of doing bulk updates; and Geographically distributed sites to provide greater stability and performance. In addition, .MUTUALʹs thick-WHOIS solution also provides for additional search capabilities and mechanisms to mitigate potential forms of abuse as discussed below. (e.g., IDN, registrant data). 26.2 Software Components The WHOIS architecture comprises the following components: An in-memory database local to each WHOIS node: To provide for the performance needs, the WHOIS data is served from an in-memory database indexed by searchable keys. Redundant servers: To provide for redundancy, the WHOIS updates are propagated to a cluster of WHOIS servers that maintain an independent copy of the database. Attack resistant: To ensure that the WHOIS system cannot be abused using malicious queries or DOS attacks, the WHOIS server is only allowed to query the local database and rate limits on queries based on IPs and IP ranges can be readily applied. Accuracy auditor: To ensure the accuracy of the information served by the WHOIS servers, a daily audit is done between the SRS information and the WHOIS responses for the domain names which are updated during the last 24-hour period. Any discrepancies are resolved proactively. Modular design: The WHOIS system allows for filtering and translation of data elements between the SRS and the WHOIS database to allow for customizations. Scalable architecture: The WHOIS system is scalable and has a very small footprint. Depending on the query volume, the deployment size can grow and shrink quickly. Flexible: It is flexible enough to accommodate thin, thick, or modified thick models and can accommodate any future ICANN policy, such as different information display levels based on user categorization. SRS master database: The SRS database is the main persistent store of the registry information. The Update Agent computes what WHOIS updates need to be pushed out. A publish-subscribe mechanism then takes these incremental updates and pushes to all the WHOIS slaves that answer queries. 26.3 Compliance with RFC and Specifications 4 and 10 Neustar has been running thick-WHOIS Services for over 10+ years in full compliance with RFC 3912 and with Specifications 4 and 10 of the Registry Agreement. RFC 3912 is a simple text-based protocol over TCP that describes the interaction between the server and client on port 43. Neustar built a home-grown solution for this service. It processes millions of WHOIS queries per day. See attachment: Table 26-1, which describes Neustar’s compliance with Specifications 4 and 10. Neustar ensures compliance with all RFCs through a variety of processes and procedures. Members from the engineering and standards teams actively monitor and participate in the development of RFCs that impact the registry services, including those related to WHOIS. When new RFCs are introduced or existing ones are updated, the team performs a full compliance review of each system impacted by the change. Furthermore, all code releases include a full regression test that includes specific test cases to verify RFC compliance. 26.4 High-level WHOIS System Description 26.4.1 WHOIS Service (port 43) The WHOIS service is responsible for handling port 43 queries. Our WHOIS is optimized for speed using an in-memory database and master-slave architecture between the SRS and WHOIS slaves. The WHOIS service also has built-in support for IDN. If the domain name being queried is an IDN, the returned results include the language of the domain name, the domain name’s UTF-8 encoded representation along with the Unicode code page. 26.4.2 Web Page for WHOIS queries In addition to the WHOIS Service on port 43, Neustar provides a Web-based WHOIS application (www.whois.tld). It is an intuitive and easy to use application for the general public to use. The WHOIS Web-application provides all of the features available in the port 43 WHOIS. This includes full and partial search on: Domain names; Nameservers; Registrant, Technical, and Administrative Contacts; and Registrars. It also provides features not available on the port 43 service. These include: Redemption Grace Period calculation: Based on the registry’s policy, domains in pendingDelete can be restorable or scheduled for release depending on the date⁄time the domain went into pendingDelete. For these domains, the Web-based WHOIS displays “Restorable” or “Scheduled for Release” to clearly show this additional status to the user. Extensive support for international domain names (IDN); Ability to perform WHOIS lookups on the actual Unicode IDN; Display of the actual Unicode IDN in addition to the ACE-encoded name; A Unicode to Punycode and Punycode to Unicode translator; An extensive FAQ; and A list of upcoming domain deletions. 26.5 IT and Infrastructure Resources As described above, the WHOIS architecture uses a workflow that decouples the update process from the SRS. This ensures SRS performance is not adversely affected by the load requirements of dynamic updates. It is also decoupled from the WHOIS lookup agent to ensure the WHOIS service is always available and performing well for users. Each of Neustar’s geographically diverse WHOIS sites use: Firewalls, to protect this sensitive data; Dedicated servers for MQ Series, to ensure guaranteed delivery of WHOIS updates; Packetshaper for source IP address-based bandwidth limiting; Load balancers to distribute query load; and Multiple WHOIS servers for maximizing the performance of WHOIS service. The WHOIS service uses HP BL 460C servers, each with 2 X Quad Core CPU and a 64GB of RAM. The existing infrastructure has 6 servers, but is designed to be easily scaled with additional servers should it be needed. See attachment: Figure 26-1, which depicts the different components of the WHOIS architecture. WHOIS is decoupled from the architecture to protect production databases and increased overall systems security. 26.6 Interconnectivity with Other Registry System As described in Question 24 about the SRS and further in response to Question 31, “Technical Overview,” when an update is made by a registrar that impacts WHOIS data, a trigger is sent to the WHOIS system by the external notifier layer. The update agent processes these updates, transforms the data if necessary and then uses messaging-oriented middleware to publish all updates to each WHOIS slave. The local update agent accepts the update and applies it to the local in-memory database. A separate auditor compares the data in WHOIS and the SRS daily and monthly to ensure accuracy of the published data. 26.7 Frequency of Synchronization between Servers Updates from the SRS, through the external notifiers, to the constellation of independent WHOIS slaves happens in real-time via an asynchronous publish⁄subscribe messaging architecture. The updates are guaranteed to be updated in each slave within the required SLA of 95% ≤ 60 minutes. Please note that Neustar’s current architecture is built towards the stricter SLAs (95% ≤ 15 minutes) of .BIZ. The vast majority of updates tend to happen within 2-3 minutes. 26.8 Provision for Searchable WHOIS Capabilities Neustar will create a new Web-based service to address the new search features based on requirements specified in Specification 4 Section 1.8. The application will enable users to search the WHOIS directory using any one or more of the following fields: Domain name; Registrar ID; Contact’s and registrant’s name; Contact’s and registrant’s postal address, including all the sub-fields described in EPP (e.g., street, city, state or province, etc.); and The system will also allow search using non-Latin character sets, which are compliant with IDNA specification. The user will choose one or more search criteria, combine them by Boolean operators (AND, OR, NOT) and provide partial or exact match regular expressions for each of the criterion name-value pairs. The domain names matching the search criteria will be returned to the user. See attachment: Figure 26-2, which shows an architectural depiction of the new service. Neustar’s Web-based service provides new search features based on requirements specified in Specification 4 Section 1.8. To mitigate the risk of this powerful search service being abused by unscrupulous data miners, a layer of security will be built around the query engine, which will allow the registry to identify rogue activities and then take appropriate measures. Potential abuses include, but are not limited to: Data Mining; Unauthorized Access; Excessive Querying; and Denial of Service Attacks. To mitigate the abuses noted above, Neustar will implement any or all of these mechanisms as appropriate: Username-password based authentication; Certificate based authentication; Data encryption; CAPTCHA mechanism to prevent robo invocation of Web query; and Fee-based advanced query capabilities for premium customers. The searchable WHOIS application will adhere to all privacy laws and policies of the .MUTUAL registry. 26.9 Resourcing Plans As with the SRS, the development, customization, and on-going support of the WHOIS service is the responsibility of a combination of technical and operational teams. The primary groups responsible for managing the service include: Development⁄Engineering – 19 employees Database Administration – 10 employees Systems Administration – 24 employees Network Engineering – 5 employees Additionally, if customization or modifications are required, the Product Management and Quality Assurance teams will also be involved. Finally, the Network Operations and Information Security play an important role in ensuring the systems involved are operating securely and reliably. The necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. Neustar’s WHOIS implementation is very mature, and has been in production for over 10 years. As such, very little new development will be required to support the implementation of the .MUTUAL registry. The resources are more than adequate to support the WHOIS needs of all the TLDs operated by Neustar, including the .MUTUAL registry.
27. Registration Life Cycle
27.1 Registration Life Cycle Introduction Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) will follow the lifecycle and business rules found in the majority of gTLDs today. Our back-end operator, Neustar, has over ten years of experience managing numerous TLDs that utilize standard and unique business rules and lifecycles. This section describes the business rules, registration states, and the overall domain lifecycle that will be use for .MUTUAL. Domain Lifecycle - Description The registry will use the EPP 1.0 standard for provisioning domain names, contacts, and hosts. Each domain record is comprised of three registry object types: domain, contacts, and hosts. Domains, contacts, and hosts may be assigned various EPP defined statuses indicating either a particular state or restriction placed on the object. Some statuses may be applied by the Registrar; other statuses may only be applied by the Registry. Statuses are an integral part of the domain lifecycle and serve the dual purpose of indicating the particular state of the domain and indicating any restrictions placed on the domain. The EPP standard defines 17 statuses, however only 14 of these statuses will be used in the .MUTUAL registry per the defined .MUTUAL business rules. The following is a brief description of each of the statuses. Server statuses may only be applied by the Registry, and client statuses may be applied by the Registrar. OK – Default status applied by the Registry. Inactive – Default status applied by the Registry if the domain has less than 2 nameservers. PendingCreate – Status applied by the Registry upon processing a successful Create command, and indicates further action is pending. This status will not be used in the .MUTUAL registry. PendingTransfer – Status applied by the Registry upon processing a successful Transfer request command, and indicates further action is pending. PendingDelete – Status applied by the Registry upon processing a successful Delete command that does not result in the immediate deletion of the domain, and indicates further action is pending. PendingRenew – Status applied by the Registry upon processing a successful Renew command that does not result in the immediate renewal of the domain, and indicates further action is pending. This status will not be used in the .MUTUAL registry. PendingUpdate – Status applied by the Registry if an additional action is expected to complete the update, and indicates further action is pending. This status will not be used in the .MUTUAL registry. Hold – Removes the domain from the DNS zone. UpdateProhibited – Prevents the object from being modified by an Update command. TransferProhibited – Prevents the object from being transferred to another Registrar by the Transfer command. RenewProhibited – Prevents a domain from being renewed by a Renew command. DeleteProhibited – Prevents the object from being deleted by a Delete command. The lifecycle of a domain begins with the registration of the domain. All registrations must follow the EPP standard, as well as the specific business rules described in the response to Question 18 above. Upon registration a domain will either be in an active or inactive state. Domains in an active state are delegated and have their delegation information published to the zone. Inactive domains either have no delegation information or their delegation information in not published in the zone. Following the initial registration of a domain, one of five actions may occur during its lifecycle: Domain may be updated Domain may be deleted, either within or after the add-grace period Domain may be renewed at anytime during the term Domain may be auto-renewed by the Registry Domain may be transferred to another registrar. Each of these actions may result in a change in domain state. This is described in more detail in the following section. Every domain must eventually be renewed, auto-renewed, transferred, or deleted. A registrar may apply EPP statuses described above to prevent specific actions such as updates, renewals, transfers, or deletions. 27.1.1 Registration States Domain Lifecycle – Registration States As described above, the .MUTUAL registry will implement a standard domain lifecycle found in most gTLD registries today. There are five possible domain states: Active Inactive Locked Pending Transfer Pending Delete All domains are always in either an Active or Inactive state, and throughout the course of the lifecycle may also be in a Locked, Pending Transfer, and Pending Delete state. Specific conditions such as applied EPP policies and registry business rules will determine whether a domain can be transitioned between states. Additionally, within each state, domains may be subject to various timed events such as grace periods, and notification periods. Active State The active state is the normal state of a domain and indicates that delegation data has been provided and the delegation information is published in the zone. A domain in an Active state may also be in the Locked or Pending Transfer states. Inactive State The Inactive state indicates that a domain has not been delegated or that the delegation data has not been published to the zone. A domain in an Inactive state may also be in the Locked or Pending Transfer states. By default all domain in the Pending Delete state are also in the Inactive state. Locked State The Locked state indicates that certain specified EPP transactions may not be performed to the domain. A domain is considered to be in a Locked state if at least one restriction has been placed on the domain; however up to eight restrictions may be applied simultaneously. Domains in the Locked state will also be in the Active or Inactive, and under certain conditions may also be in the Pending Transfer or Pending Delete states. Pending Transfer State The Pending Transfer state indicates a condition in which there has been a request to transfer the domain from one registrar to another. The domain is placed in the Pending Transfer state for a period of time to allow the current (losing) registrar to approve (ack) or reject (nack) the transfer request. Registrars may only nack requests for reasons specified in the Inter-Registrar Transfer Policy. Pending Delete State The Pending Delete State occurs when a Delete command has been sent to the Registry after the first 5 days (120 hours) of registration. The Pending Delete period is 35-days during which the first 30-days the name enters the Redemption Grace Period (RGP) and the last 5-days guarantee that the domain will be purged from the Registry Database and available to public pool for registration on a first come, first serve basis. 27.1.2 Typical Registration Lifecycle Activities Domain Creation Process The creation (registration) of domain names is the fundamental registry operation. All other operations are designed to support or complement a domain creation. The following steps occur when a domain is created. Contact objects are created in the SRS database. The same contact object may be used for each contact type, or they may all be different. If the contacts already exist in the database this step may be skipped. Nameservers are created in the SRS database. Nameservers are not required to complete the registration process; however any domain with less than 2 name servers will not be resolvable. The domain is created using the each of the objects created in the previous steps. In addition, the term and any client statuses may be assigned at the time of creation. The actual number of EPP transactions needed to complete the registration of a domain name can be as few as one and as many as 40. The latter assumes seven distinct contacts and 13 nameservers, with Check and Create commands submitted for each object. Update Process Registry objects may be updated (modified) using the EPP Modify operation. The Update transaction updates the attributes of the object. For example, the Update operation on a domain name will only allow the following attributes to be updated: Domain statuses Registrant ID Administrative Contact ID Billing Contact ID Technical Contact ID Nameservers AuthInfo Additional Registrar provided fields The Update operation will not modify the details of the contacts. Rather it may be used to associate a different contact object (using the Contact ID) to the domain name. To update the details of the contact object the Update transaction must be applied to the contact itself. For example, if an existing registrant wished to update the postal address, the Registrar would use the Update command to modify the contact object, and not the domain object. Renew Process The term of a domain may be extended using the EPP Renew operation. ICANN policy general establishes the maximum term of a domain name to be 10 years, and Neustar recommends not deviating from this policy. A domain may be renewed⁄extended at any point time, even immediately following the initial registration. The only stipulation is that the overall term of the domain name may not exceed 10 years. If a Renew operation is performed with a term value will extend the domain beyond the 10-year limit, the Registry will reject the transaction entirely. Transfer Process The EPP Transfer command is used for several domain transfer related operations: Initiate a domain transfer Cancel a domain transfer Approve a domain transfer Reject a domain transfer To transfer a domain from one Registrar to another the following process is followed: The gaining (new) Registrar submits a Transfer command, which includes the AuthInfo code of the domain name. If the AuthInfo code is valid and the domain is not in a status that does not allow transfers the domain is placed into PendingTransfer status A poll message notifying the losing Registrar of the pending transfer is sent to the Registrar’s message queue The domain remains in PendingTransfer status for up to 120 hours, or until the losing (current) Registrar Acks (approves) or Nack (rejects) the transfer request If the losing Registrar has not Acked or Nacked the transfer request within the 120 hour timeframe, the Registry auto-approves the transfer The requesting Registrar may cancel the original request up until the transfer has been completed. A transfer adds an additional year to the term of the domain. In the event that a transfer will cause the domain to exceed the 10-year maximum term, the Registry will add a partial term up to the 10 year limit. Unlike with the Renew operation, the Registry will not reject a transfer operation. Deletion Process A domain may be deleted from the SRS using the EPP Delete operation. The Delete operation will result in either the domain being immediately removed from the database or the domain being placed in PendingDelete status. The outcome is dependent on when the domain is deleted. If the domain is deleted within the first five days (120 hours) of registration, the domain is immediately removed from the database. A deletion at any other time will result in the domain being placed in PendingDelete status and entering the Redemption Grace Period (RGP). Additionally, domains that are deleted within five days (120) hours of any billable (add, renew, transfer) transaction may be deleted for credit. 27.1.3 Applicable Time Elements The following section explains the time elements that are involved Grace Periods There are six grace periods: Add-Delete Grace Period (AGP) Renew-Delete Grace Period Transfer-Delete Grace Period Auto-Renew-Delete Grace Period Auto-Renew Grace Period Redemption Grace Period (RGP). The first four grace periods listed above are designed to provide the Registrar with the ability to cancel a revenue transaction (add, renew, or transfer) within a certain period of time and receive a credit for the original transaction. The following describes each of these grace periods in detail. Add-Delete Grace Period The APG is associated with the date the Domain was registered. Domains may be deleted for credit during the initial 120 hours of a registration, and the Registrar will receive a billing credit for the original registration. If the domain is deleted during the Add Grace Period, the domain is dropped from the database immediately and a credit is applied to the Registrar’s billing account. Renew-Delete Grace Period The Renew-Delete Grace Period is associated with the date the Domain was renewed. Domains may be deleted for credit during the 120 hours after a renewal. The grace period is intended to allow Registrars to correct domains that were mistakenly renewed. It should be noted that domains that are deleted during the renew grace period will be placed into PendingDelete and will enter the RGP (see below). Transfer-Delete Grace Period The Transfer-Delete Grace Period is associated with the date the Domain was transferred to another Registrar. Domains may be deleted for credit during the 120 hours after a transfer. It should be noted that domains that are deleted during the renew grace period will be placed into PendingDelete and will enter the RGP. A deletion of domain after a transfer is not the method used to correct a transfer mistake. Domains that have been erroneously transferred or hijacked by another party can be transferred back to the original registrar through various means including contacting the Registry. Auto-Renew-Delete Grace Period The Auto-Renew-Delete Grace Period is associated with the date the Domain was auto-renewed. Domains may be deleted for credit during the 120 hours after an auto-renewal. The grace period is intended to allow Registrars to correct domains that were mistakenly auto-renewed. It should be noted that domains that are deleted during the auto-renew delete grace period will be placed into PendingDelete and will enter the RGP. Auto-Renew Grace Period The Auto-Renew Grace Period is a special grace period intended to provide registrants with an extra amount of time, beyond the expiration date, to renew their domain name. The grace period lasts for 45 days from the expiration date of the domain name. Registrars are not required to provide registrants with the full 45 days of the period. Redemption Grace Period The RGP is a special grace period that enables Registrars to restore domains that have been inadvertently deleted but are still in PendingDelete status within the Redemption Grace Period. All domains enter the RGP except those deleted during the AGP. The RGP period is 30 days, during which time the domain may be restored using the EPP RenewDomain command as described below. Following the 30day RGP period the domain will remain in PendingDelete status for an additional five days, during which time the domain may NOT be restored. The domain is released from the SRS, at the end of the 5-day non-restore period. A restore fee applies and is detailed in the Billing Section. A renewal fee will be automatically applied for any domain past expiration. Neustar has created a unique restoration process that uses the EPP Renew transaction to restore the domain and fulfill all the reporting obligations required under ICANN policy. The following describes the restoration process. 27.2 State Diagram See attachment: Figure 27-1, which provides a description of the registration lifecycle. The different states of the lifecycle are active, inactive, locked, pending transfer, and pending delete. Please refer to section 27.1.1 for detail description of each of these states. The lines between the states represent triggers that transition a domain from one state to another. The details of each trigger are described below: Create: Registry receives a create domain EPP command. WithNS: The domain has met the minimum number of nameservers required by registry policy in order to be published in the DNS zone. WithOutNS: The domain has not met the minimum number of nameservers required by registry policy. The domain will not be in the DNS zone. Remove Nameservers: Domainʹs nameserver(s) is removed as part of an update domain EPP command. The total nameserver is below the minimum number of nameservers required by registry policy in order to be published in the DNS zone. Add Nameservers: Nameserver(s) has been added to domain as part of an update domain EPP command. The total number of nameservers has met the minimum number of nameservers required by registry policy in order to be published in the DNS zone. Delete: Registry receives a delete domain EPP command. DeleteAfterGrace: Domain deletion does not fall within the add grace period. DeleteWithinAddGrace: Domain deletion falls within add grace period. Restore: Domain is restored. Domain goes back to its original state prior to the delete command. Transfer: Transfer request EPP command is received. Transfer Approve⁄Cancel⁄Reject: Transfer requested is approved or cancel or rejected. TransferProhibited: The domain is in clientTransferProhibited and⁄or serverTranferProhibited status. This will cause the transfer request to fail. The domain goes back to its original state. DeleteProhibited: The domain is in clientDeleteProhibited and⁄or serverDeleteProhibited status. This will cause the delete command to fail. The domain goes back to its original state. Note: the locked state is not represented as a distinct state on the diagram as a domain may be in a locked state in combination with any of the other states: inactive, active, pending transfer, or pending delete. 27.2.1 EPP RFC Consistency As described above, the domain lifecycle is determined by ICANN policy and the EPP RFCs. Neustar has been operating ICANN TLDs for the past 10 years consistent and compliant with all the ICANN policies and related EPP RFCs. 27.3 Resources The registration lifecycle and associated business rules are largely determined by policy and business requirements; as such the Product Management and Policy teams will play a critical role in working with Northwestern Mutual MU TLD Registry to determine the precise rules that meet the requirements of the TLD. Implementation of the lifecycle rules will be the responsibility of Development⁄Engineering team, with testing performed by the Quality Assurance team. Neustar’s SRS implementation is very flexible and configurable, and in many case development is not required to support business rule changes. The .MUTUAL registry will be using standard lifecycle rules, and as such no customization is anticipated. However should modifications be required in the future, the necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. The following resources are available from those teams: Development⁄Engineering – 19 employees Registry Product Management – 4 employees These resources are more than adequate to support the development needs of all the TLDs operated by Neustar, including the .MUTUAL registry.
28. Abuse Prevention and Mitigation
28.1 Abuse Prevention and Mitigation Strong abuse prevention of a new gTLD is an important benefit to the Internet community. Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) and its back-end registry services provider, Neustar, Inc. (“Neustar”), agree that a registry must not only aim for the highest standards of technical and operational competence, but also needs to act as a steward of the space on behalf of the Internet community and ICANN in promoting the public interest. Neustar brings extensive experience establishing and implementing registration policies. This experience will be leveraged to help Northwestern Mutual MU TLD Registry combat abusive and malicious domain activity within the new gTLD space. One of those public interest functions for a responsible domain name registry includes working towards the eradication of abusive domain name registrations, including, but not limited to, those resulting from: Illegal or fraudulent actions Spam Phishing Pharming Distribution of malware Fast flux hosting Botnets Distribution of child pornography Online sale or distribution of illegal pharmaceuticals More specifically, although traditionally botnets have used Internet Relay Chat (IRC) servers to control registry and the compromised PCs, or bots, for DDoS attacks and the theft of personal information, an increasingly popular technique, known as fast-flux DNS, allows botnets to use a multitude of servers to hide a key host or to create a highly-available control network. This ability to shift the attacker’s infrastructure over a multitude of servers in various countries creates an obstacle for law enforcement and security researchers to mitigate the effects of these botnets. But a point of weakness in this scheme is its dependence on DNS for its translation services. By taking an active role in researching and monitoring these sorts of botnets, Northwestern Mutual MU TLD Registry’s partner, Neustar, has developed the ability to efficiently work with various law enforcement and security communities to begin a new phase of mitigation of these types of threats. Policies and Procedures to Minimize Abusive Registrations A registry must have the policies, resources, personnel, and expertise in place to combat such abusive DNS practices. As Northwestern Mutual MU TLD Registry’s registry provider, Neustar is at the forefront of the prevention of such abusive practices and is one of the few registry operators to have actually developed and implemented an active “domain takedown” policy. We also believe that a strong program is essential given that registrants have a reasonable expectation that they are in control of the data associated with their domains, especially its presence in the DNS zone. Because domain names are sometimes used as a mechanism to enable various illegitimate activities on the Internet, often the best preventative measure to thwart these attacks is to remove the names completely from the DNS before they can impart harm, not only to the domain name registrant, but also to millions of unsuspecting Internet users. Removing the domain name from the zone has the effect of shutting down all activity associated with the domain name, including the use of all websites and e-mail. The use of this technique should not be entered into lightly. Northwestern Mutual MU TLD Registry has an extensive, defined, and documented process for taking the necessary action of removing a domain from the zone when its presence in the zone poses a threat to the security and stability of the infrastructure of the Internet or the registry. Abuse Point of Contact As required by the Registry Agreement, Northwestern Mutual MU TLD Registry will establish and publish on its website a single abuse point of contact responsible for addressing inquiries from law enforcement and the public related to malicious and abusive conduct. Northwestern Mutual MU TLD Registry will also provide such information to ICANN prior to the delegation of any domain names in the TLD. This information shall consist of, at a minimum, a valid e-mail address dedicated solely to the handling of malicious conduct complaints, and a telephone number and mailing address for the primary contact. We will ensure that this information will be kept accurate and up-to-date and will be provided to ICANN if and when changes are made. In addition, with respect to inquiries from ICANN-Accredited registrars, our registry services provider, Neustar, shall have an additional point of contact, as it does today, handling requests by registrars related to abusive domain name practices. 28.2 Policies Regarding Abuse Complaints One of the key policies each new gTLD registry will need to have is an Acceptable Use Policy that clearly delineates the types of activities that constitute “abuse” and the repercussions associated with an abusive domain name registration. In addition, the policy will be incorporated into the applicable Registry-Registrar Agreement and reserve the right for the registry to take the appropriate actions based on the type of abuse. This will include locking down the domain name, preventing any changes to the contact and nameserver information associated with the domain name, placing the domain name “on hold,” rendering the domain name non-resolvable, transferring to the domain name to another registrar, and⁄or in cases in which the domain name is associated with an existing law enforcement investigation, substituting name servers to collect information about the DNS queries to assist the investigation. Northwestern Mutual MU TLD Registry will adopt an Acceptable Use Policy that clearly defines the types of activities that will not be permitted in the TLD and reserves the right to lock, cancel, transfer, or otherwise suspend or take down domain names violating the Acceptable Use Policy and allow the registry where and when appropriate to share information with law enforcement. Each ICANN-Accredited Registrar must agree to pass through the Acceptable Use Policy to its Resellers (if applicable) and ultimately to the TLD registrants. Below is the registry’s initial Acceptable Use Policy that we will use in connection with the .MUTUAL TLD. .MUTUAL Acceptable Use Policy This Acceptable Use Policy gives the registry the ability to quickly lock, cancel, transfer, or take ownership of any .MUTUAL domain name, either temporarily or permanently, if the domain name is being used in a manner that appears to threaten the stability, integrity, or security of the registry, or any of its registrar partners – and⁄or that may put the safety and security of any registrant or user at risk. The process also allows the registry to take preventive measures to avoid any such criminal or security threats. The Acceptable Use Policy may be triggered through a variety of channels, including, among other things, private complaint, public alert, government or enforcement agency outreach, and the ongoing monitoring by the registry or its partners. In all cases, the registry or its designees will alert registry’s registrar partners about any identified threats, and will work closely with them to bring offending sites into compliance. The following are some (but not all) activities that may be subject to rapid domain compliance: Phishing: the attempt to acquire personally identifiable information by masquerading as a website other than .MUTUAL’s own. Pharming: the redirection of Internet users to websites other than those the user intends to visit, usually through unauthorized changes to the Hosts file on a victim’s computer or DNS records in DNS servers. Dissemination of Malware: the intentional creation and distribution of ʺmaliciousʺ software designed to infiltrate a computer system without the owner’s consent, including, without limitation, computer viruses, worms, key loggers, and Trojans. Fast Flux Hosting: a technique used to shelter Phishing, Pharming, and Malware sites and networks from detection and to frustrate methods employed to defend against such practices, whereby the IP address associated with fraudulent websites are changed rapidly so as to make the true location of the sites difficult to find. Botnetting: the development and use of a command, agent, motor, service, or software which is implemented: (1) to remotely control the computer or computer system of an Internet user without their knowledge or consent, (2) to generate direct denial of service (DDOS) attacks. Malicious Hacking: the attempt to gain unauthorized access (or exceed the level of authorized access) to a computer, information system, user account or profile, database, or security system. Child Pornography: the storage, publication, display, and⁄or dissemination of pornographic materials depicting individuals under the age of majority in the relevant jurisdiction. The registry reserves the right, in its sole discretion, to take any administrative and operational actions necessary, including the use of computer forensics and information security technological services, among other things, in order to implement the Acceptable Use Policy. In addition, the registry reserves the right to deny, cancel, or transfer any registration or transaction, or place any domain name(s) on registry lock, hold, or similar status, that it deems necessary, in its discretion; (1) to protect the integrity and stability of the registry; (2) to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process; (3) to avoid any liability, civil or criminal, on the part of the registry as well as its affiliates, subsidiaries, officers, directors, and employees; (4) per the terms of the registration agreement or (5) to correct mistakes made by the registry or any registrar in connection with a domain name registration. The registry also reserves the right to place upon registry lock, hold, or similar status a domain name during resolution of a dispute. Taking Action Against Abusive and⁄or Malicious Activity The registry is committed to ensuring that those domain names associated with abuse or malicious conduct in violation of the Acceptable Use Policy are dealt with in a timely and decisive manner. These include taking action against those domain names that are being used to threaten the stability and security of the TLD, or are part of a real-time investigation by law enforcement. Once a complaint is received from a trusted source, third party, or detected by the registry, the registry will use commercially reasonable efforts to verify the information in the complaint. If that information can be verified to the best of the ability of the registry, the sponsoring registrar will be notified and be given 12 hours to investigate the activity and either take down the domain name by placing the domain name on hold or by deleting the domain name in its entirety, or providing a compelling argument to the registry to keep the name in the zone. If the registrar has not taken the requested action after the 12-hour period (i.e., is unresponsive to the request or refuses to take action), the registry will place the domain on “ServerHold.” Although this action removes the domain name from the TLD zone, the domain name record still appears in the TLD WHOIS database so that the name and entities can be investigated by law enforcement should they desire to get involved. Coordination with Law Enforcement With the assistance of Neustar as its back-end registry services provider, Northwestern Mutual MU TLD Registry can meet its obligations under Section 2.8 of the Registry Agreement where required to take reasonable steps to investigate and respond to reports from law enforcement and governmental and quasi-governmental agencies of illegal conduct in connection with the use of its TLD. The registry will respond to legitimate law enforcement inquiries within one business day from receiving the request. Such response shall include, at a minimum, an acknowledgement of receipt of the request, questions or comments concerning the request, and an outline of the next steps to be taken by Northwestern Mutual MU TLD Registry for rapid resolution of the request. In the event such request involves any of the activities which can be validated by the registry and involves the type of activity set forth in the Acceptable Use Policy, the sponsoring registrar is then given 12 hours to investigate the activity further and either take down the domain name by placing the domain name on hold or by deleting the domain name in its entirety, or providing a compelling argument to the registry to keep the name in the zone. If the registrar has not taken the requested action after the 12-hour period (i.e., is unresponsive to the request or refuses to take action), the registry will place the domain on “serverHold.” 28.2 Measures for Removal of Orphan Glue Records As the Security and Stability Advisory Committee of ICANN (SSAC) rightly acknowledges, although orphaned glue records may be used for abusive or malicious purposes, the “dominant use of orphaned glue supports the correct and ordinary operation of the DNS.” See http:⁄⁄www.icann.org⁄en⁄committees⁄security⁄sac048.pdf. While orphan glue often support correct and ordinary operation of the DNS, we understand that such glue records can be used maliciously to point to name servers that host domains used in illegal phishing, botnets, malware, and other abusive behaviors. Problems occur when the parent domain of the glue record is deleted but its children glue records still remain in DNS. Therefore, when the registry has written evidence of actual abuse of orphaned glue, the registry will take action to remove those records from the zone to mitigate such malicious conduct. Neustar runs a daily audit of entries in its DNS systems and compares those with its provisioning system. This serves as an umbrella protection to make sure that items in the DNS zone are valid. Any DNS record that shows up in the DNS zone but not in the provisioning system will be flagged for investigation and removed if necessary. This daily DNS audit serves to not only prevent orphaned hosts but also other records that should not be in the zone. In addition, if either Northwestern Mutual MU TLD Registry or Neustar becomes aware of actual abuse on orphaned glue after receiving written notification by a third party through its Abuse Contact or through its customer support, such glue records will be removed from the zone. 28.3 Measures to Promote WHOIS Accuracy Northwestern Mutual MU TLD Registry acknowledges that ICANN has developed a number of mechanisms over the past decade that are intended to address the issue of inaccurate WHOIS information. However, the proposed use of the .MUTUAL as a .GENERIC gTLD in which all domain names will initially be registered by Northwestern Mutual MU TLD Registry to the parent, or its qualified subsidiaries and affiliates, essentially eliminates the potential of false or inaccurate WHOIS data. Further ensuring that all domain names contain uniform, accurate, and up-to-date WHOIS information is the fact that these domain names will be registered through The Northwestern Mutual Life Insurance Company’s existing registrars, or a similarly situated corporate registrar, which handles Northwestern Mutual Life Insurance Company’s existing domain name portfolio. Should Northwestern Mutual MU TLD Registry expand the universe of potential registrants in the .MUTUAL namespace, to include third parties such as licensees or strategic partners, Northwestern Mutual MU TLD Registry intends to offer the following enhanced mechanism to ensure the accuracy of WHOIS data, specifically, a mechanism whereby third parties can submit complaints directly to Northwestern Mutual MU TLD Registry (as opposed to ICANN or the sponsoring registrar) about inaccurate or incomplete WHOIS data. Such information shall be forwarded to the sponsoring registrar, who shall be required to address those complaints with their registrants. Thirty days after forwarding the complaint to the registrar, Northwestern Mutual MU TLD Registry will examine the current WHOIS data for names that were alleged to be inaccurate to determine if the information was corrected, the domain name was deleted, or there was some other disposition. If the registrar has failed to take any action, or it is clear that the registrant was either unwilling or unable to correct the inaccuracies, Northwestern Mutual MU TLD Registry reserves the right to suspend the applicable domain name(s) until such time as the registrant is able to cure the deficiencies. In addition, should Northwestern Mutual MU TLD Registry expand the universe of potential registrants within the .MUTUAL namespace to include third parties such as licensees or strategic partners, Northwestern Mutual MU TLD Registry shall on its own initiative, no less than twice per year, perform a manual review of a random sampling of .MUTUAL domain names to test the accuracy of the WHOIS information. Although this will not include verifying the actual information in the WHOIS record, Northwestern Mutual MU TLD Registry will be examining the WHOIS data for prima facie evidence of inaccuracies. In the event that such evidence exists, it shall be forwarded to the sponsoring registrar, who shall be required to address those complaints with its registrants. Thirty days after forwarding the complaint to the registrar, the Northwestern Mutual MU TLD Registry will examine the current WHOIS data for names that were alleged to be inaccurate to determine if the information was corrected, the domain name was deleted, or there was some other disposition. If the registrar has failed to take any action, or it is clear that the registrant was either unwilling or unable to correct the inaccuracies, Northwestern Mutual MU TLD Registry reserves the right to suspend the applicable domain name(s) until such time as the registrant is able to cure the deficiencies. 28.3.1 Authentication of Registrant Information As noted above, the proposed use of the .MUTUAL as a .BRAND gTLD in which all domain names will initially be registered by Northwestern Mutual MU TLD Registry to The Northwestern Mutual Life Insurance Company or Northwestern Mutual MU TLD Registry, or its qualified subsidiaries and affiliates, essentially eliminates the potential of false or inaccurate WHOIS data. Additionally, all domain names will be registered through The Northwestern Mutual Life Insurance Company’s corporate registrar, or a similar corporate registrar, which employs enhanced security protocols that limit which employees can register domain names, as well as ensure that those domain names that are registered contain uniform, accurate, and up-to-date WHOIS information. Should Northwestern Mutual MU TLD Registry expand the universe of potential registrants within the .MUTUAL namespace to include third parties such as licensees or strategic partners, such domain names would not be permitted to be registered until Northwestern Mutual MU TLD Registry had a process in place to verify the identity of the registrant and the accuracy of the WHOIS data. 28.3.2 Monitoring of Registration Data As noted above Northwestern Mutual MU TLD Registry will provide a mechanism by which third parties can submit a WHOIS accuracy complaint directly to the Registry Operator for timely investigation and resolution. In addition, Northwestern Mutual MU TLD Registry has committed to perform a manual review of a random sampling of .MUTUAL domain names no less than twice per year to test the accuracy of the WHOIS information after the expanding the potential universe of domain names to include third parties such as licensees or strategic partners. 28.3.3 Policies and Procedures Ensuring Compliance These proposed enhanced safeguards designed to promote the accuracy of WHOIS data will be hard coded into the Registry-Registrar Agreement (RRA) as well as the end-registrant agreement. Northwestern Mutual MU TLD Registry will proactively be monitoring similar .GENERIC gTLDs to ensure best in class policies to promote the accuracy and availability of WHOIS data. 28.4 Resourcing Plans Responsibility for abuse mitigation rests with a variety of functional groups. The Abuse Monitoring team is primarily responsible for providing analysis and conducting investigations of reports of abuse. The customer service team also plays an important role in assisting with the investigations, responded to customers, and notifying registrars of abusive domains. Finally, the Policy⁄Legal team is responsible for developing the relevant policies and procedures. The necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. The following resources are available from those teams: Customer Support – 12 employees Policy⁄Legal – 2 employees In addition to the above staffing provided by Neustar, Northwestern Mutual MU TLD Registry will provide the full support of its internal staff (.25 FTE count) as well as its external vendors where the situation requires the extra staffing resources. The resources are more than adequate to support the abuse mitigation procedures of the .MUTUAL registry.
29. Rights Protection Mechanisms
29.1. Rights Protection Mechanisms Northwestern Mutual MU TLD Registry, LLC (“Northwestern Mutual MU TLD Registry”) is firmly committed to the protection of intellectual property rights and to implementing the mandatory rights protection mechanisms contained in the Applicant Guidebook and detailed in Specification 7 of the Registry Agreement. Northwestern Mutual MU TLD Registry recognizes that although the New gTLD Program includes significant protections beyond those that were mandatory for a number of the current TLDs, a key motivator for Northwestern Mutual MU TLD Registry’s selection of Neustar, Inc. (“Neustar”) as its registry services provider is Neustar’s experience in successfully launching a number of TLDs with diverse rights protection mechanisms, including many of the ones required in the Applicant Guidebook. More specifically, Northwestern Mutual MU TLD Registry will implement the following rights protection mechanisms in accordance with the Applicant Guidebook as further described below: Trademark Clearinghouse: a one-stop shop so that trademark holders can protect their trademarks with a single registration; Sunrise and Trademark Claims processes for the TLD; Implementation of the Uniform Domain Name Dispute Resolution Policy to address domain names that have been registered and used in bad faith in the TLD; Uniform Rapid Suspension: A quicker, more efficient, and cheaper alternative to the Uniform Domain Name Dispute Resolution Policy to deal with clear cut cases of cybersquatting; Implementation of a thick WHOIS, making it easier for rights holders to identify and locate infringing parties. A. Trademark Clearinghouse Including Sunrise and Trademark Claims The first mandatory rights protection mechanism (“RPM”) required to be implemented by each new gTLD registry is support for, and interaction with, the Trademark Clearinghouse. The Trademark Clearinghouse is intended to serve as a central repository for information to be authenticated, stored, and disseminated pertaining to the rights of trademark holders. The data maintained in the Clearinghouse will support and facilitate other RPMs, including the mandatory Sunrise Period and Trademark Claims service. Although many of the details of how the Trademark Clearinghouse will interact with each registry operator and registrars, Northwestern Mutual MU TLD Registry is actively monitoring the developments of the Implementation Assistance Group (“IAG”) designed to assist ICANN staff in firming up the rules and procedures associated with the policies and technical requirements for the Trademark Clearinghouse. In addition, Northwestern Mutual MU TLD Registry’s back-end registry services provider is actively participating in the IAG to ensure that the protections afforded by the Clearinghouse and associated RPMs are feasible and implementable. Utilizing the Trademark Clearinghouse, all operators of new gTLDs must offer: (i) a Sunrise registration service for at least 30 days during the pre-launch phase, giving eligible trademark owners an early opportunity to register second-level domains in new gTLDs; and (ii) a Trademark Claims service for at least the first 60 days that second-level registrations are open. The trademark claim service is intended to provide clear noticeʺ to a potential registrant of the rights of a trademark owner whose trademark is registered in the clearinghouse. Northwestern Mutual MU TLD Registry’ registry service provider, Neustar, has already implemented Sunrise and⁄or Trademark Claims programs for numerous TLDs including .BIZ, .US, .TRAVEL, .TEL, and .CO and will implement the both of these services on behalf of .MUTUAL. Neustar’s Experience in Implementing Sunrise and Trademark Claims Processes In early 2002, Neustar became the first registry operator to launch a successful authenticated Sunrise process. This process permitted qualified trademark owners to pre-register their trademarks as domain names in the .US ccTLD space prior to the opening of the space to the general public. Unlike any other “Sunrise” plans implemented (or proposed before that time), Neustar validated the authenticity of trademark applications and registrations with the United States Patent and Trademark Office (USPTO). Subsequently, as the back-end registry operator for the .TEL gTLD and the .CO ccTLD, Neustar launched validated Sunrise programs employing processes. These programs are very similar to those that are to be employed by the Trademark Clearinghouse for new gTLDs. Below is a high-level overview of the implementation of the .CO Sunrise period that demonstrates Neustar’s experience and ability to provide a Sunrise service, and an overview of Neustar’s experience in implementing a Trademark Claims program to trademark owners for the launch of .BIZ. Neustar’s experience in each of these rights protection mechanisms will enable it to seamlessly provide these services on behalf of Northwestern Mutual MU TLD Registry as required by ICANN. Sunrise and .CO The Sunrise process for .co was divided into two sub-phases: Local Sunrise giving holders of eligible trademarks that have obtained registered status from the Colombian trademark office the opportunity apply for the .CO domain names corresponding with their marks; and Global Sunrise program giving holders of eligible registered trademarks of national effect that have obtained a registered status in any country of the world the opportunity apply for the .CO domain names corresponding with their marks for a period of time before registration is open to the public at large. Like the new gTLD process set forth in the Applicant Guidebook, trademark owners had to have their rights validated by a Clearinghouse provider prior to the registration being accepted by the registry. The Clearinghouse used a defined process for checking the eligibility of the legal rights claimed as the basis of each Sunrise application, using official national trademark databases and submitted documentary evidence. Applicants and⁄or their designated agents had the option of interacting directly with the Clearinghouse to ensure their applications were accurate and complete prior to submitting them to the registry pursuant to an optional “Pre-validation Process.” Whether or not an applicant was “pre-validated,” the applicant had to submit its corresponding domain name application through an accredited registrar. When the Applicant was pre-validated through the Clearinghouse, each was given an associated approval number that it had to supply to the registry. If they were not pre-validated, applicants were required to submit the required trademark information through their registrar to the registry. At the registry level, Neustar subsequently either delivered the approval number and domain name registration information to the Clearinghouse, or in cases where there was no approval number, trademark information and the domain name registration information that was provided to the Clearinghouse through EPP (as is currently required under the Applicant Guidebook). Information was then used by the Clearinghouse as either further validation of those pre-validated applications, or initial validation of those that did not go through pre-validation. If the applicant was validated and its trademark matched the domain name applied for, the Clearinghouse communicated that fact to the Registry via EPP. When there was only one validated Sunrise application, the application proceeded to registration when .CO launched. If there were multiple validated applications (recognizing that there could be multiple trademark owners sharing the same trademark), those were included in the .CO Sunrise auction process. Neustar tracked all of the information it received and the status of each application and posted that status on a secure website to enable trademark owners to view the status of their Sunrise application. Although the exact process for the Sunrise program and its interaction between the trademark owner, registry, registrar, and IP Clearinghouse is not completely defined in the Applicant Guidebook and is dependent on the current RFI issued by ICANN in its selection of a Trademark Clearinghouse provider, Neustar’s expertise in launching multiple Sunrise processes and its established software will implement a smooth and compliant Sunrise process for the new gTLDs. Trademark Claims Service Experience With Neustar’s .BIZ TLD launched in 2001, Neustar became the first registry with a Trademark Claims service. Neustar developed the Trademark Claims Service by enabling companies to stake claims to domain names prior to the commencement of live .BIZ domain registrations. During the Trademark Claims process, Neustar received over 80,000 Trademark Claims from entities around the world. Recognizing that multiple intellectual property owners could have trademark rights in a particular mark, multiple Trademark Claims for the same string were accepted. All applications were logged into a Trademark Claims database managed by Neustar. The Trademark Claimant was required to provide various information about their trademark rights, including the: Particular trademark or service mark relied on for the trademark Claim; Date a trademark application on the mark was filed, if any, on the string of the domain name; Country where the mark was filed, if applicable; Registration date, if applicable; Class or classes of goods and services for which the trademark or service mark was registered; Name of a contact person with whom to discuss the claimed trademark rights. Once all Trademark Claims and domain name applications were collected, Neustar then compared the claims contained within the Trademark Claims database with its database of collected domain name applications (DNAs). In the event of a match between a Trademark Claim and a domain name application, an e-mail message was sent to the domain name applicant notifying the applicant of the existing Trademark Claim. The e-mail also stressed that if the applicant chose to continue the application process and was ultimately selected as the registrant, the applicant would be subject to Neustar’s dispute proceedings if challenged by the Trademark Claimant for that particular domain name. The domain name applicant had the option to proceed with the application or cancel the application. Proceeding on an application meant that the applicant wanted to go forward and have the application proceed to registration despite having been notified of an existing Trademark Claim. By choosing to “cancel,” the applicant made a decision in light of an existing Trademark Claim notification to not proceed. If the applicant did not respond to the e-mail notification from Neustar, or elected to cancel the application, the application was not processed. This resulted in making the applicant ineligible to register the actual domain name. If the applicant affirmatively elected to continue the application process after being notified of the Claimant’s (or Claimants’) alleged trademark rights to the desired domain name, Neustar processed the application.
This process is very similar to the one ultimately adopted by ICANN and incorporated in the latest version of the Applicant Guidebook. Although the collection of Trademark Claims for new gTLDs will be by the Trademark Clearinghouse, many of the aspects of Neustar’s Trademark Claims process in 2001 are similar to those in the Applicant Guidebook. This makes Neustar uniquely qualified to implement the new gTLD Trademark Claims process. B. Uniform Domain Name Dispute Resolution Policy (UDRP) and Uniform Rapid Suspension (URS) 1. UDRP Prior to joining Neustar, Mr. Neuman was a key contributor to the development of the Uniform Domain Name Dispute Resolution Policy (“UDRP”) in 1998. This became the first “Consensus Policy” of ICANN and has been required to be implemented by all domain name registries since that time. The UDRP is intended as an alternative dispute resolution process to transfer domain names from those that have registered and used domain names in bad faith. Although there is not much of an active role that the domain name registry plays in the implementation of the UDRP, Neustar has closely monitored UDRP decisions that have involved the TLDs that it supports and ensures that the decisions are implemented by the registrars supporting its TLDs. When alerted by trademark owners of failures to implement UDRP decisions by its registrars, Neustar either proactively implements the decisions itself or reminds the offending registrar of its obligations to implement the decision. URS In response to complaints by trademark owners that the UDRP was too cost prohibitive and slow, and the fact that more than 70 percent of UDRP cases were “clear cut” cases of cybersquatting, ICANN adopted the IRT’s recommendation that all new gTLD registries be required, pursuant to their contracts with ICANN, to take part in a Uniform Rapid Suspension system (“URS”). The purpose of the URS is to provide a more cost effective and timely mechanism for brand owners than the UDRP to protect their trademarks and to promote consumer protection on the Internet. The URS is not meant to address questionable cases of alleged infringement (e.g., use of terms in a generic sense), for anti-competitive purposes, or denial of free speech, but rather for those cases in which there is no genuine contestable issue as to the infringement and abuse that is taking place. Unlike the UDRP, which requires little involvement of gTLD registries, the URS envisages much more of an active role at the registry level. For example, rather than requiring the registrar to lock down a domain name subject to a UDRP dispute, it is the registry under the URS that must lock the domain within 24 hours of receipt of the complaint from the URS Provider to restrict all changes to the registration data, including transfer and deletion of the domain names. In addition, in the event of a determination in favor of the complainant, the registry is required to suspend the domain name. This suspension remains for the balance of the registration period and would not resolve the original website. Rather, the nameservers would be redirected to an informational web page provided by the URS Provider about the URS. Additionally, the WHOIS reflects that the domain name will not be able to be transferred, deleted, or modified for the life of the registration. Finally, there is an option for a successful complainant to extend the registration period for one additional year at commercial rates. 〈Applicant〉 is fully aware of each of these requirements and will have the capability to implement these requirements for new gTLDs. In fact, during the IRT’s development of the URS, Neustar began examining the implications of the URS on its registry operations and provided the IRT with feedback on whether the recommendations from the IRT would be feasible for registries to implement. Although there have been a few changes to the URS since the IRT recommendations, Neustar continued to participate in the development of the URS by providing comments to ICANN, many of which were adopted. As a result, Neustar is committed to supporting the URS for all of the registries to which it provides back-end registry services. C. Implementation of Thick WHOIS The .MUTUAL registry will include a thick WHOIS database as required in Specification 4 of the Registry Agreement. A thick WHOIS provides numerous advantages, including a centralized location of registrant information, the ability to more easily manage and control the accuracy of data, and a consistent user experience. D. Policies Handling Complaints Regarding Abuse In addition the rights protection mechanisms addressed above, Northwestern Mutual MU TLD Registry will implement a number of measures to handle complaints regarding the abusive registration of domain names in its gTLD as described in its response to Question 28. Registry Acceptable Use Policy One of the key policies each new gTLD registry needs to have is an Acceptable Use Policy that clearly delineates the types of activities that constitute “abuse” and the repercussions associated with an abusive domain name registration. The policy must be incorporated into the applicable Registry-Registrar Agreement and reserve the right for the registry to take the appropriate actions based on the type of abuse. This may include locking down the domain name, preventing any changes to the contact and nameserver information associated with the domain name, placing the domain name “on hold,” rendering the domain name non-resolvable, transferring to the domain name to another registrar, and⁄or in cases in which the domain name is associated with an existing law enforcement investigation, substituting nameservers to collect information about the DNS queries to assist the investigation. .MUTUAL’s Acceptable Use Policy, set forth in our response to Question 28, will include prohibitions on phishing, pharming, dissemination of malware, fast flux hosting, hacking, and child pornography. In addition, the policy will include the right of the registry to take action necessary to deny, cancel, suspend, lock, or transfer any registration in violation of the policy. Monitoring for Malicious Activity Northwestern Mutual MU TLD Registry is committed to ensuring that those domain names associated with abuse or malicious conduct in violation of the Acceptable Use Policy are dealt with in a timely and decisive manner. These include taking action against those domain names that are being used to threaten the stability and security of the gTLD, or is part of a real-time investigation by law enforcement. Once a complaint is received from a trusted source, third party, or detected by the registry, the registry will use commercially reasonable efforts to verify the information in the complaint. If that information can be verified to the best of the ability of the registry, the sponsoring registrar will be notified and be given 12 hours to investigate the activity and either take down the domain name by placing the domain name on hold or by deleting the domain name in its entirety, or providing a compelling argument to the registry to keep the name in the zone. If the registrar has not taken the requested action after the 12-hour period (i.e., is unresponsive to the request or refuses to take action), the registry will place the domain on “ServerHold.” Although this action removes the domain name from the gTLD zone, the domain name record still appears in the gTLD WHOIS database so that the name and entities can be investigated by law enforcement should they desire to get involved. 29.2 Safeguards against Unqualified Registrations As set forth in Northwestern Mutual MU TLD Registry’s response to Question 28, the proposed use of the .MUTUAL as a .GENERIC gTLD is one in which all domain names will initially be registered by Northwestern Mutual MU TLD Registry to The Northwestern Mutual Life Insurance Company or its qualified subsidiaries and affiliates, at least for the first three years of operation, thus eliminating the potential of unqualified registrants. Further ensuring that all domain names are only registered by qualified registrants is the fact that these domain names will be registered through The Northwestern Mutual Life Insurance Company’s existing registrar(s), or a similar corporate registrar, which handle(s) The Northwestern Mutual Life Insurance Company’s existing domain name portfolio. Should Northwestern Mutual MU TLD Registry expand the universe of potential registrants in the .MUTUAL namespace to include third parties such as licensees and⁄or strategic partners, Northwestern Mutual MU TLD Registry intends to offer the following enhanced mechanism to ensure that only qualified registrants have registered in the name space: specifically, a mechanism whereby third parties can submit complaints directly to Northwestern Mutual MU TLD Registry (as opposed to ICANN or the sponsoring registrar) about the qualification of a domain name registrant in the .MUTUAL namespace. Northwestern Mutual MU TLD Registry will then undertake an investigation to either confirm or dismiss the allegation. Northwestern Mutual MU TLD Registry reserves the right to suspend the applicable domain name(s) until such time as the Registrant is able to resolve any qualification requirements. If this mechanism, coupled with verification requirements imposed at the registrar level, prove inadequate, Northwestern Mutual MU TLD Registry would evaluate implementing an annual sampling of the active zone file to verify registrant qualification as well as WHOIS accuracy. The size of the sampling would be based upon a meaningful statistical universe and would be subject to change based upon the results of this survey. 29.3 Resourcing Plans The rights protection mechanisms described in the response above involve a wide range of tasks, procedures, and systems. The responsibility for each mechanism varies based on the specific requirements. In general, the development of applications such as Sunrise and IP claims is the responsibility of the Engineering team, with guidance from the Product Management team. Customer Support and Legal play a critical role in enforcing certain policies such as the rapid suspension process. These teams have years of experience implementing these or similar processes. The necessary resources will be pulled from the pool of available resources described in detail in the response to Question 31. The following resources are available from those teams: Development⁄Engineering – 19 employees; Product Management – four employees; Customer Support – 12 employees. Northwestern Mutual MU TLD Registry’s 0.25 FTE allocated to registry oversight and compliance should have no problem undertaking these initial functions based upon the closed nature of the registry and the limited zone files size. However, if the number of domain names were to exceed a manageable size, Northwestern Mutual MU TLD Registry would consider outsourcing this potential function to a qualified third party that could recognize more efficiencies and economies of scale in implementing these additional safeguard mechanisms. These combined resources are more than adequate to support the rights protection mechanisms of the .MUTUAL registry.
30(a). Security Policy: Summary of the security policy for the proposed registry
Northwestern Mutual MU TLD Registry, LLC and its back-end operator, Neustar, Inc. (“Neustar”), recognize the vital need to secure the systems and the integrity of the data in commercial solutions. The .MUTUAL registry solution will leverage industry-best security practices including the consideration of physical, network, server, and application elements. Neustar’s approach to information security starts with comprehensive information security policies. These are based on the industry best practices for security including SANS (SysAdmin, Audit, Network, Security) Institute, NIST (National Institute of Standards and Technology), and Center for Internet Security (CIS). Policies are reviewed annually by Neustar’s information security team. The following is a summary of the security policies that will be used in the .MUTUAL registry, including: Summary of the security policies used in the registry operations; Description of independent security assessments; Description of security features that are appropriate for .MUTUAL; List of commitments made to registrants regarding security levels; All of the security policies and levels described in this section are appropriate for the .MUTUAL registry. 30.(a).1 Summary of Security Policies Neustar, Inc. has developed a comprehensive Information Security Program in order to create effective administrative, technical, and physical safeguards for the protection of its information assets, and to comply with Neustarʹs obligations under applicable law, regulations, and contracts. This Program establishes Neustarʹs policies for accessing, collecting, storing, using, transmitting, and protecting electronic, paper, and other records containing sensitive information. The Program defines: The policies for internal users and its clients to ensure the safe, organized, and fair use of information resources: The rights that can be expected with that use; The standards that must be met to effectively comply with policy; The responsibilities of the owners, maintainers, and users of Neustar’s information resources; Rules and principles used at Neustar to approach information security issues.