Document:

QuickLinks
 -- Click here to rapidly navigate through this document

Exhibit 10.5  

        Pursuant to 17 CFR 230.406, confidential information has been omitted in places marked [***] and has been filed separately with the
Securities and Exchange Commission pursuant to a Confidential Treatment Application filed with the Commission.

 
 

ORDER FOR SUPPLIES OR SERVICES    
    

	1.	 	DATE OF ORDER	 	26 Oct. 2001
	

2.	
 	

CONTRACT NO. (if any)	
 	

 
	

3.	
 	

ORDER NO.	
 	

SB1335-02-W-0175
	

4.	
 	

REQUISITION/REFERENCE NO.	
 	

01-909-0066
	

5.	
 	

ISSUING OFFICE

(address correspondence to: 000SB	
 	

NIST

100 BUREAU DRIVE STOP 3571

BUILDING 301 ROOM B129

GAITHERSBURG, MD 20899-3571

WIDDUP, JOSEPH (301-975-6324
	

6.	
 	

SHIP TO:	
 	

SCHED
	

 	
 	

a.  Name of Consignee	
 	

SEE SCHEDULE BELOW
	

 	
 	

b.  Street Address	
 	

 
	

 	
 	

c.  City	
 	

 
	

 	
 	

d.  State	
 	

 
	

 	
 	

e.  Zip Code	
 	

 
	

 	
 	

f.  Ship VIA	
 	

 
	

7.	
 	

TO:	
 	

0007158
	

 	
 	

TIN:	
 	

522141938
	

 	
 	

a.  Name of Contractor	
 	

NEUSTAR
	

 	
 	

b.  Company Name	
 	

 
	

 	
 	

c.  Street Address	
 	

1120 VERMONT AVENUE NW

Suite 400
	

 	
 	

d.  City	
 	

Washington
	

 	
 	

e.  State	
 	

DC
	

 	
 	

f.  Zip	
 	

20005
	

8.	
 	

TYPE OF ORDER	
 	

 
	

 	
 	

a.  /x/ Purchase	
 	

REFERENCE YOUR: Quotation

Dated July 27, 2001

Please furnish the following terms and conditions specified on both sides of this order and on the attached sheet, if any, including delivery as indicated.
	 	 	 	 	 

 

	

 	
 	

b.  / / Delivery	
 	

Except for billing instructions on the reverse, this delivery order is subject to instructions contained on this side only of this form and is issued subject to the terms and conditions of the above-referenced contract.
	

9.	
 	

ACCOUNTING AND APPROPRIATION	
 	

See Attached Schedule
	

 	
 	

BOC:	
 	

$0.00
	

 	
 	

OBLIGATED AMT:	
 	

 
	

10.	
 	

REQUISITIONING OFFICE	
 	

NTIA 909.00
	

11.	
 	

ACCOUNTING CLASSIFICATION	
 	

/ / a.  Small
	

 	
 	

(check appropriate box(es))	
 	

/x/ b.  Other Than Small
	

 	
 	

 	
 	

/ / c.  Disadvantaged
	

 	
 	

 	
 	

/ / d.  Women-Owned
	

12.	
 	

F.O.B. POINT	
 	

See Schedule
	

13.	
 	

PLACE OF	
 	

 
	

 	
 	

a.  Inspection	
 	

Destination
	

 	
 	

b.  Acceptance	
 	

Destination
	

14.	
 	

GOVERNMENT B/L/ NO.	
 	

 
	

15.	
 	

DELIVER TO F.O.B. POINT ON OR BEFORE	
 	

25 Oct 2005
	

16.	
 	

DISCOUNT TERMS	
 	

00.00% 0 Days
	

 	
 	

 	
 	

Net 0
	

17.	
 	

SCHEDULE (seer reverse for Projections)	
 	

 

2

 

	Item No.

(a)
	 	Supplies or Services

(b)
	 	Quantity

Ordered

(c)
	 	Unit

(d)
	 	Unit Price

(e)
	 	Amount

(f)
	 	Qty

Accept.

(g)

	 	 	The Contractor's quotation dated July 27, 2001 is hereby incorporated by reference into this purchase order as though it were included in full text. In the event of an inconsistency between the provisions of this Purchase
Order and the Contractor's quotation, the inconsistency shall be resolved by giving precedence in the following order: i) the Purchase Order (excluding the Contractor's	 	 	 	 	 	 	 	 	 	 
	

 	
 	

Account and Appropriation Data: 00.00.00.0000000000.0000000000. 000.00000000000000.0000000000	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 
	

 	
 	

BOC: 27800	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 
	

002	
 	
Option Period One

The Contractor must perform the services required by the SOW
 Period of Performance: 365 days, beginning the day after the Base Period expires	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 
	

 	
 	

Account and Appropriation Data:

00.00.00.0000000000.0000000000. 000.00000000000000.0000000000	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 
	

 	
 	

BOC: 27800	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 

3

   
July 27, 2001 

Attn:
Joseph L. Widdup

National Institute of Standards and Technology

100 Bureau Dr. Stop 3571

Bldg. 301 Room B129

Gaithersburg, MD 20899-3571

M/F Solicitation SB1335-01-Q-0740 

Dear
Mr. Widdup: 

        We
are pleased to submit the attached proposal in response to the National Institute of Standards and Technology's Request for Quotation (RFQ) (Solicitation Number
SB1335-01-Q-0740) on behalf of the U. S. Department of Commerce's National Telecommunications and Information Administration for Centralized Management and
Coordination of Registry, Registrar, Database, and Information Services for the usTLD. 

        As
our proposal demonstrates, we offer the Department of Commerce a truly neutral vendor who is qualified to perform the required roles and responsibilities set forth in the Statement of
Work in the Request for Quotation. 

        The
solution we propose will demonstrate that NeuStar has: 

	•
	A
legacy of managing public resources in a responsible manner.

	•
	The
experience to transition mission critical infrastructure services.

	•
	Proven
experience implementing advanced technologies to increase the utility of public resources.

	•
	A
legacy of facilitating policy processes in environments with multiple stakeholders.

	•
	The
financial means and necessary commitment to build and operate mission critical resources. 

        As
requested, we have provided an original version and two copies of our response to the RFQ. The proposal is organized in accordance with the Instructions for Submitting Quotations, and
Amendment 1, Question 15. Following this letter of transmittal is the RFQ Transmittal Form, NeuStar's signed Acknowledgment of Amendment 0001 (June 16, 2001), Amendment 0002
(June 17, 2001), and Amendment 0003 (July 23, 2001). NeuStar submits this response as "Confidential and Proprietary Information" and has indicated so in the left hand corner of each
page. NeuStar understands this to mean, all information received in response to this solicitation will be considered confidential and proprietary information and will be treated as such, as cited in
SB1335-01-Q-0740 Amendment 0001, Question 5. 

        While
I am the negotiator for this proposal and am authorized to bind the Corporation to any contract resulting herefrom, should you have any questions regarding our proposal, please
contact [***], via fax at [***], or via e-mail at [***]. 

        We
look forward to working with the DOC and NTIA to ensure the successful enhancement and expansion of the usTLD. 

Sincerely,

Robert
Poulin

Vice President, Corporate Development

NeuStar, Inc. 

Enclosures 

4

  

	

REQUEST FOR QUOTATION
 (THIS IS NOT AN ORDER)	
 	

This RFQ o is ý is not a small Business set-aside	
 	

 	
 	

 
	

1. REQUEST NO

SB1335-01-Q-0740	
 	

2. DATE ISSUED

Jun 12, 2001	
 	

3. REQUISITION/PURCHASE REQ NO.

01-909-0066	
 	

4. CERT FOR NAT. DEF. UNDER BDSA REG 2 AND/OR DMS REQ. 1	
 	

RATING
	

5a. ISSUED BY	
 	

6. DELIVERY BY (Date)
	 	
 NATIONAL INST OF STDS AND TECHNOLOGY

100 BUREAU DRIVE STOP 3572

CONTRACTS BUILDING 301 ROOM B117

GAITHERSBURG MD 20899-3572	
 	

7. DELIVERY

o FOB Destination ý Other (See Schedule)
	

5b. FOR MORE INFORMATION CALL (No Collect Calls)	
 	

9. DESTINATION    SCHED
	

NAME	
 	

 	
 	

Area Code	
 	

Telephone	
 	

a. NAME OF CONSIGNEE
	WIDDUP, JOSEPH	 	061	 	301	 	975-6324	 	SEE SCHEDULE BELOW
	

8. TO	
 	

b. STREET ADDRESS
	

a. NAME	
 	

b. COMPANY	
 	

 	
 	

 	
 	

 	
 	

 
	Robert Poulin	 	NeuStar, Inc.	 	 	 	 	 	 	 	 
	

c. STREET ADDRESS	
 	

 	
 	

 
	1120 Vermont Avenue, NW

Suite 400	 	 	 	 
	

d. CITY	
 	

e. STATE	
 	

f. ZIP CODE	
 	

d. STATE	
 	

e. ZIP CODE
	Washington	 	DC	 	20005	 	 	 	 
	

10. PLEASE FURNISH QUOTATIONS TO THE ISSUING OFFICE IN BLOCK 5A ON OR BEFORE CLOSE OF BUSINESS (DATE)

Jul 27, 2001	
 	

IMPORTANT: This is a request for information and quotations furnished are not offers. If you are unable to quote, please so indicate on this form and return it to the address in Block 5A. This request does not commit the Government to pay any costs
incurred in the the submission of this quotation or to contract for supplies or services. Supplies are of domestic origin unless otherwise indicated by Any representations and/or certifications to this Request for Quotations must be completed by the
quoter.
	

11. SCHEDULE (Indicate applicable Federal, State and local taxes)
	

 	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 

	ITEM NO.

(a)
	 	SUPPLIES/SERVICES

(b)
	 	QUANTITY

(c)
	 	UNIT

(d)
	 	UNIT PRICE

(f)
	 	AMOUNT

(f)

	0001	 	The Contractor must perform the services required by the SOW Period of Performance: Base Period (4 years, beginning on the date of purchase order award)	 	4	 	YR	 	$	0.00	 	$	0.00
	0002	 	The Contractor must perform the services required by the SOW Period of Performance: Option Period One (365 days, beginning the day after the Base Year expires)	 	1	 	YR	 	$	0.00	 	$	0.00
	0003	 	The Contractor must perform the services required by the SOW Period of Performance: Option Period Two (365 days, beginning the day after the Base Year expires)	 	1	 	YR	 	$	0.00	 	$	0.00

	

12. DISCOUNT FOR PROMPT PAYMENT	
 	

a. 10 Calendar Days (%)	
 	

b. 20 Calendar Days (%)	
 	

c. 30 Calendar Days (%)	
 	

D. CALENDAR DAYS
	

 	
 	

 	
 	

 	
 	

 	
 	

NUMBER	
 	

PERCENTAGE
	

NOTE: Additional provisions and representations ý are o are not attached.
	

13. NAME AND ADDRESS OF QUOTER	
 	

14. SIGNATURE OF PERSON AUTHORIZED TO SIGN QUOTATION	
 	

15. DATE OF QUOTATION
	

a. NAME OF QUOTER	
 	

 	
 	

 	
 	

 	
 	

 
	NeuStar, Inc.	 	DUNS-11-240-3295	 	 	 	 	 	 	 	 
	

b. STREET ADDRESS	
 	

16. SIGNER
	1120 Vermont Avenue, NW, Suite 400	 	a. NAME (Type or print)	 	b. TELEPHONE
	

c. COUNTY	
 	

Robert Poulin	
 	

AREA CODE

202
	

d. CITY	
 	

e. STATE	
 	

f. ZIP CODE	
 	

c. TITLE (Type or print)	
 	

NUMBER
	Washington	 	DC	 	20005	 	Vice President	 	533.2680
	
AUTHORIZED FOR LOCAL REPRODUCTION	
 	

STANDARD FORM 18 (Rev. 6/95)

5

  

 
 

STATEMENT OF WORK (SOW)    
    

        The Contractor must furnish the necessary personnel, material, equipment, services, and facilities (except as otherwise specified) to perform the requirements
stated in this SOW. 

A. INTRODUCTION  

        The.us domain ("usTLD") is the country code top level domain ("ccTLD") of the Internet domain name system ("DNS") that corresponds to the United States.
Currently, second-level domain space in.us is designated for states and U.S. territories and special purposes as described in the Internet Engineering Task Force's ("IETF") RFC 1480 (titled  The US Domainhttp://www.ietf.org/rfc/rfc1480.txt?number=1480) ("RFC 1480"), and is further subdivided
into localities and other functional designations. 

        Individuals
and organizations may currently request a delegation from the usTLD Administrator to provide registry and registrar services for a particular locality or localities. Local
governments and community-based organizations typically use the usTLD, although some commercial names have been assigned. Where registration for a locality has not been delegated, the usTLD
Administrator itself provides necessary registry and registrar services. Information on the locality-based usTLD structure and registration policies is available for review at:  http://www.nic.us

        The
usTLD is a widely distributed registry, currently with over 8000 sub-domain delegations to over 800 individuals and entities, who maintain a registry and provide
registration services for commercial, educational, and governmental entities. This distributed registration model affords scalable registration services and opportunities for organizations and
commercial entities to provide name registration services. For purposes of this acquisition, we will refer to the current.us name space and structure, including its non-locality,
functional elements, as the "locality-based usTLD structure." 

        While
the locality-based usTLD structure has not attracted high levels of registration and utilization in comparison to other ccTLD's, it is popular with its current base of users.
During consultations with the public on the administration of the usTLD, a considerable number of parties expressed a desire for the
continued operation and support of the locality-based usTLD structure. The Contractor will be required to maintain and improve the management of the current usTLD space. 

        Because
of its deeply hierarchical and somewhat cumbersome structure, the usTLD has not been used on a wide scale. The general absence of less hierarchical registration opportunities in
the usTLD has limited the domain's attractiveness to users. It has been suggested that this more "generic" space would greatly increase the utility of the usTLD. Therefore, this acquisition also
encompasses functions that will allow, on a competitive basis, for the registration of second level domains directly under usTLD (such as example.us). 

        A
number of technical enhancements to the usTLD system functions are required to make the system more robust and reliable. Because the usTLD has operated for the most part on a delegated
basis for a number of years, the availability of centralized contact information for the usTLD has proven difficult to maintain. For example, RFC 1480 advises but does not require that the
administrator of a delegated sub-domain operate a database of accurate and up-to-date registration information ("WHOIS") service. As described in section above,
"locality-based usTLD structure" in this acquisition refers to the current usTLD space (as described in RFC 1480), including those limited non-locality, functional designations. 

        Notwithstanding
the fact that some of the administrative responsibilities for the locality-based usTLD structure require the registry to act as a registrar in certain limited
circumstances, in order to encourage competition in domain name registration services, the Contractor will not be permitted to act as both the registry and a registrar in the expanded usTLD space.
Further, the Contractor will be 

6

 

required
to perform a core set of usTLD registry functions, as described in the Contractor Requirements section below. 

        On
August 4, 1998, the United States Department of Commerce ("DOC"), through DOC's National Telecommunications and Information Administration ("NTIA"), solicited comments
addressing the future expansion and administration of the usTLD space. On March 9, 1999, NTIA hosted a public meeting regarding the future management and administration of the.us domain with
approximately sixty participants, including the current usTLD Administrator, current.us registrars, educators, representatives of the technical, public interest and business communities, and federal,
state and foreign government officials. NTIA also established an open electronic mailing list to facilitate further public discussions of the issues. On August 17, 2000, NTIA requested comments
on a draft SOW for this acquisition. Comments received by NTIA were reviewed and considered by NTIA in connection with preparation of this SOW. 

        This
acquisition is being conducted in accordance with Federal Acquisition Regulation (FAR) Part 13, Simplified Acquisition Procedures. 

B. CONTRACTOR REQUIREMENTS  

        The Contractor must perform the required services for this acquisition as a prime Contractor, not as an agent or subcontractor. (The provision of the required
services may be accomplished through coordinating the resources and services provided by entities other than the prime Contractor.) The Contractor must be (a) incorporated within one of the
fifty states of the United States of America or the District of Columbia or (b) organized under a law of a state of the United States of America or the District of Columbia. The Contractor must
possess and maintain through the performance of this acquisition a physical address within the United States and must be able to demonstrate that all primary registry services will remain within the
United States of America (including the District of Columbia). 

        The Contractor may not charge the United States Government for performance of the requirements of this purchase order (the unit price and amount for Line Items
0001, 0002 and 0003 must each be $0.00). However, the Contractor may establish and collect fees from third parties for performance of the requirements of this purchase order,
provided that the fee levels are approved by the Contracting Officer before going into effect, which approval will not be withheld unreasonably, provided that the fee levels are fair and reasonable. 

B.1 Statement of Purpose  

        The Department of Commerce seeks to acquire centralized management and coordination of registry, registrar (where specified), database, and information services
for the usTLD. In broadest terms, the usTLD was created to provide a locus for registration of domain names to serve the Internet community of the United States, and is intended to be available to a
wide range of registrants. Given the foregoing, the Department seeks quotations that will achieve the following objectives: 

	1.
	Ensure
that procedures and a framework of accountability for the delegation and the administration of usTLD evolve into a more robust, certain, and reliable system.

	2.
	Promote
increased use of the usTLD by the Internet community of the United States (including small businesses, consumers, Internet users, not-for-profit
organizations, and local governments (i.e., state, city, and county), among others), with residence or a
bona fide presence in the United States) through introduction of enhanced services, dissemination of information through advertising and/or other appropriate mechanisms, and simplification of
registration services including direct registration. 

7

 

	3.
	Create
a centrally administered and efficiently managed structure that ensures both registrant/consumer confidence and infrastructure stability through coordination of delegations as
well as other appropriate functions.

	4.
	Create
a stable, flexible, and balanced environment within the usTLD that is conducive to innovation and that will meet the future demands of potential registrants.

	5.
	Ensure
continued stability of the domain name system as a whole and the usTLD, particularly throughout the transition period from the current management structure into the new
structure developed and maintained under the Contractor.

	6.
	Manage
the usTLD consistent with the Internet Corporation for Assigned Names and Numbers' (ICANN) technical management of the DNS.

	7.
	Allow
for the adequate protection of intellectual property in the usTLD. This includes, in particular, the implementation of a "sunrise period" that permits qualified trademark owners
to pre-register their trademarks as domain names in the expanded usTLD space prior to the opening of the expanded usTLD space to wider registration, and a dispute resolution procedure to
address conflicts between trademarks and domain names arising from "cybersquatting" in the usTLD.

	8.
	Establish
and maintain consistent communication between the COTR, the Contractor and ICANN. This includes representation of the usTLD in the ICANN ccTLD constituency and contribution
to ICANN's operating costs as apportioned to the usTLD through the ICANN budget process.

	9.
	Promote
robust competition within the usTLD and in particular registration services that will lead to greater choice, new, and better services for users. 

B.2 Core Registry Functions  

        The Contractor must provide, at a minimum, the services that are outlined below. This list should not be viewed as exhaustive. The Contractor must provide all
systems, software, hardware, facilities, infrastructure, and operation for the following functions: 

	1.
	Operation
and maintenance of the primary, authoritative server for the usTLD;

	2.
	Operation
and/or administration of a constellation of secondary servers for the usTLD;

	3.
	Compilation,
generation, and propagation of the usTLD zone file(s);

	4.
	Maintenance
of an accurate and up-to-date registration (WHOIS) database for all usTLD registrations;

	5.
	Maintenance
of an accurate and up-to-date database of usTLD subdelegation managers;

	6.
	Establishment
of a data escrow for usTLD zone file and domain name registration information, including chain of registration data;

	7.
	Compliance
with applicable Internet Engineering Task Force (IETF) and applicable ICANN policies for the functions outlined above; and

	8.
	Promotion
of awareness and registration in the usTLD including maintaining website with up-to-date policy and registration information for the usTLD. 

8

 

B.3 Core Policy Requirements  

        The Contractor must: 

	1.
	Implement United States Nexus Requirement: The Contractor must run the usTLD as a country code top level domain intended to serve the
community of Internet users (including end users, business, government, and not-for-profit organizations, among others) resident or located with a bona fide presence in the
United States, and is not intended to attract or otherwise encourage registrations from outside the United States. In addition to the current policy set forth in RFC 1480 requiring that usTLD domain
name registrations be hosted on computers located within the United States, the Contractor must implement a United States Nexus Requirement in both the locality-based usTLD structure and the expanded
usTLD space.

	2.
	Adopt ICANN Policies Pertaining to Open ccTLD's: Although the usTLD is intended to serve the Internet community of the United States,
and is not intended to encourage registrations from entities or individuals resident outside the United States, the Contractor must follow the ICANN policies pertaining to open ccTLD's unless
otherwise directed by the Contracting Officer.

	3.
	Implement a Uniform Domain Name Dispute Resolution Procedure and Sunrise Policy. The Contractor must implement a uniform domain name
dispute resolution procedure intended to resolve disputes arising from "cybersquatting" applicable to the usTLD (such policy is intended to be modeled upon the ICANN Uniform Domain Name Dispute
Resolution Procedure, consistent with modifications necessary for such policy to be applicable to the usTLD specifically). The Contractor must also implement a "Sunrise Policy" that permits qualified
trademark owners to pre-register their trademarks as domain names in the expanded usTLD space prior to the opening of the expanded usTLD space to wider registration.

	4.
	Abide by Government Advisory Committee Principles: The Contractor must abide by the principles and procedures set forth in the
Government Advisory Committee document "Principles for the Delegation and Management of Country-Code Top Level Domains," unless inconsistent with U.S. law or regulation. 

B.4 Locality-based usTLD Structure Functions  

        The Contractor must: 

	1.
	Provide Service for Existing Delegees and Registrants: Provide service and support for existing delegees and registrants in the
existing, locality-based usTLD structure under current practice, including policies set forth in RFC 1480 and other documented usTLD policies.

	2.
	Provide Services for Undelegated Third Level Sub-Domains: Provide direct registry and registrar services for all other
undelegated third level locality sub-domains, including services for CO and CI, and undelegated special purpose domains (K12, CC, TEC, LIB, MUS, STATE, DST, COG and GEN).

	3.
	Modernize Locality-Based usTLD processes: The Contractor must modernize and automate the locality-based usTLD delegation and
registration process under the control of the usTLD administrator, including the creation of an electronic database to store historical usTLD registration data.

	4.
	Coordinate Current Locality-Based usTLD Users: The Contractor must create a mechanism or mechanisms whereby delegated managers of the
usTLD, users of the locality-based usTLD, traditional usTLD user groups (such as state and local governments, the library community and educational institutions, among others), and other interested
parties, can coordinate to discuss usTLD administrative, technical, and policy issues related to the operation and management of locality-based usTLD structure. 

9

 
	5.
	Investigate Compliance with Current Locality-Based usTLD Policies: The Contractor must conduct an investigation (or commission such an
investigation) and submit a report to the COTR, within six months after purchase order award, evaluating the compliance of existing sub-domain managers with the requirements of RFC 1480
and other documented usTLD policies. Further, the study should include an evaluation of "locality-squatting" issues, or the practice of registering a locality name without providing a responsive level
of service to such locality. Such report must recommend structural, procedural, and policy changes designed to enhance such compliance or improve usTLD registration services and increase the value of
the locality-based usTLD structure to local communities. During this evaluation period, the Contractor must not make any additional locality delegations or transfers unless otherwise directed by the
Contracting Officer.

	6.
	Develop Database of usTLD Delegated Managers: The Contractor must develop a single database for up-to-date and
verified contact information for all delegated managers in the usTLD, including to locality-level and functional second level (where delegated) administrators and, where applicable, for all
sub-delegations made by such locality-level or second level administrators. Such databases should allow for multiple string and field searching through a free, public,
web-based interface, and consist of at least the following elements:

	A.
	The
name of the delegated manager;

	B.
	The
IP address of the primary nameserver and secondary nameserver(s) for the delegation;

	C.
	The
corresponding names of those nameservers;

	D.
	The
date of delegation;

	E.
	The
name and postal address of the delegated manager;

	F.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the delegated manager;

	G.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the delegated manager; and

	H.
	The
website or other contact information through which registrations can be accepted under that delegation.

	7.
	Develop Registrant WHOIS Database: The Contractor must develop an enhanced searchable WHOIS database that contains, or provides reliable
access to, all locality-based usTLD registrants including the registrants of delegated usTLD managers and, where applicable, registrants located under delegated managers' sub-delegations.
Such WHOIS database must allow for multiple string and field searching through a free, public, web-based interface, and consist of at least the following elements:

	A.
	The
name of the domain registered;

	B.
	The
Internet Protocol (IP) address of the primary nameserver and secondary nameserver(s) for the registered domain name;

	C.
	The
corresponding names of those nameservers;

	D.
	The
identity of the delegated manager under which the name is registered;

	E.
	The
creation date of the registration;

	F.
	The
name and postal address of the domain name holder; 

10

 

	G.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder; and

	H.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder. 

B.5 Expanded usTLD Space Functions  

        The Contractor must not act as a registrar in the expanded usTLD space. Presented below is a non-exhaustive list of elements that the Contractor must
incorporate into its procedures and policies for the expanded usTLD structure: 

	1.
	Develop and Implement Shared Registration System: The Contractor must develop and implement a shared registration system whereby
qualified competing registrars may register domain names for their customers in the expanded usTLD space (i.e., example.us). At a minimum, this proposed
shared registration system must allow an unlimited number of accredited/licensed registrars to register domain names in the expanded usTLD; provide equivalent access to the system for all
accredited/licensed registrars to register domains and transfer domain name registrations among competing accredited/licensed registrars; update domain name registrations; and provide technical
support for accredited/licensed registrars.

	2.
	Accreditation of usTLD Registrars: The Contractor must develop and implement a process describing the manner in which registrars in the
expanded usTLD space will be accredited to register names in the expanded usTLD.

	3.
	Technical Certification of usTLD Registrars: The Contractor must develop and implement a process for technical certification of
registrars in the expanded usTLD space.

	4.
	Develop WHOIS Database: The Contractor must develop an enhanced searchable WHOIS database that contains, or provides reliable access to,
all expanded usTLD registrations. Such WHOIS database must be operated at the registry level (as opposed to at the level of individual accredited registrars) and allow for multiple string and field
searching through a free, public, web-based interface, and consist of at least the following elements:

	a.
	The
name of the second level domain registered;

	b.
	The
IP address of the primary nameserver and secondary nameserver(s) for the registered domain name;

	c.
	The
corresponding names of those nameservers;

	d.
	The
creation date of the registration;

	e.
	The
name and postal address of the domain name holder;

	f.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder; and

	g.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder.

	5.
	Community Outreach Plan: The Contractor must develop a public outreach mechanism whereby the public space can suggest or recommend
additional policies or procedures for the usTLD that may be developed or suggest how existing policy should be modified or updated. 

11

 

C. REPORTING REQUIREMENTS AND DELIVERABLES  

        The Contractor must post the following reports on their Internet site in order to facilitate transparency and public access. 

C.1 Investigational Study (One-Time Report Due Six Months After Purchase Order Award)

        The
Contractor must conduct an investigation and submit a written report to the COTR, within six months after purchase order award, evaluating the compliance of existing
sub-domain managers with the requirements of RFC 1480 and other documented usTLD policies. Such report must recommend structural, procedural, or policy changes designed to enhance such
compliance and increase the value of the locality-based structure to local communities. During this evaluation period, the Contractor must make no additional locality delegations unless otherwise
directed by the Contracting Officer. 

C.2 Progress Reports  

        For the first two years of the purchase order, the Contractor must submit monthly progress reports to the COTR, in writing, detailing the Contractor's progress
towards meeting the purchase order SOW requirements. Thereafter, such reports must be provided to the COTR on a quarterly basis. 

        These
reports must indicate the status of all major events, as well as major work performed during the month, including technical status, accomplishments, and complications experienced
in fulfilling the SOW requirements, and must be submitted in such detail and form as required by the COTR. Such reports must also provide performance data related to operation of the usTLD including,
but not limited to, the following: the total number of registry transactions; the number of new, transferred or deleted registrations in the usTLD (including cumulative registrations over time); the
number of delegated managers and changes in delegated managers in the locality-based usTLD space; the number of registrars accredited to register names in the expanded usTLD space, including the
operational status of those registrars; and any updates or modifications to the shared registration system made by the Contractor. 

12

  

 
 

CLAUSES AND PROVISIONS    
    

1.    52.203-12 DEV 52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS (DEVIATION NOV 1990) (JUN 1997)  

        (a)   Definitions.

        "Agency,"
as used in this clause, means executive agency as defined in 2.101. 

        "Covered
Federal action," as used in this clause, means any of the following Federal actions: 

        (1)   The
awarding of any Federal contract; 

        (2)   The
making of any Federal grant; 

        (3)   The
making of any Federal loan; 

        (4)   The
entering into of any cooperative agreement; and, 

        (5)   The
extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement. 

        "Indian
tribe" and "tribal organization," as used in this clause, have the meaning provided in section 4 of the Indian Self-Determination and Education Assistance Act
(25 U.S.C. 450B) and include Alaskan Natives. 

        "Influencing
or attempting to influence," as used in this clause, means making, with the intent to influence, any communication to or appearance before an officer or employee of any
agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with any covered Federal action. 

        "Local
government," as used in this clause, means a unit of government in a State and, if chartered, established, or otherwise recognized by a State for the performance of a governmental
duty, including a local public authority, a special district, an intrastate district, a council of governments, a sponsor group representative organization, and any other instrumentality of a local
government. 

        "Officer
or employee of an agency," as used in this clause, includes the following individuals who are employed by an agency: 

        (1)   An
individual who is appointed to a position in the Government under title 5, United States Code, including a position under a temporary appointment. 

        (2)   A
member of the uniformed services as defined in subsection 101(3), title 37, United States Code. 

        (3)   A
special Government employee, as defined in section 202, title 18, United States Code. 

        (4)   An
individual who is a member of a Federal advisory committee, as defined by the Federal Advisory Committee Act, title 5, United States Code, appendix 2. 

        "Person,"
as used in this clause, means an individual, corporation, company, association, authority, firm, partnership, society, State, and local government, regardless of whether such
entity is operated for profit or not for profit. This term excludes an Indian tribe, tribal organization, or any other Indian organization with respect to expenditures specifically permitted by other
Federal law. 

        "Reasonable
compensation," as used this clause, means, with respect to a regularly employed officer or employee of any person, compensation that is consistent with the normal
compensation for such officer or employee for work that is not furnished to, not funded by, or not furnished in cooperation with the Federal Government. 

13

 

        "Reasonable
payment," as used this clause, means, with respect to professional and other technical services, a payment in an amount that is consistent with the amount normally paid for
such services in the private sector. 

        "Recipient,"
as used in this clause, includes the Contractor and all subcontractors. This term excludes an Indian tribe, tribal organization, or any other Indian organization with
respect to expenditures specifically permitted by other Federal law. 

        "Regularly
employed," as used in this clause, means, with respect to an officer or employee of a person requesting or receiving a Federal contract, an officer or employee who is employed
by such person for at least 130 working days within 1 year immediately preceding the date of the submission that initiates agency consideration of such person for receipt of such contract. An
officer or employee who is employed by such person for less than 130 working days within 1 year immediately preceding the date of the submission that initiates agency consideration of such
person must be considered to be regularly employed as soon as he or she is employed by such person for 130 working days. 

        "State,"
as used in this clause, means a State of the United States, the District of Columbia, the Commonwealth of Puerto Rico, a territory or possession of the United States, an agency
or instrumentality of a State, and multi-State, regional, or interstate entity having governmental duties and powers. 

        (b)   Prohibitions. 

        (1)   Section 1352
of title 31, United States Code, among other things, prohibits a recipient of a Federal contract, grant, loan, or cooperative agreement from using
appropriated funds to pay any person for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a
Member of Congress in connection with any of the following covered Federal actions: the awarding of any Federal contract; the making of any Federal grant; the making of any Federal loan; the entering
into of any cooperative agreement; or the modification of any Federal contract, grant, loan, or cooperative agreement. 

        (2)   The
Act also requires Contractors to furnish a disclosure if any funds other than Federal appropriated funds (including profit or fee received under a covered Federal
transaction) have been paid, or will be paid, to any person for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress,
or an employee of a Member of Congress in connection with a Federal contract, grant, loan, or cooperative agreement. 

        (3)   The
prohibitions of the Act do not apply under the following conditions: 

          (i)  Agency
and legislative liaison by own employees. 

	(A)
	The
prohibition on the use of appropriated funds, in subparagraph (b)(1) of this clause, does not apply in the case of a payment of reasonable compensation made to an officer or
employee of a person requesting or receiving a covered Federal action if the payment is for agency and legislative liaison activities not directly related to a covered Federal action.

	(B)
	For
purposes of subdivision (b)(3)(i)(A) of this clause, providing any information specifically requested by an agency or Congress is permitted at any time. 

14

 

	(C)
	The
following agency and legislative liaison activities are permitted at any time where they are not related to a specific solicitation for any covered Federal action: 

        (1)   Discussing
with an agency the qualities and characteristics (including individual demonstrations) of the person's products or services, conditions or terms of sale, and
service capabilities. 

        (2)   Technical
discussions and other activities regarding the application or adaptation of the person's products or services for an agency's use. 

	(D)
	The
following agency and legislative liaison activities are permitted where they are prior to formal solicitation of any covered Federal action— 

        (1)   Providing
any information not specifically requested but necessary for an agency to make an informed decision about initiation of a covered Federal action; 

        (2)   Technical
discussions regarding the preparation of an unsolicited proposal prior to its official submission; and 

        (3)   Capability
presentations by persons seeking awards from an agency pursuant to the provisions of the Small Business Act, as amended by Pub. L. 95-507, and
subsequent amendments. 

	(E)
	Only
those services expressly authorized by subdivision (b)(3)(i)(A) of this clause are permitted under this clause. 

         (ii)  Professional
and technical services. 

	(A)
	The
prohibition on the use of appropriated funds, in subparagraph (b)(1) of this clause, does not apply in the case of— 

        (1)   A
payment of reasonable compensation made to an officer or employee of a person requesting or receiving a covered Federal action or an extension, continuation, renewal,
amendment, or modification of a covered Federal action, if payment is for professional or technical services rendered directly in the preparation, submission, or negotiation of any bid, proposal, or
application for that Federal action or for meeting requirements imposed by or pursuant to law as a condition for receiving that Federal action. 

        (2)   Any
reasonable payment to a person, other than an officer or employee of a person requesting or receiving a covered Federal action or any extension, continuation,
renewal, amendment, or modification of a covered Federal action if the payment is for professional or technical services rendered directly in the preparation, submission, or negotiation of any bid,
proposal, or application for that Federal action or for meeting requirements imposed by or pursuant to law as a condition for receiving that Federal
action. Persons other than officers or employees of a person requesting or receiving a covered Federal action include consultants and trade associations. 

	(B)
	For
purposes of subdivision (b)(3)(ii)(A) of this clause, "professional and technical services" must be limited to advice and analysis directly applying any professional or technical
discipline. For example, drafting of a legal document accompanying a bid or proposal by a lawyer is allowable. Similarly, technical advice provided by an engineer on the performance or operational
capability of a piece of equipment rendered directly in the negotiation of a contract is allowable. However, communications with the intent to influence made by a professional (such as a licensed
lawyer) or a technical person (such as a licensed accountant) are not allowable under this section 

15

 

unless
they provide advice and analysis directly applying their professional or technical expertise and unless the advice or analysis is rendered directly and solely in the preparation, submission or
negotiation of a covered Federal action. Thus, for example, communications with the intent to influence made by a lawyer that do not provide legal advice or analysis directly and solely related to the
legal aspects of his or her client's proposal, but generally advocate one proposal over another are not allowable under this section because the lawyer is not providing professional legal services.
Similarly, communications with the intent to influence made by an engineer providing an engineering analysis prior to the preparation or submission of a bid or proposal are not allowable under this
section since the engineer is providing technical services but not directly in the preparation, submission or negotiation of a covered Federal action. 

	(C)
	Requirements
imposed by or pursuant to law as a condition for receiving a covered Federal award include those required by law or regulation and any other requirements in the actual
award documents.

	(D)
	Only
those services expressly authorized by subdivisions (b)(3)(ii)(A)(1) and (2) of this clause are permitted under this clause.

	(E)
	The
reporting requirements of FAR 3.803(a) must not apply with respect to payments of reasonable compensation made to regularly employed officers or employees of a person. 

        (iii)  Selling
activities by independent sales representatives. The prohibition on the use of appropriated funds, in subparagraph (b)(1) of this clause, does not apply to the
following sales activities before an agency by independent sales representatives, provided such activities are prior to formal solicitation by an agency and are specifically limited to the merits of
the matter; 

	(A)
	Discussing
with an agency (including individual demonstrations) the qualities and characteristics of the person's products or services, conditions or terms of sale, and service
capabilities; and

	(B)
	Technical
discussions and other activities regarding the application or adoption of the person's products or services for an agency's use. 

        (c)   Disclosure.

        (1)   The
Contractor who requests or receives from an agency a Federal contract must file with that agency a disclosure form, OMB standard form LLL, Disclosure of Lobbying
Activities, if such person has made or has agreed to make any payment using nonappropriated funds (to include profits from any covered Federal action), which would be prohibited under subparagraph
(b)(1) of this clause, if paid for with appropriated funds. 

        (2)   The
Contractor must file a disclosure form at the end of each calendar quarter in which there occurs any event that materially affects the accuracy of the
information contained in any disclosure form previously filed by such person under subparagraph (c)(1) of this clause. An event that materially affects the accuracy of the information reported
includes— 

          (i)  A
cumulative increase of $25,000 or more in the amount paid or expected to be paid for influencing or attempting to influence a covered Federal action; or 

         (ii)  A
change in the person(s) or individual(s) influencing or attempting to influence a covered Federal action; or 

16

 

        (iii)  A
change in the officer(s), employee(s), or Member(s) contacted to influence or attempt to influence a covered Federal action. 

        (3)   The
Contractor must require the submittal of a certification, and if required, a disclosure form by any person who requests or received any subcontract exceeding
$100,000 under the Federal contract. 

        (4)   All
subcontractor disclosure forms (but not certifications) must be forwarded from tier to tier until received by the prime Contractor. The prime Contractor must submit
all disclosures to the Contracting Officer at the end of the calendar quarter in which the disclosure form is submitted by the subcontractor. Each subcontractor certification must be retained in the
subcontract file of the awarding Contractor. 

        (d)   Agreement.
The Contractor agrees not to make any payment prohibited by this clause. 

        (e)   Penalties.

        (1)   Any
person who makes an expenditure prohibited under paragraph (a) of this clause or who fails to file or amend the disclosure form to be filed or amended by
paragraph (b) of this clause must be subject to civil penalties as provided for by 31 U.S.C. 1352. An imposition of a civil penalty does not prevent the Government from seeking any other remedy
that may be applicable. 

        (2)   Contractors
may rely without liability on the representation made by their subcontractors in the certification and disclosure form. 

        (f)    Cost
allowability. Nothing in this clause makes allowable or reasonable any costs which would otherwise be unallowable or unreasonable. Conversely, costs made
specifically unallowable by the requirements in this clause will not be made allowable under any other provision. 

2.     52.204-6 DATA UNIVERSAL NUMBERING SYSTEM (DUNS) NUMBER (JUNE 1999)  

        (a)   The
offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation "DUNS" followed by the DUNS number that identifies the
offeror's name and address exactly as stated in the offer. The DUNS number is a nine-digit number assigned by Dun and Bradstreet Information Services. 

        (b)   If
the offeror does not have a DUNS number, it should contact Dun and Bradstreet directly to obtain one. A DUNS number will be provided immediately by telephone at no
charge to the offeror. For information on obtaining a DUNS number, the offeror, if located within the United States, should call Dun and Bradstreet at
1-800-333-0505. The offeror should be prepared to provide the following information: 

        (1)   Company
name. 

        (2)   Company
address. 

        (3)   Company
telephone number. 

        (4)   Line
of business. 

        (5)   Chief
executive officer/key manager. 

        (6)   Date
the company was started. 

        (7)   Number
of people employed by the company. 

        (8)   Company
affiliation. 

17

 

        (c)   Offerors
located outside the United States may obtain the location and phone number of the local Dun and Bradstreet Information Services office from the Internet Home
Page at http://www.customerservice@dnb.com

        If
an offeror is unable to locate a local service center, it may send an e-mail to Dun and Bradstreet at  globalinfo@mail.dnb.com

(End
of provision) 

3.    52.213-4 TERMS AND CONDITIONS—SIMPLIFIED ACQUISITIONS (OTHER THAN COMMERCIAL ITEMS) (MAR 2001)  

        (a)   The
Contractor shall comply with the following Federal Acquisition Regulation (FAR) clauses that are incorporated by reference: 

        (1)   The
clauses listed below implement provisions of law or Executive order: 

          (i)  52.222-3,
Convict Labor (AUG 1996) (E.O. 11755). 

         (ii)  52.225-13,
Restrictions on Certain Foreign Purchases (July 2000)(E.O.'s 12722, 12724, 13059, 13067, 13121, and 13129). 

        (iii)  52.233-3,
Protest After Award (AUG 1996) (31 U.S.C. 3553). 

        (2)   Listed
below are additional clauses that apply: 

          (i)  52.232-1,
Payments (APR 1984). 

         (ii)  52.232-8,
Discounts for Prompt Payment (MAY 1997). 

        (iii)  52.232-11,
Extras (APR 1984). 

        (iv)  52.232-25,
Prompt Payment (JUN 1997). 

         (v)  52.233-1,
Disputes (DEC 1998). 

        (vi)  52.244-6,
Subcontracts for Commercial Items and Commercial Components (MAR 2001). 

      (viii)  52.253-1,
Computer Generated Forms (JAN 1991). 

        (b)   The
Contractor shall comply with the following FAR clauses, incorporated by reference, unless the circumstances do not apply: 

        (1)   The
clauses listed below implement provisions of law or Executive order: 

          (i)  52.222-20,
Walsh-Healey Public Contracts Act (DEC 1996) (41 U.S.C. 35-45) (Applies to supply contracts over $10,000 in the United States). 

         (ii)  52.222-26,
Equal Opportunity (FEB 1999) (E.O. 11246) (Applies to contracts over $10,000). 

        (iii)  52.222-35,
Affirmative Action for Disabled Veterans and Veterans of the Vietnam Era (APR 1998) (38 U.S.C. 4212) (Applies to contracts over $10,000). 

        (iv)  52.222-36,
Affirmative Action for Workers with Disabilities (JUN 1998) (29 U.S.C. 793) (Applies to contracts over $10,000). 

         (v)  52.222-37,
Employment Reports on Disabled Veterans and Veterans of the Vietnam Era (JAN 1999) (38 U.S.C. 4212) (Applies to contracts over $10,000). 

18

 

        (vi)  52.222-41,
Service Contract Act of 1965, As Amended (MAY 1989) (41 U.S.C. 351, et seq.) (Applies to service contracts over $2,500). 

       (vii)  52.222-19,
Child Labor—Cooperation with Authorities and Remedies (JAN 2001) (E.O. 13126). (Applies to contracts for supplies exceeding the
micro-purchase threshold.) 

      (viii)  52.223-5,
Pollution Prevention and Right-to-Know Information (APR 1998) (E.O. 12856) (Applies to services performed on Federal
facilities). 

        (ix)  52.225-1,
Buy American Act—Balance of Payments Program—Supplies (FEB 2000) (41 U.S.C. 10a - 10d) (Applies to contracts
for supplies, and to contracts for services involving the furnishing of supplies, for use within the United States if the value of the supply contract or supply portion of a service contract exceeds
the micro-purchase threshold and the acquisition— 

	(A)
	Is
set aside for small business concerns; or

	(B)
	Cannot
be set aside for small business concerns (19.502-2), and does not exceed $25,000). 

         (x)  52.232-33,
Payment by Electronic Funds Transfer—Central Contractor Registration (May 1999). (Applies when the payment will be made by
electronic funds transfer (EFT) and the payment office uses the Central Contractor Registration (CCR) database as its source of EFT information.) 

        (xi)  52.232-34,
Payment by Electronic Funds Transfer—Other than Central Contractor Registration (May 1999). (Applies when the payment will be
made by EFT and the payment office does not use the CCR database as its source of EFT information.) 

       (xii)  52.247-64,
Preference for Privately Owned U.S.-Flag Commercial Vessels (June 2000) (46 U.S.C. 1241). (Applies to supplies transported by
ocean vessels.) 

        (2)   Listed
below are additional clauses that may apply: 

          (i)  52.209-6,
Protecting the Government's Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment (JULY 1995) (Applies to
contracts over $25,000). 

         (ii)  52.211-17,
Delivery of Excess Quantities (SEPT 1989) (Applies to fixed-price supplies). 

        (iii)  52.247-29,
F.o.b. Origin (JUN 1988) (Applies to supplies if delivery is f.o.b. origin). 

        (iv)  52.247-34,
F.o.b. Destination (NOV 1991) (Applies to supplies if delivery is f.o.b. destination). 

        (c)   FAR
52.252-2, Clauses Incorporated by Reference (FEB 1998). This contract incorporates one or more clauses by reference, with the same force and effect as if
they were taken in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):
http://www.arnet.gov/far 

        (d)   Inspection/Acceptance.
The Contractor shall tender for acceptance only those items that conform to the requirements of this contract. The Government reserves the right
to inspect or test any supplies or services that have been tendered for acceptance. The Government may require repair or replacement of nonconforming supplies or reperformance of nonconforming
services at no increase in contract price. The Government must exercise its postacceptance rights— 

        (1)   Within
a reasonable period of time after the defect was discovered or should have been discovered; and 

19

 

        (2)   Before
any substantial change occurs in the condition of the item, unless the change is due to the defect in the item. 

        (e)   Excusable
delays. The Contractor shall be liable for default unless nonperformance is caused by an occurrence beyond the reasonable control of the Contractor and without
its fault or negligence, such as acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes,
unusually severe weather, and delays of common carriers. The Contractor shall notify the Contracting Officer in writing as soon as it is reasonably possible after the commencement of any excusable
delay, setting forth the full particulars in connection therewith, shall remedy such occurrence with all reasonable dispatch, and shall promptly give written notice to the Contracting Officer of the
cessation of such occurrence. 

        (f)    Termination
for the Government's convenience. The Government reserves the right to terminate this contract, or any part hereof, for its sole convenience. In the event of
such termination, the Contractor shall immediately stop all work hereunder and shall immediately cause any and all of its suppliers and subcontractors to cease work. Subject to the terms of this
contract, the Contractor shall be paid a percentage of the contract price reflecting the percentage of the work performed prior to the notice of termination, plus reasonable charges that the
Contractor can demonstrate to the satisfaction of the Government, using its standard record keeping system, have resulted from the termination. The Contractor shall not be required to comply with the
cost accounting standards or contract cost principles for this purpose. This paragraph does not give the Government any right to audit the Contractor's records. The Contractor shall not be paid for
any work performed or costs incurred that reasonably could have been avoided. 

        (g)   Termination
for cause. The Government may terminate this contract, or any part hereof, for cause in the event of any default by the Contractor, or if the Contractor
fails to comply with any contract terms and conditions, or fails to provide the Government, upon request, with adequate assurances of future performance. In the event of termination for cause, the
Government shall not be liable to the Contractor for any amount for supplies or services not accepted, and the Contractor shall be liable to the Government for any and all rights and remedies provided
by law. If it is determined that the Government improperly terminated this contract for default, such termination shall be deemed a termination for convenience. 

        (h)   Warranty.
The Contractor warrants and implies that the items delivered hereunder are merchantable and fit for use for the particular purpose described in this contract. 

(End
of clause) 

4.     52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)  

        (a)   The
Government may extend the term of this contract by written notice to the Contractor within sixty (60) days of expiration of the then-current
contract period, provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least sixty (60) days before the contract expires. The preliminary
notice does not commit the Government to an extension. 

        (b)   If
the Government exercises this option, the extended contract shall be considered to include this option clause. 

20

  

        (c)   The total duration of this contract, including the exercise of any options under this clause, shall not exceed six (6) years. 

        (End
of clause) 

5.    52.227-17 RIGHTS IN DATA—SPECIAL WORKS (JUN 1987)  

        (a)   Definitions.

        "Data,"
as used in this clause, means recorded information regardless of form or the medium on which it may be recorded. The term includes technical data and computer software. The term
does not include information incidental to contract administration, such as financial, administrative, cost or pricing or management information. 

        "Unlimited
rights," as used in this clause, means the right of the Government to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly
and display publicly, in any manner and for any purpose whatsoever, and to have or permit others to do so. 

        (b)   Allocation
of Rights. (1) The Government shall have— 

          (i)  Unlimited
rights in all data delivered under this contract, and in all data first produced in the performance of this contract, except as provided in
paragraph (c) of this clause for copyright. 

         (ii)  The
right to limit exercise of claim to copyright in data first produced in the performance of this contract, and to obtain assignment of copyright in such data, in
accordance with subparagraph (c)(1) of this clause. 

        (iii)  The
right to limit the release and use of certain data in accordance with paragraph (d) of this clause. 

        (2)   The
Contractor shall have, to the extent permission is granted in accordance with subparagraph (c)(1) of this clause, the right to establish claim to copyright
subsisting in data first produced in the performance of this contract. 

        (c)   Copyright—(1)
Data first produced in the performance of this contract. (i) The Contractor agrees not to assert, establish, or authorize others to
assert or establish, any claim to copyright subsisting in any data first produced in the performance of this contract without prior written permission of the Contracting Officer. When claim to
copyright is made, the Contractor shall affix the appropriate copyright notice of 17 U.S.C. 401 or 402 and acknowledgment of Government sponsorship (including contract number) to such data when
delivered to the Government, as well as when the data are published or deposited for registration as a published work in the U.S. Copyright Office. The Contractor grants to the Government, and others
acting on its behalf, a paid-up nonexclusive, irrevocable, worldwide license for all such data to reproduce, prepare derivative works, distribute copies to the public, and perform publicly
and display publicly, by or on behalf of the Government. 

         (ii)  If
the Government desires to obtain copyright in data first produced in the performance of this contract and permission has not been granted as set forth in subdivision
(c)(1)(i) of this clause, the Contracting Officer may direct the Contractor to establish, or authorize the establishment of, claim to copyright in such data and to assign, or obtain the
assignment of, such copyright to the Government or its designated assignee. 

        (2)   Data
not first produced in the performance of this contract. The Contractor shall not, without prior written permission of the Contracting Officer, incorporate in data
delivered under this contract any data not first produced in the performance of this contract and which contain the copyright notice of 17 U.S.C. 401 or 402, unless the Contractor identifies such data
and grants to the Government, or acquires on its behalf, a license of the same scope as set forth in subparagraph (c)(1) of this clause. 

21

 

        (d)   Release
and use restrictions. Except as otherwise specifically provided for in this contract, the Contractor shall not use for purposes other than the performance of
this contract, nor shall the Contractor release, reproduce, distribute, or publish any data first produced in the performance of this contract, nor authorize others to do so, without written
permission of the Contracting Officer. 

        (e)   Indemnity.
The Contractor shall indemnify the Government and its officers, agents, and employees acting for the Government against any liability, including costs and
expenses, incurred as the result of the violation of trade secrets, copyrights, or right of privacy or publicity, arising out of the creation, delivery, publication, or use of any data furnished under
this contract; or any libelous or other unlawful matter contained in such data. The provisions of this paragraph do not apply unless the Government provides notice to the Contractor as soon as
practicable of any claim or suit, affords the Contractor an opportunity under applicable laws, rules, or regulations to participate in the defense thereof, and obtains the Contractor's consent to the
settlement of any suit or claim other than as required by final decree of a court of competent jurisdiction; nor do these provisions apply to material furnished to the Contractor by the Government and
incorporated in data to which this clause applies. 

        (End
of clause) 

6.    1352.233-70 HARMLESS FROM LIABILITY (MARCH 2000)  

        The Contractor shall hold and save the Government, its officers, agents, and employees harmless from liability of any nature or kind, including costs and expenses
to which they may be subject, for or on account of any or all suits or damages of any character whatsoever resulting from injuries or damages sustained by any person or persons or property by virtue
of performance of this contract, arising or resulting in whole or in part from the fault, negligence, wrongful act or wrongful omission of the contractor, or any subcontractor, their employees, and
agents. 

7.    1352.233-71 SERVICE OF PROTESTS (MARCH 2000)  

        An agency protest may be filed with either (1) the Contracting Officer, or (2) at a level above the Contracting Officer, with the agency Protest
Decision Authority. See 64 Fed. Reg. 16,651 (April 6, 1999) (Internet site: http://oamweb.osec.doc.gov/conops/reflib/alp1296.htm) for the procedures for filing agency protests at the level
above the Contracting Officer (with the Protest Decision Authority). Agency protests filed with the Contracting Officer shall be sent to the following address: 

ATTN JOSEPH L. WIDDUP, CONTRACTING OFFICER  

U
S DEPT OF COMMERCE

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY

100 BUREAU DRIVE STOP 3571

BUILDING 301 ROOM B129

GAITHERSBURG MD 20899-3571

PHONE: (301) 975-6324

FAX: (301) 975-8884

EMAIL: Joseph.Widdup@nist.gov 

        If
a protest is filed with either the Protest Decision Authority, or with the General Accounting Office (GAO), a complete copy of the protest (including all attachments) shall be served
upon both the Contracting Officer and Contract Law Division of the Office of the General Counsel within one day of 

22

 

filing
with the Protest Decision Authority or with GAO. Service upon the Contract Law Division shall be made, as follows: 

ATTN
JERRY WALZ, ESQ

U S DEPT OF COMMERCE

OFFICE OF THE GENERAL COUNSEL

CONTRACT LAW DIVISION—RM 5893 HCH BLDG

14TH ST AND CONSTITUTION AVE NW

WASHINGTON DC 20230

FAX: (202) 482-5858 

8.    1352.252-71 REGULATORY NOTICE (MARCH 2000)  

        Offerors are advised that certain provisions and clauses identified with a Commerce Acquisition Regulation (CAR) notation for identification purposes, have not
yet been incorporated into the CAR. However, all of these items are binding for this acquisition and will eventually be contained in the CAR at Part 13 of Title 48 of the Code of Federal
Regulations. 

9.    52.233-1 I DISPUTES (DEC 1998)—ALTERNATE I (DEC 1991)  

        (Reference 33.215) 

10.    52.239-1 PRIVACY OR SECURITY SAFEGUARDS (AUG 1996)  

        (Reference 39.107) 

11.    1352.201-70 CONTRACTING OFFICER'S AUTHORITY (MARCH 2000)  

        The Contracting Officer is the only person authorized to make or approve any changes in any of the requirements of this contract and notwithstanding any
provisions contained elsewhere in this contract, the said authority remains solely in the Contracting Officer. In the event the Contractor makes any changes at the direction of any person other then
the Contracting Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract terms and conditions, including price. 

12.    1352.201-71 CONTRACTING OFFICER'S TECHNICAL REPRESENTATIVE (COTR) (MARCH 2000)  

        a.     (To
be completed at time of award) is hereby designated as the Contracting Officer's Technical Representative (COTR). The COTR may be changed at any time by the
Government without prior notice to the Contractor by a unilateral modification to the Contract. The COTR is located at: 

        To
be completed at time of award 

        b.     The
responsibilities and limitations of the COTR are as follows: 

        (1)   The
COTR is responsible for the technical aspects of the project and serves as technical liaison with the Contractor. The COTR is also responsible for the final
inspection and acceptance of all reports, and such other responsibilities as may be specified in the contract. 

        (2)   The
COTR is not authorized to make any commitments or otherwise obligate the Government or authorize any changes, which affect the Contract price, terms or conditions.
Any Contractor request for changes shall be referred to the Contracting Officer directly or through the COTR. No such changes shall be made without the expressed prior authorization of the Contracting
Officer. The COTR may designate assistant COTR(s) to act for the COTR by naming such assistant(s) 

23

 

in
writing and transmitting a copy of such designation through the Contracting Officer to the Contractor. 

13.    ANSWERS TO ANTICIPATED OFFEROR QUESTIONS  

        A.    What procedure is the Government using to conduct this acquisition? The Government is using Federal Acquisition Regulation
(FAR) Part 13, Simplified Acquisition Procedures, to conduct this acquisition. The entire FAR (including Part 13) may be accessed on the Internet at: http://www.arnet.gov/far. The
competitive solicitation, solicitation amendments, and all questions and answers related to this procurement will only be made available via the Internet at http://www.fedbizops.gov. 

        B.    Is the solicitation available in hard copy? No. The solicitation will only be released and made available in Microsoft
Word 97 format via the Internet at the above web site. Potential offerors are responsible for accessing the web site. Interested parties must respond to the solicitation in order to be considered for
award of any resultant contract. There is no written solicitation document available, telephone requests will not be honored, and no bidders list will be maintained. 

        C.    What organization is currently administering the .us domain space? Under what authority? Network Solutions, Inc.,
21345 Ridgetop Circle, Dulles, VA 20166-6503, a wholly owned subsidiary of VeriSign, Inc., is administering the .us domain space under the authority of Cooperative Agreement No. NCR
92-18724 originally issued by the National Science Foundation in 1992. The cooperative agreement was transferred to DOC in September of 1998 through a memorandum of understanding between
the two agencies. 

        D.    What organizations (by name, address, and phone number) currently have .us addresses? Is there a web site for this, or a database from which a
report could be extracted? (If there is a database from which a report could be extracted, then please extract such a report and send the report to me in Microsoft Word or other windows-based
format.) Because of the hierarchical nature of registrations in the .us domain, there is at present no compiled list or database that includes all registrations in the .us
space. A description of the information that is available can be found on the Official US Domain Registry web site at: http://www.nic.us/register/whois.html. A list of delegated subdomains and related
contacts is provided at: http://www.nic.us/register/register.html. 

        E.    Over the next five years, how many current .us registrants does DOC expect to not renew their registration (at some point during the next five
years) for their .us web site? Because of the hierarchal structure of the usTLD, this information is not directly available. Further, with the introduction of an expanded usTLD
space, it is expected that a considerable number of new registrations will occur. Prospective Contractors should include estimated registration projections in their proposals. 

        F.     Historically, how many registrants, per year, have not renewed their registration for their .us web site? Because of the
hierarchal structure of the usTLD, this information is not directly available. Further, with the introduction of an expanded usTLD space, it is expected that a considerable number of new registrations
will occur. Prospective Contractors should include estimated registration projections in their proposals. 

        G.    Over the next five years, how many new organizations, per year, does DOC expect to register for a new .us web site?
Prospective contractors should include estimated registration projections in their proposals. 

        H.    What is the fee structure that is currently being charged, per registrant, for registration in the .us space? Network
Solutions, Inc., does not charge a fee for registration in the .us space. Organizations approved to register .us domain names by the US Domain Registry may charge a fee, 

24

 

which
is generally nominal in nature. For a fuller description of charges, see the Official US Domain Registry web site at http://www.nic.us/register/cost.html 

        I.     What data will have to be transitioned from the incumbent contractor to the contractor from the new procurement? What format is the data in? When
will that data be transitioned? How will that data be transitioned? Does the Government own that data, or does the incumbent contractor own that data? Pursuant to Amendment 21
to the Cooperative Agreement between the Department of Commerce and Network Solutions, Inc., Network Solutions has agreed, upon designation of a successor registry for .us by the Department, to
use commercially reasonable efforts to cooperate with the Department to facilitate the smooth transition of operation of the .us domain. That cooperation will include timely transfer to the successor
registry of an electronic copy of the then-current top-level domain registration data and, to the extent such information is available, specification of the format of the data.
Network Solutions has also agreed to provide, upon the Department's request, any information or documentation regarding administration of the .us domain that the Department reasonably deems necessary
to secure a successor registry. After the transition period, any rights held by Network Solutions, Inc., as registry in the registry data shall terminate. DOC will license the data on a
non-exclusive, transferable, irrevocable, royalty-free, paid-up basis to the successor registry. 

        J.     Are there minimum facilities requirements (i.e., space, equipment) will companies be expected to meet in order to be considered technically
acceptable from that standpoint? If so, then please specify what those requirements are. There are no minimum facilities requirements per se. Rather, quotations will be
evaluated, in part, on the basis of Offerors demonstrating the quality and adequacy of their technical facilities, equipment, software, hardware, and related technology to meet these requirements. 

        ** Any additional Offeror questions shall be sent by email only to Joseph.Widdup@nist.gov no later than 12:00 noon
Eastern Time on June 29, 2001. Answers to all questions received by then will be posted as amendment(s) to the solicitation. Questions received regarding this solicitation after June 29,
2001 may not be answered by the Government. **

25

 
 
 

REPRESENTATIONS AND CERTIFICATIONS OF OFFERORS    
    

1.    52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS (MAR 2001)  

        (a)   (1)
The North American Industry Classification System (NAICS) code for this acquisition is 541519 

        (2)   The
small business size standard is $18.0 million. 

        (3)   The
small business size standard for a concern which submits an offer in its own name, other than on a construction or service contract, but which proposes to furnish a
product which it did not itself manufacture, is 500 employees. 

        (b)   Representations.
(1) The offeror represents as part of its offer that it o is,
ý is not a small business concern. 

        (2)   [Complete
only if the offeror represented itself as a small business concern in paragraph (b)(1) of this provision.] The offeror
represents, for general statistical purposes, that it o is, o is not, a small disadvantaged
business concern as defined in 13 CFR 124.1002. 

        (3)   [Complete
only if the offeror represented itself as a small business concern in paragraph (b)(1) of this provision.] The offeror
represents as part of its offer that it o is, o is not a women-owned small business concern. 

        (4)   [Complete
only if the offeror represented itself as a small business concern in paragraph (b)(1) of this provision.] The offeror
represents as part of its offer that it o is, o is not a veteran-owned small business concern. 

        (5)   [Complete
only if the offeror represented itself as a veteran-owned small business concern in paragraph (b)(4) of this provision.] The
offeror represents as part of its offer that it o is, o is not a service-disabled
veteran-owned small business concern. 

        (c)   Definitions.
As used in this provision— 

        "Service-disabled veteran-owned small business concern"— 

        (1)   Means
a small business concern— 

          (i)  Not
less than 51 percent of which is owned by one or more service-disabled veterans or, in the case of any publicly owned business, not less than
51 percent of the stock of which is owned by one or more service-disabled veterans; and 

         (ii)  The
management and daily business operations of which are controlled by one or more service-disabled veterans or, in the case of a veteran with permanent and severe
disability, the spouse or permanent caregiver of such veteran. 

        (2)   Service-disabled
veteran means a veteran, as defined in 38 U.S.C. 101(2), with a disability that is service-connected, as defined in 38 U.S.C. 101(16). 

        "Small
business concern," means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government
contracts, and qualified as a small business under the criteria in 13 CFR Part 121 and the size standard in paragraph (a) of this provision. 

        "Veteran-owned
small business concern" means a small business concern— 

        (1)   That
is at least 51 percent owned by one or more women; or, in the case of any publicly owned business, at least 51 percent of the stock of which is owned
by one or more women; and 

26

 

        (2)   The
management and daily business operations of which are controlled by one or more veterans. 

        "Women-owned
small business concern," means a small business concern- 

        (1)   Which
is at least 51 percent owned by one or more women or, in the case of any publicly owned business, at least 51 percent of the stock of which is owned
by one or more women; and 

        (2)   Whose
management and daily business operations are controlled by one or more women. 

        (d)   Notice.
(1) If this solicitation is for supplies and has been set aside, in whole or in part, for small business concerns, then the clause in this solicitation
providing notice of the set-aside contains restrictions on the source of the end items to be furnished. 

        (2)   Under
15 U.S.C. 645(d), any person who misrepresents a firm's status as a small, HUBZone small, small disadvantaged, or women-owned small business concern in order to
obtain a contract to be awarded under the preference programs established pursuant to section 8(a), 8(d), 9, or 15 of the Small Business Act or any other provision of Federal law that
specifically references section 8(d) for a definition of program eligibility, shall— 

          (i)  Be
punished by imposition of fine, imprisonment, or both; 

         (ii)  Be
subject to administrative remedies, including suspension and debarment; and 

        (iii)  Be
ineligible for participation in programs conducted under the authority of the Act. 

        (End
of provision) 

2.    52.203-11 DEV 52.203-11 CERTIFICATION AND DISCLOSURE REGARDING PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS DEVIATION (JAN 1990)  

        (a)   The
definitions and prohibitions contained in the clause, at FAR 52.203-12, Limitation on Payments to Influence Certain Federal Transactions, included in
this solicitation, are hereby incorporated by reference in paragraph (b) of this certification. 

        (b)   The
offeror, by signing its offer, hereby certifies to the best of his or her knowledge and belief as of December 23, 1989 that— 

        (1)   No
Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any agency, a Member of
Congress, an officer or employee of Congress, or an employee of a Member of Congress on his or her behalf in connection with the awarding of a contract resulting from this solicitation; 

        (2)   If
any funds other than Federal appropriated funds (including profit or fee received under a covered Federal transaction) have been paid, or will be paid, to any person
for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress on his or her behalf
in connection with this solicitation, the offeror must complete and submit with its offer, OMB standard form LLL, Disclosure of Lobbying Activities, to the Contracting Officer, and 

        (3)   He
or she will include the language of this certification in all subcontract awards at any tier and require that all recipients of subcontract awards in excess of
$100,000 must certify and disclose accordingly. 

        (c)   Submission
of this certification and disclosure is a prerequisite for making or entering into this contract imposed by section 1352, title 31, United States Code.
Any person who makes an expenditure prohibited under this provision or who fails to file or amend this disclosure form to be filed or amended by this provision, must be subject to a civil penalty of
not less than $10,000, and not more than $100,000, for each such failure. 

        [End
of Clause] 

27

  

 
 

INSTRUCTIONS FOR SUBMITTING QUOTATIONS    
    

        Before submitting a quotation, Offerors are encouraged to review the information on the locality-based usTLD structure and registration policies at:
http://www.nic.us 

The Offeror must submit the ORIGINAL VERSION and TWO COPIES of the Quotation to the following address:

ATTN
JOSEPH L WIDDUP

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY

100 BUREAU DR STOP 3571

BLDG 301 RM B129

GAITHERSBURG MD 20899-3571

M/F SOLICITATION SB1335-01-Q-0740 

Each quotation (original and copies) submitted in response to this solicitation must:

	A.
	Include
resume(s) of key personnel (including education and experience credentials) that would perform and/or manage the requirements of this acquisition.

	B.
	Describe
how the Offeror would satisfy each of the individual requirements described in the "Contractor Requirements" section of the
SOW. (In the event that the provision of the required services would be accomplished through coordinating the resources and services provided by entities other than the prime Contractor, the quotation
must explicitly indicate how the Contractor will ensure that the "Contractor Requirements" will be fulfilled.)

	C.
	In
light of the "Statement of Purpose" in the SOW, present a detailed narrative describing the Offeror's overall vision for future management of the usTLD, including how the Offeror
proposes to make the usTLD more attractive and useful to United States Internet users and the Offeror's expectations for the number of potential usTLD registrants.

	D.
	Describe
any services or functions, if any, the Offeror proposes to perform as part of usTLD management in addition to those listed in the SOW.

	E.
	Demonstrate
clearly, concisely and accurately, in written narrative form, the Offeror's understanding of the current state of the usTLD domain space.

	F.
	Describe,
for the SOW requirement related to the development of a database of usTLD delegated managers, and the development of registrant WHOIS databases (both for the locality-based
usTLD structure and the expanded usTLD space) how the Offeror would collect the necessary information and the technical and operational specifications of the databases.

	G.
	Include
a proposed draft of any contract(s) that the Offeror proposes to use between itself, as Contractor, and usTLD delegated managers (which may include "flow through" registration
agreements to be used by locality-based usTLD registrants) considered necessary to ensure the stable operation of the locality-based usTLD structure and implement necessary policies. Note: The content
of the final version of all such contract(s) must be approved by the Contracting Officer before use by the Contractor in performance of the resultant purchase order.

	H.
	Include
a proposed draft of any contract(s) that the Offeror proposes to use between itself, as Contractor, and expanded usTLD registrars to ensure the stable operation of the expanded
usTLD and implement the necessary policies (which may include shared registration system license agreements, registrar accreditation agreements, and registrant agreements). Note: The content of the
final version of all such contract(s) must be approved by the Contracting Officer before those contract(s) may be used by the Contractor in performance of the resultant purchase order; 

28

 

	I.
	Include
written policies (including implementation details) that the Offeror proposes to follow, as Contractor, during the start-up phase of registrations in the usTLD.
Such description must include the following considerations:

	1)
	How the Offeror would design and implement the "Sunrise Policy" that permits qualified trademark owners to pre-register their trademarks as domain
names in the expanded usTLD space prior to the opening of the expanded usTLD space to wider registration.

	2)
	How the Offeror would implement a uniform domain name dispute resolution procedure intended to resolve disputes arising from "cybersquatting" applicable to the
usTLD (such policy is intended to be modeled upon the ICANN Uniform Domain Name Dispute Resolution Procedure, consistent with modifications necessary for such a policy to be applicable to the usTLD
specifically. Offeror should propose necessary modifications).

	3)
	How the Offeror proposes to implement and enforce the United States nexus requirement intended to preserve the usTLD for use by the community of United States
Internet users.

	4)
	Describe any proposed additional, alternative, or supplemental policies or programs the Offeror considers relevant and essential towards the locality-based
usTLD space or the expanded usTLD space.

        Offerors
should also describe additional procedures that address other considerations than those listed above that they consider relevant to their quotation. 

	J.
	Address the following considerations in the description of the registration process:

	1)
	How the Offeror proposes to address the potential initial "rush" for registrations at the opening of the expanded usTLD space.

	2)
	Describe
the proposed application process for potential registrants;

	3)
	Describe the proposed mechanisms for ensuring that registrants meet registration requirements;

	4)
	Describe
any proposed appeal process that could be used by the applicant as a result of Contractor denial of registration.

	5)
	Describe
any proposed procedure that would permit third parties to seek cancellation of a registration for failure to comply with restrictions imposed by the Contractor.

	K.
	Describe
in detail the proposed mechanisms and community outreach plans for coordinating the current locality-based usTLD users and the mechanism by which the public can suggest or
recommend additional policys or procedures for the usTLD.

	L.
	Describe, in detail, how the Contractor would fund the requirements of this acquisition at no cost to the United States Government.

	M.
	Project/estimate and explain annual Contractor costs for this acquisition in such a way to permit the Government to match those costs to specific SOW Contractor
Requirements.

	N.
	Include detailed proposed financial plans, including, if appropriate, the manner in which fees levied for services rendered by the Contractor would be derived,
considering cost plus a fair and reasonable profit.

	O.
	Describe, in detail, the technical facilities, equipment, software, hardware, and related technology that the Offeror would use to meet the requirements of this
acquisition.

29

 

	P.
	Include no more than five past performance references for other efforts similar in scope to this acquisition that were either (a) completed by the
Offeror (either as a prime Contractor or as a first-tier subcontractor) in the past five years or (b) currently in process. For each past performance reference, include the
following information:

	1.
	Contract
Number/Purchase Order Number;

	2.
	Duration
of the Contract/Purchase Order;

	3.
	Dollar
Value of Contract/Purchase Order (Broken Down on a Per-Year Basis, if Applicable);

	4.
	Contract
type of Contract/Purchase Order (e.g., firm-fixed-price, cost-plus-fixed-fee,
cost-plus-award-fee, fixed-price with economic price adjustment);

	5.
	Name
and Mailing Address of Customer Organization;

	6.
	Technical
Point of Contact at Customer Organization for the Contract/Purchase Order, including Phone Number, Fax Number and Email Address;

	7.
	Information
Noted in I.4 above for an Alternate Customer Organization Point of Contact; and

	8.
	Detailed
Description of the Effort Performed by the Contractor/Subcontractor under the Contract/Purchase Order. 

At the discretion of the Contracting Officer, a site visit to the Offeror's facility(ies) may also be requested and conducted by DOC personnel involved in this acquisition. The
purpose of this visit would be to gather information relevant to the Offeror's submitted quotation. The Contracting Officer would arrange such a visit at least seven days in advance with the
Offeror.

	Q.
	Describe, in detail, proposed performance measures that will provide accurate indicators of the Contractors progress under the project and assessment of
services offered.

	R.
	Include a completed copy of "Offeror Representations and Certifications" from this solicitation.

	S.
	The Offeror's Data Universal Numbering System (DUNS) Number. (See FAR 52.204-6 on page 16 of this solicitation.)

30

  

 
 

EVALUATION CRITERIA FOR AWARD    
    

        A quotation will only be considered if it is submitted by an organization that is (a) incorporated within one of the fifty states of the United States of
America or the District of Columbia or (b) organized under a law of a state of the United States of America. The Contractor must have a physical address within the United States of America or
the District of Columbia and must be able to demonstrate that all primary registry services will remain within the United States of America (including the District of Columbia). 

        The
Government will evaluate quotations submitted in response to this acquisition for services and will award a purchase order to the technically acceptable, responsible Offeror whose
quotation represents the best value. Technical excellence and comprehensiveness of the overall service for usTLD operation is significantly more important than proposed price(s) to .us registrants.
The evaluated price for all quotations, in terms of the price paid by the Government, will be $0.00. This acquisition is being conducted under FAR Part 13, Simplified Acquisition Procedures.
Under FAR Part 13, solicitations are not required to state the relative order of importance assigned to each evaluation factor and subfactor, nor are they required to include subfactors. The
evaluation factors are listed below. 

	•
	Technical
excellence and comprehensiveness of the offered service—For this factor, the Government will evaluate responses to items A through O and item Q in the
"INSTRUCTIONS FOR SUBMITTING QUOTATIONS."

	•
	Past
performance information—For this factor, the Government will evaluate information obtained from past performance references provided by the Offeror in their
quotation in response to item "P" in the "INSTRUCTIONS FOR SUBMITTING QUOTATIONS" section of the solicitation, as well as any other relevant past performance information that the Government obtains
about the Offeror from other sources;

	•
	Reasonableness
of proposed price(s) to .us registrants. For this factor, the Government will determine whether the proposed price(s) to the registrants are fair and
reasonable considering the level of service(s) to be provided to the .us registrants. 

        For
the purposes of this solicitation, "best value" means the expected outcome of an acquisition that, in the Government's estimation, provides the greatest overall benefit in response
to the requirement. In this solicitation, the term "best value" is not meant to imply that a specific tradeoff process (as described in FAR Part 15, Contracting by Negotiation) will be used by
the Government. This acquisition is being conducted under FAR Part 13, Simplified Acquisition Procedures. 

31

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

00001
	

3.	
 	

Effective Date	
 	

 
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

National Inst of Stds and Technology

100 Bureau Drive Stop 3571

Building 301 Room B129

Gaithersbur MD 20899-3571

Widdup, Joseph 301-975-6324
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NUESTAR

1120 Vermont Avenue NW

Suite 400

Washington DC 20005

Vendor ID: 00007158

DUNS: 112403295
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and

Appropriation Data

(if required)	
 	

61010001020400009091900000

9000090900000000000000$US0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

32

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR Subpart 43.103(a)
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

A.	
 	

The purpose of this modification is to modify Section J, Registration Process: Land Rush Implementation, An Overview of the Land Rush Solution, The Benefits of NeuStar's Land Rush Implementation Approach in the Contractor's quotation, which is incorporated by reference into this Purchase Order, as follows:
	

 	
 	

—Delete the batch-based Landrush process originally proposed by the Contractor.
	

 	
 	

—The Contractor must implement increased monitoring of the system loads to ensure equality among its customers and that the Contractor's systems do not become overloaded.
	

 	
 	

—The Contractor must proceed with a first-come-first-served ("FCFS") registration approach following Sunrise.
	

B.	
 	

The adoption of the FCFS approach must not affect the overall timeline for the usTLD startup phases described on page I-2 of the Contractor's quotation. The Sunrise process will remain unchanged.
	

 	
 	

END OF MODIFICATION
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

James A. Casey
	

15B.	
 	

Contractor/Offeror	
 	

/s/ James A. Casey
	

15C.	
 	

Date Signed	
 	

02-04-2002
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Widdup, Joseph

Contracting Officer

301-975-6324

jwiddup@nist.gov
	

16B.	
 	

United States of America	
 	

/s/ Joseph Widdup
	

16C.	
 	

Date Signed	
 	

02-04-2002
	

 	
 	

 	
 	

 	
 	

 

33

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	

1.	
 	

Contract Id Code	
 	

 
	

2.	
 	

Amendment/Modification No.	
 	

0002
	

3.	
 	

Effective Date	
 	

June 14, 2002
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code 000SB

National Inst. Of Stds. And Technology

100 Bureau Drivestop 3571

Building 301 Room B129

Gaithersburg, MD 20899-3571

Widdup, Joseph 301-975-6324
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NEUSTAR

1120 Vermont Avenue NW

Suite 400

Washington, DC 20005

Vendor ID: 00007158

DUNS: 112403295

CAGE:
	

9A	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and

Appropriation Data

(if required)	
 	

61010001020400009091900000

9000090900000000000000$US0.00
	 	 	 	 	 	 	 

34

 

	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR Subpart 43.103(a)
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

A.	
 	

The purpose of this modification is to incorporate the Government-approved version of the Contractor's usTLD Undelegated Name Policy (Interim) into this purchase order in full text. That policy is stated verbatim in the continuation pages of this
modification.
	

B.	
 	

The parties agree that the usTLD Undelegated Name Policy (Interim) in no way affects the Contractor's obligation to produce a report within six months of Purchase Order award, as required by Section C.1 of the Purchase Order.
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

Robert Poulin

Senior Vice President
	

15B.	
 	

Contractor/Offeror	
 	

/s/ Robert Poulin
	

15C.	
 	

Date Signed	
 	

June 14, 2004
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Widdup, Joseph

Contracting Officer

301-975-6324

jwiddup@nist.gov
	

16B.	
 	

United States of America	
 	

/s/ Joseph Widdup
	

16C.	
 	

Date Signed	
 	

June 14, 2002

 
 

usTLD Undelegated Name Policy (Interim)    
    

I.    Background  

        One of NeuStar's primary responsibilities for the usTLD is the enhancement of the locality-based space in .us. The distributed nature of this space has led,
despite the good efforts of many existing delegated managers, to an often poorly coordinated and sometimes "broken" top-level domain. NeuStar is committed, in partnership with existing
delegated managers and users, to improving the coordination, management and operation of the locality space. This policy provides an interim solution for registration of locality-based names, in
formerly undelegated domains, by state and local governments to ensure smooth operation of the existing locality space during this undertaking. 

        This
diagram shows the current basic structure of the usTLD locality space. 

35

 

        Since
its inception, the locality space has operated through "delegated managers". Delegated managers take responsibility for the operation of specified zones within the usTLD structure.
These delegations are based upon "localities," such as cities and counties, and have been third-level delegations in the form <locality>.<state>.us. For example, an entity might
operate as the delegated manager of the domainburke.va.us. As the delegated manager, that entity would be fully responsible for the operation and
maintenance of the delegated domain—the usTLD Administrator maintains no records or information for the zone created by the delegation beyond the actual delegation to the delegated
manager. 

        Under
the government contract between NeuStar and the Department of Commerce ("DoC"), the existing delegated managers maintain their delegations and will operate them in the normal
fashion, but NeuStar is not permitted to make any new delegations until it has completed a report on the status of the locality space and made recommendations on its future operation. In order to
allow the continued operation of the space for local and state governments during this process. NeuStar has developed this interim policy relating to names that were never delegated to a delegated
manager prior to NeuStar's acceptance of the usTLD Administrator role. 

II.    Interim Policy  

        Until completion of the "Compliance Report Process," NeuStar will assume responsibility for the operation of all of the currently undelegated name spaces
identified in RFC 1480 and/or created by the prior usTLD Administrator.NeuStar will become the interim delegated manager for all such names and run the nameservers for those names.NeuStar's role as
the delegated manager for these spaces and its operation of the corresponding nameservers will be an interim role until completion of the usTLD locality space compliance report process. Upon
completion of that process, NeuStar will implement necessary changes, if any, to this policy to realize the goals and requirements set out in the report. Recognizing that this process could result in
a change to the manner in which the undelegated locality-based names are managed, NeuStar has designed the policy below to allow the greatest degree of flexibility while maintaining the integrity of
the hierarchical locality-based domain space. 

III.  Domain Delegations for Undelegated Domains  

        In keeping with the goal of centralizing the technical function of the usTLD, all of the currently undelegated names in the identified usTLD structure will, in
the interim, be delegated(1) to NeuStar.Specifically, NeuStar will be the delegated manager for the following domains to the extent that they were not delegated prior to NeuStar's acceptance of the
administrator role: us.(2) 

	(1)
	A
"delegation" results in the entire authority and responsibility over a given name being assigned to another party. Delegations are implemented via NS (or nameserver) records.

	(2)
	Labels
indicated by "<name>" are labels that may have any number of entries. For example, <state> indicates any of the two-letter postal codes for
the states of the United States and its possessions and territories. 

        <state>.us

        <locality>.<state>.us 

        lib.<state>.us 

        k12.<state>.us 

        pvt.k12.<state>.us

        cc.<state>.us

        tec.<state>.us

36

 

        isa.us 

        nsn.us

        dni.us

        This
approach will allow NeuStar to maintain control of the listed zone while permitted additional records to be registered at higher delegation levels. For example, an entity would not
be permitted to be the delegated manager of some locality.<state>.us. That domain already would be delegated to NeuStar. However, the city or county government for that locality would be
permitted to register its corresponding city or county government name at a level higher (e.g., ci.somelocality.<state>.us or co.somelocality.<state>.us). 

IV.    Registration of Names  

        NeuStar will serve as the registrar for all currently undelegated domains. Adds, modifies, deletes and renewals will be ordered through an Internet GUI or other
process.(3) However, during the time in which this interim policy applies, only state and local government agencies and their designated representatives will be eligible to register new names in
formerly undelegated.US domains.(4) In order to register a name, the registrant must complete the online form (including the provision of all requested information) and agree to the NeuStar.US Domain
Name Registration Terms and Conditions. The data required from registrants in the locality space is the same as in the expanded space. 

	(3)
	Initial
registration processes may be manually run until suitable web-based tools are developed and tested. The basic registration process and requirements will be the
same, however.

	(4)
	As
noted above, for those locality domains already delegated, this policy will not apply and the authorized delegated managers will continue to operate in their normal fashion. 

        Upon
completion submission of the registration information, the entity registering the name will be required to provide the following along with the registration information: 

	•
	If
the entity requesting the name is the entity eligible to hold the name (a local government, for example), then the requester must provide a notarized letter on the
letterhead of the requesting entity stating that the requestor is authorized to request and use the name.

	•
	If
the entity requesting the name is not the entity eligible to hold the name, but is operating under authority of such entity (a hosting company hired by a local
government, for example) then the requester must provide a notarized letter that it is authorized to request the name On behalf of the eligible entity, as well as a notarized letter from the eligible
entity stating that it has authorized the requestor to obtain and maintain the name.

	•
	Once
NeuStar receives the originals of the above letters, the requested name will be activated. 

V. Future Policies and Processes  

        Any registration made under this interim policy will remain subject to the results of the compliance report process. Policies and procedures described in the
compliance report and approved by the DoC will apply to all registered names, including names registered under this interim policy. 

37

  

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0003
	

3.	
 	

Effective Date	
 	

August 17, 2002
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AJF60012

National Inst. Of Stds. And Technology

100 Bureau Drivestop 3571

Building 301 Room B129

Gaithersburg, MD 20899-3571

Widdup, Joseph 301-975-6324
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NEUSTAR

1120 Vermont Avenue NW

Suite 400

Washington, DC 20005

Vendor ID: 00007158

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers is o extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	 	 	 	 	 	 	 

38

 

	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

610100010020400009091900009000009090000000000000$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

(X)	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

 	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor ý is not, o is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

39

 

        THIS
PAGE IS INTENTIONALLY LEFT BLANK 

40

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

        a.     Ms. Sallianne
Schagrin is hereby designated as the Contracting Officer's Technical Representative (COTR). The Government may change the COTR at any time without
prior notice to the Contractor by a unilateral modification to the Contract. The COTR is located at: 

U.
S. Department of Commerce

National Telecommunications and Information Administration (NTIA)

Office of Policy Analysis and Development

1401 Constitution Ave., N.W., Room 4725

Washington, D.C. 20230 

Phone:
(202) 482-1885

Email: SSchagrin@ntia.doc.gov 

        b.     The
responsibilities and limitations of the COTR are as follows: 

        (1)   The
COTR is responsible for the technical aspects of the project and serves as technical liaison with the Contractor. The COTR is the only Government person other than
the Contracting Officer from whom the Contractor may rely for information or guidance related to performance under this purchase order. The COTR is also responsible for the final inspection and
acceptance of all reports, and such other responsibilities as may be specified in the contract. 

        (2)   The
COTR is not authorized to make any commitments or otherwise obligate the Government or authorize any changes that affect the purchase order terms or conditions. Any
Contractor request for changes shall be referred to the Contracting Officer directly or through the COTR. No such changes shall be made without the expressed prior authorization of the Contracting
Officer. The COTR may designate assistant COTR(s) to act for the COTR by naming such assistant(s) in writing and transmitting a copy of such designation through the Contracting Officer to the
Contractor. 

END
OF MODIFICATION 

41

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0004
	

3.	
 	

Effective Date	
 	

 
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code 000SB

National Inst. Of Stds. And Technology

100 Bureau Drive Stop 3571

Building 301 Room B129

Gaithersburg, MD 20899-3571

Widdup, Joseph 301-975-6324
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NEUSTAR

1120 Vermont Avenue NW

Suite 400

Washington, DC 20005

Vendor ID: 00007158

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	 	 	 	 	 	 	 

42

 

	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

610100010020400009091900009000009090000000000000$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.)
	

 	
 	

 	
 	

Set forth item 14, pursuant to the authority of FAR 43.103(a).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 43.103(a)
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

        The purpose of this modification is to incorporate the Government-approved version of the usTLD Reserved Name Registration Process and the.US Validated Domain Registration Process, along with associated
appendices. Those documents are found in the continuation pages of this modification.
	

END OF TEXT

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    
    USTLD RESERVED NAME REGISTRATION PROCESS    
    

        The U. S. Department of Commerce awarded Purchase Order No. SB1335-02-W-0175 ("the contract") to NeuStar, Inc. ("the
Contractor") for management of the.us domain, the country-code toplevel domain uniquely associated with the United States. On April 24, 2002, the.us domain was opened to the general
public for registration. To preserve the U.S. Government presence in the new expanded.us space, the Department of Commerce, working through the Federal CIO Council among others, reserved second-level
domain names that correspond to the names used by the U.S. Government in the.gov space, as well as the names of states and local governments. The reservation list currently appears on the Contractor's
website at http://www.neustar.us. 

        This
document describes the process that the Contractor will use for registration of these names by the appropriate entities. This process is intended to provide a streamlined method for
Federal, State and Local government entities to obtain access to the reserved names. 

Proposed Federal Reserved Name Registration Process  

        The Contractor will serve as the registrar for all reserved name registrations. Registrations, modifications to registrations, deletions and registration renewals
all will be ordered through a formbased registration and certification process. The Contractor will implement the following process: 

Step 1: A pre-populated form will be sent by electronic mail to each Federal government Central Information Officer (CIO). This form will
contain only those names that correspond to the recipient's agency or department. State and local government contacts will receive either email, or direct mail notifications and a web address, which
they can go to for viewing their reserved names. 

43

 

Step 2: In the case of the Federal Government, the CIO will complete the electronic form, selecting the available reserved names they wish to register
along with the term of the registration (yearly or lifetime) and method of payment (credit card). State and local government points of contact will fill out a web form and then mail it to a PO Box
that the Contractor set up. 

Step 3: The CIO will return the completed form by e-mail within 90 days. State and local government points of contact will have
120 days. 

Step 4: Once the Contractor has received the completed form and the appropriate payment, the names will be loaded into the Contractor's Registry system
and the registration point of contact will be notified by email of the name registration(s). 

        The
reserved names will be released for general availability on the date to be identified in the mailing described in Step 1. 

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    
    VALIDATED DOMAIN REGISTRATION PROCESS    
    

        The .US Validated Domain Registration Process is detailed in the sections that follow. The documents provided break down the steps by type. Specifically, what
parts are handled by the systems that the Contractor built for standard .BIZ and .US registrations as well as the manual processes required to complete validation and order entry. 

        The
documents also detail the level of effort required to complete each step in the registration process. In order to give one an understanding of how the level of effort impacts the
Contractor's costs, the incremental time by functional area are categorized for these out of manual processes. This information was used to derive the pricing that is provided in Appendix 3. 

	1.
	Process
Flow 

Appendix 1
contains two process flows. The first process flow details the steps required to process a validated domain registration. The second process flow details the steps required to
process a fully automated domain registration. In the first process flow the incremental level of effort to perform a validated registration are listed. 

	2.
	Process
Flow Description 

Appendix 2
is the process flow description document. This documents provides the details of each step in the registration process as well as the functional areas that are impacted. 

	3.
	Business
Case & Price By Option: 

Appendix 3
contains the pricing options for a validated registration. The Contractor factored into its standard registration business case all of the incremental costs associated with the
Validated Domain Registration Process. After capturing the incremental costs and applying a reasonable margin, the Contractor arrived at what the cost per unit needs to be for a Validated
registration. 

44

  

 
 

AMENDMENT OF SOLICITATION OF CONTRACT    
    

 
 

APPENDIX 1
  VALIDATED DOMAIN REGISTRATION PROCESS    
    

45

 
 
 

APPENDIX 2
  USTLD FEDERAL RESERVE NAME ALLOCATION PROCESS    
    

	STEP
	 	OWNER
	 	ACTIVITY & DESCRIPTION
	 	TRIGGER
	 	SUPPORT TOOL(S)/

SYSTEMS

	

1	
 	

Customer Service	
 	

Send Request Packet to Agency Email full Request Packet with instructions and "terms & conditions" to Federal Agency points of contact. The Request Packet will minimally include;	
 	

DoC Pricing Approval	
 	

1.	
 	

Dol provided Agency email list
	

 	
 	

 	
 	

—	

Reserved names for each agency	
 	

 	
 	

2.	
 	

Agency Master List—excel spreadsheet w/Agency, domain name, and authorized email cross-ref
	

 	
 	

 	
 	

—	

Request instructions	
 	

 	
 	

3.	
 	

Contractor email text, email generator, and receipt email box
	

 	
 	

 	
 	

—	

Terms & Conditions	
 	

 	
 	

4.	
 	

Request packet with;
	

 	
 	

 	
 	

—	

Domain request forms with fields for all domain contacts	
 	

 	
 	

 	
 	

• Reserved name list
	

 	
 	

 	
 	

—	

Credit card authorization form	
 	

 	
 	

 	
 	

• Instructions
	

 	
 	

 	
 	

—	

Pricing and billing sheet	
 	

 	
 	

 	
 	

• Terms & Conditions
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

 	
 	

• Payment authorization
	

2	
 	

Customer Service	
 	

Receive Completed Request Packet	
 	

Email with Request Packet attachment	
 	

1.	
 	

Contractor email address
	

 	
 	

 	
 	

Email with completed Request Packets received via defined and unique Federal Gov't Contractor email address	
 	

 	
 	

2.	
 	

Talisma
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Request Packet
	

3	
 	

Customer Service	
 	

Confirm Authorization	
 	

Email with Request Packet attachment	
 	

1.	
 	

Agency Master List
	

 	
 	

 	
 	

Compare "from" email address and "Agency Name" to Agency Master List content. If the email address and Agency name do not match that contained in the excel spreadsheet a "non confirmed" email response must be sent.	
 	

 	
 	

2.	
 	

Soft -copy pre-written "non- email
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Request Packet
	 	 	 	 	 	 	 	 	 	 	 	 

46

 

	

4	
 	

Customer Service	
 	

Review Completeness	
 	

Email with Request Packet attachment	
 	

1.	
 	

Request Packet Requirements Checklist
	

 	
 	

 	
 	

Review Request Packet completeness ensuring that all forms and fields are included paying special attention to ensure minimally that each domain name has all contact information and that Credit Card authorization is included	
 	

 	
 	

2.	
 	

Pre-written common error response emails
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Request Packet
	

5	
 	

Customer Service	
 	

Review Accuracy	
 	

Email with Request Packet attachment	
 	

1.	
 	

Common Error Checklist
	

 	
 	

 	
 	

Review each form and field to identify incorrect data, data that does not synch from form to form and instances where multiple credit cards are not associated with domain names.	
 	

 	
 	

2.	
 	

Pre-written common error response emails
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Request Packet
	

6	
 	

Customer Service	
 	

Assess Charge & Assign Order Number	
 	

Email with Request Packet attachment	
 	

1.	
 	

Pricing sheet
	

 	
 	

 	
 	

Audit pricing/billing sheet to ensure numbers tie with domain order forms and pricing calculations are correct.	
 	

 	
 	

2.	
 	

Calculator
	

 	
 	

 	
 	

Assign an order number and record such in Talisma and on the paperwork for translation to billing data.	
 	

 	
 	

3.	
 	

Order number tracking sheet
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

4.	
 	

Talisma
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

5.	
 	

Request Packet
	

7	
 	

Customer Service	
 	

Determine if Request Packet Complete	
 	

Completion of Steps 3,4,5, and 6.	
 	

1.	
 	

Agency Master List Updated
	

 	
 	

 	
 	

Record results of preliminary review steps (steps 3-6) in Talisma and on paperwork.	
 	

 	
 	

2.	
 	

Talisma
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Request Packet
	 	 	 	 	 	 	 	 	 	 	 	 

47

 

	

7a	
 	

Customer Service	
 	

Request Packet Incomplete	
 	

Completion of Step 7.	
 	

1.	
 	

Talisma
	

 	
 	

 	
 	

If Request Packet appears to be complete, does not have common/known errors, and is confirmed as being received from an authorized Agency email account then date/time/rep stamp the packet and forward to Finance.	
 	

 	
 	

2.	
 	

Request Packet
	

7b	
 	

Customer Service	
 	

Request Packet Complete	
 	

Completion of Step 7.	
 	

3.	
 	

Email text editor
	

 	
 	

 	
 	

If any error is identified in Steps 3, 4, 5, or 6 such should be record in Talisma and on the paperwork. An email must be crafted with all error details and next steps and then returned to the submitting email address.	
 	

 	
 	

4.	
 	

Talisma Request Packet
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

5.	
 	

Request Packet
	

8	
 	

Finance	
 	

Enter Credit Card Transaction	
 	

Credit Card Authorization form sent by Customer Service	
 	

1.	
 	

Fed Gov't SurePay account
	

 	
 	

 	
 	

Enter each Credit card transaction into the Federal Gov't Reserve Name SurePay account via the web interface. The SurePay order number should be the Customer Service assigned order number to support later reconciliation and research.	
 	

 	
 	

2.	
 	

SurePay interface
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Customer Service assigned order number
	

9	
 	

Finance	
 	

Receive Credit Response	
 	

Entered SurePay transaction	
 	

1.	
 	

Email
	

 	
 	

 	
 	

SurePay shall respond with approval or denial within 5 minutes. The response shall be printed and attached to original credit card authorization noting any pertinent denial information for use by Customer Service. Finance personnel should go to step
14 after sending approvals to Customer Service entry temp or denials to Customer Service lead.	
 	

 	
 	

2.	
 	

Printer
	 	 	 	 	 	 	 	 	 	 	 	 

48

 

	

10	
 	

Customer Service Temp	
 	

Update Contacts	
 	

Credit card approval response from Finance	
 	

1.	
 	

SRS GUI
	

 	
 	

 	
 	

Using the "Modify Domain" transaction command in the CSR GUI change all domain contacts per information contained in the Request Packet. Domain contacts include;	
 	

 	
 	

2.	
 	

"Modify Domain" transaction instructions/job aid
	

 	
 	

 	
 	

—	

Registrant	
 	

 	
 	

3.	
 	

Request Packet
	

 	
 	

 	
 	

—	

Billing	
 	

 	
 	

 	
 	

 
	

 	
 	

 	
 	

—	

Administrative	
 	

 	
 	

 	
 	

 
	

 	
 	

 	
 	

—	

Billing	
 	

 	
 	

 	
 	

 
	

 	
 	

 	
 	

Note the registrant password should be entered into the "name- value pair" field to verify authorization of later changes	
 	

 	
 	

 	
 	

 
	

11	
 	

Customer Service Temp	
 	

Update Registration Period	
 	

Credit card approval response from Finance	
 	

1.	
 	

SRS GUI
	

 	
 	

 	
 	

Using the "renew domain" transaction command in the CSR GUI update the registration period for each domain as indicated in the Request Packet.	
 	

 	
 	

2.	
 	

"Renew Domain" transaction instruction/job aid
	

12	
 	

Customer Service Temp	
 	

Send Confirmation	
 	

Completion of Steps 10 and 11	
 	

1.	
 	

Pre-written confirmation email text
	

 	
 	

 	
 	

Draft confirmation email (utilizing pre-written template) listing all completed/updated domain names, their registration period, and the total credit card charge.	
 	

 	
 	

2.	
 	

List of entered domain names
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Credit card charge details
	 	 	 	 	 	 	 	 	 	 	 	 

49

 

	

13	
 	

Customer Service Temp	
 	

Review & File	
 	

 	
 	

1.	
 	

Full Request Packet with activity not es and date/time stamps
	

 	
 	

 	
 	

Ensure that all necessary activities have been completed and properly noted on paperwork and in Talisma with order number cross- reference. Check Whois and Speed of Light to confirm DNS and Whois propogation.	
 	

 	
 	

2.	
 	

SRS GUI
	

 	
 	

 	
 	

All paperwork to include at least the following must be filed for later retrieval.	
 	

 	
 	

3.	
 	

usTLD Whois
	

 	
 	

 	
 	

—	

Initial Request	
 	

 	
 	

4.	
 	

Speed of Light
	

 	
 	

 	
 	

—	

Order Number	
 	

 	
 	

 	
 	

 
	

 	
 	

 	
 	

—	

Date/time/rep stamps for each activity and disposition	
 	

 	
 	

 	
 	

 
	

 	
 	

 	
 	

—	

SurePay approval/denial response	
 	

 	
 	

 	
 	

 
	

14	
 	

Finance	
 	

Record Billing Transaction	
 	

Step 9	
 	

1.	
 	

Peoplesoft
	

 	
 	

 	
 	

Create a daily Peoplesoft (billing system) transaction tracking all SurePay submissions.	
 	

 	
 	

2.	
 	

SurePay
	

15	
 	

Finance	
 	

Reconcile w/Daily	
 	

 	
 	

1.	
 	

List of prior credit card submissions
	

 	
 	

 	
 	

Reconcile daily SurePay bank clearance list with prior SurePay transaction submissions to ensure accuracy and completeness. Upon accurate reconciliation clear/close Peoplesoft transaction for posting.	
 	

 	
 	

 	
 	

 
	 	 	 	 	 	 	 	 	 	 	 	 

50

 

	

16	
 	

Customer Service	
 	

Audit Review SRS Inventory and Activity reports comparing such to Billing and Talisma activity reports to ensure full reconciliation. Audit approach must confirm that no domain orders have been lost or added and that no financial transactions have
been lost or duplicated.	
 	

 	
 	

1.	
 	

SRS Reserve Name Activity Report
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

2.	
 	

SRS Reserve Name Inventory List
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

3.	
 	

Agency Master List with disposition notes
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

4.	
 	

SurePay Activity List
	

 	
 	

 	
 	

 	

 	
 	

 	
 	

5.	
 	

Peoplesoft Activity List

Note: This process only represents Federal reserve name allocation activities conducted after system and tool development, training, and SurePay account
set-up and does not fully represent the error correction process for submissions that are denied payment authorization or otherwise do not meet the Contractor's full information
requirements. 

51

 
 
 

APPENDIX 3
  PRICING    
    

Option
1

Permanent Reservation: $152 

Option
2

Three-year registration: $168 ($56 per year) 

Option
3

Five-year registration: $180 ($36 per year) 

Option
4

Lifetime registration: $395 

Note:
all prices listed above represent up front fees that must be paid at the time the registration is processed. For example, for a three-year registration, the Contractor will charge
the registrant $168. 

52

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0005
	

3.	
 	

Effective Date	
 	

December 23, 2002
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code 000SB

National Inst. Of Stds. And Technology

100 Bureau Drive Stop 3571

Building 301 Room B129

Gaithersburg, MD 20899-3571

Widdup, Joseph 301-975-6324
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NEUSTAR

1120 Vermont Avenue NW

Suite 400

Washington, DC 20005

Vendor ID: 00007158

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

610100010204000090919000090000090900000000000000$US 0.00
	 	 	 	 	 	 	 

53

 

	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.)
	

 	
 	

 	
 	

Set forth item 14, pursuant to the authority of FAR 43.103(a).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 43.103(a)
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

A.	
 	

The purpose of this modification is to incorporate the usTLD Federal, State and Local Name Request Registration Process that is found on the continuation pages of this modification.
	

END OF TEXT	
 	

 

 
 

usTLD Federal, State and Local Name Request Registration Process    
    

Introduction  

        Prior to the launch of the second-level us domain space, the Contractor, in consultation with the National Telecommunications and Information Administration
(NTIA) within the U. S. Department of Commerce, reserved certain Federal, State, and Local names from open registration to ensure their availability to Federal, State and Local governments.The process
for registering these reserved names was incorporated into this purchase order via Modification No. 0004. 

Additional Governmental Name Requests  

        Recently, representatives from Federal, State and Local government agencies have requested that additional names be registered under the Reserved Name Process.
Consistent with the Contractor's obligations under this purchase order to serve the needs and interests of these users of the usTLD, the Contractor must accommodate such requests following the process
described below.There is no deadline or limited time period for requests for additional names under the Reserved Name Process, as modified. 

Additional Governmental Name Registration Process  

        In order to register additional names, a Federal, State, or Local governmental agency, department or bona fide representative must follow these steps: 

Step
One 

	•
	The
Federal, State or Local governmental agency, department or bona fide representative must contact the Contractor with a request for names serving a governmental function
or purpose. 

54

 

Step
Two 

	•
	The
Contractor must verify the availability of the requested names, reserve the available name requested, and inform the governmental representative of the list of names
that have been "reserved" as a result of their request. 

Step
Three 

	•
	The
Federal, State or Local governmental agency must follow the reserved name registration process incorporated into this purchase order or otherwise approved by the
Contracting Officer for the identified names. 

Requests by a Governmental Agency for Names Currently Registered by the General Public  

        The Contractor must maintain a list of those names, presently registered by members of the general public, for which representatives of Federal, State or Local
government request a reservation in the event that such general public registrations expire. Upon expiration of such registrations, the Contractor must remove the requested name(s) from the general
pool of names available for public registration and place them on the Reserved Name List.The Contractor must inform the Federal, State or Local governmental representative who requested the
reservation that the requested name(s) is now available for registration under the Reserved Name Process, and process the Federal, State or Local governmental entity's request pursuant to the
requirements set forth in this modification to the purchase order. 

55

  

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0006
	

3.	
 	

Effective Date	
 	

January 13, 2003
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code 000SB

National Inst. Of Stds. And Technology

100 Bureau Drive Stop 3571

Building 301 Room B129

Gaithersburg, MD 20899-3571

Widdup, Joseph 301-975-6324
	

7.	
 	

Administered By (if other than item 6)	
 	

Code 0000013

DOC/NOAA/OFA External Customer Acq.

OFA66

1305 East West Highway Suite 7604

Silver Spring, Maryland 20910
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NEUSTAR

1120 Vermont Avenue NW

Suite 400

Washington, DC 20005

Vendor ID: 00007158

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	 	 	 	 	 	 	 

56

 

	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

610100010020400009091900009000009090000000000000$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

(X)	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.)
	

 	
 	

 	
 	

Set forth item 14, pursuant to the authority of FAR 43.103(b).
	

 	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor ý is not, o is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

A.	
 	

The purpose of this modification is to assign administration of all functions listed in Federal Acquisition Regulation (FAR) Subparts 42.302(a) and 42.302(b) to the agency listed in Block 7 of this modification.
	

B.	
 	

This assignment is effective on the date that appears in Block 3 of this modification.
	

END OF TEXT

57

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0007
	

3.	
 	

Effective Date	
 	

February 13, 2003
	

4.	
 	

Requisition/Purchase Req. No.	
 	

NTIA907-3-0055SS
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AMD00065

DOC/NOAA/OFA/ External Customers

c/o CAMS Support Center

209 Perry Parkway, Suite 5

Gaithersburg, MD 20877-2171

Joel L. Perloth 301-258-4505 x258
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NEUSTAR

1120 Vermont Avenue NW

Suite 400

Washington, DC 20005

Vendor ID: 00007158

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	 	 	 	 	 	 	 

58

 

	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.)

Set forth item 14, pursuant to the authority of FAR 43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 52.243-1 "Changes", FAR 43, and MUTUAL AGREEMENT OF BOTH PARTIES
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

Modification no.: 0007 under Purchase Order No. SB1335-02-W-0175 ("the Contract") for management of the.us domain by NeuStar, Inc. ("the Contractor") sets forth the implementation and operation of a second level domain in .us domain pursuant to
the "DotKids Implementation and Efficiency Act of 2002," Public Law No. 107-317. On December 4, 2002, President George W. Bush signed this law requiring NTIA to establish a second level domain within the.us domain to provide access to
material that is suitable for and not harmful to minors.
	

15.A	
 	

Name and Title of Signer (Type or Print)	
 	

 
	

15B.	
 	

Contractor/Offeror	
 	

 
	

15C.	
 	

Date Signed	
 	

 
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.PerlrothAnoaa.gove

301-258-4505 x258
	

16B.	
 	

United States of America	
 	

/s/ Joel L. Perlroth
	

16C.	
 	

Date Signed	
 	

 

59

 

Implementation and Operation of "Kids" Second Level Domain  

        This document describes the Contractor requirements to establish, operate and maintain a second level domain within the United States country code top level
domain as required by Section 4 of Pub. Law No. 107-317. Each of the following tasks shall be completed in accordance with the requirements of Pub. Law
No. 107-317. 

	1.
	The
Contractor shall establish, operate and maintain a second level domain within the United States country code domain to be called the "kid.us" domain.

	2.
	The
Contractor shall establish written content standards for the kids.us domain that ensures access only to material that is suitable for minors and not harmful to minors as such terms
are defined by Pub. Law No. 107-317.

	3.
	The
Contractor shall establish rules and procedures for enforcement and oversight that minimizes the possibility that the kids.us domain provides access to content that is not in
accordance with the standards and requirements of the Contractor.

	4.
	The
Contractor shall establish a process for removing from the kids.us domain any content that is not in accordance with the standards and requirements of the Contractor.

	5.
	The
Contractor shall establish a process to provide registrants in the kids.us domain with an opportunity for a prompt, expeditious, and impartial dispute resolution process regarding
any material of the registrant excluded from the kids.us domain.

	6.
	The
Contractor shall establish procedures and mechanisms to promote the accuracy of contact information submitted by registrants and retained by registrars in the kids.us domain.

	7.
	The
Contractor shall have written agreements with each registrar for the kids.us domain that requires each registrar to:

	a.
	Ensure
that use of the kids.us domain will be in accordance with the standards and requirements of the Contractor.

	b.
	Enter
into a written agreement with each registrant in the kids.us domain to use the kids.us domain in accordance with the standards and requirements of the Contractor; to prohibit
two-way and multiuser interactive services in the kids.us domain, unless the registrant certifies to the registrar that such service will be offered in compliance with the kids.us content
standards and is designed to reduce the risk of exploitation of minors using such two-way and multiuser interactive services; and to prohibit hyperlinks in the kids.us domain that take
kids.us users outside the kids.us domain.

	8.
	The
Contractor shall establish and ensure that the kids.us domain is operational and begins accepting registrations no later than December 3, 2003.

	9.
	The
Contractor shall ensure continuous and uninterrupted service for the kids.us domain during any transition to a successor registry operator for the kids.us domain or the .us domain.

	10.
	The
Contractor shall take any other action that NTIA considers necessary to establish, operate, or maintain the new domain in accordance with the purposes of Section 4 of Pub.
Law No. 107-317, including, but not limited to, the following:

	a.
	The
Contractor shall implement a "Sunrise Period" that permits qualified trademark owners to preregister their trademarks in the kids.us domain prior to general public registration in
the kids.us domain.

	b.
	The
Contractor shall establish, in conjunction with NTIA, a list of domain names (if any) that will be reserved from domain name registration in the kids.us domain. 

60

 

	c.
	The
Contractor shall have written agreements with each registrar for the kids.us domain that requires each registrar to enter into a written agreement with each registrant in the
kids.us domain to subject such kids. us domain name registration to the following us policies and requirements, as may be amended from time to time by the Contractor and approved by the Contracting
Officer: 

            i.  usTLD
Dispute Resolution Policy and Rules; 

           ii.  The
usTLD Nexus Requirements; 

          iii.  Nexus
Dispute Policy and Rules; and 

          iv.  Registration
Review Policy (April 22, 2002) 

	d.
	The
Contractor shall create and maintain a centralized, publicly accessible Whois database for all domain name registrations in the kids.us domain. 

        All
requirements, rules, processes, procedures, mechanisms, fees, agreements and subcontracts required to implement the kids.us domain shall be subject to the Contracting Officer's
approval. 

61

  

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0008
	

3.	
 	

Effective Date	
 	

May 1, 2003
	

4.	
 	

Requisition/Purchase Req. No.	
 	

AJF60000-3-01088
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AMD00065

DOC/NOAA/OFA/ External Customers.

c/o CAMS Support Center

209 Perry Parkway, Suite 5

Gaithersburg, MD 20877

Joel L. Perloth 301-258-4505 x258
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166

Vendor Id: 00001032

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

62

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 52.243-1 "CHANGES", FAR 43 and Mutual Agreement of the Parties
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

Modification No.: 0007 under Purchase order No.: SB1335-02-W-0175 set forth the implementation and operation of a second level domain in.us domain pursuant to the "Dot Kids Implementation and Efficiency Act of 2002" Public Law
No. 107-317
	

This Modification No.: 0008 is being issued to add a new subsection (e) under paragraph 10. Accordingly, paragraph 10 is being deleted and replaced in its entirety.
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

Jeffrey J. Neuman

Director, Law & Policy, NeuStar, Inc.

Jeff.Neuman@NeuStar.US
	

15B.	
 	

Contractor/Offeror	
 	

/s/ Jeffrey J. Neuman
	

15C.	
 	

Date Signed	
 	

May 1, 2003
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.Perlroth@noaa.gov

301-258-4505 x258
	

16B.	
 	

United States of America	
 	

/s/ Joel L. Perlroth
	

16C.	
 	

Date Signed	
 	

May 1, 2003
	

 	
 	

 	
 	

 	
 	

 

63

 

	Schedule

	
Item No.
 
	
 	

Supplies/Services
	
 	

Quantity
	
 	

Unit
	
 	

Unit Price
	
 	

Amount

	
 	
 	

 	
 	

 	
 	

 	
 	

 	
 	

 
	

0001	
 	

BASE PERIOD	
 	

4	
 	

YR	
 	

0.00	
 	

0.00
	

 	
 	

The Contractor must perform the services required by the SOW.	
 	

 	
 	

 	
 	

 	
 	

 
	

 	
 	

Period of Performance: 4 years, beginning on the date of purchase order award	
 	

 	
 	

 	
 	

 	
 	

 

64

 

Implementation and Operation of "Kids" Second Level Domain  

        This document describes the Contractor requirements to establish, operate and maintain a second level domain within the United States country code top level
domain as required by Section 4 of Pub. Law No. 107-317. Each of the following tasks shall be completed in accordance with the requirements of Pub. Law
No. 107-317. 

	1.
	The
Contractor shall establish, operate and maintain a second level domain within the United States country code domain to be called the "kid.us" domain.

	2.
	The
Contractor shall establish written content standards for the kids.us domain that ensures access only to material that is suitable for minors and not harmful to minors as such terms
are defined by Pub. Law No. 107-317.

	3.
	The
Contractor shall establish rules and procedures for enforcement and oversight that minimizes the possibility that the kids.us domain provides access to content that is not in
accordance with the standards and requirements of the Contractor.

	4.
	The
Contractor shall establish a process for removing from the kids.us domain any content that is not in accordance with the standards and requirements of the Contractor.

	5.
	The
Contractor shall establish a process to provide registrants in the kids.us domain with an opportunity for a prompt, expeditious, and impartial dispute resolution process regarding
any material of the registrant excluded from the kids.us domain.

	6.
	The
Contractor shall establish procedures and mechanisms to promote the accuracy of contact information submitted by registrants and retained by registrars in the kids.us domain.

	7.
	The
Contractor shall have written agreements with each registrar for the kids.us domain that requires each registrar to:

	a.
	Ensure
that use of the kids.us domain will be in accordance with the standards and requirements of the Contractor.

	b.
	Enter
into a written agreement with each registrant in the kids.us domain to use the kids.us domain in accordance with the standards and requirements of the Contractor; to prohibit
two-way and multiuser interactive services in the kids.us domain, unless the registrant certifies to the registrar that such service will be offered in compliance with the kids.us content
standards and is designed to reduce the risk of exploitation of minors using such two-way and multiuser interactive services; and to prohibit hyperlinks in the kids.us domain that take
kids.us users outside the kids.us domain.

	8.
	The
Contractor shall establish and ensure that the kids.us domain is operational and begins accepting registrations no later than December 3, 2003.

	9.
	The
Contractor shall ensure continuous and uninterrupted service for the kids.us domain during any transition to a successor registry operator for the kids.us domain or the.us domain.

	10.
	The
Contractor shall take any other action that NTIA considers necessary to establish, operate, or maintain the new domain in accordance with the purposes of Section 4 of Pub.
Law No. 107-317, including, but not limited to, the following:

	a.
	The
Contractor shall implement a "Sunrise Period" that permits qualified trademark owners to preregister their trademarks in the kids.us domain prior to general public registration in
the kids.us domain.

	b.
	The
Contractor shall establish, in conjunction with NTIA, a list of domain names (if any) that will be reserved from domain name registration in the kids.us domain. 

65

 

	c.
	The
Contractor shall have written agreements with each registrar for the kids.us domain that requires each registrar to enter into a written agreement with each registrant in the
kids.us domain to subject such kids. us domain name registration to the following us policies and requirements, as may be amended from time to time by the Contractor and approved by the Contracting
Officer:

	i.
	usTLD
Dispute Resolution Policy and Rules;

	ii.
	The
usTLD Nexus Requirements;

	iii.
	Nexus
Dispute Policy and Rules; and

	iv.
	Registration
Review Policy (April 22, 2002)

	d.
	The
Contractor shall create and maintain a centralized, publicly accessible Whois database for all domain name registrations in the kids.us domain.

	e.
	The Contractor shall serve as Content Manager and is therefore responsible for the content review at the initial stage and through ongoing monitoring. The
Contractor may perform these duties directly or subcontract a portion or all of these duties to a third party(ies).

        All
requirements, rules, processes, procedures, mechanisms, fees, agreements and subcontracts required to implement the kids.us domain shall be subject to the Contracting Officer's
approval. 

66

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0009
	

3.	
 	

Effective Date	
 	

August 19, 2003
	

4.	
 	

Requisition/Purchase Req. No.	
 	

AJF60000-3-01423
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AMD00065

DOC/NOAA/OFA/ External Customers

c/o CAMS Support Center

209 Perry Parkway, Suite 5

Gaithersburg, MD 20877-2171

Joel L. Perloth 301-258-4505 x258
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166

Vendor Id: 00001032

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14, the hour and date specified for receipt of offers is extended o is not extended. Offers must acknowledge
receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

67

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 52.243-1 "CHANGES", FAR 43 and Mutual Agreement of the Parties
	

 	
 	

D.	
 	

Other (specify type of modification and authority)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

Modification No.: 0009 under Purchase order No.: SB1335-02-W-0175 is being issued to accomplish the following:
	

1.	
 	

To extend the date for the usTLD Reserved Name Registration Process until September 30, 2003.
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

Jeffrey J. Neuman

Director, Law & Policy, NeuStar, Inc.

Jeff.Neuman@NeuStar.US
	

15B.	
 	

Contractor/Offeror	
 	

/s/ Jeffrey J. Neuman
	

15C.	
 	

Date Signed	
 	

 
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.Perlroth@noaa.gov

301-258-4505 x258
	

16B.	
 	

United States of America	
 	

/s/ Joel L. Perlroth
	

16C.	
 	

Date Signed	
 	

 

68

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

U.
S. Department of Commerce

National Telecommunications and Information Administration (NTIA)

1401 Constitution Ave., Room 4720

Washington, D.C. 20230

Phone: (202) 482-0775

E-mail: BKFulton(untia.doc.gov 

	0001	 	BASE PERIOD	 	4	 	YR	 	0.00	 	0.00
	

 	
 	

The Contractor must perform the services required by the SOW. Period of Performance: 4 years, beginning on the date of purchase order award	
 	

 	
 	

 	
 	

 	
 	

 

69

  

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0010
	

3.	
 	

Effective Date	
 	

September 30, 2003
	

4.	
 	

Requisition/Purchase Req. No.	
 	

AJF60000-4-00024
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AMD00065

DOC/NOAA/OFA/ External Customers

c/o CAMS Support Center

209 Perry Parkway, Suite 5

Gaithersburg, MD 20877-2171

Joel L. Perloth 301-258-4505 x258
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166

Vendor Id: 00001032

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

70

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of
FAR 43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 52.243-1 "Changes", FAR 43, and Mutual Agreement of the Parties
	

 	
 	

D.	
 	

Other (specify type of modification and authority).

The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

Modification No: 0010 under Purchase Order No. SB1335-02-W-0175 is being issued to accomplish the following:
	

1.	
 	

To extend the date for the Coordination and Management of the.us Top Level Domain (usTLD) Reserved Name Registration Process until December 31, 2003.
	

2.	
 	

To implement interim content monitoring procedures as follows:
	

15.A	
 	

Name and Title of Signer (Type or Print)	
 	

James A. Casey

Director, Policy and Bus. Development
	

15B.	
 	

Contractor/Offeror	
 	

/s/ James A. Casey
	

15C.	
 	

Date Signed	
 	

10/20/03
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.Perlroth@noaa.gov

301-258-4505 x258
	

16B.	
 	

United States of America	
 	

/s/ Joel L. Perlroth
	

16C.	
 	

Date Signed	
 	

10-29-03

 
 

SF 30 Continuation of Block Narrative    
    

        Consistent with Section 10 Paragraph (e) of Modification 8 to the.us requirements, the Contractor shall serve as Content Manager and is therefore
responsible for the content review at the initial stage and through ongoing monitoring. The Contractor may perform these duties directly or subcontract a portion or all of these duties to a third
party(ies). 

71

 

 
 

Schedule    
    

	Item No.
 
	 	Supplies/Services
	 	Quantity
	 	Unit
	 	Unit Price
	 	Amount

	

0001	
 	

BASE PERIOD	
 	

4	
 	

YR	
 	

0.00	
 	

0.00
	

 	
 	

The Contractor must perform the services required by the SOW.	
 	

 	
 	

 	
 	

 	
 	

 

72

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0011
	

3.	
 	

Effective Date	
 	

December 31, 2003
	

4.	
 	

Requisition/Purchase Req. No.	
 	

 
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AMD00065

DOC/NOAA/OFA/ External Customers

c/o CAMS Support Center

209 Perry Parkway, Suite 5

Gaithersburg, MD 20877-2171

Carol A. Silverman 301-258-4506
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166

Vendor Id: 00001032

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

73

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of
FAR 43.103(b).
	

 	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:
	

(X)	
 	

D.	
 	

Other (specify type of modification and authority).

Mutual agreement of the parties. (Ref: Contractor Request dated 12/23/03)
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return    copies to
the issuing office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

        The purpose of this modification is to extend the date for the coordination and management of the .us Top Level Domain (usTLD) Reserved Name Registration Process until March 31, 2004.
	

All other terms and conditions of Order No. DG1335-02-W-0175 remain the same.
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

 
	

15B.	
 	

Contractor/Offeror	
 	

 
	

15C.	
 	

Date Signed	
 	

 
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Carol A. Silverman

Contracting Officer

csilverman@doc.gov

301-258-4506
	

16B.	
 	

United States of America	
 	

/s/ Carol A. Silverman
	

16C.	
 	

Date Signed	
 	

December 31, 2003

 
 

Schedule    
    

	Item No.
 
	 	Supplies/Services
	 	Quantity
	 	Unit
	 	Unit Price
	 	Amount

	 	 	 	 	 	 	 	 	 	 	 
	 	 	 	 	 	 	 	 	 	 	 

74

  

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	

1.	
 	

Contract Id Code	
 	

 
	

2.	
 	

Amendment/Modification No. 0012	
 	

 
	

3.	
 	

Effective Date	
 	

March 31, 2004
	

4.	
 	

Requisition/Purchase Req. No.	
 	

AJF60000-4-00560
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AJF60012

DOC/NOAA/OFA/ External Customers Acq.

OFA66

1305 East West Hwy, Suite 7604

Silver Spring, MD 20910

Joel L. Perloth 301-713-0838 x205
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166

Vendor Id: 00001032

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

75

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

(X)	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

 	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:
	

 	
 	

D.	
 	

Other (specify type of modification and authority).
	

 	
 	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return    copies to
the issuing office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

 	
 	

The purpose of this Modification No. 0012 under Purchase Order No. SB1335-02-W-0175 is being issued to accomplish the following:
	

1.	
 	

To extend the date for the coordination and management of the .us Top Level Domain (usTLD) Reserved Name Registration Process until June 30, 2004.
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

 
	

15B.	
 	

Contractor/Offeror	
 	

 
	

15C.	
 	

Date Signed	
 	

 
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.Perlroth@noaa.gov

301-713-0838 x205
	

16B.	
 	

United States of America	
 	

/s/ Joel L. Perlroth
	

16C.	
 	

Date Signed	
 	

March 31, 2004

 
 

SF 30 Continuation of Block Narrative    
    

2.
To accept the contractors proposed fee of $65.00 per domain name for the direct registration of the reservation list for kids.us 

        All
other terms and conditions remain unchanged. 

	Schedule

	Item No.
	 	Supplies/Services
	 	Quantity
	 	Unit
	 	Unit Price
	 	Amount

	

0001	
 	

BASE PERIOD	
 	

4	
 	

YR	
 	

0.00	
 	

0.00
	

 	
 	

The Contractor must perform the services required by the SOW.	
 	

 	
 	

 	
 	

 	
 	

 
	

 	
 	

Period of Performance: 4 years, beginning on the date of purchase order award	
 	

 	
 	

 	
 	

 	
 	

 

76

 
 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0013
	

3.	
 	

Effective Date	
 	

June 1, 2004
	

4.	
 	

Requisition/Purchase Req. No.	
 	

AJF60000-4-01203
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AJF60012

DOC/NOAA/OFA/ External Customers Acq.

OFA66

1305 East West Hwy, Suite 7604

Silver Spring, MD 20910

Joel L. Perloth 301-713-0838 x205
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166

Vendor Id: 00001032

DUNS: 112403295

CAGE:
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

77

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of FAR
43.103(b).
	

 	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:
	

(X)	
 	

D.	
 	

Other (specify type of modification and authority) Mutual agreement of the Parties.
	

E.	
 	
IMPORTANT: Contractor o is not, ý is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

 	
 	

Modification No. 0013 under Purchase Order No. SB1335-02-W-0175 is being issued to implement the EPP-complaint Redemption Grace Period (RGP) for ".US" domain names in accordance with the attached proposal.
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

Jeffrey J. Neuman

Director, Law & Policy, NeuStar, Inc.

Jeff.Neuman@NeuStar.US
	

15B.	
 	

Contractor/Offeror	
 	

/s/ Jeffrey J. Neuman
	

15C.	
 	

Date Signed	
 	

June 6, 2004
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.Perlroth@noaa.gov

301-713-0838 x205
	

16B.	
 	

United States of America	
 	

 
	

16C.	
 	

Date Signed	
 	

 

OVERVIEW  

        NeuStar proposed the implementation of a fully automated, EPP-compliant Redemption Grace Period (RGP) for .US domain names. The NeuStar RGP will
enable Registrars to restore registered.US domain names that have been inadvertently deleted through registrant or Registrar error, but which are still within a designated 30-day
Redemption Period. 

STATUSES  

        In order to remain EPP-complaint, NeuStar will only use domain statuses defined in the current EPP specifications. As such, all domains slated for
deletion will remain in PendingDelete status for 35 days or until they are restored. 

	•
	All
domains deleted outside the Add Grace Period will be placed on PendingDelete status for a total of 35 days, after
which time the names will be purged from the Registry database and made available again for registration.

	•
	During
this PendingDelete timeframe, domain names will only be redeemable for the first 30 days, and cannot be
otherwise modified. The only action allowed by the Registrar is the restoration of the domain name. 

78

 

	•
	Upon
being placed in PendingDelete status, domain names will be immediately removed from the DNS, but will remain in the
WHOIS with a notation about their dates of deletion in the "Last Updated Date" field.

	•
	At
the conclusion of the 30-day restoration period, the domain will remain on PendingDelete for an additional
five days. During this time, the domain cannot be restored, modified, deleted, or transferred. At the conclusion of this five-day period, the domain will be purged from the Registry
database. 

RESTORE COMMAND  

        NeuStar will use the existing EPP Renew command as the basis for the  Restore command. In
addition, EPP extensions will be used to capture additional required information as set forth below in the section entitled
"Registrar Reporting Requirements." 

REPORTS  

        Registrars may only restore domains in order to correct unintentional deletions caused by the registrant or Registrar. Restoring registered domains in order to
assume the rights to use or sell them will be considered a violation of the Registry-Registrar Agreement. 

Registrar Reporting Requirements  

        Registrars must verify their compliance with the intention of the RGP service by submitting a Registrar Restore Report to the Registry. The primary purpose of the
report is to identify the circumstance that led to the Restore request. NeuStar will take advantage of its "thick" registry to collect the reporting
data at the time the Restore command is submitted. The following data is already collected and stored by the Registry, and as such will not need to be provided separately by the Registrar: 

	•
	WHOIS
data for deleted name, as it existed prior to deletion

	•
	WHOIS
data for deleted name, as it existed at the time of report submission

	•
	Exact
date and time of deletion

	•
	Exact
date and time of redemption 

        In
addition, the following information must be submitted by the Registrar to the Registry as part of the Restore command. Failure to
provide all of the follow data at the time the command is submitted will result in a failure to restore the domain name. 

	•
	Written
explanation and corresponding reason code as to why registered name was restored (e.g., Registrar error, dispute resolution, etc.)

	•
	Written
statement affirming that Registrar has not, unless required by law, restored the.US domain name in question in order to assume the rights to use or sell the name for
itself or for any third party

	•
	Written
statement affirming that information in report is factually accurate to the best of the Registrar's knowledge 

        NeuStar
will retain copies of all Registrar Restore and will provide the United States Department of Commerce with such reports as requested. 

79

 

Registry Reporting Requirements  

        To facilitate the recirculation of unredeemed domain names back into the publicly available pool of names, NeuStar will provide comprehensive, regularly updated
lists of names with a PendingDelete status to all Registrars via an FTP or SCP mechanism; these lists will include corresponding dates of deletion.
Other than as set forth in these paragraphs, no Registrars will be able to modify or restore names with a PendingDelete status. 

FEES  

        NeuStar proposed a tiered fee structure as follows: 

	•
	For
the first five (5) days of the RGP, a domain name that has been unintentionally deleted can be restored for a one-time fee of $6.00.

	•
	The
cost of restoring an accidentally deleted name will be raised to a one-time fee of $40.00 for the remaining 25 days of the RGP. 

        Please
also note that fees associated with the restoration of a domain name through the RGP are separate and apart from the fees that are due and payable to NeuStar for the registration
or renewal of a domain name. Thus, if a domain name is deleted within five (5) days of the expiration of a domain
name registration and a domain name registrant would like to restore the name through the RGP, the registry would charge the registrar the $6 for the restoration plus $5.50 for the renewal of the
domain name. If the restoration occurs more than five (5) days after the expiration of the domain name, the registry would charge the registrar $40 for the restoration of the domain plus $5.50
for the one (1) year renewal of the domain name registration. 

80

  

 
 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT    
    

	1.	 	Contract Id Code	 	 
	

2.	
 	

Amendment/Modification No.	
 	

0014
	

3.	
 	

Effective Date	
 	

September 21, 2004
	

4.	
 	

Requisition/Purchase Req. No.	
 	

NTIA911-4-0111BF
	

5.	
 	

Project No. (If Applicable)	
 	

 
	

6.	
 	

Issued By	
 	

Code AJF60012

DOC/NOAA/OFA/ External Customers,AMD

OFA66

1305 East West Hwy, Suite 7604

Silver Spring, MD 20910

Joel L. Perloth 301-713-0838 x205
	

7.	
 	

Administered By (if other than item 6)	
 	

See Block 6
	

8.	
 	

Name And Address Of Contractor (No. Street, County, And Zip Code)	
 	

NeuStar, Inc.

46000 Center Oak Plaza

Building 10

Sterling VA 20166-6593

Vendor Id: 00001032

DUNS: 112403295

CAGE: 3DXC3
	

9A.	
 	

ý Amendment Of Solicitation No.	
 	

 
	

9B.	
 	

Date (See Item 11)	
 	

 
	

10A.	
 	

ý Modification Of Contractor/Order No.	
 	

SB1335-02-W-0175
	

10B.	
 	

Date (See Item 13)	
 	

October 26, 2001
	

11	
 	

THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
	

o The above numbered solicitation is amended as set forth in item 14. the hour and date specified for receipt of offers o is extended o is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing item 8 and 15, and returning            copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or
(c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOU ACKNOWLEDGEMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY
RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment,
and is received prior to the opening hour and date specified.
	

12.	
 	

Accounting and Appropriation Data (if required)	
 	

$US 0.00
	

13.	
 	

THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESIRED IN ITEM 14
	 	 	 	 	 	 	 

81

 

	

(X)	
 	

A.	
 	

This change order is issued pursuant to: (Specify authority). The changes set forth in item 14 are made in the Contract Order No. In Item 10A.
	

 	
 	

B.	
 	

The above numbered Contract/Order is modified to reflect the administrative charges (such as changes in paying office, appropriation date, etc.) Set forth item 14, pursuant to the authority of
FAR 43.103(b).
	

(X)	
 	

C.	
 	

This supplemental agreement is entered into pursuant to authority of:

FAR 52.243-1 "Changes", and Mutual Agreement of the Parties
	

 	
 	

D.	
 	

Other (specify type of modification and authority)	
 	

 
	

E.	
 	
IMPORTANT: Contractor o is not o, is required to sign this document and return 3 copies to the issuing
office.
	

14.	
 	

Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
	

Modification No. 0014 under Purchase Order No. SB1335-02-W-0175, Coordination and Management of the.us Top Level Domain (usTLD) is being issued to end the usTLD Reserved Name Registration Process (RNRP) in a phased manner by
December 31, 2004 in accordance with the plan and schedule set forth below:
	

15A.	
 	

Name and Title of Signer (Type or Print)	
 	

Jeffrey J. Newman, Esq.

Director, Law & Policy, NeuStar, Inc.

Jeff.Neuman@NeuStar.US
	

15B.	
 	

Contractor/Offeror	
 	

/s/ Jeffrey J. Neuman
	

15C.	
 	

Date Signed	
 	

September 21, 2004
	

16A.	
 	

Name and title of Contracting Officer (Type or Print)	
 	

Joel L. Perlroth

Contracting Officer

Joel.L.Perlroth@noaa.gov

301-713-0838 x205
	

16B.	
 	

United States of America	
 	

/s/ Joel L. Perlroth
	

16C.	
 	

Date Signed	
 	

September 24, 2004

PHASES:  

Phase 1—Review and Cleansing of Reserve List  

        NeuStar will undertake a thorough review of all registration applications received to date. Shared Registration System (SRS) registration data will be
crosschecked with any payments received. At the conclusion of this process, a definitive list of non-registered/non-reserved domain names will be created. This list will be
used to complete the remaining phases. A keyword scan will be performed against the entire set of names will be created. This list will be used to complete the remaining phases. A keyword scan will be
performed against the entire set of non-registered reserved names to identify any potentially sensitive domain names. These domain names will be set aside for further manual review at a
later stage. During this period, NeuStar will work, with the Department of Commerce to make every reasonable effort to reach out to the various affinity groups to notify them of the conclusion of the
reserved name program. NeuStar will publish a press release, send letters, send e-mail, make direct telephone calls, and where possible create articles to be published in relevant affinity
group and stakeholder newsletters. In addition, NeuStar will provide an announcement on the official.us website. 

82

 

Phase 2—Release of Local Names  

        This phase will involve the release of all unregistered or unreserved local names. This includes any city, town, village, borough, rancheria, community, or county
name. This list will contain approximately 51,000 domain names. The names will be released in bulk, however due to the large number of names, the release will occur over a period of several hours. 

Phase 3—Release of all State and Indian Reservation Names  

        All unregistered or unreserved State and Indian Reservation domain names will be released. This will include the various on each name, and state mottos. This list
will contain approximately 600 domain names. 

Phase 4—Interim Review  

        With prior approval of the NTIA, NeuStar will develop a permanent reservation list from the federal government domain names. 

Phase 5—Release of Remaining Names  

        All remaining names not placed in the permanently reserved state during Phase 4 will be released at this point. 

SCHEDULE  

September 30,
2004 

	•
	Phase
1 completed (Review all registration applications, create master list, keyword scan, and affinity group and stakeholder outreach)

	•
	Final
day for accepting Local Name registrations 

October 15,
2004 

	•
	Phase
2 completed (Release Local Names)

	•
	Final
day for accepting State and Indian Reservation registrations 

November 1,
2004 

	•
	Phase
3 completed (Release State and Indian Reservation Names) 

November 15,
2004 

	•
	Phase
4 completed (Review remaining names for permanent reserves)

	•
	Final
day for accepting Federal registrations 

December 15,
2004

Phase 5 completed (Release remaining names) 

83

   Table of Contents  

	Transmittal Letter/Forms	 	Tab
	Acronyms/ Clarification of Terms	 	Tab
	Compliance Matrix	 	Tab
	Solution Summary	 	Tab
	A.    usTLD Team	 	A-1
	B.    Contractor Requirements	 	B.1
	B.1	 	Statement of Purpose	 	B.1-1
	B.2	 	Core Registry Functions	 	B.2-1
	B.2.1	 	Primary usTLD Server	 	B.2-2
	B.2.1.1	 	NeuStar's Multiple Primary Nameservers	 	B.2-3
	B.2.1.2	 	General Description of Proposed Facilities and Systems	 	B.2-3
	B.2.1.3	 	Description of System Functions	 	B.2-6
	B.2.2	 	Secondary usTLD Servers	 	B.2-8
	B.2.3	 	usTLD Zone Files	 	B.2-9
	B.2.3.1	 	Current Zone File Generation—Problems and Solution	 	B.2-9
	B.2.3.2	 	Secure Access to Update Zone File Data	 	B.2-10
	B.2.3.3	 	Frequency of Zone File Generation	 	B.2-11
	B.2.3.4	 	Zone File Generation Architecture	 	B.2-11
	B.2.3.5	 	Zone File Distribution and Publication	 	B.2-11
	B.2.3.6	 	Locations and Architecture	 	B.2-12
	B.2.3.7	 	Frequency of Zone File Publication/Update	 	B.2-13
	B.2.4	 	Whois Database	 	B.2-13
	B.2.5	 	usTLD Delegated Manager Database Administration	 	B.2-15
	B.2.6	 	Data Escrow	 	B.2-16
	B.2.7	 	Industry Representation/Compliance	 	B.2-17
	B.2.8	 	usTLD Public Awareness Initiatives	 	B.2-18
	B.2.8.1	 	Executive Summary	 	B.2-18
	B.2.8.2	 	Background	 	B.2-19
	B.2.8.3	 	Strategic Goal	 	B.2-20
	B.2.8.4	 	Customer Base	 	B.2-20
	B.2.8.5	 	Marketing Objectives	 	B.2-24
	B.2.8.6	 	Market Definition	 	B.2-24
	B.2.8.7	 	Market Opportunity	 	B.2-28
	B.2.8.8	 	Value Proposition	 	B.2-28
	B.2.8.9	 	Channel	 	B.2-31
	B.2.8.10	 	Marketing Plan	 	B.2-32
	B.2.9	 	Integration Assistance	 	B.2-34
	B.2.10	 	Compliance Monitoring	 	B.2-35
	B.2.11	 	Web Site	 	B.2-36

84

 

	B.2.12	 	Documentation and Training	 	B.2-37
	B.2.13	 	Customer Relationship Management	 	B.2-39
	B.2.14	 	Reporting	 	B.2-40
	B.2.15	 	Progress and Quarterly Reporting	 	B.2-41
	B.2.16	 	Help Desk	 	B.2-41
	B.3	 	Core Policy Requirements	 	B.3-1
	B.3.1	 	US Nexus Requirement Implementation	 	B.3-3
	B.3.2	 	Open ccTLD Policies Adoption	 	B.3-5
	B.3.3	 	usTLD Dispute Policies and Sunrise Policy/Implementation	 	B.3-6
	B.3.3.1	 	usTLD Dispute Resolution Policy	 	B.3-6
	B.3.3.2	 	Sunrise Policy and Implementation	 	B.3-8
	B.3.4	 	GAC Principles	 	B.3-10
	B.3.5	 	Additional, Alternative, or Supplemental Policies	 	B.3-10
	B.4	 	Locality-Based usTLD Structure Functions	 	B.4-1
	B.4.1	 	Existing Delegees and Registrants Service Provision	 	B.4-2
	B.4.1.1	 	Needs of Existing Users	 	B.4-2
	B.4.1.2	 	Implementing Services for Delegees	 	B.4-3
	B.4.1.3	 	Providing Support for Registrants	 	B.4-3
	B.4.2	 	Undelegated Third Level SuB.domains Service Provision	 	B.4-4
	B.4.2.1	 	Additional Needs of Undelegated Domains	 	B.4-6
	B.4.2.2	 	Implementing Registrar Services	 	B.4-6
	B.4.2.3	 	Providing Registry Services	 	B.4-7
	B.4.3	 	Locality-Based Process Modernization	 	B.4-7
	B.4.4	 	Current Locality-Based usTLD Users Coordination	 	B.4-8
	B.4.5	 	Compliance with Current Locality-Based usTLD Polices Investigation and Report	 	B.4-8
	B.4.6	 	usTLD Delegated Manager Database Development	 	B.4-12
	B.4.7	 	Whois Database Development	 	B.4-14
	B.5	 	Expanded usTLD Space Functions	 	B.5-1
	B.5.1	 	usTLD Shared Registration System	 	B.5-2
	B.5.2	 	Accreditation Process for usTLD Registrars	 	B.5-3
	B.5.3	 	Technical Certification of usTLD Registrars	 	B.5-4
	B.5.4	 	Whois Database Development	 	B.5-7
	B.5.5	 	Community Outreach Plan	 	B.5-9
	C.    NeuStar's Vision of the usTLD	 	C-1
	D.    Enhancing the Utility of the usTLD	 	D-1
	E.    Current State of the usTLD Domain Space	 	E-1
	F.    Centralized usTLD Database and Enhanced Shared Registration System	 	F-1
	F.1	 	Enhanced Shared Registration System	 	F-2
	F.2	 	Centralized usTLD Database	 	F-3
	G.    Draft Delegated Managers/Administrator Contract	 	G-1

85

 

	H.    Draft Registrar/Registry Contract	 	H-1
	I.    Start-up Phase Policies	 	I-1
	J.    Registration Process	 	J-1
	K.    Outreach to Current Locality-based usTLD Users	 	K-1
	L.    Funding for the usTLD	 	L-1
	M.    Description of Cost Elements	 	M-1
	N.    Pro Forma Projections	 	N-1
	O.    Proposed Technical Plan	 	O-1
	O.1	 	Proposed Technical Facilities and Systems	 	O-2
	O.1.1	 	Registry Facilities Site Description	 	O-2
	O.1.1.1	 	Enhanced Shared Registration System (SRS) Data Center Functional Description	 	O-2
	O.1.1.2	 	Nameserver Sites Functional Description	 	O-5
	O.1.1.3	 	Enhanced SRS Data Center and Nameserver Buildings	 	O-6
	O.1.2	 	Enhanced Shared Registration System Descriptions	 	O-8
	O.1.2.1	 	Enhanced SRS Data Center System Descriptions	 	O-10
	O.1.2.2	 	Nameserver Description	 	O-14
	O.1.3	 	Registry Network System Description	 	O-15
	O.1.3.1	 	Internet Connectivity	 	O-15
	O.1.3.2	 	VPN Registry Management Network	 	O-16
	O.1.4	 	Registry System Application Software	 	O-16
	O.1.4.1	 	Application Components	 	O-16
	O.1.4.2	 	Registry Software Development Methodology	 	O-19
	O.2	 	Registry-Registrar Model and XRP Protocol	 	O-22
	O.3	 	NeuStar's Database Capabilities	 	O-23
	O.3.1	 	Functional Overview	 	O-23
	O.3.2	 	Database System Description	 	O-26
	O.3.3	 	Database Security and Access Privileges	 	O-32
	O.4	 	Zone File Generation	 	O-33
	O.4.1	 	Secure Access to Update Zone File Data	 	O-33
	O.4.2	 	Zone File Generation Architecture	 	O-34
	O.5	 	Zone File Distribution and Publication	 	O-35
	O.5.1	 	Locations of Data Centers Housing Zone File Nameservers	 	O-35
	O.5.2	 	Zone File Publication/Update Architecture	 	O-35
	O.6	 	Billing and Collection System	 	O-37
	O.6.1	 	Technical Capabilities and Characteristics	 	O-37
	O.6.2	 	Security	 	O-43
	O.6.3	 	Access Privileges	 	O-44
	O.6.4	 	Backup and Recovery	 	O-45
	O.6.5	 	Billing and Collection Audits	 	O-46
	O.7	 	Data Escrow and Backup	 	O-47

86

 

	O.7.1	 	Frequency and Procedures for Backup of Data	 	O-47
	O.7.2	 	Backup Hardware and Software Systems	 	O-48
	O.7.3	 	Procedures for Retrieval of Data and Rebuild of the Database	 	O-48
	O.8	 	Whois Databases for Both Registrars and Delegated Managers	 	O-49
	O.8.1	 	Whois Service Functional Description	 	O-50
	O.8.2	 	Whois System Architecture	 	O-52
	O.8.3	 	Network Speed and Proposed Service Levels	 	O-52
	O.9	 	System Security	 	O-54
	O.9.1	 	System Security	 	O-54
	O.9.1.1	 	Enhanced Shared Registration System Data Center Security	 	O-55
	O.9.1.2	 	Nameserver Data Center Security	 	O-58
	O.9.2	 	Physical Security	 	O-59
	O.10	 	Peak Capacities	 	O-61
	O.10.1	 	Enhanced SRS Peak Capacity	 	O-61
	O.10.2	 	Whois Peak Capacity	 	O-62
	O.10.3	 	DNS Query Peak Capacity	 	O-63
	O.11	 	System Reliability	 	O-64
	O.11.1	 	Quality of Service and Performance Measurements	 	O-64
	O.12	 	System Outage Prevention	 	O-65
	O.13	 	System Recovery Procedures	 	O-71
	O.13.1	 	Restoring Enhanced SRS Operations in the Event of a System Outage	 	O-71
	O.13.2	 	Redundant/Diverse Systems for Providing Service in the Event of an Outage	 	O-73
	O.13.3	 	Process for Recovery From Various Types of Failures	 	O-74
	O.13.4	 	Training of Technical Staff Who Will Perform Recovery Procedures	 	O-76
	O.13.5	 	Software and Operating Systems for Restoring System Operations	 	O-76
	O.13.6	 	Hardware Needed To Restore and Run the System	 	O-76
	O.13.7	 	Backup Electrical Power Systems	 	O-76
	O.13.8	 	Projected Time for Restoring the System	 	O-77
	O.13.9	 	Testing the System Restoration Process	 	O-77
	O.13.10	 	Documenting System Outages	 	O-77
	O.13.11	 	Documenting System Problems That Could Result in Outages	 	O-77
	O.14	 	Technical and Other Support	 	O-78
	O.14.1	 	Technical Help Systems	 	O-78
	O.14.2	 	Staffing	 	O-80
	O.14.3	 	Test and Evaluation Facility	 	O-80
	O.14.4	 	Customer Satisfaction Survey	 	O-80
	P.    Past Performance	 	P-1
	P.1	 	Registry, Database, and Internet Experience	 	P-7
	P.2	 	Technical Capabilities	 	P-9
	P.3	 	Past Performance References	 	P-11
	Q.    Performance Measurements	 	Q-1

87

 

	R.    Offerors Representations and Certifications	 	R-1
	S.    NeuStar's DUNs Number	 	S-1
	T.    Transition and Project Plan	 	T-1
	T.1	 	Transition to New usTLD Administrator	 	T-2
	T.1.1	 	Requirements for Successful Transition	 	T-2
	T.1.2	 	Time Line for Transition	 	T-4
	T.1.3	 	Implementation	 	T-5
	T.1.4	 	Resources	 	T-5
	T.2	 	Project Plan	 	T-5
	T.2.1	 	High-level Task Descriptions	 	T-7
	T.2.2	 	Staffing and Organization	 	T-8
	T.2.3	 	Monitoring, Control, and Change Management	 	T-8
	T.2.4	 	Quality Assurance	 	T-8

88

   Acronyms  

	

AAA	
 	

American Arbitration Association
	

ACD	
 	

Automatic Call Distributor
	

AFNOG	
 	

African Network Operators Group
	

API	
 	

Application Program Interface
	

APRICOT	
 	

Asia Pacific Regional Internet Conference on Operational Technologies
	

ARIN	
 	

American Registry for Internet Numbers
	

B&C	
 	

Billing and Collections
	

BEEP	
 	

Blocks Extensible Exchange Protocol
	

CASE	
 	

Computer-Aided Software Engineering
	

ccTLD	
 	

Country Code Top-Level Domain
	

COTR	
 	

Contracting Officer's Technical Representative
	

CRM	
 	

Customer Relationship Management
	

DBMS	
 	

Database Management System
	

DFP	
 	

Dynamic Feedback Protocol
	

DNS	
 	

Domain Name System
	

DOC	
 	

Department of Commerce
	

DUNS	
 	

Data Universal Numbering System
	

FAQ	
 	

Frequently Asked Questions
	

FCC	
 	

Federal Communications Commission
	

ftp	
 	

File Transfer Protocol
	

GDP	
 	

Gross Domestic Product
	

gTLD	
 	

Generic Top-Level Domain
	

http	
 	

Hypertext Transfer Protocol
	

ICANN	
 	

Internet Corporation for Assigned Names and Numbers
	

ICC	
 	

International Chamber of Commerce
	

ID	
 	

Identification
	

IDL	
 	

Interface Domain Language
	

IETF	
 	

Internet Engineering Task Force
	

IP	
 	

Internet Protocol
	

IPC	
 	

Intellectual Property Constituency
	

IPNS	
 	

Internet Property Notification Service
	 	 	 

89

 

	

IPv6	
 	

Internet Protocol Version 6
	

IP Services/Solutions	
 	

Internet Protocol Services or Solutions
	

ISA	
 	

Inter-State authority
	

ISO	
 	

International Organization for Standards
	

ISP	
 	

Internet Service Provider
	

IT	
 	

Information Technology
	

IVR	
 	

Interactive Voice Response
	

LOB	
 	

Line of business
	

M & P	
 	

Methods and Procedures
	

MORs	
 	

Monthly Operation Reviews
	

MTTR	
 	

Mean Time To Repair
	

N + 1	
 	

Needed Number Plus One for A Safety Factor
	

NANPA	
 	

North American Numbering Plan Administrator
	

NANOG	
 	

North American Network Operators Group
	

NDP	
 	

Nexus Dispute Policy
	

NIST	
 	

National Institute of Standards and Technology
	

NOC	
 	

Network Operations Center
	

NPAC	
 	

Number Portability Administration Center
	

NSI	
 	

Network Solutions, Inc.
	

NTIA	
 	

National Telecommunications and Information Administration
	

NXX	
 	

Central Office Code (where N is a number greater than 1 and X is a number greater than 0)
	

OLTP	
 	

Online Transaction Processing
	

OT&E	
 	

Operational Test & Evaluation
	

PGP	
 	

Pretty Good Privacy
	

PKI	
 	

Public Key Infrastructure
	

POC	
 	

Point of Contact
	

PSU	
 	

Production Support Unit
	

QA	
 	

Quality Assurance
	

RAD	
 	

Rapid Application Development
	

RAID	
 	

Redundant Array of Independent Disks
	

RAP	
 	

Registry Authentication Period
	

RFC	
 	

Request for Comment
	

RFQ	
 	

Request for Quotation
	 	 	 

90

 

	

RRP	
 	

Registry-Registrar Protocol
	

RTK	
 	

Registrar Tool Kit
	

Rwhois	
 	

Referral Whois protocol
	

SDA	
 	

Session Distribution Algorithm
	

SDK	
 	

Software Development Kit
	

SIPNS	
 	

Start-up Intellectual Property Notification Service
	

SLA	
 	

Service Level Agreement
	

SLD	
 	

Second-Level Domain
	

SMP	
 	

Symmetric Multiprocessing
	

SMS	
 	

Service Management System
	

SNMP	
 	

Simple Network Management Protocol
	

SOW	
 	

Statement of Work
	

SRS	
 	

Shared Registration System
	

SSL	
 	

Secure Socket Layer
	

SW-CMM	
 	

Software Capability Maturity Model
	

SUDRP	
 	

Start-Up Dispute Resolution Policy
	

TCP	
 	

Transmission Control Protocol
	

TLD	
 	

Top-Level Domain
	

TPC	
 	

Transaction Processing Council
	

tpsC	
 	

Transactions per second
	

UAT	
 	

User Acceptance Test
	

UDRP	
 	

Uniform Dispute Resolution Policy
	

US$	
 	

United States dollars
	

usDRP	
 	

United States Dispute Resolution Policy
	

usTLD	
 	

us Top-Level Domain
	

VoIP	
 	

Voice over IP
	

VPN	
 	

Virtual Private Network
	

WAP	
 	

Wireless Application Protocol
	

WIPO	
 	

World Intellectual Property Organization
	

www	
 	

World Wide Web
	

XML	
 	

eXtensible Markup Language
	

XRP	
 	

eXtensible Registry Protocol

91

 

Clarification of Terms  

	Delegee	 	An entity designated by the past usTLD administrator to be responsible for registering names within the third and fourth levels of the locality-based namespace.
	
Subdelegee	
 	

An entity designated by a delegee to operate a subdomain within the delegee's namespace. The term "delegee" as used in this proposal always includes both delegees and subdelegees.
	
Delegated Manager	
 	

The term "delegated managers" refers collectively to delegees and subdelegees.

92

 

Highlights  

	•
	NeuStar has a legacy of managing public resources in a responsible and neutral manner

	•
	NeuStar has the experience to transition mission critical infrastructure services

	•
	NeuStar has proven experience implementing advanced technologies to increase the utility of public resources

	•
	NeuStar has a legacy of facilitating policy processes in environments with multiple stakeholders

	•
	NeuStar has the financial means and necessary commitment to build and operate mission critical resources

Solution Summary  

        NeuStar, the leading neutral third party administrator of critical public resources, possesses the experience, technical expertise, service capabilities, and
integrity to ensure all the DOC's objectives for managing and enhancing the usTLD namespace are met. 

        The
current United States top-level domain (usTLD) is greatly underutilized. The existing hierarchical structure, operational challenges, limited awareness, service level
issues, and infrastructure needs have resulted in limited adoption and use by the U.S. community. A great opportunity exists to unlock the potential of the usTLD to the benefit of the American people.
Widespread use of the usTLD for e-Gov, consumer, business, and public service applications has the potential to improve the ability of the American people to find information, access
services, to communicate, and to transact business. 

        The
new administrator must meet the critical needs identified by the Department of Commerce (DOC) in order for the U.S. Internet community to realize the full benefit of the usTLD. The
administrator must: 

        Develop
a more robust, certain, and reliable system. 

        Promote
increased use of the usTLD. 

        Create
a centrally administered and efficiently managed structure that ensures confidence and infrastructure stability. 

        Create
a stable, flexible, and balanced environment within the usTLD that is conducive to innovation and that will meet the future demands of potential registrants. 

        Ensure
continued stability of the domain name system as a whole and the usTLD in particular especially through the transition period from the current to the new management structure. 

        Manage
the usTLD so it is consistent with the Internet Corporation for Assigned Names and Numbers' (ICANN) technical management of the domain name space (DNS). 

        Allow
for the adequate protection of intellectual property in the usTLD. 

        Establish
and maintain consistent communication between the Contracting Officer's Technical Representative (COTR), the Contractor, and ICANN. 

        Promote
robust competition within the usTLD. 

        In
order to meet its objectives, the DOC should seek an administrator that can meet the significant challenges outlined below: 

	•
	Manage public resources in a responsible and neutral manner—The usTLD Administrator will be a trustee of an
important public resource. Undertaking the administration of any public 

93

 

resource,
including the usTLD, means taking on an obligation to operate in a fair and even-handed manner, providing equal access and service levels to all. 

	•
	Transition mission critical infrastructure services—Since the existing usTLD space currently contains over 8,000
registrations, and the vast majority of these registrations support important public service and government applications, it is extremely important that a transition take place with zero impact to the
existing usTLD community.

	•
	Implement advanced technologies to meet the needs of the public and private sectors—In order to meet the current
and future needs of the public and private sectors, the usTLD Administrator must be prepared to employ the advanced technologies necessary to meet the demands of a vital public resource. The
technology must be highly reliable, scalable, and secure. The architecture must have attributes that provide for great flexibility in meeting the needs of both the private and public sectors.

	•
	Facilitate policy in an environment with multiple stakeholders—The usTLD will serve a broad spectrum of users.
Given that widespread acceptance and use of the usTLD is expected, the stakeholders in the usTLD collectively represent a group that is as diverse as the American people. The usTLD Administrator
should have the experience necessary to work collaboratively with this diverse group in order to facilitate policy that reflects the needs of the community.

	•
	Ensure the financial commitment and means to build and operate mission critical resources—The usTLD Administrator
must have the necessary financial resources to build the required infrastructure and to sustain the business over the long term. Companies who lack the considerable financial resources required to
build and operate the required infrastructure may have to "cut corners" in their implementation of the usTLD resulting in poor service and inhibiting their ability to introduce enhanced services. 

        NeuStar
is amply qualified to meet these challenges and execute the solution highlighted in the following paragraphs. A chart describing NeuStar's capabilities, qualifications, and
experience is attached to the end of this section. 

The NeuStar Solution  

        Integrity is the cornerstone of NeuStar's solution for the usTLD namespace. Our long-term vision of the usTLD is to see it regarded as the world's
premier country code top-level domain (ccTLD), and that goal can only be achieved by ensuring that every aspect of its administration is managed with integrity. Integrity permeates every
element of our solution and is fundamental to our corporate mission to lead and serve the industry as a neutral third party. We understand that this space is a ccTLD not a generic
top-level domain (gTLD) and is exclusively available to serve the needs of U.S. constituents. Therefore, our solution for administering and enhancing the space is structured with that
awareness. NeuStar will reach out to the industry and the U.S. public to ensure that the interests of all participants will be incorporated into the administration of the usTLD, and this important
public resource will be managed in a manner designed to serve the public interest. Our active, ongoing involvement with the industry provides us with a perspective only experience can impart. We
understand the needs and concerns of the industry for the usTLD namespace and this understanding clarifies our responsibility to develop operations and systems that address those needs while
conducting ourselves in strict adherence to the principles of a neutral third party. If NeuStar did not firmly believe it could meet and exceed the DOC's objectives for the usTLD, through innovation,
dedication, excellence, and integrity, we would not be submitting this proposal. We are committed to managing extremely sensitive proprietary data in an atmosphere of high security and confidentiality
and our goal is the equitable treatment of all participating industry players and stakeholders. 

94

 

        Our
solution can be broken down into four primary components, each of which will be defined below. 

NeuStar Service Administration  

        Every aspect of service administration for the usTLD space must be managed with integrity. NeuStar will do this by ensuring equal access of all industry players
and stakeholders to our locality-based and expanded registry services through a thick registry architecture that operates at the highest levels of availability and security. We will coordinate
disparate user communities under a stable, centralized
umbrella and conduct a phased, customer-focused outreach program through public awareness campaigns, marketing initiatives, and defined, accessible public mechanisms to promote the space as a place
for the U.S. and its citizens. 

        Integrity
requires that the usTLD space be operated in a responsible manner. This includes ensuring there is open communication between the administrator and the DOC, seeking
on-going feedback from users, and introducing various applications and services. In addition, NeuStar will establish an advisory council made up of parties representative of the multiple
constituency interests involved in the space to provide guidance regarding the addition of new features and enhancements. Finally, integrity means ensuring that policies are being applied and followed
appropriately. Our approach is a collaborative one through which we will work with industry players and stakeholders to conduct compliance investigations and develop reports. As the usTLD vendor,
NeuStar understands that it has several roles to play including administrator, registry, and registrar for unallocated localities. Integrity requires that each of these positions be clearly defined
and appropriately managed. NeuStar understands the definitions as well as the distinctions between the three and will serve each role in an independent and neutral manner. A brief summary of some
features of our Service Administration follows. More details may be found in Proposal Section B and Sections B.1 through B.5. 

	•
	NeuStar
will support competition and promote use of the usTLD by encouraging communication, ensuring equitable application of policies and procedures, and cultivating an
environment conducive to innovation

	•
	NeuStar
will provide a comprehensive suite of core registry functions that take into account the needs of all our customers—delegated managers, registrars, and
registrants.

	•
	NeuStar
will leverage our Centralized usTLD Database and Enhanced Shared Registration System (SRS) and implement automated registration processes, updates, and zone file
generation to provide accurate, up-to-date information on demand.

	•
	NeuStar's
policies and processes will be designed to foster collaborative partnerships between the usTLD administrator and the usTLD community.

	•
	NeuStar
will develop policies to ensure our operations serve the public interest

	•
	NeuStar
will modernize the usTLD locality space by working with delegated managers to centralize all data currently managed by locality delegees and subdelegees.

	•
	NeuStar's
expanded usTLD registry will promote registrar competition and encourage registrations in the usTLD namespace. 

Policy Framework  

        Integrity is essential when we establish policies to ensure they are created to serve the needs of the entire U.S. population, are applied in an
even-handed fashion, protect intellectual property and the privacy of individuals, and yet, are not so restrictive as to discourage registrations. NeuStar will ensure, through its policies
and processes, that the space is used appropriately as a ccTLD to serve the public interest. This is a unique opportunity to redefine the space, and it is essential that it be done properly. 

95

 

Some
highlights of our proposed policy are below and more details about them may be found in Proposal Section B.3 Core Policy Requirements and Proposal Section J Registration Process. 

	•
	To
address the complex problem of heavy registration traffic during the start-up, NeuStar will implement a Land Rush policy to provide an effective and fair
method for ensuring stability during the initial registration period of the TLD.

	•
	NeuStar
will implement a Sunrise policy for owners of United States trademark applications and registrations which validates whether the claimed applications or
registrations actually exist within the United States Patent and Trademark Office database, thus eliminating any need for a costly and time-consuming Sunrise dispute resolution mechanism

	•
	NeuStar
will develop a usTLD Dispute Resolution Policy (usDRP) modeled after ICANN's Uniform Dispute Resolution Policy to develop a set of policies and dispute resolution
processes that are simple, effective, and provide a level of accountability for usTLD users.

	•
	NeuStar
will implement a Nexus Requirement that registrants in the usTLD must be citizens or permanent residents of the United States, an entity or organization that is
incorporated within one of the states or territories of the United States, or an entity or organization with a bona fide presence in the United States.

	•
	As
a trustee for the usTLD, NeuStar will hold itself to a Code of Conduct exceeding traditional commercial standards. This code addresses issues such as confidentiality,
equal access to administration services, non-disclosure of proprietary information and user data, as well as others to ensure DNS resources in the usTLD are administered in a fair and
efficient manner that makes them available to all parties.

	•
	NeuStar
will develop a usTLD Policy Advisory Council as an advisory body for usTLD policy operations to ensure representative and unbiased policymaking. This body will
interface with the public and provide an independent forum and mechanism for future development of the usTLD to address recognized public needs, enhancement of privacy protections, or enforcement of
accreditation agreements with registrars. 

Next Generation Technical Infrastructure  

        Integrity of our Technical Infrastructure implies several fundamental requirements. The system must work; the name must resolve. It must be robust, secure,
dependable, and available on a consistent basis. In addition, it must enable enhanced services thereby enhancing the utility of the usTLD to service all U.S. constituencies. As with our approach for
Service Administration, NeuStar will follow an inclusive and responsible process to introduce new uses and will set up mechanisms for feedback. In addition, we will provide documented, disciplined,
systematic, quality processes for transition. As the space is operational, we will be introducing new functionality while commercially live and will ensure existing industry players and stakeholders
experience a seamless transition. Below we describe some features of our technical infrastructure; detailed descriptions can be found in Proposal Section O. 

	•
	NeuStar's
registry architecture is designed to be flexible, scalable, and highly available to virtually eliminate downtime while providing for smooth growth.

	•
	NeuStar
will provide support for the existing usTLD space as well as full registry support to all eligible registrars for the expanded usTLD space.

	•
	NeuStar
proposes the implementation of a centralized usTLD database that includes a Delegated Manager Database and a centralized Whois. 

96

  

	•
	NeuStar
will implement co-active data centers and a number of nameserver data centers to create a resilient infrastructure protected against outages through
redundancy, fault tolerance, and geographic dispersion.

	•
	NeuStar
will frequently arrange for data escrow of the usTLD registry to ensure continued operations and availability in the unlikely case of a catastrophic loss of data.

	•
	NeuStar
will implement near-real-time updates to the zone files and Whois database.

	•
	NeuStar's
high-availability cluster architecture will provide scalable processing throughout, dynamic load balancing between the two data centers, and multiple
high-speed Internet connections.

	•
	NeuStar
will develop and deploy a new, streamlined registry-registrar protocol for the expanded usTLD space called the extensible registry protocol (XRP) that provides more
features, functionality, and greater security than the existing registry/registrar interface. 

Business Plan  

        Business Plan integrity implies that an administrator is financially stable and therefore dependable. NeuStar is financially stable. We are not a
start-up company. We have a reputation for dependability and integrity. We have been in operation for over five years, have a fully funded business plan, and our original line of business
is cash flow and net income positive. Furthermore, with respect to the usTLD space, NeuStar will allocate significant marketing funds to promote it. Another aspect of Business Plan integrity is
developing consistent and equitable pricing strategies. In compliance with the RFQ, NeuStar will not charge the government, nor will we charge those who have existing usTLD
name registries. For new players, we have highly competitive market rates for registry funding. Our for profit commercial enterprise is the right business model for providing stability and utilization
to the namespace. Without profit as a motivator, there is no incentive to be creative or adhere to performance measurements. Risk and reward is an effective vehicle for delivering innovation into a
competitive market. Detailed information about our Business Plan can be found in Proposal Sections L, M, and N. A summary of some of its features follows: 

	•
	NeuStar's
financial stability ensures full funding of the usTLD administration

	•
	Domain
name registrations will be offered at highly competitive prices

	•
	NeuStar
will leverage its existing infrastructure and experience to reduce overall expenses

	•
	NeuStar
has a high confidence level in our expense estimates based on our five plus years of registry experience

	•
	NeuStar
will be responsible to ICANN for all ccTLD fees

	•
	NeuStar's
financial plan is based on a solid understanding of the costs to build and operate a highly stable, next generation registry and on a competitive pricing structure
that will facilitate market adoption. 

NeuStar—Corporate Overview  

        NeuStar is particularly suited to be the administrator responsible for further developing and improving the usTLD. As the leading provider of mission critical
infrastructure and services in North America, NeuStar has as its central purpose, the neutral provisioning of mission critical systems in support of important public resources. 

        Since
its founding in 1996, NeuStar has been selected time and again by the industry in open competitive procurements to provide first-of-a-kind
mission critical services. In this capacity, NeuStar 

97

 

designed,
built, and manages the Number Portability Administration Center (NPAC), one of the largest databases in the world, and is the North American Numbering Plan Administrator (NANPA) whose duties
include operating the public telephone numbering database for North America. Integrity and accuracy are the underpinnings of these services which affects virtually every telephone call placed within
the United States and 18 other countries, including Canada. In addition, in a highly competitive bid for expansion of the Internet's Top Level Domains, NeuLevel, a subsidiary of NeuStar, was selected
to serve as the registry operator for dot-biz. 

        The
"Neu" in NeuStar refers to its trusted, neutral, third party role. All of its services are available to all service providers on non-discriminatory terms. Its entire
staff is sworn to a corporate Code of Conduct and voluntarily subjects itself to independent quarterly audits, reported publicly, verifying its compliance to this Code. The critical nature of the
industry functions with which NeuStar has been entrusted leads it to serve all stakeholders: regulators, standards bodies, industry and public interest groups, as well as all segments of the
communications industry itself. It does so in a policy-neutral manner, providing important technical and operational subject matter expertise. Its mission is to remain the trusted, neutral third party
that all these stakeholders have come to rely upon. The "Star" in NeuStar refers to its central role as a trusted clearinghouse, the hub to which communications networks connect. As the administrator,
NeuStar will ensure the usTLD namespace is available to users on a neutral and equitable basis. 

        For
all vendors, past performance is indicative of future accomplishment and NeuStar's serious, corporate commitment to the neutral, even-handed administration of
communications resources is peerless. The following descriptions demonstrate our varied and rich experience in providing communications services. For each of our services, NeuStar created the
necessary systems from scratch with the long-term interests of the industry in mind. We worked closely with the industry while developing these to ensure we met its initial and ongoing
needs. We hope to enjoy that same productive working relationship with the DOC to ensure its evolving priorities and requirements to enhance the operation and utilization of the usTLD are also met. 

        NeuStar
offers a diverse range of products and services for the communications industry that can be broken down into three main categories: 

	•
	Internet
Protocol (IP) Services

	•
	Numbering
Services

	•
	Operational
Support Systems (OSS) Commercial Services 

IP Services  

        "Next-Gen" Registry for dot-biz—NeuStar, through its majority owned NeuLevel
joint venture, was recently selected in November, 2000, to operate the new top-level domain registry for dot-biz. The dot-biz registry will be successful because of
the combined skill sets of both NeuLevel and NeuStar. NeuLevel is the ICANN accredited registry for dot-biz and provides the marketing, sales, and service delivery of dot-biz
registrations. NeuStar, the majority owner of NeuLevel, has designed, is developing, and will implement, operate, and manage the technical infrastructure of the dot-biz "thick" registry
platform. NeuStar also provides standards development, external affairs, and additional corporate support services to ensure the success of dot-biz. NeuLevel was selected by the Internet
Corporation for Assigned Names and Numbers (ICANN) from over 40 respondents as the result of a worldwide, competitive procurement to develop the only top-level Internet domain created
exclusively for business activity. This new TLD will be the place for businesses to establish their presence on the Internet. In addition, dot-biz will open the Internet to more businesses
and support the introduction of new products and functionality that will provide increased services for the business community. 

98

 

        Convergence Directories—NeuStar is leading the development and introduction of a suite of Global Directory Services that
include national and international ENUM administration, as well as next generation signaling standards that will bring intelligent network capabilities to IP based networks. Collectively, NeuStar's
Global Directory Services will facilitate the convergence and interoperability of the Public Switched Telephone Network (PSTN) and IP based networks. As co-chair of the Internet
Engineering Task Force Working Group (IETF WG) that has finalized the ENUM standard, NeuStar is a recognized leader in the development of technologies required for the introduction of next generation
network services. NeuStar continues its leadership role by working closely with the communications industry, regulators, and standards bodies to leverage the ENUM standard to efficiently connect
networks and to enable a broad range of converged services. 

Numbering Services  

        North American Numbering Plan Administration (NANPA)—NeuStar operates the telephone numbering registry
for the North American Numbering Plan as a public resource, serving customers throughout the United States, Canada, Bermuda, and many of the Caribbean Islands. It is the centralized source for
assigning all Number Plan Area (NPA) codes and central office codes, and coordinating NPA code relief as the demand for numbers increases. NeuStar became the NANPA on October 9, 1997 for a
five-year period that began formally on February 21, 1998. The Federal Communications Commission (FCC) and the North American Numbering Council (NANC), an industry group advising
the FCC on numbering issues, selected NeuStar through a competitive bidding process. NeuStar transitioned this responsibility from the original Regional Bell Operating Companies and the former
Bellcore in a highly responsible manner, transparent to the public. As designated in NeuStar's agreement with the FCC and the NANC, NeuStar ensures timely, equitable, and efficient administration of
the rapidly growing number of requests for NPA codes and central office codes by working with all industry stakeholders. 

        Number Portability Administration Center (NPAC)—In April 1996, NeuStar was chosen to serve as the Local Number
Portability Administrator (LNPA) through 2003. The contract was recently extended until 2006. In that role, NeuStar operates the routing registry for North America that allows customers to keep their
existing phone numbers when changing local service providers. NeuStar's development and operation of the NPAC in Chicago, Illinois, provides a master registry of routing information that interfaces
with local carriers. Virtually all calls in North America query a copy of NeuStar's database to be properly routed. Through this center, NeuStar coordinates the porting of local telephone numbers
between carriers in North America, serving more than 250 service providers daily and porting more than one million numbers each month. 

        Number Pooling Administration—As proven by NeuStar, number pooling has the potential to extend the North American Numbering
Plan's (NANP) life well into the next century. NeuStar has been the Pooling Administrator for over two years for U.S. pooling trials in several states and number planning areas, and in June, 2001,
NeuStar was selected as the National Number Pooling Administer by the FCC. Number pooling, also known as thousands-block pooling, allows for the disbursement of numbers to service providers in 1,000
number parcels. NeuStar worked with the telecommunications industry to develop the initial Pooling Administration guidelines in New York and Illinois in 1997-1998. The current guidelines
are based upon those findings and have spurred the demand for pooling implementation in several other states. NeuStar continues to work with the Industry Numbering Council (INC) to suggest and modify
changes to current pooling guidelines based upon NeuStar's actual experiences with pooling trials. 

        ETNS—In March 2001 the European Radiocommunications Office (ERO)—a permanent office of the European
Committee on Telecommunications Regulatory Affairs of CEPT (European Conference of Postal and Telecommunications Administrations) and a center of expertise in the fields of licensing, numbering, and
radiocommunications—selected NeuStar in a competitive bidding process to manage 

99

 

the
establishment of the European Telephony Numbering Space (ETNS) to establish a single country code for all of Europe and assist in enhancing the availability of pan-European
telecommunications services. A pan-European service is an international service that can be invoked from at least two European countries. The designation of a new European country
code—388—allows European international companies, services, and individuals to obtain a single European Number for accessing their services. In this role, NeuStar will manage a
pan-European numbering registry for the provisioning of critical public resources. 

OSS Commercial Services  

        NeuStar's commercial services build on the company's strength as a neutral third-party in developing and managing complex database systems and network elements.
New commercial services are designed to help the industry improve operational efficiencies while saving time and money. 

        CARE Clearinghouse—An industry solution for Customer Account Record Exchange (CARE), the CARE Clearinghouse simplifies the
mechanized exchange of customer information between long distance and competitive local exchange carriers. NeuStar's CARE Clearinghouse service supports CARE industry standards. CARE Clearinghouse
participants benefit from expedited CARE processing and reduced costs. 

        IdentiBaseSM—A solution to number registry problems resulting from deregulation, number portability, pooling,
and local competition. With IdentiBaseSM, the Local Service Provider of any telephone number—ported, pooled, or not—can be identified whenever it is needed, in
whatever format is desired. Information from IdentiBaseSM can help improve billing, provisioning, order entry, trouble management and universal emergency services.
IdentiBaseSM's flexible, easy-to-query, timely data allows each department to better serve the customer base, increase revenue, decrease costs, and reduce
customer churn. 

        NeuStar
has rich experience in successfully building databases and establishing clearinghouse services that benefit the communications industry and has been widely recognized for this.
Yet our expertise is not limited to systems development, and we are not merely a systems developer. We actually operate and support the systems we develop. We manage a complete
start-to-finish solution. Working closely with our clients we design, develop, and create systems. We then implement and support them which allows us to understand
first-hand any issues that arise and to address them quickly and intelligently. It also enables us to recognize and mitigate problems we encounter and readily adapt appropriate methods and
procedures. We will assume direct accountability for the administration of the usTLD from beginning to end, because we provide services, not just systems or software. 

        In
addition, NeuStar's corporate mission is to lead and serve the industry as a neutral third party. Neutrality for us is not a platitude; it is our identity, embodying the impeccable,
high-quality, even-handed service essential to the central role we play in the industry. We are committed to impartiality and fairness, and our staff has a history of
recognizing the importance of understanding and working successfully with the various industry participants and respecting their differing perspectives within the confines of regulatory environments.
Our adherence to the tenets of neutrality does not come from a desire to please nor is it considered an obligation. Rather, it is what we were established to do. Neutrality is a belief we embrace and
have embodied in the Code of Conduct available on NeuStar's Web site. We satisfy the strict criteria established for neutrality by the FCC and have been certified as a neutral third party in FCC order
99-346. To ensure our impartiality, we undergo a quarterly neutrality audit. We are committed to managing extremely sensitive proprietary data in an atmosphere of high security and
confidentiality and our goal is the equitable treatment of all participating industry players. 

100

 

Conclusion  

        NeuStar's believes that it is uniquely qualified to ensure the success of the usTLD. Our plan builds on our legacy of managing public resources in a responsible
and neutral manner. Neu-Star's proven experience in implementing advanced technologies to meet the needs of the public and private sectors will deliver a high level of service to usTLD
registrants and enable the introduction of enhanced services. We are confident that we can transition the administration of the usTLD with zero impact to the current users of the usTLD and begin to
enhance the services they currently receive. Widespread adoption and use within the new expanded space will be ensured by the execution of our comprehensive marketing program and through the
introduction of a competitive registrar model. NeuStar is committed to working collaboratively with the usTLD stakeholders to facilitate the development of policy that reflects the needs of the
community. NeuStar's registries are designed and administered to ensure all industry participants have equal access, its services are provided equitably to all service providers, and its corporate
focus is on the industry as a whole. This, in combination with its reputation for integrity, experience, neutrality, and industry expertise makes NeuStar the ideal vendor to administer the usTLD. 

        The
following table provides a detailed display of NeuStar's capabilities, as evidenced by our current projects and past performance. 

NeuStar's Capabilities and Qualifications  

	Vendor Qualification
 
	 	NeuStar's Experience

	Administration of complex, mission-critical U.S. public resources	 	•	 	NeuStar established processes working with the FCC and state commissions for reclamation of central office codes that have not been activated by service providers.
	

 	
 	

•	
 	

NeuStar developed databases for the tracking of central office code activity for the U.S.
	

 	
 	

•	
 	

In conjunction with the industry and FCC, NeuStar developed a new method for reporting utilization and forecasting of numbering resources (NRUF)
	

Successfully transitioning administration of mission-critical public resources	
 	

•	
 	

Transitioned Telephone number administration from 10 companies with more than 100 local administrators across all 50 states to one central administrator
	

 	
 	

•	
 	

Transitioned telephone number inventory from more than 200 local databases to one central database
	

 	
 	

•	
 	

Have been contracted to transition telephone number inventory from thousands of local databases across all 50 states to one local database
	

Proven neutrality in all business operations	
 	

•	
 	

In CC Docket No. 92-237, FCC 99-346, NeuStar was found to be in compliance with the neutrality requirements put forth in the NANP Administration Third Report and Order.
	 	 	 	 	 

101

 

	

 	
 	

•	
 	

NeuStar undergoes a quarterly Neutrality audit performed by Ernst and Young, with a report forwarded to the FCC, NANC, and NAPM LLC. This report covers the findings of the audit regarding compliance with the NeuStar Code of Conduct and Neutrality
Compliance Procedures. NeuStar asserts that it is neutral, and Ernst and Young has agreed in all audit reports.
	

Facilitation of controlled, systematic evolution, enhancement, and expansion of the space.	
 	

•	
 	

NeuStar performs the change management administration function for the NPAC SMS on behalf of the telecommunications industry. This includes over 200 change orders resulting in 7 major software releases in 4 years.
	

 	
 	

•	
 	

NeuStar hosts quarterly NPAC operations forums, known as NPAC Cross regional meetings, where issues pertinent to the operation of the NPAC and its downstream systems are discussed and resolved.
	

 	
 	

•	
 	

NeuStar facilitated the transition of state number pooling trials to a national database focusing on a systematic evolution allowing for growth and future enhancements.
	

 	
 	

•	
 	

NeuStar works closely with industry and the FCC to develop enhancements to the existing NANPA process, including expansion of current functions.
	

Experience designing, building, and supporting robust databases	
 	

•	
 	

NeuStar designed, built, and expanded the NPAC database from inception to its current support of 17 million ported telephone numbers in the database. The growth rate of the database is currently increasing, having surpassed 1 million additional
records per month earlier this year.
	

 	
 	

•	
 	

NeuStar designed and built the pooling administration system to leverage the existing portability infrastructure. An existing NPAC database was adapted and scaled to support number pooling.
	

 	
 	

•	
 	

NeuStar developed various NANPA-related databases to enhance functionality and streamline work efforts associated with number administration. This allows for real-time tracking of number assignment, utilization, and forecasting data.
	 	 	 	 	 

102

 

	

 	
 	

•	
 	

Leveraging its experience with high-availability, mission critical system in the telecommunications industry, NeuStar is developing the next generation DNS architecture for the.biz registry.
	

Experience that ensures real-time access to multiple users with a minimum of system outages and downtime	
 	

•	
 	

NPAC offers a Low Tech Interface (LTI) dialup access. This capability currently supports over 700 clients, allowing for simultaneous access by over 200 users. This access method is also fully scalable.
	

 	
 	

•	
 	

While fully scalable, the NPAC currently supports over 500 dedicated accesses by various service providers.
	

Manage a high availability system to contractual service levels	
 	

•	
 	

The NPAC SMS has 29 contractual service level requirements, developed jointly with the industry, which are reported on monthly.
	

 	
 	

•	
 	

The.biz registry has SLAs with several major Channel Partners covering limited system downtime and system performance measures.
	

Comprehensive understanding of the usTLD's evolution	
 	

•	
 	

NeuStar has monitored proceedings on the usTLD and associated DOC activities.
	

 	
 	

•	
 	

NeuStar has subject matter experts on staff who were involved with the original development of the usTLD.
	

 	
 	

•	
 	

NeuStar is an active participant in various Internet-related forums such as the IETF and ICANN
	

Strong working relationships with stakeholders	
 	

•	
 	

NeuStar holds quarterly cross-regional meetings with LNPA stakeholders.
	

 	
 	

•	
 	

NeuStar holds weekly conference calls with LNP LLCs, the NPAC contracting parties, in addition to holding monthly face-to-face meetings to discuss operational issues.
	

 	
 	

•	
 	

NeuStar actively participates in various industry forums, including LNPA WG, NOWG, IETF, ICANN, and ITU.
	

 	
 	

•	
 	

NeuStar provides assistance to both the telecommunications industry and regulators in an effort to resolve difficulties in the area of number assignment, reporting, etc.
	

Facilitation of progress in a political and competitive environment	
 	

•	
 	

NeuStar acted as interim pooling administrator in several states prior to being selected as National Pooling Administrator.
	 	 	 	 	 

103

 

	

 	
 	

•	
 	

NeuStar facilitates NPA relief planning meetings, resulting in a relief plan which meets the needs of the industry and the regulators.
	

 	
 	

•	
 	

NeuStar provided objective information and assistance to the LNPA WG in an effort to resolve issues facing the entire telecommunications industry.
	

Ability to address long-term management issues	
 	

•	
 	

Developed Number Resource Utilization Forecasting tool, ensuring that appropriate detailed carrier information is collected, stored, analyzed, and properly distributed to appropriate regulatory authorities
	

 	
 	

•	
 	

Work closely with INC, NANC, and LNPA WGs to ensure that long term Number Resource Optimization needs are and will continue to be achieved
	

 	
 	

•	
 	

Developed long term strategic view of the needs of telecommunication service providers and regulators
	

Experience in building scalable databases that ensure security of personal data	
 	

•	
 	

NeuStar developed, deployed, and supports the Customer Account Management Exchange database, which contains highly proprietary service provider information.
	

 	
 	

•	
 	

NeuStar developed, deployed, and maintains the Number Portability Administration Center, which contains routing information for all calls placed in the US and Canada.
	

 	
 	

•	
 	

NeuStar maintains physical biometric facility security, with fulltime monitoring, strong physical security, and token authentication for dial-up access.
	

Ability to understand, develop, and manage all associated policy issues	
 	

•	
 	

NeuStar has an in-depth understanding all federal and state policy issues regarding number administration, in addition to meeting requirements developed by the industry which are seen to be the guidelines under which NANPA operates
	

 	
 	

•	
 	

NeuStar's experience in the policy rich telecommunications regulatory environment provides it with significant insight into the proper means for policy identification and coordination for the Internet.
	 	 	 	 	 

104

 

	

 	
 	

•	
 	

NeuStar is active in ICANN, the IETF and other Internet-related policy and standards bodies. NeuStar has a staff of experts on Internet policy and technical matters. NeuStar policy and legal experts participate heavily in ICANN constituencies'
activities.
	

 	
 	

•	
 	

NeuStar has an in-depth understanding of federal and state regulatory processes that are likely to be of prominent importance to Internet policy in the future.
	

Support and drive important technology standards	
 	

•	
 	

NeuStar is an active participant at the IETF where important internet technology protocols are developed. We are currently co-chairs of two IETF WGs including the Whois WG.
	

 	
 	

•	
 	

NeuStar has authored important IETF draft standards documents including one for a registry-registrar protocol.
	

 	
 	

•	
 	

NeuStar developed and patented the call processing technology used to enable telephone number portability. We patented the technology and made it freely available.
	

Proven reputation for fair, impartial policy management	
 	

•	
 	

NeuStar has extended its LNPA contract for an additional 3 years over its existing 5-year contract without going through the competitive bid process, with approval by the FCC.
	

 	
 	

•	
 	

NeuStar was selected by various service providers to provide Customer Account Record Exchange service via an in-house-developed database system.
	

 	
 	

•	
 	

Through its audit activities regarding NeuStar, Ernst & Young has consistently reported positive compliance to the Code of Conduct and Neutrality Compliance Procedures as approved by the FCC.
	

Strong financial performance and stability	
 	

•	
 	

NeuStar's existing lines of business are net income and cash flow positive
	

 	
 	

•	
 	

NeuStar's recent round of equity financing fully funded our business plan; if additional capital is required, our investment partner, Warburg Pincus, stands prepared to fund all NeuStar initiatives.
	

 	
 	

•	
 	

[***].

105

   A.    usTLD Team  

        NeuStar's cross-functional team organization, combined with its strong corporate focus and oversight, ensures the successful achievement
of the DOC's objectives for managing and enhancing the usTLD.

HIGHLIGHTS  

	•
	Cross-functional team organization maximizes resources and provides economies of scale to ensure best value

	•
	Dedicated team composed of subject matter experts ensures successful implementation and ongoing operation of the usTLD

	•
	Executive oversight provides resources and direction to ensure usTLD objectives are met

        NeuStar
is organized around a principle of leveraging a centralized group of functional organizations that support market-specific business initiatives. The line of business (LOB) teams
are staffed with subject matter experts from specific markets that provide requisite knowledge to meet their LOB constituency's needs and have responsibility for business development, marketing and
sales, and service delivery. By contrast, the corporate support organization is composed of information technology, operations, corporate development, administration, legal, external affairs
(including media relations), finance, and neutrality functions. These functional teams are staffed with highly qualified and experienced staff who are tasked with administering various facets of our
services. The Executive Oversight Committee provides direction and management to both the functional organization and the
LOBs. Because the organizational structure is broad, this group is readily accessible to all teams for guidance and approval. The cohesive nature of the organization optimizes communication and
fosters a collaborative work environment, whereby all of NeuStar's customer's benefit from a shared knowledge base. Additionally, this organization can quickly respond to change and reevaluate and
deploy resources for critical operation. 

        For
the usTLD Administration Program, NeuStar is proposing a dedicated cross-functional team reporting to the usTLD Director who will report to our Vice President of Internet Protocol
(IP) Services. The usTLD management positions will be staffed with individuals who possess many years of relevant management and technical experience. These positions will be supplemented with
personnel from our Corporate Support Team and our Technology and Operations division who will be dedicated to ensuring the success of the usTLD. The management staff will be supported by our corporate
executives, who also have a strong commitment to the success of the usTLD program and will provide the requisite oversight and resources to ensure the usTLD program objectives are met. 

usTLD Team  

        NeuStar's usTLD team will consist of an Executive Oversight Committee and an Implementation and Ongoing Operations Team. These teams are described below. 

Executive Oversight  

        Our executive oversight committee, shown in Exhibit A-1 and introduced below, is composed of senior-level staff with vast experience covering
Internet expertise, operations, systems development and deployment, financial planning, communications, and resource management. This group will provide the requisite direction and resources to ensure
that the usTLD program objectives are met. 

[Exhibit A-1:
Graphic Design] 

A-1

 

Jeffrey Ganek, President and Chief Executive Officer  

        Jeffrey Ganek is responsible for overall management of NeuStar, Inc. Jeff has nearly 25 years of experience in the telecommunications industry.
Before heading the Communication Industry Services division within Lockheed Martin IMS, Jeff served as Vice President of Asian Operations for Global TeleSystems Group, where he developed and managed
competitive telecommunications services com-panies in fast-growing Asian markets. He was also Vice President of Marketing at GTE Spacenet, Director of Global Communications
Services at MCI, and Division Manager of Corporate Development at AT&T. He holds bachelor's and master's degrees from Carnegie Mellon University in Pittsburgh. 

Matthew D. Wald, Vice President, IP Services  

        Matthew D. Wald is responsible for the commercial development and management of NeuStar's emerging IP business. He has more than 12 years of experience in
the telecommunications industry, including identifying, developing, and operationalizing new business opportunities in advanced intelligent networking, IP, and Web hosting. He has held positions with
LCI/Qwest Communications and Global TeleSystems Group. Most recently, as the leader of the Global Alliance and Partnership Group at GTS, he oversaw the development of several key Web hosting, Voice
over IP (VoIP), and content delivery partnerships that formed the cornerstone of the GTS IP business strategy. 

Mark D. Foster, Chief Technology Officer  

        Mark Foster is responsible for strategic technology initiatives, standards, and program management, and the design, development, and operation of NeuStar's
complex network and systems infrastructure. A widely recognized subject matter expert, Mr. Foster pioneered number portability in the industry in 1994-1995 and subsequently led the
development of NeuStar's Number Portability Administration Center in 1996. He has more than 20 years of entrepreneurial experience in developing innovative solutions to industry problems with
inventions such as a voice-controlled intelligent network service node platform, a new computer language for developing telephone switching systems software, and the first
SS7-to-IP signaling gateway (1990). 

Joseph F. Franlin, Senior Vice President of Operations  

        Joseph Franlin is responsible for NeuStar operations and customer satisfaction for clearinghouse and numbering products and services. Joseph's organization
managed the successful introduction of Local
Number Portability in the United States and Canada and assumed the role of North American Numbering Plan Administrator in the United States, Canada, and many of the Caribbean Islands. Joseph has more
than 30 years of experience in telecommunications and systems engineering, most notably with NYNEX, AT&T, and Lockheed Martin. 

Robert Dowski, Chief Financial Officer  

        Robert Dowski joined NeuStar in 2000, assuming the role of Chief Financial Officer. Prior to joining NeuStar, he held similar positions with Gilat/GE Spacenet,
PCS, Telecorp, and Hughes Network Systems. He has worked in the telecommunications and Information Technology industry sectors for more than 10 years, concentrating on managing large,
full-scale accounting, financial planning, and strategic planning departments. In addition, he has managed the development of a series of financial systems. 

Edward Frietag, General Counsel  

        Edward Freitag, General Counsel, is responsible for oversight of legal matters for NeuStar. Prior to joining NeuStar, he was with MCI Communications Corporation
and MCI WorldCom from 1975 to 1999, last serving as Chief Corporate Counsel. During his career at MCI, he was responsible for 

A-2

 

supporting
mergers and acquisitions, financing, SEC reporting, international ventures, and other corporate matters. Prior to joining MCI, he was an associate with Donovan, Leisure, Newton &
Irvine and Pro Se Law Clerk for the United States Court of Appeals for the Second Circuit. He also has served as Chairman of the Corporate and Securities Law Section of the American Corporate Counsel
Association. Mr. Freitag is a graduate of Princeton University and the Columbia University School of Law. 

Jerry Kovach, Senior Vice President, External Affairs  

        Jerry Kovach is responsible for the corporate communications, government relations, regulatory law, public policy, and public relations activities of NeuStar.
Prior to joining NeuStar, Mr. Kovach was a Senior Vice President at MCI Communications Corporation from 1985 to 2000. From 1975 to 1984, he was on the staff of the United States Senate, last
serving as the Chief Counsel and Chief of Staff of the Committee on Commerce, Science, and Transportation. Mr. Kovach's professional background also includes senior management positions with
Chrysler Corporation and the National Academy of
Sciences. Mr. Kovach is a member of Phi Beta Kappa and holds a bachelor of arts degree (cum laude) in economics from Wayne State University, a doctor of law degree (cum laude) from Wayne State
University Law School, and a master of law degree from the University of Washington School of Law. 

Robert Poulin, Vice President, Corporate Development  

        Robert R. Poulin is responsible for early-stage development of new business initiatives as well as alliance and acquisition opportunities. He actively pursues
opportunities where NeuStar's proven capabilities as a trusted provider of registry and clearinghouse services can facilitate the interoperability of networks. He has 12 years of experience in
the communications industry. Prior to joining NeuStar, he was Director of Business Development at Global TeleSystems Group, where he was responsible for early-stage development of new ventures in
Asia. He also has held a variety of business development and finance positions with GTE Spacenet, GTE Mobilnet, and GTE Telephone Operations. He has a bachelor's degree from the Haas School of
Business at the University of California at Berkeley. 

Jerome Haynesworth, Vice President of Human Resources and Administration  

        Jerome Haynesworth is responsible for organizational development, compensation planning, facilities management, human resources development, employee relations,
and equal employment programs. Jerome manages the human resources function for the technical and nontechnical components of NeuStar, with more than 400 employees internationally. He has more than
20 years of experience in managing human resources and administration, including positions with KPMG, Hughes Aircraft Company, The Interface Group/Mass., and IBM. 

David H. Crocker, Senior Advisor, Consultant  

        David H. Crocker has been a principal with Brandenburg InternetWorking since 1991. He has been developing internetworking technologies for 30 years,
including standards for e-mail, EDI, facsimile, security, and e-commerce. He was an IETF Area Director for four years, providing oversight of DNS technical development, and he
initiated public interest enhancement to BIND, the DNS reference software. During the 1980s, Mr. Crocker led TCP/IP, OSI, and network management product development efforts.
Mr. Crocker's current efforts focus on the creation of Internet-based businesses built on a solid foundation of customer benefit and revenue potential. 

William Manning, Senior Advisor, Consultant  

        Bill Manning is a contributing scientist on CenterGate's UltraDNS and serves on the research staff at USC's Information Sciences Institute. At Texas Instruments,
Bill was responsible for the deployment 

A-3

 

of
IP networking, initially in the semiconductor division, and then throughout the corporation. He joined Rice University to become the lead engineer for the NSFnet's SESQUINET regional network.
Following the successful migration of SESQUINET and MIDnet from the NSFnet to commercial networks, Bill assumed a role in the NSF's Routing Arbiter project at NSI. Bill is active in the IETF and has
been active in the DNS and Routing working groups as a participant, working group chair, and code developer. He was responsible for specifying the method for adding NSAP support to the DNS, and then
he developed and implemented a plan to expand the Internet root server system to add four new nodes. Bill is also on the program committees for the North American Network Operators Group (NANOG), the
Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT), and the African Network Operators Group (AFNOG). He is also a member of the Advisory Council of ARIN (American Registry
for Internet Numbers). Bill continues to work on enhancing DNS code to track the growth of IP networks and is currently working with the IPv6 developers and implementers by managing the IP6.INT
domain, which is the functional equivalent of the in-addr.arpa zone. 

Implementation and Ongoing Operations Team  

        NeuStar's experience in forming successful implementation teams for such services as NPAC and NANPA will be used in staffing the usTLD operation. Leveraging these
skills ensures that the usTLD will be implemented on time and that effective ongoing operations will be established. The usTLD team will include the use of experienced, highly qualified, proven
individuals skilled in registry operation, database development and administration, data center operation, and transition and customer service. The usTLD team members were individually selected for
their respective expertise and in-depth knowledge of technical, policy, and operational requirements. Collectively, their unique qualifications and experience, when dedicated to the
coordination, expansion, and enhancement of the usTLD, will ensure success. 

        As
can be seen in Exhibits A-2 and A-3, NeuStar is proposing two functional organizations—an implementation team and an ongoing operations team.
NeuStar is committed to the delivery of high levels of quality service; therefore, most key team members participating in the implementation phase will eventually transition from the implementation
team to full-time, ongoing usTLD operations support. However, this separation provides a distinct focus on the critical implementation phase. Our experience has proven that transitioning
individuals participating in the implementation of an operation ensures an effective ongoing operation.
As required, résumés for key team members (arranged in alphabetical order) can be found at the end of this section. 

[Exhibit A-2:
Graphic Design] 

[Exhibit A-3
Graphic Design] 

A-4

 

        The
following table contains the job titles, descriptions, and skills of key NeuStar usTLD team members. 

usTLD Organization Roles and Responsibilities/Skills Matrix  

	Title
 
	 	Job Description
	 	Skills

	

Director, usTLD	

 	

Responsible for defining the usTLD product and business requirements. Has ultimate responsibility for day-to-day management of operations to support the usTLD project and will serve as the primary point of contact (POC) to the industry. Will ensure
that the necessary resources are made available to address any deviation from expectations and will be the primary decision-maker on program-related issues. Will report status to the Contracting Officer at the DOC and to NeuStar Senior
Management.	

 	

•    Extensive industry experience

•    Excellent verbal and written communications skills

•    Excellent organizational and time management skills

•    Problem resolution skills

•    Excellent facilitation skills

•    Strong decision-making skills
	

Program Manager	

 	

Has overall responsibility for the successful completion of implementation, development, deployment, and upgrade of the usTLD service. Will provide overall leadership for the entire implementation team; determine project scope; develop the project
plan, milestones, and risk mitigation plan; and act as the front-line contact with the client representatives on project-related issues.	

 	

•    Excellent customer service, decision-making, and communications skills

•    Detail-oriented, creative, and analytical

•    Industry experience

•    Experience with managing large, complex, multi-phase technical projects

•    Strong leadership skills
	 	 	 	 	 

A-5

 

	

Director, Systems Engineering	
 	

Will be responsible for overall system delivery and will manage the design and development processes of all usTLD systems.	
 	

•    Well-developed and highly effective verbal and written communications skills

•    Demonstrated ability to manage the design and development of complex applications using development standards

•    Expertise in one or more technical areas as well as experience in relational database development and design
	

Director, Information Technology and Services	

 	

Manages the technical operations group and the network support group in a 24x7 real-time mission-critical production environment. Supports, monitors, tests, and troubleshoots hardware and software problems; recommends and schedules repairs; and
provides Tier 2 support for all LAN/WAN-based applications. Maintains security and disaster recovery procedures and participates in database architecture strategy development, database design and engineering, and reliability and performance
enhancement.	

 	

•    Experience in LAN operating systems

•    Extensive knowledge of LAN infrastructure setups, including hubs, routers, and firewalls

•    Strong written and communications skills

•    Strong analytical and problem-solving skills

•    Familiar with standard concepts, practices, and procedures within particular field
	

Senior Manager, Channel Management	

 	

Is responsible for the registrar, delegee, and resellers outreach programs. This person and his or her team are responsible for channel communications for the usTLD product.	

 	

•    Experience with various Industry forums

•    Excellent verbal and written communications skills

•    Excellent organizational and time management skills

•    Problem resolution skills

•    Excellent facilitation skills

•    Ability to run efficient meetings

•    Supervisory skills
	 	 	 	 	 

A-6

 

	

Senior Manager, Product Marketing	

 	

Is responsible for the definition of enhanced services for the usTLD locality-based and expanded products. Will create marketing materials and review any training materials or other documentation about the product. Is responsible for public relations,
 branding, advertising, and Web content look and feel and will also attend industry forums.	

 	

•    Extensive Industry experience

•    Excellent verbal and written communications skills

•    Excellent organizational and time management skills

•    Problem resolution skills

•    Excellent facilitation skills
	

Senior Manager, Customer Service	

 	

Is responsible for all day-to-day usTLD service operations. Hires and supervises the Help Desk, Quality Assurance group, and the Training and Documentation group. Ensures that the staff have the adequate tools and facilities to properly perform their
functions and develops and implements escalation procedures.	

 	

•    Extensive Industry experience

•    Extensive data center operations experience

•    Excellent verbal and written communications skills

•    Excellent organizational and time management skills

•    Problem resolution skills

•    Excellent facilitation skills
	

Quality Assurance Group	

 	

Evaluates our conformance to the standards mandated by industry guidelines. Performs operational and business audit reviews, evaluates results, and makes recommendations for the improvement of internal operational and management control systems and
performance. Will send out surveys to the usTLD user base, soliciting comments about our service and incorporating their suggestions for improving the process.	

 	

•    Internal business auditing or related experience

•    Experience with commonly used auditing concepts and practices

•    Strong analytical and problem-solving skills

•    Strong written and verbal communications skills
	 	 	 	 	 

A-7

 

	

Help Desk Group	

 	

Plays a critical role in the implementation of usTLD, working closely with the industry to establish policies, procedures, and processes that facilitate usTLD operations. Ongoing activities will include resolution of all user problems and inquiries
associated with usTLD.	

 	

•    Excellent customer service, decision-making, and communications skills

•    Detail-oriented, creative, and analytical

•    Industry experience

•    Experience with troubleshooting computer hardware and software
	

Transition Team	

 	

Is responsible for managing the transition from the current administrator to NeuStar, which includes working closely with the delegees to understand and improve the existing locality-based space.	

 	

•    Excellent customer service, decision-making, and communications skills

•    Detail-oriented, creative, and analytical

•    Industry experience

•    Strong written and verbal communications skills.
	

Technical Industry Liaison	

 	

Is NeuStar's technical representative with the ICANN, IETF, and other industry standards bodies. Is responsible for ensuring that NeuStar is compliant with all industry standards and provides technical direction to the Systems Engineering
organization.	

 	

•    Well-developed and highly effective spoken and written communications skills

•    Understands the usTLD space, both technically and operationally

•    Expertise in ccTLD technology and standards.

•    Detail-oriented, creative, and analytical

•    Registry administration experience.
	

HR/Administration	

 	

Responsible for Human Resources including recruiting and hiring staff. Responsible for facilities management. Responsible for ensuring program is meeting financial budget, defining AP, AR, and credit processes. Also is responsible for neutrality
supervision and for ensuring that all program activities meet neutrality requirements.	

 	

•    Excellent customer service, decision-making, and communications skills

•    Detail-oriented, creative, and analytical

•    Industry experience

•    Strong written and verbal communications skills.
	 	 	 	 	 

A-8

 

	

Legal, Policy, and ICANN Relations	

 	

Responsible for usTLD contract negotiation and management. Also responsible for registrar, delegated manager, and delegee contracts. Responsible for US Nexus requirements, locality-based usTLD policy enforcement, domain name dispute resolution
procedure/policy, Sunrise and Land Rush Policy, ICANN Policy, Government Advisory Committee Principles, Registrar Agreement Development, and Policy compliance audit.	

 	

•    Extensive experience in ccTLD and ICANN policy

•    Excellent negotiation skills

•    Excellent contract management skills

•    Excellent decision-making and communication skills.
	

Billing and Collections	
 	

Responsible for defining Billing and Collections interface requirements, invoice design and development, methods and procedures, and credit card processing.	
 	

•    Extensive experience in registry billing and collections

•    Excellent customer service skills

•    Excellent decision-making and communications skills

Staffing Approach  

        NeuStar's philosophy is that the company achieves its business goals through its people. We promote the philosophy among our employees that they are individually
and collectively critical to the company's success and share in its rewards. A sense of ownership is encouraged among
employees—ownership of their own work as well as responsibility for the overall performance of the company. NeuStar consistently maximizes its business goals by hiring staff who are highly
productive and of high caliber, ensuring the highest levels of service. 

        Staffing
allocations may need to be adjusted as demand for service increases. Adjustments may include the staff size or refinements to required technical skills. The mechanisms for such
reviews and procedures will be consistent with NeuStar's policies. In addition, NeuStar can and will draw upon a reserve of managerial and technical skills within the corporation. Cross training is
used in all positions to promote job interest and esprit de corps. 

        [***]

        [33
pages] 

A-9

 

B.    Contractor Requirements  

        NeuStar will execute our vision for the usTLD by significantly increasing and maintaining the utility and integrity of the space. We will
meet the objectives laid out in the Statement of Purpose through implementing our service and policy administration throughout the usTLD namespace.

HIGHLIGHTS  

	•
	NeuStar addresses the needs of every customer of the usTLD registry.

	•
	Our role as the successful administrator of U.S.-based, mission-critical public resources affords us a unique understanding of the needs that such an
administrator must fill.

        The
usTLD administrator must be more than just a registry operator. Because of the complexity of the usTLD space, its administrator must act as a registry, a registrar for undelegated
third-level localities, and a service and policy administrator. To perform all of these functions, there must also be an understanding of the many kinds of customers being served. To successfully
administrate the usTLD registry, there must be a demonstrated understanding of the needs of registrars, registrants, and delegated managers, including both delegees and subdelegees in the locality
space, as well as of the stated needs of the DOC. The policy and service solutions described in this section were developed with these needs in mind. 

        The
DOC has established a clear need for the provisioning of high-quality core functions and locality-based and expanded functions, as well as the implementation of and
adherence to usTLD policies. Our provisioning of these services works to meet the objectives laid out in Sections B.1 through B.5 of the RFQ. 

        In
accordance with RFQ requirements, NeuStar will perform the functions of usTLD administrator as a prime contractor, incorporated within the state of Delaware. NeuStar's corporate
offices are in Washington, D.C., and all of our usTLD registry servers will be located within the United States. NeuStar will not charge the U.S. Government for performance of these functions. 

        Executing
our vision through serving as the usTLD administrator, we will offer the best value for the most accurate, up-to-date, and available registry services. 

        Our
policy and service solutions are highlighted below and in Sections B.1 through B.5 of this proposal. 

        Statement of Purpose—NeuStar's solution will support competition and promote use of the usTLD, by encouraging communication,
ensuring equitable application of policies and procedures, and cultivating an environment conducive to innovation. We will ensure the stability of the DNS and inspire consumer confidence with a
secure, robust, and reliable technical infrastructure. 

        Core Registry Functions—NeuStar will provide a comprehensive suite of core registry functions that take into account the needs
of all of our customers—delegated managers, registrars, and registrants. We will leverage our Centralized usTLD Database and Enhanced SRS, and implement automated registration processes,
updates, and zone file generation, to provide accurate, up-to-date information on demand. 

        Core Policy Requirements—NeuStar's policies and processes will be designed for collaborative partnerships between the usTLD
administrator and the usTLD community. As the trustee of a valuable public resource, we will develop our policies to ensure that our operations serve the public interest. 

        Locality-Based usTLD Structure Functions—NeuStar will modernize the usTLD locality space by working with delegated managers to
centralize all data currently managed by locality delegees and subdelegees. Our collaborative approach to modernizing this space will ensure that the needs of both delegated managers and registrants
are met. 

B-1

 

        Expanded usTLD Space Functions—NeuStar's expanded usTLD registry will promote registrar competition and encourage
registrations in the usTLD namespace. We will work closely with registrars in both our accreditation and certification processes. 

        NeuStar's
role in communications industries, part of our very identity, has been as an administrator of U.S.-based, mission-critical public resources. We understand the difference
between acting simply as a registry operator and acting as an administrator. Our goal is to serve every customer—registrars, delegated managers, registrants, and the DOC
itself—to provide to those customers with the best value, highest quality registry possible. 

B-2

   B.1    Statement of Purpose  

        NeuStar's solution for managing the usTLD namespace amply meets the objectives defined by the DOC and will both enhance its utility and
drive its widespread adoption.

HIGHLIGHTS  

	•
	NeuStar's administration will encourage communication, ensure equitable application of policies and procedures, and cultivate an environment
conducive to innovation

	•
	Our technical infrastructure will provide a secure, robust, reliable system that will ensure the stability of the DNS and inspire consumer
confidence

	•
	NeuStar's solution will encourage robust competition and promote the use of the usTLD

        The
usTLD was created to provide a locus for registration of domain names to serve the Internet community of the United States, and is available to a wide range of registrants. However,
it has not attracted high levels of registration and utilization when compared with other ccTLDs in part because of its hierarchical nature. Because the usTLD has been underutilized and
underdeveloped, the DOC now seeks proposals to centralize management and coordination of the existing usTLD space while expanding and enhancing it to encourage use and innovation. NeuStar's solution,
discussed below and in the subsections to follow, has been carefully designed to meet all the DOC's objectives for the space. 

NeuStar will develop a more robust, certain, and reliable system as a framework of accountability for the delegation and the administration of the usTLD.  

        NeuStar believes that the importance of expanding the scope and quality of core registry functions for the usTLD cannot be stressed enough and that the expanded
usTLD services should follow, in large part, the registry/registrar model that has become commonplace in the industry. Not only will this approach allow the development of a feature rich domain space,
it also will establish a level of consumer familiarity that will help ensure a successful roll-out of an enhanced usTLD. Therefore, the administrator must develop a robust shared registry
system (SRS) comparable to those being built for the new generic TLDs that have been established by ICANN. 

        The
development of a secure, functional and robust SRS is not a trivial task. In developing such an SRS, NeuStar believes that a number of key elements must be implemented to handle
delegation based TLD registration. In particular, Whois functionality should be centralized in the registry operator following the "thick registry" model. A "thick registry" centralizes registration
data with the TLD registry, rather than placing most of the storage burden on each registrar (or delegee). This centralization increases security, functionality, and stability. NeuStar submits that
existing usTLD delegation operators should be required to transition to a "thick registry" model. Other important aspects of a robust, trusted infrastructure will include: 

	•
	Geographically
diverse, redundant data centers with a high level of physical security and appropriate environmental conditions

	•
	Equal
network access for registrars

	•
	Open
source advanced system interface for registrars

	•
	Enhanced
security for the registrars and the information that is transmitted to the provider

	•
	Enhanced
privacy protections for registrant data

	•
	Enhanced
functionality for both delegations and direct registrations 

        For
example, currently the usTLD does not provide a comprehensive Whois service. This has a serious, negative impact on resolving some network operations problems. NeuStar will address
this and 

B.1-1

 

other
issues in the required compliance report on the usTLD space and will implement such a service with enhanced privacy protections. 

        Please
see Proposal Sections B.3, Core Policy Requirements and O, Proposed Technical Plan, for more detailed information. 

NeuStar will promote increased use of the usTLD by the Internet community of the United States by:  

	•
	Creating
a stable, flexible, and balanced environment within the usTLD that is conducive to innovation and will meet the future demands of potential registrants.

	•
	Promoting
robust competition within the usTLD, and in particular, registration services that will lead to greater choice, new, and better services for users. 

        NeuStar's
mission is to enhance the operation and utilization of the usTLD by bringing to bear the strengths and innovation of the next generation registry systems currently being
deployed in the generic TLD space. As the usTLD Administrator, NeuStar will work with the Internet Community, the DOC, and ICANN to expand significantly the use and value of the current usTLD space by
permitting direct registration of non-hierarchical names while centralizing and coordinating the management of the current usTLD delegations. This community-based, expanded approach will
allow NeuStar to develop effective policies and procedures to ensure that current uses of the usTLD not only are protected and enhanced but also that this important public resource is managed in a
manner designed to serve the public interest. To accomplish this goal, NeuStar proposes to analyze concerns
with existing usTLD delegations as contemplated by the RFQ. NeuStar will then develop policies and procedures to ensure maximum utility of the existing delegations and registrations. 

        The
complexity of the usTLD hierarchical namespace may discourage some Internet users from registering a name under the TLD. NeuStar, therefore, supports the expansion of the usTLD to
allow direct second-level registrations and potentially new, concept-based hierarchies targeted to specific communities or for specific purposes. Moreover, NeuStar believes that by developing
additional services to enhance the utility of the usTLD for its registrants, the usTLD's popularity and utility can be made to rival the existing generic TLDs. 

        In
developing services, NeuStar's approach will be to work collaboratively with registrars and end users. Registrars and domain name registrants be encouraged to provide constant
feedback and will have access to discussion lists and feedback forms. This feedback will be compiled and carefully considered in determining the ongoing development of the registry's systems,
procedures, and services. 

        By
improving the level of service and degree of coordination of the existing delegated space, NeuStar believes that there will be increased use of that space. For many functions, there
is an inherent value in the kind of geographic categorization developed in RFC 1480. Administered properly, the delegated space in the usTLD could become as valuable and highly used as the expanded
space is assumed to be. 

        Please
see Proposal Section B.4, Locality-Based usTLD Structure Functions; Section D, Enhanced Services; and Section L, Funding for usTLD for more detailed
information. 

NeuStar will create a centrally administered and efficiently managed structure that ensures registrant/consumer confidence as well as infrastructure stability.  

        NeuStar expects to tighten significantly the operation of the delegated usTLD space. It will achieve this as discussed above, by centralizing administration and
operation of the usTLD, except where decentralization is required. For all delegees there will be operational and technical standards. The centralized service will be offered for those delegees
primarily interested in addressing the "policy" function of the delegation. In addition, the usTLD will follow the "thick registry" model for the 

B.1-2

 

enhanced
space, whereby primary registrant data are kept with the registry, rather than the registrar. These measures will increase dramatically the usTLD Administrator's ability to ensure that the
promise of the usTLD is realized. 

        Please
see Proposal Sections B.2, Core Registry Functions and F, usTLD Centralized Database and Enhanced SRS, for more detailed information. 

NeuStar's solution will ensure continued stability of the usTLD and of the domain name system as a whole.  

        Citizens, businesses, consumers, and even governments depend on the Internet for communication and commerce. Key to this dependence is the domain name system
(DNS). The Internet community simply cannot afford a DNS that shows any type of unreliability. An unstable DNS has disastrous effects. It prevents communication among many thousands of organizations,
hinders trade between businesses and customers, and prohibits individuals from communicating with each other or contacting their government. NeuStar is acutely aware of the immense responsibility
attached to the administration of such a significant public resource and will undertake all measures required to ensure its success, reliability, and security. NeuStar will utilize existing DNS
infrastructure developed for the dot-biz TLD to ensure the enhanced operation and stability of the usTLD. We will do so in several ways: 

        By providing a stable and secure zone file distribution network—NeuStar's usTLD registry will not impact operation of the
existing DNS root. Publication and distribution of usTLD zone files will be entirely compatible with existing DNS standards and procedures. Our zone file distribution network will operate in parallel
with the existing root server network and will employ accepted, modern, strong, encryption-based procedures. The root servers for the network will be protected by special software and hardware
mechanisms. NeuStar's system will be developed and tested to scale seamlessly into the future for TLD name service. 

        By preserving the unique global domain name system—The NeuStar design has been developed on the principle of maintaining
consistency and interoperability through existing standards such as RFC 1034, RFC 1123, RFC 1480, and their successors. In addition, NeuStar is committed to working closely with the Internet
Engineering Task Force (IETF) and other relevant organizations to ensure the stable evolution of the domain name service technologies. NeuStar is supportive of implementing policy restrictions where
necessary to protect important Internet and ICANN policies and, thus, is committed to the administration of the usTLD in a manner that preserves the current system's strengths and acknowledges it as a
critical public resource. 

        By acting in accordance with sound business practices and operational management—NeuStar is founded on principles of strong
management, a tight user-oriented focus, and a clear vision. Market analysis and an understanding of the usTLD community is at all times the driver for NeuStar solutions. The NeuStar
executive team brings an abundance of experience in designing, implementing, and maintaining technology-based services especially in an Internet environment. 

        The
NeuStar usTLD registry solution will provide exceptional services. We are acutely conscious that support for domain names extends far beyond the initial registration or delegation
for the entire life of the domain name. By providing effective, long term operational solutions, the domain space will thrive ensuring its own stability and encouraging the improvement of service
levels within existing domain spaces. 

        By providing dedicated and responsive channel management—The NeuStar usTLD registry will deliver its solutions in the enhanced
space via the registrar community. In this context, NeuStar understands the importance of providing an absolutely neutral third party registry service to facilitate the advancement of effective
relationships in an extremely competitive environment. In this way, customer needs will drive the registry. 

B.1-3

 

        By developing an enhanced, community-based mechanism for maintaining and developing the existing usTLD space—The existing
usTLD space has suffered from a lack of coordination and technical innovation since its inception. NeuStar will develop a strong community-based mechanism for managing existing delegations. Steps to
improve the space will include analysis of delegee compliance with usTLD policies, quality of service improvement, establishment of a comprehensive centralized Whois service, development of minimum
technical standards, and provision of outsourced technical services for delegees. These and other measures will ensure the continued viability and improvement of existing usTLD services. 

        Please
see Proposal Section A, usTLD Organiztion; Section B.2, Core Registry Functions; Section B.3, Core Policy Requirements; Section F, usTLD Centralized
Database and Enhanced SRS; and Section O, Proposed Technical Plan for more detailed information. 

NeuStar's management of the usTLD will be consistent with the Internet Corporation for Assigned Names and Number's (ICANN) technical management of the DNS.  

        Since the DOC, through the National Telecommunications and Information Administration (NTIA), issued the statement of policy on the management of Internet names
and addresses, the Internet community has expended significant effort in the development of policies and mechanisms for the governance of the Internet DNS, as well as enhancement of existing TLDs and
the introduction of new TLDs. These efforts have resulted in development of a workable shared registry model that encourages competition and Internet stability, as well as protects the rights of
individual Internet users. NeuStar has, where appropriate, modeled its solutions to be entirely consistent with ICANN policies and DNS management principles. 

        Please
see Proposal Sections F, usTLD Centralized Database and Enhanced SRS, and O, Proposed Technical Plan, for more detailed information. 

NeuStar will allow for the adequate protection of intellectual property in the usTLD.  

        NeuStar recognizes and supports the need for appropriate protection of intellectual property. NeuStar will implement a "sunrise" trademark program patterned after
the "daybreak" proposal of the ICANN Intellectual Property Constituency. This program will allow registered US trademark holders and applicants a priority opportunity to register their marks within
the usTLD. NeuStar also will implement appropriate dispute resolution mechanisms designed specifically for the usTLD but consistent and compatible with the ICANN Universal Dispute Resolution Policy
(UDRP). Finally, NeuStar will explore additional policy and mechanisms as needed to address all manners of intellectual property issues in the usTLD. 

        Please
see Proposal Sections B.3, Core Policy Requirements and I, Start-up Phase Policies, for more detailed information. 

NeuStar will establish and maintain consistent communication between the Contracting Officer's Technical Representative (COTR), the Contracting Officer, and ICANN.  

        As part of its role as a neutral provider of mission critical infrastructure and services for important public resources, NeuStar has a history of coordinating
and working with numerous agencies and industry participants in performing its functions. For example, as the NANPA, NeuStar works with the FCC, the North American Numbering Council, and industry
forums as well as with individual telecommunications carriers. NeuStar has been highly successful in these endeavors and will bring these same communications abilities to the management of the usTLD.
In particular, NeuStar will identify dedicated liaison officers with the organization to ensure consistent communication between it and the Contracting Officer, the COTR, and ICANN. Moreover, NeuStar
will develop outreach programs for 

B.1-4

 

the
usTLD community including registrants and delegees, to ensure that the developing TLD meets the needs of its users. 

        Please
see Proposal Sections B.2.7, Industry Representation/Compliance, and B.3.5, Additional, Alternative, or Supplemental Policies, for more detailed information. 

        NeuStar's
solutions will address each of the DOC concerns. Indeed, because NeuStar's experience in the provision of mission critical public interest functions to US industry is
unmatched, the proposed solution significantly exceeds these requirements and will result in a usTLD that will serve as the model for the ccTLD community. 

B.1-5

 

B.2    Core Registry Functions  

        NeuStar's proven experience in delivering high-quality public resource administration services will ensure that registrars,
delegated managers, and registrants receive a total service package delivered in a neutral, even-handed manner.

HIGHLIGHTS  

	•
	NeuStar's total service package will contribute our vision of turning the usTLD into the model of a country code top-level
domain.

	•
	Additional services are designed to serve all of the registry's customers, including registrars, delegated managers, and
registrants.

	•
	We will provide a comprehensive suite of Core Registry Functions, leveraging our Centralized usTLD Database and Enhanced SRS.

        Any
administrator of the usTLD must understand the complexity of functions and services that need to be offered. In addition to understanding the needs of registrars and their
registrants, this administrator must also appreciate the needs of delegated managers and registrants in the hierarchical locality space, whether they register through the registry or through a
delegated manager. The ability to administer a system with three distinct types of end-users, all with their own needs and issues, requires support services that can respond to all of
these needs. 

        As
depicted in Exhibit B.2-1, usTLD registry services, zone file generation, and Whois services are the central components of our registry service offering. These
components on their own make up a simple registry; however, there are equally important support functions that make up a truly successful usTLD registry. Our total service package, highlighted below
and in Sections B.2.1 through B.2.16, includes all of the requirements listed in RFQ Section B.2 as well as the additional services and functions that we believe are necessary to serve all of
our customers and to turn the usTLD registry into the model country-code top-level domain. As required, NeuStar will provide all systems, software, hardware, facilities,
infrastructure, and operations to support these functions. 

        usTLD Nameserver and usTLD Zone File Administration—NeuStar's usTLD architecture is designed to be flexible, scalable and
high-available to virtually eliminate downtime while providing for smooth growth. Redundant data centers in Virginia and Illinois ensure high service availability, while dynamic,
near-real-time transfers of zone file data provides up-to-date, authoritative responses from the usTLD nameserver constellation. 

        Whois Database Administration—NeuStar will centralize the usTLD Whois database in both the expanded
space and the locality space by developing and implementing two accurate and up-to-date, logical databases, one for registrants and registrars, and one for delegated managers.
NeuStar's Web-based and port 43 interfaces to this enhanced Whois database will allow multiple field and string searches, freely available to the public. 

        usTLD Delegated Manager Database Administration—NeuStar will reach out to all delegated managers in the locality space in
order to develop and implement a centralized database of delegated managers. This centralized information will serve registrants in the locality space while enabling us to contact those managers
quickly to resolve issues effectively. 

        [Exhibit B-2.1:
Graphic Design] 

        Data Escrow—NeuStar will arrange frequently for data escrow of the usTLD registry, to maintain continued operations and
availability in the unlikely case of a catastrophic loss of data. 

B.2-1

 

        Industry Representation/Compliance—NeuStar's involvement with Internet standards and policy organizations will contribute to
our operation of the usTLD as the model for a country code top-level domain. 

        Integration Assistance—NeuStar will implement an operational test-and-evaluation facility and provide
registrars with Registrar Tool Kit software in order to familiarize them with our thick registry and assist them in passing our technical certification process. 

        Compliance Monitoring—NeuStar will monitor delegated managers for technical compliance, not only as part of our initial
compliance investigation and report, but also throughout the life of their delegations. This will ensure that NeuStar's database remains up to date, that delegated managers remain compliant with usTLD
technical requirements, and that the usTLD retains a U.S. Nexus. This compliance monitoring will maintain the improved integrity of the usTLD. 

        Web Site—NeuStar will develop and implement a usTLD Web site for the Internet community as well as for private members,
including delegated managers and registrars. This Web site will provide access to registry functions, information to the Internet community, and the ability to register domain names in the undelegated
locality space. 

        Documentation and Training—At NeuStar, we believe that clear, concise documentation and training for our staff and our
customers is essential to provide the best service to those customers. NeuStar's external documentation, from our Programmer's Guide to our information on marketing the usTLD, are intended to give our
customers the highest level of comfort when working with the usTLD registry. 

        Customer Relationship Management—NeuStar's enterprise-wide CRM program assists with channel management and
outreach for the usTLD. We use CRM in combination with our extensive market and customer knowledge to ensure that we meet our commitment to timely, responsive, and high-quality customer
service. 

        Reporting—NeuStar's Web-based reporting system will have built-in functionality to provide reporting
information to registrars on all aspects of their interaction with the registry. 

        Progress and Quarterly Reporting—As required, NeuStar will submit progress reports to the DOC that
will indicate the status of all major events and all major work performed during the reporting period. 

        Help Desk—NeuStar will provide Help Desk services through our IP Customer Service Center, and will provide assistance to
registrars, delegated managers, and registrants in the undelegated locality space. 

        NeuStar's
experience in providing mission-critical services to the telecommunications industry has given us an understanding of what functions constitute the best service packages. The
functions and services outlined in this section represent what NeuStar has come to believe are essential for a total package solution, and our flexibility will allow us to incorporate additional
services as changes in the industry require them. A registry is more than servers and databases; it must serve its customers not just as a set of servers, but also as an administrator providing
services to support those customers. 

B.2.1    Primary usTLD Server  

        The essential core function of the usTLD Registry is providing authoritative name service for its domains.

        Failure
of a usTLD administrator to provide a reliable, secure, and robust nameserver function represents a fatal flaw in its system and ensures an unsuccessful administration of the
usTLD. NeuStar will implement a nameserver architecture that is highly superior to the traditional architecture that likely will be adopted by other bidders. 

B.2-2

 

        The
traditional implementation begins with one nameserver acting as the primary ("master") for zone data, which would then be transferred to secondary ("slave") servers. Located in
physically separate locations, these multiple authoritative servers provide robust and reliable responses to DNS queries. 

        The
primary nameserver holds the most current authoritative data for its zone. Secondary nameservers are also authoritative, but their data must be brought up to date by zone data
transfers from the primary nameserver. The same requirement for at least two authoritative servers, one primary nameserver along with one or more secondary nameservers, applies to all registrants
seeking to provide name service for their delegated domains. 

        NeuStar's
architecture and dynamic services exceed the capabilities of the traditional approach. Our proposed technical solution provides two co-active data centers in
Virginia and Illinois plus one nameserver data center in California—each of which is independently capable of processing the full data center workload. Multiple nameserver sites dispersed
across the United States protect against natural or man-made disasters. Moreover, the architecture scales to support future growth of the usTLD. 

        Essentially,
each NeuStar nameserver for the usTLD is a primary, authoritative nameserver. With near-real-time updates of zone data being handled by NeuStar's
redundant, high-availability database servers, each usTLD nameserver is targeted to its primary function—providing authoritative responses to DNS queries of the usTLD. 

        Registry
data are replicated on redundant, high-availability database servers at the data centers. Zone data are dynamically updated from these databases and propagated to
all the nameservers. Zone file data on the nameservers are updated in near real time. This timely distribution of updates is a significant improvement over the traditional implementation of zone data
deployment. 

        The
benefit to the United States and the Internet community of NeuStar's enhanced approach is a solid architecture with dynamic services designed to maintain maximum stability of the
usTLD and the Internet and promote user confidence. 

        The
following sections describe the operation and maintenance of authoritative nameservers for the us TLD. NeuStar's Technical Plan is described in detail in Section O of this
document. 

B.2.1.1    NeuStar's Multiple Primary Nameservers  

        A nameserver handles resolution of usTLD domain names to their associated nameserver names and to the IP addresses of those nameservers. NeuStar's nameservers
will be dynamically updated from NeuStar's usTLD Zone Update Database over secure VPN links. 

        Each
of NeuStar's nameservers for the usTLD is a primary, authoritative nameserver because each one acquires the same authoritative zone data, in near-real-time,
directly from the authoritative database of usTLD registry data. This implementation provides high availability and scalability, along with significant operational benefits compared with the more
traditional approach based on primary and secondary nameservers. 

B.2.1.2    General Description of Proposed Facilities and Systems  

        NeuStar submits that its redundant, high-availability architectures, including redundant facility implementation, high-availability
cluster server architectures, redundant high-availability database technology, and redundant alternate routed network connectivity, provide significant support for mission-critical service
availability. The Internet community must be able to depend on the Internet as a stable, highly available infrastructure for worldwide collaboration and commerce. 

B.2-3

 

B.2.1.2.1    Facilities Sites and Availability  

        NeuStar's architecture, consisting of redundant data centers and multiple nameserver sites, provides a seamless, responsive, and reliable registry service. Our
data center sites are geographically dispersed and interconnected with Virtual Private Network (VPN) capability to provide access to countrywide coverage and protect against natural and
man-made disasters and other contingencies. The facility locations are provided in the following table: 

Facility Site Locations  

	Data Center Sites
 
	 	Site Location

	NeuStar Data Center and Nameserver Site	 	Illinois
	

NeuStar Data Center and Nameserver Site	
 	

Virginia
	

Third Nameserver Site	
 	

California

        NeuStar's
proposed usTLD Registry Service Level Agreement (SLA) provides service levels commensurate with mission-critical services for availability, outages, response time, and disaster
recovery. Highlights of the SLA include: 

	•
	Registry
Service Availability at 99.9%, with a design goal of 99.99% per year, and

	•
	Nameserver
Service Availability at 99.999%. 

B.2.1.2.2    Data Center Functional Description  

        High-availability registry services can be provided only from facilities that have been designed and built specifically for such a critical operation.
NeuStar's data centers incorporate redundant uninterruptible power supplies; high-capacity ventilation and climate control; fire suppression; physical security; information system
security; firewalls with intrusion detection; redundant, high-availability cluster technology; and redundant network and telecommunications architectures. When selecting the sites, we also
considered their inherent resistance to natural and man-made disasters. The functional block diagram of our enhanced SRS data center is depicted in
Exhibit B.2-2. As can be seen from the referenced exhibit, the data center is highly redundant and designed to eliminate any single
point of failure. 

        Each
data center facility provides the functions listed in the system function table below: 

Data Center System Functions  

	Web Server	 	Delegee Distribution Database	 	Systems/Network Management Console
	

Protocol (XRP) Servers	
 	

Delegee Distribution Clusters	
 	

Applications Administration Workstations
	

Application Servers	
 	

Delegee Servers	
 	

Building LAN
	

Central usTLD Database Servers	
 	

Zone Distribution Database	
 	

Firewall
	

Whois Distribution Database	
 	

Billing and Collection	
 	

Load Balancers
	

Whois Database Clusters	
 	

Authentication Services	
 	

Telecommunications Access
	

Whois Servers	
 	

Backup Server	
 	

Central Help Desk

B.2-4

   
[Exhibit B.2-2: Graphic Design] 

B.2.1.2.3    Nameserver Site Functional Description  

        NeuStar's usTLD nameservers will be colocated with the data center sites described above, with an additional nameserver in California, and their architectures are
consistent with NeuStar's redundant, high-availability approach. Additional nameserver sites will be added as demand warrants. 

        The
functional block diagram of NeuStar's nameserver sites is depicted in Exhibit B.2-3. As can be seen from the exhibit, the nameserver sites are configured to be
remotely managed and operated "lights out." The hardware configuration is highly redundant and designed to eliminate any single point of failure. 

[Exhibit B.2-3:
Graphic Design] 

        The
following function table lists the nameserver functions. 

 Nameserver System Functions  

	Zone Update Database	 	Firewall
	

Nameserver	
 	

Load Balancers
	

Building LAN	
 	

Telecommunications Access

B.2.1.2.4    Building Environment and Security Description  

        Each NeuStar data center facility is located in a modern, fire-resistant building that offers inherent structural protection from such natural and
man-made disasters as hurricanes, earthquakes, and civil disorder. Sites are not located within a 100-year flood plain. Facilities are protected by a public fire department and
have their internal fire-detection systems connected directly to the fire department. Data centers are protected from fire by the sprinkler systems of the buildings that house them.
Furthermore, each equipment room is protected by a pre-action fire-suppression system that uses Inergen gas as an extinguishing agent. 

        Provisions
have been made for the following environmental factors: 

 Environmental Factors  

	Ventilation and climate control	 	Primary electrical power
	

Lighting	
 	

Backup power supply
	

Control of static electricity	
 	

Grounding

        In
addition to providing physical security by protecting buildings with security guards, closed-circuit TV video surveillance cameras, and intrusion detection systems, NeuStar vigilantly
controls physical access to our facilities. Employees must present badges to gain entrance and must wear their badges at all times while in the facility. Visitors must sign in to gain entrance, must
display their badges, and must be escorted by a NeuStar employee. 

        On-site
security personnel are on duty 24 hours a day, 7 days a week to monitor the images from closed-circuit television cameras placed strategically
throughout the facilities. Security personnel are stationed at building access points throughout normal working hours; at all other times, individuals must use the proper key cards to gain access to
the buildings. Further, access to rooms housing sensitive data or equipment is additionally secured with palm-print readers. Senior facility managers 

B.2-5

 

establish
the rights of employees to access individual rooms, and the palm readers compile and record access logs. 

B.2.1.3    Description of System Functions  

        This section provides descriptions of systems functions at NeuStar data center and nameserver Sites that underlie the fundamental operations of the usTLD primary
nameserver(s). Key features of these sites include the following: 

	•
	Co-active
redundant data centers are geographically dispersed to provide mission-critical service availability due to two-way database replication
between the centers.

	•
	Nameserver
sites are designed with full redundancy, automatic load distribution, and remote management for "lights out" operation.

	•
	A
VPN provides a reliable, secure management network and dual-homed connectivity between the data centers and the nameserver sites.

	•
	Each
SRS data center and nameserver site uses high-availability cluster technology for flexibility, scalability, and high reliability.

	•
	Registry
systems are sized to handle the projected workload and can grow incrementally to accommodate workload beyond those levels.

	•
	The
registry database uses redundant, high-availability server architecture and is designed for fully redundant operations with synchronous replication between
the primary and secondary nameservers. 

B.2.1.3.1    Server Platforms  

        NeuStar is proposing cluster server platforms for installation at each site. The servers are selected for applications depending on the requirements, storage
capacity, throughput, interoperability, availability, and level of security. These server platform characteristics are summarized as follows: 

	•
	Nameserver
clusters and zone update servers are implemented with moderate-level Intel server clusters that include the following features:

 Rack-mounted
Intel 700-Mhz, 32-bit, 2- to
6-way SMP CPUs with 8 GB of ECC memory; CD-ROM; four hot-swap disk drives (9-36 MB each); redundant hot swappable power supplies; dual attach 100 BaseT
Ethernet Adapter; clustering and event management software for remote management; Red Hat Linux 6.1; and controlled access protection security. 

	•
	The
redundant, high-availability servers for the Registry's database are implemented on high-end RISC server clusters with the following
features:

 RISC
550-MHz CPU; 64-bit 2- to 32-way cross-bar SMP with 8x8 non-blocking multi-ported crossbar; 32 GB ECC RAM; 240 MB/sec
channel bandwidth; 288 GB Internal mass storage; 50 TB external RAID storage; redundant hot swappable power supplies; dual attach 1,000 BaseTX/FX Ethernet adapter; clustering and event management
software for remote management; and a Unix 64-bit operating system with controlled access protection security. 

B.2.1.3.2    Data Center Systems  

        The data centers provide co-active fully redundant system configurations with two-way replication over a high-speed VPN
network, a colocated complete nameserver, and dual-homed connectivity to Internet Service Providers (ISPs). 

B.2-6

 

        Complete
nameserver implementations for DNS queries are colocated in each data center site and at a stand-alone site in California. Their connectivity includes redundant ISP and VPN
local access links to provide alternate routed connectivity to Internet users and internal networks. Redundant Internet firewalls provide policy-based Internet Protocol (IP) filtering to protect our
internal building LAN from intruders and hackers. 

        The
redundant, high-availability database servers consist of two identical redundant, high-availability RISC systems that are designed for
high-volume, online transaction processing (OLTP) database applications. The database management software is based on a parallel database architecture with a redundant,
high-availability server option capable of maintaining 24 × 7 availability. The redundant, high-availability server supports
high-availability operations by implementing synchronous replication. The database enables transparent database failover without any changes to application code or the operating system.
Clients connecting to a replicated database are automatically and transparently
connected to the replicated pair of databases. The database replication feature enables maintaining geographically separated data services for multiple sites over a WAN to provide disaster recovery. 

B.2.1.3.3    Nameserver Description  

        Two nameserver sites are colocated at our data centers, with a third stand-alone site located in California. The nameservers are geographically dispersed with
dual-homed Internet and VPN local access telecommunications links to provide resilience and disaster recovery. Nameserver sites are configured to operate "lights out." The hardware
configuration is highly redundant, is designed to eliminate any single point of failure, and has exceptionally high throughput. Nameserver subsystem functions that are critical components for
operating a primary, authoritative nameserver include the following: 

	•
	Zone Update Database—The zone distribution database at the data center is propagated to the zone update database
using replication over the VPN. The zone update database is not hit when resolving DNS queries; instead, the nameservers update their in-memory database from the zone update database,
within defined service levels.

In
effect, nameservers are freed of the loading for handling zone transfers, just as the zone update functions are freed of the loading for handling DNS queries and responses. The capability to
insulate systems by separating processing loads is a key feature of NeuStar's systems architecture. 

	•
	Nameserver Cluster—The nameserver cluster handles resolution of TLD domain names to their associated nameserver
names and to the IP addresses of those nameservers. The resolution service can handle the expected load, and our load-balanced architecture allows additional servers to be added to any
nameserver cluster to allow on-demand scalability.

 The
nameserver cluster is based on a high-availability, rack-mounted, multiple computer cluster. A TCP/IP server load balancer switch with a dynamic feedback protocol is used
to distribute the load from Internet users to ensure that traffic is not routed to overutilized servers. 

	•
	Functions External to Nameservers—A major feature of NeuStar's implementation is the matching of functions to
platforms. Critical nameserver functions are implemented on nameserver systems. Related functions that are not specifically critical to nameserver DNS-query-response operation are located
on other platforms that are external to the nameserver platforms.

 Whois
servers, for example, facilitate rapid response to Whois queries without putting any load on the nameservers and without any impact on name service functionality. As mentioned above, 

B.2-7

 

the
traditional functions of DNS query/response handling and zone transfer processing are also performed on separate platforms. 

B.2.1.3.4    Data Center Networking  

        Networking at the data centers provides both Internet connectivity and VPN capabilities. Nameserver and data center connectivity support fundamental operational
functions for name service and zone data. 

        Internet
connectivity is provided by multiple T-class local access telecommunications links at each of our data centers, enabling each to provide usTLD services independently
of the other. The bandwidth and capacity available are provisioned to handle current loads and expected growth for at least two years. 

        Connectivity
to each data center is via redundant routers, with load balancing that distributes the query load among the nameservers in that site's cluster, and with alternate routing to
provide resilience against cable faults and loss of local access telecommunications links. Telecommunications access links for VPN capabilities are dual homed and also use redundant routers and
alternate routing. 

        The
Nameserver site is connected to each data center via VPN, and the two data centers are connected by a pair of ATM links. The VPN capability provides secure networking for internal
exchange of registry data. Important operational functions supported by these networking capabilities include the following: 

	•
	Nameserver
database replication for updating zone data, and

	•
	Remote
administration and backup of the nameservers. 

B.2.1.3.5    Nameserver Software Platform  

        For the DNS software platform, NeuStar will deploy an enhanced version of BIND. The DNS software will comply with the latest IETF standards [RFC 1035,
RFC 2181]. 

B.2.1.3.6    Related Operational Requirements  

        For NeuStar's nameservers for the usTLD, there are operational requirements related to their roles as essential parts of the technical infrastructure of the
Internet. In RFC2870, "Root Name Server Operational Requirements" (R. Bush et al, June 2000), the guidelines provided for the operation of the root nameservers are also provided as guidelines
for the operation of ccTLD nameservers. The usTLD nameservers will comply with all relevant portions of the latest applicable standards for the proper, safe, and secure operation of such nameservers. 

B.2.2    Secondary usTLD Servers  

        NeuStar proposes an architecture in which registry data are maintained on synchronized, redundant, high-availability database servers and in which
zone updates are made to the usTLD nameservers in near real time. In effect, all such nameservers would be primary nameservers, and a DNS query would receive the same authoritative response,
irrespective of which particular nameserver had received the query. This is desirable DNS behavior. 

        As
described in Section B.2.1 above, secondary nameservers are components of the traditional implementation of name service. 

        A
secondary nameserver would obtain authoritative zone data from the primary nameserver for a zone. The primary nameserver would have the responsibility for maintaining the authoritative
zone data, generating the zone data file, and supporting zone data transfers. The "current" zone data would 

B.2-8

 

be
propagated from the primary to secondary nameserver(s). Until all secondary nameservers were updated, the response to a DNS query might depend on which particular nameserver generated the response.
Getting possibly different responses to the same query is not a desirable result. 

        In
fact, if a secondary nameserver received its zone data updates from another secondary nameserver, rather than from the primary nameserver for the zone, the overall propagation delays
for updates would be doubled. This is even less desirable. 

        Section B.2.1
above describes the proposed operation and maintenance of primary authoritative nameservers for the usTLD. Since all of the proposed usTLD nameservers would be
primary, that Section therefore describes the operation and/or administration of the constellation of authoritative servers for the usTLD. 

B.2.3    usTLD Zone Files  

        NeuStar proposes generating zone files in near real time, a major improvement that will eliminate some serious deficiencies in the current TLD system. This
capability ensures that the usTLD nameservers will respond to DNS queries with the most timely, accurate, authoritative, and consistent responses possible. 

        A
zone file is a flat database file consisting of the technical information that the DNS requires to function correctly: the domain name, nameserver host name, and IP address are the
primary data elements. 

        Zone
file generation is the term traditionally used to describe the process of generating a zone file from the registry database, deploying it to the primary root server, and then
propagating it out to the secondary servers. However, this process traditionally is batch-oriented: there are delays incurred before updates to authoritative data are actually available for use in all
the authoritative nameservers. 

        NeuStar
proposes a significant improvement over traditional zone file generation and propagation (i.e., updating the zone file data in near real time within defined service levels). Just
as the current TLD
system does, our proposed registry TLD would store the usual DNS resource records in the zone file database. 

        Unlike
the current system, however, NeuStar's model does not periodically generate a zone file and then publish that new file to a set of nameservers. This proposal describes our process
for creating updates for the nameserver files, including information about distributing and publishing the updates. NeuStar's Technical Plan is described in detail in Section O of this
document. 

B.2.3.1    Current Zone File Generation—Problems and Solution  

        The current zone file creation process has caused many problems for both registrars and registrants. The process is based on the traditional approach of using a
single primary nameserver, which maintains the authoritative data locally, and one or more secondary nameservers, which receive transfers of the primary's data. These nameservers ultimately contain
authoritative data for their zones, meaning that they can respond to queries about their zones based on their locally held data, without the need to further query other nameservers before responding.
However, the traditional process incurs delays and may, at times, return inconsistent responses to queries. 

        Registrants,
in particular, have been troubled by the long delay before their registered domain names go live (or are redelegated). The following are common issues with the current
process: 

	•
	Zone
file update (and propagation) is a batch process performed twice a day.

	•
	Because
updates occur infrequently, registrants have an additional delay before their domain names become "live." This delay confuses the registrants who, assuming that a
problem exists, 

B.2-9

 

contact
the registrar. The registrars must, in turn, respond by deploying unnecessary customer support resources. 

	•
	Currently,
Web sites can easily go down when a registrant transfers a domain name to a new hosting provider. This occurs when, because of the current delay in zone file
generation, the
original hosting provider removes the Web site before the DNS is updated with the new delegation information. This adversely affects the general stability of the Internet.

	•
	Zone
file information does not match Whois information because the two files are often updated at different times.

	•
	Currently,
registrants can update zone information and then check the Whois server to verify it. Because the zone file and Whois service are not synchronized, the
registrants become confused. As with delayed zone file updates, this information mismatch causes additional and unnecessary customer support demands on registrars. 

        To
solve the problems inherent in the traditionally based implementation of zone file generation, NeuStar proposes to introduce a significant improvement to zone file generation and
propagation processes. We will update the zone files in near real time within defined service levels. Near-real-time updates provide the following significant advantages: 

	•
	They
eliminate the synchronization problems that now occur when information is modified.

	•
	They
enable us to define and monitor service levels for the maximum allowable time between zone file updates. 

        The
proposed approach enhances the value of the usTLD by providing the most timely, accurate, authoritative, and consistent responses possible to DNS queries of the usTLD. 

B.2.3.2    Secure Access to Update Zone File Data  

        Under NeuStar's proposed solution, the Centralized usTLD database in the data centers stores all data used to generate and distribute the zone file updates. For
security reasons, neither delegees nor internal data center staff can access this database directly; the application server tier controls all database access. Registrars/delegees access the database
(through the application servers) using the
XRP protocol via the protocol servers. The following procedures govern creating and modifying database information: 

	•
	Registrars/delegee
are solely responsible for creating, modifying, and deleting information that updated the zone file. The XRP protocol is the only gateway available for
zone file editing, and is accessed using XRP servers.

	•
	A
registrar/delegee gains access to a domain name (and associated nameserver) when registering that domain name or when the appropriate Transfer of Registrar is enacted. In
the case of a Transfer of Registrar, access control is revoked from the losing registrar after the transfer.

	•
	Access
control to zone file data for XRP "Delete/Modify Domain Name" commands is granted only to the registrar/delegee that has management rights over the domain name.

	•
	In
the case of an XRP "Create/Modify/Delete Nameserver" command, access control is granted only to the registrar/delegee with management rights over the parent domain name. 

        Other
proposal sections provide additional security related information, including information about deployment security, system and network security, and access-control authentication
and authorization. 

B.2-10

 

B.2.3.3    Frequency of Zone File Generation  

        NeuStar will generate zone file updates (diffs) at regular intervals within defined service levels. Our solution enables us to meet any reasonable service level
merely by adding incremental hardware items and reconfiguring system software settings. 

        Any
real-time zone file update procedure must not degrade the performance of the core registration system. NeuStar's solution will enable us to agree to service levels that
guarantee the zone file distribution database is updated within defined intervals—initially 15 minutes—without adversely affecting core registration operations. 

        In
addition, NeuStar will provide a Zone File Access Program, which will enable registrars and delegees to access the zone file in bulk. Our proposed query program will: 

	•
	Reduce
the load placed on the nameservers by data mining programs (e.g., some ISPs use data mining to accelerate domain name availability checking) and

	•
	Provide
the entire database in a consistent format that will facilitate such services as suggesting alternate names, accelerating DNS queries, and compiling industry
statistics. 

        Finally,
NeuStar will provide for the essential functions for logging and data backup. All zone files and updates are generated using information from the registry database. All updates
are recorded as database transaction logs. Information about the primary database backup and escrow systems, data center replication, and data recovery procedures is contained in other sections of
this proposal. 

B.2.3.4    Zone File Generation Architecture  

        Zone file information is stored in the registry database (along with all other registry data) and replicated to a zone distribution server. The database stored on
the zone distribution server is in turn replicated out to a database at the nameserver data centers. 

B.2.3.4.1    Zone File Replication  

        Each time the zone distribution database is modified and before the zone file update is replicated out to the nameserver data centers, the system performs a
series of quality assurance checks. If any quality assurance checks raise an alert, operations staff must approve the deployment before the update is sent to the nameservers. The quality assurance
checks include: 

	•
	Greater
than a preestablished maximum number of modifications since the last update, and

	•
	Greater
than a preestablished maximum number of modifications since the last update for a special set of domain names used by key e-commerce sites. The alert
threshold will be much lower for these domain names than for the previous check. 

B.2.3.4.2    Standards Compliance  

        Each nameserver will run software that correctly implements the IETF standards for the DNS (RFC1035, RFC2181). 

        NeuStar
will implement all applicable best-practice recommendations contained in RFC2870 (Root Nameserver Operational Requirements). 

B.2.3.5    Zone File Distribution and Publication  

        NeuStar is proposing a significant improvement over traditional zone file generation and distribution by providing near-real-time updates
of the zone file data. 

B.2-11

 

        The
process of updating zone file information at the various nameserver data centers uses information from the zone distribution servers at the two co-active data centers,
which are updated as described in Sections O.4 and O.5. 

        The
databases on the zone distribution servers will be constantly replicated over a Virtual Private Network (VPN) to the zone update database at each nameserver data center. Each
nameserver data center will, in turn, use its zone update database to update its zone file databases. 

        To
ensure availability and provide scalability and redundancy, each nameserver data center will have a cluster of two or more nameservers behind a load balancer. This configuration
enables NeuStar to rapidly accommodate increases in query load by simply adding servers to the cluster at the affected nameserver data centers. 

        The
current zone file creation process has caused many problems—long delays before registered domain names go live or are redelegated—which can also confuse
registrants, disable access to Web sites, and provide inconsistent responses to queries. Currently, zone file update (and propagation) is not real-time (the delay may exceed
12 hours), and zone file information may not match Whois information (updates often take place at different times). 

        These
problems have consequences. Registrants are clearly affected when their domain names are not live. Registrars face additional costs for operations and customer support. Even the
stability of the Internet is adversely affected when delayed zone file updates result in information mismatches and cause unnecessary additional loading. 

        NeuStar's
improvement to zone file generation and propagation—updating the zone files in real time within defined service levels—is designed to eliminate
synchronization problems that occur when information is modified, facilitate the deployment of innovative new technologies such as dynamic update, and enable definition and monitoring of service
levels for zone file updates. 

B.2.3.6    Locations and Architecture  

        The usTLD nameservers that NeuStar will deploy are located in Virginia, Illinois, and California. At the nameserver data centers, a zone update database
constantly receives replication update packages from the zone distribution database server at the registry data centers. This zone update database is not "hit' when the nameservers process requests;
the nameservers use it only to update their zone file databases. NeuStar will deploy, for DNS software, a modified version of BIND. BIND has been modified to delete functions that are unnecessary for
TLD root server operation and enhance functions that are critical to root server operations. The DNS software will comply with the latest IETF standards [RFC1035, RFC2181]. 

        Near-real-time
update of the zone file data (a significant improvement over traditional zone file generation and propagation) takes the zone file information
stored in the registry master database and replicates it to a zone distribution server database. 

        The
following two Exhibits B.2-4 and B.2-5, illustrate the zone file distribution and nameserver update processes. 

        The
database on the zone distribution server at the registry data center is constantly replicated over our VPN to the zone update database at each nameserver data center. The update
packages are compressed, encrypted, and sent with an appended checksum. 

        Every
update package includes a checksum key, which is a generated checksum of the entire database up to and including modifications in that package. Each time a package updates a
nameserver, the checksum is compared to the final state of the zone file data to ensure that the nameserver zone file corresponds to the zone file in the data center's database. If the checksums
indicate an error, the nameserver asks the data center to replicate a full zone file to the nameserver. 

B.2-12

 

The
update package replication process means that the full zone file should never need to be redeployed; however, NeuStar will provide this capability to recover from an unforeseen event. Should this
capability be needed, propagating zone file updates may result in a 60-minute delay. We will include this as an exception in the Service Level Agreements (SLAs). 

        In
the nameserver update process, each nameserver updates its zone file databases from its zone update database within defined service levels. 

B.2.3.7    Frequency of Zone File Publication/Update  

        Any technical solution that includes real-time DNS updates must recognize that the most important function of the nameservers is responding to DNS
queries. This requirement outweighs real-time updating of the zone file. NeuStar's solution is based on this reality. Although our real-time update process includes
establishing and monitoring key parameters that measure compliance with agreed service levels, this process is subordinate to resolving DNS requests. Within this limitation, we are confident in
recommending that no more than 15 minutes elapse before processing an update package. We will be willing to negotiate these or other SLAs to meet performance requirements in a way that safeguards the
integrity of the Internet under heavy DNS load. 

B.2.3.7.1    Monitoring and Logging  

        Our central network management system will log all modifications to the registry database, all zone file update actions, and all attempts at intrusion or other
security-related events. 

B.2.3.7.2    Standards Compliance  

        Each nameserver will run software that correctly implements the IETF standards for the DNS (RFC1035, RFC2181). 

[Exhibit B.2-4:
Graphic Design] 

B.2.4    Whois Database  

        NeuStar's centralized Whois database will ensure quality, consistent implementation and data, with all information available through
publicly accessible means.

        As
part of our efforts to centralize all of the usTLD registration information and to make it available for Web-based queries, NeuStar will create and maintain an accurate
and up-to-date centralized Whois database. In fact, NeuStar will actually administer two logical databases—one for registrants (in both the locality-based space and
the expanded space) and registrars and one for delegated managers, that is, delegees and subdelegees. It is important to manage these entities separately because delegated managers are held to a
higher level of accountability for the management of their namespace. NeuStar will maintain a Web site that will provide access to the Whois databases, and we will also provide a standard port 43
interface to the Whois data. In accordance with the RFQ, access to the Whois data via the Web site and to port 43 will be free of charge and available to the public, and the databases will allow for
multiple field and string searches. Responses to Whois queries will indicate whether the record is in the registrant Whois or a delegated manager's Whois. NeuStar will reach out to the existing
delegees and subdelegees to populate their information and their registrant's information in the databases. 

        Populating
the Whois information in the expanded space will be done through the registrar at the time of registration. Registrations will not be considered complete without all of the
appropriate information being provided. We will populate the data pertaining to the existing assignments by reaching out to the
delegated managers, as well as by retrieving contact information contained in existing zone files of the usTLD administrator and of the delegated managers. 

B.2-13

   
        NeuStar will collect and update, at a minimum, the information listed below for each type of Whois record. 

 Whois Information Under the usTLD  

	Registrants in Locality Space
 
	 	Delegated Managers in Locality Space

	1.	 	Name of the domain registered	 	1.	 	Name of the delegated manager
	2.	 	Internet Protocol (IP) address of the primary nameserver and secondary nameserver(s) for the registered domain name	 	2.	 	Delegated Manager ID
	3.	 	Corresponding names of those nameservers	 	3.	 	IP address of the primary nameserver and secondary nameserver(s) for the delegation
	4.	 	Identity of the delegated manager under which the name is registered	 	4.	 	Corresponding names of those nameservers
	5.	 	Creation date of the registration	 	5.	 	Date of delegation
	6.	 	Name and postal address of the domain name holder	 	6.	 	Name and postal address of the delegated manager
	7.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder	 	7.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the delegated manager
	8.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder	 	8.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the delegated manager
	 	 	 	 	9.	 	Web site or other contact information through which registrations can be accepted under the delegation

B.2-14

 

	Registrants in Expanded Space
 
	 	Registrars in Expanded Space

	10.	 	Name of the domain registered	 	17.	 	Name of the registrar
	11.	 	IP address of the primary nameserver and secondary nameserver(s) for the registered domain name	 	18.	 	Registrar ID
	12.	 	Corresponding names of those nameservers	 	19.	 	Registrar status (e.g., active, pending)
	13.	 	Creation date of the registration	 	20.	 	Name and postal address of the registrar
	14.	 	Name and postal address of the domain name holder	 	21.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the registrar
	15.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder	 	22.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the registrar
	16.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder	 	23.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the billing contact for the registrar

        Further,
to ensure the integrity and highest levels of service for Whois administration, redundant databases will be located at the geographically diverse, redundant Enhanced SRS Data
Centers located in Illinois and Virginia. In accordance with the U.S. Nexus requirement, no registry databases will be located outside of the United States. Both databases will be updated in near real
time (intervals no greater than 15 minutes) and will be synchronized to ensure consistency of the response. 

        Detailed
descriptions of how the databases will be populated, how they are kept up to date and accurate, and the structure of the Whois responses are provided in Section F,
Central usTLD Database and Enhanced Shared Registration System. A detailed description of our Whois policy is provided in Section B.3.5. 

        A
detailed description of the database infrastructure and design is provided in Sections O.3 and O.8 of this proposal. 

B.2.5    usTLD Delegated Manager Database Administration  

        NeuStar's centralized database of delegated managers will enable us to contact those managers quickly and resolve issues
effectively.

        In
order to manage a critical public resource like the usTLD, its administrator needs to maintain an accurate database for all entities that have a role in administering the space. The
usTLD's delegated managers—the locality delegees and subdelegees—play an important role in the communities they serve. The usTLD Administrator may need to contact a delegated
manager because of an outage or a question from one of their registrants. Out-of-date information prevents the administrator from resolving issues in a timely manner. To avoid
this problem and to ensure that all delegated managers can be contacted, an integral element of the Centralized usTLD Database that NeuStar will deploy as the usTLD Administrator will be an accurate
and up-to-date database of delegated managers. 

B.2-15

 

        The
most critical function with regard to creating the database is obtaining information from the existing delegated managers. NeuStar has, in the past, provided just this service to the
telecommunications industry. As the North American Numbering Plan Administrator, NeuStar was required to create a central database of telephone number assignments. This required us to work with
multiple telecommunications companies across the country, most of which had many telephone number administrators. Not only were databases across companies inconsistent, but databases within companies
were often inconsistent as well. NeuStar was nonetheless able to collect and standardize all of the data, and completed the transition ahead of schedule. 

        As
the usTLD Administrator, NeuStar will reach out to all of the delegated managers. We will provide them with a list of the data elements required in our database, and we will provide
them with multiple methods of provisioning that data with us. Our usTLD Transition Team will be tasked with the responsibility of contacting the delegated managers to collect this information. On an
ongoing basis, we will provide delegated managers with an easy-to-use web interface to provision new registrations into the Centralized usTLD Database. Alternatively, should
they have high volumes of registrations and would prefer a mechanized interface, delegated managers will have the option of using NeuStar's extensible Registry Protocol (XRP) to interface with the
registry. 

        Information
in the Delegated Manager Database will include at least the following: 

	1.
	The
name of the delegated manager;

	2.
	The
Delegated Manager ID;

	3.
	The
IP address of the primary nameserver and secondary nameserver(s) for the delegation;

	4.
	The
corresponding names of those nameservers;

	5.
	The
date of delegation;

	6.
	The
name and postal address of the delegated manager;

	7.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the delegated manager;

	8.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the delegated manager; and

	9.
	The
website or other contact information through which registrations can be accepted under the delegation. 

        Detailed
descriptions of how the databases will be populated and how they will be kept up to date and accurate are provided in Section F, Centralized usTLD Database and Enhanced
Shared Registration System. 

        Redundant
Delegated Manager databases will be located at the geographically diverse, redundant Enhanced SRS Data Centers located in Illinois and Virginia. In accordance with the U.S.
Nexus requirement, no usTLD databases will be located outside of the United States. Each database site will be updated in near real time (intervals of no more than 15 minutes) and will be
synchronized. This will ensure the requisite level of availability and stability for the usTLD. 

        A
detailed description of the operations of the databases is provided in Sections O.3 and O.9 of this proposal. 

B.2.6    Data Escrow  

        In addition to arranging for frequent escrowing of the data contained in the usTLD registry, the very design of NeuStar's registry
protects it from catastrophic failure.

B.2-16

 

        The
overall security and integrity of the usTLD requires that there be multiple mechanisms in place to ensure the continued operation of the usTLD in the event of a disaster, technical
or business failure, or any other unforeseen event affecting usTLD operations. Therefore, NeuStar will establish an agreement with an outside escrow agent to develop a process and schedule for
frequent escrowing of the usTLD zone file, Whois database, delegated manager Whois database, and delegated manager database, as well as necessary domain name registration data, including chain of
registration data. 

        Although
a usTLD administrator could choose simply to rely upon an escrow service to ensure data integrity and recovery capabilities, NeuStar believes that additional steps must be taken
to protect such an important public resource. NeuStar's heritage as an operator of mission critical, zero-downtime infrastructure makes it uniquely qualified to address such concerns.
Therefore, the design of NeuStar's registry systems virtually ensures that no single event likely will result in a catastrophic loss of data. Specifically, the NeuStar architecture will utilize
redundant, coactive data centers in Illinois and Virginia, combined with a robust, and redundant nameserver architecture. 

        These
measures by NeuStar will ensure that all data necessary for operation of the usTLD registry will be available in the unlikely event of a catastrophic failure of the registry or
following the selection of an alternate usTLD Administrator by the COTR. Such information will ensure that NeuStar, or any subsequent usTLD administrator, could recover operations quickly and easily,
or in the case of a
transition of administrators, such transmission would occur with minimal, if any, interruptions in service. 

B.2.7    Industry Representation/Compliance  

        NeuStar's continued participation with Internet standards and policy organizations will contribute to its operation of the usTLD as the
model for a country code top-level domain.

        As
is discussed throughout this proposal, one of NeuStar's primary goals is to make the usTLD an important part of the global Internet infrastructure. In order to successfully assume
such a role, however, the usTLD Administrator must be prepared to coordinate with the various members of the Internet community. In particular, the Administrator must be prepared to comply with
applicable policies and standards of the IETF and ICANN. Such policies form the basis for effective functioning of the global Internet and are followed by all reasonable Internet operators. NeuStar
will comply with all such applicable policies and standards in its operation of the usTLD. NeuStar's efforts will not stop, however, at simple compliance. 

        NeuStar
will continue to work with the NTIA, ICANN, IETF, and the Internet community to further develop and enhance not only the usTLD, but also the Internet and the DNS. Such efforts
include participation in development of privacy, security, encryption, multilingual domains, and other important policies and technologies for DNS operations. NeuStar will maintain staff dedicated to
such efforts. Indeed, NeuStar employees currently chair important IETF working groups such as the Whois Working Group. NeuStar intends, therefore, to operate as the model ccTLD in the international
ccTLD community and, through its technical and policy efforts, NeuStar will work to establish the usTLD as the leading example of, and staging platform for, the most advanced DNS registry services on
the Internet. 

        An
important example of NeuStar's efforts in this area will be the revision of RFC 1480 upon completion of the six-month compliance report. NeuStar believes that the learning
from this analysis of the locality-based usTLD will provide an important opportunity for significant improvement of the basic structure and underlying policy of the usTLD. 

B.2-17

 

B.2.8    usTLD Public Awareness Initiatives  

        NeuStar's primary research indicates that a strong demand for dot-us domain names exists within the U.S. public. NeuStar
evaluated this market analysis and performed further secondary research to produce a marketing plan that will maximize brand awareness and drive market adoption.

        In
its commitment to the promotion and marketing of the usTLD, NeuStar has crafted the following Marketing Plan to create public awareness, expand brand identity, and drive
registrations. A key component of the Marketing Plan is the maintenance of a Web site with current policy and registration information. Additional information regarding the usTLD Web site follows in
Section B.2.11. The following section outlines the target markets, potential positioning, and phased awareness initiatives for the usTLD. This approach is one potential strategy to market the
usTLD. 

B.2.8.1    Executive Summary  

        NeuStar will actively market the usTLD making it the most widely available, diverse, competitive option for both consumers and small businesses in the United
States. Sixty percent of the world's domain names originate in the United States. The usTLD, however, has not attracted registrations and remains underutilized compared to other country code domains.
This underutilization reflects poorly on the United States as a technological leader. The problem is due, in part, to lack of promotion and awareness. To address this lack of awareness and ensure the
success of public awareness initiatives, NeuStar conducted primary research uncovering the following empirical evidence to understand customers' needs, motivations, and attitudes: 

	•
	Strong
interest in purchasing a domain name exists, with more than one-quarter (27%) of consumers indicating that they plan to purchase one in the next
12 months. An additional 15% report that they plan to purchase a domain name in the next three years.

	•
	The
usTLD tested very favorably versus other options presented, particularly when the sought-after name in dot-com was unavailable.

	•
	Businesses
would rather have a dot-us extension for their corporate Web site over dot-biz, even though they acknowledge that dot-biz is
more descriptive of a business Web site.

	•
	Consumers
would rather have a dot-us for their personal Web site over dot-name, even though they acknowledge that dot-name is more
descriptive of a personal Web site.

	•
	A
key differentiator for dod-us is that they can receive the name they want. 

        These
findings present opportunities for the usTLD. These opportunities, when combined with appropriate public awareness initiatives supported by a dynamic channel strategy, create an
environment for success. NeuStar will execute a phased marketing program to create a "snowball effect." 

	•
	Phase
1: Our goal in this Phase is to capture as many early adopters/early majority consumers and small business owners as possible.

	•
	Phase
2: Our objectives in this phase focus on both channel and marketing programs. The channel strategy is designed to accredit registrars to extend the reach and
distribution and simplify usTLD acquisition. The marketing programs in Phase 2 build on this strategy and begin branding in targeted cities to capture a larger audience.

	•
	Phase
3: Our aim at this stage is to reach critical mass through a broader awareness campaign. Programs and promotions will be expanded across the country to build on the
contagion already established. 

B.2-18

 

        NeuStar
is confident that this phased approach will succeed for the following reasons: 

	1.
	There
is a strong commitment to make significant investment in marketing, advertising, and public relations to increase the awareness of the usTLD.

	2.
	The
channel strategy is a two-pronged approach. First, it targets current registrars and provides them with tools, programs, and marketing collateral to be successful. In
addition, it expands the size and reach of the distribution network by creating numerous new registrars with built-in membership networks of end users.

	3.
	It
capitalizes on the convergence of the expanded registrar network, the interactions of the early adopters coupled with a broad brand awareness campaign, and new applications to meet
end-user needs. 

        NeuStar
is committed to the success of the usTLD and submits the following documentation providing additional background, market environment analysis, complete research findings, and a
more comprehensive outline of the marketing programs as supporting credentials. 

B.2.8.2    Background  

        NeuStar is uniquely qualified to seize this challenge. As the leading provider of mission critical clearinghouse services, NeuStar has been entrusted to manage
competitively sensitive public resources. It brings distinctive strengths to these efforts: 

	•
	Neutrality Status—The "Neu" in NeuStar, Inc., refers to the trusted, neutral third-party role it maintains
in all interactions with other entities. As an organization that can be trusted for its objectivity, NeuStar is in a strong position to attract registrars and other membership organizations, thus
guaranteeing high participation levels and a strong distribution network.

	•
	Simplified Integration Services—NeuStar has repeatedly demonstrated a capability to leverage database
technologies and operating platforms to simplify the integration of additional services. This capability, when applied to the Registry for usTLD, will enable a variety of value-added services to be
easily deployed, thereby increasing the utility of the space.

	•
	Relationship Building Capabilities—NeuStar has demonstrated an ability to form coalitions of support among
diverse groups, thus providing a secure foundation for success with current delegation owners, future customers, ICANN, registrars, and public sector interests.

	•
	Public Resource Management—NeuStar has established itself as an organization that can deliver mission-critical
services. NeuStar currently manages several public resources. For example, it serves as the administrator of the North American Numbering Plan, operating the telephone numbering registry as a public
numbering resource. Recently, NeuStar was named as the Number Pooling Administrator. And NeuStar is the Local Number Portability Administrator for the U.S. and Canada, operating the enormous routing
registry for North America. The integrity and accuracy of this service is essential for virtually every call placed within North America. NeuStar will leverage this capability of successfully managing
mission-critical resources in managing the usTLD space. 

Market Environment  

        The usTLD will be introduced to a market already served by the very popular dot-com, as well as others such as dot-net and
dot-org. The usTLD will need to be positioned against these competitors, and heightened awareness levels will be required to attract consumers, businesses, and public sector entities.
Creating marketing programs to address these entrenched users will be of primary importance, though recognizing the need to retain current usTLD holders is not forgotten. In a recent NeuStar survey,
both consumers and businesses in the United States had a 99% awareness level of the domain 

B.2-19

 

extensions
dot-com (22.7M registered) and dot-net (4.4M registered).(1) Unfortunately, current awareness levels of the usTLD are not nearly as high. Both consumers and
businesses demonstrated a 3% unaided awareness level of the usTLD. (Unaided awareness tests ask respondents to answer a question without prompting or using precoded categories. For example, an unaided
question might be "Which brands of soda do you drink?") Aided awareness figures are much higher (70% to 74%), indicating general acceptance of the usTLD. (Aided awareness tests ask respondents to
answer a question while providing answer categories. For example, an aided question might be "Below is a list of sodas. Please mark on the answer sheet which brands you drink.") Americans have used
the abbreviation "us" for 200 years, are comfortable with its use, and recognize it in this context. 

	(1)
	Matthew
Zook, Berkeley, Domain Name Project 

B.2.8.3    Strategic Goal  

        The DOC "Statement of Purpose" seeks to achieve the following objectives: 

	•
	Promote
increased use of the usTLD by the Internet community of the United States and

	•
	Promote
robust competition within the usTLD and, in particular, registration services that will lead to greater choice. 

        NeuStar
is guided by these objectives and is committed to increasing the utility and overall value of the usTLD space to drive registrations. To achieve these objectives, it is important
to understand the community of customers and what motivates them to purchase. 

B.2.8.4    Customer Base  

Delegees  

        There are currently 8,000 subdomain delegations to more than 800 individual and entities who maintain a registry and provide registration services for commercial,
educational, and government entities. They span the United States and are primarily composed of businesses, individuals, federal government agencies, schools, libraries, museums, and state and local
governments. All K12 schools, community colleges/technical schools, and state and local government agencies are encouraged to register under the US Domain. 

Public Sector  

        The public sector represents a broad market that includes the sizeable government bodies as well as the many non-profit organizations, all of which
function in a way that suggests prime marketing opportunities for acquisition and promotion of the usTLD. Government bodies alone make up a sizeable group. There are currently more than 500 federal
government acronyms that identify agencies with Web sites.(2) While the opportunities represented by the federal government, the 50 states, and localities are extensive, the opportunity represented by
organizations, charities, foundations, churches, and associations is vast. These organizations, by their nature, are invested in the betterment of the United States and its people. Their numbers are
sizeable. Time Almanac lists 30 U.S. religious bodies with more than 500,000 members. GuideStar's
current list of U.S. nonprofit organizations numbers more than 700,000. Time Almanac 2001, Encyclopedia of Associations, lists approximately 23,000
organizations. These organizations will benefit greatly by expanding their reach via the Internet as they attempt, in a competitive environment, to reach their members and donors. 

	(2)
	Government
Information Resources at http://www.ulib.iupui.edu/subjectareas/gov/doc_abbrev.html 

B.2-20

 

Business  

        There are approximately 12 million businesses(3) in the United States with a labor force of 139.4 million employees.(4) They support an economy with
a gross domestic product (GDP) of $9.3 trillion in purchasing power parity.(5) As the U.S. economy continues to expand and globalization occurs, commercial enterprises are recognizing the need to
utilize the Internet in the growth of their business. In a report by Jupiter Research, the evolution of business and the Internet was explored: 

	(3)
	Dun
and Bradstreet

	(4)
	CIA
Fact Book

	(5)
	Ibid.

	•
	Businesses
reluctantly adopted computing in the 1980's to achieve productivity gains

	•
	In
the 1990's, client/server computing brought new capabilities to business

	•
	Today
the Internet offers a clear set of incentives that have spurred the exponential growth that we will continue to see. Incentives include:

	•
	Availability
of investment capital

	•
	Redefined
business practices to leverage the Internet

	•
	The
pace of adoptions means moving slower, which equals greater risk. 

        Today,
virtually all companies that participate in business-to-business (B-to-B) commerce are being forced to develop new strategies to
keep up with the reengineering of the economy as a whole. 

        Jupiter
estimates that between 2000 and 2005, online B-to-B commerce will swell from 3% to 42% of total B-to-B trade in the United States.
The five largest B-to-B online vertical segments today include: 

	•
	Computers
and telecommunications equipment,

	•
	Food
and beverages,

	•
	Motor
vehicle parts,

	•
	Industrial
equipment, and

	•
	Construction
and real estate. 

        Much
of today's research predicts that Internet growth will continue in the business sector as businesses look to the Internet as a tool to improve traditional and expensive business
processes. 

Small Business  

        There are approximately 9.8 million small businesses(6) in the United States, and they continue to be the fastest growing business segment. Defined as
having between 1 and 99 employees, small businesses employ roughly 40% of the private workforce in America.(7) Small businesses have recently created the vast majority of new jobs in the country. For
example, in a study conducted by Cognetics for the U.S. Small Business Administration, companies with 1-99 employees created 85% of the 11.2 million new jobs generated in the
country from 1992 to 1996. The top spots in the country for small business growth include Phoenix, Salt Lake City, Atlanta, Raleigh-Durham, Indianapolis, Washington DC, Orlando, Nashville, and
Charlotte.(7) 

	(6)
	Dun
and Bradstreet

	(7)
	Cognetics

B.2-21

   
        Small businesses affect every sector of the economy: 37% are in the service sector, 21% in retail, 11% in financial and investment-related, and 9% in manufacturing.(8) Computer use among
small businesses is quite high—estimated at 75% to 97%.(9) A recent study conducted by Dun and Bradstreet indicated online use was also substantial: 

	(8)
	Small
Business and Financial Services

	(9)
	Small
Business and the Internet 

 Small Business Use of the Internet  

	Use
 
	 	1999
	 
	E-mail	 	71	%
	Business research	 	58	%
	Personal research	 	50	%
	Purchase goods/services (business use)	 	43	%
	Purchase goods/sServices (personal use)	 	31	%
	Sell/market products	 	26	%

Medium and Large Business  

        Large businesses are defined as having more than 1,000 employees. There are approximately 7,000 firms(10) that fall into this category, and they represent .05% of
U.S. businesses. Medium-size businesses are characterized as having between 100 and 999 employees. There are approximately 2 million medium-size enterprises.(11) 

	(10)
	Ibid.

	(11)
	Ibid.

Consumers  

        When compared to other countries, the United States has the highest penetration of online consumers.(12) More and more consumers are utilizing the Internet to
gather information, research products, communicate via e-mail and meet their lifestyle needs. About 164 million (59%) of consumers are online today.(13) The online population is
predominantly located in large cities and the suburbs when compared with U.S. population density: 

	(12)
	Nielsen
NetRatings

	(13)
	U.S.
Census/Nielsen NetRatings 2001 

 Online Population  

	 
	 	U.S. Population
	 	Online Population
	 
	Large city	 	20	%	22	%
	Suburbs	 	23	%	31	%
	Small city/town	 	36	%	32	%
	Rural	 	21	%	14	%

        Geographically,
the online population is concentrated in the Pacific West, South Atlantic, and East North Central regions, but it continues to expand beyond the technology regions (U.S.
Census). Low-cost computers and reduced Internet access costs have contributed to the rise in overall household 

B.2-22

 

penetration.
San Francisco (66%), Seattle (64%), San Diego (62%), and Portland (60%) led the way with the highest household penetration rates as of September 2000.(14) 

	(14)
	Ibid.

        The
consumer online population is characterized by several distinct factors that play a significant role in a marketing effort. They are almost evenly split by gender (51% female and 49%
male), and 30% are between the ages of 35 and 49. They are overwhelmingly white and well educated when compared with the national average. The percentage of adult Internet users who have graduated
from college is 41%, nearly double the national average of 22%. Given that the Internet is primarily an information source, the more educated people are, the more likely it is that they will be
motivated to use the Internet. The typical online household has an annual income nearly 36% higher than that of the average American household; 30% of those online have incomes of $50,000-$75,000
although online use by those in lower and middle income groups is growing.(15) Although Internet users have higher income levels than the average American, a comparison with 1999 data reveals a
widening trend that includes lower levels of affluence. This expansion of income levels is attributed to lower costs for PCs and Internet access, as well as greater acceptance of the Internet as a
safe and convenient way to shop. Correlations can be drawn when examining occupation and online usage: 32.5% of the U.S. online population is in executive, managerial, or professional occupations.
Most of these workers use a computer and/or access the Internet as part of their work. On average, more time is spent online at work than at home. June 2001 data show that the number of online
sessions at work is twice the number of sessions at home.(16) 

	(15)
	Ibid

	(16)
	Ibid

        In
a study conducted by The Media Audit (a syndicated survey of both online and traditional media in more than 80 markets over a three-year period—1998, 1999, and
2000), online usage is diversifying. African American online usage has increased 41% during the past three years to 44% online usage today. The U.S. Census estimates that Hispanics represent the
fastest growing segment of the U.S. population with more than 30 million Spanish-speaking residents. Moreover, in a report published by The
Economist, the buying power of Hispanics in the United States has increased by 65% since 1990 to $348 billion. Tapping into this buying power can be done online: 42% of
Hispanics now have access to the Web, according to The Media Audit—an increase of 45%. Sixty-three percent of Asians were online in 1998. In 2000, that figure had risen 7% to more than
70%. Seventy percent exceeds the comparable figure for white households, whose online usage is about 58%. 

        E-mail
ranks as the most popular online activity for consumers. It is expected that there will be 140 million active e-mail users in the United States by
2003. While many consumers have between two and five accounts, 51% check only one e-mail account daily. It is estimated that online adults will spend between 9 and 10 months of a
typical lifetime writing and responding to e-mails. Research shows that e-mail has created a greater connection among family members with 26 million Americans regularly
sending e-mail to a family member with whom they had not previously had much contact.(17) Instant Messaging is another communications activity that is frequently used by online Americans.
Instant Messaging continues to grow because it is free and easy to use. In addition, approximately 30 million Americans are members of families in which someone has created a family Web
site.(18) It is evident that the internet has introduced a fundamental shift in the way people communicate. As this communication medium becomes widely accepted, more citizens will want to own domain
names to increase their online interactions. According to NeuStar research, less than 10% of Americans currently own a domain name. 

	(17)
	Pew
Internet Project

	(18)
	CyberAtlas

B.2-23

 

B.2.8.5    Marketing Objectives  

        The single marketing objective of this plan is to ensure that every consumer, business, and public sector entity of the United States is aware of the usTLD,
understands its value, and knows how they can acquire a dot-us domain name. 

B.2.8.6    Market Definition  

        Successful launch of the usTLD will rely on marketing initiatives aimed at the appropriate audience with the appropriate message. Clearly understanding the size
of the target, their demographic makeup, and their motivations and attitudes toward the Internet and domain names in particular will provide the foundation to drive usTLD penetration quickly. A
research study was conducted to obtain empirical data for both U.S. businesses and consumers. 

Research  

        NeuStar commissioned primary research to ensure a solid foundation from which to create a marketing strategy for the usTLD. The resulting information serves as
the basis for all aspects of the marketing plan and will enable NeuStar to establish a presence and firmly position the usTLD quickly. 

Objectives  

        Research was conducted in the form of a survey to a general audience of consumers and businesses regarding their attitudes and perceptions of the usTLD. The
survey objectives were to: 

	•
	Understand
market awareness of the current usTLD;

	•
	Assess
general awareness of country code extensions;

	•
	Determine
the size, demographics, and psychographics of the target market for the usTLD;

	•
	Assess
branding potential for the usTLD;

	•
	Determine
what product benefits are the most meaningful;

	•
	Understand
the barriers to purchasing a usTLD for both businesses and consumers;

	•
	Evaluate
the receptivity of usTLDs vis-à-vis other TLDs;

	•
	Evaluate
receptivity to locality-based domain name structures;

	•
	Determine
acceptability and preference for the hierarchical structure for the usTLD;

	•
	Test
various product-positioning statements for marketing the usTLD;

	•
	Determine
motivations for purchase of a domain name and types of Web sites;

	•
	Determine
means of differentiating the product;

	•
	Obtain
feedback regarding price; and

	•
	Evaluate
the likelihood to purchase. 

Methodology  

	•
	An
18-minute online survey consisting of both open-ended and close-ended questions,

	•
	A
sample size of 1,000 panelists,

	•
	Invitation
e-mailed to the respondent panels, 

B.2-24

 

	•
	Cash
drawing included as an incentive to increase the participation rate, and

	•
	Data
weighted to be representative of the overall online consumer and business market. 

Research Participants  

	•
	Sample
composition of 1,231 consumer and 1,355 business panelists within the United States,

	•
	Subsample
of at least 300 consumer and 300 business panelists who have purchased a domain name in the past to continue with the survey,

	•
	The
margin of error for the consumer sample as a whole was 2.8% at the 95% confidence interval, and

	•
	The
margin of error for the business sample as a whole was 2.6% at the 95% confidence interval. 

Target Audience  

	•
	Sample
was drawn from an existing online panel.

	•
	Split
sample consisted of consumers and business people who have used the Internet with some frequency.

	•
	All
panelists reside in the United States.

	•
	Initial
panel members were selected to be reflective of the online population of businesses and consumers and were not screened for particular knowledge of domain names.

	•
	To
continue the survey, 300 consumer and 300 business panelists were oversampled for current ownership of a domain name.

	•
	Screener
identified, but did not terminate, decision-makers in the category with the intention of finding sufficient sample size.

	•
	Small,
medium, and large business were quantified. Their percentages and responses will be reflective of the online business community.

	•
	Results
will be cross-tabbed to reflect both overall U.S. population and online U.S. population. 

Research Highlights  

        The major findings of the research can be found below. A complete report detailing the research findings is located at the end of this document. 

General Highlights  

	•
	On
a macro level, both businesses and consumers show a strong purchasing preference for gTLDs over specific TLDs.

	•
	The
usTLD tested very favorably versus the options presented, particularly when the sought-after name in dot-com was unavailable.

	•
	Consumers
and businesses overwhelmingly believe that public service second-level domains are a good idea. 

Consumer Research Findings  

	•
	Domain
name penetration (in percentage terms) is very low in the online consumer sector, with less than 1 in 10 people (6.6%) currently owning a domain name. 

B.2-25

 

	•
	In
an aided test, approximately three-quarters reported that they know that dot-us exists. This aided figure is very close to that for TLDs other than
dot-com and dot-net TLDs (such as dot-biz, dot-tv, and dot-pro). This suggests that even though the generic use of dot-us has
been released after some others, it does not start at a brand equity or intent to purchase disadvantage vis-à-vis newer TLDs.

	•
	Domain
name extensions appear to be less important to consumers than choosing a descriptive name for a Web site. For example, by a 3-to-1 margin,
consumers would rather select a first choice name with a dot-us extension than a less desirable name with a dot-com extension.

	•
	Consumers
would rather have a dot-us extension for their own Web site over dot-name, even though they acknowledge that dot-name is more
descriptive of a personal Web site.

	•
	Consumers
clearly prefer TLDs that:

	•
	Are
flat rather than hierarchical,

	•
	Are
generic (like.us) rather than specific (like dot-name), and

	•
	Encourage
shorter rather than longer names. 

Business Research Findings  

	•
	We
do not anticipate a great deal of business activity in the next year, since only 7% of businesses say they plan to purchase a domain name within the next year. An
additional 4% report that they plan to purchase a domain name in the next three years.

	•
	In
an aided test, approximately 7 in 10 report that they know that.us exists. This aided figure is very close to that for TLDs other than dot-com and
dot-net (such as dot-tv and dot-pro). This suggests that even though the generic use of dot-us has been released after some others, it does not start at
a brand equity or intent to purchase disadvantage vis-à-vis newer TLDs.

	•
	Our
initial estimates are that approximately 1 in 5 state some interest in eventually purchasing a usTLD name. This is an elastic figure, however, as many more are willing
to consider a usTLD if

	•
	Their
dot-com option is taken

	•
	dot-us
can competitively compete with dot-com on price

	•
	They
realize the necessity in purchasing dot-us in order to prevent cybersquatting.

	•
	While
small and large businesses demonstrate strong interest in purchasing domain names going forward, midsize businesses appear less interested.

	•
	Businesses
(just like consumers) clearly prefer TLDs that

	•
	Are
flat rather than hierarchical

	•
	Are
generic (like dot-us) rather than specific (like dot-name)

	•
	Encourage
shorter rather than longer names. 

Research Conclusions  

        The results from this survey show that Americans strongly feel that creating additional domain name extensions is a good idea. Clearly the market recognizes the
need for additional open space on the Internet. Whether we will see a rush to acquire additional domain names remains an open question. What is known, however, is that the usTLD is
well-positioned vis-à-vis other major TLDs. The primary reason is that both business and consumer purchasers appear to prefer multipurpose 

B.2-26

 

TLDs
over single-use TLDs. The likely cause is the widespread use of dot-com in the U.S.—the ultimate generic multipurpose TLD. Over the years, research has shown
that people tend to gravitate toward the familiar, hence the preference for other generic multipurpose TLDs. We believe that, with an intelligent brand awareness and advertising campaign, the usTLD
can gain significant market share in the coming years. 

        Many
natural uses for the usTLD already exist. In particular, Americans feel that dot-us is particularly well suited for e-government initiatives. For example,
Americans overwhelmingly think the use of the usTLD would work for programs such as creating a Web site called voting.us which lists local polling places and information about political candidates or
a Web site called parks.us which lists local, state, and national parks. 

[Graphic
Design] 

        While
e-government initiatives could help drive the growth of the usTLD, it would be a mistake to limit its utilization to that market, since both consumers and businesses
show interest in using the usTLD. In fact, overemphasis of e-government initiatives could persuade consumers and businesses that the usTLD is solely for government and public sector Web
sites—a scenario that is clearly avoidable. There appears to be strong demand on the consumer side of the equation. Our survey found that 27% of American consumers plan to register a
domain name in the next year. Additionally, survey respondents acknowledge that their first choice domain name with the dot-com suffix might be taken. As a result, they are looking at
secondary options. When we asked likely domain name consumer purchasers "If you had to select a new domain name and dot-com was already
taken but dot-us and dot-name were available, which would you choose?" a plurality (38%) selected the usTLD, 30% chose another name with the dot-com extension, and
only 10% selected
nameTLD. This speaks both to the power of the usTLD and the interest in multipurpose generic use TLDs. 

[Graphic
Design] 

        On
the business side of the equation, we also see a preference for the usTLD. When we asked likely domain name business purchasers "If you
had to select a new domain name and dot-com was already taken but dot-us and dot-biz were available, which would you choose?" a plurality (42%) selected the usTLD,
17% chose another name with the dot-com extension, and only 25% selected bizTLD. 

        To
reiterate: We believe that latent demand exists for the usTLD and that a strong marketing campaign will create the requisite interest in and eventual use of the usTLD. 

Key Survey Tables and Projections  

 Plan To Purchase Domain Within Next 12 Months / 3 Years  

	 
	 	Percentage
	 	Pop. Projection

	Business—12 months	 	8	%	0.7 M
	Business—3 years	 	5	%	0.4 M
	Consumer—12 months	 	27	%	35.8 M
	Consumer—3 years	 	11	%	15.2 M
	Total	 	—	 	52.1 M

B.2-27

 

 Likely To Purchase usTLD One Day  

	 
	 	Percentage
	 	Pop. Projection

	Business	 	4	%	1.6 M
	Consumer	 	23	%	31.5 M
	Total	 	—	 	33.1 M

 Likely To Consider Purchasing.usTLD After Being Informed of New System  

	 
	 	Percentage
	 	Pop. Projection

	Business	 	39	%	3.0 M
	Consumer	 	40	%	24.0 M
	Total	 	—	 	27.0 M

B.2.8.7    Market Opportunity  

        The research indicates that there are several opportunities to market and position the usTLD to address the needs of American consumers, businesses, and public
sector entities with regard to domain names: 

	•
	With
usTLD "I can get the name I want."

	•
	The
usTLD is generic, which provides greater use possibilities for both businesses and consumers.

	•
	Americans
reacted favorably to new TLDs in general.

	•
	Less
than 10%of American online consumers have domains today.

	•
	Small
and large businesses indicate interest in purchasing domain names going forward.

	•
	About
114 million Americans are not online today. NeuStar is committed to ensuring that new online citizens have a usTLD as the online household penetration continues
to grow. 

B.2.8.8    Value Proposition  

        Establishing a value proposition for a product provides the foundation around which a marketing campaign can be built. Value propositions define the most
important benefits or facts the target group of customers should know and readily understand about the product being marketed. They clearly establish why the product is important, defining each
product feature specifically and translating those features into customer benefits. Marketing programs are designed around communicating those benefits 

B.2-28

 

to
target groups. The research indicates that customers are interested in receiving the following benefits from the features of a domain name product: 

 Domain Name Features and Benefits Identified Through NeuStar's Research  

	Feature
 
	 	Benefit

	U.S.-centric	 	Identifies owner as a U.S. citizen, organization, nonprofit organization, government, charity, or church
	

New	
 	

Name they want is available
	

Competitive price proposition	
 	

Affordable, good value
	

Generic TLDs with flatter hierarchical structure	
 	

Wider use/wider popularity
	

Direct registration	
 	

Simplicity, ease of acquisition
	

Available through a wide distribution network	
 	

Simplicity, ease of acquisition

Positioning  

        Product positioning is helpful in identifying the specific position or definition that is desired when promoting the product. It defines how a product should be
known, described, or characterized in the 

B.2-29

 

customer's
mind. Based on the research outlined above, the following are examples of how the usTLD could be positioned: 

 usTLD Positioning  

	Market
 
	 	Responding to what

emotion or attribute
	 	Product Feature

Targeted
	 	Positioning Statement

	Consumers and businesses	 	Trust and security	 	U.S.-centric	 	usTLDs are trusted Web sites managed by individuals and businesses located in the United States
	

Consumers and businesses	
 	

Ease	
 	

Generic TLDs with flatter hierarchical structure	
 	

A new, easy-to-remember Web site that is owned and operated in America
	

Consumers and businesses	
 	

Uniqueness and urgency	
 	

New	
 	

A newly introduced domain name extension that allows me to get the name I want
	

Consumer singles, students, young families, self-employed	
 	

Cool factor, few people have this new cool thing	
 	

Personalization	
 	

usTLDs give you a piece of the Web that is as individual as you are by letting you name your own Web site.
	

5) Self-employed, SOHO	
 	

Multipurpose	
 	

Generic	
 	

usTLDs allow my Web site to be used for multiple purposes

Logos and Taglines  

        Logos and taglines are developed to provide customers an easily identifiable company symbol. These images or symbols help to brand a company or product by
offering a brief, easily recognizable description. Both consumers and businesses agreed that dot-us was easy to remember. In addition, they felt the extension was a clear indication that
the owner of the Web site was an American citizen. They also had favorable reactions to words like "trustworthy" and "descriptive" when asked to describe the usTLD. Given these findings, the logos, as
shown in Exhibit B.2-6, are examples of the types of symbols that could be used to brand or characterize the usTLD with the American public. 

[Exhibit B.2-6:
Graphic Design] 

B.2-30

   B.2.8.9    Channel  

        Surprisingly, many consumers and businesses do not know how to purchase a domain name today. NeuStar's survey revealed that 3 in 5 consumers and 1 in 5 businesses
do not know how or where to purchase domain names. This indicates a need for both education and a widely distributed network of sales channels to provide ease of acquisition for U.S. citizens.
NeuStar's channel strategy is to create the widest distribution network possible to enable every citizen a speedy and simplified registration process. Educating citizens on where and how to acquire a
usTLD will be covered within the Marketing Plan below. NeuStar would accomplish the channel objective in two phases: 

 Phase 1  

	 
	 	 
	 	 

	Objectives	 	•	 	Achieve 100% participation from ICANN-accredited registrars
	

 	
 	

•	
 	

Create a sense of urgency and excitement around the usTLD to encourage the registrars to assist in public awareness and promotional campaigns
	

Market	
 	

Accredited registrars
	

Programs	
 	

•	
 	

Seminars
	

 	
 	

•	
 	

Letters of usTLD introduction to all appropriate registrars
	

 	
 	

•	
 	

Creation of sales materials
	

 	
 	

•	
 	

Sample graphics for use on resellers' Web sites
	

 	
 	

•	
 	

Fact sheet outlining the usTLD opportunity and benefits of the structure and application platform
	

 	
 	

•	
 	

Tool kit
	

 	
 	

•	
 	

Online Web site
	

 	
 	

•	
 	

Work with search engines to ensure dot-us is recognized
	

Timing	
 	

1-4 months prior to launch

B.2-31

 

 Phase 2  

	 
	 	 
	 	 

	Objectives	 	•	 	Expand the network beyond current registrars to ensure that every American citizen, business, and public sector can easily acquire a usTLD
	

 	
 	

•	
 	

Simplify the accreditation process to encourage wide participation of commercial organizations, nonprofit organizations, foundations, government, charities, churches, and associations
	

Market	
 	

•	
 	

Entities that offer channels beyond the online environment
	

 	
 	

•	
 	

Benefits to these organizations as they expand service offerings and end-user benefits
	

Programs	
 	

•	
 	

Creation of accreditation process (Registrar in a box)
	

 	
 	

•	
 	

Letters of introduction to wide selection of entities
	

 	
 	

•	
 	

Direct sales to targeted businesses and public service groups
	

 	
 	

•	
 	

Creation of sales materials
	

 	
 	

•	
 	

Educational seminars—benefits of the proposition and ease of implementation
	

 	
 	

•	
 	

Fact Sheet outlining features and benefits, sales potential, or member reach for use in collateral
	

 	
 	

•	
 	

Tool kit
	

 	
 	

•	
 	

Sample graphics for use in information material/collateral
	

 	
 	

•	
 	

Online Web site
	

Timing	
 	

Launch + 1 year

B.2.8.10    Marketing Plan  

        In order to promote the increased use of the space, expanding awareness levels is essential to a successful strategy. To be successful, branding requires a
consistent message, delivered frequently to the target group. A phased approach is recommended, based on the levels of immediate interest and the purchase intent of target groups. The programs are
designed to increase brand awareness and penetration across the United States to businesses, consumers, and the public sector. 

        Phase
1 objectives are to reach two specific target groups prior to launch. 

	•
	Current
owners of the usTLD will be notified of the changes taking place. The marketing material will pay particular attention to the benefits of a new Administrator and the
expansion of utility. Registrants will be encouraged to take advantage of these new features.

	•
	Consumers
and small business owners will be targeted to create buzz and suspense. The overall objective is to generate a level of interest prior to launch that would
encourage a high number of registrations at launch. 

        These
initiatives are critical and will be successful because they reach both current owners and those targeted consumers and business owners who have already expressed interest and
purchase intent. Capturing this group first is essential, as they become the foundation for the public awareness and word of mouth advertising on the Web. 

B.2-32

 

        Phase
2 builds on the awareness objectives as marketing and promotional efforts are launched to reach a wider audience. The major objectives of this phase are to: 

	•
	Touch
consumer early adopters and early majority to lead the way in numbers of usTLD registrations. As a sizeable mass of consumers begins to adopt the usTLD, more will be
interested and will follow suit.

	•
	Increase
awareness of those in the business community likely to purchase in the near term. Advertising and branding efforts will include education on product benefits and
the registration process to address lack of knowledge on how to acquire a domain name.

	•
	Enable
e-Government initiatives (see Section D for further information) outlining the public's interest in response to the NeuStar research. This interest
will be leveraged as sites come online to further the program.

	•
	Drive
registrations within the ethnic community by increasing awareness levels. Online populations within this community are growing. 

        Phase
2 efforts are designed to address both the timing related to purchase intent as well as the educational challenges that were uncovered within the research. Ensuring that the
population is knowledgeable of the product benefits and is aware of how and where to purchase is critical to driving registrations. This effort will be supported by the channel strategy. As more and
more businesses, groups, and organizations recognize the value of providing and promoting usTLDs to their customers, associates, and members, registrations will increase. In addition, both businesses
and consumers were overwhelmingly positive toward e-Government initiatives. These initiatives should be launched in Phase 2 as an increased benefit and in response to customer needs. 

        Phase
3 reaches across the country to all citizens to ensure they have the knowledge and the opportunity to acquire a usTLD. The major initiatives are planned to: 

	•
	Drive
toward critical mass using vehicles and messages that reach a wider audience of U.S. consumers and businesses. The marketing vehicles will place specific emphasis on
promoting product benefits—"with dot-us, you can get the name you want"—and educating Americans on where to acquire the premier ccTLD.

	•
	Partnership
marketing, affinity opportunities, and relationships will be leveraged to maximize awareness opportunities and drive registrations.

	•
	New
applications will be launched to derive additional product benefits and increase end-user utilization. 

        Phase
3 leverages the momentum established in the early stages. The usTLD message is spread to a greater audience with increased frequency. As the third phase progresses, Americans will
know that a new generic TLD is available, the value of owning one, how applications can improve their utility, and how and where to acquire one. Phase 3 continues to build and rely upon partnership
and affinity marketing strategies that take advantage of the greatly expanded distribution network. NeuStar is confident in this strategy because it: 

	•
	Implements
a build-out strategy to create the brand and increase awareness levels.

	•
	Provides
the greatest distribution network possible by leveraging end-user relationships and providing customers more opportunities to acquire a usTLD.

	•
	Executes
a staged plan to capture those users who are ready to purchase today, creates awareness for the group who indicated a desire to purchase tomorrow, and educates the
balance on why they need a usTLD next week.

	•
	Addresses
educational challenges uncovered in the research. 

B.2-33

 

	•
	Communicates
new applications to increase the utility of the product.

	•
	Responds
to citizens' needs for public interest and e-Government services. 

        What
follows is an outline of the types of campaigns and the coverage that would be launched within each of the program phases. Each phase builds upon the one prior to capture the widest
possible audience with as many impressions as possible. 

Conclusion  

        This plan conclusively demonstrates NeuStar's ability to successfully achieve expansion of the space and drive registrations of the usTLD to every corner of the
country. NeuStar has reviewed and addressed the key factors for success. It has conducted research to understand what American consumers and businesses think about domain names and the usTLD in
particular. With this understanding of the market, NeuStar has developed a plan to reach the U.S. audience. NeuStar recommends getting started on this plan immediately to ensure that usTLDs will be
available to more American consumers, businesses, and public sector entities without delay. 

Complete Research Findings  

 Summary of Results and Conclusions—Consumers  

	[***]	 	[***]

 Summary of Results and Conclusions—Businesses  

	[***]	 	[***]

B.2.9    Integration Assistance  

        NeuStar's Registrar Tool Kit software and operational test-and-evaluation facility will ensure that registries
rapidly become familiar with our thick registry system, allowing them to begin operations efficiently, as soon as possible after accreditation.

        NeuStar
will operate a thick registry for the usTLD; although this thick registry allows us to enable new and enhanced services, it will also require registrars to follow new procedures
when working with the usTLD registry. NeuStar will make every effort to give our registrars the support they need for a smooth transition to integrating with the usTLD registry. 

        Once
a registrar is accredited, NeuStar will provide the XRP Registrar Tool Kit (RTK) software, along with documentation and training materials, to enable that registrar to learn the
procedures and to obtain the technical knowledge necessary to interface with the usTLD registry. 

        NeuStar
will establish an operational test-and-evaluation facility that will be available 24 × 7 × 365 for
registrars to test their client systems. Our technical support team, which consists of functional experts in the processes and technologies for domain-name registration, will support this
testing. 

        Once
each new registrar is satisfied that its system is compatible with the registry system, it will schedule a formal acceptance test that will be monitored by our system
engineers. After a registrar has passed the acceptance test, we will issue a user ID, passwords, and digital certificates, so that the registrar can begin operations. 

B.2-34

 

B.2.10    Compliance Monitoring  

        Monitoring of delegees for technical compliance to the most current usTLD policies will ensure that NeuStar's database remains up to date,
that delegees remain compliant with usTLD technical requirements, and that the usTLD retains a U.S. Nexus.

        As
discussed in Section B.4.5, NeuStar will conduct an initial compliance investigation in the first six months after contract award. This investigation is a requirement of the
RFQ, and is intended to allow NeuStar to suggest policy changes, as well as to identify non-responsive delegees (including subdelegees), delegees who do not meet policy and technical
compliance requirements, and "locality squatters." As part of this investigation, we will work collaboratively with delegees to help them achieve both policy and technical compliance, if they are
found lacking in any way. 

        Information
garnered from this investigation should also serve to confirm information received from the current administrator regarding server names and physical locations of the delegee
servers. This will allow NeuStar to ensure that all delegee nameservers are physically located in the United States. 

        It
is also important, however, that delegees continue to remain compliant with usTLD technical requirements for the lifetime of their delegations, and a level of oversight by NeuStar
will help to guarantee this. Since NeuStar will not necessarily be hosting the resource records associated with names registered to delegated managers, it is possible for the delegee to register a
name and forget to update NeuStar. NeuStar will "walk the tree" (see Section F for a description) on a continuous basis and compare the results with information in the Centralized usTLD
Database. If there is a difference, we will contact the delegated manager to correct the discrepancy. Additionally, NeuStar will perform yearly monitoring for technical compliance of locality
delegees. 

        During
this yearly audit, NeuStar will check that delegees continue to meet the technical and other requirements set out in RFC 1480 and other documents, and will include the following: 

	•
	There
must be a knowledgable and competent technical contact, familiar with the Internet Domain Name System.

	•
	The
actual management of the assigning of domain names, delegating subdomains, and operating nameservers must be done with technical competence. This includes keeping the
usTLD administrator or other higher-level domain managers advised of the status of the domain; responding to requests in a timely manner; and operating the database with accuracy, robustness, and
resilience.

	•
	There
must be a primary and a secondary nameserver that have IP connectivity to the Internet and can be easily checked for operational status and database accuracy by the
usTLD administrator.

	•
	Nameservers
should be in distinctly separate physical locations. It is appropriate to have more than two nameservers, but there must be at least two. 

        In
order to perform this monitoring function, NeuStar will compare delegee information in the Centralized usTLD Database with information in the zone files. NeuStar will also prepare a
technical survey to send to delegees, requesting information to confirm the names and physical locations of delegee nameservers, as well as delegee contact information. 

        In
continuing with our cooperative approach to our initial compliance investigation, NeuStar will be monitoring compliance to ensure that all delegees meet the technical and U.S. Nexus
requirements necessary to run a usTLD delegation and protect the integrity of the usTLD and of the Internet. As with the original report, we will work with any deficient delegees to help them achieve
technical compliance. 

B.2-35

 

B.2.11    Web Site  

        NeuStar's usTLD Web site will provide comprehensive information and communications methods to registrars and delegees while also
displaying, informative essential pages to the general public.

        NeuStar
recognizes how critical information flow is for a registry to interact with its registrars. We also understand that, as the administrator responsible for the integrity of the
usTLD, we must provide information that can be easily accessed by the Internet community. Although these are two very distinct requirements, they can easily be incorporated into a single,
easy-to-navigate, content-based Web site. NeuStar will implement such a Web site divided into a public section for potential new registrars and the Internet community and a
private section for existing registrars and locality delegees (including subdelegees). 

        The
public section of this Web site will provide information to potential new registrars as well as to the Internet community. It is vital that this section of the Web site be easy to
use and easy to navigate; we will make every effort to prevent confusion, especially among the newest visitors to the Web site. 

        This
public portion of the Web site will allow users to do the following: 

	•
	Obtain
information about the locality—based and expanded usTLD spaces;

	•
	Identify
a locality-based delegee for registration in a delegated space or subdelegation of a space;

	•
	Register
a domain name in an undelegated locality space;

	•
	Locate
a registrar for registration in the usTLD expanded space;

	•
	Access
the usTLD Help Desk via e-mail and messaging services;

	•
	Obtain
Whois information, by string or field search, in the usTLD;

	•
	Look
up the availability of domain names; and

	•
	Apply
for accreditation as a registrar in the expanded space. 

        Our
efforts to maintain the best possible communications with usTLD registrars will be reflected in the private members section of the usTLD Web site. This section will allow registrars
to access information about all areas of the registry's operation. Some of the key components of the site will be: 

	•
	A
password-protected area where registrars will be able to access reports,

	•
	A
password-protected area where delegees and registrants will be able to communicate with the registry,

	•
	A
central repository of all public documentation,

	•
	Detailed
information and documentation regarding integration assistance,

	•
	A
comprehensive list of Frequently Asked Questions (FAQs),

	•
	Access
to the usTLD Help Desk via e-mail and instant messaging services,

	•
	All
relevant contact information and escalation procedures,

	•
	Access
to customer account information,

	•
	A
collection of marketing material and information that may be freely used by registrars to help them promote the domain space, and

	•
	Free
downloads of RTK software. 

B.2-36

 

        NeuStar's
Web development team is experienced in providing Web sites that allow both public and private access. We will leverage our Web development experience and design an
easy-to-navigate, content-based Web site that will provide fast and easy access to services, help, and information to all of our customers. 

B.2.12    Documentation and Training  

        Readily available, clear and concise procedures and documentation ensure a stable system, informed customers, and knowledgeable Help Desk
account representatives. These are fundamental to NeuStar's customer service philosophy.

        Accurate,
detailed documentation is vital to the implementation of any successful TLD registry, particularly when transitioning the administration of and enhancing the registry. System
documentation in particular will contribute to the stability of the registry and improve service enhancements. 

        Two
distinct types of documentation are required in order to provide a complete understanding of the usTLD and the services being provided—internal and external. Internal
documentation
includes both system documents and methods and procedures (M&P) documents. External documentation includes all user documents, such as online help and user's manuals and training materials for new
registrars. Training of the usTLD staff ensures the highest quality of customer service that NeuStar can offer, and training materials provided to registrars allow those registrars to quickly become
familiar with usTLD registry operations. 

        System
documentation allows developers to relay the details of the usTLD registry specifications, design, and interfaces. These documents assist not only in the initial implementation of
the system but also in repairing the system and scaling the system, should the need arise. M&P documentation will provide the usTLD support staff with policies and procedures for support of the usTLD.
These documents will provide clear instructions for responding to requests for help, procedures for handling service interruptions, and workflow processes for all functional areas. M&P documentation,
while invisible to our customers, is a vital step in providing the best possible services to them. User documentation provides registrars with detailed instructions for using the Registrar Tool Kit
and interfacing with the usTLD registry. These documents are vital to successful implementation of the usTLD expanded space. 

Internal Documentation  

        As part of our internal documentation initiative, NeuStar will develop both system documents and M&P documents. In addition, a Quality Assurance (QA) Plan will be
prepared and used throughout the development, test, implementation, and maintenance life cycles to ensure the quality and success of the usTLD registry. The QA Plan will specify all system and user
documents to be produced for the usTLD registry. 

        The
full suite of internal documentation will be prepared and maintained by NeuStar through the project life cycle and will be made available to the DOC or to a designated third party
for audit purposes. Compliance matrices will be prepared to map system requirements to system design and to individual test scenarios. At a minimum, system documentation will include the following: 

	•
	Functional Requirements Specification—Describes all external interfaces and specifies the
functional, data, performance, and security requirements of the usTLD registry.

	•
	System Design Document—Presents a high-level overview of the usTLD registry
that will facilitate analysis, planning, and implementation.

	•
	Detailed Design Document—Presents a more detailed overview of the usTLD registry to
further facilitate analysis, planning, and implementation. 

B.2-37

 

	•
	Testing Documentation—Includes detailed test plans, test scenarios, and test scripts to
ensure that the usTLD meets the requirements outlined in the Functional Requirements Specification.

	•
	Security Policy Document—Outlines all aspects of NeuStar's security policies, including access, Internet and
physical security, and procedures for handling security breaches.

	•
	Disaster Recovery Plan—Details the requisite procedures for full recovery of the usTLD registry. 

        M&P
documents will be developed and maintained to guide NeuStar personnel in the day-to-day operation of the usTLD. These documents will contain all of the usTLD
business rules and workflow processes for all functional areas, as well as internal and external reporting requirements. At a minimum, M&P Documentation will include the following: 

	•
	Help Desk (Tier 1) Methods and Procedures—Provides all methods and procedures for
Help Desk staff in NeuStar's IP Customer Service Center, including phone and e-mail help procedures, trouble-ticketing procedures, and escalation procedures.

	•
	Applications Support (Tier 2) Methods and Procedures—Provides methods and
procedures for the applications support staff, including procedures for resolving trouble tickets as well as expected times for resolution of service-affecting and non-service-affecting
problems.

	•
	Billing and Collections Methods and Procedures—Provides all methods and procedures for
the usTLD billing staff, including procedures for handling registrar calls and resolving billing issues.

	•
	Quality Assurance Methods and Procedures—Provides all methods and procedures for QA
staff, to ensure that all QA requirements are followed by NeuStar's usTLD staff. 

        All
M&P documentation will also include contact information for escalation of issues. 

B.2-38

   External Documentation  

        As part of our external documentation initiative, NeuStar will develop guides for use by registrars in the usTLD expanded space, as well as guidelines for
locality-space delegees. These documents will be available on the usTLD Web site. 

        At
a minimum, user documentation will include the following: 

	•
	RTK Programmer's Guide—Contains detailed information to registrars about using the
Registrar Tool Kit, which will be provided to all usTLD accredited registrars via the private area of the usTLD Web site.

	•
	Connecting to the usTLD—Provides information and detailed guidelines for delegees and registrars for interfacing
with the usTLD registry.

	•
	Guidelines for Locality Delegees—Provides detailed guidelines for delegees and
subdelegees in the locality-based usTLD space, including technical and operational requirements of a locality delegee, as well as procedures for transferring a locality space to a new delegee.

	•
	Frequently Asked Questions—Provides answers to Frequently Asked Questions for both
registrars and locality delegees and subdelegees. An additional FAQ will be available on the public section of the Web site for registrants and the general public.

	•
	Marketing the usTLD—Provides ideas and information to registrars for successfully marketing the usTLD in their
own advertising. 

Training  

        In order to provide the best value in service to registrars, delegees, and registrants, the IP Customer Support Team will develop and distribute extensive
training materials to ensure that all staff have a well-rounded knowledge and understanding of registry and registrar operations and procedures. Although staff will be chosen on the basis
of domain name management experience, it is vital that all members of the usTLD team are trained on usTLD-specific methods and procedures. In this way, NeuStar will ensure extremely high levels of
quality, consistent support services. 

        At
NeuStar, we want our customers to feel comfortable working within our systems; a registrar that does not fully comprehend our procedures and functions may feel uncomfortable working
with us. To avoid these problems and ensure fuller participation in the usTLD registry, training materials will be provided to registrars via the usTLD Web site. These materials will include
presentations and walk-throughs that instruct registrars on use of the RTK software and inform them on how to interface with the usTLD registry. Any questions from registrars not covered
in these training materials and in the user documentation and FAQs will be answered, either by our Integration Assistance team or the Help Desk staff. 

B.2.13    Customer Relationship Management  

        NeuStar will leverage an enterprise-wide CRM program to assist in channel management and outreach for the
usTLD.

        NeuStar
recognizes that the most important element in any service is the customer—whether that customer is the Department of Commerce, a registrar, or an individual
registrant. To this end, NeuStar has codified and implemented throughout its lines of business a thoughtful, thorough, and down-to-earth approach to Customer Relationship
Management (CRM). NeuStar's goal is to ensure customer satisfaction and provide superb service levels to all of the customers with whom we have a relationship. 

B.2-39

 

        Our
CRM vision is to exceed customer satisfaction levels by managing all communications channels, regardless of how customer interactions are initiated, and by observing the needs and
wants of our
customers to better understand them. CRM allows us to seamlessly blend multiple technologies and applications with processes and resources while managing all areas and types of customer interactions,
including sales, marketing, customer service, billing, and technical support. Our CRM program will optimize the value of every customer interaction and experience with usTLD points of contact and
service. NeuStar's commitment to provide this down-to-earth customer support is at the heart of our CRM business practices and procedures. We understand the high expectations
of our customer base for providing usTLD services to the Internet community in the United States—and NeuStar will deliver. 

        Our
CRM program comprises scalable infrastructure, solid processes, and a technological foundation. We will use CRM in combination with our extensive market and customer knowledge to
ensure that we meet our commitment to timely, responsive, and high-quality customer service. 

B.2.14    Reporting  

        NeuStar's Web-based usTLD reporting system will be rich in functionality and have built-in flexibility to provide
reporting information to registrars in numerous ways.

        NeuStar's
usTLD registry will include an automated reporting service that will provide a regular, high-level description of information about the registrar's interaction with
the registry. This report will be e-mailed to designated registry contacts and will be available via the private section of the usTLD Web site. It is important to note that a registrar
will have access only to its own data; a registrar will not have access to any other registrar's private information. The specific information included in these reports will be developed in
consultation with registrars to ensure that they have access to information they deem critical for their business, and different sets of information will be available for different time periods. The
reports will include data such as: 

	•
	Total
number of domains registered since initiating service as a usTLD registrar;

	•
	Total
number of domains registered or cancelled in the previous 7 days, 24 days, or 1 month, as requested by the registrar;

	•
	Total
number of domains transferred from other registrars;

	•
	Total
number of domains transferred to other registrars;

	•
	Remaining
account balance; and

	•
	A
list of domain names that are coming due for re-registration. 

        It
is anticipated that registrars may require additional, specific information from time to time. To make this information available to registrars, NeuStar will develop a
Web-based report query function. This function will allow registrars to obtain information on registration and maintenance activity such as: 

	•
	Numbers
and names of domains registered within any specified period;

	•
	Domain
names transferred to or away from the registrar within a specified period;

	•
	Change
of ownership activity, including exact time and date requests were processed; and

	•
	Re-delegation
activity for domains assigned to a given registrar. 

        These
reports will be developed on an ongoing basis in consultation with registrars and the DOC. 

B.2-40

 

B.2.15    Progress and Quarterly Reporting  

        In order to provide assurances to the COTR of the level of work and progress toward goals of the usTLD, NeuStar will submit progress
reports and quarterly reports, as required by the RFQ.

        Routine
communications with our customer is the best way to ensure that we are making progress toward our goals for the usTLD. In accordance with RFQ Section C.2, NeuStar will
submit monthly progress reports to the COTR and post them on our web site for the first two years of the purchase order, as well as quarterly reports thereafter. These reports will indicate the status
of all major events as well as major work performed during the reporting period, including technical status, accomplishments, and complications experienced in fulfilling SOW requirements. These
reports will also provide performance data related to the operation of the usTLD registry. This data will include, for each reporting period: 

	•
	The
total number of registry transactions;

	•
	The
number of new, transferred, or deleted registrations in the usTLD, including cumulative registrations over time;

	•
	The
number of locality delegees (including subdelegees) and changes in locality delegees;

	•
	The
number of registrars accredited to register names in the expanded usTLD space, including the operational status of those registrars; and

	•
	Any
updates or modifications to the system made by NeuStar. 

B.2.16    Help Desk  

        Our unparalleled experience in providing data administration solutions and services makes NeuStar the only entity truly capable of
providing the technical support and administration services necessary for the successful operation of the usTLD registry.

        Because
of the complex nature of the usTLD space, a high level of Help Desk services will be necessary to support our customers—registrars, delegees (which includes
subdelegees), and locality-based registrants. NeuStar will ensure that these communities have access to the right support from the right people. 

        During
implementation, the usTLD staff will work to establish policies, processes, and procedures that facilitate efficient usTLD operations, including verifying and understanding
registrar interfaces, problem resolution and escalation procedures, service and administration guidelines, and customer record security. Registrars who call the Help Desk will be identified by caller
ID and by a pre-established pass phrase that is different for each registrar. 

        NeuStar's
usTLD Help Desk within the Internet Protocol (IP) Customer Service Center will be the first point of contact for registrars, delegees, and direct registrants for Tier 1
technical and account questions as well as for billing questions. Tier 2 technical support will be available on a 24 × 7 × 365 basis. We will
leverage NeuStar employees trained in Internet Help Desk operations; these employees will be familiar will all usTLD policies, standards, and practices. In order to accommodate multiple U.S. time
zones, the Help Desk will be available from 8:00 a.m. to 8:00 p.m. (EST), Monday through Friday. 

        Help
Desk personnel and other assistance will be available to our customers through a variety of means, including: 

	•
	A
toll-free Help Desk number that provides customer support from 8:00 a.m. to 8:00 p.m. (EST) and technical support on a
24 × 7 × 365 basis;

	•
	E-mail
access for Tier 1 and Tier 2 assistance; 

B.2-41

 

	•
	Extensive
self-help provided via the usTLD registry Web site, including detailed documentation and answers to Frequently Asked Questions;

	•
	Online
instant messaging support;

	•
	Easy-to-use
training materials;

	•
	Discussion
and news lists; and

	•
	Password
access to reports via a secured section of the registry Web site. 

        The
IP Customer Service Center's phone system will use an Interactive Voice Response (IVR) system and Automatic Call Distributor (ACD) to route registrar and direct registrant calls to
the appropriate Help Desk personnel. Customers who call the toll-free number after 8:00 p.m. will have their calls routed to the on-call Second Tier technical support
specialist. NeuStar's highly skilled, customer-oriented Help Desk staff will be responsive to customer needs and will provide the following support services: 

	•
	Assistance
with domain name registration and administration operations,

	•
	Troubleshooting
assistance and problem resolution for first-level technical and integration issues,

	•
	Answers
to questions regarding policies and procedures,

	•
	Assistance
with address charging and payment issues, and

	•
	Explanations
of general guidelines over the phone. 

        Customer
support queries received by phone, by e-mail, or from the usTLD Web site will be logged and tracked through assignment of a trouble ticket. It is the goal of
NeuStar's IP Customer Support Center to close as many trouble tickets as possible on the first call. In the event that an issue cannot be resolved during the initial call, it will be escalated to the
appropriate Second Tier support service. 

        NeuStar's
Second Tier Customer Support staff will act as a second level of escalation in resolving registrars' technical issues. This team will be responsible for providing complex
problem identification and resolution, in-depth system integration assistance, and system troubleshooting. Some of the key functions supported by this team include: 

	•
	Addition
of new registrars into the system;

	•
	Maintenance
of registrar security mechanisms, such as public and private keys and passwords;

	•
	System
service reporting;

	•
	Change
management;

	•
	Mass
database modifications and updates;

	•
	Non-standard
database modifications; and

	•
	Production
and updates of system documentation and integration guides. 

        The
Billing and Collections team will provide support for account statements, reconciliation, and other billing issues. Although the primary point of contact for registrars on these
issues will be the account manager, the Billing and Collections team will be responsible for understanding and meeting the day-to-day billing needs of registrars. The core
responsibilities of the Billing and Collections team will be to: 

	•
	Accept
and process initial registration payments from registrars,

	•
	Assist
registrars in adding funds to their account, 

B.2-42

 

	•
	Audit
and produce monthly statements for registrars,

	•
	Monitor
available funds in registrar accounts, and

	•
	Audit
and reconcile system registration records with accounting system records. 

Help Desk Escalation  

        Help Desk escalation procedures are intended to resolve issues as quickly as possible. An escalated Help Desk call will use the following procedure: 

	1.
	A
customer will contact the usTLD Help Desk via the toll-free number. The Help Desk account representative receiving the call will open a trouble ticket by obtaining the
following information from the customer:

	•
	Name
of customer contact;

	•
	Company
name;

	•
	Point
of Contact, if other than the person opening the trouble ticket;

	•
	Call-back
telephone number;

	•
	E-mail
address; and

	•
	Detailed
description of the problem, including how the problem manifested itself, the time the problem occurred or began, whether or not the symptoms of the problem are
still occurring, and whether or not a root cause analysis and/or resolution/fix are required. The problem description should be in bullet format.

	2.
	The
Help Desk account representative will attempt to resolve the issue and close the trouble ticket. The account representative will use a check sheet developed by second-level support
in diagnosing the problem and attempted problem resolution.

	3.
	If
the account representative cannot immediately resolve the issue, the account representative will escalate the issue to a Tier-2 support specialist. Our escalation policy
defines procedures and time lines for elevating problems either to functional experts or to management for 

B.2-43

 

resolution
if they are not resolved within the escalation policy time limits. The following table is an overview of our escalation policy. 

 NeuStar usTLD Help Desk Escalation Policy  

	Level
 
	 	Description
	 	Escalation Policy
	 	Notification

	I	 	Catastrophic outage affecting overall registry operations	 	Service center manager escalates to usTLD management and Disaster Recovery Team if not resolved in 15 minutes	 	Web portal and e-mail notifications to all registrars and locality delegees within 15 minutes; updates every 30 minutes
	

II	
 	

Systems outage affecting one or two registrar sessions but not the entire system	
 	

Systems engineer escalates to service center manager if not resolved in one hour.	
 	

Web-portal notification to all registrars and locality delegees, including subdelegees; hourly updates
	

III	
 	

Technical questions	
 	

Help Desk account representative escalates to the systems engineer if not resolved in two hours	
 	

Hourly updates to registrar, locality delegee, or registrant via e-mail
	

IV	
 	

Basic questions	
 	

Help Desk account representative escalates to the systems engineer if not resolved within four hours	
 	

Hourly updates to registrar, locality delegee, or registrant via e-mail

The NeuStar Difference  

        Throughout our operations, in both telephony and IP services, NeuStar has demonstrated its ability to deliver and manage complex database services such as those
needed to run a successful top-level domain. More than that, NeuStar has first-hand experience in learning what difficulties can arise from registry services like the usTLD
registry and has proven its capability not only to handle problems efficiently when they arise but also to prevent them from occurring. 

B.2-44

  

B.3    Core Policy Requirements  

        NeuStar will establish sound policies and processes designed to create a collaborative partnership between the usTLD Administrator and the
usTLD community.

	•
	Only NeuStar has the combination of technical and public resource service capabilities required to ensure proper administration of the
usTLD

	•
	NeuStar will develop collaborative partnerships focused on service to the community rather than ownership of a registry

	•
	NeuStar has entered into an agreement with the American Arbitration Association to provide dispute resolution services for the usTLD. This agreement
ensures the availability of a U.S.-based dispute resolution provider for the usTLD

        NeuStar
believes that the role of the usTLD Administrator is similar to that of a trustee of an important public resource. Indeed, NeuStar submits that this should be the role of the
administrator for any ccTLD. Given this role, the usTLD Administrator is responsible for the development of sound policies and procedures designed to ensure that the Administrator's operations serve
the public interest. 

        To
properly serve the public interest in the usTLD context, the usTLD Administrator must: 

	•
	Develop
a robust, secure, shared registry system designed to expand the utility and use of the usTLD. In effect, the system must be designed to bring the usTLD
infrastructure into the global Internet infrastructure to serve as a model of ccTLD "best practices".

	•
	Ensure
the stability and usability of the locality-based usTLD structure, delegations and registrations while describing a path forward for enhancements and new uses of the
locality-based space.

	•
	Develop
open policies and procedures with a high degree of responsiveness and accountability to the usTLD community. In particular, members of the usTLD community must have
readily accessible means to discuss, suggest, and promote modified or supplemental policies, services, and procedures in the usTLD, as well as address complaints or other issues raised in the context
of the operation of the domain space. 

        In
its development and implementation of policies and procedures for the usTLD, the new usTLD administrator must avoid (i) taking a minimalist approach by describing certain
public interest aspirations and guidelines without establishing sufficient processes to back them up, or (ii) adopting very heavy-handed regulation designed to force users and services
providers of the space into a single vision of the usTLD. The first approach fails to establish a sufficient framework to promote certainty and value for users of the space, and the second approach
establishes rigid structures lacking the flexibility to deal with changing business, social and policy environments. Thus, both approaches will fail, causing the ultimate failure of the enhanced
usTLD. NeuStar's approach will avoid the pitfalls of under- or over-structuring the TLD space. 

        NeuStar
will establish a number of core policies designed to address certain issues specified in the RFQ, as well as issues generally required for the transition and start-up
of an enhanced usTLD. The basic polices that NeuStar will implement include: 

	•
	The
US Nexus Requirement to ensure that the usTLD serves the US Internet community;

	•
	Adoption
of Uniform Dispute Resolution Procedures modeled after ICANN models to address intellectual property protection and similar concerns;

	•
	Adoption
of the "Sunrise" policy to allow trademark holders to protect their valuable names; 

B.3-1

 

	•
	Adoption
of ICANN and Governmental Advisory Committee policies on open ccTLDs to bring the usTLD into the global ccTLD community;

	•
	Whois
policy designed to enhance privacy and accountability in the whois database;

	•
	Review
and oversight of the locality-based space within the usTLD;

	•
	Other
implementation policies to support the development of the usTLD. 

        The
majority of NeuStar's policy activity will not be prescriptive in nature. Rather, NeuStar submits that the most effective policy structure for the usTLD will be one of collaborative
partnership. NeuStar will establish effective and flexible processes responsive to the usTLD community and the public interest. In particular, NeuStar will develop a usTLD Policy Council (Council) as
an advisory body for usTLD policy operations. This body will interface with the public and provide an independent forum and mechanism for future development of the usTLD. 

        Initially,
the Council will be responsible for the modernization and enhancement of the locality-based usTLD space. In the future, however, the Council may be called upon to address such
issues as new hierarchical space within the TLD to address recognized public needs, the enhancement of privacy protections for domain registrants, or the enforcement of the accreditation agreement
with registrars. In any event, the Council will be designed to work effectively with the various usTLD constituencies, federal, state and local governments, and ICANN, to ensure that the usTLD
Administrator's role as a trustee is fulfilled. 

        NeuStar
is uniquely qualified to assume the complex policy role needed to properly serve the usTLD community. Indeed, the kinds of goals described are entirely consistent with NeuStar's
proven record in its roles as the North American Numbering Plan Administrator and the Local Number Portability
Administrator. Much more is needed in the administration of the usTLD than a strong technical solution. Absent the skills developed through the administration of public resources, it is unlikely that
an entity will have the expertise to properly manage the usTLD envisioned in the RFQ and the capability to support the principles established for ccTLDs by the Governmental Advisory Committee of
ICANN. 

        As
demonstrated through the proposed development of the Council, a key aspect of NeuStar's plan to meet the goals discussed above is its commitment to ensuring that the usTLD
Administrator operates as a trusted neutral third-party in the provision of secure, stable and fair administration services for the critical public resource, the usTLD space. As is clearly outlined
above, despite the views of many that a ccTLD is simply another commercial venture, the usTLD Administrator cannot act simply as a commercially motivated operator. Therefore, in performing its duties
for the usTLD the Administrator must hold itself to a code of conduct exceeding traditional commercial standards. 

        Access
to DNS services is critical to entities wishing to participate in the DNS industry specifically and in Internet business generally. Domain names are the means by which
governments, businesses, and consumers gain access to, navigate, and reap the benefits of the worldwide web. These benefits cannot be fully realized, however, unless policies are in place to ensure
that DNS resources in the usTLD are administered in a fair, equitable and efficient manner that makes them available to all parties desiring to provide DNS services. In order to meet this goal,
NeuStar submits that the services of the Administrator must be administered to meet the following objectives: 

	•
	Facilitate
the provision of Internet services and use of the usTLD by making DNS resources available on an efficient, timely basis to registrars and registrants;

	•
	Not
unduly favor or disadvantage any particular industry segment, public organization, government agency, or group of consumers; 

B.3-2

 

	•
	Ensure
that interests of all usTLD constituents are considered and addressed fairly and efficiently. 

        To
ensure that NeuStar meets these objectives, it commits to strict adherence to the following usTLD Administrator Code of Conduct: 

 
 

usTLD ADMINISTRATOR CODE OF CONDUCT    
    

        To ensure the provision of neutral usTLD administrative services, NeuStar will comply with this Code of Conduct.

	1.
	NeuStar will conduct periodic reviews of its policy and operation structures to ensure continuing operation of the usTLD in the public
interest.

	2.
	NeuStar will ensure that improvements and enhancements developed for the usTLD will benefit both the expanded and locality-based spaces of the
usTLD.

	3.
	NeuStar will not, and will require that its subcontractors do not, directly or indirectly, improperly show preference or provide special consideration to any
usTLD Accredited Registrar, Delegated Manager or usTLD user versus any other usTLD Accredited Registrar, Delegated Manager, or usTLD user.

	4.
	All usTLD Accredited Registrars, Delegated Managers, and usTLD users shall have equal access to Administration Services provided by
NeuStar.

	5.
	NeuStar will ensure that no user data or proprietary information from any usTLD Accredited Registrar is disclosed to its affiliates, subsidiaries, or other
related entities, or to other usTLD Accredited Registrars, except as necessary for usTLD Administrator management and operations.

	6.
	Registry Operator will not disclose Confidential information about its Registry Services to employees of any usTLD Accredited Registrar, Delegated Manager, or
usTLD user with the intent of putting them at an advantage in obtaining usTLD Administration Services from NeuStar, except as necessary for usTLD Administrator management and
operations.

	7.
	NeuStar will conduct internal neutrality reviews on a regular basis. In addition, NeuStar and DOC may mutually agree on an independent party to conduct a
neutrality review of NeuStar, ensuring that NeuStar and its owners comply with all the provisions of this Code of Conduct. The neutrality review may be conducted as often as once per year. NeuStar
will provide the analyst with reasonable access to information and records appropriate to complete the review. The results of the review will be provided to DOC and shall be deemed to be confidential
and proprietary information of NeuStar and its owners.

B.3.1    US Nexus Requirement Implementation  

        As an important public resource, the usTLD must be managed in a manner designed to serve the United States Internet community. Therefore
NeuStar will implement a US Nexus Requirement.

        Recognizing
that the usTLD is an important public resource that must be managed for the benefit of the United States, its citizens, and its residents, NeuStar will implement, in addition
to the requirement set forth in RFC 1480 that usTLD domain name registrations be hosted on computers located within the United States, the following Nexus Requirement in both locality-based usTLD
structure and the expanded usTLD space: Registrants in the usTLD must be either: 

	1.
	A
natural person (i) who is a citizen or permanent resident of the United States of America or any of its possessions or territories, or (ii) whose primary place of
domicile is in the United States of America or any of its possessions, or 

B.3-3

 

	2.
	An
entity or organization that is (i) incorporated within one of the fifty (50) U.S. states, the District of Columbia, or any of the United States possessions or
territories or (ii) organized or otherwise constituted under the laws of a state of the United States of America, the District of Columbia or any of its possessions or territories, or

	3.
	An
entity or organization (including a federal, state, or local government of the United States, or a political subdivision thereof) that has a bona fide presence in the United States. 

        Whether
a prospective registrant has a "bona fide presence in the United States" will be determined on a case-by-case basis in light of all relevant facts and
circumstances at the time of application for a usTLD domain name. This requirement is intended to ensure that only those individuals or organizations that have a substantive connection to the United
States are permitted to register for usTLD domain names. 

        Factors
that should be considered in determining whether an entity or organization has a bona fide presence in the United States shall include, without limitation, whether such
prospective usTLD domain name registrant: 

	•
	Regularly
performs activities within the United States related to the purposes for which the entity or organization is constituted (e.g., selling goods or providing services
to customers, conducting regular training activities, attending conferences), provided such activities are not conducted solely or primarily to permit it to register for a usTLD domain name;

	•
	Maintains
an office or other facility in the United States for a business, noncommercial, educational, or governmental purpose and not solely or primarily to permit it to
register for a usTLD domain name; or

	•
	Derives
a material portion of its revenues or net income from sales to purchasers located in the United States. 

        For
purposes of this definition, the terms United States and United States of America shall include all U.S. territories and possessions. 

        It
shall be a continuing requirement that all usTLD domain name registrants maintain the US Nexus Requirement. 

        The
Nexus Requirement will be enforced through an initial screening of the contact information provided by the registrant, as well as a challenge process permitted through the Nexus
Dispute Policy
discussed below. The screening by NeuStar will verify that selected fields, within the contact information provided, on their face, meet the Nexus Requirement and that the registrant has certified
compliance with the requirement, as well as certified that the nameservers identified are located within the United States. In the event that the
contact information provided does not meet the above requirement, the name requested will be placed on hold within the registry and the registrant will be given an opportunity to correct any mistake
or demonstrate compliance with the Nexus requirement. If no action is taken by the registrant within the 30-day period, the registration will be cancelled and the name will be returned to
available status. If, on the other hand, the registrant is able to demonstrate compliance with the requirement, the name will be registered. 

Nexus Dispute Policy  

        Although the Nexus Requirement will initially be enforced through a usTLD Registrar's screening of the contact information provided by the registrant, and the
registrant will certify that it meets at least one of the Nexus Requirements set forth above, NeuStar understands that disputes may arise as to the authenticity, veracity, or accuracy of the
registrant's Nexus certification. Therefore, NeuStar, as administrator of the usTLD has devised a Nexus Dispute Policy (NDP) which will be administered 

B.3-4

 

solely
by the usTLD Administrator, or its designated representative. The NDP will provide interested parties with an opportunity to challenge a registration not complying with the Nexus Requirement. 

        In
the event that a third party wishes to challenge the authenticity or veracity of a usTLD registrant's United States Nexus, that party may submit a "Nexus Challenge" to the usTLD
Administrator or its authorized representative. The challenger must submit a written statement to the usTLD Administrator via first class mail alleging in specificity evidence to support its
allegation that the registrant fails to meet any of the Nexus Requirements set forth above. 

        Once
a challenge is received by the usTLD Administrator the domain name shall be "locked" by the usTLD Administrator until the matter is resolved. While in a "locked" position, the
registrant may not (i) change any of the contact information for that particular domain name or (ii) transfer the domain name to any third party. 

        In
the event that the usTLD Administrator finds that the challenger has established a prima facie case that the registrant has not met any of the Nexus Requirements, the usTLD
Administrator shall issue a letter to the registrant to submit evidence of compliance with the Nexus Requirements ("Letter"). The registrant shall have a period of thirty (30) days from the
date of the Letter to submit evidence of compliance. If, within the thirty (30) days, the registrant submits evidence establishing any of the Nexus Requirements, the registrant shall be
permitted to keep the domain name. 

        If,
however, the registrant either (i) does not respond within the thirty days, or (ii) is unable to demonstrate through documentary evidence that it met any of the Nexus
Requirements prior to the date the NDP was invoked, the usTLD Administrator shall issue a finding that the registrant has failed to meet the Nexus Requirements. Upon such a finding, the registrant
shall be given a total of thirty (30) days to cure the US Nexus deficiency. If the registrant is able to demonstrate within (30) days that it has cured such deficiency, the registrant
shall be allowed to keep the domain name. If the registrant either (i) does not respond within the thirty (30) days, or (ii) is unable to proffer evidence demonstrating compliance
with the Nexus Requirements, the domain name registration shall be deleted from the registry database and the domain name will be placed into the list of available domain names. This process
represents the exclusive remedy for an NDP challenger. 

        NeuStar
reserves the right to modify this NDP at any time with the permission of COTR. NeuStar will post its revised NDP on its Website at least thirty (30) calendar days before
it becomes effective. 

B.3.2    Open ccTLD Policies Adoption  

        NeuStar intends to establish the usTLD as a model ccTLD in the global Internet community. NeuStar fully supports, and will abide by, the
open ccTLD policies established by ICANN.

        NeuStar
believes that the usTLD should be developed to serve as the model ccTLD in the global Internet community. In particular, it supports the significant work done by ICANN and the
Internet community in developing and enhancing the Internet in the public interest. Therefore, in accordance with the DOC's requirements, from both a technical and a policy standpoint, NeuStar will
develop the usTLD pursuant to developing "best practices" for open ccTLDs, as established by ICANN. Further, we will work with ICANN in the development and enhancement of new policies as they relate
to the usTLD and the Internet at large. 

        An
example of the types of open ccTLD policies supported by NeuStar is the ccTLD Constituency of the ICANN DNSO's document "Best Practice Guidelines for ccTLD Managers." Open, consensus-
based policies such as these provide a sound basis for operating public resource services. Indeed, many of the principles contained in the "Best Practices" document reflect the basic themes discussed
in this 

B.3-5

 

proposal.
For example, the document establishes, among other things, the following obligations of ccTLD Managers: 

The
primary duty of the ccTLD Manager is one of public service—to manage and operate the ccTLD Registry in the interest of and in consultation with the local Internet community, mindful of
the interests of the global Internet community. 

A
ccTLD Manager is a trustee for the delegated domain and has a duty to serve the community it represents as well as the global Internet community. Concerns about "rights" and "ownership" of
top-level domains are inappropriate. It is appropriate to be concerned about "responsibilities" and "service" to the community. The ccTLD manager should be judged on his or her performance
and the extent to which it satisfies the needs of the local and global Internet communities. 

        NeuStar
considers it a basic principle of usTLD administration that the administrator is a trustee of a valuable and important public resource. Thus, NeuStar agrees with and will abide
by ICANN's open ccTLD policies, subject to any requirements of United States law and unless otherwise directed by the Contracting Officer. 

B.3.3    usTLD Dispute Policies and Sunrise Policy/ Implementation  

        NeuStar understands that the success of an expanded and enhanced usTLD requires the development of a set of policies and dispute resolution processes that are
simple and effective and provide a level of accountability for the users of the usTLD. Therefore, NeuStar has established (i) the usTLD Dispute Resolution Policy (usDRP) that is modeled after
ICANN's Uniform Dispute Resolution Policy, and (ii) a Nexus Dispute Policy; a dispute mechanism to handle disputes relating to the usTLD Nexus Requirements set forth in Section B.3.1
above. 

B.3.3.1    usTLD Dispute Resolution Policy  

        The usDRP combines the globally accepted Uniform Dispute Resolution Policy ("UDRP") for the gTLDs with improvements developed in conjunction with the World
Intellectual Property Organization ("WIPO") for the administration of domain name disputes in the .BIZ top-level domain. Through its ongoing relationship with WIPO in its development of
the .BIZ dispute resolution services, NeuStar is uniquely qualified to apply its knowledge and expertise in the development of domain name dispute resolution policies for the usTLD. 

        Although
an applicant for the usTLD administrator might simply adopt the UDRP as in its current form, NeuStar believes that this would be unwise given the number of flaws that two years
of experience with the policy has demonstrated. 

        The
UDRP was adopted in late-1999 by ICANN as its first, and to date, its only global consensus-based policy, in response to the WIPO's recommendation to establish a uniform
dispute resolution policy for "cases of bad faith, abusive registration of domain names that violate trademark rights ("cybersquatting' in popular terminology)." The Management
of Internet Names and Addresses: Intellectual Property Issues, Final Report of the WIPO Internet Domain Name Process, See
http://wipo2.wipo.int/process1/report/finalreport.html. 

        Through
its numerous consultations with WIPO during the formulation of the .BIZ dispute resolution policies, NeuStar uncovered several flaws in the UDRP process that not only led to the
issuance of inconsistent determinations by panelists but also unnecessary administrative burdens on the UDRP dispute providers. For example, the current UDRP requires that a trademark owner
demonstrate that a domain name registrant both registered and used the domain name in bad faith. This
requirement of both "registration and use" of domain names in bad faith has led UDRP panelists to find in favor of cybersquatters who have warehoused domain names that are identical or confusingly
similar to famous trademarks, but have not "used" the domain names in bad faith (i.e., the domain 

B.3-6

 

names
do not resolve to actual web pages). In other words, panelists have found that although a trademark owner has demonstrated that a cybersquatter has registered a number of domain names that
correspond to famous trademarks, because the domain name in question did not actually resolve to a web site, there was no "use" in bad faith. This result was clearly not intended by the original
drafters of the UDRP. 

        In
order to address this problem, NeuStar had modified this specific language in its usDRP to allow panelists to find in favor of the trademark owner if the trademark owner can establish
that the domain name was either registered or used in bad faith. This change was met with high praise by
both WIPO and the Intellectual Property Constituency of ICANN when it was adopted in .BIZ's Start-up Trademark Opposition Policy. 

        A
second example of a flaw in the UDRP which has led to inconsistent decisions is a paragraph dealing with "evidence of registration or use in bad faith" (Section 4(b) of the
Policy). This paragraph states that bad faith can be established if a Panel finds that a registrant registered the domain name in order to prevent the owner of the trademark or service mark from
reflecting the mark in a corresponding name, provided that the registrant has engaged in a pattern of such conduct. This has led to several decisions
which have been in favor of cybersquatters who although it was shown that they registered the one domain name in question to intentionally prevent the trademark owner from registering the domain name,
it could not be shown that there was a "pattern of such conduct." In other words, under the UDRP, the explicit wording implies that unless the cybersquatter has prevented other trademark owners from
registering their corresponding domain names, one instance of such activity does not amount to bad faith. This too is clearly inconsistent with the original drafters intent behind that particular
paragraph. In order to address this problem, NeuStar adopted WIPO's suggestion to modify this specific language in its usDRP to allow panelists to find in favor of the trademark owner if the trademark
owner can establish that the registrant registered the domain name
in question in order to prevent the trademark owner from reflecting its trademark in a corresponding domain name, without showing a "pattern of such conduct." 

        A
draft of both the usDRP and the Rules for the usDRP are provided at the end of this section. 

Implementation  

        In order to ensure that NeuStar's improved dispute resolution mechanism, the usDRP, is enforced by only the most qualified dispute panelists familiar with all
facets United States law, NeuStar has entered into an agreement with the American Arbitration Association ("AAA"). The AAA, the premier alternative dispute resolution provider in the United Sates, has
flourished for nearly 75 years by demonstrating an unparalleled commitment to progressive leadership in alternative dispute resolution. 

        While
many of the more than 140,000 cases administered by the American Arbitration Association in 1999 were resolved through mediation or arbitration, less formal methods of dispute
resolution—such as fact-finding, mini-trial, and partnering—are clearly coming into wider use. To serve dispute resolution needs, the AAA provides a
forum for the hearing of disputes through 37 offices nationwide, tested rules and procedures that have broad acceptance, and a roster of nearly 12,000 impartial experts to hear and resolve cases.
Moreover, in addition to its significant dispute resolution experience, the AAA brings a fresh perspective to the Internet dispute resolution process. 

        In
addition, if awarded the usTLD registry, NeuStar will solicit the expertise of other dispute resolution providers based in the United States in order to provide usTLD domain name
registrants and intellectual property owners around the United States with the most qualified and knowledgeable usDRP panelists. 

B.3-7

 

B.3.3.2    Sunrise Policy and Implementation  

        NeuStar will implement a Sunrise policy for owners of United States trademark applications and registrations which validates whether the claimed applications or
registrations actually exist within the United States Patent and Trademark Office database, thus eliminating any need for costly and time-consuming Sunrise dispute resolution mechanism. 

        Since
well before the formation of ICANN, intellectual property owners have debated how best to protect their trademarks and service marks ("Trademarks") on the Internet. NeuStar
proposes to implement an enhanced "Sunrise" policy that not only balances the intellectual property rights of registered trademark owners, but also provides the same level of protection to those
Trademark owners who have submitted trademark applications to the United States Patent and Trademark Office (PTO). In addition, unlike any other "Sunrise" plan implemented or even proposed, NeuStar
will validate the authenticity of Trademark applications and registrations with the PTO through a unique and proprietary technological interface developed to ensure the integrity of the "Sunrise"
process. Following is an overview of the process proposed for the implementation of the Sunrise period as in Shown in Exhibit B.3-1. 

        The
Sunrise period will commence thirty (30) days prior to the general activation of the expanded usTLD space. During the Sunrise period, owners of trademarks and service marks
(Trademarks), as well as applicants for such marks, will be able to register their marks as domain names in the new expanded usTLD space. 

        Any
owner of an existing live Trademark registered on the Principal Register of the PTO, or an existing live application filed for registration with the PTO, will be eligible to seek to
register the mark as a domain name during the Sunrise period provided that (i) the Trademark registration for that mark was issued prior to the commencement date of the Sunrise Period, or
(ii) the application was filed with the PTO no later than July 27, 2001. In addition: 

	•
	Only
characters in the range A to Z, 0 to 9, and hyphens are allowed

	•
	The
maximum length is 63 characters (exclusive of the usTLD portion)

	•
	Domain
requests must be for ASCII characters identical to the textual or word elements of the mark only. However, hyphens may be used between spaces within a registered mark
or application; names cannot begin or end with a hyphen.

	•
	Sunrise
registrations will only be accepted for terms of at least five years and will be processed after registration fees are paid in full. 

        The
registration form for the Sunrise period will include all normal registrant information along with additional details of the registered mark under which the registration is being
made. The information required will include: 

	•
	The
name, address, telephone number, facsimile number and e-mail address of the domain name registrant, administrative contact, technical contact, and billing
contact

	•
	The
domain name

	•
	Name
servers

	•
	IP
addresses

	•
	The
exact Trademark

	•
	The
date of registration of, or filing of an application for the Trademark

	•
	The
registration or application number of the Trademark, whichever is applicable 

B.3-8

 

	•
	The
name of the current owner of the registered mark

	•
	Additional
optional data elements for directory services

	•
	In
addition, the domain name registrant will be required to affirmatively certify that it has met the usTLD Nexus requirement 

        Along
with these fields, the normal registration agreement will also contain a provision to the effect that: 

        The
registrar and the usTLD Administrator shall have no liability for administering the Sunrise program so long as the registrar acts in accordance with the policies set forth in the
Sunrise proposal. 

[Exhibit B.3-1:
Graphic Design] 

Phase 1—Announcement  

        Information regarding the enhanced Sunrise program will be broadly communicated to the general public at least sixty (60) days prior to the activation date
of the expanded usTLD space. The communication will be in the form of an announcement on the NeuStar web site as well as a general press release. During the announcement period, a list of all
accredited registrars participating in the Sunrise program will be posted on the NeuStar web site along with a link to the registrars' web sites. 

Phase 2—Sunrise Registration  

        In seeking to create the most neutral and impartial allocation of domain names during the Sunrise Period, NeuStar will use the same basic
procedure as set forth for the Land Rush Period, Section J with a few important modifications specific to the Sunrise process.

        Step 1: Submission of registration lists—Each accredited registrar will provide a list of domain names and Sunrise
registration details. There will be no minimum or maximum limit for the lists. The registration files will be submitted via a secure transport mechanism before a specified closing time for first
submissions. Registration lists cannot be modified until the first batch is processed and completed. 

        Step 2: Randomization of registrar submitted lists—The lists submitted by each
registrar will be individually randomized and processed to eliminate duplicate Sunrise domain name registration requests (e.g., four different parties request unclesam.us; one of the requests will be
selected and the others deleted from the list). 

        Step 3: Combination and randomization of registrar lists—After initial
processing, the entire set of registrar lists will be combined into a single processing file and randomized. 

        Step 4: Processing of randomized list—Once the registration system is
activated, a domain name will be randomly selected from the processing list. 

        Step 5: Validation of Trademark—NeuStar will not finalize the registration of
a domain name under the Sunrise policy until the Trademark registration or application has been verified by the registry or its designated partner or agent. In order to verify the Trademark
Registration or Application after the domain name is selected in Step 4 above, NeuStar will use its unique proprietary technology to query the PTO database to ensure that (1) the SLD portion of
the domain name selected is an exact match of the claimed Trademark, (2) the Trademark has actually in fact been either applied for or registered with the PTO, and (3) the domain name
applicant is in fact recognized in the PTO trademark database as the current owner or assignee of the Trademark. If a domain name meets all these qualifications, it is registered and entered into the
domain name database. 

B.3-9

 

        If
a domain name is either (i) unavailable, or (2) is rejected as not qualifying under the Sunrise policy, then another name is chosen at random from the list until one of
the following occurs: 

	•
	A
successful registration is complete

	•
	The
registrar has no more available names on its list 

        This
process repeats until the entire list has been processed. When applicants submit registrations during the Sunrise period, they will be required to enter all relevant details for
their mark's
registration. The interface will support these extra fields and details will be published via the Whois database. If parties other than the registrant wish to challenge the validity of an application,
they will then be able to use the trademark details to verify authenticity with the US Patent and Trademark Office. 

        Step 6: Results—At the end of the list processing, the results of Sunrise registrations are returned to the registrar. 

        Step 7: At the conclusion of the Sunrise period, no further Sunrise registrations will be accepted and the registry will commence the Land
Rush registration process described in Section J. 

        NOTE: Sunrise registrations will only be accepted for terms of at least five (5) years and will be processed after registration
fees are paid in full. 

Sunrise Dispute Resolution  

        Because of NeuStar's unique and innovative approach to the Sunrise Policy coupled with actual validation of Trademarks with the PTO, NeuStar is proud to state
that there is no need for a specific dispute resolution mechanism related to Sunrise registrations other than what is provided under the Nexus Dispute Policy and the usDRP. 

B.3.4    GAC Principles  

        NeuStar fully supports and will abide by the principles established by the Government Advisory Council.

        As
previously stated, NeuStar believes that the usTLD should be developed to serve as the model ccTLD in the global Internet community. From both a technical and a policy standpoint,
therefore, NeuStar will develop the usTLD pursuant to developing "best practices" for ccTLDs. One such set of principles is set forth in the ICANN Government Advisory Council's "Principles for the
Delegation and Management of Country Code Top Level Domains." The document's preamble states that: 

[T]he
manager of a ccTLD performs a public service on behalf of the relevant local community and as such the designated manager has a duty to serve this community. The
designated manager also has a responsibility to the global Internet community. By 'global Internet
community' we do not mean any specific legal or international entity, but rather we interpret the term to refer to all of those who are affected by, now or in the future, the operation of the relevant
TLD, because such operation may impinge on more than one jurisdiction and affect the interests of individuals and entities from both within the relevant country or territory and elsewhere. 

        This
statement describes very clearly the basic premise pursuant to which NeuStar approaches the administration of the usTLD. Thus, NeuStar will abide by these principles, unless
inconsistent with U.S. law or regulation. 

B.3.5    Additional, Alternative or Supplemental Policies  

        NeuStar will develop and implement fair, flexible, and effective policies and procedures designed to ensure operation of the usTLD in the
public interest.

B.3-10

 

        NeuStar
believes that the usTLD Administrator, while establishing sound and fair initial policies for the usTLD, should limit the number and scope of policies established without the
benefit of usTLD community participation. Therefore, the additional policies included in this section are those additional matters that must be addressed prior to launch to ensure a proper framework
for enhancing and improving the usTLD in the manner set forth in the RFQ. 

        The
additional policies needed for the transition to a new usTLD Administrator are: 

	•
	Outreach
Plan and Policy

	•
	Data
Rights and Use

	•
	Whois
Policy

	•
	Reserved
Names Policy 

        Each
of these policies is discussed in turn below. 

Outreach Plan and Policy Council  

        As is stated throughout this proposal, NeuStar considers the usTLD an important public resource that must be administered to serve the public interest. It cannot
be allowed to become captured by any single industry, constituency, or interest group, but instead, must carefully balance the needs of all community stakeholders. Thus, the usTLD Administrator must
act as a trustee and facilitate consensus to ensure that all policy and development efforts are not only conducted in an open manner, but are effective. 

        In
developing an appropriate and effective outreach plan, the new usTLD Administrator will have to address a number of important issues. Some of the tasks that the administrator must
complete: 

	•
	Develop
an outreach plan that ensures appropriate representation for all constituencies within the usTLD community;

	•
	Design
outreach mechanisms that are effective for each constituency involved;

	•
	Develop
a thorough understanding of the issues relevant to the space and the various constituencies; and

	•
	Ensure
continuity of efforts and responsiveness. 

        NeuStar
believes that an administrator must conduct some level of outreach in order properly to develop its outreach plan. NeuStar already has started its outreach in preparation for
this plan. In
addition to the Public Awareness Plan work discussed in Section B.2.8, NeuStar has contacted a number of identified representatives of various constituencies in the usTLD community. Entities
with which NeuStar has discussed the usTLD include the Media Access Project, the American Library Association, the Benton Foundation, the US Chamber of Commerce, the Center for Democracy and
Technology, the National Indian Telecommunications Institute, education representatives, existing delegated managers, governmental representatives, and commercial entities. From these activities we
have identified a number of principal concerns to consider, including: 

	•
	The
operation of the usTLD must serve the public;

	•
	Commercial
interests must not dominate the usTLD;

	•
	The
administrator must develop effective outreach mechanisms for representation of user interests;

	•
	The
administrator must protect rights and ability of the existing users to maintain their use of the locality-based space; 

B.3-11

  

	•
	The
administrator must centralize much of the operation of the usTLD and develop better mechanisms for accountability to users and technical maintenance of the system;

	•
	The
administrator must improve administration and enhance the functionality of the usTLD;

	•
	All
innovation in the space must serve all constituencies within the usTLD, not just commercial interests; and

	•
	The
usTLD must operate in a highly stable manner. 

        In
addition to concerns and issues regarding the administration of the usTLD generally, a number of parties discussed possible structures for the operation of the usTLD and/or the
related policy function. 

        The
first of the proposed structures was that the registry operator should be a not-for-profit company. This approach was driven by the concern that a corporation
would be incented entirely by profit and not adequately serve the public interest. NeuStar submits, however, that a not-for-profit corporation would not be in the position to
ensure ongoing stability of the usTLD, nor would it have sufficient resources to allow it to be sufficiently innovative and enabling of innovation in the space. As a result, the use of the usTLD
likely would remain limited in comparison with the gTLDs and many other ccTLDs in the world. A commercial business, on the other hand, will commit the necessary resources to make the usTLD highly
successful. Moreover, the usTLD Administrator will be subject to the oversight of the DOC, and to the possibility of losing the contract if its services do not properly address public concerns.
Therefore, a for-profit model offers a superior approach for a successful usTLD. 

        Another
model proposed posits a separate not-for-profit corporation that would serve as the binding policy arm of the usTLD Administrator, and would require
definitive subcontract agreement as a condition of the DOC award. The administrator would fully fund the
operations of the policy corporation and could reject proposed policy measures only through a binding arbitration. This approach raises numerous concerns including: 

	•
	The
representativeness of the not-for-profit corporation;

	•
	The
appropriateness of delegating a policy level obligation;

	•
	The
lack of finality in a DOC award process subject to the formation of a policy corporation and reaching a definitive agreement as a condition of award;

	•
	The
role of the DOC and ICANN with respect to the formation of usTLD and the potentially inefficient duplication of policy efforts; and

	•
	The
lack of equity inherent in an approach which would make binding a recommendation from the not-for-profit corporation but would treat differently
recommendations from entities that were not associated with or participating in the not-for-profit policy entity. 

        NeuStar
will implement a policy structure that will address the concerns raised above and ensure independent, open, and unbiased policymaking for the usTLD, but will avoid the concerns
raised by these structures. Of course, to the extent that the groups behind these other proposal seek to work with NeuStar after award, or if the DOC determines that one of these approaches to be
preferable, NeuStar will explore effective ways of incorporating structure and concepts and addressing policy issues with participation of these important public entities. 

B.3-12

 

The usTLD Policy Council  

        The centerpiece of NeuStar's outreach and policy plan will be the usTLD Policy Council. The Council will be an advisory body facilitated by NeuStar to ensure
representative and unbiased policymaking. The Council's initial primary duties will include: 

	•
	Formation
of a mechanism for electing a full council;

	•
	Early
selection of a full council;

	•
	Develop
and implement basic outreach functions for the usTLD;

	•
	Oversight
of the locality-based policies and compliance of delegated managers;

	•
	Development
and implementation of mechanisms for addressing complaints regarding operation of the usTLD and appeals from decisions of the usTLD Administrator, as well as a
mechanism for addressing claims of non-compliance with the US Nexus Requirement;

	•
	The
facilitation of policy development forums at least annually;

	•
	The
facilitation of discussion groups, list-serves, and other electronic communications tools;

	•
	Development
and implementation of mechanisms for suggesting, discussing, and recommending to the usTLD Administrator new, modified or supplemental policies or procedures for
the usTLD;

	•
	Periodic
review of the policies and procedures of the usTLD for continuing relevance and effectiveness, and recommending necessary modifications, additions, or deletions.

	•
	Implementation
of a mechanism for identification of new sponsored categories of registration or registration services for identified spaces with a material impact on
important policy issues or concerns. 

        The
functions listed above will be facilitated by the usTLD Administrator as part of its public interest duties to the usTLD community. The Council will operate in a fashion independent
of the usTLD Administrator to ensure open and unbiased decision-making. The usTLD must, however, fully execute its DOC delegated obligations and, therefore, will participate on the council as a voting
member, as well as work with the Council members to develop an annual Council operating budget. 

        Drawing
on the significant progress that has been made within the ICANN in developing open and transparent consensus policy procedures, NeuStar, has modeled the aforementioned Council
procedures after those of ICANN. We believe that not only does this approach provide the usTLD Administrator with a solid process for policy development, it provides significant comfort to the DOC in
selecting such a structure given that it has already approved this procedural structure for ICANN, thus all parties interested in the development of usTLD policy will have a familiar mechanism to
which to turn. 

        Thus,
NeuStar will accept the policy recommendations of the usTLD Policy Council if NeuStar finds that the recommended policy (1) furthers the purposes of, and is in the best
interest of the usTLD; and (2) was arrived at through fair and open processes. If NeuStar declines to accept any recommendation of the Council, it shall return the recommendation to the Council
for further consideration, along with a statement of the reasons it declines to accept the recommendation. If, after reasonable efforts, NeuStar does not receive a recommendation from the Council that
it finds meets the standards above, NeuStar may initiate, amend or modify and then approve a specific policy recommendation. Nothing in this paragraph, however, is intended to limit the powers of the
NeuStar to act on matters not within the scope of primary responsibility of the Council or to take actions that the NeuStar finds are necessary or appropriate to further the purposes of the usTLD. 

B.3-13

 

        A
critical aspect of ensuring the effectiveness and representativeness of the Council will be its selection. To facilitate its early start of operations, NeuStar will select, in
consultation with appropriate stakeholders, an initial set of council members. The first obligation of the initial council will be the implementation of a mechanism for nomination and election of the
entire board. They also will be
responsible for determining the details of board appointment, such as term and constituencies represented (the initial council members receive one-year terms). This approach will result in
a neutral, expert board to address the ongoing policy development for the usTLD. 

        NeuStar
expects that the Council will consist of 9 to 12 members each representing a different constituency or group of stakeholders in the usTLD community. The size of the Council could
be expanded in the future as necessary. Although the initial board will establish the process for determining the complete list of constituencies, NeuStar believes that a first list must include: 

	•
	DOC
Appointee,

	•
	usTLD
Administrator,

	•
	Delegated
managers,

	•
	Existing
registrants,

	•
	Government
(local and state),

	•
	Commercial
entities,

	•
	Public
interest advocates, and

	•
	Internet
technical representatives (example, member of IAB or IESG). 

        Some
or all of the potential representation issues can be dealt with by reserving places for organizations that themselves are broadly representative of user and public interests (e.g.,
National Governors Association, the National League of Cities, the American Library Association, consumer advocacy groups, to name only a few). 

Outreach Activities  

        As discussed above, the Council will be a focal point for many of the outreach activities of the usTLD. In that role, the Council will be responsible for
developing and enhancing the primary policy outreach activities of the usTLD Administrator. However, a number of activities already are planned by NeuStar should it be awarded administration of the
usTLD. 

	•
	NeuStar
will hold an initial usTLD Administrator's Forum to introduce the usTLD community to the new administrator and begin the ongoing dialog on usTLD policy and services.
This forum will be held live and will make available means for teleconference/videoconference and online participation.

	•
	NeuStar
will establish on its usTLD website comprehensive information about the usTLD and how it will be operated, as well as open chat and e-mail forums to
allow early discussion of users' concerns, desires and suggestions.

	•
	Announcement
of the initial Council. 

        In
addition to these activities, during the first six months of NeuStar's operation of the usTLD, it will be in constant contact with the delegated manager and locality-based user
community in developing the required report to the DOC. NeuStar also will continue its public awareness activities as discussed in Section B.2.8. 

B.3-14

 

Data Rights and Use Policy  

        NeuStar, as a trusted neutral third-party registry, must maintain the trust of the registrars and delegated managers, as well as the end users of the usTLD.
Therefore, NeuStar recognizes that the data provided by usTLD Registrars and delegated managers belong exclusively to the usTLD Registrars and delegated managers, respectively. NeuStar will not use
the data obtained from registrars and delegated managers, other than for purposes of providing usTLD services and as set forth in the Registry-Registrar Agreement. 

Whois Policy  

        According to the Intellectual Property Constituency of the Domain Name Supporting Organization of ICANN, "Reliable, current, and multi-faceted Whois sites that
allow accurate and full-featured searching across all registries and registrars will help ensure the protection of copyrights and trademarks in cyberspace, as well as simultaneously
protect the interests of consumers who use the Internet to make important purchasing decisions." See Matters Related to Whois,
http://ipc.songbird.com/whois_paper.html. A Whois search allows copyright owners to identify the site operator and/or the Internet service provider that is hosting potentially infringing materials or
transmitting the infringing activities in order to identify online infringers for enforcement or licensing purposes. Trademark owners undertake Whois searches in an attempt to avoid possible
conflicts, as well as to cure unauthorized and confusing uses of their mark. 

        In
addition, Whois is a useful tool for consumers seeking to identify online merchants, the source of unsolicited e-mail, and so forth. Finally, many law enforcement
agencies, including the Federal Bureau of Investigations, state and local police departments, and public safety watch groups including the Center for Missing Children also rely heavily on the
publicly-available Whois database to prevent and apprehend criminal behavior. 

        NeuStar
recognizes, however, that unfettered access to public Whois information also raises a number of significant privacy concerns, not the least of which is the ease with which this
often-personal information can be obtained. In addition, some believe that the current state of privacy protections with respect to the Whois database essentially eliminates the ability of Internet
users to anonymously register domain names. Finally, many people who register domain names, especially those who register domain names for noncommercial or personal purposes, are unaware that their
home address and phone number will immediately become available to any Internet user in the world. 

        NeuStar
understands that ICANN and the Domain Name Supporting Organization are currently addressing issues surrounding the Whois database and its use by the Internet Community. NeuStar
will closely monitor the activities of the DNSO and ICANN as well as initiate its own analysis of the issues through the Council, as set forth above. 

NeuStar's Whois Service  

        NeuStar's Whois service, modeled in part after a Whois solution that has been adopted by ICANN and has gained acceptance with the Internet community, will provide
a central, openly accessible system for information regarding a particular domain name registration in the usTLD. This centralized "thick" Whois repository for the Whois information will be designed
for robustness, availability, and performance. 

        In
designing the Whois service for the usTLD, NeuStar reviewed current approaches to the service offered by other ccTLD administrators as well as by the various gTLD operators. NeuStar
believes that aspects of the current approach offered by the.name gTLD balances both the need for easy access to the Whois database by legitimate users, including intellectual property owners, law
enforcement, and 

B.3-15

 

consumer
organizations, but also takes into consideration relevant privacy concerns of those whose information is contained within the Whois database. 

        The
usTLD Administrator will make available both a web-based and Port 43 Whois interface on its web site which can also be linked to by each usTLD Registrar that is a party
to a Registry-Registrar Agreement with NeuStar. The information available in the Whois database will be returned as a result of a query. 

        As
required in the RFQ, NeuStar's Whois database will allow for multiple string and field searching through a free, public, web-based interface. Although NeuStar's system
will be engineered to handle high transaction loads, unreasonable levels of traffic resulting from "data mining" activities common on the Internet could hamper public availability and quality of Whois
services. Therefore, this interface will provide up to seventy-five (75) responses to any given query. Recognizing that many users, including law enforcement and intellectual
property owners, have a legitimate need for more robust searching capabilities, NeuStar also will provide a Whois-like directory service that will provide responses to queries in excess of
seventy-five and will permit sub-string (wildcard) and more advanced Boolean searching. 

The Whois Report  

        The Whois report shall contain the following information: 

	•
	The
domain name registered;

	•
	The
IP address and corresponding names of the primary and secondary nameservers for the registered name;

	•
	The
registrar name and URL or, where appropriate, the identity of the delegated manager under which the name is registered;

	•
	The
original creation date and term of the registration;

	•
	The
name and postal address of the domain name registrant;

	•
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the billing contact for the name registered;

	•
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the name registered; and

	•
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the name registered. 

        Whois
service will be subject to certain terms and conditions. The additional terms and conditions are intended to prevent the unauthorized use of Whois information for purposes such as
unsolicited marketing, e-mail (spamming), and other unlawful purposes. 

        When
requesting the Whois report, the requestor must provide the following information: 

	•
	A
declaration that the data is being requested for a lawful reason, and that the data will not be used for marketing purposes, spamming, or any other improper purpose.

	•
	A
declaration that the reason for collecting the data is to protect legal rights and obligations. Such a reason could be, but is not limited to:

	•
	Investigating
and defending a possible violation of intellectual property

	•
	Seeking
information for use by a law enforcement agency or consumer protection group 

B.3-16

 

	•
	Information
collected for use within the applicable Dispute Resolution Procedures under the usDRP or Nexus Dispute Policy, or

	•
	Gathering
or collecting information in pursuit of enforcing legal rights and/or remedies

	•
	The
name, postal address, e-mail address, voice telephone number and (where available) fax number of the requestor, and declaration that this information is
correct. 

        Data
collected from or about requestors will be used only to document the request and will not be used for any commercial purpose whatsoever. 

        NeuStar
will reserve the right to prevent access to the Whois service to any individual, entity, or organization that it has reason to believe has violated the above terms and conditions
of the Whois service. 

Enforcement of Accurate Contact and Whois Information  

        Section 3.7.7 of the draft Registrar Accreditation Agreement provides in pertinent part that a Registrar shall require all registrants to enter into a
registration agreement with a registrar including at least the following provisions: 

3.7.7.1
[Registrant] shall provide to Registrar accurate and reliable contact details and promptly correct and update them during the term of the
[Registrant] registration, including: the full name, postal address, e-mail address, voice telephone number, and fax number if available of the
[Registrant]; name of authorized person for contact purposes in the case of an [Registrant] that is an organization, association, or corporation; and
the data elements listed in Subsections 3.3.1.2, 3.3.1.7 and 3.3.1.8. 

3.7.7.2
A [Registrant]'s willful or grossly negligent provision of inaccurate or unreliable information, its willful or grossly negligent failure promptly to update information
provided to Registrar, or its failure to respond for over fifteen (15) calendar days to inquiries by Registrar concerning the accuracy of contact details associated with the
[Registrant]'s registration shall constitute a material breach of the [Registrant]'s Registration Agreement with the registrar and be a basis for
cancellation of the [Registrant] registration. 

        Although
this requirement has been in ICANN's Accreditation Agreement for Registrars in the .com, .net and .org TLDs since 1998, historically, the registrar community has largely ignored
these provisions. As a result, this has led to an increase in inaccurate, false or out of date information in the Whois database. 

        NeuStar,
as the administrator for the usTLD, will adopt additional provisions in both the Accreditation Agreement, the Registry-Registrar Agreement, and the Delegated Manager Agreement
that would ensure that registrars and delegated managers take affirmative steps to enforce its agreements with its own registrants. For Example, NeuStar will require that registrars accept written
complaints from third parties regarding false and/or inaccurate Whois data of domain name registrants. No later than thirty (30) days after receipt of a written complaint, the registrar shall
be required to conduct an initial investigation into the accuracy of the Whois contact information. If the registrar determines that the information is either false, inaccurate or not up to date, the
registrar will be required to issue a notice to the registrant stating that it believes that the information contained in the registrant's Whois record may be false, inaccurate or not up to date. The
registrant shall be required to update its contact information no later than thirty (30) calendar days of the date of such notice. If, within thirty (30) days, the registrant can either
(i) show that it has not provided false or inaccurate contact information or (ii) provide the updated Whois information, then the registrant will be allowed to maintain its usTLD domain
name registration. If, however, after thirty (30) days, the registrant either does not respond to the registrar's notice or is unable to provide true and accurate contact 

B.3-17

 

information,
the registrant shall be deemed to have breached its registration agreement and the registrar shall be required to delete the registration. The registrar shall not be required to refund
any fees paid by the registrant if the registrar terminates a registrant's registration agreement due to its enforcement of this provision. 

Reserved Names Policy  

        Consistent with existing policies and subject to approval by the DOC, NeuStar, as the usTLD Administrator proposes to reserve from registration by the general
public certain second level domain names. The reservation of such names will be made to prevent their improper use in the marketplace and/or to permit the usTLD Administrator to introduce important
new services and enhancements to the usTLD. Moreover, responsible management of some of the listed names will maximize utility of these second level domains and can uniquely serve the public interest
if administered by a responsible party. 

        The
draft list that follows is intended to be illustrative rather than definitive. NeuStar will work collaboratively with DOC and the Council to finalize a list that will responsively
preserve second level names in order to: prevent confusion; serve a public need; prevent theft of phone numbers, social security numbers and zip codes, and/or represent possible future enhancement of
the usTLD space. Once a proposed definitive list is developed, it will be submitted to the DOC for approval. 

All
single-character labels 

All
two-character ISO 3166 country codes or United States Postal codes in addition to the state codes already reserved, shall be initially reserved to avoid conflict with the other country
codes and the states. 

Names
and abbreviations for federal government agencies and divisions (e.g., Department of Commerce, army, navy, air force, DOC, DOD, NTIA). 

All
numbers five digits or greater and all numbers in the form, five digits-four digits 

	 	 	iana
	

dnso	
 	

iana-servers
	

Icann	
 	

iesg
	

internic	
 	

ietf
	

pso	
 	

irtf
	

afrinic	
 	

istf
	

Apnic	
 	

lacnic
	

arin	
 	

latnic
	

example	
 	

rfc-editor
	

gtld-servers	
 	

ripe
	

Iab	
 	

root servers
	

Pro	
 	

nic
	

aero	
 	

whois
	

arpa	
 	

www
	

biz	
 	

kids
	 	 	 

B.3-18

 

	

com	
 	

xxx
	

coop	
 	

park
	

edu	
 	

zip
	

gov	
 	

geo
	

info	
 	

locate
	

int	
 	

scholarship
	

mil	
 	

whitehouse
	

museum	
 	

veterans
	

name	
 	

library
	

net	
 	

school
	

org	
 	

911

 
 

usTLD Dispute-Resolution Policies    
    

General Information  

        All usTLD Accredited Registrars in the usTLD shall follow the usTLD Dispute Resolution Policy (referred to as the "USDRP"). The USDRP, is incorporated by
reference into all usTLD Registration Agreements, and sets forth the terms and conditions in connection with a dispute relating to alleged bad faith domain name registrations as well as violations of
the United States Nexus Requirement. 

        To
invoke the policy, a trademark owner should either (a) file a complaint in a court of proper jurisdiction against the domain name holder (or where appropriate an
in-rem action concerning the domain name) or (b) in cases of abusive registration submit a complaint to an approved dispute-resolution service provider (see below for a list and
links). 

Principal Documents  

        The following documents provide details: 

	•
	usTLD Dispute Resolution Policy—This policy is followed by all registrars.

	•
	Rules for usTLD Dispute Resolution Policy—These rules are followed by all dispute-resolution service providers,
with supplementation by each provider's supplemental rules.

	•
	Current usTLD Dispute Resolution Provider—American Arbitration Association.

	•
	Nexus Dispute Policy

B.3-19

  

NOTE: This policy is between the usTLD Registrar and its customer (the domain name holder or registrant). Thus, the policy uses "we" and "our" to refer
to the registrar and it uses "you" and "your" to refer to the domain name holder. 

 
 

usTLD Dispute Resolution Policy    
    

        (As Approved by the United States Department of Commerce on                , 2001)

	1.
	Purpose—This usTLD Dispute Resolution Policy (the "Policy") has been adopted by the United States Department of Commerce
("DOC"). It is incorporated by reference into the usTLD Registration Agreement, and sets forth the terms and conditions in connection with a dispute between you (as the registrant) and any party other
than us (as the registrar) or the registry administrator for the usTLD (as the "Registry") over the registration and use of an Internet domain name registered by you. Proceedings under
Paragraph 4 of this Policy will be conducted according to the Rules for the usTLD Dispute Resolution Policy (the "Rules"), which are available
at                        , and the selected
administrative-dispute-resolution service provider's supplemental rules.

	2.
	Your Representations—By applying to register a domain name, or by asking us to maintain or renew a domain name registration,
you hereby represent and warrant to us that (a) the statements that you made in your usTLD Registration Agreement are complete and accurate; (b) to your knowledge, the registration of
the domain name will not infringe upon or otherwise violate the rights of any third party; (c) you are not registering the domain name for an unlawful purpose; and (d) you will not
knowingly use the domain name in violation of any applicable laws or regulations. It is your responsibility to determine whether your domain name registration infringes or violates someone else's
rights.

	3.
	Cancellations, Transfers, and Changes—We will cancel, transfer or otherwise make changes to a domain name registration that
is subject to this Policy under the following circumstances:

	a.
	Subject
to the provisions of Paragraph 8, our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action;

	b.
	Our
receipt of an order from a court or arbitral tribunal, in each case of competent jurisdiction, requiring such action; and/or

	c.
	Our
receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party and which was conducted under this Policy or a
later version of this Policy adopted by the DOC. 

        We
may also cancel, transfer or otherwise make changes to a domain name registration in accordance with the terms of your Registration Agreement or other legal requirements. 

	4.
	Mandatory Administrative Proceeding—This Paragraph sets forth the type of disputes for which you are required to submit to a
mandatory administrative proceeding. These proceedings will be conducted before one of the administrative-dispute-resolution service providers listed
at                        (each, a "Provider").

	a.
	Applicable Disputes—You are required to submit to a mandatory administrative proceeding in the event that a third party (a
"complainant") asserts to the applicable Provider, in compliance with the Rules, that:

	i.
	Your
domain name is identical or confusingly similar to a trademark or service mark in which the complainant has rights; and

	ii.
	You
have no rights or legitimate interests in respect of the domain name; and

	iii.
	Your
domain name has been registered in bad faith or is being used in bad faith. 

B.3-20

 

        In
the administrative proceeding, the complainant must prove that each of these three elements is present. 

	b.
	Evidence of Registration or Use in Bad Faith—For the purposes of Paragraph 4(a)(1)(iii), the following circumstances,
in particular but without limitation, if found by the Panel to be present, shall be evidence of the registration or use of a domain name in bad faith:

	i.
	Circumstances
indicating that you have registered or you have acquired the domain name primarily for the purpose of selling, renting, or otherwise transferring the domain
name registration to the complainant who is the owner of the trademark or service mark or to a competitor of that complainant, for valuable consideration in excess of your documented
out-of-pocket costs directly related to the domain name; or

	ii.
	You
have registered the domain name in order to prevent the owner of the trademark or service mark from reflecting the mark in a corresponding domain name; or

	iii.
	You
have registered the domain name primarily for the purpose of disrupting the business of a competitor; or

	iv.
	By
using the domain name, you have intentionally attempted to attract, for commercial gain, Internet users to your web site or other on-line location, by
creating a likelihood of confusion with the complainant's mark as to the source, sponsorship, affiliation, or endorsement of your web site or location or of a product or service on your web site or
location.

	c.
	How to Demonstrate Your Rights to and Legitimate Interests in the Domain Name in Responding to a Complaint—When you receive
a complaint, you should refer to the Rules in determining how your response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be
proved based on its evaluation of all evidence presented, shall demonstrate your rights or legitimate interests to the domain name for purposes of Paragraph 4(a)(ii):

	i.
	You
are the owner or beneficiary of a trade or service mark that is identical to the domain name; or

	ii.
	Before
any notice to you of the dispute, your use of, or demonstrable preparations to use, the domain name or a name corresponding to the domain name in connection with
a bona fide offering of goods or services; or

	iii.
	You
(as an individual, business, or other organization) have been commonly known by the domain name, even if you have acquired no trademark or service mark rights; or

	iv.
	You
are making a legitimate noncommercial or fair use of the domain name, without intent for commercial gain to misleadingly divert consumers or to tarnish the trademark
or service mark at issue.

	d.
	Selection of Provider—The complainant shall select the Provider from among those approved by DOC by submitting the complaint
to that Provider. The selected Provider will administer the proceeding, except in cases of consolidation as described in Paragraph 4(f).

	e.
	Initiation of Proceeding and Process and Appointment of Administrative Panel—The Rules state the process for initiating and
conducting a proceeding and for appointing the panel that will decide the dispute (the "Administrative Panel"). 

B.3-21

 

	f.
	Consolidation—In the event of multiple disputes between you and a complainant, either you or the complainant may petition to
consolidate the disputes before a single Administrative Panel. This petition shall be made to the first Administrative Panel appointed to hear a pending dispute between the parties. This
Administrative Panel may consolidate before it any or all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy or a later version of this
Policy adopted by DOC.

	g.
	Fees—All fees charged by a Provider in connection with any dispute before an Administrative Panel pursuant to this Policy
shall be paid by the complainant, except in cases where you elect to expand the Administrative Panel from one to three panelists as provided in Paragraph 5(b)(iv) of the Rules, in which
case all fees will be split evenly by you and the complainant.

	h.
	Our Involvement in Administrative Proceedings—We do not, and will not, participate in the administration or conduct of any
proceeding before an Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel.

	i.
	Remedies—The remedies available to a complainant pursuant to any proceeding before an Administrative Panel shall be limited
to requiring the cancellation of your domain name or the transfer of your domain name registration to the complainant.

	j.
	Notification and Publication—The Provider shall notify us of any decision made by an Administrative Panel with respect to a
domain name you have registered with us. All decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact
portions of its decision.

	k.
	Availability of Court Proceedings—The mandatory administrative proceeding requirements set forth in Paragraph 4 shall
not prevent either you or the complainant from submitting the dispute to a court of competent jurisdiction for independent resolution before such mandatory administrative proceeding is commenced or
after such proceeding is concluded. If an Administrative Panel decides that your domain name registration should be canceled or transferred, we will wait ten (10) business days (as observed in
the location of our principal office) after we are informed by the applicable Provider of the Administrative Panel's decision before implementing that decision. We will then implement the decision
unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you
have commenced a lawsuit against the complainant in a jurisdiction to which the complainant has submitted under Paragraph 3 of the Rules. (In general, that jurisdiction is either the location
of our principal office or of your address as shown in our Whois database. If we receive such documentation within the ten (10) business day period, we will not implement the Administrative
Panel's decision, and we will take no further action, until we receive (i) evidence satisfactory to us of a resolution between the parties; (ii) evidence satisfactory to us that your
lawsuit has been dismissed or withdrawn; or (iii) a copy of an order from such court dismissing your lawsuit or ordering that you do not have the right to continue to use your domain name.

	5.
	All Other Disputes and Litigation—All other disputes between you and any party other than us regarding your domain name
registration that are not brought pursuant to the mandatory administrative proceeding provisions of Paragraph 4 shall be resolved between you and such other party through any court, arbitration
or other proceeding that may be available.

	6.
	Our Involvement in Disputes—We will not participate in any way in any dispute between you and any party other than us
regarding the registration and use of your domain name. You shall not name us as a party or otherwise include us in any such proceeding. In the event that we are named 

B.3-22

 

as
a party in any such proceeding, we reserve the right to raise any and all defenses deemed appropriate, and to take any other action necessary to defend ourselves. 

	7.
	Maintaining the Status Quo—We will not cancel, transfer, activate, deactivate, or otherwise change the status of any domain
name registration under this Policy except as provided in Paragraph 3 above. 

8.     Transfers During a Dispute  

	a.
	Transfers of a Domain Name to a New Holder—You may not transfer your domain name registration to another holder
(i) during a pending administrative proceeding brought pursuant to Paragraph 4 or for a period of fifteen (15) business days (as observed in the location of our principal place of
business) after such proceeding is concluded; or (ii) during a pending court proceeding or arbitration commenced regarding your domain name unless the party to whom the domain name registration
is being transferred agrees, in writing, to be bound by the decision of the court or arbitrator. We reserve the right to cancel any transfer of a domain name registration to another holder that is
made in violation of this subparagraph.

	b.
	Changing Registrars—You may not transfer your domain name registration to another registrar during a pending administrative
proceeding brought pursuant to Paragraph 4 or for a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is
concluded. You may transfer administration of your domain name registration to another registrar during a pending court action or arbitration, provided that the domain name you have registered with us
shall continue to be subject to the proceedings commenced against you in accordance with the terms of this Policy. In the event that you transfer a domain name registration to us during the pendency
of a court action or arbitration, such dispute shall remain subject to the domain name dispute policy of the registrar from which the domain name registration was transferred.

	9.
	Policy Modifications—We reserve the right to modify this Policy at any time with the permission of DOC. We will post our
revised Policy at <URL> at least thirty (30) calendar days before it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in
which event the version of the Policy in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any domain name
registration dispute, whether the dispute arose before, on or after the effective date of the change. In the event that you object to a change in this Policy, your sole remedy is to cancel your domain
name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel your domain name registration. 

B.3-23

  

 
 

Rules for Uniform Domain Name
  Dispute Resolution Policy
  (the "Rules")    
    

(As
Approved by DOC on                        , 2001) 

        Administrative
proceedings for the resolution of disputes under the Uniform Dispute Resolution Policy adopted by DOC shall be governed by these Rules and also the Supplemental Rules of
the Provider administering the proceedings, as posted on its web site. 

1.     Definitions  

In
these Rules: 

Complainant means the party initiating a complaint concerning a domain name registration. 

DOC refers to the United States Department of Commerce. 

Mutual Jurisdiction means a court jurisdiction at the location of either (a) the principal office of the Registrar of the domain name in
question, or (b) the domain name holder's address as shown for the registration of the domain name in Registrar's Whois database at the time a complaint is submitted to a Provider. 

Panel means an administrative panel appointed by a Provider to decide a complaint concerning a domain name registration. 

Panelist means an individual appointed by a Provider to be a member of a Panel. 

Party means a Complainant or a Respondent. 

Policy means the usTLD Dispute Resolution Policy that is incorporated by reference and made a part of the Registration Agreement. 

Provider means a dispute-resolution service provider approved by DOC. A list of such Providers appears
at                        . 

Registrar means the entity with which the Respondent has registered a domain name that is the subject of a complaint. 

Registration Agreement means the agreement between a Registrar and a domain name holder. 

Respondent means the holder of a domain name registration against which a complaint is initiated. 

Reverse Domain Name Hijacking means using the Policy in bad faith to attempt to deprive a registered domain name holder of a domain name. 

Supplemental Rules means the rules adopted by the Provider administering a proceeding to supplement these Rules. Supplemental Rules shall not be
inconsistent with the Policy or these Rules and shall cover such topics as fees, word and page limits and guidelines, the means for communicating with the Provider and the Panel, and the form of cover
sheets. 

2.     Communications  

	a.
	Any
written communication to the Complainant or the Respondent required under these Rules shall be made by the means specified by the Complainant or the Respondent, respectively, or in
the absence of such specification:

	i.
	By
facsimile with a confirmation of transmission; or 

B.3-24

 

	ii.
	By
postal or courier service, postage pre-paid and return receipt requested; or our receipt of an order from a court or arbitral tribunal, in each case of
competent jurisdiction, requiring such action; and/or

	iii.
	Electronically
via the Internet, provided a record of its transmission is available.

	b.
	Any
communication to the Provider or the Panel shall be made in accordance with the Provider's Supplemental Rules.

	c.
	All
communications shall be made in the language prescribed in Paragraph 11.

	d.
	Either
Party may update its contact details by notifying the other Party, the Provider and the Registrar.

	e.
	Except
as otherwise provided in these Rules, or decided by a Panel, all communications provided for under these Rules shall be deemed to have been made:

	i.
	If
delivered by facsimile transmission, on the date shown on the confirmation of transmission; or

	ii.
	If
by postal or courier service, on the date marked on the receipt; or

	iii.
	If
via the Internet, on the date that the communication was transmitted, provided that the date of transmission is verifiable.

	f.
	Except
as otherwise provided in these Rules, all time periods calculated under these Rules shall begin to run on the earliest date that the communication is deemed to have been made in
accordance with Paragraph 2(e).

	g.
	Except
as otherwise provided in these Rules, any communication by:

	i.
	A
Panel to any Party shall be copied to the Provider and to the other Party;

	ii.
	The
Provider, following the commencement of an administrative proceeding pursuant to Paragraph 4(c), to any Party shall be copied to the other Party; and

	iii.
	A
Party shall be copied to the other Party, the Panel and the Provider, as the case may be.

	h.
	It
shall be the responsibility of the sender to retain records of the fact and circumstances of sending, which shall be available for inspection by affected parties and for reporting
purposes.

	i.
	In
the event that a Party sending a communication receives notification of non-delivery of the communication, that Party shall promptly notify the Provider of the
circumstances of the notification. 

3.     The Complaint  

	a.
	Any
person or entity may initiate an administrative proceeding by submitting a complaint in accordance with the Policy and these Rules to any Provider approved by DOC. (Due to capacity
constraints or for other reasons, a Provider's ability to accept complaints may be suspended at times. In that event, the Provider shall refuse the submission. The person or entity may submit the
complaint to another Provider.)

	b.
	The
complaint shall be submitted in hard copy (with annexes) and in electronic form (without annexes). 

B.3-25

 

	c.
	The
complaint shall:

	i.
	Request
that the complaint be submitted for decision in accordance with the Policy and Rules and describe why the domain name registration should be considered subject to
the Policy;

	ii.
	Provide
the full name, postal and e-mail addresses, and the telephone and telefax numbers of the Complainant and of any representative authorized to act for
the Complainant in the administrative proceeding;

	iii.
	Specify
a preferred method for communications directed to the Complainant in the administrative proceeding (including person to be contacted, medium, and address
information) for each of (A) electronic-only material and (B) material including hard copy;

	iv.
	Designate
whether Complainant elects to have the dispute decided by a single-member or a three-member Panel and, in the event Complainant elects a three-member Panel,
provide the names and contact details of three candidates to serve as one of the Panelists (these candidates may be drawn from any DOC-approved Provider's list of panelists);

	v.
	Provide
the full name of the Respondent and, if different from the contact details available in the Whois database for the domain name, provide all information known to
the Complainant regarding how to contact Respondent or any representative of Respondent, including contact information based on pre-complaint dealings;

	vi.
	Specify
the domain name(s) that is/are the subject of the complaint;

	vii.
	Identify
the Registrar(s) with whom the domain name(s) is/are registered at the time the complaint is filed;

	viii.
	Specify
the trademark(s) or service mark(s) on which the complaint is based and, for each mark, describe the goods or services, if any, with which the mark is used
(the Complainant may also separately describe other goods and;

	ix.
	Describe,
in accordance with the Policy, the grounds on which the complaint is made including, in particular,

	(1)
	The
manner in which the domain name(s) is/are identical or confusingly similar to a trademark or service mark in which the Complainant has rights; and

	(2)
	Why
the Respondent (domain name holder) should be considered as having no rights or legitimate interests in respect of the domain name(s) that is/are the subject of the complaint; and

	(3)
	Why
the domain name(s) should be considered as having been registered in bad faith or is being used in bad faith 

(The
description should, for elements (2) and (3), discuss any aspects of Paragraphs 4(b) and 4(c) of the Policy that are applicable. The description shall comply with any word or page limit
set forth in the Provider's Supplemental Rules.); 

	x.
	Specify,
in accordance with the Policy, the remedies sought;

	xi.
	Identify
any other legal proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that are the subject of the
complaint; 

B.3-26

 

	xii.
	State
that a copy of the complaint, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent or transmitted to the Respondent
(domain name holder), in accordance with Paragraph 2(b);

	xiii.
	State
that Complainant will submit, with respect to any challenges to a decision in the administrative proceeding canceling or transferring the domain name, to the
jurisdiction of the courts in at least one specified Mutual Jurisdiction;

	xiv.
	Conclude
with the following statement followed by the signature of the Complainant or its authorized representative: 

"Complainant
agrees that its claims and remedies concerning the registration of the domain name, the dispute, or the dispute's resolution shall be solely against the domain name holder and waives all
such claims and remedies against (a) the dispute-resolution provider and panelists, except in the case of deliberate wrongdoing, (b) the registrar, (c) the registry administrator,
and (d) the Department of Commerce, as well as their directors, officers, employees, and agents." 

"Complainant
certifies that the information contained in this Complaint is to the best of Complainant's knowledge complete and accurate, that this Complaint is not being presented for any improper
purpose, such as to harass, and that the assertions in this Complaint are warranted under these Rules and under applicable law, as it now exists or as it may be extended by a good-faith
and reasonable argument."; and 

	xv.
	Annex
any documentary or other evidence, including a copy of the Policy applicable to the domain name(s) in dispute and any trademark or service mark registration upon
which the complaint relies, together with a schedule indexing such evidence.

	c.
	The
complaint may relate to more than one domain name, provided that the domain names are registered by the same domain name holder. 

4.     Notification of Complaint  

	a.
	The
Provider shall review the complaint for formal compliance with the Policy and the Rule. If the complaint is found to be in compliance, the Provider shall notify it to the
Respondent, in the manner prescribed by Paragraph 2(a). For the purposes of notifying the complainant, the Provider shall not be required to use any contact details other than those available
in the Whois database for the domain name(s) in dispute.

	b.
	If
the Provider finds the complaint to be formally deficient, it shall promptly notify the Complainant of the nature of the deficiencies identified. The Complainant shall have five
(5) calendar days within which to correct any such deficiencies, after which the administrative proceeding will be deemed withdrawn without prejudice to submission of a different complaint by
Complainant.

	c.
	The
date of commencement of the administrative proceeding shall be the date on which the Provider completes its responsibilities under Paragraph 2(a) in connection with
forwarding the Complaint to the Respondent.

	d.
	The
Provider shall immediately notify the Complainant, the Respondent, the concerned Registrar(s), and DOC of the date of commencement of the administrative proceeding. 

5.     The Response  

	a.
	Within
twenty (20) calendar days of the date of commencement of the administrative proceeding the Respondent shall submit a response to the Provider. 

B.3-27

 

	b.
	The
response shall be submitted in hard copy (with annexes) and in electronic form (without annexes).

	c.
	The
response shall:

	i.
	Specifically
respond to the statements and allegations contained in the complaint and include any and all bases for the Respondent to retain registration and use of the
disputed domain name;

	ii.
	Provide
the name, postal and e-mail addresses, and the telephone and telefax numbers of the Respondent and of any representative authorized to act for the
Respondent in the administrative proceeding;

	iii.
	Specify
a preferred method for communications directed to the Respondent in the administrative proceeding (including person to be contacted, medium, and address
information) for each of (A) electronic-only material and (B) material including hard copy;

	iv.
	If
Complainant has elected a single-member panel in the Complaint (see Paragraph 3(b)(iv)), state whether Respondent elects instead to have the dispute decided by
a three-member panel;

	v.
	If
either Complainant or Respondent elects a three-member Panel, provide the names and contact details of three candidates to serve as one of the Panelists (these
candidates may be drawn from any DOC-approved Provider's list of panelists);

	vi.
	Identify
any other legal proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that are the subject of the
complaint;

	vii.
	Conclude
with the following statement followed by the signature of the Respondent or its authorized representative: 

"Respondent
certifies that the information contained in this Response is to the best of Respondent's knowledge complete and accurate, that this Response is not being presented for any improper
purpose, such as to harass, and that the assertions in this Response are warranted under these Rules and under applicable law, as it now exists or as it may be extended by a good-faith and
reasonable argument."; and 

	viii.
	Annex
any documentary or other evidence upon which the Respondent relies, together with a schedule indexing such documents.

	d.
	If
Complainant has elected to have the dispute decided by a single-member Panel and Respondent elects a three-member Panel, Respondent shall be required to pay one-half of
the applicable fee for a three-member Panel as set forth in the Provider's Supplemental Rules. This payment shall be made together with the submission of the response to the Provider. In the event
that the required payment is not made, the dispute shall be decided by a single-member Panel.

	e.
	At
the request of the Respondent, the Provider may, in exceptional cases, extend the period of time for the filing of the response. The period may also be extended by written
stipulation between the Parties, provided the stipulation is approved by the Provider.

	f.
	If
a Respondent does not submit a response, in the absence of exceptional circumstances, the Panel shall decide the dispute based upon the complaint. 

B.3-28

 

6.     Appointment of the Panel and Timing of Decision  

	a.
	Each
Provider shall maintain and publish a publicly available list of panelists and their qualifications.

	b.
	If
neither the Complainant nor the Respondent has elected a three-member Panel (Paragraphs 3(b)(iv) and 5(b)(iv)), the Provider shall appoint, within five (5) calendar
days following receipt of the response by the Provider, or the lapse of the time period for the submission thereof, a single Panelist from its list of panelists. The fees for a single-member Panel
shall be paid entirely by the Complainant.

	c.
	If
either the Complainant or the Respondent elects to have the dispute decided by a three-member Panel, the Provider shall appoint three Panelists in accordance with the procedures
identified in Paragraph 6(e). The fees for a three-member Panel shall be paid in their entirety by the Complainant, except where the election for a three-member Panel was made by the
Respondent, in which case the applicable fees shall be shared equally between the Parties.

	d.
	Unless
it has already elected a three-member Panel, the Complainant shall submit to the Provider, within five (5) calendar days of communication of a response in which the
Respondent elects a three-member Panel, the names and contact details of three candidates to serve as one of the Panelists. These candidates may be drawn from any DOC-approved Provider's
list of panelists.

	e.
	In
the event that either the Complainant or the Respondent elects a three-member Panel, the Provider shall endeavor to appoint one Panelist from the list of candidates provided by each
of the Complainant and the Respondent. In the event the Provider is unable within five (5) calendar days to secure the appointment of a Panelist on its customary terms from either Party's list
of candidates, the Provider shall make that appointment from its list of panelists. The third Panelist shall be appointed by the Provider from a list of five candidates submitted by the Provider to
the Parties, the Provider's selection from among the five being made in a manner that reasonably balances the preferences of both Parties, as they may specify to the Provider within five
(5) calendar days of the Provider's submission of the five-candidate list to the Parties.

	f.
	Once
the entire Panel is appointed, the Provider shall notify the Parties of the Panelists appointed and the date by which, absent exceptional circumstances, the Panel shall forward
its decision on the complaint to the Provider.

 

	7.
	Impartiality and Independence—A Panelist shall be impartial and independent and shall have, before accepting appointment,
disclosed to the Provider any circumstances giving rise to justifiable doubt as to the Panelist's impartiality or independence. If, at any stage during the administrative proceeding, new circumstances
arise that could give rise to justifiable doubt as to the impartiality or independence of the Panelist, that Panelist shall promptly disclose such circumstances to the Provider. In such event, the
Provider shall have the discretion to appoint a substitute Panelist.

	8.
	Communication Between Parties and the Panel—No Party or anyone acting on its behalf may have any unilateral communication
with the Panel.

	9.
	Transmission of the File to the Panel—The Provider shall forward the case file as soon as the last Panelist is appointed in
the case of a three-member Panel. 

10.   General Powers of the Panel  

	a.
	The
Panel shall conduct the administrative proceeding in such manner as it considers appropriate in accordance with the Policy and these Rules. 

B.3-29

 

	b.
	In
all cases, the Panel shall ensure that the Parties are treated with equality and that each Party is given a fair opportunity to present its case.

	c.
	The
Panel shall ensure that the administrative proceeding takes place with due expedition. It may, at the request of a Party or on its own motion, extend, in exceptional cases, a
period of time fixed by these Rules or by the Panel.

	d.
	The
Panel shall determine the admissibility, relevance, materiality and weight of the evidence.

	e.
	A
Panel shall decide a request by a Party to consolidate multiple domain name disputes in accordance with the Policy and these Rules. 

11.   Language of Proceedings  

	a.
	Unless
otherwise agreed by the Parties, or specified otherwise in the Registration Agreement, the language of the administrative proceeding shall be the language of the Registration
Agreement, subject to the authority of the Panel to determine otherwise, having regard to the circumstances of the administrative proceeding.

	b.
	The
Panel may order that any documents submitted in languages other than the language of the administrative proceeding be accompanied by a translation in whole or in part into the
language of the administrative proceeding.

 

	12.
	Further Statements—In addition to the complaint and the response, the Panel may request, in its sole discretion, further
statements or documents from either of the Parties.

	13.
	In-Person Hearings—There shall be no in-person hearings (including hearings by teleconference,
videoconference, and web conference), unless the Panel determines, in its sole discretion and as an exceptional matter, that such a hearing is necessary for deciding the complaint. 

14.   Default  

	a.
	In
the event that a Party, in the absence of exceptional circumstances, does not comply with any of the time periods established by these Rules or the Panel, the Panel shall proceed to
a decision on the complaint.

	b.
	If
a Party, in the absence of exceptional circumstances, does not comply with any provision of, or requirement under, these Rules or any request from the Panel, the Panel shall draw
such inferences therefrom as it considers appropriate. 

15.   Panel Decisions  

	a.
	A
Panel shall decide a complaint on the basis of the statements and documents submitted and in accordance with the Policy, these Rules and any rules and principles of law that it deems
applicable.

	b.
	In
the absence of exceptional circumstances, the Panel shall forward its decision on the complaint to the Provider within fourteen (14) days of its appointment pursuant to
Paragraph 6.

	c.
	In
the case of a three-member Panel, the Panel's decision shall be made by a majority.

	d.
	The
Panel's decision shall be in writing, provide the reasons on which it is based, indicate the date on which it was rendered and identify the name(s) of the Panelist(s).

	e.
	Panel
decisions and dissenting opinions shall normally comply with the guidelines as to length set forth in the Provider's Supplemental Rules. Any dissenting opinion shall accompany
the majority decision. If the Panel concludes that the dispute is not within the scope of 

B.3-30

 

Paragraph 4(a)
of the Policy, it shall so state. If after considering the submissions the Panel finds that the complaint was brought in bad faith, for example in an attempt at Reverse Domain
Name Hijacking or was brought primarily to harass the domain name holder, the Panel shall declare in its decision that the complaint was brought in bad faith and constitutes an abuse of the
administrative proceeding. 

16.   Communication of Decision to Parties  

	a.
	Within
three (3) calendar days after receiving the decision from the Panel, the Provider shall communicate the full text of the decision to each Party, the concerned
Registrar(s), and DOC. The concerned Registrar(s) shall immediately communicate to each Party, the Provider, and DOC the date for the implementation of the decision in accordance with the Policy.

	b.
	Except
if the Panel determines otherwise (see Paragraph 4(j) of the Policy), the Provider shall publish the full decision and the date of its implementation on a publicly
accessible web site. In any event, the portion of any decision determining a complaint to have been brought in bad faith (see Paragraph 15(e) of these Rules) shall be published. 

17.   Settlement or Other Grounds for Termination  

	a.
	If,
before the Panel's decision, the Parties agree on a settlement, the Panel shall terminate the administrative proceeding.

	b.
	If,
before the Panel's decision is made, it becomes unnecessary or impossible to continue the administrative proceeding for any reason, the Panel shall terminate the administrative
proceeding, unless a Party raises justifiable grounds for objection within a period of time to be determined by the Panel. 

18.   Effect of Court Proceedings  

	a.
	In
the event of any legal proceedings initiated prior to or during an administrative proceeding in respect of a domain name dispute that is the subject of the complaint, the Panel
shall have the discretion to decide whether to suspend or terminate the administrative proceeding, or to proceed to a decision.

	b.
	In
the event that a Party initiates any legal proceedings during the pendency of an administrative proceeding in respect of a domain name dispute that is the subject of the complaint,
it shall promptly notify the Panel and the Provider. See Paragraph 8 above. 

19.   Fees  

	a.
	The
Complainant shall pay to the Provider an initial fixed fee, in accordance with the Provider's Supplemental Rules, within the time and in the amount required. A Respondent electing
under Paragraph 5(b)(iv) to have the dispute decided by a three-member Panel, rather than the single-member Panel elected by the Complainant, shall pay the Provider one-half
the fixed fee for a three-member Panel. See Paragraph 5(c). In all other cases, the Complainant shall bear all of the Provider's fees, except as prescribed under Paragraph 19(d). Upon
appointment of the Panel, the Provider shall refund the appropriate portion, if any, of the initial fee to the Complainant, as specified in the Provider's Supplemental Rules.

	b.
	No
action shall be taken by the Provider on a complaint until it has received from Complainant the initial fee in accordance with Paragraph 19(a). 

B.3-31

 

	c.
	If
the Provider has not received the fee within ten (10) calendar days of receiving the complaint, the complaint shall be deemed withdrawn and the administrative proceeding
terminated.

	d.
	In
exceptional circumstances, for example in the event an in-person hearing is held, the Provider shall request the Parties for the payment of additional fees, which shall
be established in agreement with the Parties and the Panel.

 

	20.
	Exclusion of Liability—Except in the case of deliberate wrongdoing, neither the Provider nor a Panelist shall be liable to
a Party for any act or omission in connection with any administrative proceeding under the Policy and the Rules.

	21.
	Amendments—The version of these Rules in effect at the time of the submission of the complaint to the Provider shall apply
to the administrative proceeding commenced thereby. These Rules may not be amended without the express written approval of DOC. 

B.3-32

   B.4    Locality-Based usTLD Structure Functions  

        NeuStar's modernized functions for the locality-based usTLD namespace will support the current delegated managers and registrants, and
encourage new registrations in the namespace.

	•
	NeuStar's modernization of the usTLD structure extends not only to the expanded space but to the locality space as well.

	•
	We will reach out to delegated managers and registrants for continued input for improving functions in the locality space.

	•
	NeuStar will automate the registration process in the locality space to encourage registrations and ensure that those registrations are processed
quickly and efficiently.

        Although
the usTLD locality space is currently underutilized and undervalued, it remains a valuable space, with existing delegated managers and registrants who appreciate its
hierarchical structure. A goal of modernizing the usTLD infrastructure cannot lie only in plans to allow registrations in an expanded space; it must also accommodate the existing locality space.
Similarly, simply keeping the locality space as is, without modernizing its infrastructure or examining policies for improvements, is a disservice to the users of that space. 

        NeuStar's
approach to developing and implementing a usTLD infrastructure is inclusive. Our current understanding of the locality space will be augmented when we reach out to delegated
managers and to registrants for their input. Our services provided in the locality space, to registrants and to delegated managers, will be equal to those services offered in the expanded space. Our
customers are important to us, and our diminishing those services for any subset of our customers would be contrary to our philosophy of equitable treatment and integrity. 

        The
locality-based usTLD structure functions highlighted below and in Sections B.4.1 through B.4.7 include all of the requirements listed in RFQ Section B.4. In each case,
although the specific needs of customers in the locality space have been kept in mind, our solution is as rich in functionality as the comparable function in the expanded space. 

        Existing Delegees and Registrants Service Provision—NeuStar will provide an implementation of the usTLD consistent with the
policies and philosophy embodied in RFC 1480 and the other usTLD policy documents. This implementation will be supplemented by our Centralized usTLD Database, a centralized Whois, Delegee Whois and
automatic registration services to replace the current manual process. 

        Undelegated Third Level Subdomains Service Provision—NeuStar will provide registrar services for undelegated third-level
subdomains in the locality space through the use of our Enhanced Shared Registry System (SRS), the same system that will be used by registrars in the expanded space. 

        Locality-Based Process Modernization—NeuStar will modernize the processes used in the locality space by leveraging our
Enhanced SRS and Centralized usTLD Database, by automating registrations, and by implementing an automated update process and a modernized zone file update process. 

        Current Locality-Based usTLD Users Coordination—NeuStar will establish target communications mechanisms, including
e-mail listservs, chat services, and other Internet-based services, as well as traditional customer outreach mechanisms, such as user group meetings, user support representatives, and
other support services to maintain close relationships with usTLD stakeholders. 

        Compliance with Current Locality-Based usTLD Policies Investigation and Report—NeuStar will approach our compliance
investigation as a means of forming partnerships with the Delegated Managers, i.e., delegees and subdelegees in the locality space. We view this report as a means of not only discovering problems in
the locality space, but also of collaborating with Delegated Managers to improve the overall utility of the namespace. 

B.4-1

 

        usTLD Delegated Manager Database Development—NeuStar's database of Delegated Manager information will ensure that all delegee
and subdelegee contact information and delegation information is kept up to date, so that both the registry can contact these Delegated Managers to
resolve issues, and so that registrants can contact these Delegated Managers to register in the locality space. 

        Whois Database Development—NeuStar's centralized enhanced Whois database will accommodate Web-based, free, public
searches for registrant and delegated manager contact information and will ensure the accuracy of data throughout the locality space. 

        The
functions presented in this section will enhance the utility of the locality space and make the namespace more attractive to registrants who wish to register a domain name based in
the geographic hierarchy. By centralizing our services and automating the registration process, we will provide our customers with a stable registry environment and easy-to-use
services as good as or better than those offered by any other top-level domain registry. 

B.4.1    Existing Delegees and Registrants Service Provision  

        Existing delegees and registrants in the usTLD rely on the services that the usTLD infrastructure provides. However, that current infrastructure has not evolved
along with other leading Internet registries. Currently, the registration process currently is manual, the zone data update process is batch oriented, and the basic usTLD policies are not even
available in a single coherent document. 

        It
is unfortunate that the current implementations are now outdated. The lag behind modern implementations causes potential users to question the value of acquiring or maintaining names
in the US domain name space. NeuStar proposes significant improvements that will benefit the existing users of the usTLD. We intend to make the usTLD a world renown ccTLD. We intend to provide
services and support that improves on current practice and complies with existing policies (including RFC 1480 and Web pages on www.nic.us that take precedence). We intend to enhance the value of
domain names held by existing delegees and registrants. 

        As
proposed by NeuStar, the usTLD will have a robust, secure, and reliable infrastructure equal to or better than any Internet registry. The registration process will be streamlined so
that users can check, add, modify, or delete names over an easy to access, simple to use web interface. All pertinent data related to name registrations will be maintained in a centralized data base
at the registry. NeuStar will provide tools to delegees and subdelegees to simplify the process of inputting data into the Centralized usTLD Database. Zone file data will be updated from the database
and propagated to nameservers in near real time. Whois data for all name holders (name holder refers collectively to delegees, subdelegees and registrants) will be available free through a public,
web-based interface, and the Whois DB will allow for multiple string and field searches. 

        The
existing delegees and registrants in the US domain will then be provided the service and support that they are entitled to expect. NeuStar will provide these services using robust
and reliable systems designed to support the use of the usTLD by the Internet community of the United States. 

B.4.1.1    Needs of Existing Users  

        The continued operation and support of the locality based usTLD is a fundamental concern to its users and an essential set of functions for the Internet community
of the United States. For existing delegees and registrants, NeuStar proposes to provide service and support that will enhance the value of the names they hold in the US domain. 

        Current
name holders want the capability to check, add, modify, or delete their data. They want DNS nameservers to have current zone file data, and they want their Whois data to be
accurate and timely. In addition, users need to rely on a robust, reliable, and secure infrastructure that will be able to satisfy their expected future needs as well as their current ones. 

B.4-2

 

        NeuStar
plans to implement an infrastructure designed to meet users' needs. This will include the following: 

	•
	Secure
website for delegee and registrant access,

	•
	Centralized
usTLD database, and

	•
	Updates
of zone file, Whois and Delegee Whois in near real time. 

        In
addition, as described elsewhere in this proposal, NeuStar's facilities will be based on high availability, reliable platforms, and users (Section O.1) will have access to a
range of technical and customer support services (Section B.2). NeuStar will provide clear and current guidance on the
applicable policies (Section B.3). The needs of the existing delegees and registrants will be met by this approach. 

B.4.1.2    Implementing Services for Delegees  

        In the existing locality-based name space, delegees support the fabric of the US domain. These delegees are responsible for the technical operation of nameservers
for the zone names they hold, and they are responsible for administering the names in that branch of the name space. RFC 1480 speaks clearly to the degree of responsibility and commitment involved. In
addition to the technical and operational aspects, as indicated by the following: 

The
designated manager must do a satisfactory job of operating the DNS service for the domain. That is, the actual management of the assigning of domain names, delegating subdomains and operating name
servers must be done with technical competence. This includes keeping the US Domain Administrator or other higher-level domain managers advised of the status of the domain, responding to requests in a
timely manner, and operating the database with accuracy, robustness, and resilience. 

        That
RFC also conveys the administrative context of delegation: 

The
major concern in selecting a designated manager for a domain is that it be able to carry out the necessary responsibilities, and have the ability to do an equitable, just, honest, and competent
job. The key requirement is that for each domain there be a designated manager for supervising that domain's name space. These designated authorities are trustees for the delegated domain, and have a
duty to serve the community. The designated manager is the trustee of the domain for the domain itself and the global Internet community. 

        In
that spirit, NeuStar plans to provide an implementation of the usTLD consistent with the policies and philosophy embodied in RFC 1480 and the other usTLD policy documents (e.g., as
posted on www.nic.us). The major features that will provide service and support are described in Sections B, F, and O in this proposal, and include: 

	•
	Secure
website for delegee and subdelegee access, with authentication ensuring that they are modifying records within their own name space,

	•
	Centralized
usTLD database, replicated on high availability, reliable platforms, and

	•
	Updates
of zone file, Whois data, and Delegee Whois in near real time. 

B.4.1.3    Providing Support for Registrants  

        In the existing locality-based name space, registrants are offered an alternative to running their own name servers, since delegation entails its own burdens of
responsibility and costs. Instead, registrants' data is directly entered in the US domain, meaning that the zone data files on the usTLD name servers themselves have the name holders' information. 

B.4-3

 

        Direct
registration provides name service support to a wider population of users by relieving them of administrative and technical requirements that come with delegation. As described
later in this proposal, the usTLD registry will be able to perform registry and registrar functions on behalf of such registrants. 

        Registrants,
too, will enjoy the benefit from the same services and support indicated above for delegees in the existing locality-based space, including secure website, centralized
database, near real time updates, and other features provided for name holders in the usTLD. 

B.4.2    Undelegated Third Level Sub-domains Service Provision  

        Undelegated sub-domains have been situated as a middle ground that offers name registration without requiring name server operation. The name servers
for names in undelegated sub-domains are in fact the usTLD's name servers, and the name holders' data is kept in the main usTLD database and zone files. 

        The
Statement of Work (SOW) requires that the usTLD Administrator provide registry and registrar services for name holders in undelegated third level locality sub-domains and
others. 

B.4-4

 

According
to the official US Domain Registry's Web site (www.nic.us), that set of undelegated domains has the following structure: 

Name Structures—usTLD Locality-Based  

	City Government:	 	<dept-name>	 	.	 	CI	 	.	 	<locality>	 	.	 	<state-code>	 	.	 	US
	

County Government:	
 	

<dept-name>	
 	

..	
 	

CO	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Parish Government:	
 	

<dept-name>	
 	

..	
 	

PARISH	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Town Government:	
 	

<dept-name>	
 	

..	
 	

TOWN	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Township:	
 	

<dept-name>	
 	

..	
 	

TOWNSHIP	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Township (option):	
 	

<dept-name>	
 	

..	
 	

TWP	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Borough Government:	
 	

<dept-name>	
 	

..	
 	

BOROUGH	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Village Government:	
 	

<dept-name>	
 	

..	
 	

VILLAGE	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Village (option):	
 	

<dept-name>	
 	

..	
 	

VIL	
 	

..	
 	

<locality>	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Schools K12 District:	
 	

 	
 	

 	
 	

<school-district>	
 	

..	
 	

K12	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

K12 School:	
 	

<school>	
 	

..	
 	

<school-district>	
 	

..	
 	

K12	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Private School:	
 	

<school>	
 	

..	
 	

PVT	
 	

..	
 	

K12	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Community College:	
 	

 	
 	

 	
 	

<school>	
 	

..	
 	

CC	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Technical School:	
 	

 	
 	

 	
 	

<school>	
 	

..	
 	

TEC	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Councils of Government:	
 	

 	
 	

 	
 	

<org-name>	
 	

..	
 	

COG	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

District:	
 	

 	
 	

 	
 	

<org-name>	
 	

..	
 	

DST	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Library:	
 	

 	
 	

 	
 	

<library-name>	
 	

..	
 	

LIB	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Museum:	
 	

 	
 	

 	
 	

<org-name>	
 	

..	
 	

MUS	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

State Government:	
 	

 	
 	

 	
 	

<state-agency>	
 	

..	
 	

STATE	
 	

..	
 	

<state-code>	
 	

..	
 	

US
	

Statewide Non-Profit:	
 	

 	
 	

 	
 	

<org-name>	
 	

..	
 	

GEN	
 	

..	
 	

<state-code>	
 	

..	
 	

US

        In
order to satisfy these requirements, the needs of the name holders in these domains include not only those of direct registrants, but also those analogous to certain capabilities
available to delegees and subdelegees. The problem is that there is no delegee for the undelegated domains. The solution is to provide the functions of registry and registrar, on behalf of those
domains, for name holders who are direct registrants of undelegated domains. 

        The
usTLD functions will already include those of usTLD Administrator, for all users, and as name server operators and name space administrators for the undelegated third level
sub-domains. In addition to those, NeuStar proposes to provide the functions of registrar, on behalf of an undelegated sub-domain and its direct registrants, and of registry,
to include that registrar in the Enhanced SRS. 

        The
direct registrants in undelegated sub-domains of the US domain will then be provided the service and support that they are entitled to expect. NeuStar will provide these
services using robust and reliable systems designed to support the use of the usTLD by the Internet community of the United States. 

B.4-5

 

B.4.2.1    Additional Needs of Undelegated Domains  

        Undelegated domains, by definition, have no official delegee to whom the domain is delegated. Registrants in such a domain must rely on the usTLD itself to
operate name servers, store data for the
zone files, and administer that portion of the name space. There are two different roles for the usTLD Registry to perform, depending on the particular domain, namely: 

	•
	For
the ".us" domain, the function is that of the registry operator for a ccTLD, and

	•
	For
the undelegated sub-domain, the function is that of a registrar.

	•
	Secure
website for delegee and registrant access,

	•
	Centralized
usTLD database, and

	•
	Updates
of zone file, Whois, and Delegee Whois in near real time, 

        but
also including: 

	•
	Implementation
of an Enhanced SRS, and

	•
	Provision
of Registrar Services, on behalf of and in trust for undelegated sub-domains. 

        As
described elsewhere in this proposal, NeuStar's facilities will be based on high availability, reliable platforms (Section O), and users will have access to a range of
technical and customer support services (Section B.2). NeuStar will provide clear and current guidance on the applicable policies. The needs of the name holders in requisite undelegated
sub-domains will be met by this approach. 

B.4.2.2    Implementing Registrar Services  

        NeuStar will provide registrar services on behalf of undelegated sub-domains through a process analogous to that for competitive registrars wishing to
interconnect with the Enhanced Shared Registry System (SRS) for the usTLD. NeuStar is developing this Enhanced SRS as part of its planned modernized registry infrastructure. Registrar functions will
be developed to support NeuStar's capability to act as a registrar on behalf of an undelegated sub-domain in the locality-based name space. The term SRS refers to a system that has a
mechanized interface to multiple registrars, which provides the same service to all of the interconnected registrars. 

        The
process of acting as a registrar requires that the registrar functions, along with the relevant terms and conditions, satisfy all appropriate requirements for competitive registrars
who wish to interconnect with the SRS for the usTLD domain. This formal approach will provide both the services and the safeguards that are needed for NeuStar to act as a registrar. 

        In
NeuStar's role as registrar for an undelegated sub-domain, it acts on behalf of the name holders who are direct registrants in the locality-based name space and who wish
to have NeuStar perform the registrar function. In this role, registrants will register names at a website provided by NeuStar. This will be very similar to the way registrants register names with
registrars in gTLDs such as.biz. NeuStar will provide each registrant with authenticating information that will need to be submitted for future changes and updates. This will ensure that it is the
appropriate registrant modifying the name. 

        Just
like in the expanded space, NeuStar will gather information about the registrant to populate the Central usTLD Database, create a Whois record, and update the zone file. In addition
NeuStar needs to clear the payment and register the registrant in NeuStar's Registrant Database. There is a clear difference between managing a name for a registrar and managing a name for a
registrant. NeuStar understands the importance of treating these two types of registrations differently. 

B.4-6

 

B.4.2.3    Providing Registry Services  

        NeuStar will provide registry services on behalf of undelegated sub-domains through the use of our Enhanced SRS that is being developed to include
NeuStar's capability to act as a registrar on behalf of an undelegated sub-domain in the locality-based name space. 

        The
following briefly describes some of the registry functionality and support proposed by NeuStar. Details are contained in Sections F and O this proposal. 

	•
	NeuStar
will centralize all pertinent information regarding all names registered in the usTLD, and all name holders and registrars will be included in the Centralized usTLD
database and the Whois database.

	•
	The
Centralized usTLD database will be escrowed on a regular basis.

	•
	The
publicly accessible Whois, Delegee Whois and the zone file will be created from the Centralized usTLD database and the updates will be propagated in near real time. 

        NeuStar
understands the range of roles, the services and the safeguards, that are required to satisfy the needs of name holders in the usTLD. Our implementation and operation will
enhance the value of the names of name holders who actually are the usTLD. 

B.4.3    Locality-Based Process Modernization  

        NeuStar's automated registration process, Centralized Database, and Enhanced Shared Registration System (SRS) will modernize the usTLD
registry and encourage new registrations in the locality space.

        Under
the current usTLD administration, all registration and update processes within the registry are done manually. Although requests for registrations are received over a Web
interface, this interface does not interact with a registration system. It simply sends a message to a person who then checks to see if the name is available, if the forms are filled out correctly,
and if the registrant has met the appropriate requirements. The information is then manually added to a list of names and to the zone file, and a new zone file is created and sent to the nameservers,
where it writes over the old zone file. 

        This
process was implemented for registrations from delegated managers, that is, delegees and subdelegees, and for direct registrations with the registry. If a registrant wants to
register with a delegated manager, the registration process depends on the specific delegated manager. There are no
standard requirements for how or where delegated managers store information or how they update zone files, and there are very few requirements for how they maintain and manage their nameservers. 

        NeuStar
will make vast improvements in the operations of the registry itself. NeuStar will implement an automated registration process, a Centralized usTLD Database, a Centralized Whois,
an automated update process, and a modernized zone file update process. All system software and databases will be backed up daily, and the tapes will be stored off-site. As required,
historical files and data will be escrowed with an escrow agent. 

        NeuStar's
Enhanced SRS will be available to all delegated managers via secure web access. Under this new system, changes made by the delegated manager will be implemented directly into
the registry systems, eliminating all manual processes associated with a registration. Changes to the Centralized usTLD Database will be made in real-time, and updates to the Whois and the
zone file (if necessary) will be done in near-real time, that is, in intervals of no more than 15 minutes. A name will go from registration to live in 15 minutes or less, whereas today it
can take weeks. 

        NeuStar
will utilize its state-of-the-art Network Operation Center (NOC) to monitor the Enhanced SRS and its subsystems, including the Centralized
usTLD Database and Whois, as well as the constellation of nameservers, on a 24-hour basis 365 days per year. The NOC will not only monitor for 

B.4-7

 

failures
but also will monitor the systems and network for degraded service that may indicate that a failure is about to happen. 

        NeuStar
will implement billing systems to accommodate both debit accounts and credit cards. This will allow instantaneous registrations. In addition, we will utilize our customer
resource management system that allows for trouble ticket management and customer contact tracking, among other capabilities. 

        A
more detailed description of the ancilliary services provided by NeuStar to the locality space, e.g., customer service, tech support, software, is provided in Sections B.2.9 to B.2.16. 

        A
more detailed description of the Enhanced SRS and the Centralized usTLD Database is provided in Section F of this proposal. 

        Section O
of this proposal provides a detailed description of the systems, software, and functional capabilities that NeuStar will deploy to modernize the usTLD registry for the
locality name space. 

B.4.4    Current Locality-Based usTLD Users Coordination  

        NeuStar will develop user-friendly, effective mechanisms to encourage and coordinate the contributions of the current
locality-based usTLD stakeholders.

        NeuStar
is acutely aware that as a result of the comparative complexity of the namespace and the lack of coordination and marketing for the usTLD, the locality-based usTLD has not
attracted a high level of domain name registration activity and remains underpopulated in comparison with other ccTLDs. Although the existing administrator has established basic policies and
procedures for the TLD, little has been done to enforce such policies and procedures nor has any effort been made to analyze compliance by delegated managers or the value of the namespace to its
users. Moreover, virtually no effort has been made to reach out to users and stakeholders to further develop and improve the space. 

        NeuStar
has a strong legacy of coordinating complex groups of users in the industries that it serves. Successful administration of public resources, whether they are telephone numbers or
domain names, requires strong awareness of constituencies and their needs. NeuStar intends to establish target communications mechanisms, including e-mail listservs, chat services, and
other Internet-based services. In addition, NeuStar will utilize traditional customer outreach, such as user group meetings, user support representatives, and other support services to maintain close
relationships with usTLD stakeholders. These forums will be tailored to allow stakeholders to discuss usTLD administrative, technical, and policy issues related to the operation and management of the
locality-based usTLD structure. This will ensure that, going forward with improvements in the overall space, the current users have a "voice" and stake in the future success and increased utility of
the usTLD. 

        To
begin this process, NeuStar will leverage the six-month compliance report process, discussed in detail below in Section B.4.5, to develop a strong understanding of
stakeholder desires and concerns and to identify the best way to communicate with each constituency group. 

        Coordination
of all usTLD outreach will ultimately be coordinated and developed under the auspices of the usTLD Policy Council. This council will be very important to the ongoing
development of usTLD policy and public outreach. The structure and duties of this council, as well as the detailed outline of our basic outreach plan, are discussed in detail in Section B.3.5. 

B.4.5    Compliance with Current Locality-Based usTLD Policies Investigation and Report  

        NeuStar's approach to the Compliance Investigation and Report will forge good relations with locality delegees while solving many of the
problems that plague the current locality space.

B.4-8

 

        In
its request for an immediate investigation of policy compliance in the usTLD locality space, the DOC is sending a strong message about the current state of this space. Delegating
portions of localities within the usTLD hierarchy began as a logical method of maintaining the space and encouraging individuals within those physical localities to register domain names. However,
noncompliance by some delegees and specifically the problem of "locality squatting," have caused stagnation in registrations and have done little to promote the public interest aspect of the usTLD. 

        The
problem of locality squatting is prevalent across current locality delegations. According to current policy, for delegations or redelegations made after July 1, 1997, it is
assumed that every applicant for the delegation of a locality name has received written authorization from the locality's legitimate government to manage the domain name of that locality. Yet,
according to the current list of delegated subdomains and their contacts (available on the current usTLD Web site), approximately 40 percent of the delegated subdomains are held by five
individuals. Although a number of delegees who hold multiple locality delegations may be legitimate, that legitimacy is questioned when an individual delegee manages registries for localities in more
than 30 states. 

        This
compliance investigation effort is an excellent and necessary first step in improving usTLD operation and use. It will serve as more than just a report on compliance; it will also
aid efforts to create a partnership among the usTLD community for achieving stable, consistent service and for pursuing enhancements in the usTLD locality space. Because of the history of usTLD
administration, there is little information about current administration and operations. It is essential that a thorough investigation be performed to obtain a baseline for current information about
the status of usTLD operations, assess points of satisfaction and dissatisfaction among current delegees and current registrants, and enable NeuStar to provide recommendations to the DOC for
improvements by surveying current delegees and current registrants. 

        Without
this report, it will not be possible to ensure consistent and correct administration or operation of locality-based registrations within the usTLD. The existing problems in the
space will persist from an unclear, unresolved history with existing usTLD delegees. 

        Finally,
the stated goal for the Compliance activity is to establish a basis for moving to consistent quality of service for usTLD administration. However, investigation would be
appropriate even with a flawless history because it permits NeuStar to develop initial channels of communication with the existing usTLD community and to learn what changes and enhancements the
community desires. NeuStar anticipates that this investigation and report will be the first step toward codifying new technical and administrative policies and proposing a successor document to RFC
1480. 

 The Importance of Compliance  

        The usTLD portion of the DNS is as essential to the infrastructure of the Internet as any other portion of the DNS. Serious use of the Internet requires highly
reliable, highly stable, and highly efficient performance of the usTLD domain. Further, registrants and potential registrants in the usTLD must have assurances that they can register within their own
localities without encountering resistance or nonresponsiveness from the assigned delegee. To these ends, concerns for locality-space operations divide among: 

	•
	Technology and Operations—Modern, standard versions of DNS and registration protocols must be used, with
particular attention to recent security standards. Reliability and responsiveness of each DNS, Whois, and the registration process must be on a par with corresponding services elsewhere on the
Internet.

	•
	Administration—Quality, style, and access to registry and registrar customer services must also be on a par with
the recent, considerable improvements seen elsewhere in the DNS. 

B.4-9

 

	•
	Policies—The Domain Name Service is designed to support a variety of naming and operations models. However, there
is increasing support for some policies to be consistent across the entire DNS and for consistency among subsets of DNS activities.

	•
	Service—Service to registrants is of the utmost importance in ensuring that the locality hierarchy serves its
public service functions. Nonresponsiveness to customers and
resistance to serving those customers is an unacceptable practice. So, too, is unreasonable pricing for registration services. 

        Ultimately
there are four simple and direct needs that require assessment: 

	1.
	Historical
and current status and effectiveness of coordination and oversight for individual usTLD locality assignments. That is, for each delegee, an assessment must be made regarding
the method of operation and the effectiveness of that operation.

	2.
	Inconsistencies
in registry operation and in registered data. That is, a review must be undertaken across all usTLD locality assignments for differences in administration that would be
better to make consistent.

	3.
	Authority
of the delegee to run the delegated locality assignment. That is, if a delegation (or re-delegation) was made after July 1, 1997, the delegee should be
able to produce written authorization from the legitimate government of a locality to manage the domain name of that locality.

	4.
	Adherence
to the US Nexus Requirement, as outlined in Section B.3.1. 

 NeuStar's Approach  

        The new administrator of the usTLD domain will have a dual role. Although its main function will be to operate a registry for the usTLD root, it will also be
charged with continuing, expanding, and enhancing the usTLD domain. This latter role entails oversight, not just operations and administration. 

        There
are two approaches that a registry can take for oversight of the usTLD. One is top-down and authority-based, primarily entailing issuance of directives and checking for
conformance. The alternative is to treat the entire usTLD domain as an activity among partners, all seeking success for the stakeholders and satisfaction among the customers. NeuStar strongly believes
that an approach based on partnership will be easier to pursue and much more productive. Ultimately, a service is always collaborative, especially when the effort comprises multiple organizations. 

        An
approach based on partnership would be essential even with a flawless history. The "social" lesson of the Internet is that large-scale, multi-organization efforts must be based on
strong, consensus-based collaboration. Use of "authority" must be carefully limited, even to the extent of choosing not to use that authority if it is likely to cause ill will among participants.
However, the problematic history of usTLD makes this effort more sensitive and more difficult. We realize that there may be cases where a partnership approach may be unsuccessful, and we stand ready
to use a more authoritative approach, only if it becomes necessary. 

 NeuStar's Investigation Process  

        In order to conduct this compliance investigation, NeuStar will follow steps that are typical for survey research. 

 Planning Phase  

        In order to successfully conduct a compliance investigation and to ensure fairness to all parties, NeuStar will begin by reviewing all relevant documentation,
including RFC 1480, the post-1997 

B.4-10

 

agreement
with delegees, and any documentation provided to us by delegees. At the same time, NeuStar will request from the current usTLD registry all contact information for current delegees and
information on which delegees have signed the post-1997 agreement. This information is of vital importance to conducting a compliance investigation, because delegations or redelegations
made beginning in July 1997 follow different guidelines from those delegated before that date. 

        Once
this information is obtained from the current usTLD registry, a letter introducing NeuStar as the new usTLD registry will be sent to all delegees. This letter will be a formal
request for registrant and subdelegee data from the delegees and will include a request for a copy of the written authorization to manage the domain for each locality, for delegations or for
redelegations made since July 1997. The same letter will be sent to subdelegees to request registrant data under those suddelegations. 

        From
this effort, NeuStar will compile aggregate requirements for delegees, including subdelegees, and registrants and will begin our effort to find legitimate delegees. During this
time, we will also select an agency to conduct a compliance survey. 

        This
phase of activity will ensure that the investigation is based on existing history and, to the extent possible, based on the expectations of delegees and registrants. 

Design Phase  

        During the design phase, investigation questionnaires will be formulated for delegees, including subdelegees, and for registrants. The questionnaires will cover
the full range of administration and operations topics. Use of professional survey experts will ensure that the research tools employ proper wording to elicit helpful responses and otherwise avoid the
serious pitfalls often encountered with surveys developed by nonprofessionals. The surveys produced must be sufficiently open to permit participants to offer unexpected information and suggestions.
However, they will also be partially based on information that is already available, so that participants can be assisted with intelligent, directed questions and plausible solutions. 

        NeuStar
expects the survey to produce several types of useful information, including but not limited to: 

	•
	Legitimacy
of individual delegees;

	•
	Status
of current delegations, including adherence to current policies, policies outlined in RFC 1480, the usTLD web site and the US Nexus Requirement;

	•
	Changes
desired by delegees or registrants;

	•
	Status
quo desired by delegees or registrants; and

	•
	Identification
of nonresponsive delegees. 

        This
feedback will permit NeuStar to pursue a constructive, iterative process for obtaining a cure to problems, while maintaining stable operations. 

        As
noted earlier, it is essential that NeuStar approach the design of this survey as a means of finding ways to help delegees and serve them as customers of the usTLD registry. This
approach is in marked contrast to one that could be heavy-handed and oriented towards establishing authority and strictness. Such a heavy-handed approach would be likely to produce poor information
and strong resentment. It is expected that delegees will have concerns, and even fears, about the new administrator. NeuStar views it as appropriate and essential to allay those fears through a
constructive tone and process. 

B.4-11

 

Execution Phase  

        This phase is dominated by the mechanics of distributing surveys to delegees and registrants, ensuring they complete the forms, and then obtaining the completed
forms for processing. In cases where a delegee is nonresponsive, we will send a second request, followed by an attempt to contact the delegee by another method. 

Analysis  

        Structured portions of the surveys will be straightforward and will produce simple statistics. Open-ended portions of the survey will require the
skills of a professional survey researcher to ensure that answers are compiled in an appropriate and useful manner. 

Recommendations and Report  

        Beyond basic data analysis is the step of reducing the analysis to practical suggestions to remedy problems and pursue enhancements of the usTLD locality-space
policies. These may include recommendations on: 

	•
	Structure
of the locality hierarchy

	•
	New
policies for delegees to follow

	•
	New
cost guidelines for delegees to follow

	•
	Technical
aspects of the locality delegations

	•
	Methods
to enhance compliance among noncompliant delegees

	•
	Methods
of increasing the value of the locality-based structure to local communities as a public resource. 

        In
addition to presenting recommendations for changes in locality delegations, this report will, as required in RFQ Section B4, present a full evaluation of locality squatting issues.
Delegees who have proven their legitimacy by producing the requested letter of authorization will be listed, and carefully recorded information will be presented listing those delegees who contributed
to the investigation, as well as those who were nonresponsive to our requests. We believe that our partnership approach to this investigation will encourage participation in our survey, and it is our
hope that the vast majority of delegees will be responsive. We further believe that this investigation will serve as an excellent introduction of NeuStar's usTLD operations to current delegees, aid
efforts to create partnerships between the TLD and the delegees, and allow NeuStar to discover ways to improve the services offered in the usTLD locality space. Within six months of contract award, we
will file our report and recommendations with the DOC and post the report on the usTLD Web site, as required. 

B.4.6    usTLD Delegated Manager Database Development  

        NeuStar's Delegated Manager Database will ensure the accuracy and validity of all data for delegees and subdelegees.  

        Because of the administrative structure of the usTLD, that is, because there are a vast number of locality delegees and subdelegees (collectively known as
delegated managers), NeuStar will develop a database of delegated managers that will be kept accurate and up to date. This will be an integral element of the Centralized usTLD Database that NeuStar
will deploy as the usTLD Administrator. To manage a critical public resource like the usTLD, the Administrator needs an accurate database for all entities that have a role in administering the space,
and delegated managers play an important role in the functioning of the usTLD localities. Because the usTLD Administrator may need to contact a delegated manager for reasons ranging from network
outages to questions from a registrant, it is not 

B.4-12

 

acceptable
to have out-of-date contact information that prevents issues from being addressed in a timely manner. 

        The
most critical function with regard to creating the database is obtaining relevant information from the existing delegated managers—NeuStar has performed a similar
function before. The task at hand is analogous to NeuStar's undertaking in the transitioning of the North American Numbering Plan to centralized administration. In order to fulfill our duties, NeuStar
was required to create a centralized database of telephone number assignments by working with multiple phone companies across the country, most having multiple telephone number administrators. The
databases across companies were inconsistent, as were those within companies. NeuStar was able to collect and standardize all of the data, and completed the transition ahead of schedule. 

        In
order to ensure the accuracy and validity of the delegated manager data, NeuStar's Transition Team will reach out to all of the delegees and subdelegees. We will provide them with a
list of the data elements we wish to populate, and will provide them with multiple methods of provisioning this data with us. On an ongoing basis, we will provide the delegated managers an
easy-to-use web interface to provision new registrations into the Centralized usTLD Database. Alternatively, should they have high volumes of registrations and would prefer a
mechanized interface, they may opt to use NeuStar's eXtensible Registry Protocol, or XRP, to interface to the registry. 

        Information
in the Delegated Manager Database will, at a minimum, include the following: 

	1.
	The
name of the delegated manager;

	2.
	The
Delegated Manager ID;

	3.
	The
IP address of the primary nameserver and secondary nameserver(s) for the delegation;

	4.
	The
corresponding names of those nameservers;

	5.
	The
date of delegation;

	6.
	The
name and postal address of the delegated manager;

	7.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the delegated manager;

	8.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the delegated manager; and

	9.
	The
Web site or other contact information through which registrations can be accepted under the delegation. 

        As
required the information in NeuStar's usTLD Delegated Manager Database will allow for multiple string and field searches though a free, publicly accessible, Web-based
interface. 

        Detailed
descriptions of how the databases will be populated and how they will be kept up to date and accurate are provided in Section F, Centralized usTLD Database and Enhanced
Shared Registration System. 

        Redundant
Delegated Manager databases will be located at the geographically diverse, redundant Enhanced SRS Data Centers located in Illinois and Virginia. In accordance with U.S. Nexus
requirements, no databases will be located outside of the United States. Both databases will be updated in near real time (intervals of no more than 15 minutes) and will be synchronized. 

        A
detailed description of the technology and operations of the Delegated Manager Database is provided in Sections O.3 and O.9. 

B.4-13

 

B.4.7    Whois Database Development  

        NeuStar's centralized Whois database will accommodate public searches for registrant and delegated manager contact information and will
ensure the accuracy of data throughout the locality space.  

        The locality-based usTLD space has traditionally had no centralized Whois which makes it difficult to look up contact information for domain name holders, and
even for delegees. NeuStar will remedy the current deficiency by developing an enhanced, searchable, accurate, and up-to-date Whois database containing locality-based usTLD
registrant information. In fact, this Whois database will be common with the Whois database for the expanded usTLD space. 

        NeuStar
will maintain a Web site that will allow free public, searches of the Whois database, and will also provide a standard port 43 interface. As required by the COTR, the database
will allow for multiple string and field searches. These searches will return Whois records that will show a differentiation between a registrant's Whois record and a delegated manager's Whois record.
NeuStar will reach out to the existing delegees and subdelegees to populate information on their registrants in the databases. 

        NeuStar
will populate the data pertaining to the existing assignments by reaching out to each of the delegated managers through information provided by the current usTLD Administrator,
as well as with
contact information contained in existing zone files of the usTLD Administrator and of the delegated managers. At a minimum, NeuStar will collect and update the information described below for each
Whois record: 

	1.
	The
name of the domain registered;

	2.
	The
Internet Protocol (IP) address of the primary nameserver and secondary nameserver(s) for the registered domain name;

	3.
	The
corresponding names of those nameservers;

	4.
	The
identity of the delegated manager under which the name is registered;

	5.
	The
creation date of the registration;

	6.
	The
name and postal address of the domain name holder;

	7.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder; and

	8.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder. 

        More
detailed descriptions of how the databases will be populated, how they will be kept up to date and accurate, and the structure of the Whois responses are provided in
Section F, Centralized usTLD Database and Enhanced Shared Registration System. A detailed description of Whois policy is provided in Section B.3.5. 

        Redundant
databases will be located at the geographically diverse, co-active Enhanced SRS Data Centers located in Illinois and Virginia. In accordance with the U.S. Nexus
requirement, no registry databases will be located outside of the United States. All databases will be updated in near real time (intervals no greater than 15 minutes) and will be synchronized to
ensure consistency of responses. 

        A
more detailed, technical description of the usTLD database is provided in Sections O.3 and O.8. 

B.4-14

  

 
 

HIGHLIGHTS    
    

	•
	NeuStar
will leverage our Enhanced Shared Registration System and Centralized usTLD Database to promote registrar participation and registration in the usTLD expanded
namespace

	•
	We
will deploy a centralized Whois upon introduction of the expanded namespace

	•
	NeuStar's
centralized, automated processes ensure the continued integrity of data in the usTLD registry

	•
	Creation
of the us TLD Policy Council to assist in outreach efforts. 

B.5    Expanded usTLD Space Functions  

        NeuStar's functions for the expanded usTLD namespace will support an unlimited number of competitive registrars and encourage second-level
registrations in the namespace.  

        Although many users find the current usTLD hierarchical locality space to be valuable, or even essential to their presence on the Internet, the naming structure
is generally considered to be cumbersome. Expanding the usTLD space to allow registrations in the second level will encourage more registrations in the namespace, and open the usTLD to registrar
competition. 

        By
introducing this new namespace, we also introduce the need for functions related to a registrar community, including a shared registration system and registrar accreditation and
certification. Just as we have proposed in the locality namespace, we will leverage our Enhanced Shared Registration System (SRS) and Centralized usTLD Database, and implement an automated update
process and a modernized zone file update process for use in the expanded space. 

        The
expanded usTLD functions highlighted below and in Sections B.5.1 through B.5.5 include all of the requirements listed in RFQ Section B.5. In these sections, we emphasize our
desire to work with registrars throughout the accreditation and certification process, and our understanding of the need to develop a registry that the Internet community will consider to be valuable
and useful. 

        usTLD Enhanced Shared Registration System—NeuStar will leverage our eXtensible Registry Protocol (XRP) for interfacing
registrars to our Enhanced Shared Registration System (SRS). This Enhanced SRS will support an unlimited number of competitive registrars for the expanded name space, and will provide equivalent
access to the system for all registrars to register, transfer, and update domain registrations. 

        Accreditation Process for usTLD Registrars—NeuStar's registrar accreditation process will ensure consistency in quality and
service within the usTLD, while at the same time promoting stability and competition for domain name registration services. 

        usTLD Technical Certification Process—NeuStar's Operational Test and Evaluation (OT&E) process will verify the correct
operation and performance of a registrar's client system before access to the live Enhanced SRS is granted. This OT&E Certification will allow NeuStar to maintain the integrity of the usTLD and of the
DNS as a whole. 

        Whois Database Development—NeuStar's centralized Whois database will accommodate Web-based, free, public searches
for registrant and registrar contact information and will ensure the accuracy of data in the expanded space, beginning with the very first Whois entry in that space. 

        Community Outreach Plan—NeuStar will coordinate usTLD public outreach under the auspices of the usTLD Policy Council, which
will be very important to the ongoing development of usTLD policy and public outreach. 

        Expanding
the usTLD namespace will be one of the biggest steps in achieving the goal of increasing registrations and promoting competition in the space. Furthermore, the expansion of the 

B.5-1

 

usTLD
space affords NeuStar the unique opportunity to centralize all data and information from the inception of the new space. Whereas centralizing this information in the locality space must be done
by reaching out to existing delegated managers, all information in the expanded space will be centralized from the beginning, ensuring that all Whois and zone file information has the highest possible
levels of accuracy and integrity. 

B.5.1    usTLD Enhanced Shared Registration System  

        NeuStar will develop and implement an Enhanced Shared Registration System (SRS) that will support an unlimited number of competitive
registrars for the expanded name space. As required, this enhanced SRS will provide equivalent access to the system for all registrars to register, transfer, and update domain registrations.  

        NeuStar's Enhanced SRS will be developed according to a three-level architecture: protocol servers, application servers, and database servers (the Centralized
usTLD Database). Exhibit B.5-1 displays a high-level view of this Enhanced SRS architecture. Registrars will interface to the registry over the Internet to the protocol
servers located at redundant data centers in Illinois and Virginia. Registrars will be able to interface with either data center, and in the unlikely event of an outage to one data center, registrars
will still be able to interface to the other. This redundancy ensures that the Centralized usTLD Database will always be available for handling queries, registrations, and modifications. 

        Protocol
servers will authenticate registrars based on authentication information provided by the registry. For each registrar, a profile will dictate the access rights that will be
provided. This ensures that one registrar will not be allowed to view customer-sensitive information for any other registrar or to modify registration data for another registrar's registrant. 

        NeuStar's
protocol for interfacing registrars to a registry, called XRP (eXtensible Registry Protocol) has been developed and is currently being deployed for the .biz registry. XRP is
based on two very important Internet protocols, eXtensible Markup Language (XML) and Blocks Extensible Exchange Prototcol (BEEP). Both of these protocols, XML for the data schema and BEEP for the
transport layer, make it extremely easy to expand the functionality of XRP to include registrar and registry capabilities for the usTLD. 

        It
should be noted that the IETF Provreg Working Group, in which NeuStar is an active participant, is developing an industry standard interface between registrars and registries. XRP
will be functionally compatible with the standard developed at the IETF. 

        NeuStar
has already developed the tool kits for registrars interfacing with the.biz registry. Registrars that have been tested with XRP for .biz will need to go through only simple
testing to be certified for the additional functionality required for the usTLD. Assistance will be provided to registrars through an operational test-and-evaluation facility,
described in Section B.2.9, and technical support will be available for usTLD accredited registrars, by phone or via the usTLD Web site, on a
24 × 7 × 365 basis. 

        [Exhibit B.5-7:
Graphic Design] 

        NeuStar's
application servers contain the business rules that manage the registration data between the registrar and the registry. Simply stated, it acts as the interface between the
protocol server, which interfaces to the registrars, and the Centralized usTLD Database. It is the most complex element of the registry because of the complex business rules and the need for
real-time efficiency. NeuStar has a great deal of experience in building high-availability, complex systems to support critical public resources. Examples of these systems
include the Number Portability Administration Center, the National Number Pooling Administration Center, and the.biz registry. 

B.5-2

 

        A
detailed description of the functions of the Enhanced SRS is provided in Section F, Centralized usTLD Database and Enhanced Shared Registration System. 

        A
detailed description of the technical operations and facilities of the Enhanced SRS, including XRP and the Centralized usTLD Database, is provided in Sections O.1, O.2, and O.3 of this
proposal. 

B.5.2    Accreditation Process for usTLD Registrars  

        NeuStar will implement a simple registrar accreditation process to ensure consistency in quality and service within the usTLD, while at
the same time promoting stability and competition for domain name registration services.

        In
order to encourage the rapid implementation of the enhanced usTLD space, promote strong competition among registrars, and ensure the continued neutrality of the registry, while at the
same time promoting competition and stability for domain name registration services, NeuStar will use a straightforward, fair and efficient accreditation process for all usTLD registrars. Eligibility
to access the registry will be subject only to an accreditation application process and technical testing and approval by NeuStar technical staff, payment of a registrar accreditation fee, and the
execution of a usTLD Registrar Accreditation and usTLD Registry-Registrar Agreements. 

        All
registrars or potential registrars, including those who are already ICANN-Accredited Registrars, must become accredited to register domain names in the usTLD. A registrar need not be
an ICANN-accredited registrar to become a usTLD registrar. The usTLD Registrar Accreditation Process is illustrated in Exhibit B.5-2. The following bullets outline the basic
process: 

	•
	Apply for Registrar Accreditation. All registrars must complete and submit to NeuStar a usTLD Registrar Accreditation
Application. They must also must review the Application Instructions and the current usTLD Registrar Accreditation Agreement and Registry-Registrar Agreement. 

        [Exhibit B.5-2:
Graphic Design] 

	•
	Receive Notification of Registrar Accreditation. After completing its review of the accreditation application and conducting
any necessary follow-up inquiries, NeuStar will inform the applicant by e-mail of its decision.

	•
	Sign a usTLD Accreditation Agreement Once NeuStar has approved the applicant for accreditation, the applicant must execute a
usTLD Registrar Accreditation Agreement with NeuStar.

	•
	Sign a usTLD Registry-Registrar Agreement. Each applicant must also execute a usTLD Registry-Registrar Agreement.

	•
	Technical Certification Process. Upon execution of the necessary agreements, the usTLD Accredited registrar will begin
operational testing and evaluation utilizing the NeuStar provided Registrar Tool Kit. Upon receipt of approval from the NeuStar Technical Evaluation Team, the new
registrar will be eligible to access and register domain names in the usTLD registry system. This process is described in detail in Section 3.5.3, Technical Certification of usTLD Registrars.

	•
	Announcement of Accreditation. NeuStar will announce the accreditation, along with contact information for the newly
accredited usTLD registrar on its Web site, unless the registrar specifies that it would prefer, for business reasons, to postpone the announcement of accreditation. 

        Because
NeuStar proposes an open, shared registry for the expanded usTLD space, there will be no restrictions on the number of registrars permitted to register names in the system. 

B.5-3

 

        Copies
of the usTLD Registrar Accreditation Agreement and the Accreditation Application are attached at the end of this section. NOTE: The Application refers to Application Instructions
which will be developed by NeuStar and approved by the Department of Commerce prior to the commencement of the accreditation process. 

B.5.3    usTLD Technical Certification Process  

        NeuStar's process for Operational Test and Evaluation certification will test the capabilities of registrar systems before access to the
live Enhanced Shared Registry System is granted.

        In
order to maintain the integrity of the usTLD and of the DNS as a whole, it is necessary to ensure that registrars are technically competent and that their systems, which will
interface with the usTLD Enhanced Shared Registration System (SRS), are capable of operating and performing the required functions. To fill this need, NeuStar will develop and implement a process for
technical certification of registrars in the expanded usTLD space. 

        Before
a registrar would be given permissions to access the live usTLD Enhanced SRS, it will first need to pass NeuStar's usTLD Technical Certification Process, called Operational Test
and Evaluation (OT&E) certification. The purpose of this OT&E certification will be to verify the correct operation and performance of a registrar's client system. 

Preparations for OT&E Certification  

        The OT&E certification process will begin when a registrar becomes accredited by NeuStar to register names in the usTLD, at which point the registrar will enter
the usTLD registry provisioning process. This process begins when the registrar fills out a registration form. NeuStar will then send a usTLD welcome package to the registrar that will include
information to help implement its eXtensible Registry Protocol (XRP) client application for the Enhanced SRS. This package will also include the following: 

	•
	Username
and password to access the private members area of the usTLD Web site.

	•
	The
OT&E test bed server information and username/password for two accounts to access the usTLD OT&E test bed for registrar client testing.

	•
	Instructions
for downloading the XRP Registrar Tool Kit.

	•
	Instructions
for downloading the documentation for the XRP Registrar Tool Kit. This tool kit will be available to any interested party that would like to implement registrar
client applications.

	•
	Instructions
for downloading the XRP specifications and XRP Common Application Programmer Interfaces (APIs).

	•
	Instructions
on how to proceed with the OT&E certification process.

	•
	Instructions
on how to obtain an SSL certificate from an approved Certificate Authority.

	•
	Instructions
on how to provide the usTLD registry with the list of subnets that will be used to access the Enhanced SRS Test Plans and Procedures, which will explain the
test cases, test metrics, data collection, test data analysis, and reporting to be performed during OT&E verification. 

        The
registrar will be responsible for installing the XRP client application that will interface to the registry using the XRP. The registrar will interface the XRP client to the
back-office systems via the XRP common APIs. 

B.5-4

 

        Because
the registry-registrar communication channel will be encrypted, an SSL certificate from an approved Certificate Authority will be required to establish an SSL encrypted channel.
The username/password and subnet list will provide additional security; only a valid combination of an SSL certificate, username/password, and subnet will be allowed to access the live Enhanced SRS. 

        During
XRP client implementation, the registrar will have access to the Registry OT&E test bed environment. In the OT&E test bed, the registrar may test the operation of its software to
verify the correct handling of XRP commands, their responses, and notification messages. Operations performed in the OT&E environment will not be charged and will not have any impact on the live
Enhanced SRS. Registrars/Delegees will continue to have access to the OT&E test bed after certification, so that they may continue to test their back-office software systems. 

        When
a registrar has completed the testing of its XRP client and back-office systems and would like to proceed with OT&E certification, it will then contact the usTLD
Customer Service Center to schedule a time slot for an acceptance test. Time slots will be scheduled on a first-come-first-served basis. At the scheduled time, the
registrar will contact the usTLD OT&E Technical Support Team to initiate the certification. 

The XRP Registrar Tool Kit  

        The XRP Registrar Tool Kit is a software development kit (SDK) that will support the development of a registrar software system for registering Internet domain
names in the usTLD registry using the XRP registry-registrar protocol and the XRP common APIs. The SDK will consist of software and documentation as described below. 

        The
SDK will be used by the registrar as a basis for connecting to the usTLD registry test bed environment during OT&E and can also be used to develop a system for interfacing with the
live usTLD registry once the registrar has been certified. 

        The
software will consist of a working Java XRP common API and samples of interfaces to back-office systems that implement the XRP core functions and XRP extensions used to
communicate between the registry and registrar. The SDK will illustrate how XML requests (registration events) can be assembled and forwarded to the registry for processing. The software will provide
the registrar with the basis for a reference implementation that conforms to the XRP registry-registrar protocol. The software component of the SDK will also include XML schema definition files for
all Registry XRP objects and XRP object extensions. 

        The
documentation will also describe the XRP 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 SDK will be made available from time to time to provide support for additional features as they become available and support for other platforms and languages. 

OT&E Certification Test Cases  

        During OT&E certification, a registrar's client application will be required to demonstrate the proper execution of the following operations: 

	•
	SSL
connection establishment

	•
	XRP
<login> command

	•
	Change
of <login> password

	•
	XRP
<logout> command

	•
	Domain
name operations 

B.5-5

 

        -
Create domain without nameservers and without contacts (XRP Transform <create>) 

        -
Create domain with nameservers 

        -
Create domain with contacts 

        -
Create domain with maximum registration period 

        -
Create domain with maximum number of nameservers 

        -
Create domain with maximum number of contacts 

        -
Create domain with maximum length domain name (63 characters +.US) 

        -
Create domain with invalid name 

        -
Check domain (XRP Query <check>)—domain not available 

        -
Check domain (XRP Query <check>)—domain available 

        -
Check domain—maximum length domain name (63 characters +.US) not available 

        -
Query domain (XRP Query <info>) 

        -
Query domain transfer status (XRP Query <transfer>) 

        -
Delete domain (XRP Transform <delete>) 

        -
Renew domain (XRP Transform <renew>) 

        -
Transfer domain (XRP Transform <transfer>) 

        -
Change domain (XRP Transform <update>)—nameservers 

        -
Change domain (XRP Transform <update>)—contact 

        -
Change domain (XRP Transform <update>)—status 

	•
	Nameserver
operations 

        -
Create nameserver (XRP Transform <create>) 

        -
Create nameserver with maximum length host name (80 characters) 

        -
Check nameserver (XRP Query <check>)—nameserver known 

        -
Check nameserver (XRP Query <check>)—nameserver unknown 

        -
Query nameserver (XRP Query <info>) 

        -
Delete nameserver (XRP Transform <delete>) 

        -
Change nameserver (XRP Transform <update>)—add IP address 

        -
Change nameserver (XRP Transform <update>)—remove IP address 

	•
	Contact
operations 

        -
Create contact (XRP Transform <create>) 

        -
Check contact (XRP Query <check>)—contact known 

        -
Check contact (XRP Query <check>)—contact unknown 

        -
Query contact (XRP Query <info>) 

        -
Query contact transfer status (XRP Query <transfer>) 

B.5-6

 

        -
Delete contact (XRP Transform <delete>) 

        -
Transfer contact (XRP Transform <transfer>) 

        -
Change contact (XRP Transform <update>)—change element 

        -
Change contact (XRP Transform <update>)—remove element 

	•
	Registrant
account operations 

        -
Create registrant account (XRP Transform <create>) 

        -
Check registrant account (XRP Query <check>)—contact known 

        -
Check registrant account (XRP Query <check>)—contact unknown 

        -
Query registrant account (XRP Query <info>) 

        -
Query registrant account transfer status (XRP Query <transfer>) 

        -
Delete registrant account (XRP Transform <delete>) 

        -
Transfer registrant account (XRP Transform <transfer>) 

        -
Change registrant account (XRP Transform <update>)—change element 

        -
Change registrant account (XRP Transform <update>)—remove element 

	•
	Effectiveness
and utility of client session management and information exchange

	•
	Performance
of client session management and information exchange throughput. 

        NOTE: The Registry will reserve the right to change the OT&E certification requirements as necessary to ensure compliance with the evolving XRP protocol and XRP
common APIs.

Post OT&E Certification  

        All tests performed during OT&E certification must be completed without errors. The registry will provide the certification results in a timely manner and provide
feedback for those registrars that failed to successfully complete the tests. Those registrars may correct their systems and reschedule for certification. Registrars will not be limited in the number
of attempts at OT&E certification. 

        Upon
successful OT&E certification, the registrar will become eligible for operation in the live Enhanced SRS. A new username and password will be assigned, and the NeuStar will
configure the live system to recognize the SSL certificate, username, password, and subnet blocks for the registrar. 

B.5.4    Whois Database Development  

        NeuStar's centralized Whois database will accommodate public searches for registrant and registrar contact information and will ensure the
accuracy of data throughout the usTLD namespace.

        The
locality-based usTLD space has traditionally had no centralized Whois, which made it difficult to look up contact information for domain name holders. But the usTLD expanded space is
new, and we have the chance to implement an enhanced Whois database for that space that will be accurate and up to date from the very first registration in that space. NeuStar will develop and
implement an enhanced Whois database that will contain information about all usTLD registrations, registrants, and registrars active in the usTLD namespace. NeuStar's usTLD Web site will provide
access to both the locality and expanded Whois databases; Whois will also be available through a standard port 43 interface. 

B.5-7

 

        In
accordance with the RFQ, the Whois database will allow for multiple string and field searches through a publicly available, Web-based interface. Query returns will
indicate the Whois database being accessed, and whether the record is for a registrant or a registrar. Access to the database through the Web site and through port 43 will be free of charge and
available to the public. 

        Populating
the Whois information in the expanded space will be done through the registrar at the time of registration. Registrations will not be considered complete without all of the
appropriate information being provided. 

        At
a minimum, NeuStar will collect and update the information provided below for each type of Whois record in the expanded space: 

        Registrant
Whois information in the expanded namespace will include the following information: 

	1.
	The
name of the domain registered;

	2.
	The
IP address of the primary nameserver and secondary nameserver(s) for the registered domain name;

	3.
	The
corresponding names of those nameservers;

	4.
	The
creation date of the registration;

	5.
	The
name and postal address of the domain name holder;

	6.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder; and

	7.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder. 

        Registrar
Whois information in the expanded space will include the following information: 

	1.
	The
name of the registrar;

	2.
	The
Registrar ID;

	3.
	The
registrar status (e.g., active, pending);

	4.
	The
name and postal address of the registrar;

	5.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the registrar; and

	6.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the registrar; and

	7.
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the billing contact for the registrar. 

        Detailed
descriptions of how the database will be populated, how it will be kept up to date and accurate, and the structure of the Whois responses are provided in Section F,
Central usTLD Database and Enhanced Shared Registration System. A detailed description of Whois policy is provided in Section B.3.5. 

        Further,
to ensure the integrity and highest levels of service for Whois administration, redundant databases will be located at the geographically diverse, redundant Enhanced SRS Data
Centers located in Illinois and Virginia. In accordance with the U.S. Nexus requirement, no usTLD registry databases will be located outside of the United States. Both databases will be updated in
near real time (intervals no greater than 15 minutes) and will be synchronized to ensure consistency of the response. 

B.5-8

 

        A
more detailed technical description of the database is provided in Sections O.3 and O.8 of this proposal. 

B.5.5    Community Outreach Plan  

        NeuStar has a strong history of facilitating discussion among stakeholders while ensuring it does not become a barrier to progress in the
public interest. NeuStar will bring this experience to bear in the usTLD.

        Administration
of public resources, whether they are telephone numbers or domain names, requires strong awareness of constituencies and their needs. Thus, community outreach is a
critical element in such administration. In addition, however, an administrator also must have the experience and resources to ensure that public outreach, discussion and input do not becomes barriers
to meeting project objectives. An inexperienced administrator might not recognize this important distinction. The distinction is, however, critical to the success of the usTLD, for without strong
coordination of the outreach process itself, enhancement and development efforts for the usTLD will stagnate. 

        NeuStar
has a strong legacy of coordinating complex groups of users in the industries that it serves. NeuStar intends to establish targeted communications mechanisms, including
e-mail listservs, chat services, and other Internet-based services whereby the public can suggest or recommend either additional policies and procedures or modifications to existing ones.
In addition, NeuStar will utilize traditional customer outreach, such as users group meetings, user support representatives, and other support services to maintain close relationships with usTLD users
and the public. 

        NeuStar
proposes the creation of a usTLD Policy Council to assist in the development and implementation of usTLD outreach, among other functions. This council will be very important to
the ongoing development of usTLD policy and public outreach. The structure and duties of this council, as well as the detailed outline of our basic outreach plan, are discussed in detail in
Section B.3.5 herein. 

B.5-9

   C.    NeuStar's Vision of the usTLD  

        NeuStar will elevate the usTLD to be as widely relied upon and responsive to demand as all other US public
resources.

	•
	NeuStar will position the usTLD as a citizen-centric name space

	•
	Functional attributes of NeuStar's registry will enable numerous applications and services to meet the needs of its
constituency

	•
	NeuStar is uniquely qualified to administer the usTLD in a responsible and even-handed manner

	•
	Combined, these measures will ensure integrity and wide adoption of the usTLD

        By
its very nature, a ccTLD denotes a sense of nationalism, generates a mental image in ones mind of that country, and establishes an impression about that country's relative position in
technological advancement. A ccTLD can only do this, however, if it is managed and developed to benefit the needs of its user community—the citizens and government bodies of that country.
This takes more than a nexus requirement, more than random newspaper advertisements, more than a commonplace central administrator. It requires a comprehensive business plan that will fulfill the
vision of elevating that ccTLD into the next generation of the Internet—a place where people communicate with one another, with their government, with their local businesses, in a stable,
secure and readily accessible environment. NeuStar has such a vision for the usTLD. 

        The
body of NeuStar's response enumerates the tools we will use to fulfill this vision—a thick registry architecture that operates at the highest levels of availability and
security, the coordination of disparate user communities under a stable, centralized umbrella, a phased and customer-focused outreach program to propagate the need for dot-us domain names,
the introduction of enhanced services and the enablement of new advanced applications. The response also illustrates NeuStar's commitment to operate the usTLD in a responsible manner—open
communication between the administrator and the DOC, willingness to seek user feedback, the formation of a representative policy council to act as a check point in the development of policy and
introduction of various applications and services, an advisory team representative of multiple constituency interests and consisting of pioneers in Internet technology and user constituencies. 

        NeuStar's
ability to perform each of the prescribed mission critical public resource functions is reinforced time and again—experience transitioning the North American
Numbering Plan and coordinating over 3,000 carriers, creation of the Number Portability Administration Center and integration of hundreds of users, and the design for a next generation Internet
registry. 

        This
section of NeuStar's response is dedicated to describing our vision for the usTLD and illustrating how our infrastructure, our position as a neutral third party, and our experience
will execute that vision. This section describes the image of the usTLD today, tomorrow and years from now. It is a roadmap for successful evolution of the usTLD into a revered domain name space. 

Representation of the usTLD  

        The repurposing of ccTLDs has become almost commonplace—efforts that ignore the needs of a country citizenry in order to take a name space into the
realm of the gTLDs. The reasons behind the moves are purely commercial, and serve only the economic interests of the participants. Promoting the utility of the usTLD in an effort to drive
registrations should not be confused with administering the space like a gTLD, something akin to repurposing. While a ccTLD deserves to have the technical and operational functionality of a gTLD, it
has a very different purpose. A ccTLD must have fulfilling the needs of its user community, its citizens, as its top priority. 

        NeuStar
will implement a US nexus requirement to encourage all registrations be made by registrants with a valid US address or bona fide presence in the U.S. Additionally, by requiring
proof of delegation in the current locality-based structure, we can promote the use of locality hierarchies by 

C-1

 

their
rightful community. This is the first step in representing the usTLD as truly being the name space of its citizens. 

        Once
the user community is defined, the next phase of proper representation of the usTLD is enabling applications and services that benefit those constituencies. These services can serve
a subset, a superset, or the entire user base. There should be no limitation on the application areas, no limit on the benefit from the usTLD. (Examples of services and applications can be found in
Section D of NeuStar's response.) By enabling applications that serve the public interest within a ccTLD, the space inherently becomes citizen-centered. NeuStar's proposed enhancements reflect
a commitment to enhance the usTLD to serve its unique user community. 

        NeuStar's
vision for the representation of the usTLD has a strong constituency focus; a name space with the needs of the user community at the core of its design and operational
philosophies. The usTLD should be revered as the most innovative ccTLDs and a vital U.S. public resource. 

Integrity of the Infrastructure  

        NeuStar's response highlights our commitment to providing a next generation registry architecture. Simply, what this means, is that NeuStar has actively reviewed
the current legacy systems, the similar registry work we perform as a part our existing businesses and balanced that with the needs of registrars and the end-user community to scope a
platform that is more stable and more flexible than what is known today. This sort of evolution is natural in every industry, and the Internet is at a migration point; the usTLD must utilize a next
generation design and lead the progression. 

        There
are many technical facets of the NeuStar design that qualify it as 'next gen', but it is how these facets will enable advancement in
the space that is truly visionary. One feature represents the shard dimension of our registry—a 'thick' registry model that utilizes an extensible protocol based on XML, standardizes and
centralizes Whois information and requirements, supports numerous data fields 'objects', and provides near real-time DNS and Whois updates. A second technical feature is that NeuStar is
using a database structure that treats data fields not as independent, stationary pieces of information, but as 'objects', dynamic components that can be integrated at any point of the database
lifecycle, that demonstrate ever-changing relationships between data and maximize scalability. 

        To
the end-user, the technical design of the registry is not as relevant as the way they can utilize it. The benefits to the end-user include: 

	•
	Assurance
that a query to a name within the usTLD will resolve to its appropriate site, regardless of its level in the hierarchy, i.e., any domain name with a.us extension
is resolvable;

	•
	Any
information registrants provide to the registry (either directly or indirectly through a registrar) will be secure and follow guidelines for confidentiality, i.e., data
will be collected on an opt-in basis;

	•
	Enhanced
services can be introduced to serve a variety of public interest initiatives, i.e., including creation of public interest hierarchies and directories that can
assist in identification of desired information;

	•
	Digital
security and trust initiatives at a local level, i.e., user-prescribed permissioning and authentication; and,

	•
	New
protocols and changes to the DNS will be supported and are less likely to have adverse affects on the registry, i.e., the progression to IPv6 addressing. 

        NeuStar's
Internet registry architecture is flexible and scalable by design, and based on an open protocol standard available to developers across the US. The usTLD should be open to any
applications that will benefit the user community, as long as they maintain the integrity of the overall infrastructure. The responsible introduction of enhanced applications is facilitated by
utilizing standards created by subject matter experts. The usTLD should become a space for continued evolution of 

C-2

 

Internet
technology, further strengthening the U.S. perception in the world as Internet pioneers. The NeuStar design enables this evolution. 

        NeuStar's
vision of the usTLD infrastructure is that of a platform renown for its high standards of technological excellence. The security, stability, and reliability of the architecture
will foster the introduction of numerous applications and services on the open protocol platform. 

Integrity of the usTLD Administrator  

        Selection of an administrator is a multi-faceted analysis of technical and operational capabilities, as determined by past performance and the specifications
defined for the usTLD, the commitment to protecting IP and personal information, as well as the standard the administrator will set for the usTLD in general. The usTLD administrator must be a trusted
entity that is known for coordinating numerous interests with proprietary systems into single platform, protecting confidential data, taking efforts to promote competition—effectively,
being a trusted neutral third party. 

        The
reputation of the usTLD administrator will have a role in shaping the overall image of the usTLD, and therefore the selected administrator must be a responsible member of the
Internet community. NeuStar is uniquely qualified to fit this role through our past and present performance: 

	•
	Committing
to not directly compete with our customers, specifically here, to be a registry operator and not a registrar in the expanded space;

	•
	Openly
supporting a single authoritative root, managed by ICANN, whereby all TLDs are used for their intended purposes; and,

	•
	Participation
in the IETF, specifically leading efforts to shape more flexible and less burdensome registry-registrar protocols. 

        These
are more than a list of random guidelines; they represent a commitment to being a neutral, trusted third party. This represents a starting framework that the administrator of the
usTLD should live by. An administrator must be a respected member of its community to effectively, coordinate and manage the usTLD in such a way as to create a valuable public asset for the United
States. 

        To
alleviate administrative burdens on the DOC, NeuStar do proposes the formation of an advisory council that can make recommendations on issues and new enhancements that have a material
impact on the policy of the usTLD. Part of this group's function is to offer an additional level of checks and balances to ensure the administrator is abiding by its code of conduct in the
introduction of policies and changes to the usTLD. 

        NeuStar's
vision of itself as administrator of the usTLD is as an enabler, that is, the facilitator for introducing applications and services all the while monitoring the needs of its
constituencies. The administrator must perform many roles, and each must be carried out in a responsible and even-handed manner. 

Anticipated Demand for the usTLD  

        Like the many models of ccTLDs that have opened before it, the usTLD is expected to generate a national interest and create a desire among public and private
bodies to secure usTLD domain names. Our vision for the usTLD will promote similar market adoption. NeuStar has reviewed our primary research (as presented in Section B2.8 of NeuStar's response) and
numerous points of secondary research to develop a forecast of demand for the usTLD. We assume there are many needs and user groups of the usTLD, and apply varying penetration factors against those
addressable markets. 

        Thus,
NeuStar anticipates the following demand (in millions) for the usTLD: 

	 
	 	Contract

Year 1
	 	Contract

Year 2
	 	Contract

Year 3
	 	Contract

Year 4

	Names Under Management	 	1.39	 	4.20	 	6.81	 	9.63

        These
projections are considered a moderate estimation; we recognize the names under management in the registry could be lower or higher. Given growth rates in other ccTLDs that have
been migrated to a more open space and have easier registration process, we feel these projections outline a scenario where the usTLD has gained broad market acceptance. 

C-3

 

D.    Enhancing the Utility of the usTLD  

        The phased introduction of new applications and innovations in a responsible manner to further the enhancement and utilization of the
usTLD will be a core function of NeuStar's administration of the space.

	•
	NeuStar's Internet Registry is uniquely developed with the ability to enable enhanced utility and services

	•
	NeuStar Service Levels meet and exceed those required to manage usTLD public resource enhancements

	•
	Use of standards-based protocols furthers the potential for developers to create new applications

Introduction  

        NeuStar has actively followed the domain name space for over three years—both the generic TLDs and the usTLD. Our involvement in the Internet
community and active participation at ICANN, IETF, and other standards-making bodies provide the requisite understanding of Industry needs in the near and long-term. Subsequently, our
Internet Registry architecture was shaped by the Industry desire to have a highly reliable, secure, scalable, open-protocol platform that will allow for the seamless introduction of
enhancements. 

        NeuStar
will leverage the following technical advancements and business commitments to enable a variety of enhanced services. 

        NeuStar
will dedicate resources to enable the numerous applications that the U.S. public and private sectors can utilize through a responsibly managed addressing scheme within the usTLD.
The new service enablers would be optional and made available for use both in the new expanded space and the existing hierarchical space. We present below a brief summary of enhanced applications that
could be enabled by integrating the combined strengths of a U.S.-centric addressing space and NeuStar's next-generation thick registry platform. NeuStar has gauged market demand and has
actively been developing the ability of its thick registry to uniquely enable these application areas. To this end, NeuStar also proposes a fair and responsible process for enabling these enhanced
services while maintaining the integrity of the usTLD. 

Enabling Enhanced Services  

        Thick Registry—NeuStar's industry-leading, next-generation thick-registry architecture
provides the flexibility required to introduce innovative private and public services that meet the needs of the U.S. Internet community. An extensible "thick" structure means that an unlimited number
of fields of information can be maintained in the registry database in order to enhance utility and facilitate the delivery of enhanced services. These extensible information fields are a key enabler
for the delivery of opt-in services to end users by registrars, resellers, delegees, and service providers. 

        High Reliability—NeuStar has a proven record of managing mission-critical public resources. NeuStar has developed highly
reliable infrastructure that is well suited to the consistent delivery of enhanced services within the usTLD. 

        Highly Secure—NeuStar's experience in securing mission-critical infrastructure, such as the Local Number Portability database,
is reflected in the registry platform. NeuStar will implement a trust infrastructure, comprising both security technology and business processes, to ensure the integrity, accuracy, and privacy of the
data in the registry. These attributes are critical for the delivery of enhanced services. 

D-1

 

        Open Standards—NeuStar's registry infrastructure makes use of approved open protocol standards. This approach is optimal in
terms of the ability of registrars, resellers, and delegees to interface with the registry and also facilitates the development of new services. A standards-based
approach will maximize the number of sales channels guaranteeing greater public awareness, access to the usTLD domain, and development of innovative services. 

        Marketing Investment—NeuStar has the financial resources and is committed to making the necessary investment in marketing and
promotional activities to ensure widespread awareness of enhanced service enablers. This approach will tap into the entrepreneurial energy and public-service spirit of the American people and will
lead to innovative services that are responsive to the needs of the U.S. community. 

        Neutrality—Consistent with NeuStar's trusted neutral third party status and Code of Conduct (See Section B.3 for
details), NeuStar will make all of the enhanced service enablers available on an equal and fair basis to all members of the U.S. Internet community. 

        NeuStar
has been validating the potential utility of these service enablers from a technical and market perspective. These "enablers" are intended to facilitate applications that are
provided to businesses, organizations, and citizens via registrars, resellers, delegees, and service providers. We will provide an overview of the following Enhanced Services for which there is market
demand and that our Internet Registry can uniquely enable. 

	•
	Public
Resource Domains

	•
	e-Government

	•
	Directory
Services

	•
	Personal
Identification Services

	•
	Location-based
Services 

        NeuStar
anticipates working with a broad base of representative organizations and government agencies to identify additional services that unlock the utility of the usTLD to serve the
American Internet community. 

Process for Enabling Enhanced Applications and Services  

        NeuStar has a history of managing shared public resources while simultaneously introducing enhanced features and functionality in a
responsible and even-handed manner. These neutral and responsible practices will be mirrored in the introduction of enhancements in the usTLD.

        NeuStar
will manage the introduction of new enhanced services and applications in an open, neutral, and responsible manner. The usTLD will be well suited to serving the interests of the
public—the way the government, citizens, business, and organizations communicate and interact. In many instances, NeuStar simply will enable enhanced services offered by others that
leverage the combined benefits of the usTLD address space and NeuStar's technically advanced registry. In these instances, no change in policy will be warranted. Nevertheless, NeuStar will follow a
strict process for the introduction of any new services. All new services will be analyzed for their technical and operational feasibility, and receptiveness to the usTLD existing or potential user
base, and will be openly discussed within a proposed usTLD Policy Council. The Council will provide policy comments and recommendations concerning the proposed new enhanced services. A detailed
discussion of the Council is found in Section B.3.5. 

        The
technical evaluation criteria will include, but is not limited to, ensuring that service level agreements will continue to be met or exceeded, that interested parties needs are met,
and that intellectual property rights and registrant privacy is protected. 

D-2

 

        After
NeuStar affirms the feasibility of a new service, it will seek approval by the DOC for implementation. NeuStar will develop a document to assist in the approval process; this
proposal will include a description and price of the enhancement. As shown in Exhibit D-1, NeuStar will comply with the request to have all new services approved by the DOC. 

Public Resource Domains  

Public Need  

        The current locality structure generates lengthy names that are difficult to remember, but this is most notably because the requisite contextual information is
typically beyond the fourth level. While we will be taking direct second-level registrations as the administrator of the usTLD, we propose to explore the management of "public resource" domains that
serve as a common naming scheme to allow for convenient and consistent naming of various public interests and services. These condensed hierarchies afford Internet users the opportunity to easily
locate the information they seek without complicated trial-and-error searching. They will cross many district or state lines and be relevant to all citizens of the United
States. 

        The
usTLD is quite naturally the proper TLD for establishing such a condensed hierarchy, since the purpose would be to serve the American public. 

Enhanced Services  

        Numerous second-level domain names could be reserved to create unique and content-specific spaces on the Internet to serve a variety of citizen-centric public
interest needs. NeuStar can responsibly manage the third-level registries for each of these name spaces, through a sponsor approved by the usTLD Policy Council and the DOC, to maximize the overall
utility of the second-level name. 

        The
domain names could be registered through the sponsoring, name-specific channel that has an interest in the preservation of the name for a specific use. An example of a
public resource hierarchy NeuStar could manage for the benefit of the U.S. public includes: 

	•
	Park.us—a single reference point for all parks—national, state, or local—that are
physically located in the United States, where the name of the park is registered at the third level (e.g., arcadia.park.us, everglades.park.us, or grandcanyon.park.us). Currently, because our U.S.
parks fall under various jurisdictions, they are governed by disparate bodies, and do not have a single reference point to provide direct resolution. Park.us could offer a
common structure for citizens to gather information about any U.S. park under a memorable naming convention. 

[Exhibit D-1:
Graphic Design] 

        Other
examples of second-level domain names NeuStar could manage (i.e., NeuStar would take third level registrations for the sponsored second level): 

	•
	Vote.us—the
name space dedicated to campaign information and potentially a future forum to enable online voting

	•
	Veterans.us—a
reserved structure dedicated to the needs of U.S. Veterans. Organizations that provide informational resources and services that are relevant to
Veterans might register within this space.

	•
	Kids.us—A
"safe" space on the Internet that is specifically tailored to the needs of children. To avoid improper use of the space, a third party sponsorship
approach likely would be utilized.

	•
	Healthcare.us—a
naming structure designed to allow citizens to locate and access healthcare services and programs and to facilitate HIPPA compliance. 

D-3

 

	•
	Library.us—an
area of the Internet where citizens can identify libraries

	•
	Zip.us—A
space in which zip codes can be utilized to enhance navigation or to provide location-based services. Citizens could then easily locate local government
resources and services. 

        By
having a single administrator for these public service domains, the user community will better associate the domain name space with the high standards and reliability of the NeuStar
registry. This will further the notion of the usTLD as a trustworthy space managed for the benefit of the U.S. public, a ccTLD that propagates the U.S. image as the pioneers of the Internet. 

NeuStar's Enabling Role  

        The NeuStar registry is uniquely positioned to manage these public resource hierarchies through the design of our Internet registry. The registry will manage
domain names at any level with equal standards for reliability and security, for the same competitive price. NeuStar will extend its infrastructure to the third and fourth level domains to ensure
highly reliable and secure namespaces. Additionally, because these hierarchies will be centrally managed, NeuStar can provide directory services to facilitate user searching. 

Recommended Process  

        NeuStar has proposed a draft list of names for reservation by the usTLD Administrator (see Section B.3.5) and would work with the proposed Council and DOC
to introduce enhanced services for these namespaces in a fair and responsible manner. We will also conduct additional outreach activities to identify other namespaces that would serve the public
interest and to identify potential sponsors where appropriate. NeuStar will actively seek comment and input from delegated managers and organizations currently utilizing the existing hierarchical
space or with a public interest in the space prior to the introduction of Public Resource Domains. 

        NeuStar
will develop a document to assist in the approval process. NeuStar will comply with the request to have all new services approved by the DOC. 

E-government  

Public Need  

        The usTLD should be utilized to support the directive from the White House to "use the Internet to create a citizen-centric government." As more government
agencies move critical components of their operations online, the need for a secure space increases. Moreover, an addressing infrastructure is a key enabler for a capability that allows citizens to
find and access government informational resources, services and e-Gov applications. 

        In
tandem to initiatives to provide a more secure platform for e-government initiatives, attempts are being made to streamline government processes and increase government
efficiency. Our Internet registry architecture, our unique position as a trusted neutral third party, and our commitment to fulfillment of the US Nexus requirement uniquely positions NeuStar to meet
this need. NeuStar will work very closely with the U.S. federal, state, and local governments to enable their requisite e-government initiatives. 

Enhanced Services  

        Several e-government applications and services can be responsibly enabled through NeuStar's coordination and management of the usTLD. The primary
objective of these online application areas is to allow citizens to interact with the government in a direct, secure forum. According to a study by the Council for Excellence in Government, the
majority of Americans feel that e-Gov would have a 

D-4

 

positive
effect on government. Many such initiatives are underway today: motor vehicle administrators allow for license and registration renewals, public safety organizations take payment for fees and
services, the Internal Revenue Service accepts tax forms via their secure site. Future e-government applications enabled by the usTLD addressing mechanism could include: 

	•
	Enabling
direct communication between elected officials and their constituencies,

	•
	Introducing
a naming structure to streamline any processes whereby individuals are required to populate standard forms and submit to a government agency,

	•
	Facilitation
of public forums or "town hall" meetings to open forums for all citizens, including those who are not physically able to attend, and

	•
	Providing
an addressing structure for centralized procurement facilities or exchanges for state and local governments to maximize purchasing power. 

        Because
of the critical nature of e-Government applications, it is crucial that the usTLD administrator have demonstrated technical expertise, real-world
operating experience, an established position as a trusted neutral third party, and the ability to provide a highly reliable and secure environment. 

NeuStar's Enabling Role  

        Because the NeuStar platform is being developed to perform at high levels of service availability and will employ encryption technology, it is a logical domain
space for all U.S. governmental bodies—national, state or local—to develop their critical online initiatives. NeuStar currently manages a mission-critical public resource for
the communications industry (e.g. the public switched network relies on NeuStar numbering databases), and is prepared to do the same for the public sector through administration of the usTLD. 

Recommended Process  

        NeuStar proposes to work with the usTLD Policy Council and the DOC to conduct an outreach program, which will include current e-Government service
providers, to identify ways in which the usTLD addressing scheme can be leveraged to enable e-Gov services that reduce government cost, improve accessibility and productivity, and serve
the American people. 

        NeuStar
will develop a document to assist in the approval process. NeuStar will comply with the request to have all new services approved by the DOC. 

Directory Services  

Public Need  

        One of the primary enhanced services NeuStar proposes for increased ease of use of the usTLD is directory services. We propose to evaluate, trial, and implement a
series of sophisticated directory search capabilities for services and sites on the usTLD. The primary reason the existing locality-based hierarchical structure is awkward to use is the absence of a
comprehensive search capability for users to locate the service of interest without having to know the exact fully-qualified domain name. While numerous search engines exist in the Internet, none of
them allow the user to pre-select U.S.-based services, specifically ones meeting the Nexus requirement or that are named using the usTLD. Consequently, prospective users must wade through
long and confusing lists of services across the entire Internet to find the specific one of interest. The presentation order and content is dictated by the search sites' commercial policies, not
necessarily the public interest. 

D-5

 

Enhanced Services  

        A directory service for the usTLD would provide not only a separate navigational schema for the TLD while retaining the existing locality-based name structure,
but would provide a usTLD-specific search capability that doesn't currently exist elsewhere, and provide for consistency and uniformity in the listings of usTLD entries. This is extremely important
for government services accessed through the locality structure, as there is no pervasive user-friendly government-service-specific directory today. Commercial search sites intermix
listings for government and commercial sites, obscuring which services are official government services versus similarly listed commercial services, thus confusing potential users and causing
potential security and fraud problems. 

        One
of the first objectives would be to establish a keyword schema for categorization and characterization of the existing usTLD entries, and the primary service associated with each
entry (URL using the usTLD). The keyword to URL mapping forms the core of the directory, along with appropriate fields from the Whois data. This data can then be searched from the web, using any
number of attributes (service name, offering entity name, associated locality info, e.g. state or county), at a site to be established, e.g. http://www.search.nic.us/. In addition, it is possible to
re-direct web inquires to non-existent (incorrect) usTLD names to the
search site to solicit the user to navigate to the site of interest through the directory instead. This type of mechanism makes the directory an automatic help capability and significantly aids in
usTLD usage. Users would be encouraged to add a site to their bookmarks to streamline navigation in the future. 

        In
addition to a web-based search capability, NeuStar would propose to also provide directory listings online accessible via standard (IETF) directory protocols such as LDAP,
and newly emerging so-called fuzzy search protocols such as CNRP (common name resolution protocol). Lastly, NeuStar could also make the directory database available to commercial search
sites to increase accuracy and usability of usTLD data they have. 

        Lastly,
a comprehensive directory search capability makes it possible to facilitate foreign language navigation to these same sites. In some areas of the U.S. foreign language (e.g.,
Spanish) access is important and even mandated. Keywords and directory listings in other languages in addition to English of the same usTLD sites will facilitate these important local policies. 

NeuStar's Enabling Role  

        The enablement of directory services by the NeuStar thick registry within the usTLD would provide an important mechanism by which both the private and public
sector users could easily find information, products, and services provided by companies within the United States. Furthermore, this capability would allow citizens to easily find public services and
interact with local, state, and Federal government agencies. 

Recommended Process  

        NeuStar proposes to work with the proposed usTLD Policy Council and the DOC to fairly and responsibly implement Directory Service enablers within the usTLD
addressing structure. Both public and private sector directory needs will be pursued. 

        NeuStar
will develop a document to assist in the approval process. NeuStar will comply with the request to have all new services approved by the DOC. 

D-6

 

Personal Identification Applications  

Public Need  

        Over 116 million Americans are online, and each could utilize a unique personal identifier in their browsing, purchasing, or other use of the Internet.
Effective use of the usTLD, in the interest of the American people, should include protection mechanisms so any American citizen could elect to register a unique personal domain name tied to any
information they wish to associate with themselves for use on the Internet. These names could be the key for streamlining access to information, reducing the need to re-enter
identification information to sites that are not secure, or for dynamic assignment between sites or platforms. 

Enhanced Service  

        The need and market for various forms of globally unique, administered namespaces is well understood within the Industry. The use of "distinguished keys" is a
well-known concept that we all use in various contexts. The most obvious one is the use of Social Security numbers as a "distinguished key" that links data about us in various contexts.
The overuse of the SSN in various industries has created substantial concerns about privacy, formalizing the need for other forms of nationally unique identifiers. As we move online, an addressing
system such as the DNS, which provides a one-to-one unique resolution, is a logical mechanism, and the usTLD a logical extension for U.S. citizens. 

        The
core value proposition is the creation of namespaces directly under the control of consumers that can be "dynamic," in the manner in which they are accessible across a variety of
applications. The product offered to the consumer will be the opportunity to obtain a domain name during the registration process that could be used for: 

	•
	Applications
where personal name and identity is not required or suitable;

	•
	Permissioning
of information established by a custodian of the name-holder, i.e., a parent, to limit access to information; or

	•
	Permissioning
of information from the name-holder to those trying to access their information. 

        The
name, coupled with digital security and encryption technology, could be a single online identifier for U.S. citizens. This identity could be used in a variety of applications and
sites, at home or in the office, with the assurance of confidentiality. 

        An
important element of this service would be the ability of an end user to determine what information is accessible by whom ("permissioning"), and also to decide what organization
stores the data. As a neutral third party, NeuStar is a viable alternative repository for personal information or pointers that would redirect queries to other repositories selected by the end user. 

NeuStar's Enabling Role  

        We believe that optional user-controlled digital identifiers would accelerate the adoption of electronic services in both the private and public
sectors. Given that the usTLD is a public resource utilizing this capability within the usTLD to improve access to public services and to facilitate e-Gov applications including Business
to Government (B2G) is particularly appropriate. 

        NeuStar,
as a part of its existing core businesses, is in possession of confidential and competitive information and follows strict rules to ensure protection of confidential data. A
Code of Conduct that restricts the resale of our data for marketing purposes, and a Whois database design that calls for a two-step process to elicit registrant information, are examples
of our commitment to privacy. From a technology perspective, the extensible fields of the NeuStar Internet registry are fully capable of securely storing (registrant granted) personal data and its
permissioning rights. 

D-7

 

Recommended Process  

        As with any innovation, it is difficult to predict with certainty the degree of acceptance and use; however, in this case, the potential benefits appear to be
compelling. NeuStar is therefore prepared to make the investment required to enable this enhanced utility within the usTLD. We propose to work with the usTLD Policy Council ("the Council") and the DOC
to introduce Personal Identification Services within the usTLD in a fair and responsible manner. 

        NeuStar
will develop a document to assist in the approval process. NeuStar will comply with the request to have all new services approved by the DOC. 

Location-Based Services  

Public Need  

        Today the Internet is indexed and navigated based primarily on domain name via the URL line of browsers and key word via search engines. Although this has served
the user community well, many users seek information, resources, products, and services that by their very nature would be more conveniently organized by geographic location. Such an enabler could be
applied to, for example: 

	•
	Identify
attractions at a vacation destination,

	•
	Locate
the nearest ATM,

	•
	Find
a nearby plumber,

	•
	Provide
the address of the nearest gas station, or

	•
	Locate
the nearest motor vehicle office. 

        The
need to organize information based on geography is most readily apparent in mobile applications. Knowing where a user is located is not enough to provide useful services. End users,
networks, and applications need a simple way to identify what products, services, and resources are located within the surrounding area. 

        Other
than registering in geographically-oriented hierarchical namespaces (e.g., www.aservice.centreville.va.us), which has proven to be unattractive from a marketing perspective and
impractical for multiple locations, there is there is no agreed upon globally resolvable mechanism for registering a location or multiple locations against a domain name. The location-based service
capability described below provides a practical solution that satisfies an identified user need. 

Enhanced Service  

        In order to facilitate this capability, NeuStar proposes to reserve all of the longitude and latitude coordinates that make up the United States and its
territories under the usTLD. One or more locations would be associated with a domain name, and each location would in turn be associated with its geographic coordinates, which would be stored in the
thick registry database. 

        Location
registration would take place through registrars, resellers, delegees, and other service providers. Registered locations would be automatically geographically coded for
longitude and latitude by the Registry based on physical address. The longitude and latitudes associated with a domain name and relevant key words will be stored in the "thick registry" database.
Resolution by location will take place via API interfaces provided by NeuStar to search engines, geographically oriented portal providers, wireless operators, and other enhanced-applications providers
or through direct query to the registry via client-based software. This would allow an end user to search on a particular key word for a given geographical location (e.g., search on key word "bicycle"
to find all bike shops within 10 miles of 

D-8

 

a
given address). The same location-based service enabler could allow an individual to locate government offices or public services in a particular geography. 

NeuStar's Enabling Role  

        The NeuStar thick registry architecture has the ability to support enhanced applications that require transactional resolution of queries based on parameters
other than domain name. Given the geographic nature of any ccTLD, enabling location-based services within a country code would seem to make perfect sense. NeuStar seeks to enable this enhanced utility
within the usTLD so that usTLD registrars, resellers, delegees, and service providers may offer domain name registrants the ability to register their locations against their domain name at an
additional nominal fee and so the usTLD can be the first to offer this useful and innovative capability. 

Recommended Process  

        As with any innovation it is difficult to predict with certainty the degree of acceptance and use; however, in this case the potential benefits appear to be
compelling. NeuStar is therefore prepared to make the investment required to enable this enhanced utility within the usTLD. We propose to work with the usTLD Policy Council and DOC to introduce
location-based services within the usTLD in a fair and responsible manner. 

        NeuStar
will develop a document to assist in the approval process. NeuStar will comply with the request to have all new services approved by the DOC. 

        Each
of the enhancements described represents a brief sample of the innovations possible within the usTLD. All enhancements will be closely evaluated to ensure that the stability of the
Internet is maintained and that the usTLD is balanced with the goal of increasing utility. 

D-9

   E.    Current State of the usTLD Domain Space  

        NeuStar's thorough understanding of the current state of the usTLD strengthens our ability to effectively manage and enhance the
space.

        NeuStar's understanding of the current usTLD space provides the foundation for solution development that ensures:

	•
	Significant improvement of the integrity of the usTLD

	•
	Innovative, yet responsible improvements are developed and properly executed

	•
	The needs of all current and future stakeholders are addressed

        It
is often said that hindsight is 20/20. This means that with time and experience, we come to understand, in context, the implications of previous decisions. Had anyone been able to
predict the developmental course of the Internet and the effect it would have on people's lives, many issues that currently complicate its use would have been addressed and clarified. The same holds
true for the dot-us top-level domain (usTLD). When the original structure and administrative mechanisms for the usTLD were established, there was nothing to compare it with and
no way to predict its evolution. With the advantage of time, however, it is clear that the complexities of the current structure, combined with the lack of coordination and marketing of the namespace,
have resulted in a space that has not attracted a high level of domain name registration activity and that remains underpopulated and underutilized in comparison with other ccTLDs. 

        Without
an in-depth comprehension of the current usTLD space—its successes and its shortcomings—no administrator could successfully meet the challenge
of
improving the integrity of the usTLD. This comprehension must include a thorough understanding of the naming structure, current administration, technical and operational conditions, and other factors
relating to the usTLD, as well as a general understanding of what makes a ccTLD successful. Policy issues in the usTLD run throughout these issues and are discussed throughout this section and this
proposal. 

        The
usTLD was established in 1985 as the country code top-level domain (ccTLD) for the United States. ccTLDs are based on the two-letter country codes from the
list of countries in ISO-3166. A number of these ccTLDs have been repurposed—used not to serve the individuals, governments, and businesses of the country that they represent
but instead as a globally available alternative to the generic top-level domains. For example, the registry for the dot-cc domain, which began as the ccTLD for Cocos Island,
now advertises dot-cc as the newest alternative to the gTLDs. This type of rebranding may create user confusion and can cause a situation where the ccTLD is not managed in the best
interest of the country that it should represent, thereby significantly diminishing the integrity. 

        This
kind of repurposing has not occurred in the usTLD. Today there are approximately 8,000 subdomain delegations under the usTLD to entities providing services for commercial,
educational, and governmental purposes to registrants physically located in the United States. Individuals, federal government agencies, schools, libraries, museums, and state and local governments
are all registered in the usTLD locality-based hierarchy. 

Naming Structure of the usTLD  

        The original hierarchical structure of the usTLD was defined by Dr. Jon Postel in IETF RFC 1480, "The US Domain." This structure is based upon the
geography of the United States. Second-level domain space is designated for states and U.S. territories and consists of two-letter state abbreviations. For example, the state of
Pennsylvania is designated by pa.us. Within the state name space, there is a further subdivision for locality names—counties, cities, or local names. Further structure is available for
each of the various registering entities listed above, and additional structures not based in national geography (e.g., .fed.us, .isa.us, and .nsn.us), which represent special organizations not
contained within 

E-1

 

a
specific locality, have also been established. Some of the designated structures in the usTLD include, but are not limited to: 

 usTLD Designated Structures  

	Structure
 
	 	Description

	<state>.us	 	No direct registrations currently allowed.
	

state.<state>.us	
 	

Used for state governments (e.g., state.va.us). State agencies may register under this structure.
	

<locality>.<state>.us	
 	

Used for city and county names (e.g., arlington.va.us). Businesses, individuals, and private schools may register under this structure.
	

ci.<locality>.<state>.us	
 	

Used for city governments. Agencies that make up those governments may register under this structure.
	

co.<locality>.<state>.us	
 	

Same as above, for county governments.
	

k12.<state>.us	
 	

Used for public schools. Public school districts may register under this structure.
	

<district>.k12.<state>.us	
 	

Used for public school districts. Public schools may register under this structure.
	

cc.<state>.us	
 	

Used to designate community colleges.
	

tec.<state>.us	
 	

Used to designate technical schools.
	

lib.<state>.us	
 	

Used to designate libraries.
	

fed.us	
 	

Used for federal agencies. Only federal agencies may register under this structure.
	

isa.us	
 	

Used to designate inter-state authorities (ISAs), for joint governmental authorities that are inter-state.
	

nsn.us	
 	

Used to designate Native Sovereign Nations, for example Indian tribes, villages, colonies, and other communities that may span state, regional, and national boundaries.

        Additional
nongeographical domains are also included as part of this structure, as defined either in RFC 1480 or by previous administrators. 

        The
locality-based hierarchy provides structure, name uniqueness, and a geographic reference point for registrants and, although it is regarded by some as unwieldy, there are enterprises
that do value the specificity of the system. Exhibit E-1 demonstrates the basic structure of this hierarchy and shows the number of levels possible in the locality structure. The
second-level domain names shown are a subset of all possible second-level domains, and additional "special" domains, as noted above, exist in this 

E-2

 

space.
Registrations must be made within the hierarchical structure, and no registrations are allowed in the second level. 

[Exhibit E-1:
Graphic Design] 

        Designations
for schools provide a good example of this hierarchy. Because many schools share the same name, it is important to distinguish by locality the specific school being
referenced. There might be several Washington High Schools in the United States, but there is likely only one Washington High School in any given school district in the United States. The locality
structure for schools was designed in RFC 1480 to permit distinction between such schools. The k12 designation was created to allow registrations of public and private elementary schools, and the
basic structure for these is k12.<state>.us. Beyond the k12 designation is a designation for a school district, and beyond that, schools may register individual names so that the final
structure becomes <school name>.<district>.k12.<state>.us. Private schools register as <school name>.pvt.k12.<state>.us, but they may also
register under a locality as <school name>.<locality>.<state>.us 

        To
add further complexity, although RFC 1480 defines this structure for registration of schools, the current usTLD administrator has allowed registrations outside of this hierarchy, so
that a school might
register directly under the k12 branch (for example, <school name>.k12.<state>.us). Additionally, entities designated as "special service units," which are discussed but not
definitively structured in RFC 1480, may register directly under k12. Similar discrepancies exist under other areas of the hierarchy. For example, a city government would generally be designated as
ci.<city name>.<state>.<us>, and a county government would be co.<city name>.<state>.<us>. In general, these guidelines have been
followed, but not consistently. As a real example, the following table lists some city and county government domains within the Commonwealth of Virginia. 

 Hierarchical Structure of Government Domains Under.va.us  

	City or County Name
 
	 	Fully Qualified Domain

Name
	 	Follows Hierarchical

Structure

	Arlington County	 	co.arlington.va.us	 	Yes
	

City of Alexandria	
 	

ci.alexandria.va.us	
 	

Yes
	

City of Chesapeake	
 	

chesapeake.va.us	
 	

No
	

City of Covington	
 	

covington.va.us	
 	

No
	

City of Falls Church	
 	

ci.falls-church.va.us	
 	

Yes
	

City of Norfolk	
 	

norfolk.va.us	
 	

No
	

Richmond County	
 	

co.richmond.va.us	
 	

Yes

        Although
the existing structures for Chesapeake, Covington, and Norfolk would have existed had these cities used the "ci" structure, it creates public confusion when cities and counties
in the same state follow different naming conventions for their domains. 

Administration of the usTLD  

        Most branches of the usTLD are delegated to a delegated manager, also known as a delegee, or locality delegee. RFC 1480, written in 1993, maintained that a single
registry operator would not be able to assign all of the DNS names under dot-us and, under the administrative guidelines established for the usTLD, included guidelines for selection of
delegated managers. Although some of these guidelines have changed since 1993, the current administrator has continued the practice of delegating subdomains, and the basic requirements have been
maintained. 

E-3

 

Delegation Guidelines  

        Delegated managers are typically commercial or public institutions with a presence or interest in the location designated. Individuals and organizations may
request an exclusive delegation from the usTLD administrator to provide a registry and registrar services for a particular subdomain under dot-us. For example, one individual with an
interest in Virginia libraries might request delegation of lib.va.us, and become responsible as the delegated manager for all Virginia library names. Delegees are responsible for providing physical
DNS services and maintaining technical support for registrants. A delegee may also assign further subdelegations to a subdelegee, and that subdelegee is then responsible for providing DNS services and
technical support for registrants under that subdelegation. For example, a delegee who is responsible for k12.va.us might subdelegate the Wilson district to a subdelegee. That subdelegee would then be
responsible for all registrations under wilson.k12.va.us. 

        Where
registration for a locality has not been delegated, the usTLD administrator itself provides necessary registry and registrar services. Additionally, no delegations are made in the
second level, so that all cases of <state>.us remain under the control of the main registry operator. 

"Locality Squatting"  

        From the beginning, the concern in selecting a delegee for a subdomain has been assessing their ability to carry out the necessary technical and operational
responsibilities in a neutral manner, that is, applying the same set of rules to all requests for a domain name. Although RFC 2916 maintained that delegees have a duty to serve the community, no
requirements were established regarding the physical location of the delegee, and no limits were made on the number of delegations that could be held by a single subdomain registry operator. 

        Because
there is no such restriction, a small number of delegees became responsible for a very large portion of the delegated namespace. In fact, according to the current contact list of
locality delegees, approximately 40% of the delegations are held by 5 delegees, and 54% of the delegations are held by 10 delegees. Additionally, registry operators who have no interest in the
localities themselves, except for a commercial interest, run many of the delegations. The act of running a registry in which the delegee has no legitimate interest, or of refusing to provide services
to legitimate registrants, has come to be known as "locality squatting." 

        In
response, additional guidelines were established in 1997 to ensure that delegations were made to entities with a legitimate interest in the delegated locality. Beginning in
July 1997, it is assumed that for any new delegations or redelegations, the delegee has the written authorization of the legitimate government for that locality to manage the domain name for
that locality. Although this written authorization does not have to be presented at the time of delegation, the delegee might be asked to produce it if the delegation is later contested. Additionally,
the administrative contact on the delegation application must be a government representative. Finally, guidelines have also been added stating that no delegee may be responsible for more than 50
localities in one state or 500 localities in total. 

        Although
these guidelines are meant to promote diversity and ensure that legitimate governments are able to choose their own delegated registry operator, analysis of the zone file
suggests that problems with "locality squatting" persist in the dot-us subdomains. 

Pricing of Registrations  

        Another important administrative issue in the usTLD is that of cost. The current administrator does not charge customers for registration of a domain name, but
they do state that delegees may charge a fee for their services, as long as the fee is small, fair, and applied equally to all customers. The definition of "small" is determined by the delegee. In
many cases, the "small" fee determined by the delegee is larger than fees most registrars charge for a domain name under dot-com, dot-net, or 

E-4

 

dot-org.
Whereas many registrars now charge under $15 per year to register a domain name under a gTLD, some dot-us delegees charge $25—$30 per year, with additional
one-time registration fees. Paired with the long string that constitutes a dot-us domain name, this additional cost is even more likely to deter individuals and businesses from
registering under dot-us. 

Technical Aspects of the usTLD  

        Both RFC 1480 and information available through the current usTLD administrator specify the technical requirements for delegees who are responsible for a
delegated subdomain. Delegees must provide at least two independent, robust, and reliable nameservers in physically separate locations on the Internet, and any changes to these nameservers must be
reported to the domain registry so that they can be reflected in the usTLD zone files. Delegee host computers must also be set up to accept zone transfers from the usTLD registry. All of these
technical requirements are essential for the usTLD to remain a viable registry, and any delegee not following these requirements risks having the delegation revoked. 

Registration Process  

        Another important technical issue is that of ease of registration. That is, the registration process is currently a manual one, with no consistent, automatic
registration process for registrants. Although registrants can fill out and submit an application online, there is no automatic verification of registration. Registrants have no guarantee that their
requested domain name is available and whether that name has been entered into the zone file. Moreover, registration applications can often take several weeks to be processed, and some customers have
stated that their applications have not been processed at all. As compared to registration in a gTLD, this process is unreliable and cumbersome. 

Whois Service  

        Today, another essential component of a successful TLD registry is a central, accurate Whois service. RFC 1480 provided for a Whois database only through the
third level, intending that delegees and subdelegees would eventually run their own Whois databases for their individual branches. Under current administrative practices, the usTLD not only has no
central database that can in turn create a central Whois, there is also no mechanism in place for delegees to provision database information to the central registry. Even if delegees wished to provide
new Whois information to the usTLD administrator, that capability is currently nonexistent. 

        In
order to remedy the lack of Whois information under the usTLD, the current registry operator installed a client/server Rwhois, (referral Whois) protocol and requested that delegees
also operate an Rwhois server for their delegated subdomains. The Rwhois protocol, presented in RFC 1714 in 1994, defines a method for maintaining Whois information on multiple servers while having
the ability to answer queries from any of those servers. If a query were made to the usTLD registry's Rwhois server, that server would either respond with its own data or refer to the delegated
subdomain's server to return the Whois information. 

        Although
the Rwhois solution appears to be a logical one, three problems prevent it from being successful. First, a central Whois is currently the industry standard for Whois services;
Rwhois is generally not considered to be a robust and secure technical solution. Second, the current registry operator has merely requested that delegees install an Rwhois server. Without mandating
installation of Rwhois servers, there is no way to build a complete Whois database. Third, there is no easy-to-use, Web-based method for Rwhois lookups in the
namespace, so any Whois information that is available is difficult to find. 

E-5

 

Other Factors  

        The use of the usTLD has only one restriction—it is intended for entities that have a physical presence in the United States. Yet many Internet users
in the United States have little or no knowledge about this namespace. Aside from the individual advertising done by locality delegees, the space is generally not promoted and not advertised. That an
individual or company can register in the usTLD space is not widely known; in fact, there are no widely held perceptions regarding the types of entities registered under the usTLD. 

        For
those individuals who do have knowledge of and wish to register in the dot-us space, inconsistent policies among delegees, the lack of a central Whois, and even the need
to locate a delegee for individual subdomains creates a degree of difficulty that many registrants would rather not encounter. 

        Because
of the comparative complexity of the namespace and the lack of coordination and marketing, the usTLD has not attracted a high level of domain name registration activity and
remains underpopulated in comparison with gTLDs and even other ccTLDs. However, many schools, libraries, state and local governments, and even individuals do retain a domain name within the
dot-us namespace. Those current users of the usTLD find the space to be valuable; in fact, many of them depend on it. 

The ccTLD Environment  

        Many countries have already been successful in building awareness and increasing the use of registrations for their country code, while others have had less
success. The following page displays data collected on relative successes across three other ccTLDs—dot-de (Germany), dot-uk (United Kingdom), and
dot-ca (Canada). These three countries represent differing levels of development in the evolution of their ccTLD space. Based on ccTLD domain name registrations, both Germany and the
United Kingdom are characteristic of countries that have created environments that encourage growth. Both countries have experienced thriving markets and have developed mature organizations with
extensive distribution networks. Canada has recently converted from a hierarchical structure that was loosely managed, to a flatter, less complex hierarchy with a newly formed administrative
organization. 

E-6

 

Success Factors in Administration of other Country Code TLDs  

	Factors
 
	 	Germany (.de)
	 	United Kingdom (.uk)
	 	Canada (.ca)

	Administrative Organization	 	DENIC eG Cooperative	 	Nominet	 	CIRA (Canadian Internet Registration Authority)
	Policies	 	Either the domain name owner or the designated administrator of the site must reside in Germany

Self identification

Can purchase registrations from member organizations only	 	No residency restrictions Second-level domain (SLD) structure requires self identification Can purchase registrations from member organizations only	 	Must meet Canadian presence requirements

Citizen

Residency

Various entities

Documentation required

Can purchase registrations from member organizations only
	

Structure	
 	

Direct registration Can register any name except another TLD name (.arpa, .com, .edu, .gov, .int, .net, .nato, .mil, .org and all country-related TLDs) Cannot register German automobile identification numbers as domain names	
 	

SLD hierarchical structure Commercial—.co.uk Non.commercial—.org.uk Registered.companies only —.plc.uk &.ltd.uk Network Providers—.net.uk Schools—.sch.uk	
 	

Direct Registration Can still register under a geographic hierarchy that was the ccTLD structure until December 1, 2000
	

Price—Wholesale	
 	

US$5—US$10	
 	

US$5—US$10	
 	

US$5—US$10
	

Price—Retail	
 	

Generally ccTLDs are considered to be more expensive than gTLDs	
 	

Generally ccTLDs are considered to be more expensive than gTLDs	
 	

US$25—US$40 for one year
	

Awareness levels and cultural aspects	
 	

Very well known Available and promoted since 1997 Previous campaigns include organizations giving away .de domain names with additional purchase Nationalistic	
 	

..uk stands for United Kingdom—Abbreviation has meaningful brand acceptance

General awareness is high	
 	

CIRA recently became the administrative organization 12.01.00
	

Country Code Domain	
 	

4M names as of 2/2001	
 	

Growing at 28,000/month	
 	

Growing at 20,000/month
	

Name Growth	
 	

Growing at 167,000/month	
 	

 	
 	

 
	

Total population	
 	

83M	
 	

60M	
 	

31M
	

Online population	
 	

20.1M	
 	

20M	
 	

13.3M
	

Population % online	
 	

24%	
 	

33%	
 	

43%

E-7

 

        When
analyzing the ccTLD administration for these three countries in comparison to the current administration of the usTLD, it becomes apparent that five factors have
played an important role in the expansion of the ccTLD space: 

	•
	An
administrative organization with maturity and experience;

	•
	Established
policies that facilitate registration and serve to administer, maintain, and enforce the ccTLD space;

	•
	A
low degree of complexity in utilizing the structure or hierarchy for the ccTLD;

	•
	Appropriate
pricing to the end user; and

	•
	Recognition
of cultural differences and levels of awareness within the country. 

        In
each case, an administrative organization has been assigned to maintain the registry database, and the registry manages a centralized database of information on registered domain
names for that country code, assists with administration of the Internet, and provides information about domain name registrations. Neither Germany, the United Kingdom, nor Canada act as registrars.
Based on the high number of domain name registrations, clearly DENIC, the German administrative organization, has created one of the most successful environments for TLD expansion. DENIC has managed
the deTLD since September of 1997 and has established a wide distribution network that provides extensive opportunities for users to register names with ease. 

        The
policies created to register, administer, and maintain each ccTLD are another contributing factor to the speed of ccTLD growth. Policies that are easily understood and require
minimal enforcement establish an environment that simplifies transactions. Both DENIC and Nominet have established registration policies requiring self-selection or
self-identification and no documentation for registration; in contrast, the Canadian Internet Registration Authority, CIRA, requires documentation of compliance before domain names can be
registered. 

        The
cost of registration plays a significant role in the growth of domain name registrations. gTLDs became competitive in late 1999, and until then, there was no wholesale market
opportunity for gTLDs. This has not been true for many ccTLDs. Wholesale prices for ccTLDs in Germany, the United Kingdom, and Canada are relatively consistent in the US$5—US$10 range.
With gTLDs fixed at $35 per year, this created a margin opportunity for the members or registrars promoting ccTLDs. With a US$20—US$30 margin opportunity, it was in the best interests of
the registrars to heavily promote ccTLDs. With heavy promotion by the registrars, ccTLDs gained a significant increase in awareness and registrations. 

        Finally,
awareness of the ccTLD, coupled with certain cultural aspects impact user acceptance. The United Kingdom has the helpful advantage of having a meaningful TLD. "uk" resonates
with the user base of customers within the United Kingdom. This contributes to the overall awareness and general acceptance of the country code. "us" has a similar advantage, with clear recognition of
"us" being synonymous with United States. Coupled with strong nationalistic pride, the usTLD should resonate favorably with the citizens of the United States. 

Conclusion  

        The usTLD namespace is underutilized and under-recognized, but it remains a valuable public space. There is room for improvement in any large undertaking, and the
usTLD is no exception. We have presented this extensive analysis of the current state of the usTLD and an analysis of ccTLDs in general, because we believe that the only way to make
improvements—to expand and enhance the space—is to understand its current successes as well as its shortcomings. Throughout every section of this RFQ response, we have
addressed our understanding of the current space along with our plans for its improvement. 

        The
United States is the world's technological leader, and the current state of the usTLD namespace does not positively represent that. By thoroughly studying the current space, and
through our careful plan for improvements, we believe that we can make the usTLD space the model for a widely used, visible, and successful country code top-level domain. 

E-8

  

F.    Centralized usTLD Database and Enhanced Shared Registration System  

        NeuStar's Centralized usTLD Database and Enhanced Shared Registration System will modernize the usTLD registry and promote registration in
the space.  

        The infrastructure of the usTLD has not evolved along with other leading Internet registries. DNS standards and policies created at the IETF and ICANN have
advanced significantly since the inception of the usTLD and the introduction of RFC 1480, and the usTLD has not kept pace with these advances. Yet it is reasonable for the user community to expect
that the registry will be consistent with appropriate industry standards and policies. An outdated infrastructure causes potential users to question the value of acquiring a name in the usTLD name
space, and most members of the user community have chosen to register names in other TLDs. 

HIGHLIGHTS  

	•
	NeuStar will implement an Enhanced Shared Registraion System to simplify the process for delegated managers and registrars to provision the usTLD
registry

 
	•
	 NeuStar will run a thick registry that stores registrant information in a central usTLD database.

	•
	Whois data for all nameholders, including delegees, subdelegees, and registrants, will be available through a free public, web-based
interface that allows for multiple string and field searches.

        There
are four specific areas where the usTLD infrastructure is lacking. 

	1.
	The
current usTLD administrator has not deployed an automated registration system for the usTLD. The registration process is manual. This makes the process of updating zone files,
creating a central database, tracking changes, and providing a Whois extremely difficult. It also introduces an opportunity for errors.

	2.
	Delegees
and subdelegees are not required to submit registrant information to the current registry. Consequently, there is no centralized, complete, and accurate database of registrant
information for the usTLD.

	3.
	Because
of the hierarchical structure of the usTLD, it was expected that delegees and subdelegees would maintain their own databases and Whois servers. Although some delegees have
followed this recommendation, others have not, and no complete and accurate, centralized Whois service exists for the usTLD. Further, because there is there is no centralized database of registrant
information, a centralized Whois cannot be generated.

	4.
	Although
e-mail addresses are available for third-level delegees, there is little evidence of a central, publicly available or privately held database of all delegees and
subdelegees. 

        If
it is to become the model for the world's country code TLDs, the usTLD must have a robust, secure, and reliable infrastructure equal to or better than any other Internet registry. In
order to modernize the usTLD infrastructure and provide the services and functions outlined in Section B of this proposal, NeuStar will leverage an enhanced shared registration system as shown
in Exhibit F-1, Enhanced SRS, and a centralized usTLD database. This Enhanced SRS and Centralized usTLD database are the central components of NeuStar's usTLD registry, and, in
turn, they create the necessary zone files and Whois service required to round out the usTLD infrastructure. 

        [Exhibit F-1:
Graphic Design] 

F-1

 

F.1    Enhanced Shared Registration System  

        As stated above, the manual registration process currently used by the usTLD administrator introduces difficulties into the processes of updating zone files,
creating a centralized database, tracking changes, and providing a centralized Whois service. Currently, registrants have no guarantee that their registrations have been entered into a database or
into the zone file. NeuStar's solution modernizes the registration, so that all of these functions will become automated. 

        There
are a number of methods that could be used to modernize the infrastructure of the usTLD, and nearly all of them are likely to include a Web-based user interface. In
fact, an interface that would allow registrations over the Web would be expected, if not demanded by the user community. However, a Web interface that looks better to users but that has no associated
capability to update the usTLD database or zone files would not solve the timeliness and reliability problems associated with the manual process. This would be unacceptable to registrars in the
expanded name space. They need immediate access to accurate and up-to-date information, and they need to have a machine interface to the registry due to the high volumes of
registrations that they would expect. 

NeuStar's Solution—Modernizing the Registration Process  

        NeuStar's modernization of the usTLD registry infrastructure begins with the implementation of an Enhanced shared registration system (Enhanced SRS). The Enhanced
SRS is enhanced in that it can accommodate competitive registrars in the expanded space as well as delegated managers and registrants on the locality-based space. The term Enhanced SRS refers to a
system that has a mechanized interface to multiple registrars that provides the same service to all of the interconnected registrars. In addition to supporting competitive registrars, NeuStar's
Enhanced Enhanced SRS will support delegated managers that are the only entity allowed to register names in their name space. The Enhanced Enhanced SRS will automate the registration process for all
name holders. 

        Due
to the nature of the usTLD name space, it is necessary to define the three different registration processes, as shown in Exhibit F-2: (1) registrations in
the expanded name space, (2) registrations in the locality-based space where NeuStar is the registrar, and (3) registrations in the locality-based space with existing delegees or
subdelegees. 

Expanded Name Space  

        Registrations in the expanded name space will be very similar to registrations in a generic TLD such as.biz, as shown in Exhibit F-3.
Registrars will be responsible for the registration of names in the expanded name space, and NeuStar will not act as a registrar for that space. In order for registrars to interface over a mechanized
interface with the usTLD registry, NeuStar has developed a protocol called XRP (eXtensible Registry Protocol). This protocol has been developed and is undergoing implementation for the .biz registry.
NeuStar is also an active participant at the IETF Provreg Working Group, which is developing an industry standard protocol for an interface between registrars and a registry. NeuStar will ensure that
XRP is functionally compatible with the standard developed by the IETF Provreg WG. All usTLD-accredited registrars will be provided with an XRP software toolkit, free of charge. 

[Exhibit F-2: Graphic Design] 

        NeuStar
will deploy a thick registry, which means that registrars will submit name, registration, and contact information about registrants to the registry, and the registry will store
that information in the central usTLD database. This information will allow the registry to create a centralized Whois and populate the zone file with the appropriate resource record. 

F-2

 

Locality-Based Name Space Where NeuStar is the Registrar  

        NeuStar will be required to act as a registrar in the locality-based name space in cases of undelegated third-level names. To fulfill this role, NeuStar will
implement a Web-based interface for registrants to register names in that space. This interface will be very similar to the way registrants register names with registrars today in generic
top level domains (gTLD), such as.com. Upon initial registration registrants will be provided with authenticating information that will need to be submitted for future changes and updates to the
registration. This will permit an extra level of security and ensure that the appropriate registrant is modifying the name. 

[Exhibit F-3:
Graphic Design] 

        Just
like in the expanded space NeuStar will gather information about the registrant to populate the central usTLD database, create a Whois record, and update the zone file. In addition,
NeuStar needs to clear the payment and enter the registrant in NeuStar's Registrant database. There is a clear difference between managing a name for a registrar and managing a name for a registrant.
NeuStar understands the importance of treating these two types of registrations differently. 

Locality-Based Name Space for Existing Delegees and Subdelegees  

        Existing delegees and subdelegees will continue to provide registration services to registrants within their designated localities. However, their functions will
be expanded so that NeuStar can store information for all of the registrants in the usTLD name space. Delegees and subdelegees will be responsible for providing NeuStar with registration information
for each name that they register, as well as contact information for each registrant so that NeuStar can update the central usTLD database and create a Whois record for the registrant. If the delegee
or subdelegee chooses to host the registered names on their own name servers then they do not need to provide resource record information to NeuStar. As an additional service, NeuStar will host
resource records in the usTLD zone file created at the registry. In cases where delegees and subdelegees choose to take advantage of this option, they will need to provide NeuStar with the appropriate
resource record information. 

        NeuStar
will provide a secure Web site where delegees and subdelegees will provision this information with the registry. Each delegee and subdelegee will be provided with authenticating
information to ensure that they are modifying records within their name space. However, if a delegee or subdelegee would prefer to interface with the registry over a mechanized interface, they can
choose to implement the XRP interface by downloading the tool kit from the usTLD web site. 

F.2    Centralized usTLD Database  

        As noted earlier in this section, RFC 1480 made no provision for a centralized database and Whois in the usTLD space, in the hopes that delegees and subdelegees
would maintain their own database and Whois. As the domain name system evolved, it became obvious that this was not the best way to maintain and administer such an important public resource. It is
important that the domain name community can easily determine the entities responsible for a domain name. This is important for the proper functioning of the system and the names as well as for
ensuring that the entity responsible for the name is complying with appropriate policies and practices. If that information is not centralized, it is difficult to ensure consistency and accuracy. 

        Additionally,
there is little evidence of a publicly available or privately held database of all delegees and subdelegees. While there is a simple contact list which provides delegated
names and email addresses this is not sufficient for the purposes of ensuring the proper operations of an important public resource. Delegees and subdelegees are clearly held to a higher standard of
operations since they are responsible for managing other names. It is critical that the usTLD administrator and the public have very specific and up-to-date information
regarding these entities. 

F-3

 

        In
an attempt to provide Whois services, the current administrator implemented a Referral Whois (Rwhois) service, in which delegees and subdelegees were asked to install Rwhois, so that
Whois requests could be referred, through the main Rwhois server, down to the individual delegees. This is a solution that could be implemented in both the expanded space as well as the existing
locality space. Registrars would maintain the database and Whois data for their customers in the expanded space and delegees and subdelegees would maintain their customer's data and Whois in the
locality-based space. 

        However,
Rwhois is generally considered by the technical community to be an inferior and unreliable protocol. Rwhois is not widely deployed and therefore not well understood. This is
particularly a problem when the administrator would be relying on potentially thousands of entities (i.e., delegees, subdelegees, and registrars) to deploy and maintain it. A distributed Whois also
creates the likelihood of there being inconsistent policies and treatment of name holders. Furthermore, it would be extremely difficult to monitor the compliance of delegees, subdelegees, and
registrars if the database and Whois were distributed. 

        Since
the database itself is not publicly accessible (only the Whois data is), a distributed architecture would virtually ensure a lack of consistency to the data that is stored and the
manner that it is stored. For example one entity could store data on an Excel spreadsheet where another entity could store data in an Oracle database. One entity could store different data than
another entity. This would make the process of transferring registrants from one entity to another much more difficult. 

        But
the most convincing evidence that a distributed database and Whois approach does not work is the fact that this is the current solution deployed in the usTLD, and it is well
understood that it is not sufficient. 

NeuStar's Solution—A Centralized usTLD Database  

        In an effort to create a centralized Whois, and in order to be able to provide complete information about nameholders, NeuStar will centralize all pertinent
information regarding all names registered in the usTLD name space. There are two broad categories of name holders: (1) registrants and (2) delegated managers, including all delegees,
subdelegees. Registrants will register names through a delegated manager in the locality-based name space, and they will register through competitive registrars in the expanded name space. All name
holders and registrars will be included in the central usTLD database and the central Whois database. 

        The
Centralized usTLD database will be escrowed on a regular basis with an escrow agent that is acceptable to both NeuStar and the Contracting Officer's Technical Representative (COTR).
The Centralized usTLD database is the heart of the usTLD registry; the publicly accessible Whois, the delegated manager Whois and the zone file will all be created from this database. Centralizing and
escrowing the registration information will ensure the integrity, security, and reliability of the entire name space. 

        All
Whois information will be free and publicly available over a Web-based interface that will allow for multiple string and field searches. NeuStar will provide a Web site
for this purpose as well as providing access over the IANA-approved port 43. 

        The
following table provides details on the Whois information that will be available through the usTLD Web interface and port 43. 

F-4

 

 
 

Whois Information Under the usTLD    
    

	Registrants in Locality Space
 
	 	 
	 	Delegated Managers in Locality Space
 

	24	 	Name of the domain registered	 	 	 	 
	25	 	Internet Protocol (IP) address of the primary nameserver and secondary nameserver(s) for the registered domain name	 	32.

33.	 	Name of the delegated manager

Delegated Manager ID
	26	 	Corresponding names of those nameservers	 	34.	 	IP address of the primary nameserver and secondary nameserver(s) for the delegation
	27	 	Identity of the delegated manager under which the name is registered	 	35.	 	Corresponding names of those nameservers
	28	 	Creation date of the registration manager	 	36.	 	Date of delegation
	29	 	Name and postal address of the domain name holder	 	37.	 	Name and postal address of the delegated manager
	30	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder	 	38.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the delegated manager
	31	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder	 	39.	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the delegated manager
	 	 	 	 	40.	 	Web site or other contact information through which registrations can be accepted under the delegation

	

Registrants in Expanded Space
 
	
 	

 
	
 	

Registrars in Expanded Space
 

	41.	 	Name of the domain registered	 	48.	 	Name of the registrar
	42	 	IP address of the primary nameserver and secondary nameserver(s) for the registered domain name	 	49.

50.	 	Registrar ID

Registrar status (e.g., active, pending)
	43	 	Corresponding names of those nameservers	 	51	 	Name and postal address of the registrar
	44	 	Creation date of the registration	 	52	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the registrar
	45	 	Name and postal address of the domain name holder	 	53	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the registrar
	46	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder	 	54	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the billing contact for the registrar
	47	 	Name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder	 	 	 	 

F-5

 

        It
is necessary to divide the methods for provisioning this information into two categories, existing information and new information. The technical and functional interfaces and methods
for provisioning new information are defined earlier in this section. 

        Provisioning
existing information will require an outreach effort to the current delegated managers. The first step is to contact the delegated managers through contact information
provided by the current usTLD Administrator, we will request this information as outlined in our Transition Plan, discussed in Section T. This name and contact information can be supplemented
by writing a script to "walk the tree." Walking the tree refers to the process of performing a recursive search of the usTLD, which gathers zone file information from delegees and subdelegees and
includes all delegations and direct registrations. The zone files of delegated managers include contact information for the delegated manager, and they also include all registrations under the
delegated manager's name space. NeuStar has already starting walking the tree and analyzing the results to develop a database of delegated manager contact information and a database of all of the
names in the usTLD name space, so that NeuStar will be able to initiate our outreach effort beginning on the day of contract award. 

        Once
the delegated managers have been contacted, they will be provided with a list of the information we would expect to receive from them including a list of names for which we believe
they are responsible. We will offer them options as to how they provide us this information. They will be able to provision it on a secure website or they will be able to send us a file in a format
provided by NeuStar. It may be necessary for the delegated manager to contact their registrants for some of the information we will be requesting. This will be an iterative process with regular
contact between NeuStar and the delegated manager until the information is verified. 

        Because
NeuStar will not necessarily be hosting the resource records associated with names registered to delegated managers, it is possible for the delegated manager to register a name
and forget to update NeuStar. In order to ensure that our Centralized usTLD database is accurate and up to date, NeuStar will "walk the tree" continuously and compare the results with information in
that database. If there is a difference, we will contact the delegated manager to correct the discrepancy. 

Conclusion  

        If the usTLD is to be considered on par with or better than the rest of the available top-level domains, its registry must contain accurate and
up-to-date information pertaining to name registrations and name holders. To accumulate this information on an ongoing basis, NeuStar will use standard practices now common in
the domain name registry community. We will provide easy-to-access and easy-to-use tools by which registrants, delegated managers, and registrars can
provide this information to us. Accumulating existing information is simply a matter of using data and tools at our disposal to reach out to the existing name holders. While this will be a time
consuming task, NeuStar welcomes this as a good opportunity to develop a relationship with the existing user community. 

F-6

  

G.    Draft Delegated Managers/Administrator Contract  

        The delegated Managers/Administrators contract will establish clear and comprehensive parameters for the management of the delegated
subdomains

	•
	Agreement establishes mutual obligations of delegated managers and usTLD Administrator

	•
	Establishes mutual performance specifications and performance credits to ensure mutual compliance with minimum technical
requirements

	•
	Promotes greater accountability in locality-based usTLD space

        As
an important part of its work to centralize and enhance the usTLD delegated space, NeuStar intends to establish comprehensive contractual arrangements with all of the usTLD Delegated
Managers. The agreements will establish clear and comprehensive parameters for the management of the delegated subdomains, as well as basic requirements and obligations binding on NeuStar as the usTLD
Administrator and the Delegated Manager. In addition, because the usTLD Administrator will not have a direct contractual arrangement with the registrants, these contracts will include "flow through
obligations", such as the Nexus requirement or the obligation to provide accurate WHOIS data, that the Delegated Managers will be required to enforce in its contracts with its registrants. These legal
relationships will help provide the accountability and administrative certainty necessary to maintain the stable operation of the usTLD. 

        Recognizing
the significant and useful effort that has gone into the development of similar agreements in the ICANN context, these agreements will be patterned after the
Registry-Registrar agreement developed for the new gTLDs by ICANN. These agreements contain certain modifications necessary to address the dynamics and specific requirements of the usTLD. Such changes
have, however, been kept to a minimum. Use of the existing ICANN agreements as templates will establish a sense of consistency
between the usTLD and the DNS at large, as well as providing usTLD users, delegated managers, and registrars a familiar and effective system under which to operate. A template for the Delegated
Manager Agreement is attached hereto. This document will be a standard document signed by all usTLD Delegated Managers and will be finalized upon completion of the compliance report described in
Section B.4.5 of this Proposal. 

WORKING DRAFT DATED JULY 27, 2001  

THIS AGREEMENT IS A TEMPLATE TO SHOW THE BASIC STRUCTURE UNDER WHICH NEUSTAR EXPECTS THAT THE DELEGATED MANAGERS MIGHT OPERATE. THIS
AGREEMENT WILL BE FINALIZED UPON COMPLETION OF THE COMPLIANCE REPORT DISCUSSED IN SECTION B.4.5 BASED UPON INFORMATION GATHERED IN THAT PROCESS.  

 
  usTLD ADMINISTRATOR-DELEGATED MANAGER AGREEMENT    
    

        This usTLD Administrator-Delegated Manager Agreement is made and effective as
of                        , 200  , by and between NeuStar, Inc., a
Delaware corporation, with its principal place of business located at 1120 Vermont Avenue, Suite 400, Washington, D.C. 20005 ("usTLD Administrator"), and [Delegated
Manager's name], a [jurisdiction and type of organization], with its principal place of
business located at [Delegated Manager's location] ("Delegated Manager"). 

        WHEREAS, usTLD Administrator has been appointed to be the administrator of the usTLD by the U.S. Department of Commerce, National
Institute of Standards and Technology to operate a shared registration system, TLD nameservers, and other equipment for the ".us" top-level domain; 

        WHEREAS, the usTLD Administrator has entered a usTLD Agreement with the U.S. Department of Commerce, National Institute of Standards and
Technology to administer the .us top-level domain 

G-1

 

name
and to operate a shared registration system, TLD nameservers, and other equipment for the ".us" top-level domain 

        WHEREAS, historically the second, third, and in certain cases fourth level sub-domains of the usTLD were geographically and
politically defined pursuant to the Internet Engineering Task Force's RFC 1480 (titled The US Domain at www.ietf.or/rfc/rfc1480.txt?number+1480) ("RFC
1480"); 

        WHEREAS, pursuant to the provisions of RFC 1480 and RFC 1591 (titled Domain Name System Structure and
Delegation at http://www.isi.edu/in-notes/rfc1591.txt) ("RFC 1591"), in each case as supplemented by the rules and procedures on the.us domain website
(http://www.nic.us), as they may be amended from time to time (".US Domain Policies"), Registrar, along with other registrars, currently acts as a registry and registrar for certain third level and
fourth-level sub-domain names within the.us top-level domain for a particular locality or localities. 

        WHEREAS, pursuant to this Agreement, Delegated Manager wishes to continue to provide services pursuant to RFC 1480 and RFC 1591, as
supplemented by the policies created and administered by the usTLD Administrator. 

        NOW, THEREFORE, for and in consideration of the mutual promises, benefits and covenants contained herein and for other good and valuable
consideration, the receipt, adequacy and sufficiency of which are hereby acknowledged, usTLD Administrator and Delegated Manager, intending to be legally bound, hereby agree as follows: 

1.     DEFINITIONS  

	1.1
	"Agreement"
means this usTLD Administrator-Delegated Manager Agreement between usTLD Administrator and Delegated Manager, as such may be amended from time to time in the future.

	1.2
	The
"APIs" are the application program interfaces by which Delegated Manager may interact, through the XRP, with the usTLD System.

	1.3
	"Confidential
Information" means all information and materials, including, without limitation, computer software, data, information, databases, protocols, reference implementation and
documentation, and functional and interface specifications provided by one party to this Agreement (the "Disclosing Party") to the other party (the "Receiving Party") and marked or otherwise
identified as "confidential", provided that if a communication is oral, the Disclosing Party will notify the Receiving Party in writing within fifteen (15) days of the disclosure of the
confidential nature of such information.

	1.4
	The
word "Delegated Manager" when appearing with an initial capital letter, refers to [Delegated Manager Name],
a party to this Agreement.

	1.5
	The
word "Delegated Manager" when appearing without an initial capital letter, refers to an entity that contracts with Registrants and with the usTLD Administrator to provide domain
name registration services and collects registration data about the Registrants and submits registration information for entry in the usTLD Database and is party to an Accreditation Agreement with
usTLD Administrator.

	1.6
	"Delegated
Manager Services" means services provided by a Delegated Manager in connection with the usTLD under this Agreement, and includes contracting with Registrants, collecting
registration data about the Registrants, and submitting registration information for entry in the usTLD Database.

	1.7
	The
"Delegated Manager Tool Kit" shall mean the Tool Kit set forth in Exhibit A.

	1.8
	"DNS"
means the Internet domain name system. 

G-2

 

	1.9
	The
"Effective Date" shall be the date first set forth above.

	1.10
	"NIST"
means the U.S. Department of Commerce, National Institute of Standards and Technology (or any successor agency or governmental unit charged with ultimate responsibility for
the country code top-level domain name for the United States).

	1.11
	"Personal
Data" refers to data about any identified or identifiable natural person.

	1.12
	"Registered
Name" refers to a sub-domain name within the domain of the usTLD, about which usTLD Administrator or an affiliate engaged in providing usTLD Services
maintains data in a usTLD Database, arranges for such maintenance, or derives revenue from such maintenance.

	1.13
	"Registrant"
means the holder of a Registered Name.

	1.14
	"Term"
means the term of this Agreement, as set forth in Subsection 8.1.

	1.15
	A
"TLD" means a top-level domain of the DNS.

	1.16
	In
order to have to required "U.S. Nexus", a Registrant must be: (a) a natural person (i) who is a citizen or permanent resident of the United States of America or any
of its possessions or territories, or (ii) whose primary place of domicile is in the United States of America or any of its possessions, or (b) an entity or organization that is
(i) incorporated within one of the fifty (50) U.S. states, the District of Columbia, or any of the United States possessions or territories or (ii) organized or otherwise
constituted under the laws of a state of the United States of America, the District of Columbia or any of its possessions or territories, or (c) an entity or organization (including a federal,
state, or local government of the United States, or a political subdivision thereof) that has a bona fide presence in the United States. "usTLD" means the.us TLD.

	1.17
	"usTLD
Agreement" means the usTLD Agreement between usTLD Administrator and NIST dated [date of usTLD Agreement] for the administration and operation of the
usTLD.

	1.18
	"usTLD
Database" means a database comprised of data about one or more DNS domain names within the domain of the usTLD that is used to generate either DNS resource records that are
published authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names.

	1.19
	"usTLD
Policy Council" shall mean the United States Policy Advisory Council established by the usTLD Administrator under the usTLD Agreement

	1.20
	"usTLD
Services" means services provided as an integral part of the operation of the usTLD.

	1.21
	The
"usTLD System" means the registry system operated by usTLD Administrator for Registered Names in the usTLD.

	1.22
	"XRP"
means the extensible registry-Delegated Manager protocol used by the usTLD System. 

Other
terms used in this Agreement as defined terms shall have the meanings ascribed to them in the context in which they are defined. 

2.     OBLIGATIONS OF USTLD ADMINISTRATOR  

	2.1
	Access to usTLD System.    Throughout the Term of this Agreement, usTLD Administrator shall provide Delegated Manager with
access as a Delegated Manager to the usTLD System. Nothing in this Agreement entitles Delegated Manager to enforce any agreement between usTLD Administrator and NIST, and Delegated Manager shall not
be deemed to be a third-party beneficiary under the usTLD Agreement. 

G-3

 

	2.2
	Maintenance of Registrations Sponsored by Delegated Manager.    Subject to the provisions of this Agreement, and requirements
under the usTLD Agreement, and solely if requested by Delegated Manager, usTLD Administrator shall maintain the registrations of Registered Names sponsored by Delegated Manager in the usTLD System so
long as Delegated Manager has paid the Fees required by Subsection 4.1 below and this Agreement remains in effect. Otherwise, Delegated Manager shall maintain the registrations of Registered Names
sponsored by Delegated Manager in the usTLD System.

	2.3
	Provision of Tool Kits; Limited License.

	2.3.1
	Delegated Manager Tool Kit.    If the Delegated Manager requests that the usTLD Administrator maintains the registrations
of Registered Names sponsored by Delegated Manager in the usTLD System, no later than five (5) business days after the Effective Date, usTLD Administrator shall provide to Delegated Manager a
copy of the Delegated Manager Tool Kit, which shall provide sufficient technical specifications to permit Delegated Manager interface with the usTLD System and employ its features that are available
to Delegated Managers, provided that, if the Effective Date occurs prior to the date that usTLD Administrator has made the usTLD Tool Kit available to .us Delegated Managers generally ("Availability
Date"), usTLD Administrator shall provide to Delegated Manager a copy of the usTLD Tool Kit, no later than five (5) business days after the Availability Date. Subject to the terms and
conditions of this Agreement, UsTLD Administrator hereby grants Delegated Manager and Delegated Manager accepts a non-exclusive, non-transferable, worldwide limited license to
use for the Term and purposes of this Agreement, all components owned by or licensed to UsTLD Administrator in and to the RRP, APIs, any reference client software and any other intellectual property
included in the Delegated Manager Tool Kit, as well as updates and redesigns thereof, to provide domain name registration services in the usTLD only and for no other purpose.

	2.3.2
	Limited License.    Subject to the terms and conditions of this Agreement, including without limitation Delegated Manager's
timely payment of all Fees owed, usTLD Administrator hereby grants Delegated Manager and Delegated Manager accepts a non-exclusive, non-transferable, worldwide limited license,
to use for the Term and purposes of this Agreement the XRP, APIs and any reference client software included in the Delegated Manager Tool Kits, as well as any updates and redesigns thereof, for
providing domain name Delegated Manager Services in the usTLD only and for no other purpose.

	2.4
	Changes to usTLD System.    usTLD Administrator may in its discretion from time to time make modifications to the XRP, APIs,
or other software or materials licensed hereunder that will modify, revise or augment the features of the usTLD System. usTLD Administrator will use commercially reasonable efforts to provide
Delegated Manager with at least ninety (90) days notice prior to the implementation of any material changes to the XRP, APIs or software licensed hereunder. usTLD Administrator shall have no
obligation under this Agreement to update, modify, maintain, or repair any XRP, APIs, or other software materials (or any updates or redesigns thereto) licensed under this Agreement to Delegated
Manager.

	2.5
	Engineering and Customer Service Support; Performance Specifications.    usTLD Administrator shall provide Delegated Manager
with engineering and customer service support as set forth in Exhibit B.

	2.6
	Handling of Personal Data.    usTLD Administrator shall notify Delegated Manager of the purposes for which Personal Data
submitted to usTLD Administrator by Delegated Manager is collected, the intended recipients (or categories of recipients) of such Personal Data, and 

G-4

 

the
mechanism for access to and correction of such Personal Data. usTLD Administrator shall take commercially reasonable steps to protect Personal Data from loss, misuse, unauthorized disclosure,
alteration or destruction. 

	2.7
	NIST/usTLD Administrator Requirements.    usTLD Administrator's obligations hereunder are subject to modification at any time
as the result of NIST-mandated requirements and NeuStar policies developed by usTLD Administrator through its United States Policy Advisory Council ("usTLD Policy Council") from time to
time. Notwithstanding anything in this Agreement to the contrary, Delegated Manager shall comply with any such NIST requirements or usTLD Policy Council policies in accordance with the stated
timelines. 

3.     OBLIGATIONS OF DELEGATED MANAGER  

	3.1
	Delegated Manager Responsibility for Customer Support; Participation in Marketing Campaigns/Community Outreach
Programs.    Delegated Manager shall provide (i) support to accept and process orders for Registered Names from proposed Registrants and (ii) customer
service (including domain name record support) and billing and technical support to Registrants. In addition, Delegated Manager will use commercially reasonable efforts to market, either directly or
through authorized re-sellers, Registered Names to potential Registrants and to solicit such potential customers to register for Registered Names, and Delegated Manager will cooperate with
usTLD Administrator in marketing campaigns or community outreach programs that usTLD Administrator may commence from time to time.

	3.2
	Delegated Manager's Registration Agreement; U.S. Nexus Requirements.    At all times during the Term of this Agreement while
it is sponsoring the registration of any Registered Name within the usTLD System, Delegated Manager shall have in effect an electronic or paper registration agreement with each Registrant (a
"Registration Agreement"). Delegated Manager shall, if so requested by usTLD Administrator from time to time, promptly furnish to usTLD Administrator a copy of each general form of Registration
Agreement it uses with Registrants. Delegated Manager shall include in each Registration Agreement those terms specifically required by this Agreement and the Accreditation Agreement and other terms
that are consistent with Delegated Manager's obligations to usTLD Administrator under this Agreement and the Accreditation Agreement and that will ensure ongoing compliance with both such agreements.
Without limiting the foregoing, the Registration Agreement shall require each Registrant to certify, under penalty of perjury, that it has, and shall continue to have, a bona fide U.S. Nexus in order
to qualify to register and maintain its use of a Registered Name.

	3.3
	Indemnification Required of Registrants.    In its Registration Agreement with each Registrant, Delegated Manager shall
require such Registrant to indemnify, defend and hold harmless usTLD Administrator, and its directors, officers, employees, representatives, agents, affiliates, and stockholders from and against any
and all claims, suits, actions, other proceedings, damages, liabilities, costs and expenses of any kind, including without limitation reasonable legal fees and expenses, arising out of or relating to
the Registrant's (i) domain name registration and (ii) use of any Registered Name. Each Registration Agreement shall further require that this indemnification obligation survive the
termination or expiration of the Registration Agreement.

	3.4
	Data Submission Requirements.    As part of its registration and sponsorship of Registered Names in the usTLD, Delegated
Manager shall submit complete data (and update such data) as required by technical specifications of the usTLD System that are made available to Delegated Manager from time to time and the
Accreditation Agreement. If the Delegated Manager requests that the usTLD Administrator maintains the Registered Names in the 

G-5

 

usTLD
System, Delegated Manager hereby grants usTLD Administrator a non-exclusive, non-transferable, limited license to such data for propagation of and the provision of
authorized access to the TLD zone files and as otherwise required in usTLD Administrator's operation of the usTLD. 

	3.5
	Security.    Delegated Manager agrees to develop and employ in its domain name registration business all necessary technology
and restrictions to ensure that its connection to the usTLD System is secure. All data exchanged between Delegated Manager's system and the usTLD System shall be protected to avoid unintended
disclosure of information. Delegated Manager agrees to employ the necessary measures to prevent its access to the usTLD System granted hereunder from being used to (1) allow, enable, or
otherwise support, the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than its own existing customers; or
(2) enable high volume, automated, electronic processes that send queries or data to the systems of usTLD Administrator, any other registry operated under an agreement with usTLD Administrator,
or any other Delegated Manager, except as reasonably necessary to register domain names or modify existing registrations in compliance with this Agreement. In addition, usTLD Administrator may from
time to time require other reasonable security provisions to ensure that the usTLD System is secure, and Delegated Manager will comply with all such provisions.

	3.6
	Resolution of Technical Problems.    Delegated Manager agrees to employ necessary employees, contractors, or agents with
sufficient technical training and experience to respond to and fix all technical problems concerning the use of the XRP and the APIs in conjunction with Delegated Manager's systems. Delegated Manager
agrees that in the event of significant degradation of the usTLD System or other emergency, usTLD Administrator may, in its sole discretion, temporarily suspend access to the usTLD System. Such
temporary suspensions shall be applied in a non-arbitrary manner and shall apply fairly to any Delegated Manager similarly situated, including any affiliates of usTLD Administrator that
serve as Delegated Managers.

	3.7
	Time of Entry of Domain Name Registration.    Delegated Manager agrees that in the event of any dispute concerning the time
of the entry of a domain name registration into the usTLD Database, the time shown in the usTLD System records shall control.

	3.8
	Compliance with Terms and Conditions.    Delegated Manager shall comply with, and shall include in each Registration
Agreement all of the following:

	3.8.1
	Any
NIST standards, policies, procedures, and practices for which usTLD Administrator has monitoring responsibility in accordance with the usTLD Agreement or other arrangement with
NIST and/or ICANN, including without limitation ICANN policies pertaining to open county code TLDs (unless otherwise provided in the usTLD Agreement); and

	3.8.2
	Operational
standards, policies, procedures, and practices for the usTLD as set forth in the usTLD Agreement and as established from time to time by usTLD Administrator and/or the
usTLD Policy Council in a non-arbitrary manner and applicable to all Delegated Managers generally, and consistent with NIST's standards, policies, procedures, and practices. Among usTLD
Administrator's current operational standards, policies, procedures, and practices are those set forth in Exhibit E. Additional or revised usTLD Administrator operational standards, policies,
procedures, and practices for the usTLD shall be effective upon thirty (30) days notice by usTLD Administrator to Delegated Manager. 

G-6

 

	3.9
	Restrictions on Registered Names; Compliance with Law.    In addition to complying with NIST, policies, procedures, and
practices limiting domain names that may be registered, Delegated Manager agrees to comply with applicable statutes and regulations limiting the domain names that may be registered. Further, Delegated
Manager shall abide by applicable laws and governmental regulations.

	3.12
	Resellers/Sub-Delegated Manager.    Delegated Manager may, in its discretion from time to time, designate one or
more resellers/Sub-Delegated Managers ("Reseller") that will be permitted to provide Delegated Manager Services consistent with those permitted of Delegated Manager under this Agreement.
Delegated Manager shall enter into a written agreement with each of its re-sellers (a "Reseller Agreement"), which will ensure compliance with this Agreement and the Accreditation
Agreement and include sufficient terms and conditions to obligate each Reseller to abide by all terms and conditions and all Delegated Manager obligations set forth in this Agreement (provided that
re-sellers will not be entitled to appoint their own resellers) and the Accreditation Agreement. Delegated Manager shall be primarily liable
for all acts or omissions of its resellers, and usTLD Administrator's obligations under this Agreement and the Accreditation Agreement shall not be increased due to Delegated Manager's appointment of
re-sellers. Promptly following the end of each calendar year during the Term of this Agreement (but in no event later than January 30), Delegated Manager shall provide to usTLD
Administrator a complete written list of all of its current resellers. Further, in its Reseller Agreement with each re-seller, Delegated Manager shall require such reseller to indemnify,
defend and hold harmless usTLD Administrator, and its directors, officers, employees, representatives, agents, affiliates, and stockholders from and against any and all claims, damages, liabilities,
costs and expenses of any kind, including without limitation reasonable legal fees and expenses, arising out of or relating to any activities of such sub-Delegated Manager. Each such
Reseller Agreement shall further require that this indemnification obligation survive the termination or expiration of that agreement. 

4.     FEES  

	4.1
	Amount of usTLD Administrator Fees.    In the event that the Delegated Manager requests that Registered Names are maintained
by the usTLD Administrator, Delegated Manager agrees to pay usTLD Administrator the fees set forth in Exhibit F for initial and renewal
registrations and other services provided by usTLD Administrator to Delegated Manager (collectively, "Fees"). usTLD Administrator reserves the right to revise the Fees prospectively upon thirty
(30) days notice to Delegated Manager, provided that such adjustments are consistent with the usTLD Agreement.

	4.2
	Payment of usTLD Administrator Fees.    In advance of incurring Fees, Delegated Manager shall establish a letter of credit,
deposit account, or other credit facility accepted by usTLD Administrator, which acceptance will not be unreasonably withheld so long as payment is assured. All Fees are due immediately upon receipt
of applications for initial and renewal registrations, or upon provision of other services provided by usTLD Administrator to Delegated Manager. Payment shall be made via debit or draw down of the
deposit account, letter of credit or other credit facility. usTLD Administrator shall provide monthly invoices to the Delegated Manager.

	4.3
	Non-Payment of Fees.    In the event Delegated Manager has insufficient funds deposited or available through the
letter of credit or credit facility with usTLD Administrator or otherwise fails to pay Fees when due, usTLD Administrator may do any or all of the following: (a) stop accepting new initial or
renewal registrations from Delegated Manager; (b) delete the domain names associated with any negative balance incurred from the usTLD Database; and (c) pursue any other remedy permitted
under this Agreement or at law or in equity. 

G-7

 

5.     CONFIDENTIALITY AND INTELLECTUAL PROPERTY  

	5.1
	Use of Confidential Information.    During the Term of this Agreement, a Disclosing Party may be required (or elect) to
disclose Confidential Information to the Receiving Party. Each party's use and disclosure of the Confidential Information shall be subject to the following terms and conditions:

	5.1.1
	The
Receiving Party shall treat as strictly confidential, and use all reasonable efforts to preserve the secrecy and confidentiality of, all Confidential Information, including
implementing reasonable physical security measures and operating procedures.

	5.1.2
	The
Receiving Party agrees that it will use any Confidential Information solely for the purpose of exercising its rights or performing its obligations under this Agreement and for
no other purposes whatsoever.

	5.1.3
	The
Receiving Party shall make no disclosures whatsoever of any Confidential Information of the Disclosing Party to others; provided, however, that if the Receiving Party is a
corporation, partnership, or other organization, disclosure is permitted to the Receiving Party's officers, employees, contractors and agents who have a demonstrable need to know such Confidential
Information, provided the Receiving Party shall advise such personnel of the confidential nature of the Confidential Information and of the procedures required to maintain the confidentiality thereof,
and shall require them to acknowledge in writing that they have read, understand, and agree to be individually bound by the confidentiality terms of this Agreement.

	5.1.4
	The
Receiving Party shall not modify or remove any confidentiality legends and/or copyright notices appearing on any Confidential Information.

	5.1.5
	The
Receiving Party agrees not to prepare, or claim any rights to, any derivative works based on the Confidential Information.

	5.1.6
	Notwithstanding
the foregoing, this Subsection 5.1 imposes no obligation upon the parties with respect to information that (a) is disclosed to a third party with the
Disclosing Party's prior written approval; or (b) is or has entered the public domain through no fault of the Receiving Party; or (c) is known by the Receiving Party prior to the time of
disclosure (as shown by documentary records to that effect); or (d) is independently developed by the Receiving Party without use of, or reference to, the Confidential Information; or
(e) is made generally available by the Disclosing Party without restriction on disclosure; or (f) Receiving Party receives in good faith from a third party who is not, directly or
indirectly, under an obligation of confidentiality to Disclosing Party with respect to same.

	5.1.7
	In
the event the Receiving Party is required by law, regulation or court order to disclose any Confidential Information, Receiving Party will promptly notify Disclosing Party in
writing prior to making any such disclosure in order to facilitate Disclosing Party seeking a protective order or other appropriate remedy from the proper authority, at the Disclosing Party's expense.
Receiving Party agrees to cooperate with Disclosing Party in seeking such order or other remedy. Receiving Party further agrees that if Disclosing Party is not successful in precluding the requesting
legal body from requiring the disclosure of the Confidential Information, it will furnish only that portion of the Confidential Information which is legally required.

	5.1.8
	The
Receiving Party's duties under this Subsection 5.1 shall expire five (5) years after the expiration or termination of this Agreement, or earlier upon written agreement of
the parties. 

G-8

  

	5.2
	Intellectual Property.

	5.2.1
	Each
party will continue to independently own its intellectual property, including all patents, patent applications, copyrights, trademarks, trade names, service marks,
know-how, trade secrets, data, proprietary processes, software, and all other forms of intellectual property, and nothing in this agreement shall confer any ownership right whatsoever to
one party in the intellectual property of the other party. In addition, usTLD Administrator, or its suppliers and/or licensees, as the case may be,shall own all right, title and interest in and to the
XRP, API's, Delegated Manager Tool Kits, and any software incorporated into the usTLD System, or any component of any of the foregoing, as well as all intellectual property appurtenant thereto.

	5.2.2
	Subject
only to the limited licenses set forth in Subsections 2.3.2, 3.5, and 5.1.2 above, no commercial use rights or any licenses of any kind under or to any patent, patent
application, copyright, trademark, trade name, service mark, know-how, trade secret, data, proprietary process, software or any other intellectual proprietary rights of any kind are
granted by one party to the other party by this Agreement, or by virtue of any disclosure of any Confidential Information to a Receiving Party under this Agreement. 

6.     INDEMNITIES AND LIMITATION OF LIABILITY  

	6.1
	Indemnification.    Delegated Manager, at its own expense and within thirty (30) days after presentation of a demand
by usTLD Administrator under this Section, will indemnify, defend and hold harmless usTLD Administrator and its directors, officers, employees, representatives, agents, affiliates, and stockholders
(along with usTLD Administrator, each an "Indemnified Person"), against any claim, suit, action, other proceeding of any kind (a "Claim") brought against that Indemnified Person based on, arising
from, or relating in any way to: (i) any product or service of Delegated Manager; (ii) any agreement, including Delegated Manager's dispute policy, with any Registrant or
re-seller; or (iii) Delegated Manager's domain name registration business, including, but not limited to, Delegated Manager's advertising, domain name application process, systems
and other processes, fees charged, billing practices and customer service, or any other business conducted by Delegated Manager; provided, however, that
in any such case: (a) usTLD Administrator or any other Indemnified Person provides Delegated Manager with reasonable prior notice of any such Claim, and (b) upon Delegated Manager's
written request, usTLD Administrator or any other Indemnified Person will provide to Delegated Manager all available information and assistance reasonably necessary for Delegated Manager to defend
such Claim; provided further that Delegated Manager reimburses usTLD Administrator and such other Indemnified Persons for their actual and reasonable
costs incurred in connection with providing such information and assistance. Delegated Manager will not enter into any settlement or compromise of any such indemnifiable Claim with respect to a
particular Indemnified Person without the prior written consent of such Indemnified Person, which consent shall not be unreasonably withheld. Delegated Manager will pay any and all costs, damages,
liabilities, and expenses, including, but not limited to, reasonable attorneys' fees and costs awarded against or otherwise incurred by usTLD Administrator and other Indemnified Persons in connection
with or arising from any such indemnifiable Claim.

	6.2
	Limitation of Liability.    EXCEPT WITH RESPECT TO DELEGATED MANAGER'S INDEMNIFICATION OBLIGATIONS SET FORTH IN ELSEWHERE IN
THIS AGREEMENT, IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE, EXEMPLARY OR CONSEQUENTIAL DAMAGES FOR ANY VIOLATIONS OF, OR CAUSES OF ACTION RELATING TO OR 

G-9

 

ARISING
FROM, THIS AGREEMENT, EVEN IF SUCH PARTY HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. 

7.     DISPUTE RESOLUTION  

	7.1
	Dispute Resolution; Governing Law.    Any and all disputes of any nature arising under or in connection with this Agreement,
including requests for specific performance, shall be resolved through binding arbitration conducted as provided in this Section pursuant to the rules of the American Arbitration Association ("AAA").
The arbitration shall be conducted in the English language and shall occur in the District of Columbia, Washington, D.C., USA. There shall be three (3) arbitrators: each party shall choose one
arbitrator, who together will select a third; if the two arbitrators are not able to agree on a third arbitrator within fifteen (15) calendar days of the designation of the second arbitrator,
the AAA shall choose the third. The parties shall bear the costs of the arbitration in equal shares, subject to the right of the arbitrators to reallocate the costs in their award as provided in the
AAA rules. The parties shall bear their own attorneys' fees in connection with the arbitration, and the arbitrators may not reallocate the attorneys' fees in conjunction with their award. The
arbitrators shall render their decision within ninety (90) calendar days of the selection of the third arbitrator. Any litigation brought to enforce an arbitration award shall be brought in a
Commonwealth or federal court in the Eastern District of the Commonwealth of Virginia, USA; however, the parties shall also have the right to enforce a judgment of such a court in any court of
competent jurisdiction. For the purpose of aiding the arbitration and/or preserving the rights of a party during the pendency of an arbitration, each party shall have the right to seek temporary or
preliminary injunctive relief from the arbitration panel or any court of competent jurisdiction located in the Eastern District of the Commonwealth of Virginia, USA, which shall not be a waiver of
this arbitration agreement. This Agreement shall be construed in accordance with and governed by the laws of the Commonwealth of Virginia (without regard to any rules or principles of conflicts of law
that might look to any jurisdiction outside Virginia). 

8.     TERM AND TERMINATION  

	8.1
	Term of the Agreement; Revisions.    The Term of this Agreement shall commence on the Effective Date and, unless earlier
terminated in accordance with the provisions of this Agreement, shall expire on the last expiration of the usTLD Agreement. In the event that revisions to usTLD Administrator's approved form of usTLD
Administrator-Delegated Manager Agreement (such as this one) are approved or adopted by NIST from time to time, Delegated Manager will either execute an amendment substituting the revised agreement in
place of this Agreement or, at its option exercised within thirty (30) days after receiving notice of such amendment, terminate this Agreement immediately by giving written notice to usTLD
Administrator. In the event that usTLD Administrator does not receive such executed amendment or notice of termination from Delegated Manager within such thirty (30) day period, Delegated
Manager shall be deemed to have accepted the provisions of such revised usTLD Administrator-Delegated Manager Agreement, and as such, shall be bound by all the terms and conditions of such revised
usTLD Administrator-Delegated Manager Agreement. usTLD Administrator will use commercially reasonable efforts to post such revised form of usTLD Administrator-Delegated Manager Agreement on its US
website at least thirty (30) days prior to its effective date.

	8.2
	Termination.    This Agreement may be terminated as follows:

	8.2.1
	Termination
For Cause.    In the event that either party materially breaches any of its obligations under this Agreement and such breach is not substantially cured within
thirty (30) calendar days after written notice thereof is given by the other party, then the 

G-10

 

non-breaching
party may, by giving written notice thereof to the other party, terminate this Agreement as of the date specified in such notice of termination. 

	8.2.2
	Termination
at Option of Delegated Manager.    Delegated Manager may terminate this Agreement at any time by giving usTLD Administrator thirty (30) days written
notice of termination.

	8.2.3
	Termination
Upon Loss of Delegated Manager's Accreditation.    This Agreement shall immediately terminate in the event Delegated Manager's accreditation by usTLD
Administrator is terminated or expires without renewal.

	8.2.4
	Termination
in the Event of Termination of usTLD Agreement.    This Agreement shall immediately terminate in the event the usTLD Agreement is terminated or expires without
entry of a subsequent usTLD Agreement with NIST and this Agreement is not assigned under Subsection 9.1.1 below.

	8.2.5
	Termination
in the Event of Insolvency or Bankruptcy.    This Agreement will automatically and immediately terminate if the Delegated Manager is adjudged insolvent or
bankrupt, or if proceedings are instituted by or against Delegated Manager seeking relief, reorganization or arrangement under any laws relating to insolvency or bankruptcy, or seeking any assignment
for the benefit of creditors, or seeking the appointment of a receiver, liquidator or trustee of Delegated Manager's property or assets or the liquidation, dissolution or winding up of Delegated
Manager's business.

	8.3
	Effect of Termination.    Upon the expiration or termination of this Agreement for any reason:

	8.3.1
	usTLD
Administrator will complete the registration of all domain names processed by Delegated Manager prior to the effective date of such expiration or termination, provided that
all Delegated Manager's payments to usTLD Administrator for Fees are current and timely.

	8.3.2
	Delegated
Manager shall immediately transfer its sponsorship of Registered Names to another Delegated Manager in compliance with any procedures established or approved by usTLD
Administrator.

	8.3.3
	All
Confidential Information in the possession of the Receiving Party shall be immediately returned to the Disclosing Party.

	8.3.4
	All
Fees and any other amounts owing to usTLD Administrator shall become immediately due and payable.

	8.4
	Survival.    In the event of termination of this Agreement, the following shall survive: (i) Subsections 2.6, 3.5,
5.1, 5.2, 6.1, 6.2, 7.1, 8.3.3, 8.3.4, 8.4, 9.2, 9.3.3, 9.5, 9.6, 9.8, 9.9, 9.10, 9.11 and 9.13 and (ii) the indemnification obligations of (a) Registrants under Subsection 3.4 and
(b) resellers under Subsection 3.12. Neither party shall be liable to the other for damages of any sort resulting solely from terminating this Agreement in accordance with its terms. 

9      MISCELLANEOUS  

	9.1
	Assignments.

	9.1.1
	Assignment to Successor usTLD Administrator.    In the event the usTLD Agreement is terminated (and such termination is
deemed final under the usTLD Agreement) or expires without entry by usTLD Administrator and NIST of a subsequent registry agreement, usTLD Administrator's rights under this Agreement may be assigned
to a entity with a subsequent registry agreement covering the usTLD upon NIST's giving Delegated Manager written notice within sixty (60) days of the termination or expiration, 

G-11

 

provided
that the subsequent usTLD Administrator assumes all or substantially all of the duties of usTLD Administrator under this Agreement. 

	9.1.2
	Assignment in Connection with Assignment of usTLD Agreement with NIST.    In the event that the usTLD Agreement for the
usTLD is validly assigned, usTLD Administrator's rights under this Agreement shall be automatically assigned to the assignee of the usTLD Agreement, provided that the assignee assumes all or
substantially all of the duties of usTLD Administrator under this Agreement.

	9.1.3
	Other Assignments.    Except as otherwise expressly provided in this Agreement, the provisions of this Agreement shall
inure to the benefit of and be binding upon, the successors and permitted assigns of the parties. Neither party shall assign or transfer its rights or obligations under this Agreement without the
prior written consent of the other party, which shall not be unreasonably withheld; provided, however, that usTLD Administrator shall have the right to assign all its rights and delegate all its
duties under this Agreement to an affiliated organization without such consent.

	9.2
	Notices.    Any notice or other communication required or permitted to be delivered to any party under this Agreement shall
be in writing and shall be deemed properly delivered, given and received when delivered by hand, by registered mail (return receipt requested), by courier or express delivery service, by
e-mail (against of receipt of confirmation of delivery) or by telecopier (against receipt of answerback confirming delivery) during business hours to the address or telecopier number, or
e-mail address set forth beneath the name of such party below or when delivery as described above is refused by the intended recipient, unless such party has given a notice of a change of
address in writing pursuant to the foregoing. Notwithstanding the foregoing, notice shall be deemed properly given from usTLD Administrator to Delegated Manager at such time as usTLD Administrator
posts any notice, update, modification or other information on its U.S. website, so long as such notice, update, modification or other information is intended for all Delegated Managers generally
(e.g., NIST-mandated revisions to the form usTLD Administrator-Delegated Manager Agreement). 

If
to Delegated Manager: 

	 

	 

	 

	 

	 

	 

with
copy to: 

	 

	 

	 

	 

	 

	 

G-12

 

If
to usTLD Administrator: 

	NeuStar, Inc.

1120 Vermont Avenue, N.W.

Suite 400

Washington, D.C. 20005

Attn: VP of Policy and Industry Relations

phone:

fax:

with
a copy to: 

	NeuStar, Inc.

1120 Vermont Avenue, N.W.

Suite 400

Washington, D.C. 20005

Attn: General Counsel

phone:

fax:

9.3   Representations and Warranties.

	9.3.1
	Delegated Manager.    Delegated Manager represents and warrants that: (1) it is an organization (e.g., corporation,
partnership, limited liability company, government agency) duly formed, validly existing and in good standing under the laws of
the                        , (2) it has all requisite power and authority
to execute, deliver and perform its obligations under this Agreement (3) it is, and during the Term of this Agreement will continue to be, accredited by usTLD Administrator, (4) the
execution, performance and delivery of this Agreement has been duly authorized by Delegated Manager, (5) no further approval, authorization or consent of any governmental or regulatory
authority is required to be obtained or made by Delegated Manager in order for it to enter into and perform all its obligations under this Agreement.

	9.3.2
	usTLD Administrator.    usTLD Administrator represents and warrants that: (1) it is a corporation duly incorporated,
validly existing and in good standing under the laws of the State of Delaware, (2) it has all requisite corporate power and authority to execute, deliver and perform its obligations under this
Agreement, (3) the execution, performance and delivery of this Agreement has been duly authorized by usTLD Administrator, and (4) no further approval, authorization or consent of any
governmental or regulatory authority is required to be obtained or made by usTLD Administrator in order for it to enter into and perform all its obligations under this Agreement.

	9.3.3
	Disclaimer of Warranties.    THE XRP, APIs, DELEGATED MANAGER TOOLKIT, usTLD SYSTEM AND ANY COMPONENT THEREOF ARE PROVIDED
"AS-IS" AND WITHOUT ANY WARRANTY OF ANY KIND. usTLD OPERATOR EXPRESSLY DISCLAIMS ALL WARRANTIES AND/OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
AND CONDITIONS OF MERCHANTABILITY OR SATISFACTORY QUALITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. usTLD OPERATOR DOES NOT WARRANT THAT THE XRP, APIs, DELEGATED
MANAGER TOOLKIT, usTLD SYSTEM OR ANY COMPONENT THEREOF WILL MEET DELEGATED MANAGER'S REQUIREMENTS, OR THAT THE OPERATION OF XRP, APIs, DELEGATED MANAGER TOOLKITS, THE usTLD SYSTEM OR ANY COMPONENT
THEREOF WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE XRP, APIs, DELEGATED MANAGER 

G-13

 

TOOLKIT,
usTLD SYSTEM OR ANY COMPONENT THEREOF WILL BE CORRECTED. FURTHERMORE, usTLD OPERATOR DOES NOT WARRANT NOR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE XRP, APIs, DELEGATED
MANAGER TOOLKITS, usTLD SYSTEM OR ANY COMPONENT THEREOF OR RELATED DOCUMENTATION IN TERMS OF THEIR CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. SHOULD THE XRP, APIs, DELEGATED MANAGER TOOLKIT,
THE usTLD SYSTEM OR ANY COMPONENT THEREOF PROVE DEFECTIVE, DELEGATED MANAGER ASSUMES THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION OF DELEGATED MANAGER'S OWN SYSTEMS AND SOFTWARE. 

In
the event of any conflict in this Agreement between this Subsection 9.3.3 and any other provision, this Subsection 9.3.3 will govern and control. 

	9.4
	Insurance.    During the Term of this Agreement (including any renewal terms), Delegated Manager shall have in place
US$500,000 in comprehensive legal liability insurance from a reputable insurance provider with an A.M. Best rating of "A" or better. Such insurance shall be used to indemnify and hold harmless
usTLD Administrator and its employees, directors, officers, representatives, agents, affiliates, and stokholders from all costs and damages (including without limitation reasonable attorneys' fees)
which it may suffer by reason of Delegated Manager's failure to indemnify usTLD Administrator as provided above; provided, however, that Delegated
Manager's indemnity obligations under this Agreement shall not deemed to be limited by the amount of such insurance. Delegated Manager shall provide a
copy of the insurance policy to usTLD Administrator upon usTLD Administrator's request and shall name usTLD Administrator and the other Indemnified Persons as additional insureds under that policy.

	9.5
	Third-Party Beneficiaries.    The parties expressly agree that NIST is an intended third-party beneficiary of this Agreement.
Otherwise, this Agreement shall not be construed to create any obligation by either party to any non-party to this Agreement, including any Registrant or re-seller. Delegated
Manager acknowledges that nothing in this Agreement shall confer upon Delegated Manager or any person or entity the status of an intended third-party beneficiary of the usTLD Agreement.

	9.6
	Relationship of the Parties.    Nothing in this Agreement shall be construed as creating an employer-employee or agency
relationship, a partnership or a joint venture between the parties.

	9.7
	Force Majeure.    Except for the non-payment of Fees, neither party shall be liable to the other for any loss or
damage resulting from any cause beyond its reasonable control (a "Force Majeure Event") including, but not limited to, insurrection or civil disorder, war or military operations, national or local
emergency, acts or omissions of government or other competent authority, compliance with any statutory obligation or executive order, industrial disputes of any kind (whether or not involving either
party's employees), fire, lightning, explosion, flood, subsidence, weather of exceptional severity, equipment or facilities shortages which are being experienced by providers of telecommunications
services generally, or other similar force beyond such Party's reasonable control, and acts or omissions of persons for whom neither party is responsible. Upon occurrence of a Force Majeure Event and
to the extent such occurrence interferes with either party's performance of this Agreement, such party shall be excused from performance of its obligations (other than payment obligations) during the
first six (6) months of such interference, provided that such party uses commercially reasonable efforts to avoid or remove such causes of nonperformance as soon as possible. 

G-14

 

	9.8
	Amendments.    Except as otherwise provided herein, no amendment, supplement, or modification of this Agreement or any
provision hereof shall be binding unless executed in writing by authorized signatories of both parties.

	9.9
	Waivers.    No failure on the part of either party to exercise any power, right, privilege or remedy under this Agreement,
and no delay on the part of either party in exercising any power, right, privilege or remedy under this Agreement, shall operate as a waiver of such power, right, privilege or remedy; and no single or
partial exercise or waiver of any such power, right, privilege or remedy shall preclude any other or further exercise thereof or of any other power, right, privilege or remedy. Neither party shall be
deemed to have waived any claim arising out of this Agreement, or any power, right, privilege or remedy under this Agreement, unless the waiver of such claim, power, right, privilege or remedy is
expressly set forth in a written instrument duly executed and delivered on behalf of such party; and any such waiver shall not be applicable or have any effect except in the specific instance in which
it is given.

	9.10
	Attorneys' Fees.    Except as otherwise may be provided in Subsection 7.1 above, if any legal action or other legal
proceeding (including arbitration) relating to the performance under this Agreement or the enforcement of any provision of this Agreement is brought against a party hereto, the prevailing party shall
be entitled to recover reasonable attorneys' fees, costs and disbursements (in addition to any other relief to which the prevailing party may be entitled).

	9.11
	Construction; Severability.    The parties agree that any rule of construction to the effect that ambiguities are to be
resolve against the drafting party shall not be applied in the construction or interpretation of this Agreement. Unless otherwise stated in this Agreement, references to a number of days shall mean
consecutive calendar days. In the event that any clause or portion thereof in this Agreement is for any reason held to be invalid, illegal or unenforceable, the same shall not affect any other portion
of this Agreement, as it is the intent of the parties that this Agreement shall be construed in such fashion as to maintain its existence, validity and enforceability to the greatest extent possible.
In any such event, this Agreement shall be construed as if such clause or portion thereof had never been contained in this Agreement, and there shall be deemed substituted therefor such provision as
will most nearly carry out the intent of the parties as expressed in this Agreement to the fullest extent permitted by applicable law.

	9.12
	Further Assurances.    Each party hereto shall execute and/or cause to be delivered to the other party hereto such
instruments and other documents, and shall take such other actions, as such other party may reasonable request for the purpose of carrying out or evidencing any of the transactions contemplated by
this Agreement.

	9.13
	Entire Agreement.    This Agreement (including its exhibits, which form a part of it) constitutes the entire
agreement between the parties concerning the subject matter of this Agreement and supersedes any prior agreements, representations, statements, negotiations, understandings, proposals or undertakings,
oral or written, with respect to the subject matter expressly set forth herein. In the event of any conflict between the terms of this usTLD Administrator-Delegated Manager Agreement and the
Accreditation Agreement, the usTLD Administrator-Delegated Manager Agreement shall govern and control.

	9.14
	Counterparts.    This Agreement may be executed in one or more counterparts, each of which shall be deemed an original, but
all of which together shall constitute one and the same instrument. 

G-15

 

        IN
WITNESS WHEREOF, the parties hereto have executed this Agreement as of the date first set forth above. 

	NeuStar, Inc.	 	[Name of Delegated Manager]
	

By:	
 	

 
	
 	

By:	
 	

 

	Name:	 	 
	 	Name:	 	 

	Title:	 	 
	 	Title:	 	 

G-16

  

 
 

Exhibit A    
    
    Delegated Manager Tool Kit    
    

        usTLD Administrator-Delegated Manager Software Development Kit includes, but is not limited to the following: 

	•
	Reference
client implementations:

	•
	Java

	•
	C++

	•
	PERL

	•
	Interface
definition: XML Schema

	•
	usTLD
Administrator Operational Profile (our extensions)

	•
	Authentication
and Encryption guidelines

	•
	XRP
"feature freeze" drafts

	•
	XRP
test plan and coverage matrix

	•
	Java,
C++ and PERL API documentation 

G-17

  

 
 

Exhibit B    
    
    Engineering and Customer Service Support    
    

        During the Term of this Agreement, usTLD Administrator will provide reasonable telephone and electronic customer support to Delegated Manager, not Registrants or
prospective customers of Delegated Manager, for non-technical issues solely relating to the usTLD System and its operation. usTLD Administrator will provide Delegated Manager with a
telephone number and e-mail address for such support during implementation of the XRP, APIs and any reference client software included in the Delegated Manager Tool Kit. While
e-mail and FAQs are the primary method of help, usTLD Administrator will provide support on a 7-day/24-hour basis. usTLD Administrator will provide a
web-based customer service capability in the future and such web-based support will become the primary method of customer service support to Delegated Manager at such time. 

        The
usTLD Administrator provides a clear, concise and efficient deliberation of customer support responsibilities. Delegated Managers provide support to registrants (i.e., Registrants)
and registries (like usTLD Administrator) provide support for Delegated Managers. This structure allows the usTLD Administrator to focus its support on the highly technical and administratively
complex issues that arise between the usTLD Administrator and the Delegated Manager and to focus on the system operations supporting the usTLD. 

Technical Help Systems  

        usTLD Administrator will provide its Delegated Managers with the following types of technical support: 

	•
	Web-based
self-help services, including:

	•
	Knowledge
bases

	•
	Frequently
asked questions

	•
	White
papers

	•
	Downloads
of XRP client software

	•
	Support
for email messaging

	•
	Telephone
support from a central Help Desk

	•
	Fee-based
consulting services. 

Web Portal  

        usTLD Administrator will implement a secure Web-based multimedia portal to help support Delegated Manager operations. To obtain access to these
Web-based services, a Delegated Manager must register its registrants usTLD Administrator, and must have implemented our security features, including SSL encryption, log in with user ID
and password, and digital certificates for authentication. The home page of the web portal will include a notice to Delegated Managers of planned outages for database maintenance or installation of
software upgrades. usTLD Administrator will use commercially reasonable effort to post this notification at least thirty (30) days prior to the event in addition to active notification
including phone calls and email. Finally, seven (7) days and again two (2) days prior to the scheduled event, usTLD Administrator will use both an email and a Web-based
notification to remind Delegated Managers of the outage. 

        Non-affiliated
Delegated Managers and the general Internet community may obtain generic information from usTLD Administrator's public website, which will describe the TLD
service offerings and list of Delegated Managers, including Delegated Manager, providing domain-name services. 

G-18

 

Central Help Desk  

        In addition to implementing the website, usTLD Administrator will provide telephone support to Delegated Managers through a central Help Desk. Access to the help
desk telephone support is through an automatic call distributor that routes each call to the next available customer support specialist. usTLD Administrator will authenticate callers by using caller
ID and by requesting a pre-established pass phrase that is different for each Delegated Manager. Requests for assistance may also come to the Help Desk via email, either directly or via
the secure website. The Help Desk's three tiers of support are: 

Tier-1
Support.    Telephone support to Delegated Managers who normally are calling for help with customer domain-name problems and such other issues such as XRP
implementation or billing and collection. Problems that can't be resolved at Tier 1 are escalated to Tier 2. 

Tier-2
Support.    Support provided by members of the technical support team, who are functional experts in all aspects of domain-name registration. In addition to
resolving escalated Tier 1 problems with XRP implementation and billing and collection, Tier 2 staff provides technical support in system tuning and workload processing. 

Tier
3 Support.    Complex problem resolution provided by on-site maintenance technicians, third party systems and software experts, and vendors, depending on the nature of the
problem. 

        In
turn, the Help Desk uses an automated software package to collect call statistics and record service requests and trouble tickets in a help desk database. The help desk database
documents the status of requests and tickets. Each customer-support and technical support specialist uses this problem management process to respond to trouble tickets with a troubleshooting,
diagnosis, and resolution procedure and a root-cause analysis. 

Escalation Policy  

        usTLD Administrator's escalation policy defines procedures and timelines for elevating problems either to functional experts or to management for resolution if
they are not resolved within the escalation-policy time limits. The following table is an overview of the escalation policy. 

	Level
 
	 	Description
	 	Escalation Policy
	 	Notification

	I	 	Catastrophic outage affecting overall registry operations	 	Data-center manager escalates to usTLD Administrator management and Disaster-Recovery Team if not resolved in 15 minutes	 	Web portal and e-mail notifications to all Delegated Managers within 15 minutes; updates every 30 minutes
	II	 	Systems outage affecting one or two Delegated Manager sessions but not the entire system	 	Systems engineer escalates to data-center manager if not resolved in one hour	 	Web-portal notification to all Delegated Managers; hourly updates
	III	 	Technical questions	 	Help Desk customer-support specialist escalates to the systems engineer if not resolved in two hours	 	Hourly updates to Delegated Manager via e-mail
	IV	 	Basic questions	 	Help Desk customer-support specialist escalates to the systems engineer if not resolved within four hours	 	Hourly updates to Delegated Manager via e-mail

G-19

 

Staffing  

        Initially, usTLD Administrator will staff its Help Desk with a complement of customer service specialists. usTLD Administrator will add staff as necessary to
respond to incoming requests within the performance specification guidelines. Customer-service specialists will obtain assistance from usTLD Administrator's technical staff for any problems that
cannot be resolved in one (1) phone call. 

Test and Evaluation Facility  

        usTLD Administrator will establish an operational test-and-evaluation facility that will be available for Delegated Managers to test their
client XRP system. usTLD Administrator's technical-support team, which consists of functional experts in the processes and technologies for domain-name registration, will support the
Delegated Managers' testing. 

        Once
each new Delegated Manager is satisfied that its system is compatible with the usTLD System, it will schedule a formal acceptance test that will be monitored by usTLD
Administrator's system engineer. After a Delegated Manager has passed the acceptance test, usTLD Administrator will issue its user id, passwords, and digital certificates, and the Delegated Manager
can then begin operations. 

Customer Satisfaction Survey  

        To determine the satisfaction of Delegated Managers with usTLD Services, usTLD Administrator will implement a Web-based customer-satisfaction survey
that will consist of a set of survey questions with responses ranging from one to five on the Likert Scale. usTLD Administrator will tabulate the results and plans to publish them on the website
periodically. 

        To
further verify the quality of usTLD Administrator's customer services, usTLD Administrator anticipates commissioning a bi-annual customer-satisfaction survey by an
independent third party. 

G-20

  

 
 

Exhibit C    
    
    usTLD Administrator's Operational Standards,
  Policies, Procedures, and Practices    
    

I.     Registration Requirements  

        Before the usTLD Administrator will accept applications for registration from a Delegated Manager, all domain name applicants in the.us TLD must: 

	1.
	Enter
into an electronic or paper registration agreement with the Delegated Manager, in accordance with the Accreditation Agreement with usTLD Administrator and this Agreement. Such
electronic or paper registration agreement shall include, at a minimum, the following certifications:

	a)
	The
data provided in the domain name registration application is true, correct, up to date and complete; and

	b)
	The
registrant will keep the information provided above up to date.

	2.
	Certify
in the Registration Agreement that to the best of his, her or its knowledge the domain name registrant has the authority to enter into the Registration Agreement and meets all
the US Nexus Requirement set forth below. 

II.    US Nexus Requirement  

        Registrants in the usTLD must be either: 

	1.
	A
natural person (i) who is a citizen or permanent resident of the United States of America or any of its possessions or territories, or (ii) whose primary place of
domicile is in the United States of America or any of its possessions, or

	2.
	An
entity or organization that is (i) incorporated within one of the fifty (50) U.S. states, the District of Columbia, or any of the United States possessions or
territories or (ii) organized or otherwise constituted under the laws of a state of the United States of America, the District of Columbia or any of its possessions or territories, or

	3.
	An
entity or organization (including a federal, state, or local government of the United States, or a political subdivision thereof) that has a bona fide presence in the United States. 

        Whether
a prospective registrant has a "bona fide presence in the United States" will be determined on a case-by-case basis in light of all relevant facts and
circumstances at the time of application for a usTLD domain name. This requirement is intended to ensure that only those individuals or organizations that have a substantive connection to the United
States are permitted to register for usTLD domain names. 

        Factors
that should be considered in determining whether an entity or organization has a bona fide presence in the United States shall include, without limitation, whether such
prospective usTLD domain name registrant: 

	•
	Regularly
performs activities within the United States related to the purposes for which the entity or organization is constituted (e.g., providing services to customers,
conducting regular training activities, attending conferences), provided such activities are not conducted solely or primarily to permit it to register for a usTLD domain name;

	•
	Maintains
an office or other facility in the United States for a business, noncommercial, educational, or governmental purpose and not solely or primarily to permit it to
register for a usTLD domain name; or 

G-21

 

	•
	Derives
a material portion of its revenues or net income from sales to purchasers located in the United States. For these purposes, if a prospective usTLD domain name
registrant's revenues from sales to purchasers located in the United States were at least 5% of such entity's or organization's total revenues or net income for its last completed fiscal year, such
entity or organization will be presumed to have a bona fide presence in the United States. 

        For
purposes of this definition, the terms United States and United States of America shall include all U.S. territories and possessions. 

        It
shall be a continuing requirement that all usTLD domain name registrants maintain the US Nexus Requirement. 

        The
Nexus Requirement will be enforced through an initial screening of the contact information provided by the registrant, as well as a challenge process permitted through the Nexus
Dispute Policy discussed below. The screening by usTLD Administrator will verify that selected field, within the contact information provided, on its face, meets the Nexus Requirement and that the
registrant has certified compliance with the requirement, as well as certified that the nameservers identified are located within the United States. In
the event that the contact information provided does not meet the above requirement, the name requested will be placed on hold within the registry and the registrant will be given an opportunity to
correct any mistake or demonstrate compliance with the Nexus requirement. If no action is taken by the registrant within the 30-day period, the registration will be cancelled and the name
will be returned to available status. If, on the other hand, the registrant is able to demonstrate compliance with the requirement, the name will be registered. 

III.  Nexus Dispute Policy  

        Although the Nexus Requirement will initially be enforced through a usTLD Delegated Manager's screening of the contact information provided by the registrant, and
the registrant will certify that it meets at least one of the Nexus requirements set forth above, usTLD Administrator understands that
disputes may arise as to the authenticity, veracity or accuracy of the registrant's Nexus certification. Therefore, usTLD Administrator, as administrator of the usTLD has devised a Nexus Dispute
Policy ("NDP") which will be administered solely by the usTLD Administrator, or its designated representative. The NDP will provide interested parties with an opportunity to challenge a registration
not complying with the Nexus Requirement. 

        In
the event that a third party wishes to challenge the authenticity or veracity of a .US registrant's United States Nexus, that party may submit a "Nexus Challenge" to the usTLD
Administrator or its authorized representative. The challenger must submit a written statement to the usTLD Administrator via first class mail alleging in specificity evidence to support its
allegation that the registrant fails to meet any of the Nexus Requirements set forth above. 

        Once
a challenge is received by the usTLD Administrator the domain name shall be "locked" by the usTLD Administrator until the matter is resolved. While in a "locked" position, the
registrant may not (i) change any of the contact information for that particular domain name or (ii) transfer the domain name to any third party. 

        In
the event that the usTLD Administrator finds that the challenger has established a prima facie case that the registrant has not met any of the Nexus Requirements, the usTLD
Administrator shall issue a letter to the registrant to submit evidence of compliance with the Nexus Requirements ("Letter"). The registrant shall have a period of thirty (30) days from the
date of the Letter to submit evidence of compliance. If, within the thirty (30) days, the registrant submits evidence establishing any of the Nexus Requirements, the registrant shall be
permitted to keep the domain name. 

        If,
however, the registrant either (i) does not respond within the thirty days, or (ii) is unable to demonstrate through documentary evidence that it met any of the Nexus
Requirements prior to the 

G-22

 

date
the NDP was invoked, the usTLD Administrator shall issue a finding that the registrant has failed to meet the Nexus Requirements. Upon such a finding, the registrant shall be given a total of
thirty (30) days to cure the US Nexus deficiency. If the registrant is able to demonstrate within (30) days that it has cured such deficiency, the registrant shall be allowed to keep the
domain name. If the registrant either (i) does not respond within the thirty (30) days, or (ii) is unable to proffer evidence demonstrating compliance with the Nexus Requirements,
the domain name registration shall be deleted from the registry database and the domain name will be placed into the list of available domain names. This process represents the exclusive remedy for an
NDP challenger. 

        usTLD
Administrator reserves the right to modify this NDP at any time with the permission of COTR. usTLD Administrator will post its revised NDP on its Website at least thirty
(30) calendar days before it becomes effective. 

IV.    Reservation  

        usTLD Administrator reserves the right to deny, cancel or transfer any registration 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, in compliance with any dispute resolution
process; (3) to avoid any liability, civil or criminal, on the part of usTLD Administrator, as well as its affiliates, subsidiaries, officers, directors, representatives, employees, and
stockholders; (4) for violations of this Agreement (including its Exhibits); or (5) to correct mistakes made by usTLD Administrator or any Delegated Manager in connection with a domain
name registration. usTLD Administrator also reserves the right to freeze a domain name during resolution of a dispute. 

G-23

  

 
 

Exhibit D    
    
    Registration Fees    
    

	•
	Initial Registration.    The initial registration fee shall be determined by usTLD
Administrator pursuant to the Locality-based usTLD Compliance Report.

	•
	Renewal Fees.    The renewal registration fee shall be determined by usTLD Administrator
pursuant to the Locality-based usTLD Compliance Report.

	•
	Enhanced Whois Service.    Delegated Manager agrees to pay the non-refundable amounts as set forth
below: 

        To
be provided with at least 30 days advance notice: Yearly Subscription Fee Rate, One time Usage Fee 

        NOTE:    usTLD
Administrator reserves the right to revise the Fees prospectively upon thirty (30) days notice to Delegated Manager, provided that such adjustments are
consistent with the usTLD Agreement. 

G-24

   H.    Draft Registrar/Registry Contract  

        NeuStar will establish appropriate legal relationship's with usTLD Accredited Registrars to provide the accountability and administrative
certainty required to maintain the integrity and stability of the usTLD.

	•
	Agreement modeled after ICANN Registry-Registrar business model to encourage rapid competitive acceptance of usTLD

	•
	Establishes mutual obligations of usTLD Administrators and expanded usTLD Registrars

	•
	Establishes Administrator performance specifications and performance credits to ensure Administrator compliance

        As
previously noted in Section G, an important part of its work to centralize and enhance the usTLD delegated space, NeuStar intends to establish comprehensive contractual
arrangements with all of the usTLD Registrar Delegated Managers. The agreements will establish clear and comprehensive parameters for the management of the enhanced usTLD Registrars, as well as set
basic requirements and obligations binding on NeuStar as the usTLD Administrator and the Registrars. In addition, because the usTLD Administrator will not have a direct contractual arrangement with
the registrants, these contracts will include "flow through obligations", such as the Nexus requirement or the obligation to provide accurate Whois data, that the Registrar will be required to enforce
in its contracts with its registrants. These legal relationships will help provide the accountability and administrative certainty necessary to maintain the stable operation of the usTLD. 

        Recognizing
the significant and useful effort that has gone into the development of similar agreements in the ICANN context, these agreements will be patterned after the
Registry-Registrar agreement developed for the new gTLDs by ICANN. As with the agreement with delegated managers, these agreements contain certain modifications necessary to address the dynamics and
specific requirements
of the usTLD. Such changes have, however, been kept to a minimum. Because the shared registry business model developed for the gTLD space has proven successful and given the similarity of the expanded
usTLD to the gTLDs operated under the purview of ICANN, even fewer modifications are warranted The Registry-Registrar Agreement is attached hereto. This document will be a standard document signed by
all usTLD registrars and is subject to further revision and final approval by the Contracting Officer. 

H-1

  

WORKING DRAFT DATED JULY 27, 2001  

(EXPANDED .US SPACE)  

 
  usTLD ADMINISTRATOR-REGISTRAR AGREEMENT    
    

        This usTLD Administrator-Registrar Agreement is made and effective as
of                        , 200  , by and between NeuStar, Inc., a Delaware
corporation, with its principal place of business located at 1120 Vermont Avenue, Suite 400, Washington, D.C. 20005 ("usTLD Administrator"), and [Registrar's
name], a [jurisdiction and type of organization], with its principal place of business
located at [Registrar's location] ("Registrar"). 

        WHEREAS, usTLD Administrator has been appointed to be the administrator of the usTLD by the U.S. Department of Commerce, National
Institute of Standards and Technology to operate a shared registration system, TLD nameservers, and other equipment for the ".us" top-level domain; 

        WHEREAS, multiple registrars will provide Internet domain name registration services within the.us top-level domain pursuant
to usTLD Administrator-Registrar Agreements substantially similar to this Agreement; 

        WHEREAS, Registrar wishes to act as a registrar for domain names within the.us top-level domain. 

        NOW, THEREFORE, for and in consideration of the mutual promises, benefits and covenants contained herein and for other good and valuable
consideration, the receipt, adequacy and sufficiency of which are hereby acknowledged, usTLD Administrator and Registrar, intending to be legally bound, hereby agree as follows: 

1.     DEFINITIONS  

	1.1
	"Agreement"
means this usTLD Administrator-Registrar Agreement between usTLD Administrator and Registrar, as such may be amended from time to time in the future.

	1.2
	The
"APIs" are the application program interfaces by which Registrar may interact, through the XRP, with the usTLD System.

	1.3
	"Confidential
Information" means all information and materials, including, without limitation, computer software, data, information, databases, protocols, reference implementation and
documentation, and functional and interface specifications provided by one party to this Agreement (the "Disclosing Party") to the other party (the "Receiving Party") and marked or otherwise
identified as "confidential", provided that if a communication is oral, the Disclosing Party will notify the Receiving Party in writing within fifteen (15) days of the disclosure of the
confidential nature of such information.

	1.4
	"DNS"
means the Internet domain name system.

	1.5
	The
"Effective Date" shall be the date first set forth above.

	1.6
	"NIST"
means the U.S. Department of Commerce, National Institute of Standards and Technology (or any successor agency or governmental unit charged with ultimate responsibility for the
country code top-level domain name for the United States).

	1.7
	"Personal
Data" refers to data about any identified or identifiable natural person.

	1.8
	"Registered
Name" refers to a domain name within the domain of the usTLD, about which usTLD Administrator or an affiliate engaged in providing usTLD Services maintains data in a usTLD
Database, arranges for such maintenance, or derives revenue from such maintenance.

	1.9
	"Registrant"
means the holder of a Registered Name. 

H-2

 

	1.10
	The
word "Registrar" when appearing with an initial capital letter, refers to [Registrar Name], a party to this Agreement.

	1.11
	The
word "registrar" when appearing without an initial capital letter, refers to an entity that contracts with Registrants and with the usTLD Administrator to provide domain name
registration services and collects registration data about the Registrants and submits registration information for entry in the usTLD Database and is party to an Accreditation Agreement with usTLD
Administrator.

	1.12
	"Registrar
Services" means services provided by a registrar in connection with the usTLD under this Agreement, and includes contracting with Registrants, collecting registration data
about the Registrants, and submitting registration information for entry in the usTLD Database.

	1.13
	The
"Registrar Tool Kit" shall mean the Tool Kit set forth in Exhibit A.

	1.14
	"Term"
means the term of this Agreement, as set forth in Subsection 8.1.

	1.15
	A
"TLD" means a top-level domain of the DNS.

	1.16
	In
order to have to required "U.S. Nexus", a Registrant must be: (a) a natural person (i) who is a citizen or permanent resident of the United States of America or any
of its possessions or territories, or (ii) whose primary place of domicile is in the United States of America or any of its possessions, or (b) an entity or organization that is
(i) incorporated within one of the fifty (50) U.S. states, the District of Columbia, or any of the United States possessions or territories or (ii) organized or otherwise
constituted under the laws of a state of the United States of America, the District of Columbia or any of its possessions or territories, or (c) an entity or organization (including a federal,
state, or local government of the United States, or a political subdivision thereof) that has a bona fide presence in the United States. "usTLD" means the .us TLD.

	1.17
	"usTLD
Agreement" means the usTLD Agreement between usTLD Administrator and NIST dated [date of usTLD Agreement] for the administration and operation of the
usTLD.

	1.18
	"usTLD
Database" means a database comprised of data about one or more DNS domain names within the domain of the usTLD that is used to generate either DNS resource records that are
published authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names.

	1.19
	"usTLD
Policy Council" shall mean the United States Policy Advisory Council established by the usTLD Administrator under the usTLD Agreement

	1.20
	"usTLD
Services" means services provided as an integral part of the operation of the usTLD.

	1.21
	The
"usTLD System" means the registry system operated by usTLD Administrator for Registered Names in the usTLD.

	1.22
	"XRP"
means the extensible registry-registrar protocol used by the usTLD System. 

        Other
terms used in this Agreement as defined terms shall have the meanings ascribed to them in the context in which they are defined. 

2.     OBLIGATIONS OF USTLD ADMINISTRATOR  

	2.1
	Access to usTLD System.    Throughout the Term of this Agreement, usTLD Administrator shall provide Registrar with access as
a registrar to the usTLD System. Nothing in this Agreement entitles Registrar to enforce any agreement between usTLD Administrator and 

H-3

 

NIST,
and Registrar shall not be deemed to be a third-party beneficiary under the usTLD Agreement. 

	2.2
	Maintenance of Registrations Sponsored by Registrar.    Subject to the provisions of this Agreement, and requirements under
the usTLD Agreement, usTLD Administrator shall maintain the registrations of Registered Names sponsored by Registrar in the usTLD System so long as Registrar has paid the Fees required by Subsection
4.1 below and this Agreement remains in effect.

	2.3
	Provision of Tool Kits; Limited License.

	2.3.1
	Registrar Tool Kit.    No later than five (5) business days after the Effective Date, usTLD Administrator shall
provide to Registrar a copy of the Registrar Tool Kit, which shall provide sufficient technical specifications to permit registrar interface with the usTLD System and employ its features that are
available to Registrars, provided that, if the Effective Date occurs prior to the date that usTLD Administrator has made the usTLD Tool Kit available to.us registrars generally ("Availability Date"),
usTLD Administrator shall provide to Registrar a copy of the usTLD Tool Kit, no later than five (5) business days after the Availability Date. Subject to the terms and conditions of this
Agreement, UsTLD Administrator hereby grants Registrar and Registrar accepts a non-exclusive, non-transferable, worldwide limited license to use for the Term and purposes of
this Agreement, all components owned by or licensed to UsTLD Administrator in and to the RRP, APIs, any reference client software and any other intellectual property included in the Registrar Tool
Kit, as well as updates and redesigns thereof, to provide domain name registration services in the usTLD only and for no other purpose.

	2.3.2
	Limited License.    Subject to the terms and conditions of this Agreement, including without limitation Registrar's timely
payment of all Fees, usTLD Administrator hereby grants Registrar and Registrar accepts a non-exclusive, non-transferable, worldwide limited license to use for the Term and
purposes of this Agreement the XRP, APIs and any reference client software included in the Registrar Tool Kits, as well as any updates and redesigns thereof, for providing domain name Registrar
Services in the usTLD only and for no other purpose.

	2.4
	Changes to usTLD System.    usTLD Administrator may in its discretion from time to time make modifications to the XRP, APIs,
or other software or materials licensed hereunder that will modify, revise or augment the features of the usTLD System. usTLD Administrator will use commercially reasonable efforts to provide
Registrar with at least ninety (90) days notice prior to the implementation of any material changes to the XRP, APIs or software licensed hereunder. usTLD Administrator shall have no obligation
under this Agreement to update, modify, maintain, or repair any XRP, APIs, or other software materials (or any updates or redesigns thereto) licensed under this Agreement to Registrar.

	2.5
	Engineering and Customer Service Support; Performance Specifications.    usTLD Administrator shall provide Registrar with
engineering and customer service support as set forth in Exhibit B.

	2.6
	Handling of Personal Data.    usTLD Administrator shall notify Registrar of the purposes for which Personal Data submitted to
usTLD Administrator by Registrar is collected, the intended recipients (or categories of recipients) of such Personal Data, and the mechanism for access to and correction of such Personal Data. usTLD
Administrator shall take commercially reasonable steps to protect Personal Data from loss, misuse, unauthorized disclosure, alteration or destruction. 

H-4

 

	2.7
	NIST/usTLD Administrator Requirements.    usTLD Administrator's obligations hereunder are subject to modification at any time
as the result of NIST-mandated requirements and NeuStar policies developed by usTLD Administrator through its United States Policy Advisory Council ("usTLD Policy Council") from time to
time. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such NIST requirements or the usTLD Policy Council (the Council) policies in accordance with the
stated timelines. 

3.     OBLIGATIONS OF REGISTRAR  

	3.1
	Accredited Registrar.    On or prior to the Effective Date of this Agreement, Registrar shall enter into an accreditation
agreement with usTLD Administrator ("Accreditation Agreement"), the form of which is attached hereto as Exhibit C, and during the Term of this
Agreement, Registrar shall maintain in full force and effect its accreditation by usTLD Administrator as a registrar for the usTLD.

	3.2
	Registrar Responsibility for Customer Support; Participation in Marketing Campaigns/Community Outreach Programs.    As
provided for in the Accreditation Agreement, Registrar shall provide (i) support to accept and process orders for Registered Names from proposed Registrants and (ii) customer service
(including domain name record support) and billing and technical support to Registrants. In addition, Registrar will use commercially reasonable efforts to market, either directly or through
authorized re-sellers, Registered Names to potential Registrants and to solicit such potential customers to register for Registered Names, and Registrar will cooperate with usTLD
Administrator in marketing campaigns or community outreach programs that usTLD Administrator may commence from time to time.

	3.3
	Registrar's Registration Agreement; U.S. Nexus Requirements.    At all times during the Term of this Agreement while it is
sponsoring the registration of any Registered Name within the usTLD System, Registrar shall have in effect an electronic or paper registration agreement with each Registrant (a "Registration
Agreement"). Registrar shall, if so requested by usTLD Administrator from time to time, promptly furnish to usTLD Administrator a copy of each general form of Registration Agreement it uses with
Registrants. Registrar shall include in each Registration Agreement those terms specifically required by this Agreement and the Accreditation Agreement and other terms that are consistent with
Registrar's obligations to usTLD Administrator under this Agreement and the Accreditation Agreement and that will ensure ongoing compliance with both such agreements. Without limiting the foregoing,
the Registration Agreement shall require each Registrant to certify, under penalty of perjury, that it has, and shall continue to have, a bona fide U.S. Nexus in order to qualify to register and
maintain its use of a Registered Name.

	3.4
	Indemnification Required of Registrants.    In its Registration Agreement with each Registrant, Registrar shall require such
Registrant to indemnify, defend and hold harmless usTLD Administrator, and its directors, officers, employees, representatives, agents, affiliates, and stockholders from and against any and all
claims, suits, actions, other proceedings, damages, liabilities, costs and expenses of any kind, including without limitation reasonable legal fees and expenses, arising out of or relating to the
Registrant's (i) domain name registration and (ii) use of any Registered Name. Each Registration Agreement shall further require that this indemnification obligation survive the
termination or expiration of the Registration Agreement.

	3.5
	Data Submission Requirements.    As part of its registration and sponsorship of Registered Names in the usTLD, Registrar
shall submit complete data (and update such data) as required by technical specifications of the usTLD System that are made available to Registrar from time to time and the Accreditation Agreement.
Registrar hereby grants usTLD Administrator 

H-5

 

a
non-exclusive, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required in
usTLD Administrator's operation of the usTLD. 

	3.6
	Security.    Registrar agrees to develop and employ in its domain name registration business all necessary technology and
restrictions to ensure that its connection to the usTLD System is secure. All data exchanged between Registrar's system and the usTLD System shall be protected to avoid unintended disclosure of
information. Registrar agrees to employ the necessary measures to prevent its access to the usTLD System granted hereunder from being used to (1) allow, enable, or otherwise support, the
transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than its own existing customers; or (2) enable high
volume, automated, electronic processes that send queries or data to the systems of usTLD Administrator, any other registry operated under an agreement with usTLD Administrator, or any other
registrar, except as reasonably necessary to register domain names or modify existing registrations in compliance with this Agreement. In addition, usTLD Administrator may from time to time require
other reasonable security provisions to ensure that the usTLD System is secure, and Registrar will comply with all such provisions.

	3.7
	Resolution of Technical Problems.    Registrar agrees to employ necessary employees, contractors, or agents with sufficient
technical training and experience to respond to and fix all technical problems concerning the use of the XRP and the APIs in conjunction with Registrar's systems. Registrar agrees that in the event of
significant degradation of the usTLD System or other emergency, usTLD Administrator may, in its sole discretion, temporarily suspend access to the usTLD System. Such temporary suspensions shall be
applied in a non-arbitrary manner and shall apply fairly to any registrar similarly situated, including any affiliates of usTLD Administrator that serve as registrars.

	3.8
	Time of Entry of Domain Name Registration.    Registrar agrees that in the event of any dispute concerning the time of the
entry of a domain name registration into the usTLD Database, the time shown in the usTLD System records shall control.

	3.9
	Change in Registrar Sponsoring Domain Name.    Registrar may assume sponsorship of a Registrant's existing domain name
registration from another registrar by following the policy set forth in Exhibit D. When transferring sponsorship of a Registered Name to or from
another registrar, Registrar shall comply with the requirements of Exhibit D.

	3.10
	Compliance with Terms and Conditions.    Registrar shall comply with, and shall include in each Registration Agreement all
of the following:

	3.10.1
	Any
NIST standards, policies, procedures, and practices for which usTLD Administrator has monitoring responsibility in accordance with the usTLD Agreement or other arrangement with
NIST and/or ICANN, including without limitation ICANN policies pertaining to open county code TLDs (unless otherwise provided in the usTLD Agreement); and

	3.10.2
	Operational
standards, policies, procedures, and practices for the usTLD as set forth in the usTLD Agreement and as established from time to time by usTLD Administrator and/or the
Council in a non-arbitrary manner and applicable to all registrars generally, and consistent with NIST's standards, policies, procedures, and practices. Among usTLD Administrator's current
operational standards, policies, procedures, and practices are those set forth in Exhibit E. Additional or revised usTLD Administrator operational standards, policies, procedures, and practices
for the usTLD shall be effective upon thirty (30) days notice by usTLD Administrator to Registrar. 

H-6

 

	3.11
	Restrictions on Registered Names; Compliance with Law.    In addition to complying with NIST, policies, procedures, and
practices limiting domain names that may be registered, Registrar agrees to comply with applicable statutes and regulations limiting the domain names that may be registered. Further, Registrar shall
abide by applicable laws and governmental regulations.

	3.12
	Resellers.    Registrar may, in its discretion from time to time, designate one or more resellers that will be permitted to
provide Registrar Services consistent with those permitted of Registrar under this Agreement. Registrar shall enter into a written agreement with each of its re-sellers (a "Reseller
Agreement"), which will ensure compliance with this Agreement and the Accreditation Agreement and include sufficient terms and conditions to obligate each re-seller to abide by all terms
and conditions and all Registrar obligations set forth in this Agreement (provided that re-sellers will not be entitled to appoint their own
resellers) and the Accreditation Agreement. Registrar shall be primarily liable for all acts or omissions of its resellers, and usTLD Administrator's obligations under this Agreement and the
Accreditation Agreement shall not be increased due to Registrar's appointment of re-sellers. Promptly following the end of each calendar year during the Term of this Agreement (but in no
event later than January 30), Registrar shall provide to usTLD Administrator a complete written list of all of its current resellers. Further, in its Reseller Agreement with each
re-seller, Registrar shall require such reseller to indemnify, defend and hold harmless usTLD Administrator, and its directors, officers, employees, representatives, agents, affiliates,
and stockholders from and against any and all claims, damages, liabilities, costs and expenses of any kind, including without limitation reasonable legal fees and expenses, arising out of or relating
to any activities of such sub-registrar. Each such Reseller Agreement shall further require that this indemnification obligation survive the termination or expiration of that agreement. 

4.     FEES  

	4.1
	Amount
of usTLD Administrator Fees.    Registrar agrees to pay usTLD Administrator the fees set forth in Exhibit F for
initial and renewal registrations and other services provided by usTLD Administrator to Registrar (collectively, "Fees"). usTLD Administrator reserves the right to revise the Fees prospectively upon
thirty (30) days notice to Registrar, provided that such adjustments are consistent with the usTLD Agreement.

	4.2
	Payment
of usTLD Administrator Fees.    In advance of incurring Fees, Registrar shall establish a letter of credit, deposit account, or other credit facility accepted by
usTLD Administrator, which acceptance will not be unreasonably withheld so long as payment is assured. All Fees are due immediately upon receipt of applications for initial and renewal registrations,
or upon provision of other services provided by usTLD Administrator to Registrar. Payment shall be made via debit or draw down of the deposit account, letter of credit or other credit facility. usTLD
Administrator shall provide monthly invoices to the Registrar.

	4.3
	Non-Payment
of Fees.    In the event Registrar has insufficient funds deposited or available through the letter of credit or credit facility with usTLD
Administrator or otherwise fails to pay Fees when due, usTLD Administrator may do any or all of the following: (a) stop accepting new initial or renewal registrations from Registrar;
(b) delete the domain names associated with any negative balance incurred from the usTLD Database; and (c) pursue any other remedy permitted under this Agreement or at law or in equity. 

H-7

 

5.     CONFIDENTIALITY AND INTELLECTUAL PROPERTY  

	5.1
	Use of Confidential Information.    During the Term of this Agreement, a Disclosing Party may be required (or elect) to
disclose Confidential Information to the Receiving Party. Each party's use and disclosure of the Confidential Information shall be subject to the following terms and conditions:

	5.1.1
	The
Receiving Party shall treat as strictly confidential, and use all reasonable efforts to preserve the secrecy and confidentiality of, all Confidential Information, including
implementing reasonable physical security measures and operating procedures.

	5.1.2
	The
Receiving Party agrees that it will use any Confidential Information solely for the purpose of exercising its rights or performing its obligations under this Agreement and for
no other purposes whatsoever.

	5.1.3
	The
Receiving Party shall make no disclosures whatsoever of any Confidential Information of the Disclosing Party to others; provided, however, that if the Receiving Party is a
corporation, partnership, or other organization, disclosure is permitted to the Receiving Party's officers, employees, contractors and agents who have a demonstrable need to know such Confidential
Information, provided the Receiving Party shall advise such personnel of the confidential nature of the Confidential Information and of the procedures required to maintain the confidentiality thereof,
and shall require them to acknowledge in writing that they have read, understand, and agree to be individually bound by the confidentiality terms of this Agreement.

	5.1.4
	The
Receiving Party shall not modify or remove any confidentiality legends and/or copyright notices appearing on any Confidential Information.

	5.1.5
	The
Receiving Party agrees not to prepare, or claim any rights to, any derivative works based on the Confidential Information.

	5.1.6
	Notwithstanding
the foregoing, this Subsection 5.1 imposes no obligation upon the parties with respect to information that (a) is disclosed to a third party with the
Disclosing Party's prior written approval; or (b) is or has entered the public domain through no fault of the Receiving Party; or (c) is known by the Receiving Party prior to the time of
disclosure (as shown by documentary records to that effect); or (d) is independently developed by the Receiving Party without use of, or reference to, the Confidential Information; or
(e) is made generally available by the Disclosing Party without restriction on disclosure; or (f) Receiving Party receives in good faith from a third party who is not, directly or
indirectly, under an obligation of confidentiality to Disclosing Party with respect to same.

	5.1.7
	In
the event the Receiving Party is required by law, regulation or court order to disclose any Confidential Information, Receiving Party will promptly notify Disclosing Party in
writing prior to making any such disclosure in order to facilitate Disclosing Party seeking a protective order or other appropriate remedy from the proper authority, at the Disclosing Party's expense.
Receiving Party agrees to cooperate with Disclosing Party in seeking such order or other remedy. Receiving Party further agrees that if Disclosing Party is not successful in precluding the requesting
legal body from requiring the disclosure of the Confidential Information, it will furnish only that portion of the Confidential Information which is legally required.

	5.1.8
	The
Receiving Party's duties under this Subsection 5.1 shall expire five (5) years after the expiration or termination of this Agreement, or earlier upon written agreement of
the parties. 

H-8

 

	5.2
	Intellectual Property.

	5.2.1
	Each
party will continue to independently own its intellectual property, including all patents, patent applications, copyrights, trademarks, trade names, service marks,
know-how, trade secrets, data, proprietary processes, software, and all other forms of intellectual property, and nothing in this agreement shall confer any ownership right whatsoever to
one party in the intellectual property of the other party. In addition, usTLD Administrator, or its suppliers and/or licensees, as the case may be,shall own all right, title and interest in and to the
XRP, API's, Registrar Tool Kits, and any software incorporated into the usTLD System, or any component of any of the foregoing, as well as all intellectual property appurtenant thereto.

	5.2.2
	Subject
only to the limited licenses set forth in Subsections 2.3.2, 3.5, and 5.1.2 above, no commercial use rights or any licenses of any kind under or to any patent, patent
application, copyright, trademark, trade name, service mark, know-how, trade secret, data, proprietary process, software or any other intellectual proprietary rights of any kind are
granted by one party to the other party by this Agreement, or by virtue of any disclosure of any Confidential Information to a Receiving Party under this Agreement. 

H-9

   6.     INDEMNITIES AND LIMITATION OF LIABILITY  

	6.1
	Indemnification.    Registrar, at its own expense and within thirty (30) days after presentation of a demand by usTLD
Administrator under this Section, will indemnify, defend and hold harmless usTLD Administrator and its directors, officers, employees, representatives, agents, affiliates, and stockholders (along with
usTLD Administrator, each an "Indemnified Person"), against any claim, suit, action, other proceeding of any kind (a "Claim") brought against that Indemnified Person based on, arising from, or
relating in any way to: (i) any product or service of Registrar; (ii) any agreement, including Registrar's dispute policy, with any Registrant or re-seller; or
(iii) Registrar's domain name registration business, including, but not limited to, Registrar's advertising, domain name application process, systems and other processes, fees charged, billing
practices and customer service, or any other business conducted by Registrar; provided, however, that in any such case: (a) usTLD Administrator or any other Indemnified Person provides
Registrar with reasonable prior notice of any such Claim, and (b) upon Registrar's written request, usTLD Administrator or any other Indemnified Person will provide to Registrar all available
information and assistance reasonably necessary for Registrar to defend such Claim; provided further that Registrar reimburses usTLD Administrator and such other Indemnified Persons for their actual
and reasonable costs incurred in connection with providing such information and assistance. Registrar will not enter into any settlement or compromise of any such indemnifiable Claim with respect to a
particular Indemnified Person without the prior written consent of such Indemnified Person, which consent shall not be unreasonably withheld. Registrar will pay any and all costs, damages,
liabilities, and expenses, including, but not limited to, reasonable attorneys' fees and costs awarded against or otherwise incurred by usTLD Administrator and other Indemnified Persons in connection
with or arising from any such indemnifiable Claim.

	6.2
	Limitation of Liability.    EXCEPT WITH RESPECT TO REGISTRAR'S INDEMNIFICATION OBLIGATIONS SET FORTH IN ELSEWHERE IN THIS
AGREEMENT, IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE, EXEMPLARY OR CONSEQUENTIAL DAMAGES FOR ANY VIOLATIONS OF, OR CAUSES OF ACTION RELATING TO OR
ARISING FROM, THIS AGREEMENT, EVEN IF SUCH PARTY HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.

	6.3
	Performance Credits.    In the event usTLD Administrator fails to meet the performance specifications set forth in
Appendix G of this Agreement, usTLD Administrator shall provide a credit to Registrar in an amount equal to its proportionate share of applicable performance credits set forth in
Exhibit H of this Agreement. Such performance credits shall constitute the sole and exclusive remedy available to Registrar with regard to usTLD Administrator's failure to meet the performance
specifications. 

7.     DISPUTE RESOLUTION  

	7.1
	Dispute Resolution; Governing Law.    Any and all disputes of any nature arising under or in connection with this Agreement,
including requests for specific performance, shall be resolved through binding arbitration conducted as provided in this Section pursuant to the rules of the American Arbitration Association ("AAA").
The arbitration shall be conducted in the English language and shall occur in the District of Columbia, Washington, D.C., USA. There shall be three (3) arbitrators: each party shall choose one
arbitrator, who together will select a third; if the two arbitrators are not able to agree on a third arbitrator within fifteen (15) calendar days of the designation of the second arbitrator,
the AAA shall choose the third. The parties shall bear the costs of the arbitration in equal shares, subject to the right of the arbitrators to reallocate the costs in their award as provided in the
AAA rules. The parties shall bear their 

H-10

 

own
attorneys' fees in connection with the arbitration, and the arbitrators may not reallocate the attorneys' fees in conjunction with their award. The arbitrators shall render their decision within
ninety (90) calendar days of the selection of the third arbitrator. Any litigation brought to enforce an arbitration award shall be brought in a Commonwealth or federal court in the Eastern
District of the Commonwealth of Virginia, USA; however, the parties shall also have the right to enforce a judgment of such a court in any court of competent jurisdiction. For the purpose of aiding
the arbitration and/or preserving the rights of a party during the pendency of an arbitration, each party shall have the right to seek temporary or preliminary injunctive relief from the arbitration
panel or any court of competent jurisdiction located in the Eastern District of the Commonwealth of Virginia, USA, which shall not be a waiver of this arbitration agreement. This Agreement shall be
construed in accordance with and governed by the laws of the Commonwealth of Virginia (without regard to any rules or principles of conflicts of law that might look to any jurisdiction outside
Virginia). 

8.     TERM AND TERMINATION  

	8.1
	Term of the Agreement; Revisions.    The Term of this Agreement shall commence on the Effective Date and, unless earlier
terminated in accordance with the provisions of this Agreement, shall expire on the last expiration of the usTLD Agreement. In the event that revisions to usTLD Administrator's approved form of usTLD
Administrator-Registrar Agreement (such as this one) are approved or adopted by NIST from time to time, Registrar will either execute an amendment substituting the revised agreement in place of this
Agreement or, at its option exercised within thirty (30) days after receiving notice of such amendment, terminate this Agreement immediately by giving written notice to usTLD Administrator. In
the event that usTLD Administrator does not receive such executed amendment or notice of termination from Registrar within such thirty (30) day period, Registrar shall be deemed to have
accepted the provisions of such revised usTLD Administrator-Registrar Agreement, and as such, shall be bound by all the terms and conditions of such revised usTLD Administrator-Registrar Agreement.
usTLD Administrator will use commercially reasonable efforts to post such revised form of usTLD Administrator-Registrar Agreement on its US website at least thirty (30) days prior to its
effective date.

	8.2
	Termination.    This Agreement may be terminated as follows:

	8.2.1
	Termination For Cause.    In the event that either party materially breaches any of its obligations under this Agreement
and such breach is not substantially cured within thirty (30) calendar days after written notice thereof is given by the other party, then the non-breaching party may, by giving
written notice thereof to the other party, terminate this Agreement as of the date specified in such notice of termination.

	8.2.2
	Termination at Option of Registrar.    Registrar may terminate this Agreement at any time by giving usTLD Administrator
thirty (30) days written notice of termination.

	8.2.3
	Termination Upon Loss of Registrar's Accreditation.    This Agreement shall immediately terminate in the event Registrar's
accreditation by usTLD Administrator is terminated or expires without renewal.

	8.2.4
	Termination in the Event of Termination of usTLD Agreement.    This Agreement shall immediately terminate in the event the
usTLD Agreement is terminated or expires without entry of a subsequent usTLD Agreement with NIST and this Agreement is not assigned under Subsection 9.1.1 below.

	8.2.5
	Termination in the Event of Insolvency or Bankruptcy.    This Agreement will automatically and immediately terminate if the
Registrar is adjudged insolvent or bankrupt, or if 

H-11

 

proceedings
are instituted by or against Registrar seeking relief, reorganization or arrangement under any laws relating to insolvency or bankruptcy, or seeking any assignment for the benefit of
creditors, or seeking the appointment of a receiver, liquidator or trustee of Registrar's property or assets or the liquidation, dissolution or winding up of Registrar's business. 

	8.3
	Effect of Termination.    Upon the expiration or termination of this Agreement for any reason:

	8.3.1
	usTLD
Administrator will complete the registration of all domain names processed by Registrar prior to the effective date of such expiration or termination, provided that all
Registrar's payments to usTLD Administrator for Fees are current and timely.

	8.3.2
	Registrar
shall immediately transfer its sponsorship of Registered Names to another registrar in compliance with any procedures established or approved by usTLD Administrator.

	8.3.3
	All
Confidential Information in the possession of the Receiving Party shall be immediately returned to the Disclosing Party.

	8.3.4
	All
Fees and any other amounts owing to usTLD Administrator shall become immediately due and payable.

	8.4
	Survival.    In the event of termination of this Agreement, the following shall survive: (i) Subsections 2.6, 3.5,
5.1, 5.2, 6.1, 6.2, 7.1, 8.3.3, 8.3.4, 8.4, 9.2, 9.3.3, 9.5, 9.6, 9.8, 9.9, 9.10, 9.11 and 9.13 and (ii) the indemnification obligations of (a) Registrants under Subsection 3.4 and
(b) resellers under Subsection 3.12. Neither party shall be liable to the other for damages of any sort resulting solely from terminating this Agreement in accordance with its terms. 

9.     MISCELLANEOUS  

	9.1
	Assignments.

	9.1.1
	Assignment to Successor usTLD Administrator.    In the event the usTLD Agreement is terminated (and such termination is
deemed final under the usTLD Agreement) or expires without entry by usTLD Administrator and NIST of a subsequent registry agreement, usTLD Administrator's rights under this Agreement may be assigned
to a entity with a subsequent registry agreement covering the usTLD upon NIST's giving Registrar written notice within sixty (60) days of the termination or expiration, provided that the
subsequent usTLD Administrator assumes all or substantially all of the duties of usTLD Administrator under this Agreement.

	9.1.2
	Assignment in Connection with Assignment of usTLD Agreement with NIST.    In the event that the usTLD Agreement for the
usTLD is validly assigned, usTLD Administrator's rights under this Agreement shall be automatically assigned to the assignee of the usTLD Agreement, provided that the assignee assumes all or
substantially all of the duties of usTLD Administrator under this Agreement.

	9.1.3
	Other Assignments.    Except as otherwise expressly provided in this Agreement, the provisions of this Agreement shall
inure to the benefit of and be binding upon, the successors and permitted assigns of the parties. Neither party shall assign or transfer its rights or obligations under this Agreement without the
prior written consent of the other party, which shall not be unreasonably withheld; provided, however, that usTLD Administrator shall have the right to assign all its rights and delegate all its
duties under this Agreement to an affiliated organization without such consent. 

H-12

 

	9.2
	Notices.    Any notice or other communication required or permitted to be delivered to any party under this Agreement shall
be in writing and shall be deemed properly delivered, given and received when delivered by hand, by registered mail (return receipt requested), by courier or express delivery service, by
e-mail (against of receipt of confirmation of delivery) or by telecopier (against receipt of answerback confirming delivery) during business hours to the address or telecopier number, or
e-mail address set forth beneath the name of such party below or when delivery as described above is refused by the intended recipient, unless such party has given a notice of a change of
address in writing pursuant to the foregoing. Notwithstanding the foregoing, notice shall be deemed properly given from usTLD Administrator to Registrar at such time as usTLD Administrator posts any
notice, update, modification or other information on its U.S. website, so long as such notice, update, modification or other information is intended for all registrars generally (e.g.,
NIST-mandated revisions to the form usTLD Administrator-Registrar Agreement). 

If
to Registrar: 

	 

	 

	 

	 

	 

	 

with
copy to: 

	 

	 

	 

	 

	 

	 

If
to usTLD Administrator: 

	NeuStar, Inc.

1120 Vermont Avenue, N.W.

Suite 400

Washington, D.C. 20005

Attn: VP of Policy and Industry Relations

phone:

fax:

with
a copy to: 

	NeuStar, Inc.

1120 Vermont Avenue, N.W.

Suite 400

Washington, D.C. 20005

Attn: General Counsel

phone:

fax:

H-13

 

	9.3
	Representations and Warranties.

	9.3.1
	Registrar.    Registrar represents and warrants that: (1) it is an organization (e.g., corporation, partnership,
limited liability company, government agency) duly formed, validly existing and in good standing under the laws of
the                        , (2) it has all requisite power and authority to execute,
deliver and perform its obligations under this Agreement (3) it is, and during the Term of this Agreement will continue to be, accredited by usTLD Administrator, (4) the execution,
performance and delivery of this Agreement has been duly authorized by Registrar, (5) no further approval, authorization or consent of any governmental or regulatory authority is required to be
obtained or made by Registrar in order for it to enter into and perform all its obligations under this Agreement.

	9.3.2
	usTLD Administrator.    usTLD Administrator represents and warrants that: (1) it is a corporation duly incorporated,
validly existing and in good standing under the laws of the State of Delaware, (2) it has all requisite corporate power and authority to execute, deliver and perform its obligations under this
Agreement, (3) the execution, performance and delivery of this Agreement has been duly authorized by usTLD Administrator, and (4) no further approval, authorization or consent of any
governmental or regulatory authority is required to be obtained or made by usTLD Administrator in order for it to enter into and perform all its obligations under this Agreement.

	9.3.3
	Disclaimer of Warranties.    THE XRP, APIs, REGISTRAR TOOLKIT, usTLD SYSTEM AND ANY COMPONENT THEREOF ARE PROVIDED
"AS-IS" AND WITHOUT ANY WARRANTY OF ANY KIND. usTLD OPERATOR EXPRESSLY DISCLAIMS ALL WARRANTIES AND/OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
AND CONDITIONS OF MERCHANTABILITY OR SATISFACTORY QUALITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. usTLD OPERATOR DOES NOT WARRANT THAT THE XRP, APIs, REGISTRAR
TOOLKIT, usTLD SYSTEM OR ANY COMPONENT THEREOF WILL MEET REGISTRAR'S REQUIREMENTS, OR THAT THE OPERATION OF XRP, APIs, REGISTRAR TOOLKITS, THE usTLD SYSTEM OR ANY COMPONENT THEREOF WILL BE
UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE XRP, APIs, REGISTRAR TOOLKIT, usTLD SYSTEM OR ANY COMPONENT THEREOF WILL BE CORRECTED. FURTHERMORE, usTLD OPERATOR DOES NOT WARRANT NOR
MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE XRP, APIs, REGISTRAR TOOLKITS, usTLD SYSTEM OR ANY COMPONENT THEREOF OR RELATED DOCUMENTATION IN TERMS OF THEIR CORRECTNESS, ACCURACY,
RELIABILITY, OR OTHERWISE. SHOULD THE XRP, APIs, REGISTRAR TOOLKIT, THE usTLD SYSTEM OR ANY COMPONENT THEREOF PROVE DEFECTIVE, REGISTRAR ASSUMES THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION OF REGISTRAR'S OWN SYSTEMS AND SOFTWARE. 

In
the event of any conflict in this Agreement between this Subsection 9.3.3 and any other provision, this Subsection 9.3.3 will govern and control. 

	9.4
	Insurance.    During the Term of this Agreement (including any renewal terms), Registrar shall have in place US$500,000 in
comprehensive legal liability insurance from a reputable insurance provider with an A.M. Best rating of "A" or better. Such insurance shall be used to indemnify and hold harmless usTLD
Administrator and its employees, directors, officers, 

H-14

 

representatives,
agents, affiliates, and stokholders from all costs and damages (including without limitation reasonable attorneys' fees) which it may suffer by reason of Registrar's failure to
indemnify usTLD Administrator as provided above; provided, however, that Registrar's indemnity obligations under this Agreement shall not deemed to be limited by the amount of such insurance.
Registrar shall provide a copy of the insurance policy to usTLD Administrator upon usTLD Administrator's request and shall name usTLD Administrator and the other Indemnified Persons as additional
insureds under that policy. 

	9.5
	Third-Party Beneficiaries.    The parties expressly agree that NIST is an intended third-party beneficiary of this Agreement.
Otherwise, this Agreement shall not be construed to create any obligation by either party to any non-party to this Agreement, including any Registrant or re-seller. Registrar
acknowledges that nothing in this Agreement shall confer upon Registrar or any person or entity the status of an intended third-party beneficiary of the usTLD Agreement.

	9.6
	Relationship of the Parties.    Nothing in this Agreement shall be construed as creating an employer-employee or agency
relationship, a partnership or a joint venture between the parties.

	9.7
	Force Majeure.    Except for the non-payment of Fees, neither party shall be liable to the other for any loss or
damage resulting from any cause beyond its reasonable control (a "Force Majeure Event") including, but not limited to, insurrection or civil disorder, war or military operations, national or local
emergency, acts or omissions of government or other competent authority, compliance with any statutory obligation or executive order, industrial disputes of any kind (whether or not involving either
party's employees), fire, lightning, explosion, flood, subsidence, weather of exceptional severity, equipment or facilities shortages which are being experienced by providers of telecommunications
services generally, or other similar force beyond such Party's reasonable control, and acts or omissions of persons for whom neither party is responsible. Upon occurrence of a Force Majeure Event and
to the extent such occurrence interferes with either party's performance of this Agreement, such party shall be excused from performance of its obligations (other than payment obligations) during the
first six (6) months of such interference, provided that such party uses commercially reasonable efforts to avoid or remove such causes of nonperformance as soon as possible.

	9.8
	Amendments.    Except as otherwise provided herein, no amendment, supplement, or modification of this Agreement or any
provision hereof shall be binding unless executed in writing by authorized signatories of both parties.

	9.9
	Waivers.    No failure on the part of either party to exercise any power, right, privilege or remedy under this Agreement,
and no delay on the part of either party in exercising any power, right, privilege or remedy under this Agreement, shall operate as a waiver of such power, right, privilege or remedy; and no single or
partial exercise or waiver of any such power, right, privilege or remedy shall preclude any other or further exercise thereof or of any other power, right, privilege or remedy. Neither party shall be
deemed to have waived any claim arising out of this Agreement, or any power, right, privilege or remedy under this Agreement, unless the waiver of such claim, power, right, privilege or remedy is
expressly set forth in a written instrument duly executed and delivered on behalf of such party; and any such waiver shall not be applicable or have any effect except in the specific instance in which
it is given.

	9.10
	Attorneys' Fees.    Except as otherwise may be provided in Subsection 7.1 above, if any legal action or other legal
proceeding (including arbitration) relating to the performance under this Agreement or the enforcement of any provision of this Agreement is brought against a party 

H-15

 

hereto,
the prevailing party shall be entitled to recover reasonable attorneys' fees, costs and disbursements (in addition to any other relief to which the prevailing party may be entitled). 

	9.11
	Construction; Severability.    The parties agree that any rule of construction to the effect that ambiguities are to be
resolve against the drafting party shall not be applied in the construction or interpretation of this Agreement. Unless otherwise stated in this Agreement, references to a number of days shall mean
consecutive calendar days. In the event that any clause or portion thereof in this Agreement is for any reason held to be invalid, illegal or unenforceable, the same shall not affect any other portion
of this Agreement, as it is the intent of the parties that this Agreement shall be construed in such fashion as to maintain its existence, validity and enforceability to the greatest extent possible.
In any such event, this Agreement shall be construed as if such clause or portion thereof had never been contained in this Agreement, and there shall be deemed substituted therefore such provision as
will most nearly carry out the intent of the parties as expressed in this Agreement to the fullest extent permitted by applicable law.

	9.12
	Further Assurances.    Each party hereto shall execute and/or cause to be delivered to the other party hereto such
instruments and other documents, and shall take such other actions, as such other party may reasonable request for the purpose of carrying out or evidencing any of the transactions contemplated by
this Agreement.

	9.13
	Entire Agreement.    This Agreement (including its exhibits, which form a part of it) constitutes the entire
agreement between the parties concerning the subject matter of this Agreement and supersedes any prior agreements, representations, statements, negotiations, understandings, proposals or undertakings,
oral or written, with respect to the subject matter expressly set forth herein. In the event of any conflict between the terms of this usTLD Administrator-Registrar Agreement and the Accreditation
Agreement, the usTLD Administrator-Registrar Agreement shall govern and control.

	9.14
	Counterparts.    This Agreement may be executed in one or more counterparts, each of which shall be deemed an original, but
all of which together shall constitute one and the same instrument. 

H-16

 

        IN
WITNESS WHEREOF, the parties hereto have executed this Agreement as of the date first set forth above. 

	NeuStar, Inc.	 	[Name of Registrar]
	

By:	
 	

 
	
 	

By:	
 	

 

	Name:	 	 
	 	Name:	 	 

	Title:	 	 
	 	Title:	 	 

H-17

  

 
 

Exhibit A    
    
    REGISTRAR TOOL KIT    
    

        usTLD Administrator-Registrar Software Development Kit includes, but is not limited to the following: 

	•
	Reference
client implementations:

	•
	Java

	•
	C++

	•
	PERL

	•
	Interface
definition: XML Schema

	•
	usTLD
Administrator Operational Profile (our extensions)

	•
	Authentication
and Encryption guidelines

	•
	XRP
"feature freeze" drafts

	•
	XRP
test plan and coverage matrix

	•
	Java,
C++ and PERL API documentation 

H-18

  

 
 

Exhibit B    
    
    ENGINEERING AND CUSTOMER SERVICE SUPPORT    
    

        During the Term of this Agreement, usTLD Administrator will provide reasonable telephone and electronic customer support to Registrar, not Registrants or
prospective customers of Registrar, for non-technical issues solely relating to the usTLD System and its operation. usTLD Administrator will provide Registrar with a telephone number and
e-mail address for such support during implementation of the XRP, APIs and any reference client software included in the Registrar Tool Kit. While e-mail and FAQs are the
primary method of help, usTLD Administrator will provide support on a 7-day/24-hour basis. usTLD Administrator will provide a web-based customer service capability
in the future and such web-based support will become the primary method of customer service support to Registrar at such time. 

        The
usTLD Administrator provides a clear, concise and efficient deliberation of customer support responsibilities. Registrars provide support to registrants (i.e., Registrants) and
registries (like usTLD Administrator) provide support for registrars. This structure allows the usTLD Administrator to focus its support on the highly technical and administratively complex issues
that arise between the usTLD Administrator and the Registrar and to focus on the system operations supporting the usTLD. 

Technical Help Systems  

        usTLD Administrator will provide its registrars with the following types of technical support: 

	•
	Web-based
self-help services, including:

	•
	Knowledge
bases

	•
	Frequently
asked questions

	•
	White
papers

	•
	Downloads
of XRP client software

	•
	Support
for email messaging

	•
	Telephone
support from a central Help Desk

	•
	Fee-based
consulting services. 

Web Portal  

        usTLD Administrator will implement a secure Web-based multimedia portal to help support registrar operations. To obtain access to these
Web-based services, a registrar must register its registrants usTLD Administrator, and must have implemented our security features, including SSL encryption, log in with user ID and
password, and digital certificates for authentication. The home page of the web portal will include a notice to registrars of planned outages for database maintenance or installation of software
upgrades. usTLD Administrator will use commercially reasonable effort to post this notification at least thirty (30) days prior to the event in addition to active notification including phone
calls and email. usTLD Administrator will also record outage notifications in the help desk database to facilitate compliance with the performance specifications
(Exhibit B-2). Finally, seven (7) days and again two (2) days prior to the scheduled event, usTLD Administrator will
use both an email and a Web-based notification to remind registrars of the outage. 

        Non-affiliated
registrars and the general Internet community may obtain generic information from usTLD Administrator's public website, which will describe the TLD service
offerings and list of registrars, including Registrar, providing domain-name services. 

H-19

 

Central Help Desk  

        In addition to implementing the website, usTLD Administrator will provide telephone support to registrars through a central Help Desk. Access to the help desk
telephone support is through an automatic call distributor that routes each call to the next available customer support specialist. usTLD Administrator will authenticate callers by using caller ID and
by requesting a pre-established pass phrase that is different for each registrar. Requests for assistance may also come to the Help Desk via email, either directly or via the secure
website. The Help Desk's three tiers of support are: 

Tier-1
Support.    Telephone support to registrars who normally are calling for help with customer domain-name problems and such other issues such as XRP
implementation or billing and collection. Problems that can't be resolved at Tier 1 are escalated to Tier 2. 

Tier-2
Support.    Support provided by members of the technical support team, who are functional experts in all aspects of domain-name registration. In addition to
resolving escalated Tier 1 problems with XRP implementation and billing and collection, Tier 2 staff provides technical support in system tuning and workload processing. 

Tier
3 Support.    Complex problem resolution provided by on-site maintenance technicians, third party systems and software experts, and vendors, depending on the nature of the
problem. 

        In
turn, the Help Desk uses an automated software package to collect call statistics and record service requests and trouble tickets in a help desk database. The help desk database
documents the status of requests and tickets. Each customer-support and technical support specialist uses this problem management process to respond to trouble tickets with a troubleshooting,
diagnosis, and resolution procedure and a root-cause analysis. 

Escalation Policy  

        usTLD Administrator's escalation policy defines procedures and timelines for elevating problems either to functional experts or to management for resolution if
they are not resolved within the escalation-policy time limits. The following table is an overview of the escalation policy. 

	Level
 
	 	Description
	 	Escalation Policy
	 	Notification

	I	 	Catastrophic outage affecting overall registry operations	 	Data-center manager escalates to usTLD Administrator management and Disaster-Recovery Team if not resolved in 15 minutes	 	Web portal and e-mail notifications to all Registrars within 15 minutes; updates every 30 minutes
	II	 	Systems outage affecting one or two registrar sessions but not the entire system	 	Systems engineer escalates to data-center manager if not resolved in one hour	 	Web-portal notification to all registrars; hourly updates
	III	 	Technical questions	 	Help Desk customer-support specialist escalates to the systems engineer if not resolved in two hours	 	Hourly updates to registrar via e-mail
	IV	 	Basic questions	 	Help Desk customer-support specialist escalates to the systems engineer if not resolved within four hours	 	Hourly updates to registrar via e-mail

H-20

 

Staffing  

        Initially, usTLD Administrator will staff its Help Desk with a complement of customer service specialists. usTLD Administrator will add staff as necessary to
respond to incoming requests within the performance specification guidelines. Customer-service specialists will obtain assistance from usTLD Administrator's technical staff for any problems that
cannot be resolved in one (1) phone call. 

Test and Evaluation Facility  

        usTLD Administrator will establish an operational test-and-evaluation facility that will be available for Registrars to test their client
XRP system. usTLD Administrator's technical-support team, which consists of functional experts in the processes and technologies for domain-name registration, will support the registrars'
testing. 

        Once
each new registrar is satisfied that its system is compatible with the usTLD System, it will schedule a formal acceptance test that will be monitored by usTLD Administrator's
system engineer. After a registrar has passed the acceptance test, usTLD Administrator will issue its user id, passwords, and digital certificates, and the registrar can then begin operations. 

Customer Satisfaction Survey  

        To determine the satisfaction of registrars with usTLD Services, usTLD Administrator will implement a Web-based customer-satisfaction survey that will
consist of a set of survey questions with responses ranging from one to five on the Likert Scale. usTLD Administrator will tabulate the results and plans to publish them on the website periodically. 

        To
further verify the quality of usTLD Administrator's customer services, usTLD Administrator anticipates commissioning a bi-annual customer-satisfaction survey by an
independent third party. 

H-21

  

 
 

Exhibit C    
    
    ACCREDITATION AGREEMENT    
    

Initial Working Draft Dated July 27, 2001  

 
  Registrar Accreditation Agreement    
    

        This REGISTRAR ACCREDITATION AGREEMENT ("Accreditation Agreement") is by and between NeuStar, Inc., a Delaware corporation, and
[Registrar Name], a [Organization type and jurisdiction]
("Registrar"), and shall be deemed made on [DATE], at Washington, D.C., USA. 

	1.
	DEFINITIONS.    For purposes of this Accreditation Agreement, the following definitions shall apply:

	1.1
	"Accredit"
means to identify and set minimum standards for the performance of registration functions, to recognize persons or entities meeting those standards, and to enter into an
accreditation agreement that sets forth the rules and procedures applicable to the provision of Registrar Services.

	1.2
	The
"Effective Date" is                        .

	1.3
	The
"Expiration Date" is                        .

	1.4
	"NeuStar"
or "Registry" means NeuStar, Inc. and its successors and assigns.

	1.5
	"Registered
Name" means domain name within the usTLD.

	1.6
	"Registrant"
means the holder of a Registered Name.

	1.7
	The
word "Registrar," when appearing with an initial capital letter, refers to [Registrar Name], a party to
this Accreditation Agreement.

	1.8
	The
word "registrar," when appearing without an initial capital letter, refers to a person or entity that contracts with a Registrant and with NeuStar and collects registration data
about the Registrant and submits registration information for entry in the Registry Database and is party to an accreditation agreement with NeuStar.

	1.9
	"Registrar
Services" means services provided by a registrar in connection with the usTLD, and includes contracting with Registrant, collecting registration data about the Registrant,
and submitting registration information for entry in the Registry Database.

	1.10
	"Registry
Database" means a database comprised of data about one or more domain names within usTLD that is used to generate either DNS resource records that are published
authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names.

	1.11
	"Registry
System" means the registry system operated by Registry for Registered Names in the usTLD.

	1.12
	"Term
of this Accreditation Agreement" begins on the Effective Date and continues to the earlier of (a) the Expiration Date, or (b) termination of this Accreditation
Agreement.

	1.13
	"TLD
Zone-File Data" means all data contained in a DNS zone file for the registry, or for any subdomain for which Registry Services are provided and that contains
Registered Names, as provided to nameservers on the Internet. This does not include usTLD domain names hosted by a delegated manager within the usTLD. 

H-22

 

2.     NeuStar OBLIGATIONS.  

	2.1
	Accreditation.    During the Term of this Accreditation Agreement, Registrar is hereby accredited by NeuStar to act as a
registrar (including to insert and renew registration of Registered Names in the Registry Database) for the usTLD.

	2.2
	Registrar Use of NeuStar Name and Website.    NeuStar hereby grants to Registrar a non-exclusive, worldwide,
royalty-free license during the Term of this Accreditation Agreement (a) to state that it is accredited by NeuStar as a registrar for the usTLD and (b) to link to pages and
documents within the NeuStar web site. No other use of NeuStar's name or website is licensed hereby. This license may not be assigned or sublicensed by Registrar.

	2.3
	General Obligations of NeuStar.    With respect to all matters that impact the rights, obligations, or role of Registrar,
NeuStar shall during the Term of this Accreditation Agreement:

	2.3.1
	not
apply standards, policies, procedures or practices arbitrarily, unjustifiably, or inequitably and not single out Registrar for disparate treatment unless justified by
substantial and reasonable cause; and

	2.3.2
	ensure,
through its reconsideration and independent review policies, adequate appeal procedures for Registrar, to the extent it is adversely affected by NeuStar standards, policies,
procedures or practices. 

3.     REGISTRAR OBLIGATIONS.  

	3.1
	Obligations to Provide Registrar Services.    During the Term of this Accreditation Agreement, Registrar agrees that it will
operate as a registrar for the usTLD in accordance with this Accreditation Agreement and the Registry-Registrar Agreement.

	3.2
	Submission of Registered Name Holder Data to Registry.    During the Term of this Accreditation Agreement:

	3.2.1
	As
part of its registration of Registered Names in the usTLD, Registrar shall submit to, or shall place in the Registry Database operated by, NeuStar, as the Registry for the usTLD,
the following data elements:

	3.2.1.1
	The
name of the Registered Name being registered;

	3.2.1.2
	The
IP addresses of the primary nameserver and secondary nameserver(s) for the Registered Name;

	3.2.1.3
	The
corresponding names of those nameservers;

	3.2.1.4
	Unless
automatically generated by the Registry System, the identity of the Registrar;

	3.2.1.5
	Unless
automatically generated by the Registry System, the expiration date of the registration; and

	3.2.1.6
	Any
other data NeuStar, as Registry, requires be submitted to it.

	3.2.2
	Within
five (5) business days after receiving any updates from the Registered Name Holder to the data elements listed in Subsections 3.2.1.2, 3.1.2.3, and 3.2.1.6 for any
Registered Name Registrar sponsors, Registrar shall submit the updated data elements to, or shall place those elements in the Registry Database operated by NeuStar, as Registry.

	3.2.3
	In
order to allow reconstitution of the Registry Database in the event of an otherwise unrecoverable technical failure or a change in the designated NeuStar, as Registry, within ten
(10) days of any such request by NeuStar, Registrar shall submit an electronic 

H-23

 

database
containing the data elements listed in Subsections 3.2.1.1 through 3.2.1.6 for all active records in the registry sponsored by Registrar, in a format specified by NeuStar. 

	3.3
	Public Access to Data on Registered Names.    During the Term of this Accreditation Agreement:

	3.3.1
	At
its expense, Registrar shall provide an interface to the usTLD Whois. Until NeuStar otherwise specifies by means of a NeuStar adopted specification or policy, the usTLD Whois
shall consist of the following elements:

	3.3.1.1
	The
name of the Registered Name;

	3.3.1.2
	The
names of the primary nameserver and secondary nameserver(s) for the Registered Name;

	3.3.1.3
	The
identity of Registrar (which may be provided through Registrar's website);

	3.3.1.4
	Registrar
ID

	3.3.1.5
	The
original creation date of the registration;

	3.3.1.6
	The
expiration date of the registration;

	3.3.1.7
	The
name and postal address of the Registrant;

	3.3.1.8
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the Registered Name; and

	3.3.1.9
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the Registered Name.

	3.3.2
	Upon
receiving any updates to the data elements listed in Subsections 3.3.1.2, 3.3.1.3, and 3.3.1.5 through 3.3.1.8 from the Registrant, Registrar shall promptly update its database
and provide such updates to the Registry.

	3.4
	Retention of Registrant and Registration Data.

	3.4.1
	During
the Term of this Accreditation Agreement, Registrar shall maintain its own electronic database, as updated from time to time, containing data for each active Registered Name
sponsored by it within the usTLD. The data for each such registration shall include the elements listed in Subsections 3.3.1.1 through 3.3.1.8; the name and (where available) postal address,
e-mail address, voice telephone number, and fax number of the billing contact; and any other Registry Data that Registrar has submitted to the Registry or placed in the Registry Database
under Subsection 3.2.

	3.4.2
	During
the Term of this Accreditation Agreement and for three (3) years thereafter, Registrar (itself or by its agent(s)) shall maintain the following records relating to its
dealings with NeuStar, as Registry, and Registrant:

	3.4.2.1
	In
electronic form, the submission date and time, and the content, of all registration data (including updates) submitted in electronic form to NeuStar, as Registry;

	3.4.2.2
	In
electronic, paper, or microfilm form, all written communications constituting registration applications, confirmations,
modifications, or terminations and related correspondence with Registrant, including registration contracts; and

	3.4.2.3
	In
electronic form, records of the accounts of all Registrant with Registrar, including dates and amounts of all payments and refunds. 

H-24

 

	3.4.3
	During
the Term of this Accreditation Agreement and for three (3) years thereafter, Registrar shall make these records available for inspection and copying by NeuStar upon
reasonable notice. NeuStar shall not disclose the content of such records except as expressly permitted by a NeuStar specification or policy or as otherwise required by law.

	3.5
	Rights in Data.    Registrar disclaims all rights to exclusive ownership or use of the data elements listed in Subsections
3.2.1.1 through 3.2.1.3 for all Registered Names submitted by Registrar to the Registry Database for, or sponsored by Registrar in, the usTLD. Registrar does not disclaim rights in the data elements
listed in Subsections 3.2.1.4 through 3.2.1.6 and Subsections 3.3.1.3 through 3.3.1.8 concerning active Registered Names sponsored by it in the usTLD, and agrees to grant non-exclusive,
irrevocable, royalty-free licenses to make use of and disclose the data elements listed in Subsections 3.2.1.4 through 3.2.1.6 and 3.3.1.3 through 3.3.1.8 for the purpose of providing a
service or services (such as a Whois service under Subsection 3.3.4) providing interactive, query-based public access. Upon a change in sponsorship from Registrar of any Registered Name in the usTLD,
Registrar acknowledges that the registrar gaining sponsorship shall have the rights of an owner to the data elements listed in Subsections 3.2.1.4 through 3.2.1.6 and 3.3.1.3 through 3.3.1.8
concerning that Registered Name, with Registrar also retaining the rights of an owner in that data. Nothing in this Subsection prohibits Registrar from (1) restricting bulk public access to
data elements in a manner consistent with this Accreditation Agreement and any NeuStar specifications or policies and as required by law or (2) transferring rights it claims in data elements
subject to the provisions of this Subsection.

	3.6
	Data Escrow.    During the Term of this Accreditation Agreement, on a schedule, under the terms, and in the format specified
by NeuStar, Registrar shall submit an electronic copy of the database described in Subsection 3.4.1 to NeuStar or, at Registrar's election and at its expense, to a reputable escrow agent mutually
approved by Registrar and NeuStar, such approval also not to be unreasonably withheld by either party. The data shall be held under an agreement among Registrar, NeuStar, and the escrow agent (if any)
providing that (1) the data shall be received and held in escrow, with no use other than verification that the deposited data is complete, consistent, and in proper format, until released to
NeuStar; (2) the data shall be released from escrow upon expiration without renewal or termination of this Accreditation Agreement; and (3) NeuStar's rights under the escrow agreement
shall be assigned with any assignment of this Accreditation Agreement. The escrow shall provide that in the event the escrow is released under this Subsection, NeuStar (or its assignee) shall have a
non-exclusive, irrevocable, royalty-free license to exercise (only for transitional purposes) or have exercised all rights necessary to provide Registrar Services.

	3.7
	Business Dealings, Including with Registrant.

	3.7.1
	In
the event NeuStar adopts a specification or policy, supported by a consensus of NeuStar-Accredited registrars, establishing or approving a code of conduct for NeuStar-Accredited
registrars, Registrar shall abide by that code.

	3.7.2
	Registrar
shall abide by applicable laws and governmental regulations.

	3.7.3
	Registrar
shall not represent to any actual or potential Registrant that Registrar enjoys access to the Registry System that is superior to that of any other Accredited registrar.

	3.7.4
	Registrar
shall not activate any Registered Name unless and until it is satisfied that it has received a reasonable assurance of payment of its registration fee. For this purpose, a
charge to a credit card, general commercial terms extended to creditworthy customers, or other mechanism providing a similar level of assurance of payment shall be sufficient, 

H-25

 

provided
that the obligation to pay becomes final and non-revocable by the Registrant upon activation of the registration. 

	3.7.5
	Registrar
shall register Registered Names to Registrant only for fixed periods. At the conclusion of the registration period, failure by or on behalf of the Registrant to pay a
renewal fee within the time specified in a second notice or reminder shall, in the absence of extenuating circumstances, result in cancellation of the registration. In the event that NeuStar adopts a
specification or policy concerning procedures for handling expiration of registrations, Registrar shall abide by that specification or policy.

	3.7.6
	Registrar
shall not insert or renew any Registered Name in a manner contrary to a NeuStar policy stating a list or specification of excluded Registered Names that is in effect at
the time of insertion or renewal.

	3.7.7
	Registrar
shall require all Registrant to enter into an electronic or paper registration agreement with Registrar including at least the following provisions:

	3.7.7.1
	The
Registrant shall provide to Registrar accurate and reliable contact details and promptly correct and update them during the term of the Registered Name registration,
including: the full name, postal address, e-mail address, voice telephone number, and fax number if available of the Registrant; name of authorized person for contact purposes in the case
of an Registrant that is an organization, association, or corporation; and the data elements listed in Subsections 3.3.1.2, 3.3.1.7 and 3.3.1.8.

	3.7.7.2
	A
Registrant's willful or grossly negligent provision of inaccurate or unreliable information, its willful or grossly negligent failure promptly to update information provided to
Registrar shall constitute a material breach of the Registrant's Registration Agreement with the registrar and be a basis for cancellation of the Registered Name registration.

	3.7.7.3
	Enforcement of Accurate Whois Data

	3.7.7.3.1
	Registrar
shall accept written complaints from third parties regarding false and/or inaccurate Whois data of Registrants.

	3.7.7.3.2
	No
later than thirty (30) days after receipt of a written complaint, the Registrar shall conduct an initial investigation into the veracity and accuracy of the contact
details. If the Registrar determines that the information is false, inaccurate or not up to date, Registrar shall issue a letter to the Registrant via e-mail, and regular first class mail,
stating that the information contained in the Registrant's Whois record may be false, inaccurate or not up to date.

	3.7.7.3.3
	The
Registrant shall be required to update its contact information no later than thirty (30) calendar days of the date of such notice. If, within thirty (30) days,
Registrant can either (i) show that it has not provided false or inaccurate contact information or (ii) provide the updated Whois information, then the registrant will be allowed to
maintain its usTLD domain name registration. If, however, after thirty (30) days, the registrant either does not respond to Registrar's notice or is unable to provide true and accurate contact
information, the registrant shall be deemed to have breached its registration agreement and the registrar shall be required to delete the registration.

	3.7.7.3.4
	Registrar
shall not be required to refund any fees paid by the registrant if the registrar terminates a Registrant's registration agreement due to its enforcement of this
provision. 

H-26

 

	3.7.7.4
	Any
Registrant that intends to license use of a domain name to a third party is nonetheless the Registrant of record and is responsible for providing its own full contact
information and for providing and updating accurate technical and administrative contact information adequate to facilitate timely resolution of any problems that arise in connection with the
Registered Name. A Registrant licensing use of a Registered Name according to this provision shall accept liability for harm caused by wrongful use of the Registered Name, unless it promptly discloses
the identity of the licensee to a party providing the Registrant reasonable evidence of actionable harm.

	3.7.7.5
	Registrar
shall provide notice to each new or renewed Registrant stating:

	3.7.7.5.1
	The
purposes for which any personal data collected from the applicant are intended;

	3.7.7.5.2
	The
intended recipients or categories of recipients of the data (including NeuStar, as Registry, and others who will receive the data from NeuStar, as Registry);

	3.7.7.5.3
	Which
data are obligatory and which data, if any, are voluntary; and

	3.7.7.5.4
	How
the Registrant or data subject can access and, if necessary, rectify the data held about them.

	3.7.7.5
	The
Registrant shall consent to the data processing referred to in this Section 3.7.7.4.

	3.7.7.6
	The
Registrant shall represent that notice has been provided equivalent to that described in Subsection 3.7.7.4 to any third-party individuals whose personal data are supplied to
Registrar by the Registrant, and that the Registrant has obtained consent equivalent to that referred to in Subsection 3.7.7.5 of any such third-party individuals.

	3.7.7.7
	Registrar
shall agree that it will not process the personal data collected from the Registrant in a way incompatible with the purposes and other limitations about which it has
provided notice to the Registrant in accordance with Subsection 3.7.7.4 above.

	3.7.7.8
	Registrar
shall agree that it will take reasonable precautions to protect personal data from loss, misuse, unauthorized access or disclosure, alteration, or destruction.

	3.7.7.9
	The
Registrant shall represent that, to the best of the Registrant's knowledge and belief, neither the registration of the Registered Name nor the manner in which it is directly
or indirectly used infringes the legal rights of any third party.

	3.7.7.10
	For
the adjudication of disputes concerning or arising from use of the Registered Name, the Registrant shall submit, without prejudice to other potentially applicable
jurisdictions, to the jurisdiction of the courts (1) of the Registrant's domicile and (2) where Registrar is located.

	3.7.7.11
	The
Registrant shall agree that its registration of the Registered Name shall be subject to suspension, cancellation, or transfer pursuant to any NeuStar adopted specification or
policy, or pursuant to any registrar or registry procedure not inconsistent with a NeuStar adopted specification or policy, (1) to correct mistakes by Registrar or the Registry in registering
the name or (2) for the resolution of disputes concerning the Registered Name.

	3.7.7.12
	The
Registrant shall indemnify and hold harmless the Registry and its directors, officers, employees, representatives, agents, affiliates, and stockholders from and 

H-27

 

against
any and all claims, suits, actions, other proceedings, damages, liabilities, costs and expenses of any kind, including without limitation reasonable legal fees and expenses, arising out of or
relating to the Registrant's (i) domain name registration and (ii) use of any Registered Name.

	3.7.7.13
	Registrar
shall require in its Registration Agreement with each Registrant that such Registrant certify, under penalty of perjury, that it meets the following Nexus Requirements
to qualify to register to use a Registered Name. Registrants in the usTLD must be either:

	3.7.7.13.1
	A
natural person (i) who is a citizen or permanent resident of the United States of America or any of its possessions or territories, or (ii) whose primary place
of domicile is in the United States of America or any of its possessions, or

	3.7.7.13.2
	An
entity or organization that is (i) incorporated within one of the fifty (50) U.S. states, the District of Columbia, or any of the United States possessions or
territories or (ii) organized or otherwise constituted under the laws of a state of the United States of America, the District of Columbia or any of its possessions or territories, or

	3.7.7.13.3
	An
entity or organization (including a federal, state, or local government of the United States, or a political subdivision thereof) that has a bona fide presence in the United
States.

	3.7.8
	Registrar
shall abide by any specifications or policies established according to Section 4 requiring reasonable and commercially practicable (a) verification, at the
time of registration, of contact information associated with a Registered Name sponsored by Registrar or (b) periodic re-verification of such information. Registrar shall, upon
notification by any person of an inaccuracy in the contact information associated with a Registered Name sponsored by Registrar, take reasonable steps to investigate that claimed inaccuracy. In the
event Registrar learns of inaccurate contact information associated with a Registered Name it sponsors, it shall take reasonable steps to correct that inaccuracy.

	3.7.9
	Registrar
shall abide by any NeuStar adopted specifications or policies prohibiting or restricting warehousing of or speculation in domain names by registrars.

	3.7.10
	Nothing
in this Accreditation Agreement prescribes or limits the amount Registrar may charge Registrant for registration of Registered Names.

	3.8
	Domain-Name Dispute Resolution.    During the Term of this Accreditation Agreement, Registrar shall have in place
a policy and procedures for resolution of disputes concerning Registered Names. Until different policies and procedures are established by NeuStar under Section 4, Registrar shall comply with
the United Stated Dispute Resolution Policy (usDRP) and the Nexus Dispute Policy ("NDP") identified on Registry's website.

	3.9
	Accreditation Fees.    As a condition of accreditation, Registrar shall pay accreditation fees to NeuStar. These fees consist
of yearly and variable fees.

	3.9.1
	Fixed Accreditation Fee.    Registrar shall pay NeuStar a fixed yearly accreditation fee in an amount established by
NeuStar. The first year's accreditation fee shall be $1,000 for the usTLD. Thereafter, the yearly accreditation fee may be increased by up to ten percent (10%) from the previous year. Payment of the
yearly fixed fee shall be due within thirty (30) days after invoice from NeuStar. 

H-28

 

	3.9.2
	Variable Accreditation Fee.    Registrar shall pay the variable accreditation fees established by NeuStar, provided that in
each case such fees are reasonably allocated among all registrars that contract with NeuStar. Registrar shall pay such fees in a timely manner for so long as all material terms of this Accreditation
Agreement remain in full force and effect, and notwithstanding the pendency of any dispute between Registrar and NeuStar.

	3.9.3
	On
reasonable notice given by NeuStar to Registrar, accountings submitted by Registrar shall be subject to verification by an audit of Registrar's books and records by an
independent third-party that shall preserve the confidentiality of such books and records (other than its findings as to the accuracy of, and any necessary corrections to, the accountings).

	3.10
	Insurance.    Registrar shall maintain in force commercial general liability insurance with policy limits of at least
$500,000 covering liabilities arising from Registrar's registrar business during the term of this Accreditation Agreement. 

4.     PROCEDURES FOR ESTABLISHMENT OR REVISION OF SPECIFICATIONS AND POLICIES.  

	4.1
	Registrar's Ongoing Obligation to Comply With New or Revised Specifications and Policies.    During the Term of this
Accreditation Agreement, Registrar shall comply with the terms of this Accreditation Agreement on the schedule set forth in Subsection 4.4, with

	4.1.1
	new
or revised specifications (including forms of agreement to which Registrar is a party) and policies established by NeuStar as Consensus Policies in the manner described in
Subsection 4.3,

	4.1.2
	in
cases where:

	4.1.2.1
	this
Accreditation Agreement expressly provides for compliance with revised specifications or policies established in the manner set forth in one or more subsections of this
Section 4; or

	4.1.2.2
	the
specification or policy concerns one or more topics described in Subsection 4.2.

	4.2
	Manner of Establishment of New and Revised Specifications and Policies

	4.2.1
	"NeuStar
Policies" are those specifications or policies established by NeuStar through the United States Policy Advisory Council ("usPAC").

	4.2.2
	For
all purposes under this Accreditation Agreement, the policies specifically identified by NeuStar on its website for the usTLD <LINK> at the date of this Accreditation
Agreement as having been adopted by NeuStar before the date of this Accreditation Agreement shall be treated in the same manner and have the same effect as "NeuStar Policies". Such NeuStar Policies
are hereby incorporated by reference and shall be binding on Registrar.

	4.3
	Time Allowed for Compliance.    Registrar shall be afforded a reasonable period of time after receiving notice of the
establishment of a specification or policy under Subsection 4.2 in which to comply with that specification or policy, taking into account any urgency involved. 

5.     MISCELLANEOUS PROVISIONS. 

	5.1
	Specific Performance.    While this Accreditation Agreement is in effect, either party may seek specific performance of any
provision of this Accreditation Agreement in the manner provided in Section 5.5 below, provided the party seeking such performance is not in material breach of its obligations. 

H-29

 

	5.2
	Termination of Accreditation Agreement by Registrar.    This Accreditation Agreement may be terminated before its expiration
by Registrar by giving NeuStar thirty (30) days written notice. Upon such termination by Registrar, Registrar shall not be entitled to any refund of fees paid to NeuStar pursuant to this
Accreditation Agreement.

	5.3
	Termination of Accreditation Agreement by NeuStar.    This Accreditation Agreement may be terminated before its expiration by
NeuStar in any of the following circumstances:

	5.3.1
	There
was a material misrepresentation, material inaccuracy, or materially misleading statement in Registrar's application for accreditation or any material accompanying the
application.

	5.3.2
	Registrar:

	5.3.2.1
	is
convicted by a court of competent jurisdiction of a felony or other serious offense related to financial activities, or is judged by a court of competent jurisdiction to have
committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that NeuStar reasonably deems as the substantive equivalent of those offenses; or

	5.3.2.2
	is
disciplined by the government of its domicile for conduct involving dishonesty or misuse of funds of others.

	5.3.3
	Any
officer or director of Registrar is convicted of a felony or of a misdemeanor related to financial activities, or is judged by a court to have committed fraud or breach of
fiduciary duty, or is the subject of a judicial determination that NeuStar deems as the substantive equivalent of any of these; provided, such officer or director is not removed in such circumstances.

	5.3.4
	Registrar
fails to cure any breach of this Accreditation Agreement within fifteen (15) business days after NeuStar gives Registrar notice of the breach.

	5.3.5
	Registrar
fails to comply with a ruling granting specific performance under Subsections 5.1 and 5.5.

	5.3.6
	Registrar
continues acting in a manner that NeuStar has reasonably determined endangers the stability or operational integrity of the Internet or the Registry System after receiving
three (3) days notice of that determination.

	5.3.7
	Registrar
becomes bankrupt or insolvent.

	5.4
	Term of Accreditation Agreement; Renewal; Right to Substitute Updated Accreditation Agreement.    This Accreditation
Agreement shall be effective on the Effective Date and shall have an initial term running until the Expiration Date, unless sooner terminated. Thereafter, if Registrar seeks to continue its
accreditation, it may apply for renewed accreditation, and shall be entitled to renewal provided it meets the NeuStar-adopted specification or policy on accreditation criteria then in effect, is in
compliance with its obligations under this Accreditation Agreement, as it may be amended, and agrees to be bound by terms and conditions of the then-current Registrar accreditation
agreement (which may differ from those of this Accreditation Agreement) that NeuStar adopts in accordance with Subsection 2.3 and Subsection 4.2. In connection with renewed accreditation, Registrar
shall confirm its assent to the terms and conditions of the then-current Registrar accreditation agreement by signing that accreditation agreement. In the event that, during the Term of
this Accreditation Agreement, NeuStar posts on its web site an updated form of registrar accreditation agreement applicable to Accredited registrars, Registrar (provided it has not received
(1) a notice of breach that it has not cured or (2) a notice of termination of this Accreditation Agreement under Subsection 

H-30

 

5.3
above) may elect, by giving NeuStar written notice, to enter an agreement in the updated form in place of this Accreditation Agreement. In the event of such election, Registrar and NeuStar shall
promptly sign a new accreditation agreement that contains the provisions of the updated form posted on the web site, with the length of the term of the substituted agreement as stated in the updated
form posted on the web site, calculated as if it commenced on the date this Accreditation Agreement was made, and this Accreditation Agreement will be deemed terminated. 

	5.5
	Resolution of Disputes Under this Accreditation Agreement; Governing Law.    Disputes arising under or in connection with
this Accreditation Agreement, including (1) disputes arising from NeuStar's failure to renew Registrar's accreditation and (2) requests for specific performance, shall be resolved in a
court of competent jurisdiction or, at the election of either party, by an arbitration conducted as provided in this Subsection 5.5 pursuant to the Arbitration Rules of the American Arbitration
Association ("AAA"). The arbitration shall be conducted in English and shall occur in Washington, D.C., USA. There shall be three (3) arbitrators: each party shall choose one arbitrator; if
those two arbitrators do not agree on a third arbitrator within fifteen (15) calendar days of the designation of the second arbitrator, the AAA shall choose the third. The parties shall bear
the costs of the arbitration in equal shares, subject to the right of the arbitrators to reallocate the costs in their award as provided in the AAA rules. The parties shall bear their own attorneys'
fees in connection with the arbitration, and the arbitrators may not reallocate the attorneys' fees in conjunction with their award. The arbitrators shall render their decision within ninety
(90) days of the of the selection of the third arbitrator. In the event Registrar initiates arbitration to contest the appropriateness of termination of this Accreditation Agreement by NeuStar,
Registrar may at the same time request that the arbitration panel stay the termination until the arbitration decision is rendered, and that request shall have the effect of staying the termination
until the arbitration panel has granted a NeuStar request for specific performance and Registrar has failed to comply with such ruling. In all litigation involving NeuStar concerning this
Accreditation Agreement (whether in a case where arbitration has not been elected or to enforce an arbitration award), jurisdiction and exclusive venue for such litigation shall be in a court located
in the Eastern District of the Commonwealth of Virginia, USA; however, the parties shall also have the right to enforce a judgment of such a court in any court of competent jurisdiction. For the
purpose of aiding the arbitration and/or preserving the rights of the parties during the pendency of an arbitration, the parties shall have the right to seek temporary or preliminary injunctive relief
from the arbitration panel or in a court located in the Eastern District of the Commonwealth of Virginia, USA, which shall not be a waiver of this arbitration agreement. This Accreditation Agreement
shall be construed in accordance with and governed by the laws of the Commonwealth of Virginia (without regard to any rules or principles of conflicts of law that might look to any jurisdiction
outside Virginia).

	5.6
	Limitations on Monetary Remedies for Violations of this Accreditation Agreement.    NeuStar's aggregate monetary liability
for violations of this Accreditation Agreement shall not exceed the amount of accreditation fees paid by Registrar to NeuStar under Subsection 3.9 of this Accreditation Agreement. Registrar's monetary
liability to NeuStar for violations of this Accreditation Agreement shall be limited to the aggregate amount of accreditation fees previously paid plus those then owing to NeuStar under this
Accreditation Agreement. IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE, EXEMPLARY, OR CONSEQUENTIAL DAMAGES FOR ANY VIOLATION OF THIS ACCREDITATION AGREEMENT.

	5.7
	Assignment.    Either party may assign or transfer this Accreditation Agreement only with the prior written consent of the
other party, which shall not be unreasonably withheld, except that 

H-31

 

NeuStar
may, with the written approval of the U.S. Department of Commerce, assign this agreement by giving Registrar written notice of the assignment. 

	5.9
	No Third-Party Beneficiaries.    This Accreditation Agreement shall not be construed to create any obligation by either
NeuStar or Registrar to any non-party to this Accreditation Agreement, including any Registrant.

	5.10
	Notices, Designations, and Specifications.    Any notice or other communication required or permitted to be delivered to any
party under this Accreditation Agreement shall be in writing and shall be deemed properly delivered, given and received when delivered by hand, by registered mail (return receipt requested), by
courier or express delivery service, by e-mail (against of receipt of confirmation of delivery) or by telecopier (against receipt of answerback confirming delivery) during business hours
to the address or telecopier number set forth beneath the name of such party below or when delivery as described above is refused by the intended recipient, unless such party has given a notice of a
change of address in writing pursuant to the foregoing. Notwithstanding the foregoing, notice shall be deemed properly given from NeuStar to Registrar at such time as NeuStar posts any notice, update,
modification or other information on its U.S. website, so long as such notice, update, modification or other information is intended for all accredited registrars generally (e.g., adoption of a new
Consensus Policy).. 

If
to Registrar: 

	 
	 
	 
	 
	 
	 

with
copy to: 

	 
	 
	 
	 
	 
	 

If
to Registry: 

	NeuStar, Inc.

1120 Vermont Avenue

Suite 400

Washington, DC 20005

Attn: VP of

phone:

fax:

H-32

 

with
a copy to: 

	NeuStar, Inc.

1120 Vermont Avenue

Suite 400

Washington, DC 20005

Attn: General Counsel

phone:

fax:

	5.11
	Dates and Times.    All dates and times relevant to this Accreditation Agreement or its performance shall be computed based
on the date and time observed in Washington, D.C., USA.

	5.12
	Language.    All notices, designations, and specifications made under this Accreditation Agreement shall be in the English
language.

	5.13
	Amendments and Waivers.    No amendment, supplement, or modification of this Accreditation Agreement or any provision hereof
shall be binding unless executed in writing by both parties. No waiver of any provision of this Accreditation Agreement shall be binding unless evidenced by a writing signed by the party waiving
compliance with such provision. No waiver of any of the provisions of this Accreditation Agreement shall be deemed or shall constitute a waiver of any other provision hereof, nor shall any such waiver
constitute a continuing waiver unless otherwise expressly provided.

	5.14
	Counterparts.    This Accreditation Agreement may be executed in one or more counterparts, each of which shall be deemed an
original, but all of which together shall constitute one and the same instrument.

	5.15
	Entire Accreditation Agreement.    Except to the extent (a) expressly provided in a written agreement executed by
both parties concurrently herewith or (b) of written assurances provided by Registrar to NeuStar in connection with its Accreditation, this Accreditation Agreement constitutes the entire
agreement of the parties pertaining to the accreditation of Registrar and supersedes all prior agreements, understandings, negotiations and discussions, whether oral or written, between the parties on
that subject.

	5.16
	Construction; Severability.    The parties agree that any rule of construction to the effect that ambiguities are to be
resolve against the drafting party shall not be applied in the construction or interpretation of this Accreditation Agreement. Unless otherwise stated in this Accredition Agreement, references to a
number of days shall mean consecutive calendar days. In the event that any clause or portion thereof in this Accreditation Agreement is for any reason held to be invalid, illegal or unenforceable, the
same shall not affect any other portion of this Accreditation Agreement, as it is the intent of the parties that this Accreditation Agreement shall be construed in such fashion as to maintain its
existence, validity and enforceability to the greatest extent possible. In any such event, this Accreditation Agreement shall be construed as if such clause or portion thereof had never been contained
in this Accreditation Agreement, and there shall be deemed substituted therefor such provision as will most nearly carry out the intent of the parties as expressed in this Accreditation Agreement to
the fullest extent permitted by applicable law. 

H-33

 

        IN
WITNESS WHEREOF, the parties hereto have caused this Accreditation Agreement to be executed in duplicate by their duly authorized representatives. 

	NeuStar, INC.	 	 	 	 
	

By:	
 	

 
	
 	

 	
 	

 
	Name:	 	 
	 	 	 	 
	Title:	 	 
	 	 	 	 
	

[Registrar Name]	
 	

 	
 	

 
	

By:	
 	

 
	
 	

 	
 	

 
	Name:	 	 
	 	 	 	 
	Title:	 	 
	 	 	 	 

H-34

   Working Draft Dated 07-19-01 v1.0  

Registrar Accreditation: Application  

HOW TO APPLY:  

        For your application to be considered, you must send hard copies of the following items to NeuStar: 

        Completed
application. A completed application consists of your responses to the questions set forth in this document, typed or printed out on separate paper and attached to a signed
copy of this application form. 

        All
supporting documents as indicated below and in the Application Instructions. These will generally include an insurance certificate and an independently verified financial statement,
along with any other supporting documents needed to provide complete answers to the questions below. NOTE: Application Instructions will be made available prior to the
commencement of the accreditation process.

        Application
Fee. US $750 (non-refundable). Application fees may be submitted by wire transfer, money order, or bank check, and must be denominated in United States currency.
If you want to pay by wire transfer, please send an email to <                        @NeuStar.com> so we can track your
payment. The following is the bank account information you will need to send
a wire transfer: 

	 	Account number	 	 
	 	 
	 	Routing indicator	 	 
	 	 
	 	[Name of Bank] Branch #	 	 
	 	 
	 	[insert address]	 	 	 	 
	

 	

Telephone [insert telephone number of Bank]	
 	

 

        Completed
applications should be sent by mail or courier directly to NeuStar at the following address: 

NeuStar, Inc.

Registrar Accreditation

1120 Vermont Avenue, Suite 400

Washington, DC 20005

Phone: (310) 823-9358 

        NeuStar
accepts applications for registrar accreditation on a rolling basis. There is no deadline for receipt of applications for registrar accreditation. 

        Please
provide the following information on separate paper, answering each request in a numbered paragraph corresponding to the number of the question. If there is no answer available
for a particular question, please indicate that fact next to the number corresponding to the question. In answering the questions set forth below, please give the most complete answer possible,
explaining all capabilities in detail, and attaching, labeling, and referencing all necessary supporting documents at the back of the application. See the Application Instructions for additional
guidance. 

        After
reviewing your answers and supporting materials, we reserve the right, in our sole discretion, to request additional information in order to assess your capabilities to serve as an
accredited registrar. Submission of any such supplemental information shall be subject to the "ATTESTATION OF TRUTHFUL DISCLOSURE" set forth below. 

H-35

 

Registrar Accreditation Application  

GENERAL INFORMATION: 

	1.
	Name
and business address of entity applicant.

	2.
	Type
of business entity (corporation, partnership, etc.).

	3.
	Telephone
number of applicant.

	4.
	Facsimile
number of applicant, if available.

	5.
	E-mail
address of applicant.

	6.
	Name
of contact person.

	7.
	Telephone
number and email address of contact person, if different from 3. and 5., above.

	8.
	Internet
address for your World Wide Web site.

	9.
	Please
list (i) all directors, (ii) all officers, (iii) all relevant managers, and (iv) any persons or entities owning five percent or more of
your current or proposed business entity. 

BUSINESS CAPABILITIES: 

	10.
	Describe
your current business capabilities or comprehensive business plan as specified below.

	a.
	Give
an overview of your current business operations or business plan. (If you are a publicly traded company, this may be done by providing a copy of your most recent annual report.)

	b.
	What
volume of registrations for.us domain names ("UDSNs") do you reasonably project to be able to handle per month?

	c.
	What
management, communication, and information processing systems do you have (or propose to have) to handle your projected volume of registration business per month? Please be
specific.

	d.
	What
management, communication, and information processing systems do you have (or propose to have) to promptly handle USDN holders' requests for changes in registration data? How long
do you anticipate that such requests will take to execute?

	e.
	What
is your capability (or proposal for capability) for providing a reliable and readily usable daily backup and archive of all USDN holder and registration data?

	f.
	What
is your capability (or proposal for capability) for maintaining electronic copies of all transactions, correspondence, and communications with the shared registration system (SRS)
for at least the length of the registration contract?

	g.
	What
is your capability (or proposal for capability) for providing public access on a real-time basis (such as through a Whois service) to the data elements NeuStar has
designated for all active USDN registrations you sponsor in the registry (see Section 3.5 of the Registrar Accreditation Agreement)?

	h.
	What
is your capability (or proposal for capability) for providing information systems security procedures to prevent system hacks, break-ins, data tampering, and other
disruptions to your operations?

	i.
	What
is your capability (or proposal for capability) for providing USDN holders with continued use of their domain names in the event you go out of business or otherwise cease to
operate as an NeuStar-accredited registrar of USDNs? 

H-36

 

	j.
	Do
you (or will you) have the capacity to engage a sufficient number of qualified employees to handle the registration, update, and customer inquiry volume you projected in question
10.b?

	k.
	What
is your capability (or proposal for capability) for ensuring that the operation of the Internet will not be adversely affected in the event you go out of business or otherwise
cease to operate as an NeuStar-accredited registrar of USDNs?

	l.
	Do
you have commercial general liability insurance? From what insurer? In what amount? If you do not currently have such insurance, how do you propose to obtain it, and in what amount?
Please attach a current and valid certificate of insurance, if you currently hold it. If you do not currently have insurance, please attach a binder or other similar evidence of insurability (or the
intent to insure) from an insurance company.

	m.
	How
much working capital do you have available for the operation of the registrar business? Is this level of liquid capital sufficient for your projected registration volume? Please
attach evidence of working capital (if available, an audited statement for your most recent fiscal period is sufficient).

	n.
	Do
you hold an existing and operational USDN (i.e., "NeuStar.com"), second-level domain under any of the gTLDs (i.e., .biz, .com, .net, etc.) or country code top level domains (i.e.
..au), or third level domain if operating under a country code top level domain (i.e., "cam.ac.uk")? If so, please list all domain names (or third level domains) under which you or your affiliates do
business.

	o.
	Can
you meet all of a registrar's obligations under the Registrar Accreditation Agreement ? If there are any provisions of the Registrar Accreditation Agreement you may not be able to
fulfill, please explain the circumstances that prevent you from doing so.

	11.
	Have
you submitted to NeuStar within the past year an accreditation application or material accompanying an accreditation application that NeuStar has found to contain a
material misrepresentation, material inaccuracy, or materially misleading statement? If yes, then please explain the circumstances.

	12.
	Indicate
whether (i) the applicant or any of its (ii) officers, (iii) directors, or (iv) managers:

	a.
	within
the past ten years, has been convicted of a felony or of a misdemeanor related to financial activities, or has been judged by a court to have committed fraud or breach of
fiduciary duty, or has been the subject of a judicial determination that is similar or related to any of these;

	b.
	within
the past ten years, has been disciplined by the government of its, her, or his domicile for conduct involving dishonesty or misuse of funds of others;

	c.
	is
currently involved in any judicial or regulatory proceeding that could result in a conviction, judgment, determination, or discipline of the type specified in (a) or (b); or

	d.
	is
the subject of a disqualification imposed by NeuStar and in effect at the time of this application. 

If
any of the above events have occurred, please provide details. 

	13.
	Do
you give NeuStar permission to use your company's name and/or logo in its public announcements (including informational web pages) relating to registrar
accreditation? 

PAST ICANN ACCREDITATION 

	14.
	Are
you currently an ICANN-Accredited Registrar for any of the gTLDs? If so, which one(s)? 

H-37

 
	15.
	If
you are not currently accredited by ICANN as a registrar, have you ever previously been accredited by ICANN to serve as a registrar? If so, please explain in detail
the circumstances surrounding the expiration or termination of your prior ICANN accreditation. 

ATTESTATION OF TRUTHFUL DISCLOSURE: 

        By
signing this application, the undersigned Applicant attests that the information contained in this application, and all supporting documents included with this application, are true
and accurate to the best of Applicant's knowledge. By signing this application, the undersigned Applicant gives NeuStar permission to contact third parties, investigate, request and obtain additional
information and documentation, and otherwise verify the information contained in this application. Applicant waives liability on the part of NeuStar for its actions in verifying the information
provided in this application.
Applicant further waives liability on the part of any third parties who provide truthful, material, relevant information about Applicant as requested in this application. 

	 
 Signature	 	 
	 
 Name (please print)	 	 
	 
 Title	 	 
	 
 Name of Applicant Entity	 	 
	 
 Date	 	 

        Please
attach all answers and supporting documents to a signed copy of this application form. Please include the application fee and send directly or by courier to NeuStar at the address
indicated above. 

H-38

  

 
 

EXHIBIT D    
    
    POLICY ON TRANSFER OF SPONSORSHIP OF
  REGISTRATIONS BETWEEN NON-SPONSORING REGISTRARS    
    

A.    Holder-Authorized Transfers.  

Registrar Requirements.  

        The Registration Agreement between each registrar and its Registrant shall include a provision explaining that a Registrant will be prohibited from changing its
registrar during the first 60 days after initial registration of the domain name with the registrar. Beginning on the 61st day after the initial registration with the registrar, the procedures
for change in sponsoring registrar set forth in this policy shall apply. Enforcement shall be the responsibility of the registrar sponsoring the domain name registration. 

        For
each instance where a Registrant wants to change its registrar for an existing domain name (i.e., a domain name that appears in a particular top-level domain zone file),
the gaining registrar shall: 

	1)
	Obtain
express authorization from an individual who has the apparent authority to legally bind the Registrant (as reflected in the database of the losing registrar).

	a)
	The
specific form of the authorization is at the discretion of each gaining registrar.

	b)
	The
gaining registrar shall retain a record of reliable evidence of the authorization.

	2)
	In
those instances when the registrar of record is being changed simultaneously with a transfer of a domain name from one party to another, the gaining registrar shall also obtain
appropriate authorization for the transfer. Such authorization shall include, but not be limited to, one of the following:

	a)
	A
bilateral written agreement between the parties.

	b)
	The
final determination of a binding dispute resolution body.

	c)
	A
court order.

	3)
	Request,
by the transmission of a "transfer" command as specified in the Registrar Tool Kit, that the usTLD Database be changed to reflect the new registrar.

	a)
	Transmission
of a "transfer" command constitutes a representation on the part of the gaining registrar that:

	(1)
	the
requisite authorization has been obtained from the Registrant listed in the database of the losing registrar, and

	(2)
	the
losing registrar will be provided with a copy of the authorization if and when requested. 

        In
those instances when the registrar of record denies the requested change of prospective gaining registrar, the registrar of record shall notify the prospective gaining Registrar that
the request was denied and the reason for the denial. 

        Instances
when the requested change of prospective gaining registrar may be denied include, but are not limited to: 

	1)
	Situations
described in the Domain Name Dispute Resolution Policy

	2)
	A
pending bankruptcy of the Registrant

	3)
	Dispute
over the identity of the Registrant 

H-39

 

	4)
	Request
to transfer sponsorship occurs within the first 60 days after the initial registration with the registrar of record 

        In
all cases, the losing registrar shall respond to the e-mail notice regarding the transfer request within five (5) days. Failure to respond will result in a default
"approval" of the transfer. 

usTLD Administrator Requirements.  

        Upon receipt of the "transfer" command from the gaining registrar, usTLD Administrator will transmit an e-mail notification to both registrars. 

        usTLD
Administrator shall complete the "transfer" if either: 

	1)
	the
losing registrar expressly "approves" the request, or

	2)
	usTLD
Administrator does not receive a response from the losing registrar within five (5) days. 

        When
the usTLD Database has been updated to reflect the change to the gaining registrar, usTLD Administrator will transmit an email notification to both registrars. 

Records of Registration.  

        Each Registrant shall maintain his, her or its own records appropriate to document and prove the initial domain name registration date, regardless of the number
of registrars with which the Registrant enters into a contract for registration services. 

Effect on Term of Registration.  

        The completion by usTLD Administrator of a holder-authorized transfer under this Part A shall result in a one-year extension of the existing
registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) years. 

B.    Approved Transfers.  

        Transfer of the sponsorship of all the registrations sponsored by one registrar as the result of acquisition of that registrar or its assets by another registrar
may be made according to the following procedure: 

	(a)
	The
acquiring registrar must be accredited by usTLD Administrator for the usTLD under an Accreditation Agreement and must have in effect a usTLD Administrator-Registrar Agreement with
usTLD Administrator for the usTLD.

	(b)
	usTLD
Administrator shall determine, in its sole discretion, that the transfer would promote the community interest, such as the interest in stability that may be threatened by the
actual or imminent business failure of a registrar. 

        Upon
satisfaction of these two conditions, usTLD Administrator will make the necessary one-time changes in the registry database for no charge for transfers involving 50,000
name registrations or fewer; provided that the data to be transferred to usTLD Administrator is in the form specified by usTLD Administrator ("Approved Format"). If the transfer involves registrations
of more than 50,000 names, and the data to be transferred to usTLD Administrator is in the Approved format, usTLD Administrator will charge the acquiring registrar a one-time flat fee of
US $50,000. If the data to be transferred is not in the Approved Format, the usTLD Administrator may charge a reasonable fee, as determined by the usTLD Administrator, in connection with the cost
associated with reformatting such data. 

        Notwithstanding
anything in the Exhibit E above to the contrary, no transfers will be permitted from a registrar, including
Registrar, to a Sponsoring Registrar. 

H-40

  

 
 

Exhibit E    
    
    USTLD ADMINISTRATOR'S OPERATIONAL STANDARDS,
  POLICIES, PROCEDURES, AND PRACTICES    
    

I.     Registration Requirements  

        Before the usTLD Administrator will accept applications for registration from an registrar, all domain name applicants in the .us TLD must: 

	1.
	Enter
into an electronic or paper registration agreement with the registrar, in accordance with the Accreditation Agreement with usTLD Administrator and this Agreement. Such electronic
or paper registration agreement shall include, at a minimum, the following certifications:

	a)
	The
data provided in the domain name registration application is true, correct, up to date and complete; and

	b)
	The
registrant will keep the information provided above up to date.

	2.
	Certify
in the Registration Agreement that to the best of his, her or its knowledge the domain name registrant has the authority to enter into the Registration Agreement and meets all
the US Nexus Requirement set forth below. 

II.    US Nexus Requirement  

        Registrants in the usTLD must be either: 

	1.
	A
natural person (i) who is a citizen or permanent resident of the United States of America or any of its possessions or territories, or (ii) whose primary place of
domicile is in the United States of America or any of its possessions, or

	2.
	An
entity or organization that is (i) incorporated within one of the fifty (50) U.S. states, the District of Columbia, or any of the United States possessions or
territories or (ii) organized or otherwise constituted under the laws of a state of the United States of America, the District of Columbia or any of its possessions or territories, or

	3.
	An
entity or organization (including a federal, state, or local government of the United States, or a political subdivision thereof) that has a bona fide presence in the United States. 

        Whether
a prospective registrant has a "bona fide presence in the United States" will be determined on a case-by-case basis in light of all relevant facts and
circumstances at the time of application for a usTLD domain name. This requirement is intended to ensure that only those individuals or organizations that have a substantive connection to the United
States are permitted to register for usTLD domain names. 

        Factors
that should be considered in determining whether an entity or organization has a bona fide presence in the United States shall include, without limitation, whether such
prospective usTLD domain name registrant: 

	•
	Regularly
performs activities within the United States related to the purposes for which the entity or organization is constituted (e.g., providing services to customers,
conducting regular training activities, attending conferences), provided such activities are not conducted solely or primarily to permit it to register for a usTLD domain name;

	•
	Maintains
an office or other facility in the United States for a business, noncommercial, educational, or governmental purpose and not solely or primarily to permit it to
register for a usTLD domain name; or 

H-41

 

	•
	Derives
a material portion of its revenues or net income from sales to purchasers located in the United States. For these purposes, if a prospective usTLD domain name
registrant's revenues from sales to purchasers located in the United States were at least 5% of such entity's or organization's total revenues or net income for its last completed fiscal year, such
entity or organization will be presumed to have a bona fide presence in the United States. 

        For
purposes of this definition, the terms United States and United States of America shall include all U.S. territories and possessions. 

        It
shall be a continuing requirement that all usTLD domain name registrants maintain the US Nexus Requirement. 

        The
Nexus Requirement will be enforced through an initial screening of the contact information provided by the registrant, as well as a challenge process permitted through the Nexus
Dispute Policy discussed below. The screening by usTLD Administrator will verify that selected field, within the contact information provided, on its face, meets the Nexus Requirement and that the
registrant has certified compliance with the requirement, as well as certified that the nameservers identified are located within the United States. In
the event that the contact information provided does not meet the above requirement, the name requested will be placed on hold within the registry and the registrant will be given an opportunity to
correct any mistake or demonstrate compliance with the Nexus requirement. If no action is taken by the registrant within the 30-day period, the registration will be cancelled and the name
will be returned to available status. If, on the other hand, the registrant is able to demonstrate compliance with the requirement, the name will be registered. 

III.  Nexus Dispute Policy  

        Although the Nexus Requirement will initially be enforced through a usTLD Registrar's screening of the contact information provided by the registrant, and the
registrant will certify that it meets at least one of the Nexus requirements set forth above, usTLD Administrator understands that disputes may
arise as to the authenticity, veracity or accuracy of the registrant's Nexus certification. Therefore, usTLD Administrator, as administrator of the usTLD has devised a Nexus Dispute Policy ("NDP")
which will be administered solely by the usTLD Administrator, or its designated representative. The NDP will provide interested parties with an opportunity to challenge a registration not complying
with the Nexus Requirement. 

        In
the event that a third party wishes to challenge the authenticity or veracity of a.US registrant's United States Nexus, that party may submit a "Nexus Challenge" to the usTLD
Administrator or its authorized representative. The challenger must submit a written statement to the usTLD Administrator via first class mail alleging in specificity evidence to support its
allegation that the registrant fails to meet any of the Nexus Requirements set forth above. 

        Once
a challenge is received by the usTLD Administrator the domain name shall be "locked" by the usTLD Administrator until the matter is resolved. While in a "locked" position, the
registrant may not (i) change any of the contact information for that particular domain name or (ii) transfer the domain name to any third party. 

        In
the event that the usTLD Administrator finds that the challenger has established a prima facie case that the registrant has not met any of the Nexus Requirements, the usTLD
Administrator shall issue a letter to the registrant to submit evidence of compliance with the Nexus Requirements ("Letter"). The registrant shall have a period of thirty (30) days from the
date of the Letter to submit evidence of compliance. If, within the thirty (30) days, the registrant submits evidence establishing any of the Nexus Requirements, the registrant shall be
permitted to keep the domain name. 

        If,
however, the registrant either (i) does not respond within the thirty days, or (ii) is unable to demonstrate through documentary evidence that it met any of the Nexus
Requirements prior to the 

H-42

 

date
the NDP was invoked, the usTLD Administrator shall issue a finding that the registrant has failed to meet the Nexus Requirements. Upon such a finding, the registrant shall be given a total of
thirty (30) days to cure the US Nexus deficiency. If the registrant is able to demonstrate within (30) days that it has cured such deficiency, the registrant shall be allowed to keep the
domain name. If the registrant either (i) does not respond within the thirty (30) days, or (ii) is unable to proffer evidence demonstrating compliance with the Nexus Requirements,
the domain name registration shall be deleted from the registry database and the domain name will be placed into the list of available domain names. This process represents the exclusive remedy for an
NDP challenger. 

        usTLD
Administrator reserves the right to modify this NDP at any time with the permission of COTR. usTLD Administrator will post its revised NDP on its Website at least thirty
(30) calendar days before it becomes effective. 

IV.    Reservation  

        usTLD Administrator reserves the right to deny, cancel or transfer any registration 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, in compliance with any dispute resolution
process; (3) to avoid any liability, civil or criminal, on the part of usTLD Administrator, as well as its affiliates, subsidiaries, officers, directors, representatives, employees, and
stockholders; (4) for violations of this Agreement (including its Exhibits); or (5) to correct mistakes made by usTLD Administrator or any registrar in connection with a domain name
registration. usTLD Administrator also reserves the right to freeze a domain name during resolution of a dispute. 

H-43

  

 
 

Exhibit F    
    
    REGISTRATION FEES    
    

	•
	Sunrise Registration.    Registrar agrees to pay the non-refundable fee of $10.00 per domain name for
the first year of registration. For each subsequent year of registration, Registrar shall pay $5.50 per domain name per year.

	•
	Initial Registration.    Registrar agrees to pay the non-refundable fee of $5.50 per year of
registration.

	•
	Renewal Fees.    Registrar agrees to pay the non-refundable fee of $5.50 per domain name per year for
renewals.

	•
	Fees for Transfers of Sponsorship of Domain-Name Registrations    Where the sponsorship of a domain
name is transferred from one registrar to another, usTLD Administrator may require the registrar receiving the sponsorship to request a renewal of one year for the name. In connection with that
extension, usTLD Administrator may charge a Renewal Fee for the requested extension as provided in the renewal schedule set forth above. The transfer shall result in an extension according to the
renewal request, subject to a ten-year maximum on the future term of any domain-name registration. The Renewal Fee shall be paid in full at the time of the transfer by the
registrar receiving sponsorship of the domain name.

	•
	Enhanced Whois Service.    Registrar agrees to pay the non-refundable amounts as set forth below: 

        To
be provided with at least 30 days advance notice: Yearly Subscription Fee Rate, One time Usage Fee 

        NOTE:
usTLD Administrator reserves the right to revise the Fees prospectively upon thirty (30) days notice to Registrar, provided that such adjustments are consistent with the
usTLD Agreement. 

H-44

 
 
 

Exhibit G    
    
    PERFORMANCE SPECIFICATIONS    
    

	1.
	Introduction.    The
attached Performance Specification Matrix ("Matrix") provides a list of performance specifications as they apply to the three Core Services provided by
the usTLD Administrator—SRS, Nameserver, and Whois services.

	2.
	Definitions.    Capitalized
terms used herein and not otherwise defined shall have the meaning ascribed to them in the Agreement.

	2.1
	"Core
Services" refers to the three core services provided by the usTLD System—SRS, Nameserver, and Whois Services.

	2.2
	"Performance
Specification" refers to the specific committed performance service levels as specified herein.

	2.3
	"Performance
Specification Priority" refers to the usTLD Administrator's rating system for Performance Specifications. Some Performance Specifications are more critical to the
operations of the usTLD Administrator than others. Each of the Performance Specifications is rated as C1-mission critical, C2-mission important, C3-mission
beneficial, or C4-mission maintenance.

	2.4
	"Registrar
Community" refers to all the registrars accredited by usTLD Administrator that have executed usTLD Administrator-Registrar Agreements with usTLD Administrator for the
usTLD.

	2.5
	"SRS"
refers to the Shared Registration System; the service that the usTLD System provides to the Registrar Community. Specifically, it refers to the ability of registrars to add,
modify, and delete information associated with domain names, nameserver, contacts, and registrar profile information. This service is provided by systems and software maintained in coactive redundant
data centers. The service is available to registrars via an Internet connection.

	2.6
	"Nameserver"
refers to the nameserver function of the usTLD System and the nameservers that resolve DNS queries from Internet users. This service is performed by multiple nameserver
sites that host DNS resource records. The customers of the nameserver service are users of the Internet. The nameservers receive a DNS query, resolve it to the appropriate address, and provide a
response.

	2.7
	"Service
Level Measurement Period" refers to the period of time for which a Performance Specification is measured. Monthly periods are based on calendar months, quarterly periods are
based on calendar quarters, and annual periods are based on calendar years.

	2.8
	"Whois"
refers to the usTLD Administrator's Whois service. The usTLD Administrator will provide contact information related to registered domain names and nameserver through a Whois
service. Any person with access to the Internet can query the usTLD Administrator's Whois service directly (via the usTLD Administrator website) or through a registrar.

	3.
	Performance Specifications.    usTLD Administrator shall use commercially reasonable efforts to provide usTLD Services for the
usTLD.

	3.1
	Service Availability.    Service Availability is defined as the time, in minutes, that the usTLD System's Core Services are
responding to its users. Service is unavailable when a service listed in the Matrix is unavailable to all users, that is, when no user can initiate a session with or 

H-45

 

receive
a response from the usTLD System ("Unavailability"). Service Availability is a C1 priority level. 

	3.1.1
	Service Availability is measured as follows: 

Service
Availability % = {[(TM - POM) - UOM] / (TM - POM)}*100 where: 

TM =
Total Minutes in the Service Level Measurement Period (#days*24 hours*60 minutes). 

POM =
Planned Outage Minutes (sum of (i) Planned Outages and (ii) Extended Planned Outages during the Service Level Measurement Period). 

UOM =
Unplanned Outage Minutes (Difference between the total number of minutes of Unavailability during the Service Level Measurement Period minus POM). 

Upon
written request, and at the sole expense of the requesting registrar(s), usTLD Administrator will retain an independent third party (to be selected by usTLD Administrator to perform an
independent calculation of the UOM). The frequency of this audit will be no more than once yearly during the term of the Agreement between usTLD Administrator and the Registrar. 

[This calculation is performed and the results reported for each calendar month for SRS and Whois availability and for each calendar year
for Nameserver availability. Results will be reported periodically to the Registrar Community via e-mail.] 

	3.1.2
	Service Availability—SRS = 99.9% per calendar month. Service Availability as it applies to the SRS refers to the
ability of the SRS to respond to registrars that access and use the SRS through the XRP protocol. SRS Unavailability will be logged with the usTLD Administrator as Unplanned Outage Minutes. The
committed Service Availability for SRS is 99.9% and the Service Level Measurement Period is monthly.

	3.1.3
	Service Availability—Nameserver = 99.999% per calendar year. Service Availability as it applies to the Nameserver
refers to the ability of the Nameserver to resolve a DNS query from an Internet user. Nameserver Unavailability will be logged with the usTLD Administrator as Unplanned Outage Minutes. The committed
Service Availability for Nameserver is 99.999% and the Service Level Measurement Period is annually.

	3.1.4
	Service Availability—Whois = 99.95% per calendar month. Service Availability as it applies to Whois refers to the
ability of all users to access and use the usTLD Administrator's Whois service. Whois Unavailability will be logged with the usTLD Administrator as Unplanned Outage Minutes. The committed Service
Availability for Whois is 99.95% and the Service Level Measurement Period is monthly.

	3.2
	Planned Outage.    High volume data centers like that used in the usTLD System require downtime for regular maintenance.
Allowing for regular maintenance ("Planned Outage") ensures a high level of service for the usTLD System. Planned Outage Performance Specifications are a C4 priority level.

	3.2.1
	Planned Outage Duration.    The Planned Outage Duration defines the maximum allowable time, in hours and minutes, that the
usTLD Administrator is allowed to take the usTLD Services out of service for regular maintenance. Planned Outages are planned in advance and the Registrar Community is provided warning ahead of time.
This Performance Specification, where applicable, has a monthly Service Level Measurement Period. The Planned Outage Duration for the Core Services is as follows:

	3.2.1.1
	Planned
Outage Duration—SRS = 8 hours (480 minutes) per month; 

H-46

 

	3.2.1.2
	Planned
Outage Duration—Nameserver = (no planned outages allowed); and

	3.2.1.3
	Planned
Outage Duration—Whois = 8 hours (480 minutes) per month.

	3.2.2
	Planned Outage Timeframe.    The Planned Outage Timeframe defines the hours and days in which the Planned Outage can occur.
The Planned Outage Timeframe for the Core Services is as follows:

	3.2.2.1
	Planned
Outage Timeframe—SRS = 1201-0800 UTC Sunday;

	3.2.2.2
	Planned
Outage Timeframe—Nameserver =(no planned outages allowed); and

	3.2.2.3
	Planned
Outage Timeframe—Whois = 0600-1400 UTC Sunday.

	3.2.3
	Planned Outage Notification.    The usTLD Administrator will notify all of its registrars of any Planned Outage. The
Planned Outage Notification Performance Specification defines the number of days prior to a Planned Outage that the usTLD Administrator will notify its registrars. The Planned Outage Notification for
the Core Services is as follows:

	3.2.3.1
	Planned
Outage Timeframe—SRS = 3 days;

	3.2.3.2
	Planned
Outage Timeframe—Nameserver =(no planned outages allowed); and

	3.2.3.3
	Planned
Outage Timeframe—Whois = 3 days.

	3.3
	Extended Planned Outage.    In some cases such as software upgrades and platform replacements an extended maintenance
timeframe is required. Extended Planned Outages will be less frequent than regular Planned Outages but their duration will be longer. Extended Planned Outage Performance Specifications are a C4
priority level.

	3.3.1
	Extended Planned Outage Duration.    The Extended Planned Outage Duration defines the maximum allowable time, in hours and
minutes, that the usTLD Administrator is allowed to take the usTLD Services out of service for extended maintenance. Extended Planned Outages are planned in advance and the Registrar Community is
provided warning ahead of time. Extended Planned Outage periods are in addition to any Planned Outages during any Service Level Measurement Period. This Performance Specification, where applicable,
has a Service Level Measurement Period based on a calendar quarter. The Extended Planned Outage Duration for the Core Services is as follows:

	3.3.1.1
	Extended
Planned Outage Duration—SRS = 18 hours (1080 minutes) per calendar quarter;

	3.3.1.2
	Extended
Planned Outage Duration—Nameserver =(no planned outages allowed); and

	3.3.1.3
	Extended
Planned Outage Duration—Whois = 18 hours (1080 minutes) per calendar quarter.

	3.3.2
	Extended Planned Outage Timeframe.    The Extended Planned Outage Timeframe defines the hours and days in which the
Extended Planned Outage can occur. The Extended Planned Outage Timeframe for the Core Services is as follows:

	3.3.2.1
	Extended
Planned Outage Timeframe—SRS = 1201-0800 UTC Saturday or Sunday;

	3.3.2.2
	Extended
Planned Outage Timeframe—Nameserver =(no planned outages allowed); and

	3.3.2.3
	Extended
Planned Outage Timeframe—Whois = 1201-0800 UTC Saturday or Sunday. 

H-47

 

	3.3.3
	Extended Planned Outage Notification.    The usTLD Administrator will notify all of its registrars of any Extended Planned
Outage. The Extended Planned Outage Notification Performance Specification defines the number of days prior to an Extended Planned Outage that the usTLD Administrator will notify its registrars. The
Extended Planned Outage Notification for the Core Services is as follows:

	3.3.3.1
	Extended
Planned Outage Timeframe—SRS = 4 weeks;

	3.3.3.2
	Extended
Planned Outage Timeframe—Nameserver =(no planned outages allowed); and

	3.3.3.3
	Extended
Planned Outage Timeframe—Whois = 4 weeks.

	3.4
	Processing Time.    Processing Time is an important measurement of transaction-based services like those provided by the
usTLD System. The first three Performance Specifications, Service Availability, Planned Outages and Extended Planned Outages, measure the amount of time that the service is available to its users.
Processing Time measures the quality of that service. 

Processing
Time refers to the time that the usTLD Administrator receives a request and sends a response to that request. Since each of the usTLD Services has a unique function the Performance
Specifications for Processing Time are unique to each of the usTLD Services. For example, a Performance Specification for the Nameserver is not applicable to the SRS and Whois, etc. Processing Time
Performance Specifications are a C2 priority level. 

Processing
Time Performance Specifications have a monthly Service Level Measurement Period and will be reported on a monthly basis. The usTLD Administrator will log the processing time for all of the
related transactions, measured from the time it receives the request to the time that it returns a response. 

	3.4.1
	Processing
Time—Add, Modify, Delete = 3 seconds for 95%

	3.4.1.1
	Processing
Time—Add, Modify, and Delete is applicable to the SRS as accessed through the XRP protocol. It measures the processing time for add, modify, and delete
transactions associated with domain names, nameserver, contacts, and registrar profile information.

	3.4.1.2
	The
Performance Specification is 3 seconds for 95% of the transactions processed. That is, 95% of the transactions will take 3 seconds or less from the time the usTLD
Administrator receives the request to the time it provides a response.

	3.4.2
	Processing Time—Query Domain = 1.5 seconds for 95%

	3.4.2.1
	Processing
Time—Query Domain is applicable to the SRS as accessed through the XRP protocol [defined in
Appendix     of the usTLD Agreement]. It measures the processing time for an availability query of a specific domain name.

	3.4.2.2
	The
performance specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time the usTLD Administrator
receives the query to the time it provides a response as to the domain name's availability.

	3.4.3
	Processing Time—Whois Query = 1.5 seconds for 95%

	3.4.3.1
	Processing
Time—Whois Query is only applicable to the Whois. It measures the processing time for a Whois Query. 

H-48

 

	3.4.3.2
	The
Performance Specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time the Whois receives a query
to the time it responds.

	3.4.4
	Processing
Time—Nameserver Resolution = 1.5 seconds for 95%

	3.4.4.1
	Processing
Time—Nameserver Resolution is only applicable to the Nameserver. It measures the processing time for a DNS query.

	3.4.4.2
	The
Performance Specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time Nameserver receives the DNS
query to the time it provides a response.

	3.5
	Update Frequency.    There are two important elements of the usTLD System that are updated frequently and are used by the
general public: Nameserver and Whois. Registrars generate these updates through the SRS. The SRS then updates the Nameserver and the Whois. These will be done on a batch basis. Update Frequency
Performance Specifications are a C3 priority level. 

The
committed Performance Specification with regard to Update Frequency for both the Nameserver and the Whois is 15 minutes for 95% of the transactions. That is, 95% of the updates to the Nameserver
and Whois will be effectuated within 15 minutes. This is measured from the time that the registry confirms the update to the registrar to the time the update appears in the Nameserver and Whois.
Update Frequency Performance Specifications have a monthly Service Level Measurement Period and will be reported on a monthly basis.

	3.5.1
	Update Frequency—Nameserver = 15 minutes for 95%.

	3.5.2
	Update Frequency—Whois = 15 minutes for 95%. 

H-49

 

	 
	 	Performance Specification Description
	 	SRS
	 	Nameserver
	 	Whois

	1	 	Service Availability	 	99.9% per calendar month	 	99.999% per calendar year	 	99.95% per calendar month
	2	 	Processing Time—Add, Modify, Delete	 	3 sec for 95%	 	NA	 	NA
	3	 	Processing Time—Query Domain	 	1.5 sec for 95%	 	NA	 	NA
	4	 	Processing Time—Whois	 	NA	 	NA	 	1.5 sec for 95%
	5	 	Processing Time—Nameserver Resolution	 	NA	 	1.5 sec for 95%	 	NA
	6	 	Update Frequency	 	NA	 	15 min for 95%	 	15 min for 95%
	7	 	Planned Outage—Duration	 	8 hrs per calendar month	 	not allowed	 	8 hrs per calendar month
	8	 	Planned Outage—Timeframe	 	1201 - 0800 EST Sun	 	not allowed	 	1201 - 0800 EST Sun
	9	 	Planned Outage—Notification	 	3 days	 	not allowed	 	3 days
	10	 	Extended Planned Outage—Duration	 	18 hrs per calendar quarter	 	not allowed	 	18 hrs per calendar quarter
	11	 	Extended Planned Outage—Timeframe	 	1201 - 0800 ETC Sat or Sun	 	not allowed	 	1201 - 0800 ETC Sat or Sun
	12	 	Extended Planned Outage—Notification	 	28 days	 	not allowed	 	28 days

H-50

  

 
 

Exhibit H    
    
    SERVICE LEVEL AGREEMENT    
    

	1.
	Definitions.    Capitalized terms used herein and not otherwise defined shall have the definitions ascribed to them in
Exhibit G to the usTLD Administrator-Registrar Agreement.

	2.
	Credits.    If usTLD Administrator fails to meet the Performance Specifications defined in Exhibit G ("Service Level
Exception" or "SLE"), usTLD Administrator shall pay in the aggregate to the Registrar Community a credit according to the tables provided below ("Applicable Credit"). Each Registrar shall only be
entitled to a fraction of the Applicable Credit. Such fractions of the credit specified in the tables to be paid to any individual Registrar will be calculated based upon the number of domain names
that such Registrar added to the usTLD Administrator during the Service Level Measurement Period compared to the total number of domain names added to the usTLD Administrator by all Registrars during
the Service Level Measurement Period in which the SLE occurred. The credit due to Registrar may be paid as an offset to registrations and other fees owed to usTLD Administrator by Registrar. All
credits shall be paid in U.S. Dollars. The following Credit Lookup Matrix indicates the corresponding credit table for which the credits defined in this Appendix will be levied. 

 
 

CREDIT LOOKUP MATRIX    
    

	 
	 	Performance Specification Description
	 	SRS
	 	Nameserver
	 	Whois

	1	 	Service Availability	 	Table C1a	 	Table C1b	 	Table C1a
	2	 	Processing Time—Add, Modify, Delete	 	Table C2	 	NA	 	NA
	3	 	Processing Time—Query Domain	 	Table C2	 	NA	 	NA
	4	 	Processing Time—Whois	 	NA	 	NA	 	Table C2
	5	 	Processing Time—Nameserver Resolution	 	NA	 	Table C2	 	NA
	6	 	Update Frequency	 	NA	 	Table C3	 	Table C3
	7	 	Planned Outage—Duration	 	Table C4b	 	NA	 	Table C4b
	8	 	Planned Outage—Timeframe	 	Table C4a	 	NA	 	Table C4a
	9	 	Planned Outage—Notification	 	Table C4a	 	NA	 	Table C4a
	10	 	Extended Planned Outage—Duration	 	Table C4b	 	NA	 	Table C4b
	11	 	Extended Planned Outage—Timeframe	 	Table C4a	 	NA	 	Table C4a
	12	 	Extended Planned Outage—Notification	 	Table C4a	 	NA	 	Table C4a

        If
one or more SLEs occurs as the direct result of a failure to meet a Performance Specification in a single credit class, usTLD Administrator shall be responsible only for the credit
assessed for the credit class which is the proximate cause for all directly related failures. 

        The
following tables identify total Registrar Community credits due for SLEs in the four credit classes C1-C4. Notwithstanding the credit levels contained in these tables, the total
credits owed by usTLD Administrator under this Agreement shall not exceed $30,000 USD monthly and $360,000 USD annually. The credits contained in Tables C1a-C4 represent the total credits that may be
assessed in a given SLR category in one Service Level Measurement Period. 

	2.1
	C1 Credit Class—If availability of C1 Credit Class components or systems does not meet C1 Performance Specifications in any
given Service Level Measurement Period described in the 

H-51

 

Performance
Specification Matrix in Exhibit G, usTLD Administrator will credit the Registrar Community according to the tables (which amount will be credited to the Registrar on a proportional
basis as set forth above). 

 
 

Table C1a    
    

	SLE
 
	 	< 30 sec.'s
	 	30-60 sec.'s
	 	1-2 min.'s
	 	2-10 min.'s
	 	10-30 min.'s
	 	over 30 min.'s

	Monthly Credit to Registrar Community	 	$	750	 	$	1,500	 	$	2,500	 	$	3,750	 	$	5,000	 	$	6,000

C1a Availability Example:    In a given measurement period, the SRS Availability is 99.87%, which equates to 52 minutes of unplanned downtime.
The usTLD Administrator's Performance Specification for SRS Availability is 99.9%, or 43 minutes of downtime. The Service Level Exception, therefore, is 9 minutes (52-43 minutes), the
difference between the Performance Specification and the actual measured performance. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C1a. In Table C1a, the time interval
(2-10 minutes) has a corresponding credit of $3,750 USD to be paid to the Registrar Community. 

 
 

Table C1b    
    

	SLE
 
	 	< 10 min.'s
	 	10-30 min.'s
	 	30-60 min.'s
	 	1-2 hours
	 	2-4 hours
	 	over 4 hours

	Annual Credit to Registrar Community	 	$	7,500	 	$	15,000	 	$	25,000	 	$	35,000	 	$	50,000	 	$	75,000

C1b Availability Example:    In a given Service Level Measurement Period, the measured Nameserver Availability is 99.990% over a twelve
(12) month period, which equates to 52 minutes of downtime. The usTLD Administrator's Performance Specification for Nameserver Availability is 99.999%, or 5 minutes of downtime per calendar
year. The Service Level Exception, therefore, is 47 minutes (52-5 minutes), the difference between the Performance Specification and the actual measured performance. From the Credit Lookup
Matrix, we see the relevant SLA is found in Table C1b. In Table C1b, the time interval (30-60 minutes) has a corresponding credit of $25,000 USD to be paid to the Registrar Community. 

	2.2
	C2 Credit Class—If processing time for C2 Credit Class services does not meet C2 Service Levels in any given Service Level
Measurement Period, usTLD Administrator will credit the Registrar Community according to the following table (which amount will be credited to the Registrars on a proportional basis as set forth
above). 

 
 

Table C2    
    

	SLE
 
	 	< 2 sec.'s
	 	2-5 sec.'s
	 	5-10 sec.'s
	 	10-20 sec.'s
	 	20-30 sec.'s
	 	over 30 sec.'s

	Monthly Credit to Registrar Community	 	$	375	 	$	750	 	$	1,500	 	$	3,500	 	$	4,000	 	$	7,500

C2 Processing Example:    The Performance Specification for Processing Time for Add, Modify, and Delete is 3 seconds or less for 95% of the
transactions. In a given Service Level Measurement Period 7% of the transactions are greater than 3 seconds. The 5% of those transactions with the longest processing times are not subject to the SLE
calculation 

H-52

 

(3 seconds
for 95%). The SLE is calculated using the average processing time for the 2% of the transactions that are subject to the SLE. If there were 1,000 transactions and they took a total
of 4,000 seconds the average is 4 seconds. That generates an SLE of 1 second (4 seconds-3 seconds). From the Credit Lookup Matrix, we see the relevant SLA is found in Table C2. In Table C2, the SLE
time interval (< 2 seconds) has a corresponding credit $375 USD to be paid to the Registrar Community. 

	2.3
	C3 Credit Class—If update frequency measurements of C3 Credit Class components or systems do not meet C3 Service Levels in
any given Service Level Measurement Period as described in the Performance Specification Matrix in Exhibit G, usTLD Administrator will credit the Registrar Community according to the following
tables (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C3    
    

	SLE
 
	 	< 30 sec.'s
	 	30-60 sec.'s
	 	1-2 min.'s
	 	2-10 min.'s
	 	10-30 min.'s
	 	over 30 min.'s

	Monthly Credit to Registrar Community	 	$	188	 	$	375	 	$	625	 	$	938	 	$	1,250	 	$	1,500

C3 Update Frequency Example:    In a given Service Level Measurement Period, 95% of the updates to the Nameserver take 24 minutes or less to
complete. The corresponding usTLD Administrator's Performance Specification is 15 minutes for 95% of the updates. The SLE, therefore, is 9 minutes. From the Credit Lookup Matrix, we see the relevant
SLA is found in Table C3. The SLE time interval (2-10 minutes) has a corresponding credit of $938 USD to be paid to the Registrar Community. 

	2.4
	C4 Credit Class—If usTLD Administrator fails to comply with C4 Credit Class category Performance Specifications, usTLD
Administrator will credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C4a    
    

	SLE
 
	 	Any

	Monthly Credit to Registrar Community	 	$	500

C4a Planned Outage Notification Example:    In each instance the usTLD Administrator fails to meet the Performance Specifications for
Notification and Timeframe related to Planned Outages and Extended Planned Outages, the usTLD Administrator is subject to the credit in Table C4a. For example, the usTLD Administrator informs the
Registrar Community that it will initiate a Planned Outage of the SRS on the next calendar Sunday (five (5) days advance notice). The corresponding usTLD Administrator's Performance
Specification is 28 days 

H-53

 

notice.
From the Credit Lookup Matrix, we see the relevant SLA is found in Table C4a. This results in a credit of $500 USD to be paid to the Registrar Community. 

 
 

Table C4b    
    

	SLE
 
	 	< 1 hour
	 	1-2 hours
	 	2-4 hours
	 	4-6 hours
	 	6-10 hours
	 	over 10 hours

	Monthly Credit to Registrar Community	 	$	300	 	$	750	 	$	1,200	 	$	2,500	 	$	3,500	 	$	4,000

C4b Planned Outage Example:    In a given Service Level Measurement Period, the actual duration of a planned outage is 11 hours and 20
minutes for the SRS. The corresponding usTLD Administrator's Performance Specification is 8 hours per month for the SRS. The SLE, therefore, is 3 hours and 20 minutes. From the Credit
Lookup Matrix the relevant SLA is found in Table C4b. The SLE time interval (2-4 hours) has a corresponding credit of $1,200 USD to be paid to the Registrar Community. 

	3.
	Receipt of Credits.    In order for Registrars to claim credits, the following procedure must be followed:

	3.1
	usTLD
Administrator shall perform the required measurements in order to obtain the total credits associated with the applicable Service Level Measurement Period. Such measurements and
associated documentation shall be delivered by e-mail to each of the Registrars in the Registrar Community. Such notice shall also include the total credit (if any) to be paid to the
Registrar Community as a result of any outages.

	3.2
	Receipt
of Credit—When the above steps have been completed, the usTLD Administrator shall enter in each Registrar's account balance the amount of credit (if applicable)
that can be used immediately toward registrations in the Registry. 

4.     Obligations.  

	4.1
	Except
in the case of cross-network nameserver performance (which is not a subject of this Service Level Agreement), usTLD Administrator will perform monitoring from internally
located systems as a means to verify that the conditions of the SLA are being met.

	4.2
	Upon
written request, and at the sole expense of the requesting Registrar(s), usTLD Administrator will retain an independent third party to be selected by usTLD Administrator with the
consent of the Registrar(s). The Registrar may, under reasonable terms and conditions, audit the reconciliation records for the purposes of verifying measurements of the Performance Specifications.
The frequency of these audits will be no more than once yearly during the term of the agreement between usTLD Administrator and the Registrar.

	4.3
	usTLD
Administrator's obligations under this SLA are waived during the first 120 days after the date that the expanded space of the usTLD goes "live." ("Commencement of Service
Date").

	4.4
	A
Registrar must report each occurrence of alleged occasion of Unavailability of Core Services to the usTLD Administrator customer service help desk in the manner required by the
usTLD Administrator (i.e., e-mail, fax, telephone) in order for an occurrence to be treated as Unavailable for purposes of the SLE.

	4.5
	In
the event that the Core Services are Unavailable to an individual Registrar, usTLD Administrator will use commercially reasonable efforts to re-establish the affected
Core Services for such Registrar as soon as reasonably practicable. In the event that the 

H-54

 

Unavailability
of Core Services affects all Registrars, the usTLD Administrator is responsible for opening a blanket trouble ticket and immediately notifying all Registrars of the trouble ticket
number and details. 

	4.6
	Both
Registrar and the usTLD Administrator agree to use reasonable commercial good faith efforts to establish the cause of any alleged Core Services Unavailability. If it is mutually
determined to be a usTLD Administrator problem, the issue will become part of the Unplanned Outage minutes.

	4.7
	The
usTLD Administrator will use commercially reasonable efforts to restore the critical systems of the Core Services within 24 hours after the termination of a force majeure
event and restore full system functionality within 48 hours after the termination of a force majeure event. Outages due to a force majeure will not be considered Service Unavailability.

	4.9
	Incident
trouble tickets must be opened within a commercially reasonable period of time. 

5.     Miscellaneous.  

	5.1
	This
Service Level Agreement is independent of any rights, obligations or duties set forth in the usTLD Administrator Agreement. In the event of any conflict between the terms and
conditions of this Agreement and the usTLD Administrator Agreement, the usTLD Administrator Agreement shall control. 

H-55

   I. Start-up Phase Policies  

        During the start-up phase of the expanded usTLD, NeuStar will establish a set of important policies designed to improve and
maintain the integrity of the usTLD by protecting important intellectual property rights and ensuring that the usTLD serves the U.S. Internet community.

HIGHLIGHTS  

	•
	NeuStar's start-up policies will ensure a secure, stable and controlled introduction of the expanded usTLD.

	•
	Rather than prescribe policy, NeuStar will seek to develop policy in partnership with the usTLD community.

        During
the expansion of the usTLD, the new administrator will face a number of serious issues similar to those encountered by new gTLDs. These issues include, for example, concerns
regarding cybersquatting, the expected "rush" of registrations at the opening of the expanded TLD space, and the need to enforce registration restrictions such as the requirement in the usTLD that
registrants be residents of the US. The absence of well structured plans to address such issues indicates a likely inability of the would be administrator to handle the complex process of opening to
the public a new TLD space such as the expanded usTLD, and threatens the integrity and ultimately the success of the usTLD. NeuStar has a strong understanding of these issues and has designed
start-up policies and procedures to ensure that the integrity of the usTLD is maintained and improved during the critical start-up phases of the expanded usTLD. 

        NeuStar
will implement the following policies and procedures relevant to the start-up phases of the expanded usTLD: 

	•
	Sunrise Policy—NeuStar will implement a sunrise policy to allow trademark holders and applicants to register
their valuable marks in the usTLD prior to the expanded usTLD being opened to the general public. This process is modeled after the sunrise policies adopted by some of the new ICANN sponsored gTLDs.
The sunrise policy is discussed in detail in Section B.3.3 of this proposal.

	•
	usTLD Dispute Resolution Policy (usDRP)—NeuStar understands that to ensure that the usTLD serves the usTLD
community fairly and with a high degree of integrity, strong dispute resolution procedures must be implemented to address concerns and issues under the administrator's policies. Following on the
significant work by ICANN, NeuStar has developed effective, efficient, and fair dispute mechanisms for the usTLD. The usTLD dispute resolution policies are discussed in detail in Section B.3.3
of this proposal.

	•
	US Nexus Requirement—NeuStar will establish a mechanism to ensure that the usTLD serves the US Internet
community. Registrants will be required to show that they are either residents in the US or have a bona fide presence in the US. The US Nexus Requirement is discussed in detail in Section B.3.1
of this proposal.

	•
	Land Rush Process—NeuStar's Land Rush process will ensure that the initial "rush" for name registrations for
valuable second level domains expected when the expanded usTLD is opened for public registration does not overload our system. The US Nexus Requirement is discussed in detail in Section J of
this proposal. 

        Exhibit I-1
illustrates NeuStar's carefully phased and controlled start-up process. 

        NeuStar's
policy approach is thorough and fair, yet is not heavy-handed. The start-up policies outlined herein are the minimum policies required for a secure and stable
start-up of the expanded 

I-1

 

usTLD.
In major part, policy in the usTLD will be developed in collaboration with the usTLD community at large. 

        [Exhibit I-1:
Graphic Design] 

I-2

 

J. Registration Process  

        To ensure rapid acceptance and vigorous marketing of the usTLD by existing and future registrars, as well as to introduce strong
competition and innovation, NeuStar will implement a stable, straightforward, and familiar initial registration process for the usTLD domain name based upon the proven business model supported by
ICANN.

	•
	NeuStar will follow proven start-up and past start-up registration processes used for new gTLDs to ensure stable and robust
name registration in the expanded usTLD

	•
	The Sunrise Program will provide trademark holders the opportunity to protect their valuable marks

	•
	NeuStar's Land Rush Implementation provides a strong, single solution to the complex problem of heavy registration traffic during the
start-up of the new domain space

	•
	NeuStar's proven ICANN-like registry/registrar name registration model will encourage rapid acceptance of the expanded usTLD, driving use
and innovation of the space

        In
many ways, the expansion and enhancement of the usTLD is not unlike the introduction of a new top level domain. Therefore, a new usTLD administrator must take into account the same
sets of issues and potential problems relevant to the introduction of a new gTLD. To address these issues and concerns, the chosen usTLD administrator will need a high level of experience in the DNS
space, as well as significant resources to ensure stability, integrity, and accuracy of operations in a very dynamic start-up and transition process. NeuStar meets these requirements and
has developed strong solutions for the usTLD expansion. 

        Drawing
on the experience and successes of the shared registry business model developed in the context of the gTLDs, NeuStar will implement for the usTLD a clear and familiar process for
domain name registration. 

        NeuStar's
expansion of the usTLD will comprise a measured, controlled development of the usTLD consistent with the growth and development of the DNS as a whole. Thus, the expanded usTLD
registration processes will be broken into three stages: 

	1.
	The
Sunrise Program,

	2.
	The
Land Rush Implementation, and

	3.
	Post
Start-up Registration Process. 

Sunrise Program  

        The Sunrise program will address the important issue of intellectual property rights in names that will become available in an expanded usTLD space. NeuStar
agrees that it is critical to have a mechanism for dealing with the problem of "cybersquatting." NeuStar's Sunrise Program is described in detail in Section I of this proposal. 

Land Rush Implementation  

        Subsequent to the Sunrise program for intellectual property holders, the next issue to address is the "Land Rush" phenomenon during a TLD's initial
start-up period. This phenomenon, at its most basic level, describes an expected rush of registration requests as potential registrants attempt to capture the most valuable, from their
perspective, names in the usTLD space. The expanded usTLD must be introduced in a manner that manages the technical system issues associated with extremely high traffic volumes. In addition, domain
names must be allocated in an entirely impartial manner so that no party or parties may claim special privileges in registering a domain name in the expanded 

J-1

 

usTLD
space. The principle of neutrality should be the cornerstone of the registry's operation, and it is even more critical during the start-up period. While it is a given that this
principle should underpin the registry's operation in general, this is especially true during the start-up period. 

        It
is extremely difficult to accurately predict the initial volume of registration requests. While some basic assumptions will assist in defining boundaries, any solution to the
start-up issues must take into account a degree of uncertainty and be able to provide contingencies if demand greatly exceeds predictions. Thus, Land Rush represents a significant issue
that the new administrator must deal with immediately upon award by DOC. Indeed, NeuStar submits that the absence of a well-reasoned and comprehensive Land Rush solution in a party's
quotation is an indicator of probable failure of transition and implementation after award. 

        There
are several possible ways to approach the issues raised by the Land Rush phenomenon: 

	1.
	Attempt to compensate for increased volumes with hardware—This approach has several shortcomings, not the least of which is
an exorbitant cost that would seriously impact the price competitiveness of registry services. In addition, it does not take into account the high degree of uncertainty in estimating initial volumes.

	2.
	Use higher price points to control demand—Higher price points would have a significant impact on the perceived fairness of
the process since they would restrict access to registrations—an outcome incompatible with the public resource nature of the usTLD. In addition, it would involve an arbitrary allocation of
price points to domain names.

	3.
	Moderate registrations via a start-up-specific policy—In this scenario, lists of domain names are
submitted to the registry by registrars. These lists are then randomized and processed to create a list containing only one application for each name submitted (i.e., the process would randomly select
one of a number of duplicate requests for a given name, such as "neustar.us"). This initial randomization and processing prevents registrars or registrants from attempting to "game" the Land Rush
system by submitting large numbers of duplicate registration requests to increase the chance that they will be selected as the name registrant in the final random processing. The registrar lists are
then combined into a single file and again randomized. Names are selected for registration from this final list. The strength of this solution is that it will provide an effective means of moderation
regardless of the size of registration volumes. In effect, it will function efficiently whether the demand for registrations is ten or ten million. Moreover, the Land Rush solution ensures complete
impartiality in domain name allocation at the registry level. Hence, this is the solution proposed by NeuStar. 

An Overview of the Land Rush Solution  

        As demonstrated in Exhibit J-1, the Land Rush process will provide an effective and fair method
for ensuring the stability of the new TLD and the Internet during the initial registration period. 

        Phase 1: Communication of the Process—To ensure the smooth implementation of the start-up procedures, NeuStar will
undertake a proactive educational campaign with registrars. This will involve distribution of information kits by e-mail as well as personal contact from the registry customer support
staff and account managers. In this way, registrars will have the opportunity to completely understand the procedures and processes involved in the Land Rush solution. Fortunately, many registrars
already are familiar with this process from the introduction of the new ICANN-sponsored gTLDs. 

        Phase 2: Submission of Registration Lists—Each accredited registrar will provide a list of domain names and registration
details. There will be no minimum or maximum limit for the lists. The registration files will be submitted via a secure transport mechanism before a specified closing time for first submissions.
Registration lists cannot be modified until the first batch is processed and completed. 

J-2

 

        [Exhibit J-1:
Graphic Design] 

        Phase 3: Randomization of Registrar Submitted Lists—The lists submitted by each registrar will be individually randomized and
processed to eliminate duplicate domain name registration requests (e.g., four different parties request unclesam.us; one of the requests will be selected, and the others will be deleted from the
list). 

        Phase 4: Compilation and Randomization of Registrar Lists—After initial processing, the entire set of registrar lists will be
combined into a single processing file and randomized. 

        Phase 5: Processing of Randomized List—Once the registration system is activated, a domain name will be randomly selected from
the processing list. This domain name will be entered into the registry database. This process repeats until the entire list has been processed. If a chosen domain name is unavailable, then another
name is chosen at random from the list until one of the following occurs: 

	•
	A
successful registration is complete, or

	•
	The
registrar has no more available names on its list. 

        Phase 6: Results—At the end of the list processing, the results of registrations are returned to the registrar. 

        Phase 7: Commencing Normal Registration Procedures—After returning the results of the Land Rush process to the registrars, the
registrars and the public will be advised that the registry will be activated on April 1, 2002 to accept new registrations directly into the registry. 

The Benefits of NeuStar's Land Rush Implementation Approach  

        Incorporating the Land Rush solution into our overall solution provides the following benefits: 

	•
	Neutral
and impartial allocation of domain names during the start-up period,

	•
	Effective
management of technical resource issues,

	•
	Nondiscriminatory
application process for all parties of new domain names,

	•
	Scalable
and effective support for any volume of registrations,

	•
	Inexpensive
solution implementation, and

	•
	Affordable
registration for all members of the Internet community. 

        The
Land Rush solution will moderate the anticipated volume of registration requests without having any significant impact on fairness, stability, or system resources. The NeuStar
solution is fully scalable so that stability is ensured, even if registration volumes greatly exceed predictions. 

Registrant Post Start-up Registration Process and Requirements  

        NeuStar's plan to introduce changes in the usTLD that are designed to bring the usTLD into the global Internet infrastructure mandates that such changes be
consistent wherever possible with the structures already in place in the global Internet community. Such consistency is required to encourage rapid acceptance of the expanded usTLD space by the
Internet community, especially the registrar industry. Strong competition and the rapid uptake of the usTLD will drive the kind of use and innovation of the usTLD desired by the DOC and NeuStar as an
applicant for administrating the space. 

        Therefore,
following the Land Rush period of name registration, NeuStar intends to implement the ICANN registry/registrar business model for the expanded usTLD. This model has proven to
be 

J-3

 

highly
successful yet sufficiently flexible to support any modifications necessary to address specific usTLD requirements. This process will apply also to direct registrations performed by NeuStar in
the locality-based usTLD. 

        In
this model, the application requires the registrants to provide the necessary registration information through registrars who will have a functional interface with the registry.
Registrants will be asked to provide the owner's contact information along with contact information from the administrative, technical, and billing contacts. They will be asked to provide the name and
IP address for a primary and secondary nameserver and to certify that these nameservers are located within the United States to ensure compliance with the usTLD Nexus Requirement. 

        In
addition to these items (which are already required for registrations in the existing generic TLDs, with the exception of the nameserver Nexus certification), the registrant will be
asked to represent, warrant, and acknowledge that it meets the Nexus Requirement. The Nexus Requirement is set forth in Section B.3.1. Prior to acceptance of a registration, the information
provided will be checked to verify that the contact addresses and nameserver addresses meet the Nexus Requirement. If they do not, the registration will be held for a period of 30 days and the
potential registrant will be given an opportunity to prove compliance with the Nexus Requirement. Failure to demonstrate compliance will result in cancellation of the registration. 

Nexus Requirement Enforcement  

        NeuStar will require that registrars obtain from the registrant certification that it meets the Nexus Requirement and the manner in which the requirement is met
(i.e., citizenship, residence, or bona fide
presence). In addition, NeuStar will check selected data provided by the potential registrant to ensure that the contact information establishes the proper US Nexus (e.g., a valid U.S. ZIP code is
provided). NeuStar will also check the information provided for the primary and secondary nameservers identified by the potential registrant. The required certification will form the basis for the
deletion of a registered name through a usTLD dispute resolution process if the information provided is false. A registration will not be made without a completed certification. The dispute resolution
process is discussed in Section B.3.1 

Appeal Process  

        To ensure fairness and neutrality in operations, any individual who is denied a registration will be given an opportunity to ask the usTLD Administrator to review
its decision and also to demonstrate that the requested name meets usTLD domain registration requirements. Upon an adequate showing, the individual will be permitted to register the requested name. As
a general matter, however, NeuStar does not intend to deny initial registrations unless a given registration does not meet the Nexus Requirement as discussed above. 

Registration Cancellation  

        As discussed above, third parties will have the opportunity to challenge registrations, for example for lack of proper US Nexus, through the usTLD Dispute
resolution process discussed in Section B.3.3 

J-4

   K. Outreach to Current Locality-based usTLD Users  

        NeuStar believes that community involvement must be the core of any public service operation. Therefore, NeuStar will develop
user-friendly, flexible, and effective mechanisms for ensuring input and coordination of the current locality-based usTLD users.

HIGHLIGHTS  

	•
	Designed to ensure that current users have a voice in the future success of the usTLD space

	•
	User-friendly mechanisms enable open discussions and facilitate progress

        As
is noted in Section B.4.4, NeuStar is aware that as a result of the comparative complexity of the namespace and the lack of coordination and marketing for the usTLD, the
locality-based usTLD has not attracted a high level of domain name registration activity and remains underpopulated in comparison with other ccTLDs. In particular, almost no effort has been made to
reach out to locality-based users and stakeholders to further develop and improve the space. 

        NeuStar
has a strong legacy of coordinating complex groups of users in the industries that it serves. Successful administration of public resources, whether they are telephone numbers or
domain names, requires strong awareness of constituencies and their needs. NeuStar intends to establish target communication mechanisms, including e-mail listservs, chat services, and
other Internet-based services. In addition, NeuStar will utilize traditional customer outreach, such as user group
meetings, user support representatives, and other support services to maintain close relationships with usTLD stakeholders. These forums will be tailored to allow users and the public to suggest or
recommend additional policies or procedures for the usTLD. 

        To
begin this process, NeuStar will leverage the six-month compliance report process, discussed in detail in Section B.4.5, to develop a strong understanding of
stakeholder desires and concerns and to identify the best way to communicate with each constituency group. 

        Coordination
of all usTLD outreach efforts will ultimately be implemented and developed under the auspices of the usTLD Policy Advisory Council. This council will be very important to
the ongoing development of usTLD policy and public outreach. The structure and duties of this council, as well as the detailed outline of our basic outreach plan, are discussed in detail in
Section B.3.5. 

K-1

   L. Funding for the usTLD  

        Past financial performance, the ability to secure capital, and current financial commitment to the development of a next generation
Internet registry architecture position NeuStar to fully fund the usTLD at no cost to the US government and position it for a low cost to facilitate registrant adoption by the US
public.

HIGHLIGHTS  

        All stakeholders receive best value as a result of: 

	•
	NeuStar's financial stability that ensures full funding of the administration of the usTLD

	•
	NeuStar's offering domain name registrations for the usTLD at highly competitive market prices

        The
administration of the usTLD is a commercial service offering to the United States at large and should therefore be at no cost to the US government. NeuStar complies with the request
in the RFQ that the value of the purchase order related to the coordination and management of the usTLD is $0.00 [cost] to the Department of Commerce, or any other U.S.
government body that would assume control of the contract, as shown in NeuStar's Request For Quotation Standard Form 18 (Rev. 6/95) in the first section of this proposal. 

NeuStar's Financial Stability  

        NeuStar, a privately held corporation, has sufficient capital to fully fund the efforts to coordinate and manage the usTLD outlined herein. As demonstrated in the
attached financial statements, NeuStar was net income positive for the financial year 2000. The original lines of business are net income and cash flow positive going forward, and have seen
substantial growth—[***]. These statements illustrate the maturity of the existing registry businesses we have been operating for over 5 years. 

        NeuStar
recently closed on approximately $50 million in equity capital. This capital will fund the design, implementation, and operation of a next generation Internet registry. In
addition, NeuStar has a very strong balance sheet and is in the process of securing over $50 million of debt financing, the majority of which will be secured by long-term
receivables (a high quality form of security). 

        In
addition to its own fund raising capabilities, NeuStar continues to receive the on-going financial support of its world-class investment partners. NeuStar's majority
owner, Warburg Pincus, is one of the largest private equity firms in the United States. Please refer to the letter immediately following this section from Warburg Pincus that outlines its commitment
to the success of NeuStar's business. 

Registry Fees  

        To ensure that the usTLD is promoted, successful, and that the best value is received for all constituencies, NeuStar proposes competitive market rates for its
next generation registry services related to the coordination and management of the usTLD. Because NeuStar is able to leverage the current Internet registry architecture, many development costs are
effectively shared, and offset the incremental spend required for the usTLD, enabling NeuStar to offer a competitive market price for registrations. 

Delegee and Registrar Fees  

        In its role as administrator of the usTLD, NeuStar will be responsible for accreditation and management of commercial registrars. Currently, no ICANN-accredited
registrars are eligible for selling second-level registrations for the usTLD. The administrator will have the responsibility of establishing criteria, reviewing applications, and integrating
accredited registrars to the registry, and managing on-going relations. 

L-1

 

        NeuStar
will follow a similar model to ICANN for selecting registrars and establishing fees to cover administrative expenses. The fees will not exceed those enumerated in the table in
the first year; in the subsequent years, the fees will not increase by more than 10% annually. NeuStar will not charge for the registry interface or the operational testing and evaluation (OT&E). All
fees are presented in the table below: 

 Registrar Fees  

	Application Fee	 	$1,000 (one time)
	XRP License	 	$0
	OT&E	 	$0
	Annual Fixed Fee	 	$1,250 (per year)
	Variable Fee	 	$0.05 (per registration)

        Moreover,
these fees are designed to cover administrative expenses that are directly attributed to usTLD registrar activity, and are not intended to provide an additional revenue stream
for the registry. These fees are implemented to keep the registrant price at a competitive level, further promoting the enhanced utility of the space and driving market adoption. 

Registration Fees (Undelegated Localities)  

        As instructed, the usTLD administrator will act as the registrar for undelegated localities in the locality-based space. In this capacity, and in this space only,
NeuStar will provide direct registration services to the registrant. NeuStar will have a discrete registrar function, one that utilizes standard protocols and interfaces with the registry as all other
registrars. Were NeuStar to offer these domains at the same price per registration as those charged to delegees and usTLD accredited registrars, it would place NeuStar in a position of under cutting
the registrar market rate for domain names. 

        Based
on the incremental work as a registrar and the core principle of enabling adoption, NeuStar proposes the following competitive market rates: 

 Registration Price  

	Locality-based Domain Name Registration	 	$	15.00

        This
price could also be interpreted as our recommended retail rate for registrars and delegees. While NeuStar will place no enforcement mechanisms that restrict pricing at the registrar
or delegee level, it presents this as a guide. 

Registration Fees (to Registrars)  

        NeuStar will levy domain name registrations fees in a neutral and even-handed manner to all delegees and usTLD-accredited registrars. The domain name
registration fee is applicable to all new registrations in NeuStar's usTLD registry. 

        The
usTLD has a legacy, and that legacy comes with an existing base of domain names entered into the registry under varying terms and conditions. NeuStar recognizes that the existing
delegations and domain names, though they may have been handled in a different manner than what we propose herein, have nonetheless created a name space and implied rights that must be protected.
Those parties with legitimate usTLD domain names today, should continue to hold those names, and NeuStar has no desire to remove names from legitimate holders or to levy additional fees from them for
what was incurred prior to transition. 

L-2

 

        Thus,
NeuStar recognizes a distinction between the past and the present, and will not charge domain name registration fees for those names in the zone file or applications submitted
prior to the submission of this proposal. The distinction will hold only for existing registrations in the locality structure, and all new additions to that structure will be subject to the registry
fee structure presented below. This solution is deemed the best value for the usTLD community as it does not rely on the new, expanded space to subsidize all of the locality space, provides a starting
point for enactment of new policy, and provides a competitive delegee and registrar environment. 

        To
provide the registry service in a neutral and even-handed fashion on an on-going basis, the domain name registration fees must be comparable for all
registrations. By their very nature, domains at any level of hierarchy under the first level require identical levels of technical and operational support. This is NeuStar's rationale behind
consistent pricing for new additions in the locality structure and the expanded space. 

        All
fees will be charged to the Registrars and delegees at the time of registration, based on the term length of the registration. The registration applies to all new or renewed names in
the registry database (i.e., names under management). The total fee in each instance is equal to the term of the new or renewed registration multiplied by the annual registration. All fees will be
debited from the appropriate
registrars account with the registry at the time the registration is entered into the registry database, as discussed in NeuStar's proposal Section J. The registration fee for the expanded
usTLD will be as follows: 

 Price  

	Domain Name Registration	 	$	5.50

        NeuStar
will offer domain name registrations for term lengths, consistent with those available in the gTLD market. Delegees and registrars can offer and select any of the offered
registration terms to registrants during our live operation of the usTLD registry. During the Sunrise period, that period which allows legitimate trade and service mark owners to obtain names
corresponding to their marks, will have a minimum term of registration of 5 years. This will aid in the on-going protection of those trade and service marks. After this period, all
term lengths will be available for registrations. 

        During
the start-up phase of the usTLD, NeuStar will provide enhanced service offerings to further the protection of intellectual property. As discussed in Section B3.3 of
NeuStar's response, we will validate trade and service mark requests against an authoritative database during Sunrise to ensure the validity of those requests. Fees for this enhanced Sunrise phase are
as follows: 

 Price  

	Enhanced Sunrise Fee	 	$	4.50

        This
is a one-time fee, in addition to the standard registration fee, to secure a dot-us domain name during the sunrise phase. The structure is designed to
strengthen the Sunrise process, and further serves to illustrate NeuStar's understanding and willingness to protect intellectual property. NeuStar will not charge any other incremental fees during the
land rush, batch processing phase of start-up. 

        Service
fees for enhanced applications and service offerings are not included in the domain name registration fee, but will be developed in the course of implementation. All will be
competitively priced to suit market needs. 

L-3

 

Optional Hosting Service Fee  

        To minimize administrative burdens on delegated managers, optional hosting relationships can be offered. It is proposed that the usTLD Administrator host resource
records for delegated managers. The price for this hosting service is equivalent to that of a domain name registration, as it is a comparable service to that performed by the Administrator. 

        NeuStar
feels the fees outlined in this section are extremely competitive to the registration prices in the current ccTLD and gTLD markets. These prices are possible because NeuStar is
leveraging existing infrastructure and able to compensate for the increased responsibilities with the coordination and management of the usTLD. NeuStar is investing substantial capital into the
development of a next generation Internet registry that despite having no comparable market, provides competitive pricing to ensure market adoption and use. 

L-4

 

M.    Description of Cost Elements  

        With over five years of experience designing, implementing, and managing mission-critical public resources, NeuStar confidently presents
an illustrative analysis of the costs associated with administration of the usTLD.

HIGHLIGHTS  

	•
	NeuStar will be responsible to ICAAN for all ccTLD fees

	•
	NeuStar will leverage existing infrastructure and experience to reduce expenses

        The
development of a next-generation, thick Internet Registry architecture is a high-priority, fully funded, NeuStar initiative. NeuStar has developed an Internet
registry business plan with the goal of providing a state-of-the-art, innovative, world-class solution that is reliable and scalable and exceeds customer
expectations. NeuStar has analyzed and enumerated the resources required to design, implement, and operate the usTLD registry and has evaluated the market research and general demand for TLDs to
develop a registration forecast. Factors such as economies of scope and scale, interoperability, and feasibility were considered in each of the required operational aspects of the registry as well as
for the innovations NeuStar is proposing. 

        In
the following section, we provide a qualitative review of the various cost elements associated with operating the registry, managing the existing locality structure, establishing and
administering policies,
communicating and working with the Department of Commerce's Contracting Officer and other Internet stakeholders, and developing enhanced service offerings and applications to increase the demand and
utility of the space. 

Expense Estimation  

        NeuStar's technical solution has been designed to meet or exceed the requirements of the RFQ; the costs associated with delivering this service are discussed in
this section. We feel that our past and current experience providing registry services gives us a solid base for generating a resource plan that is realistic and covers all aspects of Registry
operation. NeuStar's strong efforts balance the infrastructure, security, and IP issues with providing the best value for coordination and management of the usTLD. 

        The
costs associated with coordination and management of the usTLD registry are variable with respect to registration volume, SRS queries, Whois queries, innovative designs of the
registry, the number of accredited registrars, modernization of the locality structure, policy formulation, marketing and outreach, and the ability to provide the highest levels of service. NeuStar
has considered each of these determinations when analyzing the costs for each of the resources required to operate a world-class registry. These costs refer to the implementation and transition phases
as well as to the continuing operation of the registry business after launch. The resources required to support the development, operation, and ongoing enhancement of the usTLD were derived by
weighing technical specifications against market demand in the form of anticipated volumes. 

        NeuStar
is currently developing and implementing this registry architecture through its subsidiary, NeuLevel, and will leverage that development design. When analyzing the usTLD
opportunity, proportional allocations are made to develop the stand-alone financial plan (presented in Section N). While there is technical infrastructure to be shared, there are incremental
costs associated with an additional TLD, as well as costs unique to the usTLD. All costs associated with coordination and management of the usTLD are presented below, distinguished by capital
investment and operational spending. 

M-1

 

Capital Investment  

        Hardware estimates are inclusive of all incremental hardware components required for ongoing development and operation of the Registry. Software estimates include
custom software development to
support all registry services described throughout this proposal, as well as third-party software purchases. 

        As
discussed in Section O, Proposed Technical Plan, the physical infrastructure for the registry is a highly scalable design built to operate at high performance and availability
levels. The Enhanced Shared Registry System (SRS) data centers are responsible for the core registry functions of adding, modifying, and deleting domain names to the registry. Nameservers that manage
the resolution of domain names to IP addresses are colocated. The quantity of application, name, Web and Whois servers; routers; load balancers; and relevant networking equipment is driven by the zone
root query volume and size, anticipated demand for usTLD registrations, and the thick registry design. 

        The
software design is an equally large-scale and important facet of the development of a next-generation Internet registry. The custom thick registry architecture that is
being developed will provide enhanced service offerings and applications to be seamlessly integrated into the usTLD space. Additionally, this open architecture will allow for ease in scaling the
registry hardware as query and registration volumes increase. Currently, as active members in the IETF, we are developing an open interface registry-registrar protocol that will be available at no
charge to all usTLD-accredited registrars. In addition to this custom development, NeuStar, as a part of its design, will purchase various third-party software packages. 

        The
capital investment NeuStar is currently making in an Internet registry architecture will not only surpass existing performance and security standards but will serve as a means to
promote competition and increase the number of applications available for the usTLD. 

Operating Expenses  

        The management of the usTLD includes developing policy, coordinating the current delegated managers in the locality space, fulfilling the function of registrar
for undelegated names in the locality-based space, accrediting registrars, managing operational and technical aspects of the registry, maintaining high levels of security, maintaining facilities for
infrastructure and registry employees, providing communication between and within all facets of the registry, enhancing the utility of the space through business development, implementing marketing
and outreach programs, and acting as a representative to the ccTLD constituency within ICANN. Each of these items and the cost drivers are explained in the following paragraphs. 

Functional Areas  

        The coordination and management of the usTLD comprises several roles and functions for NeuStar, including transition and integration of new customers, acting as a
registrar for undelegated names in the locality structure, and operating a near-real-time registry, as well as a product development role. As a part of its corporate
philosophy, NeuStar leverages all corporate functions (i.e., finance and accounting, human resources, legal, media relations, and procurement) across all lines of business. 

        The
generation of the compliance report and recommendations will require unique, individual efforts and external subject matter experts. The scope of this effort includes making direct
contact with existing delegees and subdelegees to determine their current technical and operational capabilities, generating an up-to-date database with their contact
information, and determining how a central administrator can share some of their responsibilities. NeuStar will leverage knowledge of large outreach programs gained in its experience of transitioning
the North American Numbering Plan 

M-2

 

Administration
(NANPA) and will solicit the assistance of subject matter experts on the U.S. domain name structure. 

        Formulation
of and monitoring acceptance of policy is another important function that NeuStar will manage as administrator of the usTLD. The policy staff is responsible for coordinating
with the usTLD Policy Council on formation of new policies or modification of existing policy. They will communicate with the requisite parties at ICANN, that is, the ccTLD constituency, the GAC, and
the Intellectual Property Constituency. This group will also be responsible for accreditation of new usTLD registrars. 

        Because
of their sensitive nature, the registry and registrar functions will be handled separately. NeuStar will have dedicated staff that fulfills the function of registrar for
undelegated domains in the locality-based structure of the usTLD; they will not have any responsibilities within the registry operations. This function will act like current registrars with an
XRP-like interface into the registry with which they register domains under that delegation. 

        In
its role as central registry, NeuStar has experience managing technical and operational responsibilities. Experienced staff will manage all networks, systems, databases, and hardware
to meet the service level requirements of the registry. 

        Additionally,
NeuStar will focus a team of individuals on the increased enhancement of the usTLD through the facilitation of new applications and value-added services to increase the
utility of the usTLD. This product development group will coordinate with various public interest groups as well as commercial entities to promote new and innovative extensions to the usTLD. 

Expense Categories  

        New and incremental staffing is required for each functional area of the coordination and management of the usTLD.
Through our existing contract with the Federal Communications Commission, NeuStar has government-approved labor burden rates that are factored to all staff rates to cover all employee-related
benefits; that rate is 33.3%. For each of the staff members, we have modeled to account for all expenses that are applicable for each function. 

        The
Enhanced SRS and two of the nameserver sites will be housed in NeuStar facilities in Virginia and Illinois. A proportional amount of
the space in those data centers is allocated for the Internet registry. In addition to these technical facilities, NeuStar will contract with qualified third parties to host nameservers in
geographically disbursed facilities. All usTLD-related staff will occupy space in one of our U.S.-based facilities. 

        Communications expense is calculated on a cost-per-Megabit rate and is projected to decline on cost at an annual
rate of 15%. This includes all bandwidth and capacity requirements at the SRS data centers and the nameserver sites. NeuStar contracts with multiple communications providers to share its communication
lines rather than being reliant on a single provider. This protects each phase of the system from outage due to a communication provider's backbone outage. 

        Significant
funds are allocated to the marketing and outreach programs for the usTLD, in conjunction with the marketing plan presented in
Section B.2.8 and the outreach programs in Sections B.3.5 This category of expense includes the public relations efforts, the execution of a brand awareness campaign, and any media or
collateral related to the usTLD. 

        In
its role as administrator of the usTLD, NeuStar will be an active member of the ccTLD constituency and abide by all policies and best practices established by ICANN. NeuStar will
participate in meetings and working groups wherever appropriate to protect the value and autonomy of the usTLD. As a member, NeuStar would be responsible for all funding requirements set forth by
ICANN. Currently, there is a formula, composed of a fixed fee and a variable component based on registry 

M-3

 

volume,
to determine quarterly "dues" to ICANN. Additionally, NeuStar will be responsible for a membership fee to the ccTLD constituency. NeuStar has included this funding requirement in the financial
plan. 

        As
a part of normal operations, NeuStar budgets for ongoing hardware and software maintenance. This provides additional support for all
capital expenditures discussed above. 

        As
with the approved labor burden, NeuStar has a government-approved general and administrative rate allocated to all direct expenses that is used in forecasting expenses and generating
a competitive price. That rate is 25%. 

        Each
of the enumerated expenses is critical to the efficient coordination and management of the usTLD. NeuStar's extensive experience operating a mission-critical public resource
uniquely qualifies us to identify and account for each aspect of our responsibilities. Quantitative analysis for these expenses can be found in the financial statement presented in Section N. 

M-4

 

N.    Pro Forma Projections  

        NeuStar's financial plan for the usTLD reflects the variability of the domain name management of an Internet registry and a pricing option
that will pass on economies of scale to registrars and registrants, but that also provides a reasonable profit.

        NeuStar
recognizes the need of the DOC to determine the fairness and reasonableness of registry prices and assess that the users, citizens of the United States, are receiving the best
value. To assist in that assessment, we submit revenue and operating expenses associated with the coordination and management of the usTLD for each of the years in the base term of the DOC's purchase
order. 

        As
a part of our proposal for the coordination and management of the usTLD, NeuStar has developed a comprehensive business plan around the anticipated demand for its
next-generation, thick Internet registry. Additionally, we have introduced creative pricing structures to pass back economies of scale that we realize. The projections presented below are
consistent with the demand enumerated in Section C of NeuStar's response, as well as the technical, operating, and policy functions outlined in Section M. 

        The
expense, both capital and operational, is variable in nature; therefore, the financials presented are a snapshot for a volume range (domain names under management). The incremental
expenses increase as volume increases in the registry; thus, if the volume exceeds that presented in this analysis, the expense will also increase. 

        The
financial statements are prepared in accordance with US GAAP. Revenue is calculated on a straight-line basis over the duration of the registration term. Likewise,
depreciation and amortization are calculated on a straight-line basis, whereby hardware is depreciated over three (3) years and software amortized over five (5) years. All
other expenses are wholly recognized in the period in which they occur. All figures are presented in thousands. 

NeuStar usTLD Pro Forma Income  

	 
	 	Contract

Year 1
	 	Contract

Year 2
	 	Contract

Year 3
	 	Contract

Year 4
	 
	Revenue	 	$	[***	]	$	[***	]	$	[***	]	$	[***	]
	

Operating	
 	
 	

 	
 	
 	

 	
 	
 	

 	
 	
 	

 	
 
	 	Staffing	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	Marketing/Outreac	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	Communication	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	Maintenanc	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	ICANN	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	Depreciation and	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	Other Direct	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	 	
	 	
	 	
	 	
	 
	 	 	 	 	Total Operating	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	 	 	
 G&A	
 	
 	

[***	
]	
 	

[***	
]	
 	

[***	
]	
 	

[***	
]
	 	 	 	 	 	
 Total	
 	
 	

[***	
]	
 	

[***	
]	
 	

[***	
]	
 	

[***	
]
	 	 	
	 	
	 	
	 	
	 
	EBIT	 	 	[***	]	 	[***	]	 	[***	]	 	[***	]
	 	 	
	 	
	 	
	 	
	 

        NeuStar
is committed to the financial success of administering the usTLD. The returns NeuStar forecasts here confirm that registry customers are receiving best value for the service
provided. This forecast assumes we will be on a strong trajectory as of year four of the contract to receive an adequate 

N-1

 

return
on our investment. We are confident we will meet or exceed the objectives of the DOC, to be eligible for the optional renewals that afford this opportunity. 

        NeuStar
believes that the financial plan associated with the usTLD is a key evaluation criterion for determining the feasibility of a project. The usTLD administrator must have: 

	•
	Demonstrable
experience in developing, implementing, and operating a mission-critical public resource to accurately produce a comprehensive business plan;

	•
	Immediate
access to capital to fully fund the coordination and management of the usTLD as well as its enhancements; and

	•
	Assured
access to additional capital as a measure of contingency. 

        NeuStar
fully satisfies all of the aforementioned criteria. 

N-2

   O.    Proposed Technical Plan  

HIGHLIGHTS  

	•
	Co-active, redundant Enhanced Shared Registration System Data Centers in VA and IL with two-way replication

	•
	Three geographically dispersed nameserver Data Centers (CA, VA, & IL). Each Data Center containing multiple load balanced
nameservers

	•
	High availability cluster architecture with flexibility, scalability, and reliability

	•
	Redundant Database Servers with seamless failover for applications

	•
	Enhanced SRS is sized initially to handle the projected workload but can grow incrementally

	•
	Enhanced SRS application software architecture is standards based, open systems to facilitate cost-effective upgrade

	•
	Rapid Application Development Methodology for new application development

        NeuStar's
proposed technical solution for usTLD operations meets all of the U.S. Department of Commerce's (DOC's) requirements for the existing and expanded usTLD, in addition to
providing numerous improvements and enhancements: 

        Full Existing and Expanded usTLD Space Support—NeuStar will provide support for the existing usTLD space, which will include
support for existing delegees, as well as providing registrar service for new and existing registrants. In addition, NeuStar will provide full registry support to all eligible registrars for the
expanded usTLD space. 

        Database Centralization—NeuStar proposes to implement a Centralized usTLD Database including a Delegated Manager Database and
a centralized Whois. This approach will offer improved consistency and accuracy of data. 

        Improved Reliability—In support of registry, registrar, database, and information services for the usTLD, NeuStar will
implement co-active data centers and a number of nameserver data centers to create a resilient infrastructure protected against outages through redundancy, fault tolerance, and geographic
dispersion. The benefits to the U.S Internet community are improved availability and better access to DNS services. 

        Providing Real-Time Responsiveness—NeuStar will implement near-real-time updates to the
zone files and the Whois database. The benefit to the U.S Internet community is the elimination of delay-caused confusion over domain name registrations. 

        Eliminating Bottlenecks—NeuStar's high-availability cluster architecture provides scalable processing throughput,
dynamic load balancing between the two data centers, and multiple high-speed Internet connections. The benefit to the Internet user and registrar communities is the elimination of registry
bottlenecks. 

        Encouraging Competition—NeuStar will develop and deploy a new, streamlined registry-registrar protocol for the expanded usTLD
space: the eXtensible registry protocol (XRP). The XRP
provides more features and functionality than the existing registry/registrar interface and far greater security. The benefits to the Internet community are greatly improved Internet stability and
increased public confidence. NeuStar will work with the Internet Engineering Task Force (IETF) to bring the protocol to standard status. 

        NeuStar's
proposed usTLD technical solution is based on our experience with the Number Portability Administration Center (NPAC) and with the.biz registry operations. As requested,
Section O.1 provides an overview of our proposed facilities and systems; subsequent sections expand this overview into a comprehensive technical plan for registry operations detailing the
equipment software, hardware, and related technology NeuStar will use to meet the usTLD program objectives and needs. 

O-1

 

O.1    Proposed Technical Facilities and Systems  

        NeuStar proposes world-class redundant Enhanced Shared Registration System (SRS) Data Centers in Virginia and Illinois and initially three
Nameserver Data Centers, co-located with the Enhanced SRS Data Centers and a standalone in California, that will provide the facilities and infrastructure to host the usTLD Registry. Our
facility locations were selected to give wide geographic separation and provide resilience against natural and man-made disasters. The benefit to the DOC and the Internet community is
reliable, non-stop usTLD registry, registrar, database, and information services operation.

        NeuStar
has developed a redundant facility implementation, high availability cluster server architectures, redundant database technology, and redundant alternate routed network
connectivity that successfully supports mission-critical services today. The Internet community needs to be able to depend on the Internet as a stable, highly available infrastructure for worldwide
collaboration and commerce. 

        In
the subsection that follows, we describe where the NeuStar facilities are located and provide a functional description and physical description of the Enhanced Shared Registration
System (SRS) data center and the nameserver sites. In subsequent subsections, we provide a more detailed system description of each of the systems residing within these facilities. 

O.1.1    Registry Facilities Site Description  

        This section describes NeuStar's proposed usTLD Registry architecture consisting of redundant Enhanced SRS data centers and multiple nameserver sites to provide a
seamless, responsive, and reliable registry service to registrars and Internet users. As shown in Exhibit O-1, our TLD registry redundant Enhanced SRS and nameserver data center
sites are geographically dispersed and interconnected with a Virtual Private Network (VPN) to provide nationwide coverage and protect against natural and man-made disasters and other
contingencies. 

O.1.1.1    Enhanced Shared Registration System (SRS) Data Center Functional Description  

        High availability registry services can be provided only from facilities that have been designed and built specifically for such a critical operation. The NeuStar
Enhanced SRS data centers incorporate redundant uninterruptible power supplies; high-capacity ventilation and climate control; fire suppression; physical security; firewalls with intrusion
detection; redundant, high availability cluster technology; and redundant network and telecommunications architectures. When selecting the sites, we considered their inherent resistance to natural and
man-made disasters. The functional block diagram of our Enhanced SRS data center is depicted in Exhibit O-2. As can be seen from this exhibit, the Enhanced SRS data
center is highly redundant and designed for no single point of failure. 

        Each
Enhanced SRS data center facility provides the functions listed in the system function directory table below. Descriptions of the Enhanced SRS systems providing these functions are
provided in the next subsection. 

[Exhibit O-1:
Graphic Design] 

[Exhibit O-2:
Graphic Design] 

O-2

 

 Enhanced Shared Registration System (SRS) Function Directory  

	System Function
	 	Functional Description

	Web Server	 	High capacity Web Servers provide secure Web services and information dissemination. It contains a registry home page to enable registrars to sign in and inquire about account status, get downloads and whitepapers, access
frequently asked questions, obtain self help support, or submit a trouble ticket to the TLD Registry Help Desk.
	

Secure Web Provisioning Interface	
 	

High capacity web servers provide a secure interface for the delegated managers and registrants in the locality space to provision registration data. Delegated managers will be provided with authenticity information that they will need to input to
access their account information. Registrants that utilize NeuStar as a registrar will be provided with similar authenticity information for their registrations. This is to ensure that only that registrant can modify the registration.
	

Protocol (XRP) Servers	
 	

XRP transactions received from registrars undergo front-end processing by the XRP server that manages the XRP session level dialog, performs session level security processing, and strips out transaction records. These XRP transaction records are sent
to the Enhanced SRS data center application server cluster for security authentication and business logic processing.
	

Application Servers	
 	

Processing of the XRP applications business logic, user authentication, posting of inserts, deletes, updates to the master database, and interfaces to authentication, billing and collections, backup, and system/network administration.
	

Centralized usTLD	
 	

The Centralized usTLD database maintains registry data in a multi-threaded, multi-session database
	

Database Servers	
 	

for building data-driven publish and subscribe event notifications and replication to downstream data marts such as the Whois, Delegee, Zone, and Billing and Collection services.
	

Whois Distribution Database	
 	

The Whois Distribution Database is dynamically updated from the Centralized usTLD database and propagates the information to the Whois Database clusters.
	

Whois Database Clusters	
 	

The Whois Database is dynamically updated from the Whois Distribution Database and sits behind the Whois Server clusters. The Whois Database clusters are used to look up records that are not cached by the Whois Servers.
	

Whois Servers	
 	

The Load Balanced Whois Server Clusters receive a high volume of queries from Registrants and Internet users. The Whois service returns information about Registrars, domain names, nameservers, IP addresses, and the associated contacts.
	 	 	 

O-3

 

	

Delegee Whois	
 	

The Delegee Distribution Database is dynamically updated from the Centralized usTLD database and
	

Distribution Database	
 	

propagates the information to the Delegee Database clusters.
	

Delegee Whois Database	
 	

The Delegee Database is dynamically updated from the Delegee Distribution Database and sits behind
	

Clusters	
 	

the Delegee Server clusters. The Delegee Database clusters are used to look up records that are not cached by the Delegee Servers.
	

Delegee Whois Servers	
 	

The Load Balanced Delegee Server Clusters receive a high volume of queries from Registrants and Internet users. The Delegee service returns information about Registrars, domain names, nameservers, IP addresses, and the associated
contacts.
	

Zone Distribution	
 	

The Zone Distribution Database is dynamically updated from the registry Centralized usTLD database
	

Database	
 	

and propagated to the nameserver sites located worldwide. It contains domain names, their associated nameserver names, and the IP addresses for those nameservers.
	

Billing and Collection	
 	

A commercial off-the-shelf system is customized for registry specific eCommerce billing and collection functions that are integrated with XRP transaction processing, the master database and a secure Web server. The system maintains each registrar's
account information by domain name and provides status reports on demand.
	

Authentication Services	
 	

Authentication Service uses commercial X.509 certificates and is used to authenticate the identity of entities interacting with the Enhanced SRS.
	

Backup Server	
 	

Provides backup and restore of each of the various cluster servers and database servers files and provides a shared robotic tape library facility for central backup and recovery.
	

Systems/Network	
 	

Provides system administration and simple network management protocol (SNMP) monitoring of the
	

Management Console	
 	

network, LAN-based servers, cluster servers, network components, and key enterprise applications including the XRP, Web, Whois, Zone, Billing and Collections, Backup/Restore, and database application. Provides threshold and fault event notification
and collects performance statistics.
	

Applications Administration Workstations	
 	

Provides client/server GUI for configuration of Enhanced SRS applications including XRP, Web, Billing and Collection, Database, Authentication, Whois, Zone, etc.
	

Building LAN	
 	

Provides dual redundant switched Gigabit Ethernet LAN-based connectivity for all network devices in the data center
	 	 	 

O-4

 

	

Firewall	
 	

Protects the building LAN from the insecure Internet via a Firewall that provides policy-based IP filtering and network-based intrusion detection services to protect the system from Internet hacking and denial of service attacks.
	

Load Balancers	
 	

Dynamic Feedback Protocol (DFP)—based load balancing of TCP/IP traffic in a server cluster including common protocols such as least connections, weighted least connections, round robin, and weighted round robin.
	

Telecommunications Access	
 	

Dual-homed access links to Internet Service Providers (ISPs) and Virtual Private Network (VPN) services are used for connectivity to the Internet and the NeuStar Registry Management Network.
	

Central Help Desk	
 	

A single point of contact telephone and Internet-Web help desk provides multi-tier technical support to registrars on technical issues surrounding the Enhanced SRS.

O.1.1.2    Nameserver Sites Functional Description  

        As discussed above, two nameserver sites are co-located at our Enhanced SRS Data Centers and a third nameserver System site is geographically
separated with dual-homed Internet and VPN local access telecommunications links to provide resilience and disaster recovery. The additional nameserver site will be installed in a Data
Center in California. Additional nameserver sites will be introduced as demand warrants. Additional nameserver sites will be introduced as demand warrants. The functional block diagram of our
nameserver sites is depicted in Exhibit O-3. As can be seen from the exhibit, the nameserver sites are configured to be remotely managed and operated "lights out." The hardware
configuration is highly redundant and designed for no single point of failure. 

[Exhibit O-3:
Graphic Design] 

        The
following function directory table lists the nameserver functions. Descriptions of the systems providing these functions are provided in the next subsection. 

O-5

 

 Nameserver Function Directory  

	System Function
 
	 	Functional Description

	Zone Update Database	 	The Enhanced SRS Zone Distribution Database is propagated to the Zone Update Database Servers at the nameserver sites. Information propagated includes domain names, their associated nameserver names, and the IP addresses
for those nameservers.
	

Nameserver	
 	

The nameserver handles resolution of usTLD domain names to their associated nameserver names and to the IP addresses of those nameservers. The nameservers are dynamically updated from the Zone Update Database. Updates are sent over the VPN Registry
Management Network.
	

Building LAN	
 	

Provides dual redundant switched Gigabit Ethernet LAN-based connectivity for all network devices in the data center
	

Firewall	
 	

Protects the building LAN from the insecure Internet via a Firewall that provides policy-based IP filtering and network-based intrusion detection services to protect the system from Internet hacking and denial of service attacks.
	

Load Balancers	
 	

Dynamic Feedback Protocol (DFP)—based load balancing of TCP/IP traffic in a server cluster including common protocols such as least connections, weighted least connections, round robin, and weighted round robin.
	

Telecommunications Access	
 	

Dual-homed access links to Internet Service Providers (ISPs) and Virtual Private Network (VPN) services are used for connectivity to the Internet and the NeuStar Registry Management Network.

O.1.1.3    Enhanced SRS Data Center and Nameserver Buildings  

        Each NeuStar data center facility is located in a modern, fire-resistant building that offers inherent structural protection from such natural and
man-made disasters as hurricanes, earthquakes, and civil disorder. Sites are not located within a 100-year flood plain. Facilities are protected by a public fire department and
have their internal fire-detection systems connected directly to the fire department. 

O-6

 

        Data
centers are protected from fire by the sprinkler systems of the buildings that house them. Furthermore, each equipment room is protected by a pre-action
fire-suppression system that uses Inergen gas as an extinguishing agent. 

        The
environmental factors at the Enhanced SRS Data Center and nameserver sites are listed in the following table. 

 Environmental Factors at Enhanced SRS Data Center and Nameserver Sites  

	Ventilation and Climate Control	 	Dual redundant HVAC units control temperature and humidity. Either unit will maintain the required environment.
	

Lighting	
 	

2x2-foot ceiling-mounted fluorescent fixtures
	

Control of static electricity	
 	

All equipment-mounting racks are grounded to the building's system, and are equipped with grounding straps that employees wear whenever they work on the equipment.
	

Primary electrical power	
 	

208-volt, 700-amp service distributed through four power panels
	

Backup power supply	
 	

30 minutes of 130-KVA UPS power

1000-KVA generator (Enhanced SRS data center)

250-KVA generator (nameserver data center)
	

Grounding	
 	

All machines are powered by grounded electrical service

A 12-gauge cable under the equipment-room floor connects all equipment racks to the building's electrical-grounding network

Building Security  

        In addition to providing physical security by protecting buildings with security guards, closed circuit TV surveillance video cameras, and intrusion detection
systems, NeuStar vigilantly controls physical access to our facilities. Employees must present badges to gain entrance and must wear their badges at all times while in the facility. Visitors must sign
in to gain entrance. If the purpose of their visit is found to be valid, they are issued a temporary badge; otherwise, they are denied entrance. At all times while they are in the facility, visitors
must display their badges and must be escorted by a NeuStar employee. Sign-in books are maintained for a period of one year. 

Security Personnel  

        On-site security personnel are on duty 24 hours a day, 7 days a week to monitor the images from closed-circuit television cameras placed
strategically throughout the facilities. Security personnel are stationed at each building-access point throughout normal working hours; at all other times (6:30 p.m. to 6:30 a.m. and
all day on weekends and major holidays), individuals must use the proper key cards to 

O-7

 

gain
access to the buildings. Further, any room housing sensitive data or equipment is equipped with a self-closing door that can be opened only by individuals who activate a
palm-print reader. Senior facility managers establish the rights of employees to access individual rooms and ensure that each reader is programmed to pass only authorized individuals. The
palm readers compile and maintain a record of individuals who enter controlled rooms. 

O.1.2    Enhanced Shared Registration System Descriptions  

        This section provides system descriptions of the NeuStar Enhanced SRS Data Center sites and the Nameserver Data Center. We provide brief system descriptions and
block diagrams of each functional system within the two sites and their network connectivity. The NeuStar usTLD system architecture's central features are as follows: 

	•
	Co-active
redundant data centers geographically dispersed (with two-way database replication between the centers) to provide mission critical service
availability.

	•
	Nameserver
sites designed with full redundancy, automatic load distribution, and remote management for "lights out" operation.

	•
	A
Virtual Private Network provides a reliable, secure management network and dual-homed connectivity between the data centers and the nameserver sites.

	•
	Each
Enhanced SRS data center and nameserver site uses high availability cluster technology for flexibility, scalability, and high reliability.

	•
	Registry
systems sized initially to handle more than the expected initial workload can grow incrementally to accommodate workload beyond the initial implementation.

	•
	The
usTLD databases use redundant server architecture and are designed for continuous operation with synchronous replication between the primary and secondary databases. 

        NeuStar
is proposing standard, mid-level, and high-end cluster server platforms for installation at each site. The servers are selected for applications depending
on the requirements, storage capacity, throughput, interoperability, availability, and level of security. The generic server platform characteristics are summarized in the following table. 

O-8

 

 Server Platform Description  

	Platform
 
	 	Features
	 	Application

	

Standard Intel Server Clusters	

 	

Rack-mounted Intel 700 Mhz, 32-bit, 2- to 6-way SMP CPUs with 8 GB of ECC memory, CD ROM, four hot-swap disk drives (9-36 MB each), redundant hot swappable power supplies, dual attach 100 BaseT Ethernet Adapter, clustering and event management
software for remote management. Red Hat Linux 6.1	

 	

•    Nameserver Cluster

•    Whois Server Cluster

•    Backup Server

•    Network Management Server

•    Update Servers (Zone/Whois)

•    XRP Server

•    Web Server
	

Mid-level RISC Server Clusters	

 	

RISC 550 Mhz 2- to 8-way SMP, 64-bit CPUs, 32 GB ECC RAM, 72 GB internal disk capacity, 71 TB external RAID, redundant hot swappable power supplies, dual attach Gigabit Ethernet Adapter, clustering and event management software for remote management.
Unix 64-bit operating system	

 	

•    Application Server Cluster

•    Billing & Collection Server

•    Authentication Server

•    Whois Database Server
	

High-end RISC Server Cluster	
 	

RISC 550 MHz CPU, 64-bit 2- to 32-way cross-bar SMP with 8x8 non-blocking multi-ported crossbar, 32 GB ECC RAM, 240 MB/sec channel bandwidth, 288 GB Internal mass storage, up to 50 TB external RAID storage, redundant hot swappable power supplies,
dual attach Gigabit Ethernet Adapter, clustering and event management software for remote management. Unix 64-bit operating system	
 	

Redundant Server for database system

O-9

 

O.1.2.1    Enhanced SRS Data Center System Descriptions  

        As previously shown in Exhibit O-2, the Enhanced SRS data centers provide co-active
fully redundant system configurations with two-way replication over the high-speed VPN Registry Management Network, a co-located complete nameserver cluster, and
dual-homed connectivity to the Internet Service Providers (ISPs). Descriptions of each of the systems in the Enhanced SRS Data Center site are as follows. 

XRP Server Cluster  

        XRP transactions received from registrars over the Internet undergo front-end processing by the XRP Server which manages the XRP session level dialog,
performs session level security processing, and strips out the transaction records. These XRP transaction records are sent to the Enhanced SRS data center application server cluster for security
authentication and business logic processing. The XRP server is a rack-mounted Intel machine with local disk storage. It off-loads the front end processing of the XRP protocol
and off-loads the extensive communication protocol processing, session management, and SSL security encryption/decryption from the applications servers. The XRP server strips the fields
out of the XML document transaction and builds XRP binary transaction packets that are sent to the application server for initial security authentication and log-on with user ID and
password. Once the user is authenticated, the session is active and the XRP application server performs all business logic processing, billing, collection, and database operations. 

Nameserver  

        A complete nameserver cluster for DNS queries is co-located in each Enhanced SRS data center site. As previously shown in
Exhibit O-3, the nameserver cluster consists of redundant ISP and Virtual Private Network (VPN) local access links to provide
alternate routed connectivity to Internet users and NeuStar's Registry Management Network. Redundant Internet firewalls provide policy-based IP filtering to protect our internal building LAN from
intruders and hackers. 

Application Server Cluster  

        The application server cluster is a high availability multiple computer cluster. Each computer within the cluster is a mid-level processor with its
own CPU, RAID disk drives, and dual LAN connections. Processor nodes used in the clusters are RISC symmetric multiprocessor (SMP) architectures scalable in configurations from 2- to
8-way with the processing and storage capacity for very large applications. As depicted in Exhibit O-4, the application server cluster is designed to handle the
registrar transaction workload and provides the business logic processing applications and interfaces to the authentication server, Centralized usTLD database, and billing and collection system. The
application server cluster is front-ended with a TCP/IP load balancer to equitably distribute the processing load across the cluster processors. The cluster manager software monitors hardware and
software components, detects failures, and responds by reallocating resources to support applications processing. The process of detecting a failure and restoring the application service is completely
automatic—no operator intervention is needed. 

Database Server  

        The database server consists of two identical redundant RISC systems that are designed for high-volume, online transaction-processing (OLTP) database
applications. Each server contains high-end RISC processors scalable in configurations from 2-to 32-way SMP. A crossbar-based SMP memory subsystem is capable of
supporting up to 32 GB of memory needed to maintain high OLTP transaction workloads. The storage subsystem supports up to 288 GB of internal RAID storage and up to 50 TB of external RAID storage. The
database management software is based on a parallel database 

O-10

 

architecture
with a redundant server option capable of maintaining 24 × 7 availability. The server supports high availability operations by implementing synchronous
replication. The database enables transparent database failover without any changes to application code or the operating system. Clients connecting to a replicated database are automatically and
transparently connected to the replicated pair of databases. The database replication feature makes it possible to maintain geographically separated data services for multiple sites over a WAN to
provide disaster recovery. 

        A
multi-session, multi-threaded server and dual cache architecture (client/server) provides exceptionally high throughput and fast access to stored objects. A powerful database-driven
publish and subscribe event notification system enables applications such as Whois or Zone Distribution to subscribe to a specific Centralized usTLD database activity (e.g., a domain name insert).
When the domain name insert occurs, an event is generated by the database to be handled as a dynamic update to the Whois and Zone distribution servers. 

[Exhibit O-4:
Graphic Design] 

Whois Distribution Database  

        Certain Centralized usTLD Database events such as a domain name insert, domain name delete, or domain name change, generate a notification to subscriber databases
such as the Whois Distribution Database. Modifications to the Whois Distribution Database are replicated to the Whois Database Clusters. 

Whois Database  

        The Whois architecture gives the flexibility to deploy a Whois database to any number of NeuStar Data Centers. In the initial phase, the Whois infrastructure will
be deployed to the two Enhanced SRS Data Centers. However, in the future, and based on load placed on the initial two Data Centers, additional infrastructure can be deployed to any of the nameserver
Data Centers managed by NeuStar. 

        Each
Whois Database receives replicated updates from the Whois Distribution Database. The initial Whois Database will consist of two mid-level RISC database servers
configured in a high availability cluster with RAID storage and from 2- to 8-way SMP processors. Since data is cached in the Whois Servers, the Whois Database is hit only when
a Whois Server has not cached a request in memory. 

Whois Server Cluster  

        The Whois service is available to anyone and is engineered to handle large volumes of transactions per day. The cluster is a rack-mount Intel
Pentium-based high availability multiple computer cluster that maintains a separate database for domain name registrations and caches commonly requested records. Processor nodes used in the Whois
cluster are standard Intel Pentium SMP machines scalable in configurations from 2- to 6-way SMP with local disk storage. 

        The
Whois database contains information about registrants, associated registrars/delegated manager, domain names, nameservers, IP addresses, and the contacts associated with them. This
is an
improvement over the current registry that provides no end-user contact information. The Whois server cluster is front-ended with a load balancer designed to distribute the load equitably
to the servers in the cluster and handle extremely high volumes of queries. The load balancer tracks processor availability and maintains high query processing throughput. 

Delegee Whois Distribution Database  

        Certain Centralized usTLD database events such as a delegation/sub-delegation insert, delegation/sub-delegation delete, or
delegation/sub-delegation change, generate a notification to subscriber 

O-11

 

databases
such as the Delegee Whois Distribution Database. Modifications to the Delegee Whois Distribution Database are replicated to the Delegee Whois Database Clusters. 

Delegee Whois Database  

        The Delegee architecture gives the flexibility to deploy a Delegee Whois database to any number of NeuStar Data Centers. Initially, the Delegee infrastructure
will be deployed to the two Enhanced SRS Data Centers. However, in the future, and based on load placed on the initial two Data Centers, additional infrastructure can be deployed to any of the
nameserver Data Centers managed by NeuStar. 

        Each
Delegee Whois Database receives replicated updates from the Delegee Whois Distribution Database. The initial Delegee Whois Database will consist of two mid-level RISC
database servers configured in a high availability cluster with RAID storage and from 2- to 8-way SMP processors. Since data are cached in the Delegee Whois Servers, the
Delegee Whois Database is hit only when a Delegee Whois Server has not cached a request in memory. 

Delegee Whois Server Cluster  

        The Delegee Whois service is available to anyone. The cluster consists of rack-mount Intel Pentium-based high availability multiple computer cluster
that maintains a separate database for domain name delegations and caches commonly requested records. Processor nodes used in the
Delegee cluster are standard Intel Pentium SMP machines scalable in configurations from 2- to 6-way SMP with local disk storage. 

        The
Delegee Whois database contains information about delegated managers, domain names, nameservers, IP addresses, and the contacts associated with them. The Delegee Whois server cluster
is front-ended with a load balancer designed to distribute the load equitably to the servers in the cluster and handle extremely high volumes of queries. The load balancer tracks processor
availability and maintains high query processing throughput. 

Zone Distribution Database  

        The Zone Distribution Database is dynamically updated from the Centralized usTLD database using the same technique used for the Whois Distribution Database. The
Zone Distribution Database is propagated to Zone Update Database at the nameserver sites using replication. This approach is far better than the current approach of TLD Zone File updates for.com,.net,
and.org that occur two times per day. 

Billing and Collection Server  

        The Billing and Collection server is a LAN-based mid-level RISC machine in configurations scalable from 2-to 8-way
SMP with the processing and storage capacity for very large enterprise applications. This server runs a commercial off-the-shelf customer relationship management and billing
and collection system that interfaces with the Centralized usTLD database. 

Secure Web Server Cluster  

        A high-capacity secure Web Server cluster is provided to enable secure Web services and information dissemination. It contains a registry home page to
enable registrars to sign in and inquire about account status, get downloads and white papers, access frequently asked questions, obtain self-help support, or submit a trouble ticket to
the TLD Registry Help Desk. The Web Server is a rack-mounted Intel machine with local disk storage. 

O-12

 

Authentication Server  

        The authentication server is a LAN-based mid-level RISC machine scalable in configurations from 2- to 8-way SMP
with local RAID storage. This server runs commercial X.509 certificate-based authentication services and is used to authenticate the identity of registrars, delegated managers, and registrants, as
well as NeuStar personnel. In addition, the authentication server supports our secure Web server portal for customer service functions. 

Backup Server  

        The backup server is an Intel Pentium-based SMP server that runs the backup and restore software to backup or restore each of the various cluster servers and
database servers and provide a shared robotic tape library facility. It interfaces to the Intel server clusters and RISC server clusters over a high-speed fiber channel bridge. It
interfaces with the high-end redundant database servers via a disk array and the fiber channel bridge that interconnects to the robotic tape library. It is capable of performing remote
system backup/restore of the nameservers over the VPN-based Registry Management Network. 

System/Network Management Console  

        The system/network management console provides simple network management protocol (SNMP) monitoring of the network, LAN-based servers, cluster
servers, and key enterprise applications including the XRP, Web, Whois, Zone, Billing and Collections, and database applications. The server is a LAN-based standard Intel Pentium-based SMP
machine with local RAID disk storage and dual attached LAN interconnections. 

Building LAN Backbone  

        The redundant switched Gigabit Ethernet building LAN backbone gives unprecedented network availability via redundant Gigabit Ethernet switches. Devices are dual
attached to each of the gigabit switches to provide a redundant LAN architecture. The building LAN is protected from the insecure Internet via a firewall that provides IP filtering and network-based
intrusion detection services to protect the system from Internet hacking and denial of service attacks. 

Dual-Homed Telecommunications Access  

        We are using dual-homed high-speed Internet local access telecommunications links to two separate ISP providers. These links will be
alternately routed to provide resilience against cable faults and loss of local access telecommunications links. Similarly, the telecommunications access links to our VPN provider for the Registry
management network will be dual-homed and alternate routed. 

O-13

   O.1.2.2    Nameserver Description  

        Two nameserver sites are co-located at our Enhanced SRS Data Centers and the third nameserver cluster site is geographically separated, with
dual-homed Internet and VPN local access telecommunications links to provide resilience and disaster recovery. The additional zone server clusters will be installed in California,
Additional nameserver sites will be installed as demand warrants. The functional block diagram of our nameserver cluster is previously depicted in Exhibit O-3. As can be seen from
the exhibit, the nameserver sites are configured to operate "lights out." The hardware configuration is highly redundant and designed for no single point of failure and exceptionally high throughput.
The following are the nameserver subsystem functions: 

Zone Update Database  

        The Zone Distribution Database at the Enhanced SRS Data Center is propagated to the Zone Update Database using replication. Replication takes place over the VPN
Registry Management Network. The Zone Update Database is not hit when resolving DNS queries; instead, the nameservers update their in-memory database from the Zone Update Database, within
defined service levels. 

Nameserver Cluster  

        The nameserver cluster handles resolution of usTLD domain names to their associated nameserver names and to the IP addresses of those nameservers. The resolution
service can handle in excess of 500 million queries per day, and our load-balanced architecture allows additional servers to be added to any nameserver cluster to allow
on-demand scalability. 

        The
nameserver Cluster is a high availability rack-mounted multiple computer cluster consisting of standard Intel Pentium-based SMP machines configurable from 2-
to 6-way SMP with local disk storage and dual attachment to the LAN. A TCP/IP server load balancer switch is used to distribute the load from Internet users. The server load balancer uses
dynamic feedback protocol to enable servers to provide intelligent feedback to the load balancer to
ensure that traffic is not routed to overutilized servers. The load balancer supports algorithms including least connections, weighted least connections, round-robin, and weighted round-robin. 

Building LAN Backbone  

        A redundant switched Ethernet building LAN backbone maintains high network availability via redundant Ethernet switches. Devices are dual attached to each of the
Ethernet switches to provide a redundant LAN architecture. The building LAN is protected from the insecure Internet via a firewall that provides IP filtering and network-based intrusion detection
services to protect the system from Internet hacking and denial of service attacks. 

O-14

 

        A
summary of the features and benefits of our usTLD system architecture is provided in the following table. 

 usTLD Registry  

	Feature
 
	 	Benefit
 

	Three classes of scalable processor configuration—standard, mid-level, and high-end	 	Provides flexible processing power and scalability to the applications
	

Direct Access Storage up to 50 Terabytes for database applications	
 	

Unmatched storage scalability of the database
	

Switched Gigabit Ethernet Redundant building LAN architecture	
 	

High capacity LAN infrastructure with no bottlenecks
	

Full Redundancy of all critical components with no single point of failure	
 	

Zero downtime and zero impact to users
	

Dual-homed, alternate routed local access links to two separate Internet Service Providers	
 	

Maintains connectivity if one of the ISP's services should experience and outage
	

Dual-homed, VPN connections to the VPN service provider	
 	

Protects against digging accidents that could damage local access cables
	

Redundant parallel database architecture configured for high	
 	

Non-stop database services and throughput scaled to handle
	

OLTP transaction throughput	
 	

all registry operations out of one data center.
	

Load balancing session distribution algorithm (SDA) to intelligently and transparently distribute traffic across servers	
 	

Maximize the number of Transmission Control Protocol/Internet Protocol (TCP/IP) connections managed by a server farm.
	

Separate Whois Server cluster and datamart to process Whois transactions	
 	

Facilitates rapid response to Whois queries.

O.1.3    Registry Network System Description  

        NeuStar is using the Internet to provide connectivity to the Registrars, Delegated Managers, and Registrants (where applicable) and a VPN to provide a secure
Registry Management Network for communications between the Enhanced SRS data centers and the nameserver sites. 

O.1.3.1    Internet Connectivity  

        NeuStar will deploy two 45-MB T-3 local access telecommunications links at each of our data centers, enabling each to provide TLD services
independently of the other. We will provision 5 MBs of capacity on each of the T-3 links. Therefore, we will provision 10 MB into each nameserver site and have up to 90 MB
(2 × 45 MB) of capacity for growth. This should be sufficient growth for at least two years. 

O-15

 

        Connectivity
to each data center will be via redundant routers. For security purposes, the router will be configured to allow only DNS UDP/TCP and BGP4 packets. Each router is connected
to a load balancer that distributes the query load among the nameservers in that site's cluster. These links will be alternately routed to provide resilience against cable faults and loss of local
access telecommunications links. Similarly the telecommunications access links to our VPN provider for the Registry Management Network will be dual-homed and alternate routed. Redundant
routers are used for both Internet and VPN access. 

O.1.3.2    VPN Registry Management Network  

        Each Enhanced SRS Data Center is connected to each of the nameserver sites over a VPN. In addition there are two ATM links that connect the two Enhanced SRS Data
Centers. Like the Internet access, the ATM links will be delivered over a T-3 local access link. Each link will be configured with some fraction of the full 45 MB of bandwidth. At the
nameservers, the two VPN connections will be delivered over a 1.5 MB T-1 local access link. The bandwidth on each of the VPN circuits will be some fraction of the full 1.5 MB. The VPN
Registry Management Network is a secure network used for NeuStar internal registry information exchange. It handles: 

	•
	Nameserver
database replication from the Zone Distribution Database to the Zone Update Database at the nameserver sites,

	•
	Remote
system/network management/backup of the nameservers, and

	•
	Remote
administration of nameservers. 

O.1.4    Registry System Application Software  

        Supporting existing delegees and registrants, as well as planning for the growth associated with domain registration and administration in the expanded usTLD
space, requires vision and a flexible design. NeuStar's vision is to successfully conduct leading-edge software engineering and product development that will address the needs of each of
the usTLD registry's sets of customers. NeuStar's proven record of successful development and implementation of large projects benefits the COTR by reducing technical and schedule risk. 

        NeuStar
software components are developed using open system and software standards to facilitate cost-effective application expansion and upgrade. The functional design
consists of a number of components representing a blend of: 

	•
	Proven
software design and development methodology;

	•
	Change
management and deployment process; and

	•
	Proven,
mission-critical-grade, third-party software products to complement the NeuStar-built software components. 

O.1.4.1    Application Components  

        The following components, illustrated in Exhibit O-5, deliver the Registry application functionality: 

	•
	Protocol
adapters

	•
	Application
server component

	•
	Process
manager

	•
	Processing
engines

	•
	Whois
component 

O-16

 

	•
	Delegee
Whois component

	•
	Datastore

	•
	Web
server (presentation) component

	•
	Billing
and Collections component

	•
	Nameserver
component 

        Further
information regarding these components is presented in the following paragraphs. 

Protocol Adapter Component  

        The protocol adapter component is the software module running on the XRP protocol servers. This component provides the standards based interface between the
Registry and the Registrar or Delegee systems. The XRP protocol will be based on open industry standards such as: 

	•
	XML—NeuStar proposes the introduction of a new standard protocol, the eXtensible Registry Protocol (XRP), based
on XML. This protocol supports system level communication between the Registrar/Delegee and the Registry.

	•
	SSL—X.509 Certificates will be used over an encrypted SSL session to authenticate Registrars/Delegees (in
addition to IP-based and user ID/password security). 

        The
protocol adapters will receive secure, encrypted data from Registrar/Delegee systems. They will convert the verbose external XML message into a compact binary internal message
format, which is delivered to the application server's process manager for processing. When processing is complete, the process manager will send the binary internal message back to the protocol
adapters for conversion to the protocol appropriate for communicating with the external system (i.e., XRP). 

        The
protocol adaptor architecture allows NeuStar to support a simple but powerful XML-based protocol supporting a comprehensive security policy, while eliminating additional
load that would otherwise be placed on the core Enhanced SRS system. 

[Exhibit O-5:
Graphic Design] 

Application Server Component  

        The design of the application server component is modular and flexible to support the requirements and scalable to meet demands placed on the system. The
application server utilizes a stateless architecture that allows scalability simply by adding additional machines to the tier. The core business logic is built into the application server component.
This component manages all back-end resources and performs services such as connection pooling and monitoring. 

        The
process engines defined in this section are some of the major functional components of the system. Process engines will be added and configured to meet the functional requirements. 

        Process Manager—is used to manage the different processes supported by the application, including starting processes in a
specific order at initialization time, monitoring the health of executing processes, restarting failed processes, and starting new processes to address application load requirements. The process
manager mediates processing and information requests from external systems by forwarding requests to the respective process engines. 

        Process Engines—will perform the underlying processing steps or primitives that are involved in performing the operation. The
process engines receive data and parameters from other application 

O-17

 

components,
including the process manager. The process engines access data from databases and update the databases while processing a transaction. The primary process engines are: 

	•
	Domain
Name Administration,

	•
	Registrar/Registrant
Administration,

	•
	Whois
Administration,

	•
	Delegee
Whois Administration,

	•
	Zone
Administration,

	•
	Security,

	•
	Billing
and Grace-period Administration, and

	•
	Logging,
Auditing & Reporting. 

        The
functionality of the primary process engines is explained in detail in Sections O.3 and O.6. 

Whois Component  

        Whois-related modifications to the Centralized usTLD database cause equivalent changes to the subscribing Whois Distribution Database. Updates to the Distribution
Database are replicated to the Whois Database Cluster at each Enhanced SRS Data Center. Machines in the Whois Server Cluster cache common requests in-memory, taking load off the Whois
Database Cluster. Cached items expire after a defined time interval to ensure that Whois data can be guaranteed correct within defined service levels (see Section O.8 for a detailed description
of the Whois capabilities). Exhibit O-6 provides a more detailed application architecture overview. 

[Exhibit O-6:
Graphic Design] 

Delegee Component  

        Delegee-related modifications to the Centralized usTLD database cause equivalent changes to the subscribing Delegee Whois Distribution Database. Updates to the
Distribution Database are replicated to the Delegee Database Cluster at each Enhanced SRS Data Center. Machines in the Delegee Whois Server Cluster cache common requests in-memory, taking
load off the Delegee Whois Database Cluster. Cached items expire after a defined time interval to ensure that Delegee data can be guaranteed correct within defined service levels (see
Section O.9 for a detailed description of the Delegee capabilities). Exhibit O-6 provides a more detailed application architecture overview. 

Datastore  

        The Enhanced SRS architecture includes a co-active databases supporting high availability operations by implementing synchronous replication. This
enables transparent database failover without any changes to application code or the operating system. Clients connecting to a co-active database are automatically and transparently
connected to the co-active pair of databases. 

        The
architecture utilizes a powerful database-driven publish and subscribe event notification system that enables components such as Whois or Zone Distribution to subscribe to specific
Enhanced SRS events. Subscribed events cause dynamic updates to the Whois and Zone distribution servers (see Section O.3 for a detailed description of the Database capabilities). 

O-18

 

Web Server Component  

        NeuStar will provide usTLD Registry functionality via a Web-based, Internet-accessible interface. Expanded usTLD space registrars, as well as existing
usTLD space delegees and registrants will all have the ability to access various registry/registrar functionality via a Web interface. 

        The
guiding principles for the design of the proposed Web Server component are flexibility and security. The Web interface will be accessible over the Internet, using a client Web
browser and will be
served up by the Registry Web server clusters at the Enhanced SRS Data Centers. The secure Web servers provide front-end HTTPS (secure Web) protocol handling with client browsers
accessible over the Internet. 

        Some
of the key features of the Registry Web interface architecture include: 

	•
	Extensible
design;

	•
	Open,
non-proprietary, standards-based technology (HTTP + SSL);

	•
	Intuitive
user interface;

	•
	Secure
access;

	•
	Online
help;

	•
	Ease
of navigation; and

	•
	Data
entry type checking (before forwarding requests to the application server tier). 

Billing and Collection System  

        NeuStar will combine our customized B&C methodology that has proved successful in the past with an accounts receivable product to provide comprehensive, secured,
high-quality, scalable, and Web-accessible B&C service. The major components of the system will include: 

	•
	Database,

	•
	Transaction
processor,

	•
	Monitor
and notifier, and

	•
	Report
generator. 

        See
Section O.6 for a detailed description of the Billing and Collection system along with the interfaces, security, and access privileges. 

Nameserver Component  

        Zone-related modifications to the Centralized usTLD database cause equivalent changes to the subscribing Zone Distribution Database. Updates to the
Zone Distribution Database are replicated out to the Zone Update Databases at each nameserver Data Center. Machines in the nameserver cluster reconcile their in-memory database with the
Zone Update Database at regular intervals defined in the service level agreement. The entirety of zone data is held memory resident. 

        Section O.5
explains nameserver architecture in detail, along with the process, software, and advantages. 

O.1.4.2    Registry Software Development Methodology  

        The quick-time-to-market and software technologies required to design and implement the registry software applications dictate
software development methodologies that minimize software development 

O-19

 

and
reduce development time without sacrificing software quality. NeuStar's technical personnel are experts in software applications development of registry and clearinghouse protocols and software
applications used in Internet domain names and phone number registry systems. NeuStar's experience will benefit the COTR by providing software products that meet the functional requirements and
operate reliably. 

        On
the basis of our experience, NeuStar is using Rapid Application Development (RAD) methodology and Computer-Aided Software Engineering (CASE) tools for registry software applications
development. RAD methodology enables large applications systems to be developed and tested incrementally in planned releases consisting of alpha, beta, and full production versions. We have found that
incremental development of software applications is a key success factor in fielding feature-rich software applications that meet business needs. This is because each incremental build
provides a testable software product that can be demonstrated to users and stakeholders. Changes can be easily incorporated in the next build cycle, and each successive build provides increased
functionality until the full production release is completed, tested, and accepted. NeuStar feels that this approach is ideally suited for allowing new software projects to quickly and fully benefit
from our previously developed software applications. 

RAD Methodology  

        In the RAD methodology there are five phases: 

	1.
	Business Analysis—Focus group and joint application design sessions are used to document the system requirements, business
process flows, business logic, and system data requirements.

	2.
	System Design—Software specifications are developed using object-oriented analysis and object-oriented design CASE tools,
and logical data models are developed using entity relationship diagram data modeling. Meta data are developed for each data entity.

	3.
	Architecture Design—The system hardware and software architecture is designed and documented. Then hardware and software
systems specifications and configurations are developed and finalized for acquisition.

	4.
	Implementation—The applications software is developed for the target hardware platforms and operating system environment
using object-oriented programming languages, database development tools, and fourth-generation languages. Development test beds are built for software testing. The applications software is built and
tested in increments, and the functionality grows with each build, from alpha to beta to full production. The system hardware and software are installed in the planned data centers for rollout and
acceptance of the applications software production release. The Carnegie Mellon University Software Engineering Institute's Software Capability Maturity Model (SW-CMM) best practices are
used for project management, requirements management, software configuration control, and software quality assurance.

	5.
	Growth and Maintenance—During this phase, the applications software is successively upgraded in planned build and release
cycles. Software incident reports are addressed in each build and release. Maintenance releases are developed for serious software problems that cannot wait until a planned upgrade release. 

Development Tools and Languages  

        NeuStar is using object-oriented analysis and object-oriented design CASE tools for requirements analysis and detailed software design. We use object-oriented
programming, database development tools, and fourth-generation programming languages for software development. The following table gives examples of tools NeuStar has used in the past and will use on
the usTLD project. 

O-20

 

 usTLD Software Development Tools  

	Development Tool/Language
 
	 	Purpose
 

	CASE Tools	 	NeuStar will utilize CASE tools such as Oracle CASE and Rational Rose. These tools provide full feature object-oriented analysis and design.
	

Java, C++, Delphi, SQL	
 	

NeuStar has extensive experience with, and will utilize, these development languages where appropriate to implement all business logic.
	

CORBA, RMI	
 	

NeuStar has extensive experience with, and will utilize, these Remote object protocols.
	

Java Servlets, Java Server Pages, Cold Fusion,	
 	

NeuStar has extensive experience with, and will utilize, these Web
	

CGI-script, XML, and XSL	
 	

development technologies for building Web sites and thin client applications for distribution to a wide range of users.

O-21

   O.2    Registry-Registrar Model and XRP Protocol  

        In the past, registry/registrar model and their associated protocol is a "thin" (limited amount of data) registry serving a "thick" (more
data) registrar. NeuStar will deploy a "thick registry" model, with contact and authentication details stored centrally at the Registry. Under this model, the business relationships would be
unchanged: registrants would still deal with the registrar, and the registrars would deal with the registry.

        As
part of its thick-registry proposal, NeuStar will deploy, the eXtensible Registry Protocol (XRP). The XRP protocol will accommodate both thin and thick registry models. We do not
anticipate introducing the XRP protocol until after the initial "land rush" period has ended. 

        The
XRP Protocol provides the following benefits: 

	•
	Extensible
protocol based on XML,

	•
	Utilizes
BEEP as a transport protocol,

	•
	Support
for both thick and thin registry models,

	•
	Support
for centralized contact information/centralized Whois,

	•
	Standardized
Whois service (same fields regardless of registrar's Web site),

	•
	Machine
readable Whois format (when specified),

	•
	Extensible
data-field support (registrars can add custom fields to Whois following standardized fields),

	•
	Functionally
complete (exposing all registry data via one interface),

	•
	Secure,

	•
	Non-repudiation
(no deniability),

	•
	Redundant
(duplicate requests have no adverse effect),

	•
	Real-time
XRP functions (e.g., check and register),

	•
	Near
Real-time DNS and Whois updates,

	•
	Support
for IPv6 addresses,

	•
	Standard,
centralized registrant authentication method,

	•
	Extensible
registrant authentication methods (e.g., support for digital certificates),

	•
	Simple
account transfer (between registrars, using centralized authentication),

	•
	Event
broadcasting (ability for registrars to place "listeners' on registry events), and

	•
	Rollback
support (i.e., rollback registrar transfer; not necessarily transactional). 

O-22

 

O.3    NeuStar's Database Capabilities  

        NeuStar will provide, redundant database system capable of managing large databases and high transaction processing loads reliably, with
scalable growth to accommodate change.

        The
database system supports asynchronous replication of data between two co-active Enhanced SRS data centers geographically dispersed. The benefit to the Internet community
is reliable, stable operations and scalable transaction processing throughput to accommodate Internet growth. 

        The
heart of the Enhanced SRS is its database systems, which provide not only simple data storage and retrieval capabilities but also the following capabilities: 

	•
	Persistence—storage and random retrieval of data,

	•
	Concurrency—ability to support multiple users simultaneously,

	•
	Distribution (data replication)—maintenance of relationships across multiple databases,

	•
	Integrity—methods to ensure data are not lost or corrupted (e.g., automatic two-phase commit,
physical and logical log files, and roll-forward recovery),

	•
	Availability—support for 24 × 7 × 365 operations (requires
redundancy, fault tolerance, and on-line maintenance), and

	•
	Scalability—unimpaired performance as the number of users, workload volume, or database size increases. 

        As
applications architectures such as Enhanced SRS become increasingly dependent on distributed client/server communications and processing, system designers must carefully plan where
the bulk of the data processing occurs: on the database server, applications server, or client. Our final design will distribute the processing workload in a way that maximizes scalability and
minimizes downtime. 

        This
proposal section (O.3) is divided into three major subsections: 

        O.3.1 Functional Overview—describes the characteristics of the three primary Centralized usTLD databases (i.e., size,
throughput, and scalability); database procedures and functions for object creation, editing, and deleting; change notifications; transfer procedures; grace-period functions; and reporting. 

        O.3.2 Database System Description—describes the database system components, server platforms, and scalability for the three
primary databases. 

        O.3.3 Security and Access Privileges—describes the access controls for granting and denying users and administrators access to
the databases. 

O.3.1    Functional Overview  

        As shown in Exhibit O-7, NeuStar's registry will include four major databases: 

	•
	Centralized usTLD Database—The primary function of this database is to provide highly reliable persistent storage
for all of the registry information required to provide domain registration services. The Centralized usTLD Database is highly secured, with access limited to authenticated registrars, trusted
application server processes, and the registry's database administrators. The Centralized usTLD Database, includes registrant data, registrar data, delegee data and is used to create the Whois
databases.

	•
	Billing and Collection Database—This database will provide the information required for NeuStar to render billing
and collection (B&C) services to the registrars, delegated managers, and registrants. Access to its data is limited to the trusted B&C system processes and to registry 

O-23

 

database
administrators. Customers can view billing data through a secure Web portal with a B&C Applications Programmer Interface (API). 

	•
	Whois Database—The Whois database is a searchable database that any Internet user can access to view details
pertaining to domain names. The Whois database maintains data about registrants, associated registrars/delegated managers, domain names, nameservers, IP addresses, and the associated contacts. The
Whois database is updated from the Centralized usTLD Database through an intermediate database and replication process.

	•
	Delegee Database—The delegee database maintains data about delegated managers, delegated subdomains, nameservers,
IP addresses, and the associated contacts. The delegee Whois database is created from the delegee database and is a searchable database that any Internet user can access to view details of delegated
subdomains stored in the Enhanced SRS. 

        In
addition to these databases, the registry will maintain various internal databases to support operations such as authorizing login user ids and passwords, authenticating digital
certificates, and maintaining access control lists. 

        In
implementing the Centralized usTLD Database systems, our system designers will carefully analyze the differing requirements for the three major databases and select the optimum
solution for each. Design techniques and considerations will include: 

	•
	Multiple
logical data models that we will optimize for the different types of information that each system needs to serve registrars efficiently;

	•
	Content
that will include data related not only to domain names and domain name registration but also to registrars, registrants, nameservers, Whois servers, and the Billing
and Collection system;

	•
	Differing
volumes of database transactions and database sizes;

	•
	Differing
business needs;

	•
	Differing
performance and availability requirements; and

	•
	Replication
of databases to achieve high availability and facilitate backup/recovery. 

[Exhibit O-7:
Graphic Design] 

Database Size, Throughput, and Scalability  

        The following table lists design parameters for the initial design of the three major databases. The term  scalability in the table refers
to the database's ultimate capacity expressed as a multiple of the initial design capacity in terms of size and
transaction processing power. NeuStar will closely monitor the overall performance and capacity of the database and will pro-actively make adjustments as 

O-24

 

required
to keep the database performing at optimal levels. Given technological advances, there really is no practical limit to the overall capacity of the database. 

 Database Design Parameters  

	[***]	 	[***]
	[***]	 	[***]
	

[***]	
 	

[***]
	[***]	 	[***]
	

[***]	
 	

[***]
	[***]	 	[***]
	

[***]	
 	

[***]
	[***]	 	[***]

Database Procedures and Functions  

        The database system is critical to the processing of Enhanced SRS business transactions. The Centralized usTLD database and B&C databases are accessed during many
registry transactions. If a transaction is completed successfully, the system not only updates these two databases but also the Whois distribution, Delegee distribution and Zone distribution databases
(as necessary). Below is a list of some of the functions performed by the Centralized usTLD Database and the Registry: 

	•
	Object
Creation—Domain name, and nameserver registration.

	•
	Object
Editing—Modifying domain name, information delegee, or nameserver data and creating or modifying associations.

	•
	Object
Deletion—Domain name cancellations.

	•
	Object
Existence and Information Query—Obtain information on domain name, nameserver, or contact name.

	•
	Object
Transfer—Transfer a domain name to a different registrar.

	•
	Automatic
Domain/Subdomain Renewal—Extend a domain name registration for one year.

	•
	Requested
Domain Renewal—Process a renewal request.

	•
	Grace
Period Implementation—Allow various time periods before actions become final.

	•
	Registrar/Delegee/Registrant
Administration—Add, delete, or change to a usTLD Registry user account or billing profile.

	•
	Billing
Notifications—Account-related information sent to registrars, registrants, delegated managers, and designated registry staff.

	•
	Reporting—Account
and billing information that can be viewed online or e-mailed.

	•
	Mass
Updates—Special procedures (e.g., changing a registrar's name on each of its domain name files if it is acquired by another registrar, or changing a
delegated manager's name on each of its delegated subdomains). 

        A
typical mass update is a global change of a registrar's name, which may occur when one registrar purchases another. NeuStar will design procedures for mass database changes initiated
by registrars, delegees, or other authorized entities. 

O-25

 

O.3.2    Database System Description  

        Although the four primary Centralized usTLD databases—Enhanced SRS, Whois, Delegee, and Billing—will differ, depending upon the services
they support, the Enhanced SRS on the whole, will be structured to: 

	•
	Manage
large quantities of data,

	•
	Support
applications that use data models with complex relationships,

	•
	Perform
complex operations on these objects, and

	•
	Process
large volumes of transactions from users. 

        NeuStar
forecasts that, as with most OLTP applications, the anticipated volume of Enhanced SRS transactions will have a high ratio of "reads" to "writes." We will design the databases
and applications by partitioning the workload to improve response times and scalability. 

O-26

 

Centralized usTLD Database  

        The Centralized usTLD Database will support and provide information for primary domain registration services. The following table lists the data stored in the
Centralized usTLD Database. 

 Centralized usTLD Database Data  

	Primary Element
 
	 	Details
 

	Domain Names	 	•	 	Domain Name Attributes (Status)
	

 	
 	

•	
 	

Associated Name Servers
	

 	
 	

•	
 	

Associated Registrar
	

 	
 	

•	
 	

Associated Delegated Manager
	

 	
 	

•	
 	

Associated Registrant Data
	

Nameserver	
 	

•	
 	

Nameserver Attributes (Status)
	

 	
 	

•	
 	

Associated IP Addresses
	

 	
 	

•	
 	

Associated Registrar
	

 	
 	

•	
 	

Associated Delegated Manager
	

 	
 	

•	
 	

Associated Registrant Data
	

IP Address	
 	

•	
 	

IP Address Attributes (Status)
	

 	
 	

•	
 	

Associated Nameservers
	

 	
 	

•	
 	

Associated Registrar
	

 	
 	

•	
 	

Associated Delegated Manager
	

 	
 	

•	
 	

Associated Registrant Data
	

Registrar List	
 	

Registrar Names
	

Registrars	
 	

•	
 	

Registrar Name
	

 	
 	

•	
 	

Registrar Contact Details
	

 	
 	

•	
 	

Registrar URL (Home page)
	

 	
 	

•	
 	

Registrar Whois URL (Web Port 80)
	

 	
 	

•	
 	

Registrar Whois URL (Port 43, if applicable)
	

 	
 	

•	
 	

Registrar Attributes (Status)
	

Delegated Manager List	
 	

Delegated Manager Names
	

Delegated Managers	
 	

•	
 	

Delegated Manager Name
	

 	
 	

•	
 	

Delegated Manager Contact Details
	

 	
 	

•	
 	

Delegated Manager URL (Home page)
	

 	
 	

•	
 	

Delegated Manager Attributes (Status)

O-27

 

        NeuStar
will configure the database system to provide appropriate response times. We will plan capacity to ensure that as business requirements increase and demand for domain names
grows, the system will be able to handle the workload within the agreed upon response times. 

Centralized usTLD Database Platform  

        For the Centralized usTLD Database platform, NeuStar will use a business-critical-proven, high-performance, data center computing platform with the
following characteristics: 

	•
	A
high-end online transaction processing (OLTP) server,

	•
	RISC
550 MHz CPU,

	•
	64-bit,
2- to 32-way cross-bar SMP,

	•
	8 × 8
non blocking multi-ported crossbar,

	•
	Up
to 32 GB of memory,

	•
	Up
to 19-GB I/O throughput,

	•
	Maximum
internal storage of 288 GB,

	•
	Maximum
external RAID storage of 50 TB,

	•
	Redundant
hot-swappable power supplies,

	•
	Dual-attach
Gigabit Ethernet Adapter, and

	•
	Event
management software for remote management. 

        The
Centralized usTLD Database server will use the Unix 64-bit operating system with controlled-access security. 

        NeuStar
will have vendor support agreements to keep the systems running and to repair or replace components immediately if problems occur. 

Scalability  

        In planning for growth, NeuStar will design a database system with the ability to add resources on an as-needed basis without interrupting processing.
Because database growth can occur in several areas, we will monitor each of the following parameters and plan for growth accordingly: 

	•
	Physical size—As the physical size of the database increases, so does the need for disk storage. Our database
platform and database will support extending the internal storage capacity to 288 GB and the external capacity to 50 TB. The system will permit online configuration with minimum downtime.

	•
	Memory—As the volume of users increases, so does the need for increased buffer and lock-pool storage.
The database platform will scale up to 32 GB, which is sufficient memory for supporting the system capacity.

	•
	CPUs—To handle increasing volumes of registrar requests, the database platform will scale up to 32 processors. 

Billing Database  

        The Billing database provides information for Billing and Collections services, including: 

	•
	Registrars' billing profiles—accessed and modified by the Registrar Administration function; 

O-28

 

	•
	Registrars' accounts—queried, credited, and debited while processing transactions from registrars;

	•
	Registrants' billing profiles—accessed and modified by the Registrant Administration function;

	•
	Registrants' accounts—queried, credited, and debited while processing transactions from registrars; and

	•
	Catalogs—Pricing information for different transactions; queried during the charging process. 

Billing Database Platform  

        The Billing database platform will have the following characteristics: 

	•
	A
high-end server;

	•
	RISC
550 MHz CPU;

	•
	64-bit,
2- to 6-way SMP with up to 32 GB ECC RAM;

	•
	Scalable
up to 72 GB internal disk capacities and 71 TB external RAID;

	•
	Redundant
hot-swappable power supplies;

	•
	Dual-attach
Gigabit Ethernet Adapter; and

	•
	Event
management software for remote management. 

        The
database server's operating system will be Unix 64-bit. 

        NeuStar
will have vendor support agreements to keep the systems running and to repair or replace components immediately if problems occur. 

Scalability  

        In planning for growth, NeuStar will design a database system with the ability to add resources on an as-needed basis without interrupting processing.
Because database growth can occur in several areas, we will monitor each of the following parameters and plan for growth accordingly: 

	•
	Physical Size—The database and database platform can have their storage capacity extended and systems configured
online with minimum downtime. The database platform will have the ability to scale up to 72 GB capacity, and external storage capacity up to 71 TB.

	•
	Memory—As the volume of users increases, so does the need for increased buffer and lock-pool storage.
The database platform will scale up to 32 GB, which is sufficient memory to support the system capacity.

	•
	CPUs—To handle increasing volumes of registrar requests, the database platform will scale up to 6 processors. 

Whois Database  

        Anyone can query the Whois database. Each database entity includes information on the following items for all Internet domain names registered in the usTLD: 

	•
	Domain
name,

	•
	Nameserver,

	•
	IP
address,

	•
	Registrar/Delegated
Manager, and 

O-29

 

	•
	Registrant
contact information associated with the domain name. 

Whois Database Platform  

        Each Whois server cluster will be supported by a clustered pair of database servers. The Whois database platform will have the following characteristics: 

	•
	A
high-end server;

	•
	RISC
550 MHz CPU;

	•
	64-bit,
2- to 6-way SMP;

	•
	Up
to 32 GB ECC RAM;

	•
	Scalable
to 72 GB internal disk capacity;

	•
	Scalable
to 71 TB external RAID;

	•
	Redundant
hot-swappable power supplies;

	•
	Dual-attach
Gigabit Ethernet Adapter; and

	•
	Event
management software for remote management. 

        The
database server will use the Unix 64-bit operating system with. 

Scalability  

        NeuStar will design the Whois database to grow with increasing demand over time. Because database growth can occur in several areas, we will monitor each of the
following parameters and plan for growth accordingly: 

	•
	Physical Size—The database and database platform can have their storage capacity extended and system configured
online with minimum downtime. The database platform will have the ability to scale up to 72 GB capacity, and external storage capacity to 71 TB.

	•
	Memory—As the volume of users increases, so does the need for increased buffer and lock-pool storage.
The database platform will scale up to 32 GB, sufficient memory to support the system capacity.

	•
	CPUs—To handle increasing volumes of registrar requests, the database platform will scale up to 6 processors. 

Delegee Database  

        Anyone can query the Delegee database. Each database entity includes the following information for all delegated subdomains registered in the usTLD: 

	•
	Subdomain
name,

	•
	Nameserver,

	•
	IP
address,

	•
	Delegated
manager, and

	•
	End-user
contact information associated with the subdomain. 

O-30

 

Delegee Database Platform  

        Each Whois server cluster will be supported by a clustered pair of database servers. The Whois database platform will have the following characteristics: 

	•
	A
high-end server;

	•
	RISC
550 MHz CPU;

	•
	64-bit,
2- to 6-way SMP;

	•
	Up
to 32 GB ECC RAM;

	•
	Scalable
to 72 GB internal disk capacity;

	•
	Scalable
to 71 TB external RAID;

	•
	Redundant
hot-swappable power supplies;

	•
	Dual-attach
Gigabit Ethernet Adapter; and

	•
	Event
management software for remote management. 

        The
database server will use the Unix 64-bit operating system. 

Scalability  

        NeuStar will design the Whois database to grow with increasing demand over time. Because database growth can occur in several areas, we will monitor each of the
following parameters and plan for growth accordingly: 

	•
	Physical Size—The database and database platform can have their storage capacity extended and system configured
online with minimum downtime. The database platform will have ability to scale up to 72 GB capacity, and external storage capacity to 71 TB.

	•
	Memory—As the volume of users increases, so does the need for increased buffer and lock-pool storage.
The database platform will scale up to 32 GB, sufficient memory to support the system capacity.

	•
	CPUs—To handle increasing volumes of registrar requests, the database platform will scale up to 6 processors. 

Database Administration  

        NeuStar personnel who administer and maintain the database will perform their tasks at times and intervals scheduled to ensure maximum system availability.
Typical database-administration tasks include the following: 

	•
	Monitoring
and tuning,

	•
	Creating
and deleting entire databases,

	•
	Starting
and stopping,

	•
	Backing
up and recovering,

	•
	Adding
additional data volumes,

	•
	Defining
clustering strategies,

	•
	Reorganizing,

	•
	Adding
and removing indexes, 

O-31

 

	•
	Evolving
the schema,

	•
	Granting
access,

	•
	Browsing
and querying, and

	•
	Configuring
fault tolerance. 

Database Backup/Restore  

        Proposal Paragraphs O.7 (Data Escrow and Backup) and O.14 (System Recovery Procedures) describe our proven backup/restore processes, which we will employ for the
Enhanced SRS operation. Backup frequency and logging processes will minimize data loss in case of system outage. 

Disaster Recovery  

        Each Centralized usTLD database component will asynchronously replicate its database in the other co-active Enhanced SRS Data Center. As Proposal
Paragraphs O.7 (Data Escrow and Backup) and O.14 (System Recovery Procedures) explain, in the unlikely event of a catastrophic outage at one data center, the Enhanced SRS operations will failover to
the replicate database. 

O.3.3    Database Security and Access Privileges  

        Proposal Paragraph O.10 explains NeuStar's security measures in detail. The major technical security-related controls to ensure data integrity and security
on the database platforms include the following: 

	•
	Server
operating system with access control provides protection against unauthorized access. It employs user ID and password, along with file access control lists.

	•
	Database
security with user profiles enable us to grant or deny access privileges to customers, database users, and database administrators. The controllable level of
granularity extends down to the individual data field.

	•
	NeuStar
will establish security policies and routine logging/auditing/monitoring functions to ensure that there is no unauthorized access. We will periodically review
security to ensure that the system is functioning as needed.

	•
	Access
to the database is via trusted processes on both the application server and the Billing server.

	•
	NeuStar
will establish routine auditing/monitoring features to ensure that there is no unauthorized activity, and we will periodically review our security features to ensure
that the system is functioning as needed. 

O-32

   O.4    Zone File Generation  

        NeuStar proposes generating zone files in near-real-time, thus ensuring timely synchronization of
nameservers.

        The
zone file is a flat database file consisting of the technical information that the DNS requires to function correctly: the domain name, nameserver host name, and IP address. 

        Zone file generation is the term traditionally used to describe the process of generating a zone file from the registry database,
deploying it to the primary root server, and then propagating it out to the secondary servers. 

        However,
NeuStar's model does not periodically generate a zone file and then publish the new file to a set of nameservers. This Proposal describes our process for creating updates for
the nameserver files; Section O.5 contains information about distributing and publishing the updates. To make the two sections complete and self-sufficient, each contains certain
information that is also found in the other. 

Benefits of the Proposed Solution  

        NeuStar's zone file generation and propagation processes will update zone files in near-real time within defined service levels.
Near-real-time updates provide the following significant advantages: 

	•
	They
eliminate the synchronization problems that now occur when information is modified.

	•
	They
enable us to define and monitor service levels for the maximum allowable time between zone file updates. 

O.4.1    Secure Access to Update Zone File Data  

        Under our proposed solution, the Centralized usTLD Database in the Enhanced SRS data centers store all data used to generate and distribute the zone file updates.
For security reasons, neither registrars nor internal data center staff can access this database directly; the application server tier controls all database access. Registrars/Delegees access the
database (through the application servers) using the XRP protocol via the protocol servers. The following procedures govern creating and modifying database information: 

	•
	Registrars
are solely responsible for creating, modifying, and deleting information that update the zone file. The XRP protocol is the only gateway available to registrars
for zone file editing. This protocol is accessed using the NeuStar XRP servers.

	•
	A
registrar gains access to a domain name (and associated nameserver) by registering that domain name or when the appropriate Transfer of Registrar is enacted. For a
Transfer of Registrar, access control is revoked from the losing registrar after the transfer.

	•
	Access
control to zone file data for XRP "Delete/Modify Domain Name" commands is granted only to the registrar/delegee who has management rights over the domain name.

	•
	In
the case of an XRP "Create/Modify/Delete Nameserver" command, access control is granted only to the registrar/delegee that has management rights over the nameserver's
parent domain name (i.e., ns1.neustar.us has the parent domain name neustar.us). 

        Other
proposal sections provide additional security-related information: 

	•
	Section O.5
contains information about deployment security, and

	•
	Section O.10
contains information about other security issues, including system and network security and access control authentication and authorization. 

O-33

 

Frequency of Zone File Generation  

        NeuStar will generate zone file updates (diffs) at regular intervals within defined service levels. Our solution enables us to meet any reasonable service level
merely by adding incremental hardware items and reconfiguring system software settings. 

        Any
zone file update procedure must not degrade the performance of the core registration system. NeuStar's solution will enable us to agree to service levels that guarantee the zone file
distribution database is updated within defined intervals (initially set to 15 minutes) without adversely affecting core registration operations. 

Logging and Data Backup  

        All zone files and updates are generated using information from the Centralized usTLD database. All updates are recorded as database transaction logs. Proposal
Sections O.7, O.13, and O.14 contain information about the primary database backup and escrow systems, data center replication, and data recovery procedures. 

O.4.2    Zone File Generation Architecture  

        Zone file information is stored in the Centralized usTLD Database (along with all other registry data) and replicated to a zone distribution server. The database
stored on the zone distribution server is in turn replicated out to a database at the nameserver data centers. 

Zone File Replication  

        Each time the zone distribution database is modified, and before the zone file update is replicated out to the nameserver data centers, the system performs a
series of quality assurance checks. If any quality assurance checks raise an alert, operations staff must approve the deployment before the update is sent to the nameservers. The quality assurance
checks include: 

	•
	Greater
than a pre-established maximum number of modifications since the last update, and

	•
	Greater
than a pre-established maximum number of modifications since the last update for a special set of domain names used by key e-commerce sites.
The alert threshold will be much lower for these domain names than for the previous check. 

Standards Compliance  

        Each nameserver will run software that correctly implements the IETF standards for the DNS (RFC1035, RFC2181). 

        NeuStar
expects to implement all applicable best-practice recommendations contained in RFC2870 (Root Nameserver Operational Requirements). 

O-34

 

O.5    Zone File Distribution and Publication  

        NeuStar proposes near-real-time updates of the zone file data, which will facilitate synchronization of the
nameservers as well as the monitoring of service levels.

        This
proposal section (O.5) describes the process of updating zone file information at the various nameserver data centers using information from the zone distribution servers at the two
co-active Enhanced SRS data centers. The preceding proposal section (O.4) describes how the databases on those zone distribution servers are updated. To make the two sections complete and
self-sufficient, each contains certain information that is also found in the other. 

        The
databases on the zone distribution servers will be constantly replicated over a VPN to the zone update database at each nameserver data center. Each nameserver data center will, in
turn, use its zone update database to update its zone file databases. Updating will comply with defined service levels. 

        To
ensure availability and provide scalability and redundancy, each nameserver data center will have a cluster of two or more nameservers behind a load balancer. This configuration
enables NeuStar to rapidly accommodate increases in query load by simply adding servers to the cluster at the affected nameserver data centers. 

Benefits of the Proposed Solution  

        NeuStar's zone file generation and propagation processes will update the zone files in near real time within defined service levels. Near real-time
updates provide the following significant advantages: 

	•
	They
eliminate the synchronization problems that now occur when information is modified.

	•
	They
facilitate the deployment of innovative new technologies, such as dynamic update, because NeuStar will have technical control of the nameservers. 

O.5.1    Locations of Data Centers Housing Zone File Nameservers  

        Exhibit O-1 (shown previously) provides the locations of the three nameservers. We will monitor network utilization and geographic traffic
flows and will deploy new nameservers in additional geographic locations when appropriate. 

        At
the nameserver data centers, a zone update database constantly receives replication update packages from the zone distribution database server at the Enhanced SRS data centers. This
zone update database is not "hit' when the nameservers process requests; the nameservers use it only to update their zone file databases. 

        NeuStar
will deploy a modified version of BIND. It has been modified to remove capabilities not required for TLD root server operations and to speed up the remaining functions. The DNS
software will comply with the latest IETF standards [RFC1035, RFC2181]. 

O.5.2    Zone File Publication/Update Architecture  

        As we introduced in Proposal Paragraph O.4, NeuStar proposes near-real-time update of the zone file. That paragraph discusses how
the zone file information is stored in the Enhanced SRS master database and then replicated to a zone distribution server database. 

        Exhibit O-8
illustrates the zone file distribution process. The database on the zone distribution server at the Enhanced SRS data center is constantly replicated over
our VPN to the zone update database at each nameserver data center. The update packages are compressed, encrypted, and sent with an appended checksum. 

O-35

 

        Every
update package includes a checksum key, which is a generated checksum of the entire database up to and including modifications in that package. Each time a package updates a
nameserver, the checksum is compared to the final state of the zone file data to ensure that the nameserver zone file corresponds to the zone file in the Enhanced SRS data center's database. If the
checksums indicate an error, the nameserver asks the Enhanced SRS data center to replicate a full zone file to the
nameserver. The update package replication process means that the full zone file should never need to be redeployed; however, NeuStar will provide this capability to recover from an unforeseen event.
Should this capability be needed, propagating zone file updates may result in a 60-minute delay. 

        Exhibit O-9
depicts how each nameserver updates its zone file databases from its zone update database. 

Frequency of Zone File Publication/Update  

        Any technical solution that includes real-time DNS updates must recognize that the most important function of the nameservers is responding to DNS
queries. This requirement outweighs real-time updating of the zone file. NeuStar's solution is based on this reality. Our real-time update process includes establishing and
monitoring key parameters. 

        [Exhibit O-8 &
Exhibit O-9: Graphic Design] 

Monitoring and Logging  

        Our central network management system will log all modifications to the Centralized usTLD database, all zone file update actions, and all attempts at intrusion or
other security-related events. 

Standards Compliance  

        Each nameserver will run software that correctly implements the IETF standards for the DNS (RFC1035, RFC2181). 

        NeuStar
expects to implement all applicable best-practice recommendations contained in RFC2870 (Root Nameserver Operational Requirements). 

O-36

 

O.6    Billing and Collection System  

        NeuStar's proven experience in successfully selecting, implementing, and operating complex Billing and Collection (B&C) systems for
communications and domain name registry services ensures that our usTLD registry billing services will be feature rich, accurate, secure, and accessible to the entire customer
base.

        The
B&C system will maintain customers' accounts, create account statements, and audit and track information for both customers and the industry. 

        The
fundamental goal of the system is to maintain the B&C data and create reports that are accurate, accessible, secured, and scalable. B&C will enable detailed transaction-based
charging to the customers, based on extensive resource accounting and usage data recording performed in the Registry System. The B&C system must produce timely and accurate account statements and
billing reports that are accurate, easy to understand, and contain only clearly defined charges from the Catalog of services and prices. Such account statements are ultimately more economical because
they are less likely to provoke costly billing disputes. 

        NeuStar
offers a simple B&C process as depicted in Exhibit O-10. It is based on debit and/or credit card accounts established by each of our clients. We will withdraw
all domain registration service payments from the incurring customer's debit or credit card account on a per-transaction basis. We will provide fee-incurring services (e.g.,
domain registrations, registrar transfers, and domain renewals) for customers only so long as their accounts are in good standing. NeuStar's B&C system will be sufficiently flexible to adapt to
different billable events, grace-period implementations, and pricing structures. 

        NeuStar's
B&C system will be located at the two redundant Enhanced SRS data centers in Virginia and Illinois. These systems will handle the key B&C functions, including: 

	•
	Debiting
and crediting registrars' accounts,

	•
	Initiating
low-balance notifications,

	•
	Performing
credit card transactions,

	•
	Enabling
customers to view their accounts, and

	•
	Tracking
and reporting historical information. 

[Exhibit O-10:
Graphic Design] 

O.6.1    Technical Capabilities and Characteristics  

        NeuStar will customize an off-the-shelf product to ensure data processing accuracy, accessibility, flexibility, and scalability to
accommodate increasing transaction volumes and additional billable events. Our finance and technical experts are experienced in customizing systems to evolve smoothly from performing simple to more
complex tasks, and from small-scale to large-scale operations. We selected this solution after conducting a detailed analysis of the options for administering the registry's B&C system. Our proposed
system will: 

	•
	Meet
all registry B&C objectives, including

	•
	Generating
the large amount of detailed resource accounting information needed to support detailed usage-based charging of registrars, delegees, and registrants

	•
	Tracking
and reporting historical information

	•
	Be
cost effective

	•
	Be
operational within the scheduled implementation dates. 

O-37

 

Billing and Collection System Description  

        Exhibit O-11 illustrates the major components of the B&C system and its interfaces with other Enhanced SRS subsystems. 

        B&C database—This database, which is separate from the Registry's Centralized usTLD Database, contains the data shown in the
following table. Proposal Paragraph O.3 discusses the capabilities, management, administration, and backup of all databases, including the B&C database. This subsection discusses only the
design aspects of the B&C database. 

        Transaction Processor—This processor, which responds to inputs from the external application server and from the B&C
operations GUI, is the only component that has access to update the B&C database. The transaction processor will process transactions in real time, responding to API calls from application servers,
and also will process transaction log files obtained from external servers. The transaction processor has two main subcomponents: 

	•
	Customer Profile Administrator—The component that responds to the customer-administration component of the
application server, and 

O-38

 

	•
	B&C Processor—The component that processes all domain registration related requests and other billable events
from external servers. 

 B&C Database Contents  

	Primary Element
 
	 	Details
	 	Primary Element
	 	Details

	Catalog	 	•	 	Transaction type	 	Transaction data	 	•	 	Transaction ID
	

 	
 	

•	
 	

Amount charged	
 	

 	
 	

•	
 	

Customer ID
	

 	
 	

•	
 	

Start date	
 	

 	
 	

•	
 	

Transaction type
	

 	
 	

•	
 	

End date	
 	

 	
 	

•	
 	

Start date
	

 	
 	

•	
 	

Additional information	
 	

 	
 	

•	
 	

End date
	

 	
 	

 	
 	

 	
 	

 	
 	

•	
 	

Domain name
	

 	
 	

 	
 	

 	
 	

 	
 	

•	
 	

Registrant contact information
	

Customer Information	
 	

•	
 	

Customer name	
 	

Account history	
 	

•	
 	

Customer ID
	

 	
 	

•	
 	

Customer ID	
 	

 	
 	

•	
 	

Amount received
	

 	
 	

•	
 	

Customer e-mail address	
 	

 	
 	

•	
 	

Date of amount received
	

 	
 	

•	
 	

Customer address	
 	

 	
 	

•	
 	

Transaction type
	

 	
 	

•	
 	

Preferred payment method	
 	

Account Information	
 	

•	
 	

Customer ID
	

 	
 	

•	
 	

Credit card information	
 	

 	
 	

•	
 	

Current Amount
	

 	
 	

•	
 	

Account setup date	
 	

User Administration	
 	

•	
 	

User ID
	

 	
 	

•	
 	

Operational date	
 	

 	
 	

•	
 	

User role
	

 	
 	

•	
 	

End date	
 	

 	
 	

 	
 	

 

[Exhibit O-11:
Graphic Design] 

        Monitor and Notifier—This component monitors the registrars' accounts for sufficient funds and monitors domain name
expirations and renewals. When it detects actionable items, it notifies the transaction processor and the registry's Customer Service organization. 

        Report Generator—This component will generate monthly account statements and various reports, including annual reports. This
is also the component that Customer Service will use to generate custom reports requested by a customer. After generating custom reports in a batch process, the report generator sends them to the FTP
directory, where they are stored for the customer to download. 

O-39

 

Billing and Collection System Interfaces  

        As Exhibit O-11 above indicates, the B&C system will have four types of interfaces: 

        Application Programmer Interfaces (APIs)—That connect billing functionality with selected non-B&C functions of the
registry (e.g., registrar administration, domain registration, accounting system entries, and e-mail processes). The APIs, which connect to the application server, will provide good query
capabilities, triggers for billable events, and a means for customizing or extending B&C functionality. The APIs will enable the B&C system to perform B&C functions in near real time (i.e., at the
same time that the registry system is processing the request). The APIs will be well defined, including parameters used and resultant status codes. All error codes will be well documented, and B&C
activities will be logged for tracking and audit purposes. API functions include the following: 

	•
	Validating
the application using application ID & password,

	•
	Accessing
a customer's account to verify its balance and perform a financial transaction (credit card or debit account),

	•
	Adding
a domain registration,

	•
	Canceling
a domain registration,

	•
	Transferring
a domain registration,

	•
	Requesting
a custom report, and

	•
	Administering
a customer's billing profile. 

        GUI Client—For the B&C system's registry operations personnel, who will use this interface for system administration and
reporting functions, including: 

	•
	Establishing
and administering customer accounts;

	•
	Administering
B&C functionality, including making adjustments; and

	•
	Generating
routine and special reports. 

        Secure Web-based Portal—That enables customers to use readily available Web browsers (Netscape Navigator 4.0 or
above, or Microsoft Internet Explorer 4.0 or above) to
monitor their account balances and view reports over the Internet. Using this interface, customers can view the balance in their debit accounts, their credit card transactions, and their domain
registration records in detail. Customers are granted permissions via the database security features to access data pertaining to their own accounts, but they cannot access data from other customers'
accounts. Customers also are able to select the interface by which the query or report will be delivered; depending upon the type of report or query, the available interfaces can include
on-screen, FTP, or e-mail. The interface will be by way of a secure network using the Enhanced SRS Web server, HTML, and an off-the-shelf reporting
tool. Features of the Web GUI include: 

	•
	Open,
non-proprietary, standards-based GUI technology (http + SSL);

	•
	Economical,
readily available client software for users;

	•
	Secure
access;

	•
	Flexible
design;

	•
	Online
help;

	•
	Consistent
presentation style;

	•
	Ease
of navigation, with menu-type options; and 

O-40

 

	•
	Data
entry checking. 

        Transaction Log Files—Are automatically created by and transferred from external systems such as the application server and
database systems. 

Billing and Collection Procedures  

        The B&C system processes data that are generated during the following three types of procedures: 

	•
	Customer
administration—The B&C system will manage the B&C profile for customers, along with the account and contact information.

	•
	Transactional
services—Actions that trigger a B&C event. Customers' requests result in "transactions" at the application level and "events" in the B&C process.

	•
	Non-transactional
services—Actions including balance forecasting and account balances. 

O-41

 

        The
following tables provide details of each type of process flow. Where they state that the B&C system sends a special notification to a customer, it also sends a copy to the usTLD
Customer Service organization. 

 Registrar Administration  

	Function
 
	 	Billing and Collection Process Flow

	Initial Account Setup	 	Registry receives the registrar's Registry Service Agreement and the license fee.
	

 	
 	

Registry establishes an account in the B&C system, enters all contact information, but account status is non-operational.
	

Operational Account Setup	
 	

Registry verifies registrar's acceptability and invoices for the annual maintenance fee.
	

 	
 	

Registry receives maintenance fee payment and changes account status to operational.
	

 	
 	

Registry notifies registrar to prepay the established debit account or collects credit card information
	

Debit Account Prepayment	
 	

Registry receives customer's payment, opens debit account, and credits received amount to that account.
	

Change in B&C Profile	
 	

Registry receives the request. If registry approves, it updates customer's B&C profile in B&C system.
	

Credit Extension	
 	

Registry receives the request. If registry approves, B&C system extends the credit.
	

Change in Payment Methods	
 	

Registry receives the request. If registry approves request, B&C system records the change.

        The
following are the transactional services recognized by the B&C system: 

	•
	Add
Domain,

	•
	Cancel
Domain,

	•
	Renew
Domain (Customer Request),

	•
	Renew
Domain (Automatic),

	•
	Cancel
after Automatic Renew (Customer Request),

	•
	Transfer
Registrar,

	•
	Mass
Updates, and 

O-42

 

	•
	Custom
Reports. 

        The
following are the non-transactional services recognized by the B&C system: 

	•
	Annual
Maintenance Fee,

	•
	Low
Account Balance,

	•
	Insufficient
Funds,

	•
	Balance
Forecasting,

	•
	Account
replenishment,

	•
	Credit
card transaction failure,

	•
	Monthly
Statements, and

	•
	Online
B&C Reports. 

O.6.2    Security  

        Proposal Paragraph O.10 provides extensive details about security issues, such as system, network, and physical security and specific issues, such as
access control, authentication, and authorization. This subsection discusses only security provisions that are specific to B&C. Like the overall registry system, the B&C system will implement security
at the Network, System, and User levels, as follows: 

        Network-level Security—The primary network-level communications technology underlying the B&C system is the IP protocol. The
only interfaces that have access to the B&C system are the secure Web GUI to monitor account status and the FTP server to download reports. A firewall forms the secure interface between our secure
internal network and the untrusted Internet. Firewalls use filters to permit or deny packet flow on the basis of the origin and/or destination of the packet's addresses and ports. 

        Users
who want to obtain access to the secure Web portal that we provide to the registrars must first obtain access to the secure Web server within the Enhanced SRS. When the user's Web
browser attempts to establish an https (secure Web application protocol) session with the registry, our system initiates the SSL (secure sockets layer). Part of the initialization sequence is a public
key exchange or identification. Once the SSL initialization is complete, it establishes a secure, encrypted channel between the user's Web browser and the registry's Web server, and exchanges digital
certificates to
ensure the integrity and authenticity of the session. The use of a secure Web browser/server ensures that no clear text, including passwords, is sent over the public or shared data network. 

        System-level Security—Secure user login facilities ensure that secure Web server users are fully authorized and authenticated.
The Enhanced SRS secure Web server presents a login menu on the user's Web browser. The login menu includes 20 lines of warning message stating that this is a private computer system and authorization
is required for access. The default warning message will be: "NOTICE: This is a private computer system. Unauthorized access or use may lead to prosecution!" 

        When
users attempt to log in to the secure Web server, they must enter their user ID and their password. The login/password information forwarded back to NeuStar's usTLD Web server is
encrypted through the SSL channel previously established. 

        User-level Security—Every B&C system user (individual and application, external and internal) has a unique user
login account on the system, with unique user identification codes (user IDs) and passwords to authenticate users and an access control list to control their access to system resources and
applications. User profiles are set up and maintained in the database system so that users' access to the B&C system is controlled by their user profile and the access privileges granted therein.
NeuStar 

O-43

 

will
establish and maintain well-defined security procedures for adding and deleting users and modifying their logon account, access control lists, and user profile access privileges,
depending on the user's functional role. The following subsection contains additional information about user roles and privileges. 

O.6.3    Access Privileges  

        The B&C system and network employ multi-tiered access control to ensure that all B&C resources—such as transactions and data—can be
accessed and used only by authorized users. As previously discussed, access to the proposed B&C system via the network is fully secured behind a perimeter firewall and user ID and password system,
while physical access is controlled using electronic keys and palm readers. Once authorized users gain access to the system, their privileges are controled by the operating system access control lists
and the database system user profile that determines what functions, system resources, and data the users are allowed to access and use. Access privileges are broadly defined and controlled for the
following user groups: 

	•
	Registry
employees, and

	•
	usTLD
customers. 

        The
following subparagraphs discuss the access privileges of each group. 

Registry Employees  

        Only internal usTLD registry staff members using cardkeys can gain access to the registry facility. Registry employees who are authorized to access the B&C system
do so using workstations connected through the registry LAN. Except for the system administrators, these employees access the system using the B&C client interface, which will be established
specifically for staff members to perform billing adjustments, maintenance, and related functions. 

        Each
internal user of the B&C system is also associated with a user role that will permit or deny access to different functions in the B&C system. The System Administrator will create
the roles that allow users to access certain functionality. Initially, we expect to define user roles within NeuStar's B&C-operations organization as follows: 

	•
	System
Administrators perform system upgrades, maintenance, and user administration. 

O-44

  

	•
	B&C
System Administrator configures the B&C system (e.g., user groups and their access rights, batch-process schedule, and configurable business rules).

	•
	B&C
System Operator establishes users, monitors back processes, provides system support, and monitors and corrects billing errors.

	•
	Customer
Service personnel view a registrar's billing history and collect information for the B&C manager.

	•
	B&C
clerks create transactions, such as invoices and collections, but do not make adjustments.

	•
	B&C
Manager creates adjustments, catalog changes, and customer changes.

	•
	B&C
Database Administrator performs mass database updates. 

Customers  

        Customers have only view access to their B&C account status, account statements, and reports. They have to contact B&C personnel within the registry's Customer
Support organization for any billing adjustments, custom reports, or special arrangements. 

        Query Capabilities—The Web GUI will provide authorized registrars with the ability to query the B&C database for information.
As previously described, to access the Web GUI, the registrar must obtain network access to the registry Web server and then proceed through the identification and authentication process using a valid
logon ID and password. A registrar's access to the B&C information is limited to his own accounts; the registrar is denied access to the information about any other registrar's account. The Web GUI
supports the following standard queries and reports: 

	•
	List
of all domain names owned by the customer,

	•
	Account
balance,

	•
	Monthly
account statements,

	•
	List
of all domain names with renewal dates within a defined period, and

	•
	Detail
transaction report for defined period. 

        Customers
can submit nonstandard queries or requests for special reports by contacting NeuStar's Customer Service organization via e-mail, phone, or fax. Customer Service
will place any custom reports on a secure FTP server from which the requesting customer can download them. 

        Adjustments—For billing issues or adjustments in profile or account statements, customers must contact NeuStar's Customer
Service organization via e-mail, phone call, or fax. The B&C Manager has the capability to perform any billing adjustments or similar services requested by a customer. 

        Notifications and Statements—The registry will e-mail to each customer a detailed monthly transaction statement,
an account summary, and a detailed list of all fee-incurring charges. In addition, the B&C system will automatically e-mail "Low Account Balance," "Insufficient Funds," and
"Credit Card Transaction Refusal" notifications to any customer when needed. 

O.6.4    Backup and Recovery  

        We will employ the same backup and recovery procedures for the B&C system that we use for the overall registry system. Proposal Paragraph O.7 provides
detail on the following procedures: 

	•
	We
will perform daily backup to DLT tapes, which will be stored in a secure off-site location.

	•
	We
will also perform periodic archives of history files and data, which we will also store in a secure off-site location. 

O-45

 

        If
the B&C system fails (i.e., the API interface to the application returns an "Error status"), a built-in recovery mechanism will ensure that transactions and data are not
lost. The application server will log all undeliverable B&C transactions, with transaction identifiers, to an internal file. After the problem is corrected, the file will be transferred to the B&C
system for processing. 

O.6.5    Billing and Collection Audits  

        NeuStar will provide the infrastructure to collect all data needed for accounting and auditing reports that meet commercially accepted standards and will provide
this data, as appropriate, to COTR-designated auditors. Data will be available for the current fiscal year and for an agreed number of preceding years. NeuStar will assist
COTR-designated auditors by providing all required statements and reports. Annually, NeuStar's internal auditors will audit the registry's B&C system, records, and supporting documentation
to verify the accuracy of billing for usTLD services. 

O-46

 

O.7    Data Escrow and Backup  

        NeuStar will back up the databases in our data centers in Virginia and Illinois and will regularly place escrow copies of the backups in secure
off-site locations. These procedures are essential elements of our realistic plans for continuity of operations in the event of system failures and natural or man-made
disasters. 

        The
goal of any data backup/recovery procedure is full recovery from failures without any loss of data. Data backup strategies handle system hardware failures (e.g., loss of a processor
or one or more disk drives) by reinstalling the data from daily backups, supplemented by the information on the "before" and "after" image-journal backup files that the database creates. 

        The
conventional strategy for guarding against loss of the entire facility because of fire, flood, or other natural or man-made disaster is to provide off-site
escrow of the usTLD data in a secure storage facility. Even when successful, this recovery strategy does not prevent the loss of a certain volume of transactions between the time the data were backed
up and the occurrence of the disaster. Users are subject to denial of service during the time required to recover the data center database and/or reestablish operations at an alternate disaster
recovery site. Relocating the data center normally requires at least 24 hours, and the escrowing of backups often is done only weekly, meaning that a disaster could result in substantial loss
of both services and data. 

        NeuStar's
backup solution goes a step further. We propose two co-active Enhanced SRS data centers, each capable of handling the entire workload should a major system failure
or natural or man-made disaster occur at the other. The transactions from each data center are replicated in real time to the other over redundant high-speed Virtual Private
Network (VPN) telecommunications links. Each Enhanced SRS data center also conducts independent backups, as described in the following paragraph. Since the two Enhanced SRS data centers are
co-active, our backup strategy maintains continuity of operations and enables full recovery of all transactions, even in the event of multiple hardware failures. 

O.7.1    Frequency and Procedures for Backup of Data  

        Each co-active data center independently implements a zero-downtime/zero-impact incremental data backup each day and a full
data backup weekly. We place escrow copies of the backup tapes in a secure off-site storage facility operated by a third party whose business is data escrow. We copy static data (e.g., the
operating systems, DNS software, and applications software) to CD-ROMs for quick reload, should that become necessary. We back up to DLT tape any dynamically changing files (e.g.,
log
files vital to system maintenance and operation, database files, database-journal files, and software configurations). Weekly, we perform full-system backups to DLT tape of all databases
identified in Section O.3 (Enhanced SRS Database, Whois, Billing). 

        Each
data center uses online zero-downtime/zero-impact backup procedures that include the following four steps: 

	1.
	The
database is put into backup mode to guarantee a consistent version of the data on the snapshot copy that is written to a RAID disk array for subsequent (slower speed) copying to
tape. While the database is in backup mode, the XRP, Whois, and Billing applications continue to function and to access the data. The database normally is in backup mode for only about 5 to 10
minutes.

	2.
	The
backup software writes the data to the RAID disk array.

	3.
	The
backup software, which is located on a backup server independent from the application servers, creates the backup DLT Tape copy from the snapshot copy on the RAID disk array.

	4.
	When
the backup is finished, the DLT Tapes are transported to the secure escrow facility. 

O-47

 

O.7.2    Backup Hardware and Software Systems  

        Exhibit O-12 depicts the backup/recovery hardware and software of the Enhanced SRS data centers. Each data center's system includes two backup
servers with DLT robotic tape libraries. The data backup system uses the DLT IV data cartridge and the DLT 5 data format. To achieve zero-downtime/zero-impact backup, we use a
RAID disk array and a high-speed fiber channel bridge interconnect to the robotic tape libraries. The backup server copies not only the database server's backup files to the disk array, as
discussed in the four-step process already described, but also the backup files of the cluster servers.
During the few minutes this process requires, applications still have access to the cluster servers and database server. Then the backup server copies the files to the DLT robotic tape device. 

        Because
of the criticality of the database, NeuStar proposes a fully redundant database management system. We will configure the database system as two independent database
servers—primary and backup—with synchronous replication using two-way commits to maintain database synchronization. If one database server fails, the database
system is sized so that the second server can process the entire load without degradation while the primary server is restored to service. 

        We
will transport both daily incremental backups of dynamically changing data and the weekly full backup to a secure escrow agent to be selected with the concurrence of the COTR. 

[Exhibit O-12:
Graphic Design] 

O.7.3    Procedures for Retrieval of Data and Rebuild of the Database  

        We maintain copies of the DLT tapes holding incremental data backups in a three-tape rotation: 

	•
	One
DLT backup tape is in transit to the secure escrow facility.

	•
	A
second DLT tape is in storage in the secure escrow facility.

	•
	The
third DLT tape is in the data center for reuse. 

        The
full backup tapes are maintained in a two-tape rotation, with one tape at the secure escrow facility and one at the data center for reuse. Copies of the static data
CD-ROMs for the operating systems and applications are also maintained at the escrow facility. 

        Should
the primary database server experience a catastrophic crash that necessitates a lengthy recovery process, data center operations continue seamlessly on the backup database server
that replicates all the data in the primary server. After the failed database server is repaired, we recover its data using the full backup tape and incremental backup tape that is retrieved from the
escrow facility. We first restore the full backup files, and then we restore the incremental files. We then synchronize the recovered database to the primary database. This procedure recovers the
database to the last complete transaction processed by the primary database. 

        This
backup procedure enables NeuStar to meet the service level agreements required for continuous availability and near-zero unplanned downtime, thereby improving the
stability of the Internet, enhancing public confidence, and improving customer satisfaction. 

O-48

 

O.8    Whois Databases for Both Registrars and Delegated Managers  

        NeuStar proposes a central, authoritative Whois service that will provide the Internet community with consistent, timely, and accurate
information about Registrants and delegated Managers.

        Whois
is a database of information about Internet domain names. NeuStar's proposed registry will maintain a state-of-the-art, near
real-time Whois service that will make this information available to registrars and delegees on the common Whois port (Port 43) as well as through a NeuStar public website. With a
simple wrapper around NeuStar's Whois service, these registrars and delegees will have the ability to control their own Whois offering, complete with its own look and feel and branding. Our registry
will store all information relating to Whois data entities, including contact and authentication data. This section covers both the Whois Database (Registrants) and the Delegee Whois database. The
term Whois implies both services 

        The
Whois service is intended as a directory service for registrants, as well as for any other individuals and businesses that want to query details of domain names or related data
stored in the registry. Our Whois data will be available in both conventional and machine-readable format, facilitating automation. 

        In
addition to providing the Whois directory service to registrars and delegees, NeuStar will also have the ability to provide the service directly to the Internet community via our Web
site. 

Benefits of Proposed Solution  

        NeuStar's proposed solution, which centralizes the Whois data and provides its own access, as well as access via registrars and delegees, provides the following
benefits: 

	•
	Central
location for all authoritative usTLD registration data,

	•
	Standard
protocol accessible over port 43 for registrars and delegees,

	•
	Consistent
format (fields and formatting) for all users,

	•
	Machine-readable
format (promotes automation),

	•
	Near
real-time update, and 

O-49

 

O.8.1    Whois Service Functional Description  

        The Whois service will accommodate queries regarding the data entities listed in the following table. 

 Whois Data Entities  

	Entities
 
	 	Fields
 

	Domain names	 	Attributes (Status)
	

 	
 	

Associated nameservers
	

 	
 	

Associated registrar Associated Delegated Manager
	

 	
 	

Associated registrant data
	

Nameserver	
 	

Attributes (Status)
	

 	
 	

Associated IP addresses
	

 	
 	

Associated registrar Associated
	

 	
 	

Delegated Manager
	

 	
 	

Associated registrant data
	

IP Address	
 	

Attributes (Status)
	

 	
 	

Associated nameserver
	

 	
 	

Associated registrar
	

 	
 	

Associated Delegated Manager
	

 	
 	

Associated registrant data
	

Registrar List	
 	

Registrar name
	

Registrars	
 	

Registrar name
	

 	
 	

Registrar contact details
	

 	
 	

Registrar URL (Home page)
	

 	
 	

Registrar Whois URL (Web Port 80)
	

 	
 	

Registrar Whois URL (Web Port 43, if applicable)
	

 	
 	

Attributes (Status)

Machine-Readable Format  

        NeuStar's standardized Whois format will facilitate automated parsing of Whois information.

        Because
the viewable data could be modified over time (e.g., new fields could be added), a robust and formalized encoding mechanism is needed to provide the
non-Registrar/Delegee community with reliable automated access to Whois data. 

        For
example, an organization tracking trademark infringement might want to acquire the Whois data, automatically parse it, and store it in a tracking system. To accommodate such
organizations, the 

O-50

 

Whois
information must be presented in a formal, way that is compatible with automated processing. To accomplish this, we will present the Whois data in a readable format. 

Advanced Search Capabilities  

        Per COTR requirements, the Whois database will support using multiple string and field searching. Boolean searches based on any combination of Whois fields will
be accommodated. 

Data Filtering  

        In order to accommodate any data access restrictions that may arise, either immediately or in the future, NeuStar will implement the capability to filter viewed
data based either on the capabilities/profile of the requestor or the query type. This will allow NeuStar to conform to any data privacy requirements imposed on the Whois data. 

Bulk-Access Program  

        NeuStar proposes to provide a data mart that will give users the ability to download the Whois database, while limiting the recipient's conditions of use. 

        The
proposed data mart bulk-access program would: 

	•
	Reduce
the load that data mining could impose on the core Whois service,

	•
	Contractually
limit subscribers in the ways they can use the data,

	•
	Provide
the entire database in a format that facilitates data mining, such as conducting trademark searches, compiling industry statistics, and providing directory services. 

        Both
the registry and the registrars/delegees will have the ability to conduct the actual bulk-access program. Data will be exposed only within the privacy restrictions
imposed by the usTLD Administrator, or by law. 

        Each
full and incremental data set will consist of an XML document meeting the content and format requirements, as agreed by the Registry and the accessing customers. Once the XML
document is generated, the following preparation steps will be performed: 

	•
	The
XML document will be placed in a file named to reflect the date and whether the file consists of incremental data or full data.

	•
	The
Registry Operator may optionally split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1 GB each (except the final file). If
files are split, an MD5 file (produced with MD5SUM or equivalent) will be included with the resulting files to isolate errors in case of transfer fault. The Registry Operator may optionally compress
the document using the Unix GZIP command (or equivalent) to reduce the file size.

	•
	The
file(s) will then be encrypted and signed using PGP version 6.5.1 or above, with a key of DH/DSS type and 2048-/1024-byte length. The Data
Recipient's public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be exchanged between the Registry Operator and the
Designated Recipient by e-mail, physical delivery of floppy diskettes, or other agreed means. 

        Once
prepared, data sets will be provided either by Internet File Transfer Protocol (FTP) or, at the option of either the Registry Operator or the Designated Recipient, by writing the
full data set to DAT tape (or other media mutually agreed by Registry Operator and the Designated Recipient) and sending it to the Designated Recipient by expedited delivery service (such as FedEx or
DHL). 

O-51

 

O.8.2    Whois System Architecture  

        NeuStar will deliver a Whois service that incorporates near-real-time update, scalable infrastructure, and multiple layers of redundancy.
We will initially deploy the Whois servers at the two co-active Enhanced SRS data centers shown previously in Exhibit O-1. The software architecture will enable us to
deploy Whois infrastructure to any number of additional NeuStar data centers. As the registry grows, we will have the ability to deploy additional Whois infrastructure as appropriate to increase
geographic dispersion, enhance the level of service in particular geographic regions, and reduce the load on the Enhanced SRS data centers. 

        Exhibit O-13
illustrates the Whois architecture. At each Whois site, incoming queries are distributed by a load balancer to a cluster of Whois servers that are, in
turn, connected to a backend database cluster. This configuration will provide both redundancy and scalability through the addition of servers to either cluster. 

        Each
Whois server will cache common requests in memory and query the back-end database cluster only on a cache miss. We can configure the duration that Whois information is
cached before being deleted (e.g., 10 minutes); after deletion, the server must query the database for the information. Each Whois server will be configured with at least 2 GB of
high-speed memory, sufficient to hold at least one million of the most commonly queried Whois records. 

        Exhibit O-14
depicts the update of the Whois databases. As the Central usTLD database is updated, the system will also update the Whois distribution database server in
near real time. This database will be replicated to the Whois databases. Replication between data centers always occurs over a VPN or a dedicated link, and the registry will digitally sign update
packages. 

        The
proposed Whois service offers the following benefits: 

	•
	Service
can be scaled by adding servers to each Whois cluster,

	•
	Databases
can be scaled by adding machines to each database cluster,

	•
	Service
can be scaled by deploying Whois infrastructure to additional data centers,

	•
	Inherent
redundancy ensures high availability,

	•
	Update
process ensures near-real-time availability of the latest information, and

	•
	Caching
of common queries provides superb response time. 

[Exhibit O-13:
Graphic Design] 

[Exhibit O-14:
Graphic Design] 

O.8.3    Network Speed and Proposed Service Levels  

        The potentially large volume of Whois queries places a significant network connectivity burden on the registry. Based on the assumption that each Whois query will
generate approximately 10 Kbits of network traffic, we will use the following engineering guidelines for provisioning bandwidth: 

	•
	Initially,
we will provide 10 Mbits per data center. The total of 20 Mbits will support approximately 2,000 queries per second (approximately 172 million requests per
day).

	•
	As
the volume of registrations grows, we will extend the service at a rate of 10 Mbits per one million domain name registration records under our management. For example,
when the registry manages 5 million domain names, we will dedicate 50 Mbits of Whois bandwidth, which will support nearly 450 million Whois queries per day. 

        These
guidelines will be compared with actual usage data and adjusted accordingly. 

O-52

 

        We
will engineer the Whois service to provide the following average service levels: 

	•
	150 million
queries per day (90% cache hits and 10% cache misses, which must be forwarded to a database file). We will increase this query service demand, based on
the total number of domain name registrations managed by the registry, as previously discussed.

	•
	200-millisecond
latency for cache hits (after the request reaches the data center).

	•
	500-millisecond
latency for cache misses (after the request reaches data center). 

        We
will configure the Whois service to limit connections based on the following criteria: 

	•
	1,000
queries per minute from any single IP address,

	•
	20,000
queries per minute for requests originating from designated registrar/delegee subnets, and

	•
	An
"acceptable use" policy that we will negotiate with COTR and the registrar/delegee community. 

        We
will scale the exact number of Whois and database servers deployed in each cluster and at each data center to maintain the specified service levels. 

O-53

 

O.9    System Security  

        NeuStar is currently operating successful data centers for various telecommunications and domain name registry services. This experience has familiarized us with
security risks, as well as with the most current and effective means of thwarting such risks. The COTR can be assured that our comprehensive security provisions will protect the usTLD infrastructure,
operations, and data. 

        Enhanced
Shared Registration System (Enhanced SRS) and nameserver data centers are subject to a wide range of security threats, including hacking, break-ins, data tampering,
denial of service, and physical attacks against the facility. The recent denial-of-service attacks against important government and dot-com sites point to the
technical capabilities of some hackers and the lengths to which they will go to attack the Internet community. Further, because the Registry will contain proprietary data from competing registrars,
security procedures must incorporate user authentication procedures that ensure that each registrar's files are available only to its own personnel. 

        Failure
to address these security threats creates the risks of unscheduled down time and the disruption or denial of services. 

        This
section describes system security features that we will implement in our networks, servers, and applications for the Enhanced SRS data centers and nameserver data centers. 

O.9.1    System Security  

        NeuStar offers the COTR comprehensive system security for our networks, servers, applications, and customer support services. Our security architecture is a
policy-based, multi-tiered structure based on industry standards and on evolving new IEFT standards for registry-to-registrar security and secure DNS. Our solution integrates
the
following security features to provide assurance that multiple security threats or attacks will be unsuccessful: 

	•
	Perimeter
protection for Whois and DNS applications;

	•
	Controlled
access at the server operating systems;

	•
	Applications-level
security features for XRP, Billing & Collection, and customer service applications;

	•
	Connection
security;

	•
	Data
security;

	•
	Intrusion
detection;

	•
	User
identification and authentication;

	•
	Continuity
of operations; and

	•
	Physical
security. 

O-54

   O.9.1.1 Enhanced Shared Registration System Data Center Security  

        The Enhanced SRS provides three layers of security to protect the registry subsystems: (1) network security, (2) server
security, and (3) application security. Each security layer addresses a specific security threat as discussed below.

Network Security  

        Edge routers, firewalls, and load balancers provide perimeter protection for the data center network and applications systems, guarding against unauthorized
access from the Internet. 

	•
	Edge Router—The first security layer is the edge routers, which employ IP-packet filtering.

	•
	Firewall—The second layer of perimeter security is a firewall that provides policy-based IP filtering to protect
against system hacks, break-ins, and denial-of-service attacks. The firewall also includes network-based intrusion detection to protect against Internet hackers.

	•
	Load Balancer—The third layer of protection is provided by load balancers within each data center. Load balancing
protects our application servers from common denial-of-service attacks (e.g., SYN floods, ping floods, and "smurfs" attacks). Security policies can be based on any combination
of source address, destination address, and protocol type or content.

	•
	Virtual Private Network (VPN)—The registry network will use VPN technology to perform database updates at the
nameservers, network-based backup/restore, remote system/network management, and system administration. Our goal is to operate the nameserver data centers sites in a "lights out" (unmanned) mode. VPN
technology achieves secure data transfer through encrypted data communications links. 

Server Security  

        The Enhanced SRS operating systems provide access protection through a user login procedure and through file-level access control lists. These access
control mechanisms perform the following functions: 

	•
	User
account security, which establishes the access capabilities of a specific authenticated user. After authenticating a user, each application's security data tables
control access to information. Access is based not only on user ID but also on the type of application being used (e.g., XRP or Billing and Collection). The application server uses user ID to provide
precise control of access privileges to—and uses of (read, write, and execute)—all system resources: screens, menus, transactions, data fields, database tables, files, records,
print facilities, tape facilities, software tools, and software executables.

	•
	Group-level
security, which establishes the access capabilities of all users within a specific group. All users belong to one or more access control groups. Access control
is identical to that for individual users.

	•
	System
Administration-level security, which restricts access to system administration tools, including the ability to change resource access privileges. Enhanced SRS system
administration staff use dedicated links on an internal LAN/WAN to access administrative functions that are off limits to others. There is no external access to this LAN. All sessions require user
identification by user name and password; access control lists determine what resources a user or user group is allowed to access and use. 

        The
Enhanced SRS operating systems will perform security-relevant logging functions, including: 

	•
	User Login—Whenever a user login is attempted, whether successful or not, the event is logged. The logged
information includes the user ID, time, and device requested. 

O-55

 

	•
	User Accounting—Logs every process executed by every user. The output includes date and time, user ID, point of
entry, process, resources accessed, and result of the operations. This log may be selectively viewed for actions performed by a specific user or users.

	•
	System Logging—This inherent, configurable logging capability permits monitoring the kernel, user processes, mail
system, and authorization system. In addition, the operating system detects when file access privileges have been changed and also audits the use of telnet, finger, rsh, exec, talk, and similar
operations. 

        The
following provisions apply to passwords: 

	•
	Passwords
must be at least six alphanumeric characters in length. At least one character must be alphabetic and at least one must be a numeric or punctuation character.

	•
	If
users forget their password, the system administrator verifies the user's identity and then provides them with a temporary password that enables them to log on only to
the site where users create their own new passwords.

	•
	Passwords
are valid only for a preestablished duration (typically 90 days, but reconfigurable). Prior to password expiration, the system instructs the user to create
a new password.

	•
	When
a user changes his/her password, the system first reauthenticates the existing password and then requires the user to verify the new password before accepting the
change. The system will not accept as a user's new password either of that user's two most recent passwords.

	•
	Passwords
are encrypted and stored in an inaccessible system file. 

Application Security  

        Each Enhanced SRS application will have its own set of security processes and technical controls. The Enhanced SRS applications that interface with the
registrars/delegees/registrants (e.g., the XRP and the secure Web customer service portal) employ the SSL (secure sockets layer) protocol element that uses public-key exchange and RC4
encryption. Public services (e.g., Whois, delegee, DNS queries, and the public Internet Web portal) rely on the previously discussed network perimeter security devices—edge routers,
firewalls, and load balancers—to protect the internal LAN and applications servers. 

	•
	XRP Applications Security—NeuStar's XRP server authenticates against a series of security controls before
granting service, as follows:

	1.
	The
registrar/delegee's host initiates an SSL session with the XRP server.

	2.
	The
XRP server receives the registrar/delegee's private key with the incoming message and authenticates it against their public key, which is stored in the registry's XRP server.

	3.
	After
the XRP server verifies the key exchange, it completes the SSL initialization to establish a secure, encrypted channel between itself and the registrar/delegee's host computer.
This secure, encrypted channel ensures the integrity of the session with registry applications.

	4.
	In
combination with completing the SSL connection, the XRP server authenticates an X.509 digital certificate to verify the registrar/delegee's identity. Digital certificates are
maintained in the Enhanced SRS authentication server database.

	5.
	The
registrar/delegee logs on to the XRP server using a user ID and password that determine access privileges. We will provide each registrar with multiple user IDs and password pairs,
so that each can establish its own group of authorized users. 

O-56

 

	•
	Whois/Delegee Whois Application Security—Although any Internet user has
read-only access to the Whois server, NeuStar's perimeter security mechanisms—edge routers, firewalls, and load balancers—will protect it against
denial-of-service attacks. A designated registry administrator performs common database administration tasks on the Whois and Delegee Whois databases, including monitoring
their performance.

	•
	Nameserver Security—Just as they have with the Whois servers, all Internet users have
read-only access to the nameservers. Similarly, the edge router, firewall, and load balancers protect the nameservers as they do the Whois servers.

	•
	Secure Web Customer Service Portal—The secure Web customer service portal uses the same
security mechanisms employed by the XRP server: SSL session encryption, digital certificates, and user ID and password between the Enhanced SRS secure Web server and the registrars' Web browsers. In
addition, e-mail messages are encrypted with a Pretty Good Privacy (PGP) public-key infrastructure implementation. Digital certificates are maintained in the authentication
server. 

        The
following table summarizes the benefits of each security mechanism that we employ at the data centers to prevent system hacking, break-ins, and
denial-of-service attacks. 

Security Summary  

	Security System Element
 
	 	Features and Benefits

	Server Operating System Security
	

User ID and password; file-level access control lists	
 	

Ensures that the user can access authorized functions, but no others, and can perform only authorized operations within these functions.
	
Database Security
	

User ID and password; user profiles	

 	

Limits database access to preauthorized users with a familiar, easy-to-use method for user authentication.

Retains the last two passwords and disallows their usage, complicating the task of password guessing and cracking.

Rejects simultaneous sessions by an individual user, helping ensure that user IDs and passwords are not shared.

Limits access rights to database objects and functions to a specified user or user group, simplifying the job of user administration.

Rejects unauthorized access attempts and automatically disables identification codes after a preestablished number of unsuccessful attempts, preventing trial-and-error hacking attempts.
	 	 	 

O-57

 

	
Application Security
	

Data encryption (SSL)	
 	

HTTPS encryption ensures that only the intended receiver can read messages between users and the NDR.
	

Digital signatures	
 	

Issued by an authentication server, digital signatures ensure that the incoming data actually have come from the purported sender. This provides nonrepudiation, avoiding disputes over data origin.
	

User ID and password	
 	

Ensures that the user can access authorized functions, but no others, and can perform only authorized operations within these functions
	
Network Security
	

Router	
 	

Permits only UDP/TCP packets to enter the application servers, thus isolating the system from most potentially damaging messages.
	

Firewall	
 	

Guards the secure LAN from the nonsecure Internet by permitting the passage of only packet flows whose origins and destinations comply with preestablished rules.
	

Intrusion detection	
 	

Detects intrusion at the LAN level. Displays an alert at the network operations center workstation and creates a log entry.
	

Load balancer	
 	

Implements security policies to prevent denial of service attacks (e.g., SYN floods, ping floods, and "smurfs").

O.9.1.2 Nameserver Data Center Security  

        NeuStar's approach to nameserver security is a subset of the security mechanisms we employ at the Enhanced SRS data centers. The nameserver data center also
relies on multi-layer perimeter protection, controlled access, enforcement of applications security features, and strong physical security protection. 

Network Security  

        The same mechanisms used for the Enhanced SRS data center are employed at the zone nameserver data centers. Edge routers and firewalls provide perimeter
protection for the data center network and applications systems, guarding against unauthorized access from the Internet. 

	•
	Edge Router—The first security layer is the edge routers, which employ IP-packet filtering to allow
only DNS UDP/TCP packets to pass into and out of the perimeter network.

	•
	Firewall—The second layer of perimeter security is a firewall that provides policy-based IP filtering to protect
against system hacks, break-ins, and denial-of-service attacks. The firewall also includes network-based intrusion detection to protect against Internet hackers.

	•
	Load Balancer—The third layer of protection is server load which protects our application servers from common
denial-of-service attacks
(e.g., SYN floods, ping floods, and "smurfs" attacks). Security policies can be based on any combination of source address, destination address, and protocol type or content.

	•
	Virtual Private Network (VPN)—The registry network will use VPN technology to perform database updates at the
zone nameservers, network-based backup/restore, remote system/network management, and system administration. Our goal is to operate the zone nameserver data center 

O-58

 

sites
in a "lights out" (unmanned) mode. VPN technology achieves secure data transfer through encrypted data communications links. 

Server Security  

        The zone nameserver operating systems provide access protection for remote system administration through a user login procedure and through file-level
access control lists. These access control mechanisms perform the following functions: 

	•
	User
account security establishes the access capabilities of a specific system administration authenticated user. After authenticating the user, the operating system's
access control lists control access to information.

	•
	System
Administrator-level security restricts access to system administration tools, including the ability to change resource access privileges. Nameserver system
administration staff use dedicated links on an internal LAN/WAN to access administrative functions that are off limits to others. There is no external access to this LAN. All sessions require user
identification by user name and password; access control lists determine what resources a user or user group is allowed to access and use. 

        The
zone nameserver operating systems will perform security-relevant logging functions, including: 

	•
	User Login—Whenever a user login is attempted, whether successful or not, the event is
logged. The logged information includes the user ID, time, and device requested.

	•
	User Accounting—Logs every process executed by every user. The output includes date and time, user ID, point of
entry, process, resources accessed, and result of the operations. This log may be selectively viewed for actions performed by a specific user or users.

	•
	System Logging—This inherent, configurable logging capability permits monitoring the kernel, user processes, and
the mail and authorization systems. In addition, the operating system detects when file access privileges have been changed and also audits the use of telnet, finger, rsh, exec, talk, and similar
operations. 

Application Security  

        The zone nameserver essentially enables the public to make DNS queries via the Internet. Public services, such DNS queries, rely on the previously discussed
network perimeter security devices—edge routers, firewalls, and load balancers—to protect the internal LAN and applications servers. 

O.9.2 Physical Security  

        NeuStar vigorously enforces physical security measures, controlling all access to our facilities. Throughout normal working hours, security personnel stationed at
each building entrance verify that employees are displaying proper identification badges, and they control access by nonemployees, who must sign in to gain entrance. The sign-in books are
stored for a period of one year. If the purpose of their visit is found to be valid, nonemployees are issued a temporary badge; otherwise, they are denied entrance. 

        At
all times while they are in the facility, visitors must display their badges and must be escorted by a NeuStar employee. We also strictly enforce the policy that employees must wear
their badges prominently displayed at all times while in the facility. 

        In
addition to providing physical security by protecting buildings with security guards, NeuStar uses a Cassi-Russco security system with Secure Perfect software to manage access
control. The system utilizes proximity card readers with PIN codes for access to the buildings nonpublic areas and biometric 

O-59

 

readers
recognition equipment to control access to the data center. Cameras monitor access points to the building and data center and provide digital recording for archives. All exterior doors are
monitored for status. A panic button has been installed for summoning aid, if it is required. 

        The
following table lists salient facts about our physical security mechanisms. 

NeuStar Physical Security Mechanisms  

	Mechanism
 
	 	Remarks

	

Security guards	
 	

Physically prevent intruder access; verify employee badges
	

Closed-circuit video surveillance cameras	
 	

Extend capabilities of security guards; maintain access records
	

Intrusion detection systems	
 	

Provide audible and visual alarms to notify security personnel in the event of unauthorized entry
	

Identity badges	
 	

Permanent badges for employees; easily recognizable temporary badges for visitors
	

Sign-in registers	
 	

Maintained as permanent records for at least one year
	

Electronic key badges	
 	

Control physical access during off hours; maintain access records
	

Palm readers	
 	

Restrict physical access to mission-critical rooms within our facilities; maintain access records
	

Self-closing doors	
 	

Restrict physical access to mission-critical rooms within our facilities

O-60

 

O.10 Peak Capacities  

        NeuStar proposes a highly scalable Enhanced Shared Registration System (SRS) and nameserver systems that are initially sized for a peak load of three times the
average projected workload. The peak load capacity and built-in scalability of the registry system architecture ensures the COTR that adequate capacity is available during initial peak
usage periods, and that as usage grows over the life of the registry operations, the Enhanced SRS system infrastructure can scale up smoothly without service disruption.

        To
avoid creating bottlenecks for Enhanced SRS, Whois, and nameserver services, NeuStar will engineer for peak usage volumes. In addition, NeuStar will deploy redundant
co-active Enhanced SRS data centers—a network of nameserver sites that are sized to handle the projected initial peak volumes. Subsequently, we will add additional zone
nameservers to handle the anticipated growth. Our Enhanced SRS, Whois, and nameserver architectures are designed with highly scalable server clusters and connected through networks that can be
smoothly scaled up without disrupting the system. Expansion provisions include the following: 

	•
	Servers
scale from Intel SMP machines to high-end RISC SMP database platforms with shared memory architectures.

	•
	Server
processors scale from 2-way to 6-way SMP for the Intel machines and from 2-way to 32-way SMP for the
high-end RISC database machines.

	•
	The
number of servers in a cluster that uses cluster management software scales from 2-way to 32-way to give near-linear processing
scalability.

	•
	The
number of servers in a cluster that do not use cluster management software can conceivably scale beyond 32 servers.

	•
	The
external telecommunications network connectivity to the Enhanced SRS and nameserver data centers scales from dual T-3 to quad T-3 to hex
T-3 connectivity and more as a function of the Enhanced SRS transaction load and the Whois and DNS query loads.

	•
	The
internal Enhanced SRS and nameserver LANs consist of a switched Gigabit Ethernet backbone fabric with extensive port expandability. 

        This
subsection describes the peak capacities of the Enhanced SRS, Whois, and nameserver subsystems in terms of the network, server, and database platforms' initial sizing and
scalability. NeuStar central backup/recovery, escrow, system/network management, and system administration systems are enterprise-strength hardware and software platforms that can easily handle these
management and administrative functions throughout the entire registry operations lifespan. Additional desktop computers and workstations can be added to accommodate growth in staff and workload as
usage increases and the registry infrastructure grows. Our maintenance support, help desk, and technical support functions are staffed for the initial peak usage period, and staff can be increased to
handle workload surges caused by registry marketing and promotional events. 

        It
should be noted that Delegee database capacity requirements are assumed to be low. For this reason, they have been factored into the Whois database capacity numbers. 

O.10.1 Enhanced SRS Peak Capacity  

        The Enhanced SRS provides the core subsystems that handle registrar transaction-based services, including XRP processing, billing and collection, secure Web
portal, and back-end database system services. This subsection describes the Enhanced SRS subsystems peak capacity in terms of the initial sizing and scalability of the network, server,
and database platforms. 

O-61

 

Network  

        The XRP average steady-state transaction load is projected to be 150 transactions per second (tps), or approximately 13 million transactions per day. Since
peak transactions are six times the average, we designed for a peak transaction load of 900 tps. The average transaction size is 5,000 bits, which translates to a required telecommunication capacity
of 4.5 MBPS. The external communication network connectivity to the Internet is initially sized at two fractional T-3 ISP 20-MBPS local access links, for a total of 40 MBPS to
handle XRP transactions and Whois queries. The registry's VPN between the sites is two T-1 1.544 MBPS. The VPN handles zone database updates, server backup and restore, system/network
management, and system administration functions. 

Server Clusters  

        The XRP server cluster and the associated applications server clusters are front-ended with load balancers that distribute the transaction processing workload
across the servers in each cluster. Distribution algorithms include least connections, weighted least connections, round robin, and weighted round robin. 

        The
XRP server and applications server clusters are initially sized to handle six times the projected steady-state workload, or 900 peak transactions per second. The processing capacity
can grow linearly by adding additional servers to the cluster. The total system capacity is a cluster size of 32 SMP 8-way RISC servers. 

        The
Billing and Collection system is sized to handle 200 peak transactions per second, because not every XRP transaction results in a billable service. 

Database System  

        The database system consists of dual high-end RISC machines, each with 2- to 32-way SMP scalability. The initial processing
capacity of the database system is 4-way SMP, sized in terms of the Transaction Processing Council Online Transaction Processing (OLTP) benchmark of 2500 transactions per second (tpsC). 

        The
database system can grow to handle eight times the initial projected volume of transaction loads. NeuStar will closely monitor system usage and will scale the database capacity
correspondingly. 

O.10.2 Whois Peak Capacity  

        A large percentage of the load on the current registry's Whois server is caused by data mining. NeuStar will increase network bandwidth and add
high-performance database capabilities to the Whois service infrastructure. Our proposed bulk-access services will reduce the Whois load by as much as two-thirds.
This subsection describes the Whois subsystems peak capacity in terms of initial sizing and scalability of the network, server, and database platforms. 

Network  

        The peak Whois transaction rate is estimated to be 2,000 queries per second, with an estimated packet size of 10,000 bits. This produces a maximum load of 20
MBPS. Initially, we will provide communication network connectivity for Whois queries between the Internet and each data center as two fractional T-3 ISP local-access links. Although these
links initially will not be used at full capacity, they ultimately can carry up to 90 MBPS per data center before we upgrade to larger links. 

O-62

 

Whois Server Cluster  

        Our Whois server cluster is front-ended with load balancers to distribute the transaction processing workload across the servers in each cluster. Distribution
algorithms include least connections, weighted least connections, round robin, and weighted round robin. 

        The
Whois server cluster is initially sized to handle 2,000 peak transactions per second. To improve query response time and lighten the load on the database, the Whois servers cache
frequently accessed domain names. 

        The
processing capacity can grow linearly by adding additional servers to the cluster. The total system capacity is a cluster size of 32 SMP 6-way Intel servers. NeuStar will
closely monitor Whois usage and will increase the system's capacity to accommodate increasing demand. 

Database System

        Behind
the Whois/Delegee servers are dual mid-range RISC machines, each with 2- to 8-way SMP scalability. Initial processing capacity will be
4-way SMP at 500 tpsC, scalable to 1,000 tpsC. (tpsC is Transaction Processing Council (TPC) Online Transaction Processing (OLTP) benchmark C workload.) 

        NeuStar
is implementing a Whois bulk-load data mart service that will enable the registrars to provide their customers with OLTP bulk query services for data mining of domain
names. 

O.10.3 DNS Query Peak Capacity  

        During the initial land rush period when registrars are marketing the expanded usTLD domain name extensions, DNS query traffic is expected to be moderate because
of less caching further down the DNS hierarchy. Moreover, the query load will not approach current dot-com/dot-net/dot-org levels until more than five million names
are registered. Although NeuStar is proposing three nameserver sites at roll-out, we will closely monitor the load to project the need to add another site 

        NeuStar's
registry handles DNS queries at the nameservers. This subsection describes the nameservers' peak capacity in terms of the network, server, and database platforms' initial
sizing and scalability. NeuStar's design will easily scale as load increases. 

Network  

        NeuStar anticipates a peak load of 5,000 DNS queries per second at each nameserver data center and estimates the average query package size to be 1,600 bits. This
load produces a required telecommunications network bandwidth for DNS queries of 8 MBPS. To provide this bandwidth, we will provision two fractional T-3 access links to the Internet at
each zone nameserver site. The nameserver data centers will easily process a peak load of 40,000 queries per second with more than 100 percent reserve capacity. 

Zone Nameservers  

        Our DNS nameserver cluster will be front-ended with load balancers to distribute the transaction processing workload across the nameservers in the cluster.
Distribution algorithms include least connections, weighted least connections, round robin, and weighted round robin. 

        The
nameserver cluster is initially sized to handle three times the projected steady-state workload, or 5,000 queries per second. To improve query response, the entire zone will be held
memory resident. 

        Processing
power can grow linearly by adding additional servers to the cluster up to its total system capacity: a cluster size of 32 SMP 6-way Intel servers. NeuStar will
closely monitor system usage and will scale up as required. 

Database System  

        The nameserver database update systems use Intel machines with up to 6-way SMP scalability to perform snapshot replication of updates to the
nameserver database. Since the snapshot replication is triggered at regular intervals, the initial nameserver database update system is sized as a 2-way SMP database server, which is more
than adequate to distribute the zone file updates. 

O-63

   O.11 System Reliability  

        To provide continuous access to usTLD registry data and applications, NeuStar proposes the use of two co-active data centers,
geographically separated and continuously online. Each data center incorporates redundancy and nonstop, high-availability features in its hardware and software configurations.  

        Today, business lives in an environment of global economies, increasing competition, ever-changing technologies and markets, population mobility, and
other uncertainties. It becomes increasingly evident that the ability of a business to quickly and intelligently respond to these changing conditions depends directly on the availability, timeliness,
and integrity of its information resources. The Information Technology industry has responded to this need with a variety of high-availability systems whose costs depend on the size of the
necessary databases and on service-level agreements covering system availability. Thus, a TLD registry's selection of a high-availability solution is not only a significant investment but
also a crucial decision that can determine the registry's success or failure. 

        usTLD
applicants must realize that few businesses can afford to be without access to mission critical applications, nor can they tolerate system failures that lead to excessive downtime
and denial of service. Furthermore, few end users would consider a system to be "available" if system performance drops below some acceptable level or if the system is only available to some subset of
the user community. How useful is the fact that a system can perform a zillion tpm or execute a query in milliseconds without knowing its availability and the cost of achieving its performance and
availability? 

        NeuStar
is proposing two co-active data centers for usTLD registry operations and a network of nameservers. These facilities are geographically dispersed to minimize the
possibility of outages caused by natural or man-made disasters. The nameservers are dual-homed to each data center via a VPN backhaul link. As Exhibit O-15
indicates, the two data centers are interconnected by high-speed, alternate-routed VPN links. The VPN network management system includes a "heartbeat" signal from each data center. If it
detects a failed heartbeat at one data center, it automatically routes all traffic to the other. 

        Each
data center will have redundant network components, high-availability server clusters, and redundant database servers to eliminate single points of failure. All critical
telecommunications access links and network components—routers, firewalls, LAN
switches, and server NIC cards—will be redundant. Anything less would be inadequate to provide the service levels that the COTR and the industry deserve. 

        [Exhibit O-15:
Graphic Design] 

O.11.1 Quality of Service and Performance Measurements  

        Neustar understands the importance of quality of service as it pertains to the usTLD. The systems and operations used to be reliable and have a high level of
performance. But quality of service is only a subjective opinion unless one provides objective measures of performance and reliability. For example the Enhanced SRS must have a high level of
availability for the registrars and provide response times. Both of these functions can be measured, monitored and reported. 

        NeuStar
believes Performance Measurements are so important to the proper functioning of the usTLD Administrator we have integrated detailed performance measurements into our usTLD
Administrator Registrar Agreements. Not only have we integrated the measurements into the agreement, but we have included credits to be paid to the registrars if we fail to meet any one of them. 

        For
a detailed description of the performance measurements please see Exhibit G of the usTLD Registrar Contract in Section H of this proposal. For a detailed description of
the Perfomance Credits please see Exhibit H of the same contract in Section H of this Proposal. Section Q of this proposal provides an overview of NeuStar's capabilities and
commitments with regard to Performance Measurements. 

O-64

 

O.12 System Outage Prevention  

        The NeuStar's co-active redundant data centers and high-availability server cluster architecture will maintain
continuous operations with no disruptions in service. The benefit is improved system availability, minimum downtime, and high confidence in the Internet registry services.  

        The Internet community requires outage prevention measures specifically designed to minimize system downtime. Downtime can be categorized as either unplanned or
planned: 

	•
	Unplanned
downtime is caused by failures in external telecommunications, power, or internal network or computer equipment.

	•
	Planned
downtime occurs when the system is unavailable due to scheduled maintenance (e.g., during software or hardware upgrades and system backups). Planned downtime is
normally minimized in two ways:

	•
	By
performing backups, maintenance, and upgrades while the system remains operational (hot), or

	•
	By
reducing the time required to perform tasks that can be performed only while the system is down. 

        In
addition to employing the above measures for minimizing planned downtime, system designers may use redundancy and high-availability system architectures designed to
minimize unplanned outages. Many data management operations will also have disaster recovery agreements with a business continuity provider who provides a disaster recovery site geographically
separated from the operational data center. The intent is to maintain continuity of operations in the event of a natural or man-made disaster. 

        NeuStar
believes these approaches alone, although commendable, are insufficient to meet the high service levels expected by the DOC and the Internet community. For example, the registry
services are so specialized and component intensive that no business continuity provider is likely to be capable of resuming services without a lengthy outage period. We contend that the only way to
provide satisfactory service levels is through a combination of approaches, including: 

	•
	Co-active
redundant data centers with two-way transaction replication,

	•
	High-availability
server cluster architecture,

	•
	Hot
backup/recovery, and

	•
	Automated
disaster recovery provisions. 

Procedures for Problem Detection and Resolution  

        To best meet data center requirements for availability, flexibility, and scalability, NeuStar has designed a high-availability architecture that will
combine multiple computers into a cluster. Nodes in the cluster will be loosely coupled, with each node maintaining its own processor, memory, operating system, and network connectivity. Our
system/network management and cluster management tools will automatically detect and compensate for system and network faults and notify system operators. 

        At
five-minute intervals the network management system will "ping" network devices with Simple Network Management Protocol (SNMP) for availability and poll them for
performance statistics. Event threshold violations or error conditions will initiate a sequence of alerting events, including visual notifications via a topology map, an entry into a trap log of event
records, e-mails to a bulletin board, and notices to technical support staff. The goal is to detect and repair potential problems before services are disrupted. 

O-65

 

        An
SNMP daemon will be configured to periodically check the status and health of vital server processes. In the event of a critical process failure, the SNMP agent will send a trap to
the network management system, initiating an alert to the technical support staff. Our network management software will include remote monitoring and management of operations, so technical support
staff can easily diagnose and troubleshoot network faults, either from the Network Operations Center or remotely. Once a problem is detected, it will be resolved using our proven problem management
process. In conjunction with this problem management process, we will employ proactive performance management and trend analysis processes to do root cause analysis and discover performance and
utilization trends that could lead to potential problems. 

        The
cluster management software will organize multiple nodes (up to 16) into a high-availability cluster that delivers application processing support to
LAN-/WAN-attached clients. The cluster software, which will monitor the health of each node and quickly respond to failures to eliminate application downtime, will
automatically detect and respond to failures in the following components: 

	•
	System
processors,

	•
	System
memory,

	•
	LAN
media and adapters,

	•
	System
processes,

	•
	Applications
processes, and

	•
	Disk
drives. 

        Since
high availability is a primary design goal, a cluster cannot have a single point of failure; accordingly, we will employ RAID mirrored disk drives and multiple LAN connections. The
cluster software will monitor these hardware and software components and respond by allocating new resources when necessary to support applications processing. The process of detecting failures and
restoring the applications service will be completely automated—no operator intervention will be required. 

Redundancy of Data Centers and Systems  

        NeuStar is proposing redundant co-active data centers: one in Virginia and one in Illinois. These data centers will be interconnected by redundant,
high-speed, secure VPN telecommunications links to provide two-way replication of all registry database transactions. A heartbeat monitor will determine the online status of
each data center and enable the services to be provided entirely from the second data center if one is lost. 

        Within
each data center, the system will be redundantly configured so that failure of any system component will leave a configuration of surviving system components capable of executing
the entire workload within 95 percent of the previous performance for at least 90 percent of users. To achieve no-single-point-of-failure
architecture, NeuStar will replicate all components and configure the system for automatic failover. 

        The
following table describes the system architecture redundancy we will employ at each Enhanced SRS data center to meet 99.9+ percent service availability levels. 

O-66

 

System Redundancy Elements  

	Issue
 
	 	Redundancy Solution
 
	 	Benefit
 

	Single failure of a system component	 	Replicate all critical components to eliminate single point of failures	 	The system is capable of executing the entire workload.
	

Maintaining availability of applications	
 	

Stateless N+1 node high-availability processor clusters	
 	

In event of a processor failure, service is not degraded.
	

LAN Interface or cable failure	
 	

Multi-path LAN I/O	
 	

Automatic switchover from one LAN switch to another to restore connectivity
	

Disk controller or cable failure	
 	

Multi-path disk I/O	
 	

Applications take alternate routes
	

Disk storage module failure	
 	

Redundant Array of Independent Disks (RAID, levels 1, 3, and 5)	
 	

Applications still have access to data in the event of a single disk failure
	

Hardware/software upgrades and additions or changes to the configuration	
 	

N+1 redundancy allows hot repair/upgrade of system components.	
 	

Eliminate downtime due to administrative and maintenance tasks
	

Dynamic processor de-allocation	
 	

Dynamically take a processor out of service to modify the physical and logical configuration of the system.	
 	

Eliminate downtime due to maintenance tasks and component replacement
	

Replace disks	
 	

RAID drives and controllers allow hot plug-in of disk modules	
 	

Eliminate downtime due to maintenance tasks

Hot Repair of System Components  

        Another advantage of system redundancy is that it will enable our maintenance staff to use hot repair or replacement of system components. Keeping the system in
full operation while we perform such common system administration tasks as upgrading the hardware or software or adding to or changing components will eliminate the MTTR
(Mean-Time-To-Repair) factor and will minimize downtime. Hot repair is possible only when major system components are redundant, as in the NeuStar solution. 

Backup Power Supply  

        Each Enhanced SRS and nameserver data center will be provided with UPSs to ride through brief electrical transients and outages. For more than brief outages, each
Enhanced SRS data center will have a 1,000 KVA generator and the nameserver data center will have a 250 KVA generator capable of running the entire data center in the event of a lengthy electrical
blackout. 

Facility Security  

        As discussed in Registry Operator's Proposal Section O.10, NeuStar will vigorously enforce physical security measures that control all access to our
facilities. Throughout normal working hours, security personnel stationed at each building entrance will verify that employees are displaying proper identification badges and will control access by
nonemployees, who must sign in to gain entrance. The 

O-67

 

sign-in
books will be stored for a period of one year. If the purpose of a nonemployee's visit is found to be valid, he or she will be issued a temporary badge; otherwise, entrance will be
denied. At all times while they are in the facility, visitors must display their badges and must be escorted by a NeuStar employee. We will also strictly enforce the policy that employees wear their
badges prominently displayed at all times while in the facility. During off hours (6:30 p.m. to 6:30 a.m. and all day on weekends and major holidays), individuals must use the proper
electronic key cards to gain access to the building. We will issue electronic key cards only to employees who need access for business purposes. 

        In
addition to being stationed at building entrances during normal working hours, on-site security personnel will be on duty 24 hours a day and 7 days a week to
monitor the images from closed-circuit television cameras placed strategically throughout the facilities. Further, any room housing sensitive data or equipment will be equipped with a
self-closing door that can be opened only by individuals who activate a palm print reader. Senior managers will establish the rights of employees to access individual rooms and ensure that
each reader is programmed to admit only those authorized individuals. We will grant access rights only to individuals whose duties require them to have hands-on contact with the equipment
housed in the controlled space; administrative and customer service staff normally do not require such access. The palm readers will compile and maintain a record of individuals who enter controlled
rooms. The following table lists our physical security mechanisms. 

Physical Security Provisions  

	Mechanism
 
	 	Purpose
 

	Security guards	 	Physically prevent intruder access; verify employee badges
	

Closed-circuit video surveillance cameras	
 	

Extend capabilities of security guards; maintain access records
	

Intrusion detection systems	
 	

Extend capabilities of security guards to building perimeter
	

Identity badges	
 	

Permanent badges for employees; easily recognizable temporary badges for visitors
	

Sign-in registers	
 	

Maintained as permanent records for at least one year
	

Electronic key badges	
 	

Control physical access during off hours; maintain access records
	

Palm readers	
 	

Restrict physical access to mission-critical rooms within our facilities; maintain access records
	

Self-closing doors	
 	

Restrict physical access to mission-critical rooms within our facilities

Technical Security  

        Registry Operator's Proposal Section O.10 also describes the technical security measures that NeuStar proposes. We will use the underlying user ID and
password security features of the XRP, supplemented by system-based Public Key Infrastructure (PKI) services to provide additional security. The following table lists the systems, protocols, and
devices to prevent system hacks, break-ins, data tampering, and denial-of-service attacks. 

O-68

 

Database and Operating System Security  

	Technical Security System Element
	 	Features and Benefits
 

	Access control system: user ID and password, file level access control lists	 	Ensures that the user can access authorized functions, but no others, and can perform only authorized operations within these functions. For example, the registrar of a registered domain name is authorized to query it and
then renew or cancel it or change its nameservers but cannot query domain names held by other registrars.
	

Database: user ID and password, user profiles	
 	

•	

Limits database access to pre-authorized users.
	

 	
 	

•	

Retains the last two passwords and disallows their usage.
	

 	
 	

•	

Rejects simultaneous sessions by an individual user.
	

 	
 	

•	

Stores user profiles.
	

 	
 	

•	

Limits access rights to database objects and functions to a specified user or user group.
	

 	
 	

•	

Rejects unauthorized access attempts. Automatically revokes identification codes after a preestablished number of unsuccessful attempts.
	

 	
 	

•	

Provides an interface to facilitate the online administration of user privileges.
	
E-commerce Security Features
	

SSL v3.0 protocol	
 	

HTTPS encryption ensures that messages between the registry and registrars/delegees can be read only by the intended receiver.
	

Digital signatures	
 	

Issued by an X.509 authentication server, digital signatures ensure that the incoming data actually has come from the purported sender; provides nonrepudiation.
	
Boundary Security Features
	

Router	
 	

Permits only DNS UDP/TCP packets to enter the data center LAN, thus isolating the TLD system from most potentially damaging messages.
	

Firewall	
 	

Guards the secure TLD LAN from the nonsecure Internet by permitting the passage of only packet flows whose origins and destinations comply with preestablished rules.
	

Intrusion detection	
 	

Detects intrusion at the LAN level. Displays an alert at the usTLD network operations workstation and creates a log entry.

Availability of Backup Software, Operating System, and Hardware  

        Registry Operator's Proposal Section O.7 describes our zero-downtime/zero-impact backup process, which will use backup servers,
disk array, and a DLT robotic tape library. The dedicated backup system will be independent of the registry server clusters that run the applications. 

O-69

 

System Monitoring  

        The subsection entitled "Procedures for Problem Detection and Resolution" describes system monitoring capabilities and procedures. Our Network Management System
and specialized element managers will monitor specific routers, LAN switches, server clusters, firewalls, applications, and the backup servers. In addition, the cluster management software will
monitor the status and health of processor, memory, disk, and LAN components in the high-availability cluster. 

Technical Maintenance Staff  

        The NeuStar three-tier customer service approach will ensure that all problems are resolved by the appropriate party in a timely manner. 

        The
Technical Support Group will operate from the Help Desk Network Operations Center (NOC) within the data centers. The group will comprise system administrators, network
administrators, database administrators, security managers, and functional experts in the TLD registry IT systems and applications infrastructure. usTLD registry customers access the Technical Support
Group through the Tier-1 Help Desk. This group will resolve trouble tickets and technical problems that have been escalated to them by the Help Desk Customer Service Agents. If the problem
involves a hardware failure, the Technical Support Group will escalate the problem to our Tier-3 on-site maintenance technicians, third-party maintenance providers, or our
hardware vendors, depending on the nature of the problem. 

Server Locations  

        NeuStar's registry servers will be located in the Enhanced SRS data centers in Virginia and Illinois. Two zone nameserver centers will be collocated with the
registry data centers; the remaining nameserver center will be California, with dual-homed telecommunications links and redundant high-availability servers to provide
resilience and disaster recovery. 

O-70

 

O.13 System Recovery Procedures  

        NeuStar is proposing two co-active Enhanced SRS data centers and a network of nameserver data centers geographically dispersed
to provide redundancy and to enable us to responsibly recover from unplanned system outages, natural disasters, and disruptions caused by human error or interference. The COTR and the Internet
community can be confident that we will respond to unplanned system outages quickly with little or no loss of services.  

        To maintain public confidence in the Internet, the COTR surely desires a high level of system recovery capabilities. Proven industry solutions to the problems of
outages and disaster recovery incorporate high-availability system architectures and fast failover from the primary data center to a mirrored backup. High-availability
solutions minimize downtime with availability of 99.9 percent or greater. Continuously available solutions go a step further with virtually zero downtime, creating an availability of
approximately 99.999 percent (five nines). 

        System
recovery architectures include: 

	•
	Symmetric Replication—The database replication (on the backup or failover system) is identical to the primary
database on the production system because any change made to the primary database is "replicated" in real time on the backup database. Since this is not a "two-phase commit" process, a
small window of vulnerability exists, during which changes made to the primary system could be lost in transit. Replication may increase transaction times, but switching from the primary database to
the backup can be very fast and essentially transparent to end users.

	•
	Standby Databases—A standby database—a special case of replication—at a backup site
originates as an identical copy of the primary database. Changes (updates, inserts, and deletes) to the primary database are recorded in transaction logs that are periodically archived. Archived logs
are delivered to the backup site and applied to the standby database. In a best-case scenario, the standby system is behind (in terms of data currency) the primary system by the number of
changes contained on the current transaction log.

	•
	Remote Data Mirroring—This is the classic disk-mirroring procedure, except it is conducted at a long
distance. Depending on whether hardware or software mirroring is used, the performance impact can vary from minimal to significant. Switchover to the backup site can be quick and virtually transparent
to end users. The loss of data is zero, although a "system crash" type of database recovery is needed. 

        NeuStar's
system recovery solution is based on running mission-critical Enhanced SRS applications at two co-active data centers (separated by nearly 700 miles) with database
replication technology that maintains database synchronization between the two centers. To provide backup for DNS queries, we are implementing multiple nameserver data centers, also physically
separated by long distances. We recognize that system management and recovery are more difficult when the system is spread over a large geographical area; however, two-way replication
between the co-active Enhanced SRS data centers will keep the registry master databases identical. 

O.13.1 Restoring Enhanced SRS Operations in the Event of a System Outage  

        Believing that prevention of failure is better than restoring after failure, and to maximize availability and eliminate the possibility that a single-point
failure could shut down operations, we implemented each of the co-active Enhanced SRS data centers and three nameservers with: 

	•
	Redundant
components with no single point of failure;

	•
	High-availability
cluster architecture; 

O-71

 

	•
	Load
balancers, which are used primarily to distribute the processing load across multiple servers and to defend against common denial-of-service
attacks that can precipitate outages caused by processor overloads;

	•
	Redundant
hardware; and

	•
	Data
backup/restore systems that work together to avoid unplanned outages. (Naturally, the primary function of these systems remains quick recovery, if such an outage should
occur.) 

        The
recovery mechanisms we will implement include: 

	•
	Full
backup and continuous, incremental backup CD-ROMs and DLT tapes are maintained at the data center and at the secure escrow facility. These backups
enable us to recover, rebuild, and return the operating system, application software, and databases to operation.

	•
	Processor
nodes in the cluster are monitored (and controlled) by cluster management software to facilitate recovery of software applications in the event of a processor
failure.

	•
	In
the event of a database failure, redundant database software fails over to the replicated backup database, enabling applications that use database services to recover
operations seamlessly.

	•
	Processors
in high-availability clusters have dual attached ports to network devices and RAID disk arrays, enabling them to recover from a failure in a single
port or disk drive.

	•
	Our
high-availability clusters are sized to run at peak load. If a processor fails, the excess capacity in the cluster handles the full processing workload while
the failed node is repaired or replaced. In essence, this is instantaneous recovery. 

        The
remainder of this subsection describes how we would recover from a system-wide disaster, that is, one that disables an entire data center. Subsection O.14.3
discusses recovery from various types of component failures. 

O-72

   
        Each of the co-active data centers is sized to take over the entire load of the Enhanced SRS operations, and each zone nameserver is dual-homed to each data
center. With this architecture, recovery in the event of a disaster is nearly instantaneous. Sessions that were dropped by the data center that suffered the disaster are simply restarted on the
remaining data center within seconds. The following are the main issues that our disaster recovery strategy solves: 

	•
	Instead
of having a primary and a backup data center, we use two co-active data centers whose data and applications are kept synchronized by
two-phase commit replication. Because the XRP servers are configured to retry failed transactions, neither registrars nor users submitting queries will perceive any degradation in service.

	•
	If
a data center goes off-line, the workload is transparently switched to the remaining data center. The transaction latency is limited to the brief time needed
to replicate the last transaction to the surviving data center.

	•
	Two-way
replication of transactions between the sites keeps each site's databases in a state of currency and synchronization that is consistent with mission
critical availability levels. 

        The
use of co-active data centers with two-way replication between them provides fast, simple disaster recovery that maintains continuity of
operations—even in the event of a major disaster. The resulting zero-downtime/zero-impact system not only solves system recovery problems, it also sustains
confidence in the Internet. The following are the procedures that are followed to restore operations if an Enhanced SRS or nameserver data center experiences a natural or man-made
disaster: 

	•
	Enhanced
SRS or nameserver operations are immediately failed over to the co-active data centers; registry operations proceed uninterrupted, except for those
transactions that were in transit between the two centers.

	•
	We
implement the disaster recovery plan for the failed data center and place the disaster recovery team on alert.

	•
	Within
eight hours, the disaster recovery team is assembled and dispatched to the failed data center to help the local data center personnel stabilize the situation, protect
assets, and resume operations.

	•
	The
disaster recovery team assesses whether the building housing the data center can be used to recover operations.

	•
	If
so, the team contacts disaster recovery specialist firms under contract to NeuStar to secure the facility and begin recovery operations.

	•
	If
not, the team salvages equipment and software assets to the extent possible and procures an alternate data center facility. NeuStar initiates its contingency plan to
reconstruct the data center in the new location, repair and test the salvaged equipment and software, and procure the remaining required components with quick-reaction procedures. 

        Once
the disaster recovery team has stabilized and tested the Enhanced SRS or nameserver equipment, it retrieves the system and application software CD-ROMs and the
database backup tapes from the secure escrow. It then rebuilds the data center using the same recovery procedures that are used for restoring components lost in a more limited failure. (Subsection
O.14.3 describes these procedures.) 

O.13.2 Redundant/Diverse Systems for Providing Service in the Event of an Outage  

        NeuStar is proposing two co-active Enhanced SRS data centers and multiple zone nameserver data centers with high availability clusters and cluster
management software that enables multiple node processors, in conjunction with RAID storage arrays, to quickly recover from failures. The server load 

O-73

 

balancer
and the cluster manager software monitor the health of system processors, system memory, RAID disk arrays, LAN media and adapters, system processes, and application processes. They detect
failures and promptly respond by reallocating resources. 

        Dual
database servers are coupled to a primary and a backup database and RAID configuration to ensure data integrity and access to the database. The database system uses synchronous
replication, with two-way commits to replicate every transaction to the backup database. The process of detecting failures and restoring service is completely automated and occurs within
30 seconds with no operator intervention required. 

O.13.3 Process for Recovery From Various Types of Failures  

        The following table lists the possible types of failures and describes the process for recovery. 

Failures Affecting the Nameserver Sites  

	Failure Type
 
	Recovery Process
 

	Nameserver cluster processor fails	Cluster management software logs out the failed processor and processing continues on the remaining nodes in the cluster.
	

Internet or VPN link fails	

Ongoing sessions are dropped and restarted on the other redundant ISP or VPN access link Ongoing sessions are dropped and restarted on one of the other nameserver sites
	

Edge router, firewall, or load balancer fails	

Ongoing sessions are dropped and restarted on the redundant components.

Failures Affecting the Data Center Applications and Database Server  

	Failure type
 
	Recovery process
 

	Applications cluster processor fails	Cluster management software logs out the failed processor and processing continues on the remaining processors in the cluster.
	

XRP server processor fails	

Registrar session is dropped from the failed server and restarted on the other XRP server
	

Web server processor fails	

Cluster management software logs out the failed processor and processing continues on the remaining processors in the cluster.
	

Database server processor fails	

The operating system automatically distributes load to the remaining SMP processors
	

Database disk drive fails	

Processing automatically continues on the RAID with no data loss
	

Database crashes	

The applications processing continues seamlessly on the backup replicate database
	

Authentication server fails	

Processing automatically continues on the redundant authentication server
	

Whois cluster processor fails	

Cluster management software logs out the failed processor and processing continues on the remaining processors in the cluster
	 	 

O-74

 

	

A Billing server fails	

Processing automatically continues on the redundant B&C server
	

Internet or VPN link fails	

Ongoing sessions are dropped and restarted on the other redundant ISP or VPN access link
	

Router or firewall fails	

Ongoing sessions are dropped and restarted on the remaining redundant router or firewall.

        In all cases of component failure, system recovery is automatic, with zero downtime and zero impact on system users. The remainder of this subsection (O.14.3)
provides additional information about failure recovery considerations for individual components. 

Recovery From a Cluster Processor Failure  

        If one processor in a cluster fails, the cluster manager software logically disconnects that processor. While technicians repair or replace it, applications and
user sessions continue on the remaining cluster processors. After the failed processor is off line, the following procedures are used to recover it: 

	1.
	Testing
and troubleshooting with diagnostic hardware and software to determine the root cause (e.g., hardware [CPU, memory, or network adapter] or software
[system or application subsystem]);

	2.
	Repairing
hardware failures and, if necessary, rebuilding system and applications software from the backup CD-ROM;

	3.
	Testing
the repaired processor and documenting the repairs in the trouble ticket; and

	4.
	Logging
the processor back into the cluster. 

Database System Recovery  

        Our database management system supports continuous operation, including online backup and management utilities, schema evolution, and disk space management. All
routine database maintenance is performed while the database is online. 

        NeuStar's
database server software solution will provide distributed redundancy by implementing synchronous replication from a primary database server to a backup database server. This
solution
includes automatic and transparent database failover to the replicated database without any changes to application code or the operating system. 

        If
a database system node experiences a hardware failure or database corruption, NeuStar technicians use the following recovery procedures: 

	1.
	Test
and troubleshoot with diagnostic hardware and software to determine the root cause (e.g., hardware [CPU, memory, network adapter, or RAID disk array] or
software [operating system, database system, or monitoring software]).

	2.
	Repair
hardware failures and, if necessary, rebuild operating system and applications software from the backup CD-ROM.

	3.
	Test
the repaired processor and document the repairs in the trouble ticket.

	4.
	Restore
the data files by applying (in the correct sequence) the full backup DLT tapes and the incremental backup DLT tapes maintained in the data center. 

O-75

 
	5.
	Log
the processor node back into the redundant server configuration and synchronize the database by applying the after-image journal files until the primary and replicate database are
fully synchronized. The procedure is as follows:

	•
	Recreate
the database directories and supporting file structure,

	•
	Insert
the full backup tape from the escrow facility and restore the base level backup,

	•
	Insert
incremental backup tapes in the correct order to ensure that they are correctly applied to the base level backup, and

	•
	Mount
the roll forward recovery tapes using the log roll forward recovery and apply them to the database. 

O.13.4 Training of Technical Staff Who Will Perform Recovery Procedures  

        NeuStar technical personnel have an average of five years of data center operations experience, encompassing the high-availability cluster technology,
distributed database management systems, and LAN/WAN network management systems that are employed in the recovery process. New hires and transfers to NeuStar's usTLD registry operations will be given
the following training: 

	•
	A
one-week "usTLD System Overview" course;

	•
	Vendor-offered
courses for certification in backup/recovery, cluster management, system management, and network management; and

	•
	On-the-job
training on registry operations, including high-availability cluster management, system backup/recovery, database
backup/recovery, and system/network management. 

O.13.5 Software and Operating Systems for Restoring System Operations  

        NeuStar will use commercially available Unix operating systems, cluster management software, and backup/recovery software to restore the Enhanced SRS and
nameserver systems to operation. In addition to providing synchronous replication of registry transactions to the backup server, our database management system will provide data recovery services
using the DLT tape backup system.
Backup/recovery hardware and software at the Enhanced SRS data center will remotely back up and restore the nameservers over the VPN. 

        All
static applications software and operating systems are backed up to DLT tape volumes and converted to CD-ROM for quick restoration in the event of operating system or
application software failures. Backup copies are maintained in the data center for quick access, with additional copies in the secure escrow facility. 

O.13.6 Hardware Needed To Restore and Run the System  

        The two co-active data centers will house the commercial off-the-shelf, redundant cluster servers and dedicated
backup/recovery servers that are needed to restore the system to operation. 

O.13.7 Backup Electrical Power Systems  

        Each of the two data centers is configured with a UPS battery backup system that provides sufficient power for 30 minutes of operation. Each one also has a
transfer switch connected to 1,000-KVA motor generators that are capable of powering the entire data center for many days without commercial power. 

O-76

 

O.13.8 Projected Time for Restoring the System  

        Two co-active data centers, each with high-availability clusters sized to handle the full projected registry load, provide the Enhanced
SRS services. 

	•
	If
an individual cluster experiences a processor failure, that processor's applications are transferred to another processor within approximately 30 seconds; however, the
remaining processor nodes in the cluster continue applications processing without interruption.

	•
	Since
there are two co-active data centers with two-way database replication to maintain database synchronization, even if a natural or
man-made disaster eliminates one data center, registry services continue with zero downtime and zero impact on users. The only impact is transitional, with dropped sessions to the XRP
server, Whois/Delegee server, and nameservers. Because the protocols re-initiate a failed transaction, even these operations are fully restored in less than 30 seconds with no loss of data
or transactions. 

O.13.9 Testing the System Restoration Process  

        NeuStar will test disaster recovery plans and outage restoration procedures annually to ensure that they can effectively restore system operations. 

O.13.10 Documenting System Outages  

        System problem documentation includes the following: 

	•
	The
system manager and the network manager systems collect performance and utilization statistics on system processors, system memory, LAN media and adapters, routers,
switches, system processes, and applications processes.

	•
	The
automated help desk database contains documentation on trouble tickets, whether they are generated by the system or generated by the Help Desk.

	•
	The
trouble ticket database contains the documentation of the steps taken to resolve trouble tickets.

	•
	The
data center manager collates, analyzes, and reports monthly statistics on help desk activities, system utilization and performance, and outages. 

O.13.11 Documenting System Problems That Could Result in Outages  

        NeuStar's proactive systems management processes include performance management, trend analysis, and capacity planning. These processes analyze system performance
and utilization data to detect bottlenecks and resource utilization issues that could develop into outages. Monthly reports on the three processes keep the data center manager apprised of our
performance against service level agreements and raise awareness of potential problems that could result in outages. 

        In
addition, NeuStar performs root cause analysis of hardware and software failures to determine and analyze the reason for any failure. On the basis of our findings, we work with
vendors to generate hardware service bulletins and software maintenance releases to prevent reoccurrence of these failures. 

O-77

 

O.14 Technical and Other Support  

        In addition to maintaining our central Help Desk and Technical Support Team, NeuStar will offer Web-based self-help support via a
Web-accessible portal, which will enable registrars to access our domain name application process, a knowledge base, and frequently asked questions. 

        NeuStar's
technical support will satisfy several criteria: 

	•
	It
must support all NeuStar-accredited registrars.

	•
	It
must support all current usTLD delegated managers in the existing usTLD locality space.

	•
	It
must support registrants in the existing usTLD locality space.

	•
	To
support the world's different time zones, access must be available worldwide, 24 × 7 × 365.

	•
	It
must accommodate the anticipated land rush when the expanded usTLD space is opened for registration. 

        For
the expanded usTLD space, NeuStar will conform to the ICANN registry model, which provides a clear, concise, and efficient deliberation of customer support responsibilities.
Registrars provide support to registrants, and registries provide support for registrars. This allows the registry to focus its support on the highly technical and administratively complex issues that
arise between the registry and the registrar. 

        For
the existing locality-based space, NeuStar will continue to support usTLD delegated managers and registrants in a manner consistent with the way they are currently supported. 

O.14.1 Technical Help Systems  

        NeuStar will provide the following types of technical support, all available on a 24 × 7 × 365 basis: 

	•
	Web-based
self-help services,

	•
	Knowledge
bases

	•
	Frequently
asked questions

	•
	White
papers

	•
	Downloads
of XRP client software

	•
	Support
for e-mail messaging

	•
	Telephone
support from our central Help Desk, and

	•
	Fee-based
consulting services. 

Web Portal  

        NeuStar will implement a secure Web-based multimedia portal to help support usTLD customer operations. To obtain access to our Web-based
services, customers must have implemented our security features, including SSL encryption, log in with user ID and password, and digital certificates for authentication. 

        The
home page of the Web portal will include a notice to customers of planned outages for database maintenance or installation of software upgrades. This notification will be posted
30 days prior to the event in addition to active notification including phone calls and e-mail. We will also record outage notifications in the help desk database to facilitate
compliance with the service-level agreement. 

O-78

 

Finally,
seven days and again two days prior to the scheduled event, we will use both an e-mail and a Web-based notification to remind registrars of the outage. 

        The
general Internet community may obtain generic information from NeuStar's public Web site, which will describe our usTLD service offerings and list certified registrars and delegated
managers providing domain name services. 

Central Help Desk  

        In addition to implementing the Web site, we will provide telephone support to our registrars through our central Help Desk. Access to the help desk telephone
support is through an automatic call distributor that routes each call to the next available customer support specialist. We will authenticate callers by using caller ID and by requesting a
preestablished pass phrase that is different for each registrar. Requests for assistance may also come to the Help Desk via e-mail, either directly or via the secure Web site. 

        The
Help Desk's three tiers of support are: 

        Tier-1 Support—Telephone support to usTLD Registry customers who normally are calling for help with domain name
problems and other issues such as XRP implementation or billing and collection. Problems that cannot be resolved at Tier 1 are escalated to Tier 2. 

        Tier-2 Support—Support provided by members of the Technical Support Team, who are functional experts in all
aspects of domain name registration. In addition to resolving escalated Tier 1 problems with XRP implementation and billing and collection, Tier 2 staff provide technical support in system tuning and
workload processing. 

        Tier-3 Support—Complex problem resolution provided by on-site maintenance technicians, third-party
systems and software experts, and vendors, depending on the nature of the problem. 

        In
turn, the Help Desk uses an automated software package to collect call statistics and record service requests and trouble tickets in a help desk database. The help desk database
documents the status of requests and tickets, and notifies the Help Desk when an SLA threshold is close to being breached. Each customer support and technical support specialist uses our problem
management process to respond to trouble tickets with a troubleshooting, diagnosis, and resolution procedure and a root-cause analysis. 

Escalation Policy  

        Our escalation policy defines procedures and timelines for elevating problems either to functional experts or to management for resolution if they are not
resolved within the escalation policy time limits. The following table is an overview of our escalation policy. 

O-79

 

Escalation Policy  

	Level
 
	 	Description
 
	 	Escalation Policy
 
	 	Notification
 

	I	 	Catastrophic outage affecting overall registry operations	 	Data center manager escalates to NeuStar management and Disaster Recovery Team if not resolved in 15 minutes	 	Web portal and e-mail notifications to all Registrars within 15 minutes; updates every 30 minutes
	

II	
 	

Systems outage affecting one or two XRP sessions but not the entire system	
 	

Systems engineer escalates to data center manager if not resolved in one hour	
 	

Web portal notification to all customers; hourly updates
	

III	
 	

Technical questions	
 	

Help Desk customer support specialist escalates to the systems engineer if not resolved in two hours	
 	

Hourly updates to customer via e-mail
	

IV	
 	

Basic questions	
 	

Help Desk customer support specialist escalates to the systems engineer if not resolved within four hours	
 	

Hourly updates to customer via e-mail

O.14.2 Staffing  

        Initially, NeuStar will staff its Help Desk with a complement of customer service specialists, enabling us to operate three shifts providing
24 × 7 × 365 coverage. We will add staff as necessary to respond to incoming requests within the service level agreement. Customer service
specialists will obtain assistance from NeuStar's technical staff for any problems that cannot be resolved in one phone call. 

O.14.3 Test and Evaluation Facility  

        NeuStar will establish an operational test-and-evaluation facility that will be available
24 × 7 × 365 for registrars and delegees to test their client XRP system. Our Technical Support Team, which consists of functional experts in the
processes and technologies for domain name registration, will support the registrars and delegees. 

        Once
each new registrar/delegee is satisfied that its system is compatible with the registry system, it will schedule a formal acceptance test that will be monitored by our system
engineer. After a registrar/delegee has passed the acceptance test, we will issue its user ID, passwords, and digital certificates, and the registrar/delegee can begin operations. 

O.14.4 Customer Satisfaction Survey  

        To determine customer satisfaction with registry services, NeuStar will implement a Web-based customer satisfaction survey that will consist of a set
of survey questions with responses ranging from one to five on the Likert Scale. We will tabulate the results and publish them on the Web site. 

        To
further verify the quality of our customer services, NeuStar will commission a biannual customer satisfaction survey by an independent third party. 

O-80

   P. Past Performance  

        NeuStar has the requisite and proven capability, administrative and technical experience, and professional integrity to responsibly
administer the usTLD to best serve the public interest while simultaneously enhancing its operation and usage.  

HIGHLIGHTS  

	•	Leading neutral third-party provider of mission-critical, U.S. public resource administration services for the communications industry since 1996
	

•	

Proven experience developing innovative solutions beneficial to the industry as a whole in a highly competitive environment
	

•	

A unique combination of world-class DNS registry and critical infrastructure operations expertise
	

•	

Strong corporate commitment and sound financial position
	

•	

Recipient of Supercomm Award for excellence in OSSs for the design and delivery of the NPAC SMS database

        The usTLD is a critical public resource that is seriously underutilized under its current administration. The United States is one of the world's technological
leaders, and its namespace should be positively perceived by the Internet community and highly regarded among Americans and the rest of the world. In fact, it should be the model of a successful,
widely used ccTLD. Instead, it is regarded as
cumbersome and overly hierarchical. In releasing the previous RFCs and this RFQ, the Department of Commerce has shown its desire to significantly improve the usTLD by bringing it into the global
Internet infrastructure while dramatically improving the awareness, utility, and value of the usTLD for its users. The DOC needs to select a responsible administrator who will meet these objectives
while maintaining and promoting the integrity of the usTLD and the Internet as a whole. All of these objectives can be met only by a vendor that has a proven ability to neutrally administer complex,
mission-critical systems while facilitating competition and progress in a competitive environment. Specifically, the DOC must select a vendor that has, among others, the following technical and
administrative qualifications: 

	•
	A
proven ability to administer complex, mission-critical U.S. public resources in a neutral, even-handed manner;

	•
	The
ability to facilitate controlled, systematic evolution, enhancement, and expansion of the space while preserving the rights of the current namespace users and ensuring
the protection of intellectual property and privacy;

	•
	Strong
working relationships with all stakeholders and experience facilitating progress in an extremely political and competitive environment;

	•
	A
comprehensive understanding of the space's evolution to date and the ability to address the long-term management issues associated with servicing and enhancing
its use;

	•
	Experience
designing, building, and supporting a robust database that requires extensive software development and infrastructure management capacity while ensuring the
security of personal contact data and license holder information;

	•
	The
ability to design and build a database that can scale seamlessly in response to anticipated growth; 

P-1

 

	•
	Experience
which ensures that data can be accessed by multiple users in real-time, that access to data is not hampered by system outages or unnecessary downtime,
and that a secure physical infrastructure is maintained to support all of its operations;

	•
	The
ability to understand, develop, and manage the associated policy issues to protect intellectual property, establish and maintain effective communication with
stakeholders, and promote healthy, robust competition;

	•
	A
proven reputation for fair, impartial policy management equitably supporting all stakeholders to ensure there is no bias or perception of bias; and

	•
	Strong
financial performance and stability. 

        NeuStar
is that vendor. Since 1996, NeuStar has successfully provided such mission-critical services to the U.S. communications industry. NeuStar possesses the strong management,
technical capabilities, strong financial performance, and depth of experience vital for the successful administration of the usTLD. 

        The
following table provides a detailed display of NeuStar's capabilities, as evidenced by our current projects and past performance. 

NeuStar's Capabilities and Qualifications  

	Vendor Qualification
 
	 	 
	 	NeuStar's Experience

	Administration of complex, mission-critical U.S. public resources	 	•	 	NeuStar established processes working with the FCC and state commissions for reclamation of central office codes that have not been activated by service providers.
	

 	
 	

•	
 	

NeuStar developed databases for the tracking of central office code activity for the U.S.
	

 	
 	

•	
 	

In conjunction with the industry and FCC, NeuStar developed a new method for reporting utilization and forecasting of numbering resources (NRUF)
	

Successfully transitioning administration of mission-critical public resources	
 	

•	
 	

Transitioned Telephone number administration from 10 companies with more than 100 local administrators across all 50 states to one central administrator
	

 	
 	

•	
 	

Transitioned telephone number inventory from more than 200 local databases to one central database
	

 	
 	

•	
 	

Have been contracted to transition telephone number inventory from thousands of local databases across all 50 states to one local database
	

Proven neutrality in all business operations	
 	

•	
 	

In CC Docket No. 92-237, FCC 99-346, NeuStar was found to be in compliance with the neutrality requirements put forth in the NANP Administration Third Report and Order.
	 	 	 	 	 

P-2

 

	

 	
 	

•	
 	

NeuStar undergoes a quarterly Neutrality audit performed by Ernst and Young, with a report forwarded to the FCC, NANC, and NAPM LLC. This report covers the findings of the audit regarding compliance with the NeuStar Code of Conduct and Neutrality
Compliance Procedures. NeuStar asserts that it is neutral, and Ernst and Young has agreed in all audit reports.
	

Facilitation of controlled, systematic evolution, enhancement, and expansion of the space.	
 	

•	
 	

NeuStar performs the change management administration function for the NPAC SMS on behalf of the telecommunications industry. This includes over 200 change orders resulting in 7 major software releases in 4 years.
	

 	
 	

•	
 	

NeuStar hosts quarterly NPAC operations forums, known as NPAC Cross regional meetings, where issues pertinent to the operation of the NPAC and its downstream systems are discussed and resolved.
	

 	
 	

•	
 	

NeuStar facilitated the transition of state number pooling trials to a national database focusing on a systematic evolution allowing for growth and future enhancements.
	

 	
 	

•	
 	

NeuStar works closely with industry and the FCC to develop enhancements to the existing NANPA process, including expansion of current functions.
	

Experience designing, building, and supporting robust databases	
 	

•	
 	

NeuStar designed, built, and expanded the NPAC database from inception to its current support of 17 million ported telephone numbers in the database. The growth rate of the database is currently increasing, having surpassed 1 million
additional records per month earlier this year.
	

 	
 	

•	
 	

NeuStar designed and built the pooling administration system to leverage the existing portability infrastructure. An existing NPAC database was adapted and scaled to support number pooling.
	

 	
 	

•	
 	

NeuStar developed various NANPA-related databases to enhance functionality and streamline work efforts associated with number administration. This allows for real-time tracking of number assignment, utilization, and forecasting data.
	 	 	 	 	 

P-3

 

	

 	
 	

•	
 	

Leveraging its experience with high-availability, mission critical system in the telecommunications industry, NeuStar is developing the next generation DNS architecture for the.biz registry.
	

Experience that ensures real-time access to multiple users with a minimum of system outages and downtime	
 	

•	
 	

NPAC offers a Low Tech Interface (LTI) dialup access. This capability currently supports over 700 clients, allowing for simultaneous access by over 200 users. This access method is also fully scalable.
	

 	
 	

•	
 	

While fully scalable, the NPAC currently supports over 500 dedicated accesses by various service providers.
	

Manage a high availability system to contractual service levels	
 	

•	
 	

The NPAC SMS has 29 contractual service level requirements, developed jointly with the industry, which are reported on monthly.
	

 	
 	

•	
 	

The.biz registry has SLAs with several major Channel Partners covering limited system downtime and system performance measures.
	

Comprehensive understanding of the usTLD's evolution	
 	

•	
 	

NeuStar has monitored proceedings on the usTLD and associated DOC activities.
	

 	
 	

•	
 	

NeuStar has subject matter experts on staff who were involved with the original development of the usTLD.
	

 	
 	

•	
 	

NeuStar is an active participant in various Internet-related forums such as the IETF and ICANN
	

Strong working relationships with stakeholders	
 	

•	
 	

NeuStar holds quarterly cross-regional meetings with LNPA stakeholders.
	

 	
 	

•	
 	

NeuStar holds weekly conference calls with LNP LLCs, the NPAC contracting parties, in addition to holding monthly face-to-face meetings to discuss operational issues.
	

 	
 	

•	
 	

NeuStar actively participates in various industry forums, including LNPA WG, NOWG, IETF, ICANN, and ITU.
	

 	
 	

•	
 	

NeuStar provides assistance to both the telecommunications industry and regulators in an effort to resolve difficulties in the area of number assignment, reporting, etc.
	

Facilitation of progress in a political and competitive environment	
 	

•	
 	

NeuStar acted as interim pooling administrator in several states prior to being selected as National Pooling Administrator.
	 	 	 	 	 

P-4

 

	

 	
 	

•	
 	

NeuStar facilitates NPA relief planning meetings, resulting in a relief plan which meets the needs of the industry and the regulators.
	

 	
 	

•	
 	

NeuStar provided objective information and assistance to the LNPA WG in an effort to resolve issues facing the entire telecommunications industry.
	

Ability to address long-term management issues	
 	

•	
 	

Developed Number Resource Utilization Forecasting tool, ensuring that appropriate detailed carrier information is collected, stored, analyzed, and properly distributed to appropriate regulatory authorities
	

 	
 	

•	
 	

Work closely with INC, NANC, and LNPA WGs to ensure that long term Number Resource Optimization needs are and will continue to be achieved
	

 	
 	

•	
 	

Developed long term strategic view of the needs of telecommunication service providers and regulators
	

Experience in building scalable databases that ensure security of personal data	
 	

•	
 	

NeuStar developed, deployed, and supports the Customer Account Management Exchange database, which contains highly proprietary service provider information.
	

 	
 	

•	
 	

NeuStar developed, deployed, and maintains the Number Portability Administration Center, which contains routing information for all calls placed in the US and Canada.
	

 	
 	

•	
 	

NeuStar maintains physical biometric facility security, with fulltime monitoring, strong physical security, and token authentication for dial-up access.
	

Ability to understand, develop, and manage all associated policy issues	
 	

•	
 	

NeuStar has an in-depth understanding all federal and state policy issues regarding number administration, in addition to meeting requirements developed by the industry which are seen to be the guidelines under which NANPA operates
	

 	
 	

•	
 	

NeuStar's experience in the policy rich telecommunications regulatory environment provides it with significant insight into the proper means for policy identification and coordination for the Internet.
	 	 	 	 	 

P-5

 

	

 	
 	

•	
 	

NeuStar is active in ICANN, the IETF and other Internet-related policy and standards bodies. NeuStar has a staff of experts on Internet policy and technical matters. NeuStar policy and legal experts participate heavily in ICANN constituencies'
activities.
	

 	
 	

•	
 	

NeuStar has an in-depth understanding of federal and state regulatory processes that are likely to be of prominent importance to Internet policy in the future.
	

Support and drive important technology standards	
 	

•	
 	

NeuStar is an active participant at the IETF where important internet technology protocols are developed. We are currently co-chairs of two IETF WGs including the Whois WG.
	

 	
 	

•	
 	

NeuStar has authored important IETF draft standards documents including one for a registry-registrar protocol.
	

 	
 	

•	
 	

NeuStar developed and patented the call processing technology used to enable telephone number portability. We patented the technology and made it freely available.
	

Proven reputation for fair, impartial policy management	
 	

•	
 	

NeuStar has extended its LNPA contract for an additional 3 years over its existing 5-year contract without going through the competitive bid process, with approval by the FCC.
	

 	
 	

•	
 	

NeuStar was selected by various service providers to provide Customer Account Record Exchange service via an in-house-developed database system.
	

 	
 	

•	
 	

Through its audit activities regarding NeuStar, Ernst & Young has consistently reported positive compliance to the Code of Conduct and Neutrality Compliance Procedures as approved by the FCC.
	

Strong financial performance and stability	
 	

•	
 	

NeuStar's existing lines of business are net income and cash flow positive
	

 	
 	

•	
 	

NeuStar's recent round of equity financing fully funded our business plan; if additional capital is required, our investment partner, Warburg Pincus, stands prepared to fund all NeuStar initiatives.
	

 	
 	

•	
 	

NeuStar has experienced strong revenue growth, from $6M in 1997 to $67M in 2000.

P-6

 

P.1 Registry, Database, and Internet Experience  

        NeuStar combines comprehensive registry operations experience with extensive DNS knowledge to effectively administer the
usTLD.

        Effective,
responsible administration of the usTLD requires that its operator understand the fluid, innovative environment of the Internet and demonstrate proven ability to build and
manage a registry. The usTLD registry operator must have substantial experience and proven credentials in managing a significant public database, the ability to facilitate discussions about standards
development and technical issues between competing parties, and a commitment to the security of proprietary data to ensure competition. In addition, the registry operator must have demonstrable
evidence of its ability to design, build, and maintain a robust, responsive, scalable, and secure database to ensure the highest levels of quality and flexibility in the changing world of global
communications. As an administrator, that operator must also have the ability to develop and manage policy issues, maintain strong working relationships with stakeholders, and control the systematic
evolution, enhancement, and expansion of the usTLD space. 

        NeuStar
is a leader and innovator in these areas and has been instrumental in the effective management, solution development, and policy guidelines for managing critical public
resources. Our administrative roles, as the North American Numbering Plan Administrator, Local Number Portability Administrator, and Pooling Administrator, directly qualify us for a similar role as
the usTLD Administrator. In all of these roles, we provide mission-critical resources to U.S.-based public resources. Furthermore, in all of these roles, we designed a transition plan that allowed us
to smoothly transition and begin operations, either on time or ahead of schedule. 

        NeuStar
has extensive experience in transitioning the administration of mission-critical public resources from multiple geographically dispersed entities to one central administrator.
Our transition of the North American Numbering Plan Administration (NANPA) from the legacy operators to NeuStar is a particularly relevant example. In 1997, NeuStar was awarded the responsibility of
administrating telephone numbers for the North American Numbering Plan. Prior to NeuStar's administration, ten large phone companies administered phone numbers across all fifty states. Each company
had multiple local number administrators in each state. Part of NeuStar's responsibility was to transition the administration from over a hundred local administrators. This required an intensely
coordinated effort involving site visits, coordination meetings, and progress reports. It was not uncommon to have to sift through file cabinets to find current and historical inventories. In many
cases, the existing administrators could provide little support because they were new to the job or did not have historical data. Despite the difficulty involved, NeuStar was able to transition the
administration well ahead of schedule. The NANPA registry of telephone number assignments is now a critical element of the U.S. telecommunications infrastructure. 

        A
second example involves the transition of telephone number inventory from hundreds of telephone companies with hundreds of different databases to one central database. NeuStar has won
number pooling administration contracts in over 12 different states. Number pooling involves transitioning unused telephone numbers from multiple telephone companies to one central administrator. The
unused numbers can then be redistributed to other telephone companies. This is a very difficult process, because it involves hundreds of phone companies with multiple administrators and different
databases. There is also a public outreach effort that involves assisting the phone companies in taking inventory, and evaluating the inventory for usable numbers. NeuStar has to advise the individual
companies on the format of the data and the process they need to undertake to transition the numbers to us. Once NeuStar has transitioned the inventory, we are responsible for redistributing it in a
neutral, even-handed, yet conservative manner. Recently, NeuStar was awarded the 

P-7

 

contract
to take on this responsibility on a federal level for all 50 states. This will involve over 3,000 different entities. 

        One
of the most significant benefits of a domain name is its portability and free movement between Internet Service Providers. The registry systems developed by NeuStar to administer
telephone numbering are directly analogous to a domain name registry, and parallels exist between the DNS and telephone number portability. For example, the telephone numbering system in North America
is broken down by area codes and a second set of three digits referred to as the NXX or prefix component of a telephone number. It is a hierarchical delegation system similar to the DNS. Prior to
1996, consumers were unable to enjoy the benefits of telephone number portability because of the monopoly environment at the Local Service Provider (LSP) level. In April 1996, NeuStar was
selected by the Illinois Commerce Commission SMS/RFP Subcommittee to develop a Number Portability Administration Center (NPAC) and provide turnkey and operational NPAC services initially within
Chicago. The Number Portability Administration Center (NPAC) Service Management System (SMS) is a master registry of routing information that interfaces with the local carrier's administration
systems. The NPAC SMS interfaces directly to Local Exchange Carriers' key operational systems and operation processes. The NPAC SMS developed and maintained by NeuStar coordinates the porting of
telephone numbers between carriers and downloads routing information to carriers' local systems, which in turn update local databases. 

        Since
the introduction of the NPAC, Local Number Portability has revolutionized the U.S. telecommunications industry. Through competitive procurement processes, NeuStar was selected to
provide telephone number registry services for a five-year term in four regions of the United States. The competing vendor was selected in the three remaining U.S. regions and Canada. In
early March 1998, the other three regions—Southeast, Western, and West Coast—terminated their vendor contracts due to poor performance and executed contracts with
NeuStar for NPAC SMS services, with Canada following soon after. Consequently, NeuStar now provides telephone number portability services to all of the United States and Canada, processing in excess
of tens of millions of transactions per day, and serving more than 4,000 service providers across North America. As the operator of the NPAC master telephone registry, NeuStar: 

	•
	Facilitates
technical discussions and standards development between competing carriers,

	•
	Safeguards
sensitive information,

	•
	Ensures
equal and fair access to vital network routing data,

	•
	Provides
impartial data measurement and analysis,

	•
	Coordinates
Local Number Portability implementation and testing,

	•
	Provides
independent and impartial certification of systems and databases,

	•
	Provides
impartial opinions (technical, policy, and schedule) to industry regulators,

	•
	Provides
services under industry agreed-upon guidelines and performance standards, and

	•
	Provides
full billing and collections services to more than 4,000 service providers. 

        All
of these qualifications are directly applicable to the administration of the usTLD. While the NPAC registry perhaps most clearly demonstrates NeuStar's experience in developing and
administering a registry, we have developed similar systems for the management of the North American Numbering Plan, European Telephony Numbering Space, Number Pooling, and the.biz TLD. In short,
NeuStar provides a level of skill and experience in registry operations in the United States that simply cannot be matched. 

P-8

 

P.2 Technical Capabilities  

        NeuStar offers comprehensive technical capabilities in the areas of registry operation, software development, database management, and
standards development. These abilities are founded on expansive experience in all areas related to technical service provision for a critical public resource. NeuStar is the best choice to design,
deliver, and maintain the next-generation domain name registry for the usTLD.

        Any
top-level domain registry operator must be capable of improving the reliability and effectiveness of domain name registration, contribute responsibly to a competitive
environment, and preserve the Internet's continuing stability. In addition, the registry operator must bring the technical know-how to specify and design a solution that ensures the
continuing evolution of the domain name system. 

        There
are many complexities within the DNS and registry environment that require a detailed understanding of the issues and their implications on the technical solution. For instance, a
minor change in policy can have far-reaching implications on how a database needs to behave in order to ensure the integrity and efficiency of domain name registration and administration.
But the usTLD space presents even more complexity because it must accommodate both the current hierarchical locality structure while allowing second-level registrations in the new, expanded space.
Management of the usTLD registry also brings with it an immense responsibility in the secure administration of personal and business contact information. The public sees a country code domain as
having the highest level of integrity, and it is essential that the registry operator understands this and stores all registry data with the highest levels of security. It is vital for the success of
the usTLD that the registry operator understands the entire operating environment and has the experience and ability
to deliver a solution that benefits all relevant stakeholders. NeuStar has the technical capabilities to deliver that solution. 

        NeuStar
specializes in developing and operating unique support services for the Internet and communications industries by using innovative solutions employing the highest standards and
practices and by providing services in an impeccably evenhanded fashion as a trusted third party. 

        As
the North American Numbering Plan Administrator, NeuStar operates the telephone numbering registry for the North American Numbering Plan as a public numbering resource. NeuStar is
also the Local Number Portability Administrator for the United States and Canada, operating the telephone number routing registry for North America. The integrity and accuracy of these services are
essential for virtually every call placed in North America. 

        The
Number Portability Administration Center Service Management System hosts the routing registry that is used to track network and call routing, SS7 signaling, and billing information
for all telephone numbers in North America. We provide, directly or indirectly, highly secure host-to-host administrative transaction interfaces to this registry for all 5,000
service providers in North America. The service providers' operational support systems (OSSs) require the highest availability standards of our service to manage and operate their networks. 

        Consequently,
we operate this service to 29 monthly service level requirements (SLRs), including availability (99.99%), transaction response time, throughput, and help desk
telephone call answer times, and we pay financial penalties for missing any of these levels. Between our data centers, we provide real-time database replication and server
failover/recovery functions and fully redundant enterprise networking facilities. Our data centers are owned and operated by NeuStar, are staffed 24 × 7 by our own network
operations center personnel, are physically located in the United States, and are secured by both card key and palm print readers. 

        NeuStar
operates its services, including the NPAC SMS, from a unique world-class Internet Protocal network and server infrastructure housed in our own diverse, redundant data centers. We 

P-9

 

operate
highly secure, quad redundant enterprise IP network application servers and support servers (e.g., DNS, NNTP, and RADIUS/SecurID) that provide dedicated access directly to more than 300
communication service providers and indirectly to all 5,000 service providers in North America. At approximately 900 Mbps of aggregate capacity, our IP network provides diverse BGP-4
routed links to external service provider OSSs and network elements. In addition, we support more than 1,000 dial-up or secured Internet users from our customers to access our services via
Web-based interfaces. In case of failure of a service provider's OSS, they may log directly into our Web-based NPAC GUI to provide critical network management functions. All
dial-up users (internal or external) must use a NeuStar-issued SecurID for strong authentication. 

        Each
data center has a completely redundant, hardened, switched VLAN backbone and a redundant set of network access servers and firewalls. All critical application and database servers
are dual-homed to each of these site-based backbones, using a virtual-IP address assigned to each host that is reachable through either NIC port on that host
through either backbone. Each NIC port and backbone link is assigned a 4-IP address subnet to ensure quick detection of NIC/link/port failures and maintain full reachability of that server
without impacting established internal or external communication associations. Certain key services (such as NPAC SMS application and database servers) are implemented using approximately 64 Lucent
(Stratus) hardware fault tolerant HP-UX servers. 

        The
NeuStar network is structured into a series of security rings to provide firewall isolation of traffic from various sources and applications. All Internet-reachable systems are
placed onto one of a series of bastion subnets (bracketed by firewalls) to ensure security of the core network in the unlikely case of a server breach on the bastion network. All external data network
links employ extensive BGP-4 route filtering to ensure that only appropriate internal routes are advertised and that routes to other service providers' networks are not advertised or
reachable. 

        While
extensively using standard, well-known, protocols (e.g., BGP-4), we also employ certain relatively unusual protocols, such as CMIP over IP, which are common
in OSS applications. The NPAC service employs this protocol to provide a distributed, bi-directional, object-oriented application framework for interacting with the registry. Strong
authentication is employed for accepting CMIP associations from service providers' OSSs, with an extensive administrative key management infrastructure to support. Each service provider system is
assigned a list of keys, each at least 660 bits in length. Each and every CMIP provisioning transaction is individually signed to provide the highest in authentication and non-repudiation,
given the potential operational and financial impacts one service provider could cause another. Given the millions of transactions we process every day, we have employed extensive hardware-based
crypto accelerators to ensure the highest performance levels without sacrificing security. Given the industry critical nature of the NPAC service, standardizing access to it from service providers'
OSSs was essential. In 1996 we developed the CMIP interface standards for the NPAC and subsequently placed
them in the public domain. They are now managed under the auspices of a specific industry standards body (the NANC LNPA WG) to whom we provide ongoing secretarial and change management support for
maintenance of the standards. 

        These
levels of standards are highly relevant and appropriate for a DNS registry provider, given the importance of the DOC's usTLD initiatives and the vital need to do so while enhancing
the value of the usTLD and maintaining the stability of the Internet. They exemplify our fluency with both the technical operational security and overall business standards with which
industry-critical services of this kind must be provided in the interest of all industry stakeholders. 

        NeuStar's
technical capabilities have extended even further since taking on the role of.biz registry operator. NeuStar's advanced TLD registration system uses a
high-performance and highly scalable 3-tier architecture. The tiers include a Web/protocol server tier, an application server tier, and a back-end server tier
(e.g., database, billing, credit card payments, and registry server). The registration 

P-10

 

system
has been developed with a custom-built application server and associated infrastructure. Security has been a priority throughout both the software architecture and network design. 

        The
infrastructure has built-in redundancy with multiple servers in the Web/protocol, application, and database tiers and has been engineered for high fault tolerance. In
addition, network devices such as routers, firewalls, and load-balancers have been deployed in a fully redundant configuration. Each tier is configured as a cluster, with failed servers
being automatically removed from the cluster. Capacity planning has been done to scale throughout the environment so that there is plenty of room for future growth. 

        Because
we operate through a channel partner network, we have experience providing integration protocols including http Post, XML, and e-mail templates and using security
mechanisms such as SSL and PGP. NeuStar's research group was an active leader in the development of new industry standards and has participated in the development of an XML-based domain
name registration protocol which has been deployed in our.biz operation. 

        The
scope of NeuStar's experience includes design and development of secure, real-time resource management systems; implementation of high-transaction,
high-availability database solutions; design and management of transcontinental IP networks; and the effective and timely delivery of technical solutions within highly regulated
environments. For all of these reasons, NeuStar is the best choice for developing and delivering a responsible and stable solution for the usTLD registry. 

P.3 Past Performance References  

        NeuStar's solid customer contact references are a reflection of the high regard in which NeuStar is held and are directly attributable to
our commitment to integrity.

        Some
vendors without extensive experience in developing and administering large-scale registry operations might not have the customer contact references needed to successfully meet the
DOC's requirements for the usTLD. Other vendors may have all the necessary references but will lack the neutral third-party component necessary to ensure that all users are dealt with in an equitable
manner and that a broad industry-wide approach to resolving the issues is taken. NeuStar has both. We are proud of our work and the relationships we have with our current customers and
respectfully submit the following past performance references for you to contact at your discretion. Further, we would welcome a site visit by the DOC Contracting Officer and COTR. 

P-11

 

Past Performance References Information  

	Required Information
 
	 	NeuStar Response

	Type of Work	 	[***]
	

Contract Number or Purchase Order Number	
 	

[***]
	

Duration of the Contract or Purchase Order	
 	

[***]
	

Dollar value of the Contract or Purchase Order	
 	

[***]
	

Type of Contract or Purchase Order	
 	

[***]
	

Name and Address of Customer Organization	
 	

[***]
	

Technical Point of Contact at Customer Organization for the Contract or Purchase Order	
 	

[***]
	

Information for an Alternative Customer Organization Point of Contact	
 	

[***]
	

Detailed Description of the Effort Performed by the Contractor/Subcontractor under the Contract or Purchase Order	
 	

[***]

[Five
tables omitted] 

P-12

   Q. Performance Measurements  

        NeuStar is committed to providing the highest level of quality and performance to ensure the overall integrity of this mission-critical
service.

HIGHLIGHTS  

        Performance
Measurements are designed to ensure: 

	•
	Objective assessment of NeuStar performance

	•
	High service availability and reliability of system

	•
	Commitment to credits for performance shortfalls—already included in usTLD Administrator Registrar Draft
Agreement

        When
the Department of Commerce selects a vendor, it must consider not only the vendor's cost components and ability to design and develop a system but also the overall quality of the
vendor's products and services. Because NeuStar is in the business of providing mission-critical services, quality is of utmost importance to us. We do not provide systems, we provide service. Our
staff recognizes quality and performance as an ongoing and evolving process that facilitates our commitment to continuous improvement by meeting the demands of our customers and the
ever-changing marketplace. Through education and training opportunities, we promote teamwork, empowerment, leadership, strategic planning, and personnel development. The quality
performance measurement system attributes managed by our staff include reliability, interoperability, availability, responsiveness, effective communication, accuracy, security, and one of our
strongest value-added trademarks—neutrality. 

        NeuStar's
Quality Management Program drives the delivery of all our services. Our performance measurement system, the heart of our Quality Management Program, is managed through
strategic Monthly Operational Reviews (MORs)—meetings of senior and executive management during which progress and results are discussed—as well as through various additional
operational and tactical reviews. In conjunction with our Quality Management Program, NeuStar is committed to constantly improving our services while ensuring high levels of responsiveness to customer
requests. NeuStar continues to work with its customers to identify the key processes required for problem resolution and delivery of quality services, including measures to assess database
performance, accessibility, and staff responsiveness to customer issues. Our Customer Relationship Management (CRM) practices capture aspects of our performance relevant to our customers to ensure
increased competitiveness, greater customer value, and delivery of world-class products and services. In addition, NeuStar's upper management commitment to provide world-class products and services to
our customers on a consistent, timely, and accurate basis is central. 

        NeuStar's
Quality Management Program ensures effective business account management, compliance with standards and applicable Service Level Agreements, and cost-effective
operations analysis while maintaining our competitive business edge within the communications industry. Our program is well administered and supported within NeuStar across all functional groups
including: 

	•
	Service
Delivery,

	•
	Program
Management,

	•
	Information
Technology,

	•
	Software
Engineering,

	•
	Systems
Quality Assurance, and

	•
	Configuration
Management. 

Q-1

 

        NeuStar
is committed to providing a high level of performance to the usTLD community. To that end, NeuStar proposes Performance Measurements related to the operation of the usTLD
registry. The purpose of these Performance Measurements is to ensure that the registry consistently performs at high levels to meet the needs of the industry, to ensure the reliability of this
mission-critical infrastructure, and to ensure stability of the usTLD. Comparable benchmarks for service level agreements are typical for public resources, and the usTLD should be no exception. 

        NeuStar
believes that Performance Measurements are so important to the proper functioning of the usTLD Administrator that we have integrated detailed Performance Measurements into our
usTLD Draft Registry-Registrar Agreements. Not only have we integrated the measurements into the agreements, but we have included credits to be paid to the registrars if we fail to meet any of them. 

        For
a detailed description of the Performance Measurements, please see Exhibit G of the usTLD Registry-Registrar Agreement in Section H of this proposal. For a detailed
description of the Performance Credits, please see Exhibit H of the same agreement. 

        We
believe these measures will provide accurate indicators of NeuStar's progress under the project and assessment of services offered. Further, as required, for the first two years of
the purchase order, we will submit monthly progress reports to the COTR, in writing, detailing the Contractor's progress toward meeting the purchase order SOW requirements. These reports are described
in Section B.2.15, Progress and Quarterly Reporting. 

Q-2

  

R.    Representations and Certifications of Offerors  

 
  REPRESENTATIONS AND CERTIFICATIONS OF OFFERORS    
    

1.     52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS (MAR 2001)  

        (a)(1) The
North American Industry Classification System (NAICS) code for this acquisition is 541519 

        (2)   The
small business size standard is $18.0 million. 

        (3)   The
small business size standard for a concern which submits an offer in its own name, other than on a construction or service contract, but which proposes to furnish a
product which it did not itself manufacture, is 500 employees. 

        (b)   Representations.
(1) The offeror represents as part of its offer that it o is,
ý is not a small business concern. 

        (2)   [Complete
only if the offeror represented itself as a small business concern in paragraph (b)(1) of this provision.] The offeror
represents, for general statistical purposes, that it o is, o is not, a small disadvantaged
business concern as defined in 13 CFR 124.1002. 

        (3)   [Complete
only if the offeror represented itself as a small business concern in paragraph (b)(1) of this provision.] The offeror
represents as part of its offer that it o is, o is not a women-owned small business concern. 

        (4)   [Complete
only if the offeror represented itself as a small business concern in paragraph (b)(1) of this provision.] The offeror
represents as part of its offer that it o is, o is not a veteran-owned small business concern. 

        (5)   [Complete
only if the offeror represented itself as a veteran-owned small business concern in paragraph (b)(4) of this provision.] The
offeror represents as part of its offer that it o is, o is not a service-disabled
veteran-owned small business concern. 

        (c)   Definitions.
As used in this provision— 

        "Service-disabled veteran-owned small business concern"— 

        (1)   Means
a small business concern— 

          (i)  Not
less than 51 percent of which is owned by one or more service-disabled veterans or, in the case of any publicly owned business, not less than
51 percent of the stock of which is owned by one or more service-disabled veterans; and 

         (ii)  The
management and daily business operations of which are controlled by one or more service-disabled veterans or, in the case of a veteran with permanent and severe
disability, the spouse or permanent caregiver of such veteran. 

        (2)   Service-disabled
veteran means a veteran, as defined in 38 U.S.C. 101(2), with a disability that is service-connected, as defined in 38 U.S.C. 101(16). 

        "Small
business concern," means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government
contracts, and qualified as a small business under the criteria in 13 CFR Part 121 and the size standard in paragraph (a) of this provision. 

        "Veteran-owned
small business concern" means a small business concern— 

        (1)   That
is at least 51 percent owned by one or more women; or, in the case of any publicly owned business, at least 51 percent of the stock of which is owned
by one or more women; and 

R-1

 

        (2)   The
management and daily business operations of which are controlled by one or more veterans. 

        "Women-owned
small business concern," means a small business concern— 

        (1)   Which
is at least 51 percent owned by one or more women or, in the case of any publicly owned business, at least 51 percent of the stock of which is owned
by one or more women; and 

        (2)   Whose
management and daily business operations are controlled by one or more women. 

        (d)   Notice.
(1) If this solicitation is for supplies and has been set aside, in whole or in part, for small business concerns, then the clause in this solicitation
providing notice of the set-aside contains restrictions on the source of the end items to be furnished. 

        (2)   Under
15 U.S.C. 645(d), any person who misrepresents a firm's status as a small, HUBZone small, small disadvantaged, or women-owned small business concern in order to
obtain a contract to be awarded under the preference programs established pursuant to section 8(a), 8(d), 9, or 15 of the Small
Business Act or any other provision of Federal law that specifically references section 8(d) for a definition of program eligibility, shall— 

          (i)  Be
punished by imposition of fine, imprisonment, or both; 

         (ii)  Be
subject to administrative remedies, including suspension and debarment; and 

        (iii)  Be
ineligible for participation in programs conducted under the authority of the Act. 

(End
of provision) 

	2.
	52.203-11 DEV 52.203-11 CERTIFICATION AND DISCLOSURE REGARDING PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS DEVIATION (JAN
1990)

        (a)   The
definitions and prohibitions contained in the clause, at FAR 52.203-12, Limitation on Payments to Influence Certain Federal Transactions, included in
this solicitation, are hereby incorporated by reference in paragraph (b) of this certification. 

        (b)   The
offeror, by signing its offer, hereby certifies to the best of his or her knowledge and belief as of December 23, 1989 that— 

        (1)   No
Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any agency, a Member of
Congress, an officer or employee of Congress, or an employee of a Member of Congress on his or her behalf in connection with the awarding of a contract resulting from this solicitation; 

        (2)   If
any funds other than Federal appropriated funds (including profit or fee received under a covered Federal transaction) have been paid, or will be paid, to any person
for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress on his or her behalf
in connection with this solicitation, the offeror must complete and submit with its offer, OMB standard form LLL, Disclosure of Lobbying Activities, to the Contracting Officer, and 

        (3)   He
or she will include the language of this certification in all subcontract awards at any tier and require that all recipients of subcontract awards in excess of
$100,000 must certify and disclose accordingly. 

        (c)   Submission
of this certification and disclosure is a prerequisite for making or entering into this contract imposed by section 1352, title 31, United States Code.
Any person who makes an expenditure prohibited under this provision or who fails to file or amend this disclosure form to be filed or amended by this provision, must be subject to a civil penalty of
not less than $10,000, and not more than $100,000, for each such failure. 

R-2

 

[End
of Clause] 

R-3

   S.    NeuStar's DUNS Number  

        NeuStar's Data Universal Numbering System (DUNS) number, presented below, is also provided on the bottom left-hand corner of the transmittal form. 

11-240-3295  

S-1

   T.    Transition and Project Plan  

        NeuStar's proven program management method-ology ensures the successful implementation of robust, high-availability
mission-critical systems and operations. NeuStar has a long legacy of transitioning administration of public resources to next-generation, open-interface platforms and will
effect a seamless, transparent, and low-risk transition through a thoughtful, deliberate transition plan.

HIGHLIGHTS  

	•
	NeuStar
has provided a detailed and thorough plan for the transition of usTLD, management and modernization of the locality-based space, and implementation of the expanded
space

	•
	NeuStar
applies our proven Program Management methodology to ensure that implementation is on-time, on-budget, and well-communicated and that it lays the foundation for a
successful business

	•
	NeuStar
uses mandatory quality assurance methods and reporting procedures in all functional areas to ensure that the highest level of performance is achieved 

        A
well-thought-out, proven program management methodology is a critical factor for implementing and running a successful TLD registry. Absent this critical
component, the project could easily fail. At NeuStar, we believe, of course, that such easily avoided failure is unacceptable. 

        Another
critical element for the successful implementation of the usTLD, is the need for a smooth, seamless transition from the legacy administrator to the new administrator. Indeed,
from NeuStar's perspective, a successful transition is the most important aspect of this project for maintaining stability and integrity of the usTLD and the Internet and ensuring the highest degree
of service to the United States Internet community. NeuStar has proven our capabilities in transitioning data and services from legacy systems to next-generation,
open-interface platforms numerous times. 

        NeuStar
has extensive experience in transitioning the administration of mission-critical public resources from multiple geographically dispersed entities to one central administrator.
Our transition of the North American Numbering Plan Administration (NANPA) from the legacy operators to NeuStar is a particularly relevant example. In 1997, NeuStar was awarded the responsibility of
administrating telephone numbers for the North American Numbering Plan. Prior to NeuStar's administration, ten large phone companies administered phone numbers across all fifty states. Each company
had multiple local number administrators in each state. Part of NeuStar's responsibility was to transition the administration from over a hundred local administrators. This required an intensely
coordinated effort involving site visits, coordination meetings, and progress reports. It was not uncommon to have to sift through file cabinets to find current and historical inventories. In many
cases, the existing administrators could provide little support because they were new to the job or did not have historical data. Despite the difficulty involved, NeuStar was able to transition the
administration well ahead of schedule. The NANPA registry of telephone number assignments is now a critical element of the U.S. telecommunications infrastructure. 

        A
second example involves the transition of telephone number inventory from hundreds of telephone companies with hundreds of different databases to one central database. NeuStar has won
number pooling administration contracts in over 12 different states. Number pooling involves transitioning unused telephone numbers from multiple telephone companies to one central administrator. The
unused numbers can then be redistributed to other telephone companies. This is a very difficult process, because it involves hundreds of phone companies with multiple administrators and different
databases. There is also a public outreach effort that involves assisting the phone companies in taking inventory, and evaluating the inventory for usable numbers. NeuStar has to advise the individual
companies on the format of the data and the process they need to undertake to 

T-1

 

transition
the numbers to us. Once NeuStar has transitioned the inventory, we are responsible for redistributing it in a neutral, even-handed, yet conservative manner. Recently, NeuStar
was awarded the contract to take on this responsibility on a federal level for all 50 states. This will involve over 3,000 different entities. 

        Because
of our firm belief that effective transition is an indispensable part of our overall project plan for the usTLD, we are presenting a detailed Transition Plan and explanation of
our comprehensive Project Plan. We are proud of our demonstrated ability to effect timely successful transitions of complex systems and are eager to apply our expertise to the usTLD. 

T.1    Transition to New usTLD Administrator  

        NeuStar will leverage our experience in successfully transitioning other mission-critical resources to ensure a smooth and seamless
transition of the usTLD administration.

        The
DOC faces a challenge in selecting a vendor that not only is qualified to build a robust registry system, but also is qualified to transition mission-critical operations and
resources, such as the existing locality-based usTLD. The usTLD domain structure is part of the Internet critical infrastructure, and many U.S. citizens rely upon its being a zero-downtime
operation. NeuStar has faced the challenge of transitioning these kinds of resources and has succeeded in all of our transition and implementation operations. NeuStar submits that no other potential
respondent to the RFQ has the kind of critical transition experience required by this RFQ. 

        The
key requirements for safe transition are careful planning; phased incremental transition stages, and the allocation of sufficient resources to oversee the process, achieve necessary
changes, and recover promptly from any difficulties that may arise. Absolutely crucial is the cooperation of the previous administrator. Our experience as the NANPA and LNPA have proven that
nonresponsiveness from legacy operators hinders progress and is detrimental to both the system and its customers. 

        The
DOC must ensure that it does not select a vendor for the usTLD that underestimates the importance of potential complexity of the transition process. The transition process that we
present here is comprehensive and sufficiently detailed in its incremental approach to transition of an operation involving critical infrastructure, to ensure a seamless and stable transition. 

T.1.1    Requirements for Successful Transition  

        Transition for the usTLD entails a number of different processes. 

	•
	The
first is transitioning existing administration and operation activities without making any policy changes.

	•
	The
second is reviewing and enhancing that existing structure.

	•
	The
third is expanding the structure with new names and services. 

        Because
the first two steps form the framework for the third step, this section focuses on these formative processes. The expansion and further enhancement of the usTLD is addressed
elsewhere in this proposal. Changes to the existing usTLD administration first require the compliance investigation and report that is correctly mandated by the DOC. This is because enhancements
cannot be intelligently specified without having much detail as possible about the current base of delegees and users, and changes need to be pursued as a collaborative effort with the existing usTLD
community. 

        To
initiate the transition process immediately upon award, certain information will be required: 

	•
	The master database—comprises contact and registration details for delegees and, where appropriate, registrants.
During normal operation of a registry, the DNS zone file and Whois file are derived from this master database. 

T-2

 

	•
	Operations information—refers to data that are available as part of the daily operation of the Internet, namely
the DNS zone files of names and addresses and the Whois file that contains essential delegee and registrant contact information.

	•
	Historical information—is necessary for evaluating the rights and obligations of delegees and registrants,
relative to changes made in the usTLD administration as of July 1, 1997. 

        The
specific information items required to initiate the transition process are: 

Requirements for a Successful Transition  

	NeuStar Needs From Current

Administrator
 
	 	Why/Benefits
 

	All contact information for current delegees	 	This information is needed to begin the required compliance investigation and report.
	

Historical information including delegations and re-delegations made after July 1, 1997	
 	

Historical data can put current situation in context. Delegation and re-delegation done after July 1, 1999 requires written proof.
	

Copy of zone file as of award date	
 	

Needed as a development tool to permit production testing prior to operational commitment.
	

All registration data, including but not limited to:	
 	

 
	

•

•

•

•

•

•

•

•	

Up-to-date list of all delegees including dates of delegation

Agreements with delegees

Agreements with registrants

Registration information for direct registrants

Policies and understandings, written or otherwise (generally understood)

Previous contracts, understandings, and agreements

Whois information

DNS zone snapshot at transition event	

 	

The complete set of registration data is needed in two phases. The first allows awardees to gain familiarity with the registrations and to prepare registration software. The second permits the awardees' operations databases to be current at the time
of handoff.

Information about delegees and agreements with them are essential for permitting awardees to make contact and understand existing arrangements with delegees.

Information about direct registrants and agreements with them is essential for the same reason.

Copies of existing policies allow NeuStar to continue operations and then introduce changes incrementally. The same is true for obtaining copies of existing databases.
	

Current, internal operational policies and procedures	
 	

Familiarity with existing practices is necessary to continue them and ensure that changes are incremental
	

Data formats	
 	

Essential for automated incorporation of existing data
	

Database administration and query volumes history	
 	

Historical operations data establish the scale of systems and operations to be provided by NeuStar.
	 	 	 	 

T-3

 

	

Final change requests for existing registrations	
 	

New registrations will not occur during transition, but changes to existing registrations may occur
	

Transition assistance from the current administrator	
 	

Assistance from the current contractor is at the core of all transition requirements, since it holds operational data, procedures, and registration agreements.
	

Transition of the www.us Web site from the current administrator to NeuStar	
 	

NeuStar will publish our own Web site for the usTLD, and needs Web site users to be able to easily find the new registry information.
	

Transition Assistance from IANA	
 	

Root server changes will be required to delegate.us to NeuStar

        We
believe that the above required information is reasonable and necessary for a seamless transition that is transparent to registrants and delegees and that will ensure the overall
stability of the usTLD, it operations, and the DNS and the Internet as a whole. 

T.1.2    Time Line for Transition  

        The schedule listed below gives a synopsis of the transition tasks and expected timing of these tasks starting from the award date. Although a quicker process is
possible, the timeline provided is ideal for the proposed transition. 

Transition Timeline  

	Schedule
	 	 
	 	Tasks

	Award Date	 	 	 	NeuStar requests:
	 	 	•	 	Current DNS TLD zone file
	 	 	•	 	Whois contact information file
	 	 	•	 	usTLD registration database
	 	 	•	 	Outreach to delegated managers begins
	 	 	•	 	All information regarding delegees
	 	 	•	 	Notify IANA of award
	

2 days post-award	
 	

 	
 	

NeuStar receives copies of existing:
	 	 	•	 	Zone file
	 	 	•	 	Whois file
	

7 days post-award	
 	

 	
 	

NeuStar receives copies of existing usTLD registration database

NeuStar receives contact information for all delegees, and information as to which delegees have signed a post-1997 delegee agreement

Development begins
	

21 days post-award	
 	

 	
 	

Development complete

Testing begins
	

28 days post-award	
 	

 	
 	

Testing complete

Begin live operations transition
	

35 days post-award	
 	

 	
 	

Complete live operations transition

IANA Delegates .us to NeuStar

T-4

 

T.1.3    Implementation  

        As shown in Exhibit T-1, NeuStar will follow these phases for the successful transition of administration and operations of the usTLD registry: 

	•
	Initiation and familiarization—NeuStar and the previous administrator must meet to arrange the delivery of
necessary data and information, as defined above. NeuStar must become familiar with the existing registry information and data formats in which it is transferred and will use this phase to prepare its
own systems for entry of the registry data. NeuStar has already begun this process by using standard DNS queries to build a database of zone information for the usTLD including the zone files of
delegated managers.

	•
	NeuStar System Initialization—NeuStar will load the provided data into its registry system and commence blind
operation and testing.

	•
	Parallel operations—Once NeuStar receives and loads all necessary data for operation of the usTLD, NeuStar and
the current administrator will run parallel operations for a period of time to ensure that the transition has occurred correctly. For this phase, NeuStar will run parallel DNS and Whois operations but
will not make any changes to current registrations or delegations or accept new registrations or delegations.

	•
	Parallel administration—Both the current administrator and NeuStar should receive any requests to changes in
registrations or delegations, but neither should accept new registrations or delegations during this time.

	•
	Hand-off of administration—The current administrator does not perform any changes to registrations or
delegations. At this point, NeuStar is the sole administrator of these functions, but the DNS and Whois operations remain in parallel.

	•
	Sole administration and operations—IANA delegates.us to NeuStar, the current administrator ends its DNS and Whois
operations, and NeuStar becomes the sole administrator and operator of the usTLD. 

T.1.4    Resources  

        NeuStar's implementation team, discussed in-depth in Section A, will include an dedicated transition team as an integral part of its
operations. This team will have significant experience in transitioning services and will work with the current administrator, delegees, and registrants to ensure that the transition is transparent to
all users and that the stability and integrity of the registry and the Internet is maintained. 

T.2    Project Plan  

        NeuStar's project plan explicitly addresses critical tasks to ensure successful implementation of the usTLD systems and
operation.

        A
well designed project plan will ensure that the usTLD project stays on schedule, management will anticipate necessary changes, strong team communications will be maintained, and
delivery will be on time. NeuStar's usTLD Project Plan outlines all phases and associated tasks required to successfully implement the usTLD systems and operations. 

        Exhibit T-1
provides a high-level Transition and Implementation Timeline. 

        We
will work to a detailed project plan to ensure all objectives are met. This project plan will include all major tasks/subtasks, duration, resources, and dependencies. 

T-5

 
GRAPHICS
TO COME 

T-6

 

T.2.1    High-level Task Descriptions  

        The following table provides overview descriptions of the major program responsibilities that NeuStar must successfully perform to meet the usTLD objectives. 

NeuStar Program Responsibilities  

	High-Level Tasks
 
	 	 
	 	Subtasks

	Project Management Project Initiation	 	•	 	Create project charter
	 	 	•	 	Create project notebook
	 	 	•	 	Assign project sponsor
	 	 	•	 	Obtain budget approval
	 	 	•	 	Create staffing plan
	 	 	•	 	Define roles and responsibilities
	 	 	•	 	Conduct initial team and project kickoff meetings
	 	 	•	 	Determine metrics for testing and production environments
	

Project Management Project Planning	
 	

•	
 	

Define scope
	 	 	•	 	Develop Work Breakdown Structure (WBS) and initial project schedule
	 	 	•	 	Create communications plan, risk management plan, stakeholder plan, quality plan, procurement plan, resource management plan, and change management plan
	 	 	•	 	Define usTLD product marketing plan
	 	 	•	 	Define usTLD business requirements
	 	 	•	 	Define usTLD outreach program
	 	 	•	 	Attend industry forums
	 	 	•	 	Define legal and policy requirements
	 	 	•	 	Define finance and budget plan
	 	 	•	 	Define administrative and facilities plan
	

Project Management Execution and Control	
 	

•	
 	

Implement locality-based usTLD operation and transition from the current administrator
	 	 	•	 	Modernize locality-based usTLD
	 	 	•	 	Implement expanded usTLD space functions
	 	 	•	 	Registrar accreditation and certification
	 	 	•	 	Sunrise
	 	 	•	 	Landrush
	 	 	•	 	Live expanded usTLD
	 	 	•	 	Deliver Monthly Progress Reports to COTR (For the 1st 2 years and quarterly thereafter)
	 	 	•	 	Deliver six-month Compliance Report
	

Project Management Closing	
 	

•	
 	

Customer acceptance
	 	 	•	 	Project turnover
	

System Development	
 	

•	
 	

Develop and finalize functional specifications
	 	 	•	 	Develop and finalize high-level design
	 	 	•	 	Develop and finalize detail design
	 	 	•	 	Conduct coding and unit test
	 	 	•	 	Data Migration/Population
	

Testing	
 	

•	
 	

Develop system and user test plans
	 	 	•	 	Establish test bed
	 	 	•	 	Develop integration test plan

T-7

 

	High-Level Tasks
	 	 
	 	Subtasks

	
 	
 	

•	
 	

Perform system test
	 	 	•	 	Conduct interface testing
	 	 	•	 	Perform connectivity testing
	 	 	•	 	Perform volume/load testing
	 	 	•	 	Perform end-to-end testing
	 	 	•	 	Perform User Acceptance Test (UAT)
	

Training	
 	

•	
 	

Develop training materials
	 	 	•	 	Conduct internal training sessions
	 	 	•	 	Conduct external training sessions
	

Production and Rollout	
 	

 	
 	

 
	 	 	•	 	Conduct production readiness review (go/no go)
	 	 	•	 	Roll out April 1, 2002

T.2.2    Staffing and Organization  

        The usTLD management team will ensure that its experienced, motivated team and knowledgeable staff are available for successful implementation. It will utilize
work breakdown structures, historical information, and understanding of scope and resource descriptions in determining resource needs. Appropriate staffing for implementation will ensure that
personnel resources are used effectively and efficiently. Periodically, NeuStar Program Management will evaluate the staffing levels and augment resources as necessary to meet the usTLD project
objectives. 

        NeuStar
Program Management will assist with the identification, documentation, and assignment of project roles and reporting relationships. The usTLD project team will provide status
updates on deliverables and resource changes to the Program Management Office. 

T.2.3    Monitoring, Control, and Change Management  

        NeuStar's project monitoring and control processes will be established to ensure that high performance standards are met at both participant and project levels
and to rapidly identify and address any issues or concerns that may arise during the usTLD project. Through strong schedule performance monitoring and control, unnecessary schedule slippage and cost
overrun will be mitigated. In addition, recognizing the occasional need for changes in project parameters, NeuStar will follow a strict change control process to ensure that necessary change does not
undermine project progress. NeuStar's monitoring and control objective will be to ensure that the activities of all participants are focused on achieving the usTLD project goals and requirements. 

        NeuStar's
change control process follows the major steps in submitting, analyzing, approving, and completing a change control request. All change requests are documented and logged into
a tracking system. Appropriate parties will be notified of the impact analysis and NeuStar's recommendation for action. 

T.2.4    Quality Assurance  

        NeuStar recognizes quality as an ongoing and evolving process that facilitates our commitment to continuous improvement by meeting the demands of our customers
and the ever-changing marketplace. Through education and training opportunities, we promote teamwork, empowerment, leadership, strategic planning, and personnel development. The quality
performance measurement system attributes managed by our staff include reliability, interoperability, availability, responsiveness, effective communication, accuracy, security, and one of our
strongest value-added trademarks—neutrality. Please see Section Q for more details on NeuStar's Quality and Performance Management process. 

T-8

usTLD Request for Quotation Response Compliance Matrix  

	RFQ Section
 
	 
	Requirement
	 	NeuStar Will

Comply
 
	 	Response

Section
 

	

B. Contractor Requirements	

The Contractor must perform the required services for this acquisition as a prime Contractor, not as an agent or subcontractor. (The provision of the required services may be accomplished through coordinating the resources and services provided by
entities other than the prime Contractor.) The Contractor must be (a) incorporated within one of the fifty states of the United States of America or the District of Columbia or (b) organized under a law of a state of the United States of America or
the District of Columbia. The Contractor must possess and maintain through the performance of this acquisition a physical address within the United States and must be able to demonstrate that all primary registry services will remain within the
United States of America (including the District of Columbia).	
 	

 	
 	

B
	

 	

The Contractor may not charge the United States Government for performance of the requirements of this purchase order (the unit price and amount for Line Items 0001, 0002 and 0003 must each be $0.00). However, the Contractor may establish and collect
fees from third parties for performance of the requirements of this purchase order, provided that the fee levels are approved by the Contracting Officer before going into effect, which approval will not be withheld unreasonably, provided that the fee
levels are fair and reasonable.	
 	

 	
 	

 
	

B.1 Statement of Purpose	

The Department of Commerce seeks to acquire centralized management and coordination of registry, registrar (where specified), database, and information services for the usTLD. In broadest terms, the usTLD was created to provide a locus for
registration of domain names to serve the Internet community of the United States, and is intended to be available to a wide range of registrants. Given the foregoing, the Department seeks quotations that will achieve the following
objectives:	
 	

N/A	
 	

Information Only
	

B.1	

 	

55.	

Ensure that procedures and a framework of accountability for the delegation and the administration of usTLD evolve into a more robust, certain, and reliable system.	
 	

 	
 	

B.1
	 	 	 	 	 	 	 	 

	

B.1	

 	

56.	

Promote increased use of the usTLD by the Internet community of the United States (including small businesses, consumers, Internet users, not-for-profit organizations, and local governments (i.e., state, city, and county), among others), with
residence or a bona fide presence in the United States) through introduction of enhanced services, dissemination of information through advertising and/or other appropriate mechanisms, and simplification of registration services including direct
registration.	
 	

 	
 	

B.1
	

B.1	

 	

57.	

Create a centrally administered and efficiently managed structure that ensures both registrant/consumer confidence and infrastructure stability through coordination of delegations as well as other appropriate functions.	
 	

 	
 	

B.1
	

B.1	

 	

58.	

Create a stable, flexible, and balanced environment within the usTLD that is conducive to innovation and that will meet the future demands of potential registrants.	
 	

 	
 	

B.1
	

B.1	

 	

59.	

Ensure continued stability of the domain name system as a whole and the usTLD, particularly throughout the transition period from the current management structure into the new structure developed and maintained under the Contractor.	
 	

 	
 	

B.1
	

B.1	

 	

60.	

Manage the usTLD consistent with the Internet Corporation for Assigned Names and Numbers' (ICANN) technical management of the DNS.	
 	

 	
 	

B.1
	

B.1	

 	

61.	

Allow for the adequate protection of intellectual property in the usTLD. This includes, in particular, the implementation of a "sunrise period" that permits qualified trademark owners to pre-register their trademarks as domain names in the expanded
usTLD space prior to the opening of the expanded usTLD space to wider registration, and a dispute resolution procedure to address conflicts between trademarks and domain names arising from "cybersquatting" in the usTLD.	
 	

 	
 	

B.1
	 	 	 	 	 	 	 	 

	

B.1	

 	

62.	

Establish and maintain consistent communication between the COTR, the Contractor and ICANN. This includes representation of the usTLD in the ICANN ccTLD constituency and contribution to ICANN's operating costs as apportioned to the usTLD through the
ICANN budget process.	
 	

 	
 	

B.1
	

B.1	

 	

63.	

Promote robust competition within the usTLD and in particular registration services that will lead to greater choice, new, and better services for users.	
 	

 	
 	

B.1
	

B.2 Core Registry Functions	

 	

The Contractor must provide, at a minimum, the services that are outlined below. This list should not be viewed as exhaustive. The Contractor must provide all systems, software, hardware, facilities, infrastructure, and operation for the following
functions:	
 	

 	
 	

B.2, B.2.1 - B.2.16
	

B.2	

64.	

 	

Operation and maintenance of the primary, authoritative server for the usTLD;	
 	

 	
 	

B.2.1, O.1, O.4, O.5
	

B.2	

65.	

 	

Operation and/or administration of a constellation of secondary servers for the usTLD;	
 	

 	
 	

B.2.2, O.1, O.4, O.5
	

B.2	

66.	

 	

Compilation, generation, and propagation of the usTLD zone file(s);	
 	

 	
 	

B.2.3, F, O.1, O.4, O.5
	

B.2	

67.	

 	

Maintenance of an accurate and up-to-date registration (WHOIS) database for all usTLD registrations;	
 	

 	
 	

B.2.4, F, O.1, O.3
	

B.2	

 	

68.	

Maintenance of an accurate and up-to-date database of usTLD subdelegation managers;	
 	

 	
 	

B.2.5, F, O.1, O.3
	

B.2	

 	

69.	

Establishment of a data escrow for usTLD zone file and domain name registration information, including chain of registration data;	
 	

 	
 	

B.2.6, F, O
	

B.2	

 	

70.	

Compliance with applicable Internet Engineering Task Force (IETF) and applicable ICANN policies for the functions outlined above; and	
 	

 	
 	

B.2.7, F, O.2
	

B.2	

 	

71.	

Promotion of awareness and registration in the usTLD including maintaining website with up-to-date policy and registration information for the usTLD.	
 	

 	
 	

B.2.8
	

B.3 Core Policy Requirements	

 	

The Contractor must:	
 	

N/A	
 	

Information Only
	 	 	 	 	 	 	 	 

	

B.3	

72.	
Implement United States Nexus Requirement: The Contractor must run the usTLD as a country code top level domain intended to serve the community of Internet users (including end users, business,
 government, and not-for-profit organizations, among others) resident or located with a bona fide presence in the United States, and is not intended to attract or otherwise encourage registrations from outside the United States. In addition to the
current policy set forth in RFC 1480 requiring that usTLD domain name registrations be hosted on computers located within the United States, the Contractor must implement a United States Nexus Requirement in both the locality-based usTLD
structure and the expanded usTLD space.	
 	

 	
 	

B.3.1
	

B.3	

73.	
Adopt ICANN Policies Pertaining to Open ccTLD's: Although the usTLD is intended to serve the Internet community of the United States, and is not intended to encourage registrations from
entities or individuals resident outside the United States, the Contractor must follow the ICANN policies pertaining to open ccTLD's unless otherwise directed by the Contracting Officer.	
 	

 	
 	

B.3.2
	

B.3	

74.	
Implement a Uniform Domain Name Dispute Resolution Procedure and Sunrise Policy. The Contractor must implement a uniform domain name dispute resolution procedure intended to resolve disputes
arising from "cybersquatting" applicable to the usTLD (such policy is intended to be modeled upon the ICANN Uniform Domain Name Dispute Resolution Procedure, consistent with modifications necessary for such policy to be applicable to the usTLD
specifically). The Contractor must also implement a "Sunrise Policy" that permits qualified trademark owners to pre-register their trademarks as domain names in the expanded usTLD space prior to the opening of the expanded usTLD space to wider
registration.	
 	

 	
 	

B.3.3
	

B.3	

75.	
Abide by Government Advisory Committee Principles: The Contractor must abide by the principles and procedures set forth in the Government Advisory Committee document "Principles for the Delegation and Management of
Country-Code Top Level Domains," unless inconsistent with U.S. law or regulation.	
 	

 	
 	

B.3.4
	 	 	 	 	 	 	 	 

	

B.4 Locality-based usTLD Structure Functions	

 	

 	

The Contractor must:	
 	

N/A	
 	

Information Only
	

B.4	

76.	

 	

Provide Service for Existing Delegees and Registrants: Provide service and support for existing delegees and registrants in the existing, locality-based usTLD structure under current practice, including policies set forth in
RFC 1480 and other documented usTLD policies.	
 	

 	
 	

B.4.1, F, O
	

B.4	

77.	

 	
Provide Services for Undelegated Third Level Sub-Domains: Provide direct registry and registrar services for all other undelegated third level locality sub-domains, including services for CO
and CI, and undelegated special purpose domains (K12, CC, TEC, LIB, MUS, STATE, DST, COG and GEN).	
 	

 	
 	

 
	

B.4	

78.	

 	

Modernize Locality-Based usTLD processes: The Contractor must modernize and automate the locality-based usTLD delegation and registration process under the control of the usTLD administrator, including the creation of an electronic database to store
historical usTLD registration data.	
 	

 	
 	

B.4.2, F, O
	

B.4	

79.	

 	
Coordinate Current Locality-Based usTLD Users: The Contractor must create a mechanism or mechanisms whereby delegated managers of the usTLD, users of the locality-based usTLD, traditional
usTLD user groups (such as state and local governments, the library community and educational institutions, among others), and other interested parties, can coordinate to discuss usTLD administrative, technical, and policy issues related to the
operation and management of locality-based usTLD structure.	
 	

 	
 	

B.4.4, B.3.5
	 	 	 	 	 	 	 	 

	

B.4	

80.	

 	
Investigate Compliance with Current Locality-Based usTLD Policies: The Contractor must conduct an investigation (or commission such an investigation) and submit a report to the COTR, within
six months after purchase order award, evaluating the compliance of existing sub-domain managers with the requirements of RFC 1480 and other documented usTLD policies. Further, the study should include an evaluation of "locality-squatting" issues, or
the practice of registering a locality name without providing a responsive level of service to such locality. Such report must recommend structural, procedural, and policy changes designed to enhance such compliance or improve usTLD registration
services and increase the value of the locality-based usTLD structure to local communities. During this evaluation period, the Contractor must not make any additional locality delegations or transfers unless otherwise directed by the Contracting
Officer.	
 	

 	
 	

B.4.5
	

B.4	

81.	

 	
Develop Database of usTLD Delegated Managers: The Contractor must develop a single database for up-to-date and verified contact information for all delegated managers in the usTLD, including
to locality-level and functional second level (where delegated) administrators and, where applicable, for all sub-delegations made by such locality-level or second level administrators. Such databases should allow for multiple string and field
searching through a free, public, web-based interface, and consist of at least the following elements:	
 	

 	
 	

B.4.6, F, O
	

 	

•	

The name of the delegated manager;	
 	

 	
 	

 
	

 	

•	

The IP address of the primary nameserver and secondary nameserver(s) for the delegation;	
 	

 	
 	

 
	

 	

•	

The corresponding names of those nameservers;	
 	

 	
 	

 
	

 	

•	

The date of delegation;	
 	

 	
 	

 
	

 	

•	

The name and postal address of the delegated manager;	
 	

 	
 	

 
	 	 	 	 	 	 	 	 

	

 	

•	

The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the delegated manager;	
 	

 	
 	

 
	

 	

•	

The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the delegated manager; and	
 	

 	
 	

 
	

 	

•	

The website or other contact information through which registrations can be accepted under that delegation.	
 	

 	
 	

 
	

B.4	

82.	
Develop Registrant WHOIS Database: The Contractor must develop an enhanced searchable WHOIS database that contains, or provides reliable access to, all locality-based usTLD registrants
including the registrants of delegated usTLD managers and, where applicable, registrants located under delegated managers' sub-delegations. Such WHOIS database must allow for multiple string and field searching through a free, public, web-based
interface, and consist of at least the following elements:	
 	

 	
 	

B.4.7, F, O
	

 	

•	

The name of the domain registered;	
 	

 	
 	

 
	

 	

•	

The Internet Protocol (IP) address of the primary nameserver and secondary nameserver(s) for the registered domain name;	
 	

 	
 	

 
	

 	

•	

The corresponding names of those nameservers;	
 	

 	
 	

 
	

 	

•	

The identity of the delegated manager under which the name is registered;	
 	

 	
 	

 
	

 	

•	

The creation date of the registration;	
 	

 	
 	

 
	

 	

•	

The name and postal address of the domain name holder;	
 	

 	
 	

 
	

 	

•	

The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder; and	
 	

 	
 	

 
	

 	

•	

The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder.	
 	

 	
 	

 
	

B.5 Expanded usTLD Space Functions	

The Contractor must not act as a registrar in the expanded usTLD space. Presented below is a non-exhaustive list of elements that the Contractor must incorporate into its procedures and policies for the expanded usTLD structure:	
 	

 	
 	

B.5
	 	 	 	 	 	 	 	 

	

B.5	

83	
Develop and Implement Shared Registration System: The Contractor must develop and implement a shared registration system whereby qualified competing registrars may register domain names for
their customers in the expanded usTLD space (i.e., example.us). At a minimum, this proposed shared registration system must allow an unlimited number of accredited/licensed registrars to register domain names in the expanded usTLD; provide equivalent
access to the system for all accredited/licensed registrars to register domains and transfer domain name registrations among competing accredited/licensed registrars; update domain name registrations; and provide technical support for
accredited/licensed registrars.	
 	

 	
 	

B.5.1, F, O
	

B.5	

 	

84.	
Accreditation of usTLD Registrars: The Contractor must develop and implement a process describing the manner in which registrars in the expanded usTLD space will be accredited to register
names in the expanded usTLD.	
 	

 	
 	

B.5.2
	

B.5	

 	

85.	
Technical Certification of usTLD Registrars: The Contractor must develop and implement a process for technical certification of registrars in the expanded usTLD space.	
 	

 	
 	

B.5.3, O
	

B.5	

 	

86.	
Develop WHOIS Database: The Contractor must develop an enhanced searchable WHOIS database that contains, or provides reliable access to, all expanded usTLD registrations. Such WHOIS database
must be operated at the registry level (as opposed to at the level of individual accredited registrars) and allow for multiple string and field searching through a free, public, web-based interface, and consist of at least the following
elements:	
 	

 	
 	

B.5.4, F, O
	

 	

•	

The name of the second level domain registered;	
 	

 	
 	

 
	

 	

•	

The IP address of the primary nameserver and secondary nameserver(s) for the registered domain name;	
 	

 	
 	

 
	

 	

•	

The corresponding names of those nameservers;	
 	

 	
 	

 
	

 	

•	

The creation date of the registration;	
 	

 	
 	

 
	 	 	 	 	 	 	 	 

	

 	

•	

The name and postal address of the domain name holder;	
 	

 	
 	

 
	

 	

•	

The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the domain name holder; and	
 	

 	
 	

 
	

 	

•	

The name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the domain name holder.	
 	

 	
 	

 
	

B.5	

 	

87.	
Community Outreach Plan: The Contractor must develop a public outreach mechanism whereby the public space can suggest or recommend additional policies or procedures for the usTLD that may be
developed or suggest how existing policy should be modified or updated.	
 	

 	
 	

B.5.5, B.3.5

usTLD Request for Quotation Response Compliance Matrix  

	RFQ Section
 
	 
	Requirement
	 	NeuStar Will

Comply
 
	 	Response

Section
 

	C. Reporting Requirements and Deliverables	 	The Contractor must post the following reports on their Internet site in order to facilitate transparency and public access.	 	X	 	B.2.15, B.4.5
	

C.1

Investigational Study (One-Time Report Due Six Months After Purchase Order Award)	

 	

The Contractor must conduct an investigation and submit a written report to the COTR, within six months after purchase order award, evaluating the compliance of existing sub-domain managers with the requirements of RFC 1480 and other documented usTLD
policies. Such report must recommend structural, procedural, or policy changes designed to enhance such compliance and increase the value of the locality-based structure to local communities. During this evaluation period, the Contractor must make no
additional locality delegations unless otherwise directed by the Contracting Officer.	
 	

X	
 	

B.4.5
	

C.2

Progress Reports	

 	

For the first two years of the purchase order, the Contractor must submit monthly progress reports to the COTR, in writing, detailing the Contractor's progress towards meeting the purchase order SOW requirements. Thereafter, such reports must be
provided to the COTR on a quarterly basis.	
 	

 	
 	

 

	

 	

 	

These reports must indicate the status of all major events, as well as major work performed during the month, including technical status, accomplishments, and complications experienced in fulfilling the SOW requirements, and must be submitted in such
detail and form as required by the COTR. Such reports must also provide performance data related to operation of the usTLD including, but not limited to, the following: the total number of registry transactions; the number of new, transferred or
deleted registrations in the usTLD (including cumulative registrations over time); the number of delegated managers and changes in delegated managers in the locality-based usTLD space; the number of registrars accredited to register names in the
expanded usTLD space, including the operational status of those registrars; and any updates or modifications to the shared registration system made by the Contractor.	
 	

X	
 	

B.2.15
	

 	

88.	

52.203-12 DEV 52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS (DEVIATION NOV 1990) (JUN 1997)	
 	

N/A	
 	

Information Only
	

 	

 	

    89.	

52.204-6 DATA UNIVERSAL NUMBERING SYSTEM (DUNS) NUMBER (JUNE 1999)	
 	

X	
 	

S
	

 	

 	

    90.	

52.213-4 TERMS AND CONDITIONS—SIMPLIFIED ACQUISITIONS (OTHER THAN COMMERCIAL ITEMS) (MAR 2001)	
 	

N/A	
 	

Information Only
	

 	

 	

    91.	

52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)	
 	

N/A	
 	

Information Only
	

 	

 	

    92.	

52.227-17 RIGHTS IN DATA—SPECIAL WORKS (JUN 1987)	
 	

N/A	
 	

Information Only
	

 	

 	

    93.	

1352.233-70 HARMLESS FROM LIABILITY (MARCH 2000)	
 	

N/A	
 	

Information Only
	

 	

 	

    94.	

1352.233-71 SERVICE OF PROTESTS (MARCH 2000)	
 	

N/A	
 	

Information Only
	

 	

 	

    95.	

1352.252-71 REGULATORY NOTICE (MARCH 2000)	
 	

N/A	
 	

Information Only
	

 	

 	

    96.	

52.233-1 I DISPUTES (DEC 1998)—ALTERNATE I (DEC 1991)	
 	

N/A	
 	

Information Only
	

 	

 	

    97.	

52.239-1 PRIVACY OR SECURITY SAFEGUARDS (AUG 1996)	
 	

N/A	
 	

Information Only
	 	 	 	 	 	 	 	 

	

 	

 	

    98.	

1352.201-70 CONTRACTING OFFICER'S AUTHORITY (MARCH 2000)	
 	

N/A	
 	

Information Only
	

 	

 	

    99.	

1352.201-71 CONTRACTING OFFICER'S TECHNICAL REPRESENTATIVE (COTR) (MARCH 2000)	
 	

N/A	
 	

Information Only
	

 	

 	

  100.	

ANSWERS TO ANTICIPATED OFFEROR QUESTIONS	
 	

N/A	
 	

Information Only
	
Representations and Certifications of Offerors	
 	

 	
 	

 
	

 	

101. 52.219-1 SMALL BUSINESS PROGRAM REPRESENTATIONS (MAR 2001)	
 	

X	
 	

R
	

 	

102. 52.203-11 DEV 52.203-11 CERTIFICATION AND DISCLOSURE REGARDING PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS DEVIATION (JAN 1990)	
 	

X	
 	

R
	
Instructions for Submitting Quotations	
 	

 	
 	

 
	

 	

 	

Before submitting a quotation, Offerors are encouraged to review the information on the locality-based usTLD structure and registration policies at: http://www.nic.us	
 	

N/A	
 	

Information Only
	

 	

 	

The Offeror must submit the ORIGINAL VERSION and TWO COPIES of the Quotation to the following address: ATTN JOSEPH L WIDDUP NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY 100 BUREAU DR STOP 3571 BLDG 301 RM B129 GAITHERSBURG MD 20899-3571 M/F
SOLICITATION SB1335-01-Q-0740 Each quotation (original and copies) submitted in response to this solicitation must:	
 	

N/A	
 	

Information Only
	

 	

 	

ATTN JOSEPH L WIDDUP

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY

100 BUREAU DR STOP 3571

BLDG 301 RM B 129

GAITHERSBURG MD 20899-3571

M/F SOLICITATION SB1335-01-q-0740	
 	

N/A	
 	

Information Only
	

 	

 	

Each quotation (original and copies)submitted in response to this solicitation must	
 	

N/A	
 	

Information Only
	

 	

A.	

Include resume(s) of key personnel (including education and experience credentials) that would perform and/or manage the requirements of this acquisition.	
 	

X	
 	

A
	 	 	 	 	 	 	 	 

	

 	

B.	

Describe how the Offeror would satisfy each of the individual requirements described in the "Contractor Requirements" section of the SOW. (In the event that the provision of the required services would be accomplished through coordinating the
resources and services provided by entities other than the prime Contractor, the quotation must explicitly indicate how the Contractor will ensure that the "Contractor Requirements" will be fulfilled.)	
 	

X	
 	

B, B.1—B.16
	

 	

C.	

In light of the "Statement of Purpose" in the SOW, present a detailed narrative describing the Offeror's overall vision for future management of the usTLD, including how the Offeror proposes to make the usTLD more attractive and useful to United
States Internet users and the Offeror's expectations for the number of potential usTLD registrants.	
 	

X	
 	

C
	

 	

D.	

Describe any services or functions, if any, the Offeror proposes to perform as part of usTLD management in addition to those listed in the SOW.	
 	

X	
 	

D
	

 	

E.	

Demonstrate clearly, concisely and accurately, in written narrative form, the Offeror's understanding of the current state of the usTLD domain space.	
 	

X	
 	

E
	

 	

F.	

Describe, for the SOW requirement related to the development of a database of usTLD delegated managers, and the development of registrant WHOIS databases (both for the locality-based usTLD structure and the expanded usTLD space) how the Offeror would
collect the necessary information and the technical and operational specifications of the databases.	
 	

X	
 	

F, B.2.4,B.2.5
	

 	

G.	

Include a proposed draft of any contract(s) that the Offeror proposes to use between itself, as Contractor, and usTLD delegated managers (which may include "flow through" registration agreements to be used by locality-based usTLD registrants)
considered necessary to ensure the stable operation of the locality-based usTLD structure and implement necessary policies. Note: The content of the final version of all such contract(s) must be approved by the Contracting Officer before use by the
Contractor in performance of the resultant purchase order.	
 	

X	
 	

G
	 	 	 	 	 	 	 	 

	

 	

H.	

Include a proposed draft of any contract(s) that the Offeror proposes to use between itself, as Contractor, and expanded usTLD registrars to ensure the stable operation of the expanded usTLD and implement the necessary policies (which may include
shared registration system license agreements, registrar accreditation agreements, and registrant agreements). Note: The content of the final version of all such contract(s) must be approved by the Contracting Officer before those contract(s) may be
used by the Contractor in performance of the resultant purchase order;	
 	

X	
 	

H
	

 	

I.	

Include written policies (including implementation details) that the Offeror proposes to follow, as Contractor, during the start-up phase of registrations in the usTLD. Such description must include the following considerations:	
 	

X	
 	

I, B.3.1,B.3.3, B.3.5
	

 	

 	

1.	

How the Offeror would design and implement the "Sunrise Policy" that permits qualified trademark owners to pre-register their trademarks as domain names in the expanded usTLD space prior to the opening of the expanded usTLD space to wider
registration.	
 	

 	
 	

 
	

 	

 	

2.	

How the Offeror would implement a uniform domain name dispute resolution procedure intended to resolve disputes arising from "cybersquatting" applicable to the usTLD (such policy is intended to be modeled upon the ICANN Uniform Domain Name Dispute
Resolution Procedure, consistent with modifications necessary for such a policy to be applicable to the usTLD specifically. Offeror should propose necessary modifications).	
 	

X	
 	

I, B.3.1, B.3.3, B.3.5
	

 	

 	

3.	

How the Offeror proposes to implement and enforce the United States nexus requirement intended to preserve the usTLD for use by the community of United States Internet users.	
 	

 	
 	

 
	

 	

 	

4.	

Describe any proposed additional, alternative, or supplemental policies or programs the Offeror considers relevant and essential towards the locality-based usTLD space or the expanded usTLD space.	
 	

 	
 	

 

	

 	

Offerors should also describe additional procedures that address other considerations than those listed above that they consider relevant to their quotation.	
 	

 	
 	

 
	

 	

J.	

Address the following considerations in the description of the registration process:	
 	

X	
 	

J
	

 	

 	

1.	

How the Offeror proposes to address the potential initial "rush" for registrations at the opening of the expanded usTLD space.	
 	

 	
 	

 
	

 	

 	

2.	

Describe the proposed application process for potential registrants;	
 	

 	
 	

 
	

 	

 	

3.	

Describe the proposed mechanisms for ensuring that registrants meet registration requirements;	
 	

X	
 	

J
	

 	

 	

4.	

Describe any proposed appeal process that could be used by the applicant as a result of Contractor denial of registration.	
 	

 	
 	

 
	

 	

 	

5.	

Describe any proposed procedure that would permit third parties to seek cancellation of a registration for failure to comply with restrictions imposed by the Contractor.	
 	

 	
 	

 
	

 	

K. Describe in detail the proposed mechanisms and community outreach plans for coordinating the current locality-based usTLD users and the mechanism by which the public can suggest or recommend additional policys or procedures for the
usTLD.	
 	

X	
 	

K, B.3.5
	

 	

L.	

Describe, in detail, how the Contractor would fund the requirements of this acquisition at no cost to the United States Government.	
 	

X	
 	

L
	

 	

M.	

Project/estimate and explain annual Contractor costs for this acquisition in such a way to permit the Government to match those costs to specific SOW Contractor Requirements.	
 	

X	
 	

M
	

 	

N.	

Include detailed proposed financial plans, including, if appropriate, the manner in which fees levied for services rendered by the Contractor would be derived, considering cost plus a fair and reasonable profit.	
 	

X	
 	

N
	 	 	 	 	 	 	 	 

	

 	

O.	

Describe, in detail, the technical facilities, equipment, software, hardware, and related technology that the Offeror would use to meet the requirements of this acquisition.	
 	

X	
 	

O
	

 	

P.	

Include no more than five past performance references for other efforts similar in scope to this acquisition that were either (a) completed by the Offeror (either as a prime Contractor or as a first-tier subcontractor) in the past five years or (b)
currently in process. For each past performance reference, include the following information:	
 	

X	
 	

P
	

 	

 	

1.	

Contract Number/Purchase Order Number;	
 	

 	
 	

 
	

 	

 	

2.	

Duration of the Contract/Purchase Order;	
 	

 	
 	

 
	

 	

 	

3.	

Dollar Value of Contract/Purchase Order (Broken Down on a Per-Year Basis, if Applicable);	
 	

 	
 	

 
	

 	

 	

4.	

Contract type of Contract/Purchase Order (e.g., firm-fixed-price, cost-plus-fixed-fee, cost-plus-award-fee, fixed-price with economic price adjustment);	
 	

 	
 	

 
	

 	

 	

5.	

Name and Mailing Address of Customer Organization;	
 	

 	
 	

 
	

 	

 	

6.	

Technical Point of Contact at Customer Organization for the Contract/Purchase Order, including Phone Number, Fax Number and Email Address;	
 	

 	
 	

 
	

 	

 	

7.	

Information Noted in I.4 above for an Alternate Customer Organization Point of Contact; and	
 	

 	
 	

 
	

 	

 	

8.	

Detailed Description of the Effort Performed by the Contractor/Subcontractor under the Contract/Purchase Order. At the discretion of the Contracting Officer, a site visit to the Offeror's facility(ies) may also be requested and conducted by DOC
personnel involved in this acquisition. The purpose of this visit would be to gather information relevant to the Offeror's submitted quotation. The Contracting Officer would arrange such a visit at least seven days in advance with the
Offeror.	
 	

 	
 	

 
	 	 	 	 	 	 	 	 

	

 	

Q.	

Describe, in detail, proposed performance measures that will provide accurate indicators of the Contractors progress under the project and assessment of services offered	
 	

X	
 	

Q
	

 	

R.	

Include a completed copy of "Offeror Representations and Certifications" from this solicitation.	
 	

X	
 	

R
	

 	

S.	

The Offeror's Data Universal Numbering System (DUNS) Number. (See FAR 52.204-6 on page 16 of this solicitation.)	
 	

X	
 	

S
	
Evaluation Criteria for Award	
 	

 	
 	

 
	

 	

 	

A quotation will only be considered if it is submitted by an organization that is (a) incorporated within one of the fifty states of the United States of America or the District of Columbia or (b) organized under a law of a state of the United States
of America. The Contractor must have a physical address within the United States of America or the District of Columbia and must be able to demonstrate that all primary registry services will remain within the United States of America (including the
District of Columbia).	
 	

 	
 	

 
	

 	

 	

The Government will evaluate quotations submitted in response to this acquisition for services and will award a purchase order to the technically acceptable, responsible Offeror whose quotation represents the best value. Technical excellence and
comprehensiveness of the overall service for usTLD operation is significantly more important than proposed price(s) to.us registrants. The evaluated price for all quotations, in terms of the price paid by the Government, will be $0.00. This
acquisition is being conducted under FAR Part 13, Simplified Acquisition Procedures. Under FAR Part 13, solicitations are not required to state the relative order of importance assigned to each evaluation factor and subfactor, nor are they
required to include subfactors. The evaluation factors are listed below.	
 	

 	
 	

 
	

 	

•	

Technical excellence and comprehensiveness of the offered service—For this factor, the Government will evaluate responses to items A through O and item Q in the "INSTRUCTIONS FOR SUBMITTING QUOTATIONS."	
 	

N/A	
 	

Information Only
	 	 	 	 	 	 	 	 

	

 	

•	

Past performance information—For this factor, the Government will evaluate information obtained from past performance references provided by the Offeror in their quotation in response to item "P" in the "INSTRUCTIONS FOR SUBMITTING QUOTATIONS"
section of the solicitation, as well as any other relevant past performance information that the Government obtains about the Offeror from other sources;	
 	

 	
 	

 
	

 	

•	

Reasonableness of proposed price(s) to.us registrants. For this factor, the Government will determine whether the proposed price(s) to the registrants are fair and reasonable considering the level of service(s) to be provided to the.us
registrants.	
 	

 	
 	

 
	

 	

 	

For the purposes of this solicitation, "best value" means the expected outcome of an acquisition that, in the Government's estimation, provides the greatest overall benefit in response to the requirement. In this solicitation, the term "best value"
is not meant to imply that a specific tradeoff process (as described in FAR Part 15, Contracting by Negotiation) will be used by the Government. This acquisition is being conducted under FAR Part 13, Simplified Acquisition
Procedures.	
 	

 	
 	

 

QuickLinks

ORDER FOR SUPPLIES OR SERVICES

STATEMENT OF WORK (SOW)

CLAUSES AND PROVISIONS

REPRESENTATIONS AND CERTIFICATIONS OF OFFERORS

INSTRUCTIONS FOR SUBMITTING QUOTATIONS

EVALUATION CRITERIA FOR AWARD

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

usTLD Undelegated Name Policy (Interim)

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT USTLD RESERVED NAME REGISTRATION PROCESS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT VALIDATED DOMAIN REGISTRATION PROCESS

AMENDMENT OF SOLICITATION OF CONTRACT

APPENDIX 1 VALIDATED DOMAIN REGISTRATION PROCESS

APPENDIX 2 USTLD FEDERAL RESERVE NAME ALLOCATION PROCESS

APPENDIX 3 PRICING

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

usTLD Federal, State and Local Name Request Registration Process

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

SF 30 Continuation of Block Narrative

Schedule

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Schedule

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

SF 30 Continuation of Block Narrative

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

usTLD ADMINISTRATOR CODE OF CONDUCT

usTLD Dispute-Resolution Policies

usTLD Dispute Resolution Policy

Rules for Uniform Domain Name Dispute Resolution Policy (the "Rules")

HIGHLIGHTS

Whois Information Under the usTLD

usTLD ADMINISTRATOR-DELEGATED MANAGER AGREEMENT

Exhibit A Delegated Manager Tool Kit

Exhibit B Engineering and Customer Service Support

Exhibit C usTLD Administrator's Operational Standards, Policies, Procedures, and Practices

Exhibit D Registration Fees

usTLD ADMINISTRATOR-REGISTRAR AGREEMENT

Exhibit A REGISTRAR TOOL KIT

Exhibit B ENGINEERING AND CUSTOMER SERVICE SUPPORT

Exhibit C ACCREDITATION AGREEMENT

Registrar Accreditation Agreement

EXHIBIT D POLICY ON TRANSFER OF SPONSORSHIP OF REGISTRATIONS BETWEEN NON-SPONSORING REGISTRARS

Exhibit E USTLD ADMINISTRATOR'S OPERATIONAL STANDARDS, POLICIES, PROCEDURES, AND PRACTICES

Exhibit F REGISTRATION FEES

Exhibit G PERFORMANCE SPECIFICATIONS

Exhibit H SERVICE LEVEL AGREEMENT

CREDIT LOOKUP MATRIX

Table C1a

Table C1b

Table C2

Table C3

Table C4a

Table C4b

REPRESENTATIONS AND CERTIFICATIONS OF OFFERORSQuickLinks
 -- Click here to rapidly navigate through this document

Exhibit 10.6  

 
  Registry Agreement  
  

This
REGISTRY AGREEMENT ("Agreement") is by and between the Internet Corporation for Assigned Names and Numbers, a not-for-profit corporation, and NeuLevel, Inc., a
Delaware, USA Corporation. 

1. DEFINITIONS. For purposes of this Agreement, the following definitions shall apply: 

1.1.
The "Authoritative Root-Server System" means the constellation of DNS root-nameservers specified, from time to time, in the file
<ftp://ftp.internic.net/domain/named.root>. 

1.2.
The "Base Period," in the case of a TLD delegated within the Authoritative Root-Server System on the Effective Date, means a period beginning on the
Commencement-of-Service Date and extending until the Expiration Date. In the case of a TLD not delegated within the Authoritative Root-Server System, the "Base
Period" means a period beginning at the conclusion of the Ramp-Up Period and extending until the Expiration Date. 

1.3.
The "Commencement-of-Service Date" means the Effective Date, except that, in the case of a TLD not delegated within the Authoritative Root-Server System on the
Effective Date, the Commencement-of-Service Date shall be the date on which the Registry TLD is first delegated within the Authoritative Root-Server System to
nameservers designated by Registry Operator. 

1.4.
The "DNS" refers to the Internet domain-name system. 

1.5.
The "Effective Date" is the date on which this Agreement is first signed on behalf of both parties. 

1.6.
The "Expiration Date" is the date specified in Subsection 5.1.1, as it may be extended according to Subsection 5.1.2. 

1.7.
"ICANN" refers to the Internet Corporation for Assigned Names and Numbers, a party to this Agreement. 

1.8.
An "ICANN-Accredited Registrar" is an entity or person accredited by ICANN to act as a registrar for domain names within the domain of the Registry TLD. 

1.9.
"Personal Data" refers to data about any identified or identifiable natural person. 

1.10.
The "Ramp-Up Period," in the case of a TLD not delegated within the Authoritative Root-Server System on the Effective Date, is the period beginning on the
Commencement-of-Service Date and extending for one year. 

1.11.
"Registered Name" refers to a domain name within the domain of the Registry TLD, whether consisting of two or more (e.g., john.smith.name) levels, about which Registry Operator (or an affiliate
engaged in providing Registry Services) maintains data in a Registry Database, arranges for such maintenance, or derives revenue from such maintenance. A name in a Registry Database may be a
Registered Name even though it does not appear in a zone file (e.g., a registered but inactive name). 

1.12.
"Registry Data" means all Registry Database data maintained in electronic form, and shall include TLD Zone-File Data, all data used to provide Registry Services submitted by
registrars in electronic form, and all other data used to provide Registry Services concerning particular domain name registrations or nameservers maintained in electronic form in the Registry
Database. 

1.13.
"Registry Database" means a database comprised of data about one or more DNS domain names within the domain of the Registry TLD that is used to generate either DNS resource records that are
published authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names. 

1.14.
"Registry Operator" refers to NeuLevel, Inc., a party to this Agreement, or any assignee of it under Subsection 5.11. 

1.15.
"Registry-Registrar Agreement" means an agreement between Registry Operator and an ICANN-Accredited Registrar with the provisions specified by Subsection 3.4. 

1.16.
"Registry Services" means services provided as an integral part of the operation of the Registry TLD, including all subdomains in which Registered Names are registered. In determining whether a
service is integral to the operation of the Registry TLD, consideration will be given to the extent to which the Registry Operator has been materially advantaged in providing the service by its
designation as such under this Agreement. The development of technology, expertise, systems, efficient operations, reputation (including identification as Registry Operator), financial strength, or
relationships with registrars and third parties shall not be deemed an advantage arising from the designation. Registry Services include: receipt of data concerning registration of domain names and
nameservers from registrars, provision to registrars of status information relating to the Registry TLD, dissemination of TLD zone files, operation of the Registry TLD zone servers, dissemination of
contact and other information concerning domain-name and nameserver registrations in the Registry TLD, and such other services required by ICANN in the manner provided in Subsections 4.3
through 4.6. Registry Services shall not include the provision of nameservice for a domain used by a single entity under a Registered Name registered through an ICANN-Accredited Registrar. 

1.17.
"Registry TLD" refers to the.biz TLD. 

1.18.
"Service Term" means that portion of the Term of this Agreement commencing on the Commencement-of-Service Date. 

1.19.
"Term of this Agreement" begins on the Effective Date and continues until the earlier of (a) the Expiration Date, or (b) termination of this Agreement. 

1.20.
"TLD" refers to a top-level domain in the DNS. 

1.21.
"TLD Zone-File Data" means all data contained in a DNS zone file for the Registry TLD, or for any subdomain for which Registry Services are provided and that contains Registered
Names, as provided to nameservers on the Internet. 

2.     ICANN OBLIGATIONS.  

2.1.  General Obligations of ICANN. With respect to all matters that affect the rights, obligations, or role of Registry Operator, ICANN shall during the
Term of this Agreement: 

2.1.1.
exercise its responsibilities in an open and transparent manner; 

2.1.2.
not unreasonably restrain competition and, to the extent feasible, promote and encourage robust competition; 

2.1.3.
not apply standards, policies, procedures or practices arbitrarily, unjustifiably, or inequitably and not single out Registry Operator for disparate treatment unless justified by substantial
and reasonable cause; and 

2.1.4.
ensure, through its reconsideration and independent review policies, adequate appeal procedures for Registry Operator, to the extent it is adversely affected by ICANN standards, policies,
procedures or practices. 

2.2.
Designation of Registry Operator. ICANN hereby designates Registry Operator as the sole operator for the Registry TLD during the Term of this
Agreement. 

2.3.
Recognition in Authoritative Root-Server System. During the Term of this Agreement, Registry Operator may, by notifying ICANN, request
(a) delegation of the Registry TLD to specified DNS nameservers and (b) changes in that delegation. Any such request must be made in a format, and 

otherwise
meet technical requirements, specified from time to time by ICANN. The initial format and technical requirements are set forth in Appendix A. Changes to the format and technical
requirements may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner provided in Subsections 4.3 through
4.6. ICANN will use commercially reasonable efforts to have such requests implemented in the Authoritative Root-Server System within five business days of the submission. 

2.4.  Recognition in the Root-Zone Contact Database. To the extent ICANN publishes contact data regarding TLDs, during the Term of this
Agreement it will show the Registry TLD's operator as Registry Operator and the Registry TLD's administrative and technical contacts as requested from time to time by Registry Operator. Any such
request must be made in a format, include the elements of contact data, and otherwise meet technical requirements, specified from time to time by ICANN. The initial requirements for these requests are
set forth in Appendix B. Changes to the requirements for requests may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without
reason) or in the manner provided in Subsections 4.3 through 4.6. 

2.5.  Other Obligations of ICANN. During the Term of this Agreement, ICANN shall use commercially reasonable efforts to: 

2.5.1.
maintain, or cause to be maintained, a stable, secure, authoritative and publicly available database of relevant information regarding the delegation of the Registry TLD; 

2.5.2.
generate, or cause to be generated, authoritative and accurate root zone information from such database and operate, or cause to be operated, the Authoritative Root-Server System in
a stable and secure manner; 

2.5.3.
maintain, or cause to be maintained, authoritative records and an audit trail regarding delegations of the Registry TLD and records related to these delegations; and 

2.5.4.
inform Registry Operator in a timely manner of any changes to ICANN's contact information. 

2.6.
Use of ICANN Name, Logo, and Website. ICANN hereby grants to Registry Operator a non-exclusive, worldwide, royalty-free
license during the Term of this Agreement (a) to state that it is designated by ICANN as the registry operator for the Registry TLD, (b) to use a logo specified by ICANN to signify that
Registry Operator is an ICANN-designated registry operator, and (c) to link to pages and documents within the ICANN web site. No other use of ICANN's name or logo is licensed hereby. This
license may not be assigned or sublicensed by Registry Operator. 

3.     REGISTRY OPERATOR OBLIGATIONS.  

3.1.
Obligation to Provide Registry Services. During the Service Term, Registry Operator shall operate, or cause to be operated, a registry of
Registered Names that meets the functional specifications described by Subsection 3.2 and the performance specifications described by Subsection 3.3. Throughout the Term of this Agreement, Registry
Operator shall be obligated to enter into a Registry-Registrar Agreement with any ICANN-Accredited Registrar seeking such an agreement on the terms specified by Subsection 3.4. Registry Operator shall
commence providing Registry Services in the Registry TLD according to the registry start-up plan specified in Subsection 3.7 and, on the conclusion of that plan and throughout the
remainder of the Term of this Agreement, shall continue providing Registry Services. Throughout the Service Term, Registry Operator shall provide Registry Services in compliance with any
Registry-Registrar Agreement as provided in Subsection 3.4 that is then in effect. 

3.2.  Functional Specifications for Registry Services. All Registry Services provided by Registry Operator shall be provided under this Agreement and
shall meet the functional specifications established by ICANN. The initial functional specifications are set forth in Appendix C. Non-material changes and additions to the
functional specifications may be made by Registry 

Operator
with prior written notice to ICANN and any affected ICANN-Accredited Registrars. All other changes and additions to the functional specifications may be made only with the mutual written
consent of ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.3.
Performance Specifications for Registry Services. All Registry Services provided by Registry Operator shall meet the performance specifications and
comply with the registrar service level agreement established by ICANN. The initial performance specifications are set forth in Appendix D and the initial service level agreement is set forth
in Appendix E. Changes to the performance specifications or service level agreement may be made only with the mutual written consent of ICANN and Registry Operator
(which neither party shall withhold without reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.4.  Registry-Registrar Agreements. During the Term of this Agreement, Registry Operator shall enter a Registry-Registrar Agreement with any
ICANN-Accredited Registrar desiring to enter such an agreement. All Registry Services provided by Registry Operator for the Registry TLD shall be provided strictly in accordance with that
Registry-Registrar Agreement: 

3.4.1.
Initially, the form of the Registry-Registrar Agreement shall be that attached as Appendix F. 

3.4.2.
The form of the Registry-Registrar Agreement may be revised (a) by Registry Operator with the written consent of ICANN, (b) by ICANN in the manner provided in Subsections 4.3
through 4.6, provided that any additional terms are within the topics set forth in Subsection 4.2, or, (c) with respect to the price charged registrars by Registry Operator for Registry
Services, according to Subsection 3.4.3. 

3.4.3.
Registry Operator may, at its option and with thirty days written notice to ICANN and to all ICANN-Accredited Registrars, revise the prices charged to registrars under the Registry-Registrar
Agreement, provided that (a) the same price shall be charged for services charged to all ICANN-Accredited Registrars (provided that volume adjustments may be made if the same opportunity to
qualify for those adjustments is available to all ICANN-Accredited Registrars) and (b) the prices shall not exceed those set forth in Appendix G, as adjusted according to Subsections
3.14.5 and 4.4. Registry Operator shall charge no fee to anyone for Registry Services if such fee is not listed on Appendix G. For Registry Services (a) listed on Appendix G
without a stated price or (b) introduced more than six months after the Commencement-of-Service Date, Registry Operator may propose to ICANN, no later than thirty days
before the commencement of that service, the inclusion in Appendix G of an offering price for the Registry Service. The offering price for the Registry Service shall be included in
Appendix G only upon the written consent of ICANN, which shall not be unreasonably withheld or delayed (ordinarily 30 days or less). 

3.5.
Fair Treatment of ICANN-Accredited Registrars. 

3.5.1.
Registry Operator shall provide all ICANN-Accredited Registrars that have Registry-Registrar Agreements in effect, and that are in compliance with the terms of such agreements, equivalent
access to Registry Operator's Registry Services, including to its shared registration system. 

3.5.2.
Registry Operator shall certify to ICANN every six months, using the objective criteria set forth in Appendix H, that Registry Operator is providing all such ICANN-Accredited Registrars
with equivalent access to its Registry Services, including to its shared registration system. 

3.5.3.
Registry Operator shall not act as a registrar with respect to the Registry TLD. This shall not preclude Registry Operator from registering names within the domain of the Registry TLD in
compliance with Subsection 3.6. This also shall not preclude an affiliate of Registry 

Operator
from acting as a registrar with respect to the Registry TLD, provided that Registry Operator complies with the provisions of Subsections 3.5.4 and 3.5.5. 

3.5.4.
Registry Operator shall comply with its Code of Conduct attached as Appendix I. Any changes to that Code of Conduct will require ICANN's written approval. 

3.5.5.
Registry Operator will ensure, in a form and through ways described in Appendix H, that the revenues and assets of Registry Operator are not utilized to advantage registrars that are
affiliated with Registry Operator to the detriment of other ICANN-Accredited Registrars. The distribution of funds by Registry Operator to its debt or equity participants in accordance with their debt
or equity participation shall not violate this Subsection 3.5.5. 

3.5.6.
With respect to its obligations under Subsections 3.5.1 through 3.5.5 and Appendices H and I, Registry Operator agrees to participate in and comply with the sanctions program described in
Appendix Y, provided that all other registry operators having registry agreements with ICANN for the operation of unsponsored top-level domains (i.e. top-level domains,
other than country-code and infrastructure domains, not having a sponsoring organization) are obligated to participate in and comply with a sanctions program with substantially the same
provisions as Appendix Y. Registry Operator agrees that the sanctions program described in Appendix Y shall be a non-exclusive and additional option for ICANN to promote
compliance with Subsections 3.5.1 through 3.5.5 and Appendices H and I, and that the availability of that option does not limit or affect in any way ICANN's ability to employ any other compliance
measures or remedies available under this Agreement. In the event that the gTLD Constituency of the Domain Name Supporting Organization proposes a substitute Appendix Y at any time prior to 1
May 2002, and ICANN determines (following an appropriate process of public notice and comment) that substitution by that Appendix Y would serve the interests of the Internet community,
the substitution shall be made. 

3.6.
Registrations Not Sponsored by Registrars Under Registry-Registrar Agreements. Registry Operator shall register domain names within the domain of
the Registry TLD, other than on a request submitted by a registrar pursuant to that registrar's Registry-Registrar Agreement, only as follows: 

3.6.1.
Registry Operator may register the domain names listed on Appendix X (Part A) for its own use in operating the registry and providing Registry Services under this Agreement,
provided the total number of domain names listed on Appendix X at any time does not exceed 5000. At the conclusion of its designation by ICANN as the operator for the Registry TLD, Registry
Operator shall transfer all such
domain-name registrations to the entity or person specified by ICANN. Appendix X may be revised upon the written notice by Registry Operator to ICANN and written consent by ICANN,
which shall not be unreasonably withheld. 

3.6.2.
Registry Operator may register the domain names listed on Appendix X (Part B) for its own use, provided that the total number of domain names listed on Appendix X at any
time does not exceed 5,000. Registry Operator may retain registration of those names at the conclusion of its designation by ICANN as the operator for the Registry TLD, provided registration fees are
paid and all other requirements for registration by third parties are met. Appendix X may be revised upon written notice by Registry Operator to ICANN and written consent by ICANN, which shall
not be unreasonably withheld. 

3.6.3.
As instructed from time to time by ICANN, Registry Operator shall maintain the registration of up to 5000 domain names within the domain of the Registry TLD for use by ICANN and other
organizations responsible for coordination of the Internet's infrastructure. 

3.6.4.
Subsection 3.6 shall not preclude Registry Operator from registering domain names within the domain of the Registry TLD through an ICANN-Accredited Registrar pursuant to that registrar's
Registry-Registrar Agreement. 

3.7.
Registration Start-Up Plan. Registry Operator shall commence provision of Registry Services for the Registry TLD, including the
provision of nameservice for the Registry TLD, according to the schedule and procedures set forth in the registration start-up plan in Appendix J to this Agreement. 

3.8.
Registration Restrictions Within Registry TLD. 

3.8.1.
Except to the extent that ICANN otherwise expressly authorizes in writing, Registry Operator shall reserve from registration the domain names specified by a schedule established by ICANN. The
initial schedule is attached as Appendix K. Changes to the schedule may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without
reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.8.2.
Registry Operator shall apply, monitor, and enforce the restrictions on registration in the Registry TLD established by ICANN in the manner established by ICANN. Appendix L sets forth
the
restrictions to be applied initially and Appendix M sets forth the manner by which these restrictions shall be applied, monitored, and enforced. Changes to the restrictions and the manner of
their application, monitoring, and enforcement may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner
provided in Subsections 4.3 through 4.6. 

3.9.
Bulk Access to TLD Zone Files. Registry Operator shall provide bulk access to the zone files for the Registry TLD as follows: 

3.9.1.
to third parties—on the terms set forth in the TLD zone file access agreement established by ICANN. The initial terms of the agreement are set forth as Appendix N to this
Agreement. Changes to the terms of the TLD zone file access agreement may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without
reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.9.2.
to ICANN—on a continuous basis in the manner which ICANN may from time to time specify. 

3.10.
Publication by Registry Operator of Registry Data. 

3.10.1.
At its expense, Registry Operator shall provide free public query-based access to up-to-date data concerning domain-name and nameserver registrations
maintained by Registry Operator in connection with the Registry TLD. The data elements reported, format of responses to queries, data update frequency, query types supported, and protocols through
which access is provided shall be as established by ICANN. The initial specification of the data elements reported, format of responses to queries, minimum data update frequency, query types
supported, and protocols through which access is provided are set forth in Appendix O. Registry Operator may request supplementation of the specification to include additional data elements
reported or query types supported, in which event ICANN shall act to supplement the specification in a reasonable manner within a reasonable time. Other changes to the specification may be made only
with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.10.2.
To ensure operational stability of the registry, Registry Operator may temporarily limit access under Subsection 3.10.1 in which case Registry Operator shall immediately notify ICANN of the
nature of and reason for the limitation. Registry Operator shall not continue the limitation longer than a period established by ICANN if ICANN objects in writing, which objection shall not be
unreasonably made. The period shall initially be five business days; changes to that period may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall
withhold without reason) or in the manner provided in Subsections 4.3 through 4.6. Such temporary limitations shall be applied in a non-arbitrary manner and shall apply fairly to all
ICANN-Accredited Registrars. 

3.10.3.
In providing query-based public access to registration data as required by this Subsection 3.10, Registry Operator shall not impose terms and conditions on the use of the data provided, except
as permitted by policy established by ICANN. Unless and until ICANN establishes a different policy, Registry Operator shall permit use of data it provides in response to queries for any lawful
purposes except to: (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to
entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator or any
ICANN-Accredited Registrar, except as reasonably necessary to register domain names or modify existing registrations. Changes to that policy may be made only with the mutual written consent of ICANN
and Registry Operator (which neither party shall withhold without reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.10.4.
To comply with applicable statutes and regulations and for other reasons, ICANN may from time to time establish policies in the manner described by Subsections 4.3 through 4.6 establishing
limits on the data concerning registrations that Registry Operator may make available to the public through a public-access service described in this Subsection 3.10 and on the manner in which
Registry Operator may make them available. In the event ICANN establishes any such policy, Registry Operator shall abide by it within the time allowed by Subsection 4.5. 

3.10.5.
At its expense, Registry Operator shall provide bulk access to up-to-date data concerning domain-name and nameserver registrations maintained by Registry
Operator in connection with the Registry TLD in the following two ways: 

3.10.5.1.
on a daily schedule, only for purposes of providing free public query-based access to up-to-date data concerning domain-name and nameserver registrations
in multiple TLDs, to a party designated from time to time in writing by ICANN. The content and format of this data, and the procedures for providing access, shall be as established by ICANN. The
initial content, format, and procedures are set forth in Appendix P. Changes to that content and format and those procedures may be made only with the mutual written consent of
ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.10.5.2.
on a continuous basis, to ICANN in the manner which ICANN may from time to time reasonably specify, only for purposes of verifying and ensuring the operational stability of Registry
Services, the DNS, and the Internet. The content and format of this data, and the procedures for providing access, shall be as established by ICANN. The initial content, format, and procedures are set
forth in Appendix Q. Changes to that content and format and those procedures may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold
without reason) or in the manner provided in Subsections 4.3 through 4.6. 

3.11.
Data Escrow. Registry Operator shall periodically deposit into escrow all Registry Data in an electronic format. The escrow shall be maintained,
at Registry Operator's expense, by a reputable escrow agent mutually approved by Registry Operator and ICANN, such approval also not to be unreasonably withheld by either party. The schedule, content,
format, and procedure for escrow deposits shall be as established by ICANN from time to time. The initial schedule, content, format, and procedure shall be as set forth in Appendix R. Changes
to the schedule, content, format, and procedure may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner
provided in Subsections 4.3 through 4.6. The escrow shall be held under an agreement, substantially in the form of Appendix S, among ICANN, Registry Operator, and the escrow agent. In the event
that, after a good-faith search by ICANN and Registry Operator, no mutually approved escrow agent agrees to the terms of Appendix S, ICANN and Registry Operator shall, in
conjunction with a mutually approved escrow agent, negotiate in good faith for a substitute escrow agreement. 

3.12.
Registry Operator's Handling of Personal Data. Registry Operator shall notify registrars sponsoring registrations in the registry for the Registry
TLD of the purposes for which Personal Data submitted to Registry Operator by registrars is collected, the intended recipients (or categories of recipients) of such Personal Data, and the mechanism
for access to and correction of such Personal Data. Registry Operator shall take reasonable steps to protect Personal Data 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. 

3.13.
Rights in Data. Except as permitted by the Registry-Registrar Agreement, Registry Operator shall not be entitled to claim any intellectual
property rights in data supplied by or through registrars. In the event that Registry Data is released from escrow under Subsection 3.11, any rights held by Registry Operator in the data shall
automatically be transferred on a non-exclusive, irrevocable, royalty-free, paid-up basis to ICANN or to a party designated in writing by ICANN. 

3.14.
Registry-Level Financial Support of ICANN. During the Term of this Agreement, Registry Operator shall pay to ICANN the following fees: 

3.14.1.
Fixed Registry-Level Fee. Registry Operator shall pay ICANN a quarterly Fixed Registry-Level Fee in an amount established by the ICANN Board of
Directors, in conformity with the ICANN bylaws and articles of incorporation, not to exceed one quarter of the annual Fixed Registry-Level Fee Cap described in Subsection 3.14.4. 

3.14.2.  Variable Registry-Level Fee. Registry Operator shall pay ICANN a quarterly Variable Registry-Level Fee in an amount calculated according to a
formula and method established from time to time by the ICANN Board of Directors, in conformity with the ICANN bylaws and articles of incorporation. The formula and method shall allocate the total
variable fee among all TLDs sponsored or operated under a sponsorship or registry agreement with ICANN (whether the fee is collected at the registry or registrar level) based on the relative size of
the registries for those TLDs. It shall be permissible for the formula and method so established to do any of the following: (a) to measure the size of a TLD's registry, at least once per year
where feasible, by the number of names under administration within the TLD by the registry's operator, (b) to deem the number of domain names under administration within the Registry TLD to be
the number of Registered Names, (c) to provide for a deduction in computing a sponsor's or operator's Variable Registry-Level Fee of some or all of that sponsor's or registry operator's Fixed
Registry-Level Fee, and (d) to provide that the number of domain names under administration for the.com,.net, and.org TLDs is the number of second-level domains within those TLDs. It shall also
be permissible for the formula and method to consider accreditation fees collected from registrars as a credit applied to the Variable Registry-Level Fee for the TLD to which the fees pertain. Groups
of registries for two or more TLDs may, with the agreement of their sponsors or operators and ICANN, agree to allocate the variable fee collected from them in a manner not based on the relative size
of 

the
registries within the group, provided that the combined variable fees collected for all TLDs within the group is based on the combined size of the registries in the group. 

3.14.3.
Payments Must Be Timely. Registry Operator shall pay the quarterly Fixed and Variable Registry-Level Fees within thirty days after the date of
ICANN's invoice for those fees. These payments shall be made in a timely manner throughout the Term of this Agreement and notwithstanding the pendency of any dispute between Registry Operator and
ICANN. Registry Operator shall pay interest on payments not timely made at the rate of 1% per month or, if less, the maximum rate permitted by California law. 

3.14.4.  Fee Caps. The Fixed Registry-Level Fee Cap shall be US$80,000 per year until and including 30 June 2002; shall automatically increase by
15% on July 1 of each year beginning in 2002; and may be increased by a greater amount in the manner provided by Subsection 4.3 The sum of the Fixed Registry-Level Fees and the Variable
Registry-Level Fees due to be paid in any year ending on any 30 June during or within one year after the Term of this Agreement by all TLD sponsors and registry operators having sponsorship or
registry agreements with ICANN shall not exceed the Total Registry-Level Fee Cap described in the following sentence. The Total Registry-Level Fee Cap shall be US$5,500,000 for the fiscal year ending
30 June 2002; shall increase by 15% each fiscal year thereafter; and may be increased by a greater amount in the manner provided by Subsection 4.3. 

3.14.5.  Adjustments to Price. The maximum pricing for initial and renewal registrations set forth in Appendix G shall be adjusted at the
beginning of each calendar quarter by adding, to the amount specified in that Appendix (after adjustment according to Subsection 4.4) as the applicable annual charge for initial or renewal
registration of a domain name, an amount calculated according to the following three sentences. For calendar quarters in which the variable fee is collected at the registrar level, the amount shall be
US$0.00. For the first two calendar quarters during the Term of this
Agreement in which the variable fee is collected at the registry level, the amount shall be four times the per-name variable accreditation fee charged to registrars for the quarter
beginning six months earlier. For subsequent calendar quarters, the amount shall be four times the quarterly Variable Registry-Level Fee reflected in the invoice to Registry Operator for such a fee
for the quarter beginning six months earlier divided by the number of Registered Names that the invoice shows was used to calculate that quarterly Variable Registry-Level Fee. 

3.15.
Reports Provided to ICANN. Registry Operator shall provide the following periodic written reports to ICANN regarding the following: 

3.15.1.
Monthly Reports on Registry Operations. Within twenty days after the end of each month during the Term of this Agreement, Registry Operator
shall provide ICANN a written report, giving information specified by ICANN, on operation of the registry during the month. The initial specification of information is set forth in Appendix T.
Changes to that specification may be made only with the mutual written consent of ICANN and Registry Operator (which neither party shall withhold without reason) or in the manner provided in
Subsections 4.3 through 4.6. 

3.15.2.
Data Related to Proof of Concept. Registry Operator shall, for the purpose of providing data concerning concepts to be proven by establishment
of the Registry TLD, provide reports concerning the Registry TLD's operation on a schedule and with content specified in Appendix U. 

4. PROCEDURES FOR ESTABLISHMENT OR REVISION OF SPECIFICATIONS AND POLICIES.

4.1.
Registry Operator's Ongoing Obligation to Comply With New or Revised Specifications and Policies. During the Term of this Agreement, Registry
Operator shall comply, in its provision of Registry Services, on the schedule provided in Subsection 4.5, with 

4.1.1.
new or revised specifications (including forms of agreement to which Registry Operator is a party) and policies established by ICANN as Consensus Policies in the manner described in Subsection
4.3, 

4.1.2.
in cases where: 

4.1.2.1.
this Agreement expressly provides for compliance with revised specifications or policies established in the manner set forth in one or more subsections of this Section 4; or 

4.1.2.2.
the specification or policy concerns one or more topics described in Subsection 4.2. 

4.2.  Topics for New and Revised Specifications and Policies. New and revised specifications and policies may be established on the following topics: 

4.2.1.
issues for which uniform or coordinated resolution is reasonably necessary to facilitate interoperability, technical reliability, and/or operational stability of Registry Services, the DNS, or
the Internet; 

4.2.2.
functional and performance specifications for the provision of Registry Services; 

4.2.3.
safety and integrity of the Registry Database; 

4.2.4.
procedures to avoid disruptions of registration due to suspension or termination of operations by a registry operator or a registrar, including procedures for allocation of responsibility for
serving Registered Names affected by such a suspension or termination; 

4.2.5.
resolution of disputes regarding whether particular parties may register or maintain registration of particular domain names; 

4.2.6.
principles for allocation of Registered Names (e.g., first-come/first-served, timely renewal, holding period after expiration); 

4.2.7.
prohibitions on warehousing of or speculation in domain names by registries or registrars; 

4.2.8.
maintenance of and access to accurate and up-to-date contact information for domain-name registrants; 

4.2.9.
reservation of Registered Names that may not be registered initially or that may not be renewed due to reasons reasonably related to (a) avoidance of confusion among or misleading of
users, (b) intellectual property, or (c) the technical management of the DNS or the Internet (e.g., establishment of reservations of names from registration); and 

4.2.10.
registry policies reasonably necessary to implement Consensus Policies relating to registrars. 

4.3.
Manner of Establishment of New and Revised Specifications and Policies. 

4.3.1.
"Consensus Policies" are those specifications or policies established based on a consensus among Internet stakeholders represented in the ICANN process, as demonstrated by (a) action of
the ICANN Board of Directors establishing the specification or policy, (b) a recommendation, adopted by at least a two-thirds vote of the council of the ICANN Supporting
Organization to which the matter is delegated, that the specification or policy should be established, and (c) a written report and supporting materials (which must include all substantive
submissions to the Supporting Organization relating to the proposal) that (i) documents the extent of agreement and disagreement among impacted groups, (ii) documents the outreach
process used to seek to achieve adequate representation of the views of groups that are likely to be impacted, and (iii) documents the nature and intensity of reasoned support and opposition to
the proposed policy. 

4.3.2.
In the event that Registry Operator disputes the presence of such a consensus, it shall seek review of that issue from an Independent Review Panel established under ICANN's bylaws. Such review
must be sought within fifteen working days of the publication of the Board's action establishing the policy. The decision of the panel shall be based on the report and supporting materials required by
Subsection 4.3.1. In the event that Registry Operator seeks review and the Independent Review Panel sustains the Board's determination that the policy is based on a consensus among Internet
stakeholders represented in the ICANN process, then Registry Operator must implement such policy unless it promptly seeks and obtains a stay or injunctive relief under Subsection 5.9. 

4.3.3.
If, following a decision by the Independent Review Panel convened under Subsection 4.3.2, Registry Operator still disputes the presence of such a consensus, it may seek further review of that
issue within fifteen working days of publication of the decision in accordance with the dispute resolution procedures set forth in Subsection 5.9; provided, however, that Registry Operator must
continue to implement the policy unless it has obtained a stay or injunctive relief under Subsection 5.9 or a final decision is rendered in accordance with the provisions of Subsection 5.9 that
relieves Registry Operator of such obligation. The decision in any such further review shall be based on the report and supporting materials required by Subsection 4.3.1. 

4.3.4.
A specification or policy established by the ICANN Board of Directors on a temporary basis, without a prior recommendation by the council of an ICANN Supporting Organization, shall also be
considered to be a Consensus Policy if adopted by the ICANN Board of Directors by a vote of at least two-thirds of its members, so long as the Board reasonably determines that immediate
temporary establishment of a specification or policy on the subject is necessary to maintain the operational stability of Registry Services, the DNS, or the Internet, and that the proposed
specification or policy is as narrowly tailored as feasible to achieve those objectives. In establishing any specification or policy under this provision, the ICANN Board of Directors shall state the
period of time for which the specification or policy is temporarily adopted and shall immediately refer the matter to the appropriate Supporting Organization for its evaluation and review with a
detailed explanation of its reasons for establishing the temporary specification or policy and why the Board believes the policy should receive the consensus support of Internet stakeholders. If the
period of time for which the specification or policy is adopted exceeds ninety days, the Board shall reaffirm its temporary establishment every ninety days for a total period not to exceed one year,
in order to maintain such specification or policy in effect until such time as it meets the standard set forth in Subsection 4.3.1. If the standard set forth in Subsection 4.3.1 is not met within the
temporary period set by the Board, or the council of the Supporting Organization to which it has been referred votes to reject the temporary specification or policy, it will no longer be a "Consensus
Policy." 

4.3.5.
For all purposes under this Agreement, the policies identified in Appendix V shall be treated in the same manner and have the same effect as "Consensus Policies." 

4.3.6.
In the event that, at the time the ICANN Board of Directors establishes a specification or policy under Subsection 4.3.1 during the Term of this Agreement, ICANN does not have in place an
Independent Review Panel established under ICANN's bylaws, the fifteen-working-day period allowed under Subsection 4.3.2 to seek review shall be extended until fifteen working days after
ICANN does have such an Independent Review Panel in place and Registry Operator shall not be obligated to comply ICANN with the specification or policy in the interim. 

4.4.  Pricing Adjustments Arising from New or Revised Specifications or Policies. The maximum prices stated in Appendix G shall be increased
through an amendment to this Agreement as approved by ICANN and Registry Operator, such approval not to be unreasonably withheld, to reflect demonstrated increases in the net costs of providing
Registry Services arising from (A) new or 

revised
ICANN specifications or policies adopted after the Effective Date, or (B) legislation specifically applicable to the provision of Registry Services adopted after the Effective Date, to
ensure that Registry Operator recovers such costs and a reasonable profit thereon; provided that such increases exceed any reductions in costs arising from (A) or (B) above. 

4.5.
Time Allowed for Compliance. Registry Operator shall be afforded a reasonable period of time (not to exceed four months unless the nature of the
specification or policy established under Subsection 4.3
reasonably requires, as agreed to by ICANN and Registry Operator, a longer period) after receiving notice of the establishment of a specification or policy under Subsection 4.3 in which to comply with
that specification or policy, taking into account any urgency involved. 

4.6.
Indemnification of Registry Operator. ICANN shall indemnify, defend, and hold harmless Registry Operator (including its directors, officers,
employees, and agents) from and against any and all claims, damages, liabilities, costs, and expenses, including reasonable legal fees and expenses, arising solely from Registry Operator's compliance
as required by this Agreement with an ICANN specification or policy (including, without limitation, a Consensus Policy) established after the Effective Date; except that Registry Operator shall not be
indemnified or held harmless hereunder to the extent that the claims, damages or liabilities arise from the particular manner in which Registry Operator has chosen to comply with the specification or
policy, where it was possible for Registry Operator to comply in a manner by which the claims, damages, or liabilities would not arise. As an alternative to providing the indemnity stated in this
Subsection 4.6, ICANN may, at the time it establishes a specification or policy after the Effective Date giving rise to an indemnity obligation under this Subsection 4.6, state ICANN's election that
the Registry Operator shall bear the cost of insuring the claims, damages, liabilities, costs, and expenses that would otherwise be indemnified by ICANN under this Subsection 4.6, in which case the
reasonable cost to Registry Operator of such insurance shall be treated under Subsection 4.4 as a cost of providing Registry Services arising from the newly established ICANN specification or policy. 

5. MISCELLANEOUS PROVISIONS.  

5.1.  Expiration of this Agreement. 

5.1.1.
The initial Expiration Date shall be five years after the Commencement-of-Service Date, except that, in the case of a TLD not delegated within the Authoritative
Root-Server System on the Effective Date, the initial Expiration Date shall be five years after the end of the Ramp-Up Period. The Expiration Date may be extended as provided
in Section 5.1.2. 

5.1.2.
The initial Expiration Date shall be extended by one year in the event that, on the date one year before the initial Expiration Date, Registry Operator has under management within the Registry
TLD at least 19,827,980 Registered Names. 

5.1.3.
Registry Operator acknowledges and agrees that upon the earlier of (i) the Expiration Date or (ii) termination of this Agreement by ICANN pursuant to Subsection 5.4, it will cease
to be the operator of the Registry TLD unless ICANN and Registry Operator enter a new registry agreement continuing Registry Operator's status as operator of the Registry TLD. 

5.1.4.
Upon conclusion of its status as operator of the Registry TLD, Registry Operator shall make all commercially reasonable efforts to cooperate with ICANN, and with any party designated by ICANN
as successor operator, to facilitate prompt and smooth transition of the operation of the Registry TLD. 

5.1.5.
Registry Operator acknowledges and agrees that, except as expressly provided by this Agreement, it shall not acquire any right in the Registry TLD by virtue of its operation of the Registry TLD
or its provision of Registry Services hereunder. 

5.2.
Procedure for Subsequent Agreement. 

5.2.1.
Registry Operator may, no later than eighteen months prior to the initial Expiration Date, submit a written proposal to ICANN for the extension of this Agreement for an 

additional
term (the "Renewal Proposal"). The Renewal Proposal shall contain a detailed report of the Registry Operator's operation of the Registry TLD and include a description of any additional
Registry Services, proposed improvements to Registry Services, or changes in price or other terms of service. ICANN shall provide an initial response to the Renewal Proposal within thirty days of
receiving it and, during a period of at least six months after receiving the Renewal Proposal, ICANN shall consider the Renewal Proposal and meet with Registry Operator to discuss the Renewal
Proposal, but the decision whether to accept the Renewal Proposal shall be in ICANN's sole discretion. 

5.2.2.
Only after the six-month period described in Subsection 5.2.1 may ICANN call for competing proposals from potential successor registry operators for the Registry TLD. Registry
Operator shall be eligible, to the same extent as similarly situated entities, to submit a proposal to such a call. To the extent that the Renewal Proposal demonstrates (i) substantial service
in the interests of the Internet community, (ii) enhancement of competition for registration services, and (iii) enhancement of the utility of the DNS, such demonstration shall be among
the specific factors considered in ICANN's evaluation of any competing proposals, but the choice from among competing proposals shall be in ICANN's sole discretion. 

5.2.3.
In the event a party other than the Registry Operator is selected as the successor registry operator for the Registry TLD upon the expiration of this Agreement, ICANN shall require the
successor registry operator to pay to Registry Operator a Registry Operator Transfer Fee equal to the difference of: 

5.2.3.1
the present value, at the Expiration Date (as extended, if applicable), computed using a discount rate equal to the London Inter-Bank Offer Rate ("LIBOR") (based on the term of
renewal of the successor registry operator) plus three percent per annum, of the revenue stream that
would be achieved by the successor registry operator from renewal fees during the term (not taking into account any extensions) of the successor registry operator's registry agreement for Registered
Names on the Expiration Date that have not been continuously under registration during the entire Base Period, assuming that the domain-name registrations are renewed at the time of their
expiration for a renewal term and at annual renewal fees and rates described in the next four sentences. The assumed renewal term, fees, and rates shall be based on actual experience within the
Registry TLD during a period (the "Benchmark Period") consisting of the eighteen months immediately prior to the Expiration Date. The assumed renewal term shall be the average total term by which
registrations of Registered Names scheduled for expiration during the Benchmark Period are extended by renewal during the Benchmark Period. The assumed renewal rate shall be the percentage of names
scheduled for expiration during the Benchmark Period that are extended by renewal at least once during the Benchmark Period. The assumed annual renewal fee shall be the lesser of (i) the
maximum annual renewal fee that the successor registry operator may charge under its registration agreement and (ii) the average of the annual renewal fees charged by Registry Operator during
the Benchmark Period; less 

5.2.3.2
the present value, at the Expiration Date, computed using a discount rate equal to the LIBOR (based on the term of renewal of the successor registry operator) plus three percent per annum, of
the expense stream that would result during the term (not taking into account any extensions) of the successor registry operator's registry agreement from continued registration of the registrations
at the Expiration Date, with the same assumptions regarding renewal rates and terms set forth in Subsection 5.2.3.1 above. For purposes of this calculation, the annual expense of continued
registration shall be assumed to be 45% of the assumed annual renewal fee stated in Subsection 5.2.3.1 above. 

5.2.3.3
The calculation of present value shall be on a monthly basis with all renewals and expenses occurring in a given month assumed to occur at the end of the month. The Registry Operator Transfer
Fee shall be paid, with interest per annum equal to the 

LIBOR
plus three percent, from the Expiration Date, within nine months after the Expiration Date. 

5.3.
Condition to Performance. In the event that ICANN is unable, through use of commercially reasonable efforts, to have the Registry TLD delegated
within the Authoritative Root-Server System to nameservers designated by Registry Operator within two years after the Effective Date, then this Agreement shall be automatically terminated
without liability of either party to the other party and neither party shall have any further obligation hereunder. Thirty days in advance of such an automatic termination, either party may propose an
extension of the time in which delegation must occur, and in that event the other party shall consult in good faith (but without obligation to agree) concerning the proposal. No extension of the time
in which delegation must occur shall be effective unless embodied in a written amendment signed by authorized agents of both parties to this Agreement. 

5.4.  Termination by ICANN. This Agreement may be terminated before its expiration by ICANN in any of the following circumstances: 

5.4.1.
There was a material misrepresentation, material inaccuracy, or materially misleading statement, made with knowledge of its falsity, inaccuracy, or misleading nature or without reasonable cause
to believe it was true, accurate, and not misleading, of then-existing fact or of Registry Operator's intention in its application for the Registry TLD or any written material provided to
or disclosed to ICANN by the Registry Operator in connection with the application. The foregoing shall not apply to projections or forward-looking statements (other than statements, not made in good
faith, about Registry Operator's intentions) in the application or materials. 

5.4.2.
Registry Operator: 

5.4.2.1.
is convicted by a court of competent jurisdiction of a felony or other serious offense related to financial activities, or is the subject of a determination by a court of competent
jurisdiction that ICANN reasonably deems as the substantive equivalent of those offenses; or 

5.4.2.2.
is disciplined by the government of its domicile for conduct involving dishonesty or misuse of funds of others. 

5.4.3.
Any officer or director of Registry Operator is convicted of a felony or of a misdemeanor related to financial activities, or is judged by a court to have committed fraud or breach of fiduciary
duty, or is the subject of a judicial determination that ICANN deems as the substantive equivalent of any of these, and such officer or director is not immediately removed in such circumstances. 

5.4.4.
Registry Operator fails to cure any material breach of this Agreement (other than a failure to comply with a Consensus Policy adopted by ICANN during the Term of this Agreement as to which
Registry Operator has obtained a stay under Subsection 5.9) within fifteen business days (or such longer reasonable period as may be necessary using best efforts to cure such breach) after ICANN gives
Registry Operator written notice of the breach. 

5.4.5.
Registry Operator's action or failure to act has been determined by arbitration under Subsection 5.9 to be in violation of this Agreement and Registry Operator continues to act or fail to act
in the manner that was determined to violate this Agreement for a period stated in the arbitration decision, or if no period is stated, fifteen business days. 

5.4.6.
Registry Operator acts or continues acting in a manner that ICANN has reasonably determined endangers the operational stability of Registry Services, the DNS, or the Internet after receiving
three days notice of that determination. 

5.4.7.
Registry Operator fails to pay to ICANN the final amount of sanctions determined to be appropriate under the sanctions program described in Appendix Y within thirty days after the amount
of sanctions is deemed final. 

5.4.8.
Registry Operator becomes bankrupt or insolvent. 

This
Agreement may be terminated in the circumstances described in Subsections 5.4.1 through 5.4.7 above only upon thirty calendar days written notice to Registry Operator (in the case of the
circumstances described in Subsections 5.4.4, 5.4.5, and 5.4.6 occurring after Registry Operator's failure to cure), with Registry Operator being given an opportunity during that time to initiate
arbitration under Subsection 5.9 to determine the appropriateness of termination under this Agreement. In the event Registry Operator initiates arbitration concerning the appropriateness of
termination by ICANN, Registry Operator may at the same time request that the arbitration panel stay the termination until the arbitration decision is rendered, and that request shall have the effect
of staying the termination until the decision or until the arbitration panel has granted an ICANN request for lifting of the stay. If Registry Operator acts in a manner that ICANN reasonably
determines endangers the operational stability of Registry Services, the DNS, or the Internet and upon notice does not immediately cure, ICANN may suspend this Agreement for five calendar days pending
ICANN's application for more extended injunctive relief under Subsection 5.9. This Agreement may be terminated immediately upon notice to Registry Operator in the circumstance described in Subsection
5.4.8. 

5.5.  Representations and Warranties of Registry Operator. Registry Operator represents and warrants to ICANN that: 

5.5.1.
it is a corporation duly organized, validly existing, and in good standing under the laws of Delaware, USA; 

5.5.2.
it has all requisite organizational power and authority to execute, deliver and perform its obligations under this Agreement; 

5.5.3.
the execution, performance and delivery of this Agreement has been duly authorized by Registry Operator; and 

5.5.4.
subject to Subsection 5.3, no further approval, authorization or consent of any governmental or regulatory authority is required to be obtained or made by Registry Operator in order for it to
enter into and perform its obligations under this Agreement. 

5.6.
Additional Covenants of Registry Operator. Throughout the Term of the Agreement, Registry Operator shall comply, in all material respects, with the
covenants contained in Appendix W. 

5.7.
Indemnification of ICANN. Registry Operator shall indemnify, defend, and hold harmless ICANN (including its directors, officers, employees, and
agents) from and against any and all claims, damages, liabilities, costs, and expenses, including reasonable legal fees and expenses, arising out of or relating to: (a) the selection of
Registry Operator to operate the Registry TLD; (b) the entry of this Agreement; (c) establishment or operation of the Registry TLD; (d) Registry Services; (e) collection or
handling of Personal Data by Registry Operator; (f) any dispute concerning registration of a domain name within the domain of the Registry TLD; and (g) duties and obligations of Registry
Operator in operating the Registry TLD; provided that, with respect to items (b) through (g) only, Registry Operator shall not be obligated to indemnify, defend, or hold harmless ICANN
to the extent of ICANN's indemnification of Registry Operator under Subsection 4.6 and provided further that, with respect to item (g) only, Registry Operator shall not be obligated to
indemnify, defend, or hold harmless ICANN to the extent the claim, damage, liability, cost, or expense arose due to a breach by ICANN of any obligation contained in this Agreement. For avoidance of
doubt, nothing in this Subsection 5.7 shall be deemed to require Registry Operator to reimburse or otherwise indemnify ICANN for the costs associated with the negotiation or execution of this
Agreement, or with the monitoring or management of the parties' respective obligations under this Agreement. 

5.8.
Indemnification Procedures. If any third-party claim is commenced that is indemnified under Subsections 4.6 or 5.7, notice thereof shall be given
to the indemnifying party as promptly as practicable. If, after such notice, the indemnifying party acknowledges its obligation to indemnify with respect to such claim, then the indemnifying party
shall be entitled, if it so elects, in a notice promptly delivered to the indemnified party, to immediately take control of the defense and investigation of such claim and to employ and engage
attorneys reasonably acceptable to the indemnified party to handle and defend the same, at the indemnifying party's sole cost and expense, provided that in all events ICANN shall be entitled to
control at its sole cost and expense the litigation of issues concerning the validity or interpretation of ICANN policies or conduct. The indemnified party shall cooperate, at the cost of the
indemnifying party, in all reasonable respects with the indemnifying party and its attorneys in the investigation, trial, and defense of such claim and any appeal arising therefrom; provided, however,
that the indemnified party may, at its own cost and expense, participate, through its attorneys or otherwise, in such investigation, trial and defense of such claim and any appeal arising therefrom.
No settlement of a claim that involves a remedy affecting the indemnifying party other than the
payment of money in an amount that is indemnified shall be entered into without the consent of the indemnified party. If the indemnifying party does not assume full control over the defense of a claim
subject to such defense in accordance with this Subsection, the indemnifying party may participate in such defense, at its sole cost and expense, and the indemnified party shall have the right to
defend the claim in such manner as it may deem appropriate, at the cost and expense of the indemnifying party. 

5.9.  Resolution of Disputes Under This Agreement. Disputes arising under or in connection with this Agreement, including requests for specific
performance, shall be resolved through binding arbitration conducted as provided in this Subsection 5.9 pursuant to the rules of the International Court of Arbitration of the International Chamber of
Commerce ("ICC"). The arbitration shall be conducted in the English language and shall occur in Los Angeles County, California, USA. There shall be three arbitrators: each party shall choose one
arbitrator and, if the two arbitrators are not able to agree on a third arbitrator, the third shall be chosen by the ICC. The parties shall bear the costs of the arbitration in equal shares, subject
to the right of the arbitrators to reallocate the costs in their award as provided in the ICC rules. The parties shall bear their own attorneys' fees in connection with the arbitration, and the
arbitrators may not reallocate the attorneys' fees in conjunction with their award. The arbitrators shall render their decision within ninety days of the initiation of arbitration. In all litigation
involving ICANN concerning this Agreement (as provided in the remainder of this Subsection), jurisdiction and exclusive venue for such litigation shall be in a court located in Los Angeles,
California, USA; however, the parties shall also have the right to enforce a judgment of such a court in any court of competent jurisdiction. For the purpose of aiding the arbitration and/or
preserving the rights of the parties during the pendency of an arbitration, the parties shall have the right to seek a temporary stay or injunctive relief from the arbitration panel or a court located
in Los Angeles, California, USA, which shall not be a waiver of this arbitration agreement. 

5.10.
Limitation of Liability. ICANN's aggregate monetary liability for violations of this Agreement shall not exceed the amount of Fixed or Variable
Registry-Level Fees paid by Registry Operator to ICANN within the preceding twelve-month period under Subsection 3.14. Registry Operator's aggregate monetary liability to ICANN for violations of this
Agreement shall be limited to fees and monetary sanctions due and owing to ICANN under this Agreement. In no event shall either party be liable for special, indirect, incidental, punitive, exemplary,
or consequential damages arising out of or in connection with this Agreement or the performance or nonperformance of obligations undertaken in this Agreement. EXCEPT AS OTHERWISE PROVIDED IN THIS
AGREEMENT, REGISTRY OPERATOR DOES NOT MAKE ANY WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE SERVICES RENDERED BY ITSELF, ITS SERVANTS, OR ITS AGENTS OR THE RESULTS OBTAINED FROM THEIR WORK,
INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. 

5.11.
Assignment. Any assignment of this Agreement shall be effective only upon written agreement by the assignee with the other party to assume the
assigning party's obligations under this Agreement. Moreover, neither party may assign this Agreement without the prior written approval of the other party. Notwithstanding the foregoing, a party may
assign this Agreement by giving written notice to the
other party in the following circumstances: (a) Registry Operator may assign this Agreement as part of the transfer of its registry business if such transfer and assignment are approved in
advance by ICANN pursuant to its procedures, and (b) ICANN may assign this Agreement (i) in conjunction with a reorganization or re-incorporation of ICANN, to another
non-profit corporation organized for the same or substantially the same purposes as ICANN or (ii) as required by Section 5 of Amendment 1 (dated 10 November 1999) to
the 25 November 1998 Memorandum of Understanding between ICANN and the United States Department of Commerce. 

5.12.  Subcontracting. Registry Operator shall not subcontract portions of the technical operations of the Registry TLD accounting for more than 80% of
the value of all Registry TLD operations without ICANN's written consent. When ICANN's consent to subcontracting is requested, ICANN shall respond within fifteen business days, and the consent shall
not be unreasonably withheld. In any subcontracting of the technical operations of the Registry TLD, the subcontract shall state that the subcontractor shall not acquire any right in the Registry TLD
by virtue of its performance under the subcontract. 

5.13.
Force Majeure. Neither party shall be liable to the other for any loss or damage resulting from any cause beyond its reasonable control (a "Force
Majeure Event") including, but not limited to, insurrection or civil disorder, war or military operations, national or local emergency, acts or omissions of government or other competent authority,
compliance with any statutory obligation or executive order, industrial disputes of any kind (whether or not involving either party's employees), fire, lightning, explosion, flood, subsidence, weather
of exceptional severity, and acts or omissions of persons for whom neither party is responsible. Upon occurrence of a Force Majeure Event and to the extent such occurrence interferes with either
party's performance of this Agreement, such party shall be excused from performance of its obligations (other than payment obligations) during the first six months of such interference, provided that
such party uses best efforts to avoid or remove such causes of nonperformance as soon as possible. 

5.14.  No Third-Party Beneficiaries. This Agreement shall not be construed to create any obligation by either ICANN or Registry Operator to any
non-party to this Agreement, including any registrar or Registered Name holder. 

5.15.
Notices, Designations, and Specifications. All notices (including determinations, designations, and specifications) to be given under this
Agreement shall be given in writing at the address of the appropriate party as set forth below, unless that party has given a notice of change of address in writing. Any notice required by this
Agreement shall be deemed to have been properly given when delivered in person, when sent by electronic facsimile, or when scheduled for delivery by an internationally recognized courier service.
Designations and specifications by ICANN under this Agreement shall be effective when written notice of them is deemed given to Registry. 

If
to ICANN, addressed to: 

Internet
Corporation for Assigned Names

and Numbers

]4676 Admiralty Way, Suite 330

Marina Del Rey, California 90292

Telephone: 1/310/823-9358

Facsimile: 1/310/823-8649

Attention: Chief Executive Officer 

If
to Registry Operator, addressed to: 

NeuLevel, Inc.

Loudoun Tech center

45980 Center Oak Plaza

Sterling, Virginia 20166

Telephone: 1/571/434-5450

Facsimile: 1/571/434-5786

Attention: VP of Policy and Industry Relations 

With
a copy addressed to: 

NeuLevel, Inc.

Loudoun Tech center

45980 Center Oak Plaza

Sterling, Virginia 20166

Telephone: 1/571/434-5450

Facsimile: 1/571/434-5786

Attention: General Counsel 

5.16.  Dates and Times. All dates and times relevant to this Agreement or its performance shall be computed based on the date and time observed in Los
Angeles, California, USA. 

5.17.
Language. All notices, designations, determinations, and specifications made under this Agreement shall be in the English language. 

5.18.
Amendments and Waivers. No amendment, supplement, or modification of this Agreement or any provision hereof shall be binding unless executed in
writing by both parties. No waiver of any provision of this Agreement shall be binding unless evidenced by a writing signed by the party waiving compliance with such provision. No waiver of any of the
provisions of this Agreement shall be deemed or shall constitute a waiver of any other provision hereof, nor shall any such waiver constitute a continuing waiver unless otherwise expressly provided. 

5.19.
Counterparts. This Agreement may be executed in one or more counterparts, each of which shall be deemed an original, but all of which together
shall constitute one and the same instrument. 

5.20.
Entire Agreement. This Agreement (including its Appendices, which form a part of it) constitutes the entire agreement of the parties hereto
pertaining to the operation of the Registry TLD and supersedes all prior agreements, understandings, negotiations and discussions, whether oral or written, between the parties on that subject. In the
event of a conflict between the provisions in the body of this Agreement (Section 1 to Subsection 5.20) and any provision in its Appendices, the provisions in the body of the Agreement shall
control. 

IN
WITNESS WHEREOF, the parties hereto have caused this Agreement to be executed in duplicate by their duly authorized representatives. 

INTERNET
CORPORATION FOR ASSIGNED NAMES AND NUMBERS 

	By:	
 M. Stuart Lynn

President and CEO	 
	

Date:	

May 11, 2001	

 
	

NeuLevel, Inc.	

 
	

By:	

 Doug Armentrout

Chief Executive Officer	

 
	

Date:	

May 11, 2001	

 

APPENDIX A  

 
  Internet Assigned Numbers Authority
  Format and Technical Requirements for Requests to Change
  TLD Nameservers in the Root Zone

(This
document applies only to TLDs as to which a written agreement is in effect between ICANN and the TLD delegee, sponsor, or operator.) 

1.
Requests for changes in TLD nameserver delegations to be reflected in the root zone are to be submitted by e-mail to root-mgmt@iana.org. 

2.
Requests should be submitted by filling out the template available at http://www.iana.org/tld/cctld-template.txt (for ccTLDs) or  http://www.iana.org/tld/tld-template.txt (for other TLDs). 

3.
Nameserver change requests are subject to verification of authenticity and authorization. Both the listed technical contact and the listed administrative contact should be available to verify that
the request is authentic and they authorize the requested change. Except where a written agreement between ICANN and the TLD delegee, sponsor, or operator expressly states to the contrary, the IANA
shall be entitled to rely on authorization of either the administrative or technical contact as constituting a request for nameserver change by the TLD delegee, sponsor, or operator. 

4.
Requests for changes to nameservice for ccTLDs (i.e. TLDs having two-letter labels) must result in delegation to at least two nameservers, preferably on different network segments.
Requests for changes to nameservice for other TLDs must result in delegation to nameservers on at least five different network segments. 

5.
Delegations of a TLD to more than thirteen nameservers are not supported. 

6.
Prior to submitting the request, nameservice should be set up at all the nameservers to which delegation is to be made. Lame delegations (i.e. delegations to servers without operating nameservice
for the delegated zone) will not ordinarily be made. 

7.
The IANA must have zone file access. Except where other arrangements are made (such as for TLDs with large zones), this means that zone file transfers must be enabled at all nameservers for
transfers to at least 128.9.0.0/16 and 192.0.32.0/20. 

(9
May 2001) 

APPENDIX B  

 
  Internet Assigned Numbers Authority
  Format, Content, and Technical Requirements for Requests to
  Change TLD Contact Information

(This
document applies only to TLDs as to which a written agreement is in effect between ICANN and the TLD delegee, sponsor, or operator.) 

1.
Requests for changes in TLD contact data are to be submitted by e-mail to root-mgmt@iana.org. 

2.
Requests should be submitted by filling out the template available at at http://www.iana.org/tld/cctld-template.txt (for ccTLDs) or  http://www.iana.org/tld/tld-template.txt (for other TLDs). 

3.
Requests for changes to TLD contact data must include all applicable elements of data requested in items 3-5 of the template. All information submitted must be accurate. 

4.
Contact change requests are subject to verification of authenticity and authorization. Both the listed technical contact and the listed administrative contact should be available to verify that the
request is authentic and they authorize the requested change. Except where a contract between ICANN and the TLD delegee, sponsor, or operator expressly states to the contrary, the IANA shall be
entitled to rely on authorization of either the administrative or technical contact as constituting a request for a contact change by the TLD delegee, sponsor, or operator, except that any change of
the identity of the sponsoring organization, administrative contact, or technical contact must comply with notice requirements stated in the agreement. 

(9
May 2001) 

APPENDIX C  

 
  Functional Specifications  
  

C.1 Registry Overview  

This
section will provide an overview of the registry. Specifically it will describe the registry facilities, the SRS systems and functions, and the nameserver systems and functions. 

C.1.1 Registry Facilities Site Description  

This
section describes NeuLevel's proposed TLD Registry architecture consisting of redundant SRS data centers and multiple nameserver sites to provide a seamless, responsive, and reliable registry
service to registrars and Internet users. The NeuLevel TLD registry consists of redundant SRS and multiple nameserver data center sites geographically dispersed. All of these sites are interconnected
with a secure Virtual Private Network (VPN) to provide worldwide coverage and protect against natural and man-made disasters and other contingencies. 

SRS Data Center and Nameserver Buildings  

Each
NeuLevel data center facility is located in a modern, fire-resistant building that offers inherent structural protection from such natural and man-made disasters as
hurricanes, earthquakes, and civil disorder. Facilities are protected by a public fire department, and have their internal fire-detection systems connected directly to the fire department. 

Data
centers are protected from fire by the sprinkler systems of the buildings that house them. Furthermore, each equipment room is protected by a pre-action fire-suppression
system that uses an extinguishing agent. 

The
environmental factors at the SRS Data Center and nameserver sites are listed in the following table. 

	

	SRS DATA CENTER ENVIRONMENTAL FACTORS
	

	Heating, ventilation, and air conditioning	 	Redundant HVAC units control temperature and humidity, able to maintain the required environment under failure of any one unit.
	

	Control of static electricity	 	All equipment-mounting racks are grounded to the building's system, and are equipped with grounding straps that employees wear whenever they work on the equipment.
	

	Power supply	 	Modular UPS with battery backup and diesel generator.
	

	Grounding	 	•	All machines are powered by grounded electrical service.
	 	 	•	A heavy-gage cable under the equipment-room floor connects all equipment racks to the building's electrical-grounding network.
	

Building Security  

In
addition to providing physical security by protecting buildings with security guards, closed circuit TV surveillance video cameras, and intrusion detection systems, physical access to our
facilities is vigilantly controlled. Employees must present badges to gain entrance, and must wear their badges at all times while in the facility. Visitors must sign in to gain entrance. If the
purpose of their visit is found to be valid, they are issued a temporary badge; otherwise, they are denied entrance. At all times while they are in the facility, visitors must display their badges and
must be escorted by an authorized employee. Sign-in books are maintained for a period of one year. 

C.1.2 Shared Registration System (SRS) Data Center Functional Description  

The
SRS data centers incorporate redundant uninterruptible power supplies; high-capacity heating, ventilation, and air conditioning; fire suppression; physical security; system security;
firewalls with intrusion detection; redundant, high availability cluster technology; and redundant network and 

telecommunications
architectures. The sites have been engineered to be resistant to natural and man-made disasters. The functional block diagram of our SRS data center is depicted in
Exhibit 1. This diagram is shown for illustrative purposes and is a target architecture. Details within the diagram are subject to change as we progress through development and deployment. 

        Each
SRS data center facility provides the functions listed in the system function directory table below. 

	

	SHARED REGISTRATION SYSTEM (SRS) FUNCTION DIRECTORY
	

	System Function	 	Functional Description
	

	Web Server	 	High capacity Web Servers provide secure web services and information dissemination that is outside the scope of the XRP protocol. It contains a registry home page to enable registrars to sign in and inquire about account
status, get downloads and whitepapers, access frequently asked questions, obtain self help support, or submit a trouble ticket to the TLD Registry Help Desk.
	

	Protocol (XRP) Servers	 	XRP transactions received from registrars undergo front-end processing by the XRP server that manages the XRP session level dialog, performs session level security processing, and strips out transaction records. These XRP
transaction records are sent to the SRS data center application server cluster for security authentication and business logic processing.
	

	Application Servers	 	Processing of the XRP applications business logic, user authentication, posting of inserts, deletes, updates to the master database, and interfaces to authentication, billing and collections, backup, and system/network
administration.
	

	SRS Database Servers	 	The SRS database maintains registry data in a multi-threaded, multi-session database for building data-driven publish and subscribe event notifications and replication to downstream data marts such as the Whois, Zone, and
Billing and Collection services.
	

	Whois Distribution Database	 	The Whois Distribution Database is dynamically updated from the SRS database and propagates the information to the Whois Database clusters.
	

	Whois Database Clusters	 	The Whois Database is dynamically updated from the Whois Distribution Database and sits behind the Whois Server clusters. The Whois Database clusters are used to lookup records that are not cached by the Whois
Servers.
	

	Whois Servers	 	The Load Balanced Whois Server Clusters receive a high volume of queries from Registrants and Internet users. The Whois service returns information about Registrars, domain names, nameservers, IP addresses, and the
associated contacts.
	

	Zone Distribution Database	 	The Zone Distribution Database is dynamically updated from the registry SRS database and propagated to the nameserver sites located worldwide. It contains domain names, their associated nameserver names, and the IP
addresses for those nameservers.
	

	Billing and Collection	 	A commercial off the shelf system is customized for registry specific eCommerce billing and collection functions that are integrated with XRP transaction processing, the master database and a secure web server. The system
maintains each registrar's account information by domain name and provides status reports on demand.
	

	Authentication Services	 	Authentication Service uses X.509 digital certificates and is used to authenticate the identity of entities interacting with the SRS.
	

	Backup Server	 	Provides backup and restore of each of the various cluster servers and database servers files and provides a shared robotic tape library facility for central backup and recovery.
	

	 	 	 

	Systems/Network Management Console	 	Provides system administration and simple network management protocol (SNMP) monitoring of the network, LAN-based servers, cluster servers, network components, and key enterprise applications including the XRP, Web, Whois,
 Zone, Billing and Collections, Backup/Restore, and database application. Provide threshold and fault event notification and collects performance statistics.
	

	Applications Administration Workstations	 	Provides client/server GUI for configuration of SRS applications including XRP, Web, Billing and Collection, Database, Authentication, Whois, Zone, etc.
	

	Building LAN	 	Provides dual redundant switched 100BaseT Ethernet LAN-based connectivity for all network devices in the data center.
	

	Firewall	 	Protects the building LAN from the insecure Internet via a Firewall that provides policy-based IP filtering and network-based intrusion detection services to protect the system from the Internet hacking and denial of
service attacks.
	

	Load Balancers	 	Dynamic Feedback Protocol (DFP) — based load balancing of TCP/IP traffic in a server cluster including common protocols such as least connections, weighted least connections, round robin, and weighted round
robin.
	

C.1.3 Nameserver Sites Functional Description  

Two
of the five initial nameserver sites are co-located at our SRS Data Centers. One of the remaining nameserver sites will be located in Europe, another of the remaining nameservers will
be located in Asia. The location of the fifth nameserver site has not yet been determined. Additional geographically dispersed nameserver sites will be deployed as load and geographic diversity needs
dictate and will be served with dual homed Internet and VPN local access telecommunications links to provide resilience and disaster recovery. The functional block diagram of our nameserver sites is
depicted in Exhibit 2. As can be seen from the exhibit the nameserver sites are configured to be remotely managed and operated "lights out". This diagram is shown for illustrative purposes and
is a target architecture. Details within the diagram are subject to change as we progress through development and deployment. 

        The
following function directory table lists the nameserver functions. 

	

	NAMESERVER FUNCTION DIRECTORY
	

	System Function	 	Functional Description
	

	Zone Update Database	 	The SRS Zone Distribution Database is propagated to the Zone Update Database Servers at the nameserver sites. Information propagated includes domain names, their associated nameserver names, and the IP addresses for those
nameservers.
	

	Nameserver	 	The nameserver handles resolution of TLD domain names to their associated nameserver names and to the IP addresses of those nameservers. The nameservers are dynamically updated from the Zone Update Database. Updates are
sent over the VPN Registry Management Network.
	

	Building LAN	 	Provides dual redundant switched 100BaseT Ethernet LAN-based connectivity for all network devices in the data center.
	

	Firewall hacking	 	Protects the building LAN from the insecure Internet via a Firewall that provides policy-based IP filtering and network-based intrusion detection services to protect the system from the Internet and denial of service
attacks.
	

	Load Balancers	 	Dynamic Feedback Protocol (DFP)—based load balancing of TCP/IP traffic in a server cluster including common protocols such as least connections, weighted least connections, round robin, and weighted round
robin.
	

	Telecommunications Access	 	Dual-homed access links to Internet Service Providers (ISPs) and Virtual Private Network (VPN) services are used for connectivity to the Internet and the NeuLevel Registry Management Network.
	

C.2 Registry-Registrar Model and Protocol  

The
document linked below has been submitted to the PROVREG Working Group of the Internet Engineering Task Force (IETF) for consideration for development of an IETF standard regarding a
Registry-Registrar Protocol. It describes in great detail the NeuLevel proposal for the registrar interface to the registry. It includes all of the commands and capabilities that exist between the
registry and the registrar. This document is subject to change by agreement of Registry Operator and ICANN during the design process as well as during the IETF standards process. However, the
following provides the target architecture and initial functionality. 

Neulevel
will implement support for the IETF PROVREG working group's protocol specification no later than 135 days after it is adopted as a Proposed Standard [RFC 2026, section
4.1.1]. 

E.  Brunner-Williams,
A. Damaraju & N. Zhang: "Extensible Registry Protocol (XRP)", draft-brunner-xrp-00.txt, work in progress. 

C.3 Zone File generation, Distribution, and Publication  

NeuLevel
will generate and propagate DNS zone file updates to the DNS server array incrementally as transactional updates initiated by the SRS resulting from new domain name registrations. Updates
will be initiated from the SRS, and queued and propagated to the DNS server array in near real-time consistent with the applicable service level requirements. 

The
NeuLevel registry would store only the following resource records in the zone file database: 

	•
	A
single SOA record

	•
	A
number of NS and A records, up to a maximum of 13 of each, for the TLD DNS servers for .biz

	•
	Domain
name and delegated nameservers (NS Records)

	•
	Name-server
host names and their associated IP addresses (A Records) 

NeuLevel
will implement, on a reasonable schedule, glue-generation and pruning criteria specified by ICANN from time to time. 

Zone File Access Program  

NeuLevel
will provide a data mart to enable registrars to access the zone file in bulk. Our proposed query program will: 

	•
	Reduce
the load placed on the nameservers by data mining programs. (For example, some ISPs use data mining to accelerate domain name availability checking.)

	•
	Bind
subscribers to limiting conditions as to how they can use the data, according to the terms set forth in Appendix N.

	•
	Provide
the entire database in a BIND format that will facilitate such services as suggesting alternate names, accelerating DNS queries, and compiling industry statistics. 

Logging and Data Back-up  

All
zone files and updates are generated using information from the SRS database. All updates are recorded as database transaction logs. 

Zone File-Generation Architecture  

Zone
file information is stored in the SRS database (along with all other registry data) and replicated to a zone distribution server within defined service levels. See Appendix D, item 3.5.1. The
database stored on the zone distribution server is in turn replicated out to a database at the nameserver data centers. 

Standards Compliance  

The
DNS name server array will comply with the IETF standards for the DNS (RFC1035, RFC2181, RFC 2182). In addition, DNS extensions (security, transactional updates, internationalization, etc.)
adopted or proposed by IETF will be assessed and supported consistent with industry acceptance and prudent operational considerations as part of the release requirements definition for the initial
registry release and each subsequent one. 

NeuLevel
expects to implement all applicable best-practice recommendations contained in RFC2870 (Root Nameserver Operational Requirements), as they become practicable. 

C.4 Whois Service  

Please
see Appendix O. 

C.5 Customer Support Services and Capabilities  

The
registry provides a clear, concise and efficient deliberation of customer support responsibilities. Registrars provide support to registrants and registries provide support for registrars. This
allows the registry to focus its support on the highly technical and administratively complex issues that arise between the registry and the registrar. 

C.5.1 Technical Help Systems  

NeuLevel
will provide the registrars with the following types of technical support: 

	•
	Web-based
self-help services, including:

	•
	Knowledge
bases

	•
	Frequently
asked questions

	•
	White
papers

	•
	Downloads
of XRP client software

	•
	Support
for email messaging

	•
	Telephone
support from our central Help Desk

	•
	Fee-based
consulting services 

Web Portal  

NeuLevel
will implement a secure Web-based multimedia portal to help support registrar operations. To obtain access to our Web-based services, a registrar must register his registrants with us, and
must have implemented our security features, including SSL encryption, log in with user ID and password, and digital certificates for authentication. 

The
home page of the web portal will include a notice to registrars of planned outages for database maintenance or installation of software upgrades. This notification will be posted 30 days prior to
the event in addition to active notification including phone calls and email. We will also record outage notifications in the help desk database to facilitate compliance with the service-level
agreement. Finally, seven days and again two days prior to the scheduled event, we will use both an email and a Web-based notification to remind registrars of the outage. 

Non-affiliated
registrars and the general Internet community may obtain generic information from NeuLevel's public Web site, which will describe our TLD service offerings and list ICANN-certified
registrars providing domain-name services. 

Central Help Desk  

In
addition to implementing the Web site, we will provide telephone support to our registrars through our central Help Desk. Access to the help desk telephone support is through an automatic call
distributor that routes each call to the next available customer support specialist. We will authenticate callers by using caller ID and by requesting a pre-established pass phrase that is different
for each registrar. Requests for assistance may also come to the Help Desk via email, either directly or via the secure Web site. 

The
Help Desk's three tiers of support are: 

Tier-1 Support—Telephone support to registrars who normally are calling for help with customer domain-name problems and such other issues
such as XRP implementation or billing and collection. Problems that can't be resolved at Tier 1 are escalated to Tier 2. 

Tier-2 Support—Support provided by members of the technical support team, who are functional experts in all aspects of domain-name
registration. In addition to resolving escalated Tier 1 problems with XRP implementation and billing and collection, Tier 2 staff provides technical support in system tuning and workload processing. 

Tier-3 Support—Complex problem resolution provided by on-site maintenance technicians, third party systems and software experts, and
vendors, depending on the nature of the problem. 

In
turn, the Help Desk uses an automated software package to collect call statistics and record service requests and trouble tickets in a help desk database. The help desk database documents the
status of requests and tickets, and notifies the Help Desk when an SLA threshold is close to being breached.
Each customer-support and technical support specialist uses our problem management process to respond trouble tickets with a troubleshooting, diagnosis, and resolution procedure and a root-cause
analysis. 

Escalation Policy  

Our
escalation policy defines procedures and timelines for elevating problems either to functional experts or to management for resolution if they not resolved within the escalation-policy time
limits. The following table is an overview of our escalation policy. 

	 
	 	 
	 	 
	 	 

	Level
 
	 	Description
	 	Escalation Policy
	 	Notification

	I	 	Catastrophic outage affecting overall registry operations	 	Data-center manager escalates to NeuLevel management and Disaster-Recovery Team if not resolved in 15 minutes	 	Web portal and e-mail notifications to all Registrars within 15 minutes; updates every 30 minutes
	

II	
 	

Systems outage affecting one or two registrar sessions but not the entire system	
 	

Systems engineer escalates to data-center manager if not resolved in one hour	
 	

Web-portal notification to all registrars; hourly updates
	

III	
 	

Technical questions	
 	

Help Desk customer-support specialist escalates to the systems engineer if not resolved in two hours	
 	

Hourly updates to registrar via e-mail
	

IV	
 	

Basic questions	
 	

Help Desk customer-support specialist escalates to the systems engineer if not resolved within four hours	
 	

Hourly updates to registrar via e-mail

Staffing  

Initially,
NeuLevel will staff its Help Desk with a complement of customer service specialists. We will add staff as necessary to respond to incoming requests within the service-level agreement.
Customer-service specialists will obtain assistance from NeuLevel's technical staff for any problems that cannot be resolved in one phone call. 

Test and Evaluation Facility  

NeuLevel
will establish an operational test-and-evaluation facility that will be available for registrars to test their client XRP system. Our technical-support team, which consists of functional
experts in the processes and technologies for domain-name registration, will support the registrars' testing. 

Once
each new registrar is satisfied that its system is compatible with the registry system, it will schedule a formal acceptance test that will be monitored by our system engineer. After a registrar
has passed the acceptance test, we will issue its user id, passwords, and digital certificates, and the registrar can begin operations. 

Customer Satisfaction Survey  

To
determine registrars' satisfaction with registry services, NeuLevel will implement a Web-based customer-satisfaction survey that will consist of a set of survey questions with responses ranging
from one to five on the Likert Scale. We will tabulate the results and publish them on the Web site. 

To
further verify the quality of our customer services, NeuLevel will commission a biannual customer-satisfaction survey by an independent third party. 

C.6 Operational Test and Evaluation  

Before
a Registrar is allowed to join the live.biz Open Architecture Registry System (OARS) it must first pass Operational Test and Evaluation (OT&E) certification. The purpose of OT&E certification
is to verify the correct operation and performance of a Registrar's client system. 

Preparations for OT&E Certification  

The
OT&E certification process begins when a Registrar becomes accredited by ICANN to register names in the.biz TLD, at which point the Registrar enters the.biz Registry provisioning process. The
Registrar fills out a registration form and a.biz welcome package is provided to the Registrar. This package includes information that will assist the Registrar in implementing its Extensible Registry
Protocol (XRP) client application for OARS. This package will include the following: 

1.  Username
and password to access the Registrar Channel Partner only area of the.biz web site. 

2.  The
OT&E Testbed server information and username/password for two accounts to access the.biz OT&E Testbed for Registrar client testing. 

3.  Instructions
on where to download the XRP Registrar Tool Kit. 

4.  Instructions
on where to download the documentation for the XRP Registrar Tool Kit. 

5.  Instructions
on where to download the XRP specifications and XRP Common Application Programmer Interfaces (APIs). 

6.  Instructions
on how to proceed with the OT&E certification process. 

7.  Instructions
on how to obtain an SSL certificate from an approved Certificate Authority. 

8.  Instructions
on how to provide.biz with the list of subnets that will be used to access the OARS. 

9.  Test
Plans and Procedures that will explain the test cases, test metrics, data collection, test data analysis, and reporting to be performed during OT&E verification. 

The
Registrar is responsible for installing the XRP client application that will interface to the Registry using the XRP protocol. The Registrar will interface the XRP client to the back office
systems via the XRP common APIs. The.biz Registrar Tool Kit is available to any interested party that would like to implement Registrar client applications. 

The
Registry-Registrar communication channel will be encrypted. A SSL certificate from an approved Certificate Authority is required to establish a SSL Version 3.0 encrypted channel. The
username/password and subnet list provides additional security as only a valid combination of a SSL Version 3.0 certificate; username/password and subnet will be allowed to access the live Shared
Registry System. 

During
XRP client implementation, the Registrar has access to the Registry OT&E Testbed environment. In the OT&E Testbed, the Registrar may test the operation of its software to verify the correct
handling of XRP commands, their responses, and notification messages. Operations performed in the OT&E environment will not be charged and will not have any impacts on the live OARS. Registrars will
continue to have access to the OT&E Testbed after certification, so that they may continue to test their back office software systems. 

When
a Registrar has completed the testing of its XRP client and back office systems and would like to proceed with OT&E certification, it should contact.biz Customer Care to schedule a time
slot. Time slots will be scheduled on a first-come-first-serve basis. 

At
the scheduled time, the Registrar should contact the.biz OT&E Technical Support Team to initiate the certification. 

The Registrar Tool Kit  

The
Registrar Toolkit Kit is a software development kit (SDK) that will support the development of a Registrar software system for registering Internet domain names in the Registry using the XRP
Registry-Registrar Protocol and the XRP common APIs. The SDK will consist of software and documentation as described below. 

The
SDK can be used by the Registrar as a basis for connecting to the.biz Registry Testbed environment during OT&E, and can also be used to develop a system for interfacing with the live.biz Registry
once the Registrar has been certified. 

The
software will consist of a working Java XRP common API and samples of interfaces to back office systems that implement the XRP protocol core functions and XRP extensions that are used to
communicate between the Registry and Registrar. The SDK will illustrate how XML requests (Registration Events) can be assembled and forwarded to the Registry for processing. The software will provide
the Registrar with the basis for a reference implementation that conforms to the XRP Registry-Registrar Protocol. The software component of the SDK will also include XML Schema definition files for
all Registry XRP objects and XRP Object extentions. 

The
documentation will also describe the XRP software package hierarchy, the object data model, and an description of the defined objects and methods (including calling parameter lists, and expected
response behavior). New versions of the SDK will be made available from time to time to provide support additional features as they become available as well as other platform and language support. 

OT&E Certification Test Cases  

During
OT&E certification, a Registrar's client application will be required to demonstrate the proper execution of the following operations. 

1.  SSL
Version 3.0 connection establishment 

2.  XRP
<login> command 

3.  Change
of <login> password 

4.  XRP
<logout> command 

5.  Domain
Name Operations 

a.  Create
domain without nameservers and without contacts (XRP Transform <create>) 

b.  Create
domain with nameservers 

c.  Create
domain with contacts 

d.  Create
domain with maximum registration period 

e.  Create
domain with maximum number of nameservers 

f.  Create
domain with maximum number of contacts 

g.  Create
domain with maximum length domain name (63 characters +.BIZ) 

h.  Create
domain with invalid name 

i.  Check
domain (XRP Query <check>)—domain not available 

j.  Check
domain (XRP Query <check>)—domain available 

k.  Check
domain—maximum length domain name (63 characters +.BIZ) not available 

l.  Query
domain (XRP Query <INFO>) 

m.  Query
domain transfer status (XRP Query <transfer>) 

n.  Delete
domain (XRP Transform <delete>) 

o.  Renew
domain (XRP Transform <renew>) 

p.  Transfer
domain (XRP Transform <transfer>) 

q.  Change
domain (XRP Transform <update>)—nameservers 

r.  Change
domain (XRP Transform <update>)—contact 

s.  Change
domain (XRP Transform <update>)—status 

5.  Nameserver
Operations 

a.  Create
nameserver (XRP Transform <create>) 

b.  Create
nameserver with maximum length host name (80 characters) 

c.  Check
nameserver (XRP Query <check>)—nameserver known 

d.  Check
nameserver (XRP Query <check>)—nameserver unknown 

e.  Query
nameserver (XRP Query <INFO>) 

f.  Delete
nameserver (XRP Transform <delete>) 

g.  Change
nameserver (XRP Transform <update>)—add IP address 

h.  Change
nameserver (XRP Transform <update>)—remove IP address 

6.  Contact
Operations 

a.  Create
contact (XRP Transform <create>) 

b.  Check
contact (XRP Query <check>)—contact known 

c.  Check
contact (XRP Query <check>)—contact unknown 

d.  Query
contact (XRP Query <INFO>) 

e.  Query
contact transfer status (XRP Query <transfer>) 

f.  Delete
contact (XRP Transform <delete>) 

g.  Transfer
contact (XRP Transform <transfer>) 

h.  Change
contact (XRP Transform <update>)—change element 

i.  Change
contact (XRP Transform <update>)—remove element 

7.  Registrant
Account Operations 

j.  Create
Registrant Account (XRP Transform <create>) 

k.  Check
Registrant Account (XRP Query <check>)—contact known 

l.  Check
Registrant Account (XRP Query <check>)—contact unknown 

m.  Query
Registrant Account (XRP Query <INFO>) 

n.  Query
Registrant Account transfer status (XRP Query <transfer>) 

o.  Delete
Registrant Account (XRP Transform <delete>) 

p.  Transfer
Registrant Account (XRP Transform <transfer>) 

q.  Change
Registrant Account (XRP Transform <update>)—change element 

r.  Change
Registrant Account (XRP Transform <update>)—remove element 

8.  Effectiveness
and Utility of client session management and information exchange. 

9.  Performance
of client session management and information exchange throughput. 

NOTE:
The Registry reserves the right to change the OT&E certification requirements as necessary to ensure compliance with the evolving XRP IEFT standard and XRP common APIs. 

Post OT&E Certification  

All
tests performed during OT&E certification must be completed without errors. The Registry will provide the certification results in a timely manner and provide feedback for those Registrars that
failed to successfully complete the tests. Registrars may correct their systems and re-schedule for certification. Registrars will not be limited in the number of attempts at OT&E
certification. 

Upon
successful OT&E certification, the Registrar becomes eligible for operation in the live OARS. A new username/password is assigned and the Registry will configure the live system to recognize the
SSL certificate, username, password, and subnet blocks for the Registrar. The Registrar may start operation when it has satisfied the financial requirements for going live. 

C.7 Registrar Reports  

NeuLevel
will provide a reporting service allowing Registrars to retrieve reports on their customer base. These reports will be posted to a secure site (i.e. FTP) that can be accessed by the
individual Registrar by entering username and passcode. The format for reports will be easily machine-readable by registrars (i.e. XML, CSV). Naming convention of reports will identify the registrar,
the date the report was created and indicate subject of the report. The Registry will archive copies of all reports created. 

These
reports are: 

1.  Daily
Reconciliation Reports created from credit/debit and debit account transaction logs 

2.  Daily
and Monthly Registrar Cumulative Report for domain-names registrations 

3.  Transaction
logs 

4.  Complete
database export file of all data entities they own 

The
Registrar Cumulative Reports include: 

	•
	Total.biz
domain-names strings processed

	•
	Total.biz
domain-names "registered"

	•
	Total.biz
domain-name strings "unavailable"

	•
	Total.biz
domain-name strings "invalid" 

	•
	Total
Credit/Debit Card account transactions and amount

	•
	Total
Debit account debits and amount

	•
	Total
Wire Transfers and amount 

Custom
Reporting is an optional feature that would allow registrars to specify report criteria and have a report available for download upon completion. 

	•
	Numbers
and names of domain-names registered within any period

	•
	Domain-names
transferred to/away from registrar within a specified period

	•
	Change
of ownership activity, time/date request were processed

	•
	Re-delegation
activity 

Comments
concerning the layout, construction and functionality of this site should be sent to webmaster@icann.org. 

Page
Updated 27-April-2001

©2001 The Internet Corporation for Assigned Names and Numbers. All rights reserved. 

C.8 Database Services  

The
following grammer representation of XML syntax uses the Augmented Backus-Naur Form (ABNF), defined in rfc2234: 

	octet	=	<any 8-bit sequence of data>
	

hextet	

=	

<any 16-bit sequence of data>
	

char	

=	

<any US-ASCII character (octets 0—127)>; see ANSI X3.4-1986
	

upalpha	

=	

"A" -- "B" -- "C" -- "D" -- "E" -- "F" -- "G" -- "H" -- "I" -- "J" -- "K" -- "L" -- "M" -- "N" -- "O" -- "P" -- "Q" -- "R" -- "S" -- "T" -- "U" -- "V" -- "W" -- "X" -- "Y" -- "Z"
	

lowalpha	

=	

"a" -- "b" -- "c" -- "d" -- "e" -- "f" -- "g" -- "h" -- "i" -- "j" -- "k" -- "l" -- "m" -- "n" -- "o" -- "p" -- "q" -- "r" -- "s" -- "t" -- "u" -- "v" -- "w" -- "x" -- "y" -- "z"
	

alpha	

=	

lowalpha -- upalpha; also called "letter"
	

digit	

=	

"0" -- "1" -- "2" -- "3" -- "4" -- "5" -- "6" -- "7" -- "8" -- "9"; also called "number"
	

alphanum	

=	

alpha -- digit; also called "letnum"
	

plus	

=	

0x2b
	

hyphen	

=	

0x2d; also called "dash"
	

dot	

=	

0x2e
	

underscore	

=	

0x5F
	

ldh	

=	

alpha -- digit -- hyphen; also (abuse of notation) called "dns-char"
	

id-prefix	

=	

alphanum
	

ldh-label	

=	

[61* ldh id-prefix]
	

label	

=	

id-prefix ldh-label
	

sldn	

=	

label dot label
	

hostname	

=	

*(label dot) sldn
	

ipv4-addr	

=	

1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT "." 1*3DIGIT
	 	 	 

	

ipv6-addr	

=	

hexpart [":" IPv4address]
	

hexpart	

=	

hexseq -- hexseq "::" [hexseq] -- "::" [hexseq]
	

hexseq	

=	

hex4 *(":" hex4)
	

hex4	

=	

1*4HEXDIG
	

e164a-addr	

=	

plus 1*3 digit dot 1*12 digit

Every
resource record in the.biz zone will have one of the following as its owner: 

	•
	xbiz
(for the SOA record and ns records for the.biz zone itself)

	•
	An
sldn, where the right-hand label is "biz" (for NS records)

	•
	A
hostname, where the right-hand label is "biz" (for A records) 

C.9 Transfers  

The
system will provide a function to TRANSFER ownership of an entity to a new parent entity. Examples of this are transferring a domain-name to a new registrant (Transfer of
registrant/registrar) and transferring a registrant to a new registrar (Transfer of registrar). 

The
TRANSFER function will operate on the registrant, domain-name, and contact entities. 

The
TRANSFER function will take a source entity type and identifier as well as a new sponsorship entity type and identifier as input. If the source entity type is a domain-name the new
owner entity type must be a registrant. If the source entity type is a registrant, the new owner entity type must be a registrar. 

The
TRANSFER function will return a response code indicating success or failure. 

Registrars
will only be able to TRANSFER a registrant entity to themselves, and to do so they must supply the registrant authentication. 

Registrars
will only be able to TRANSFER domain-name entities to registrants that they sponsor. 

Registry
supervisors will be able to TRANSFER any domain-name entity to any registrant. 

Registry
supervisors will be able to TRANSFER any registrant to any registrar. 

Transfer
of domain-name entities creates billing transactions. 

C.10 Grace Period  

Add Grace Period  

The
Add Grace Period is a specified number of calendar days following the initial registration of a domain. The current value of the Add Grace Period for all registrars is five calendar days. If a
Delete, Renew, or Transfer operation occurs within the five calendar days, the following rules apply: 

Delete.    If a domain is deleted within the Add Grace Period, the sponsoring Registrar at the time of the deletion is credited for the amount
of the registration. The domain is deleted from the Registry database and is immediately available for registration by any Registrar. See below for a description of overlapping grace period
exceptions. 

Renew.    If a domain is extended within the Add Grace Period, there is no credit for the add. The account of the sponsoring Registrar at the
time of the extension will be charged for the initial add plus the number of years the registration is extended. The expiration date of the domain is extended by the number of years, up to a total of
ten years, as specified by the registrar's requested Renew operation. 

Transfer (other than ICANN—approved bulk transfer).    Transfers under Part A of Exhibit B to the Registry—Registrar
Agreement may not occur during the Add Grace Period or at any other time within the first 60 days after the initial registration. Enforcement is the responsibility of the Registrar sponsoring the
domain name registration and is currently enforced by the SRS. 

Bulk Transfer (with ICANN approval).    Bulk transfers with ICANN approval may be made during the Add Grace Period according to the procedures
in Part B of Exhibit B to the Registry—Registrar Agreement. The expiration dates of transferred registrations are not affected. The losing Registrar's account is charged for the initial
add. 

Renew Grace Period  

The
Renew Grace Period is a specified number of calendar days following the renewal of a domain name registration period through an XRP Command Renew. The current value of the Renew Grace Period is
five calendar days. If a Delete, Extend, or Transfer occurs within that five calendar days, the following rules apply: 

Delete.    If a domain is deleted within the Renew Grace Period, the sponsoring Registrar at the time of the deletion receives a credit of the
renew fee. The deleted domain is moved to the Redemption Grace Period (that is, to the PendingDelete status) as described in Appendix C.11. See below for a description of overlapping grace period
exceptions. 

Renew.    A domain can be extended within the Renew Grace Period for up to a total of ten years. The account of the sponsoring Registrar at
the time of the additional extension will be charged for the additional number of years the registration is extended. 

Transfer (other than ICANN—approved bulk transfer).    If a domain is transferred within the Renew Grace Period, there is no
credit. The expiration date of the domain is extended by one year and the years added as a result of the Extend remain on the domain name up to a total of 10 years. 

Bulk Transfer (with ICANN approval).    Bulk transfers with ICANN approval may be made during the Renew Grace Period according to the
procedures in Part B of Exhibit B to the Registry—Registrar Agreement. The expiration dates of transferred registrations are not affected. The losing Registrar's account is charged for the
Renew operation. 

Auto-Renew Grace Period  

The
Auto-Renew Grace Period is a specified number of calendar days following an auto-renewal. An auto-renewal occurs if a domain name registration is not renewed by the expiration date; in this
circumstance the registration will be automatically renewed by the system the first day after the expiration date. The current value of the Auto-Renew Grace Period is 45 calendar days. If a Delete,
Renew, or Transfer occurs within the Auto-Renew Grace Period, the following rules apply: 

Delete.    If a domain is deleted within the Auto-Renew Grace Period the deleted domain is moved to the Redemption Grace Period (that is, to
the PendingDelete status) as described in Appendix C.11. See below for a description of overlapping grace period exceptions. 

Renew.    A domain can be Renewed within the Auto-Renew Grace Period for up to a total of ten years. The account of the sponsoring Registrar
at the time of the additional extension will be charged for the additional number of years the registration is extended. 

Transfer (other than ICANN—approved bulk transfer).    If a domain is transferred under Part A of Exhibit B to the
Registry—Registrar Agreement within the Auto-Renew Grace Period, the losing Registrar is credited with the Auto-Renew charge and the year added by the Auto-Renew operation is cancelled.
The expiration date of the domain is extended by one year up to a total maximum of ten by virtue of the transfer and the gaining Registrar is charged for that additional year, even in cases where a
full year is not added because of the 10-year maximum limitation. 

Bulk Transfer (with ICANN approval).    Bulk transfers with ICANN approval may be made during the Auto-Renew Grace Period according to the
procedures in Part B of Exhibit B to the Registry—Registrar Agreement. The expiration dates of transferred registrations are not affected. The losing Registrar's account is charged for the
Auto-Renew. 

Transfer Grace Period  

The
Transfer Grace Period is a specified number of calendar days following the transfer of a domain according to Part A of Exhibit B to the Registry—Registrar Agreement. The current value
of the Transfer Grace Period is five calendar days. If a Delete, Extend, or Transfer occurs within that five calendar days, the following rules apply: 

Delete.    If a domain is deleted within the Transfer Grace Period, the sponsoring Registrar at the time of the deletion receives a credit of
the transfer fee. The deleted domain is moved to the Redemption Grace Period (that is, to the PendingDelete status) as described in Appendix C.11. See below for a description of overlapping grace
period exceptions. 

Renew.    If a domain is extended within the Transfer Grace Period, there is no credit for the transfer. The Registrar's account will be
charged for the number of years the registration is extended. The expiration date of the domain is extended by the number of years, up to a maximum of ten years, as specified by the registrar's
requested Extend operation. 

Transfer (other than ICANN—approved bulk transfer).    If a domain is transferred within the Transfer Grace Period, there is no
credit. The expiration date of the domain is extended by one year up to a maximum term of ten years. 

Bulk Transfer (with ICANN approval).    Bulk transfers with ICANN approval may be made during the Transfer Grace Period according to the
procedures in Part B of Exhibit B to the Registry—Registrar Agreement. The expiration dates of transferred registrations are not affected. The losing Registrar's account is charged for the
Transfer operation that occurred prior to the Bulk Transfer. 

Bulk Transfer Grace Period  

There
is no grace period associated with Bulk Transfer operations according to Part B of Exhibit B to the Registry—Registrar Agreement. Upon completion of the Bulk Transfer, any associated
fee is not refundable. 

Overlapping Grace Periods  

If
an operation is performed that falls into more that one grace period, the actions appropriate for each grace period apply (with some exceptions as noted below). 

	•
	If
a domain is deleted within the Add Grace Period and the Renew Grace Period, then the Registrar is credited the registration and renew amounts, taking into account the
number of years for which the registration and renew were done. The domain is deleted from the Registry database and is immediately available for registration by any Registrar.

	•
	If
a domain is auto-renewed, then extended, and then deleted within the Renew Grace Period, the registrar will be credited for the Auto-Renew and the number of years for the
extension. The years that were added to the Registered Name's expiration as a result of the auto-renewal and extension are removed.The deleted Registered Name is moved to the Redemption Grace Period
(that is, to the PendingDelete status) as described in Appendix C.11. 

Overlap Exception  

	•
	If
a domain is deleted within one or several Transfer Grace Periods, then only the current sponsoring Registrar is credited for the transfer amount. For example if a domain
is transferred from Registrar A to Registrar B and then to Registrar C and finally deleted by Registrar C 

within
the Transfer Grace Period of the first, second and third transfers, then only the last transfer is credited to Registrar C. 

	•
	If
a domain is extended (through the XRP command "Renew") within the Transfer Grace Period, then the current Registrar's account is charged for the number of years the
registration is extended. 

Note:  If several billable operations, including transfers, are performed on a domain and the domain is deleted within the grace periods of
each of those operations, only those operations that were performed after the latest transfer, including the latest transfer, are credited to the current Registrar. 

Earlier
Drafts: 

18 June 2003

11 May 2001

27 April 2001  

C.11 Additional Services  

Redemption Grace Period  

Overview  

The
Redemption Grace Period Service allows registrars to restore Registered Names that were unintentionally deleted and are still within a thirty-day Redemption Grace Period (RGP). The RGP
Service cover all names deleted by registrars, with the exception of those names deleted in the Add Grace Period. 

The
RGP Service may be implemented in two stages. Stage 1 is as described in the following. In the future, ICANN and Registry Operator will discuss implementation of Stage 2, with the goal, if
feasible, of allowing registrants to choose which registrar will restore their deleted name(s). 

Implementation  

The.biz
Registry RGP is a fully automated and EPP-compliant implementation. Only statuses defined in the current EPP specifications will be used. As such all domains slated for deletion
will remain in PendingDelete status for 35 days or until they are restored. 

PendingDelete Status:  

All
domains deleted outside the Add Grace Period will be placed on PendingDelete status for a total of 35 days, after which time the names will be purged from the Registry database and made
available again for registration. 

During
this PendingDelete timeframe, domain names can only be restored during the first 30 days, and cannot be otherwise modified. The only action allowed by the Registrar is the restoration of
the domain name. 

Note:
BULK TRANSFER operations are allowed within the 30-day RGP provided that such transfer is in accordance with Exhibit D to Appendix F. The gaining registrar in any
ICANN-approved bulk transfer assumes the role of the deleting registrar with regards to any name in the PendingDelete status sponsored by the losing registrar at the time of transfer. 

Note:
TRANSFER or modification requests shall not be allowed during the RGP. 

Upon
being placed in PendingDelete status, domain names will be immediately removed from the DNS, but will remain in the Whois with a notation about their availability of being restored. (See
Appendix O for further details). 

At
the conclusion of the 30-day RGP, the domain will remain on PendingDelete for an additional five days. During this time, the domain cannot be restored, modified, deleted, or
transferred. At the 

conclusion
of this five-day period, the domain will be purged from the Registry database and hence available for re-registration. 

Restore Command:  

The
implementation of the Redemption Grace Period Service involves one command. 

RESTORE
Command: Registrars may restore names by using the existing EPP Renew command. In addition, EPP extensions will be used to capture the additional required reporting information, see below. A
successful restore command will terminate the PendingDelete status, remove the deleted
status attribute from the registration and return the registered name to the same state it was in immediately prior to the delete request. 

If
the registered name is past its expiration date at the time it is restored, then, following the restore, its registration term will be extended by the minimum term of years necessary to bring it
current. The registrar will first be debited for the restoration and following for the renewal term. 

There
is no Restore Grace Period. 

Appropriate Use of the Restore Capability  

Registrars
may only RESTORE Registered Names in order to correct unintentional deletions caused by registrant, registrar, or registry mistake (or as required by operation of the UDRP or other
applicable dispute resolution policy in order to implement a court, arbitral tribunal or Administrative Panel decision). Restoring Registered Names in order to assume the rights to use or sell them
will be considered an abuse of the system and will give Registry Operator the ability to delete those impacted domain names or terminate the Registry-Registrar Agreement. 

Registrar Reporting Requirement  

In
order to facilitate verification of registrar compliance with the intended purpose of the Redemption Grace Period Service, Registrars are required to submit a "Registrar Restore Report" to the
Registry Operator. 

The
reports will be generated as set forth by the Registry Operator through the restore command (EPP extensions) and in accordance with the below: 

The
following data shall be provided by the Registry Operator: 

	•
	WHOIS
data for deleted name, as it existed prior to deletion

	•
	WHOIS
data for deleted name, as it existed at the time of report submission

	•
	Exact
date and time of deletion

	•
	Exact
date and time of restore 

The
following data shall be submitted by the registrar as part of the restore command. Failure to provide all of the following data at the time the restore command is submitted will result in a
failure to restore the domain name. 

	•
	Written
explanation and corresponding reason code as to why registered name was restored (e.g., registrant mistake, registrar mistake, registry mistake, dispute resolution,
etc.)

	•
	Written
statement affirming that Registrar has not restored the.BIZ domain name in question in order to assume the rights to use or sell the name for itself or for any third
party (unless the name was restored as required to give effect to an order or decision from a court, arbitral tribunal or Administrative Panel—in such cases a copy of the order should be
provided separately to the Registry Operator by no later than five (5) business days following the restore).

	•
	Written
statement affirming that information in report is factually accurate to the best of the Registrar's knowledge, and that the registrar acknowledges that intentionally
supplying false 

information
in the Restore Report shall constitute an incurable material breach of the Registry-Registrar Agreement and may result in the deletion of the impacted domain name(s). 

The
registry will maintain (for two years) copies of all Restore commands, as well as provide ICANN with copies of such reports. Further, the registry will include in its monthly report to ICANN the
number of Restore Reports received (see Appendix T). 

Registry Transparency Requirement—Registry Reports  

The
Registry will provide comprehensive, regularly updated lists of names with a PendingDelete status to all Registrars via an FTP or SCP mechanism; these lists will include corresponding dates of
deletion. These reports will only include names in the last five days of the PendingDelete status. 

Registry Transparency—Public Whois  

See
Appendix O. 

Registry Fees for Restoring Deleted Names  

The
maximum registry fee for restoring a deleted name is set forth in Appendix G to the Registry Agreement. The Redemption Grace Period Service
fee is separate from, and in addition to, the ordinary charges for registration term extensions. 

Comments
concerning the layout, construction and functionality of this site. should be sent to webmaster@icann.org. 

Page
Updated: 28-Jun-2003

© 2003 The Internet Corporation for Assigned Names and Numbers. All rights reserved. 

Appendix C
is divided into eleven sections: 

	C.1	Registry Overview
	

C.2	

Registry-Registrar Model and Protocol
	

C.3	

Zone File Generation, Distribution, and Publication
	

C.4	

Whois Service
	

C.5	

Customer Support Services and Capabilities
	

C.6	

Operational Test and Evaluation
	

C.7	

Registrar Reports
	

C.8	

DataBase Services
	

C.9	

Transfers
	

C.10	

Grace Period
	

C.11	

Additional Services

APPENDIX D  

 
  Performance Specifications  
  

1. Introduction. The attached Performance Specification Matrix ("Matrix") provides a list of performance specifications as they apply to the three Core
Services provided by the Registry—SRS, Nameserver, and Whois services. 

2. Definition. Capitalized terms used herein and not otherwise defined shall have the meaning ascribed to them in the Registry Agreement. 

2.1
"Core Internet Service Failure" refers to an extraordinary and identifiable event beyond the control of Registry Operator affecting the Internet services to be measured pursuant to
Section 3.6 of this Appendix D. Such events include but are not limited to congestion collapse, partitioning, power grid failures, and routing failures. 

2.2
"Core Services" refers to the three core services provided by the Registry—SRS, Nameserver, and Whois Services. 

2.3
"Performance Specification" refers to the specific committed performance service levels as specified herein. 

2.4
"Performance Specification Priority" refers to the Registry's rating system for Performance Specifications. Some Performance Specifications are more critical to the operations of the Registry than
others. Each of the Performance Specifications is rated as C1—mission critical, C2—mission important, C3—mission beneficial, or C4—mission maintenance. 

2.5
"Registrar Community" refers to all of the ICANN-Accredited Registrars who have executed Registry-Registrar Agreements with Registry Operator for the Registry TLD. 

2.6
"SRS" refers to the Shared Registration System; the service that the Registry provides to the Registrar Community. Specifically, it refers to the ability of Registrars to add, modify, and delete
information associated with domain names, nameserver, contacts, and registrar profile information. This service is provided by systems and software maintained in coactive redundant data centers. The
service is available to approved Registrars via an Internet connection. 

2.7
"Nameserver" refers to the nameserver function of the Registry and the nameservers that resolve DNS queries from Internet users. This service is performed by multiple nameserver sites that host
DNS resource records. The customers of the nameserver service are users of the Internet. The nameservers receive a DNS query, resolve it to the appropriate address, and provide a response. 

2.8
"Service Level Measurement Period" refers to the period of time for which a Performance Specification is measured. Monthly periods are based on calendar months, quarterly periods are based on
calendar quarters, and annual periods are based on calendar years. 

2.9
"Whois" refers to the Registry's Whois service. The Registry will provide contact information related to registered domain names and nameserver through a Whois service. Any person with access to
the Internet can query the Registry's Whois service directly (via the Registry website) or through a Registrar. 

3. Performance Specifications. Registry Operator shall use commercially reasonable efforts to provide Registry Services for the Registry TLD. The
Performance Specifications defined below establish the basis for the Service Level Exception Credits ("SLE Credits") provided for in Appendix E to this Registry Agreement. These Performance
Specifications also set forth Registry Operator's obligations directly to ICANN under Subsection 3.3 of the Registry Agreement. 

3.1 Service Availability. Service Availability is defined as the time, in minutes, that the Registry's Core Services are responding to its users.
Service is unavailable when a service listed in the Matrix is unavailable to all users, that is, when no user can initiate a session with or receive a response from the Registry ("Unavailability").
Service Availability is a C1 priority level. 

3.1.1 Service Availability is measured as follows: 

Service
Availability % = {[(TM—POM)—UOM] / (TM—POM)}*100 where: 

TM =
Total Minutes in the Service Level Measurement Period (#days*24 hours*60 minutes) 

POM =
Planned Outage Minutes (sum of (i) Planned Outages and (ii) Extended Planned Outages during the Service Level Measurement Period) 

UOM =
Unplanned Outage Minutes (Difference between the total number of minutes of Unavailability during the Service Level Measurement Period minus POM). 

Upon
written request, and at the sole expense of the requesting Registrar(s), Registry Operator will retain an independent third party (to be selected by Registry Operator with the consent of the
Registrar(s) to perform an independent calculation of the UOM). The frequency of this audit will be no more than once yearly during the term of the agreement between Registry Operator and the
Registrar. 

This
calculation is performed and the results reported for each calendar month for SRS and Whois availability and for each calendar year for Nameserver availability. Results will be reported to the
Registrar Community via e-mail and to ICANN according to Appendix T. 

3.1.2 Service Availability—SRS = 99.9% per calendar month. Service Availability as it applies to the SRS refers to the ability of the
SRS to respond to Registrars that access and use the SRS through the XRP protocol defined in Appendix C. SRS Unavailability will be logged with the Registry Operator as Unplanned Outage
Minutes. The committed Service Availability for SRS is 99.9% and the Service Level Measurement Period is monthly. 

3.1.3 Service Availability—Nameserver = 99.999% per calendar year. Service Availability as it applies to the Nameserver refers to the
ability of the Nameserver to resolve a DNS query from an Internet user. Nameserver Unavailability will be logged with the Registry Operator as Unplanned Outage Minutes. The committed Service
Availability for Nameserver is 99.999% and the Service Level Measurement Period is annually. 

3.1.4 Service Availability—Whois = 99.95% per calendar month. Service Availability as it applies to Whois refers to the ability of
all users to access and use the Registry's Whois service. Whois Unavailability will be logged with the Registry Operator as Unplanned Outage Minutes. The committed Service Availability for Whois is
99.95% and the Service Level Measurement Period is monthly. 

3.2 Planned Outage. High volume data centers like the Registry require downtime for regular maintenance. Allowing for regular maintenance ("Planned
Outage") ensures a high level of service for the Registry. Planned Outage Performance Specifications are a C4 priority level. 

3.2.1 Planned Outage Duration. The Planned Outage Duration defines the maximum allowable time, in hours and minutes, that the Registry Operator is
allowed to take the Registry Services out of service for regular maintenance. Planned Outages are planned in advance and the Registrar Community is provided warning ahead of time. This Performance
Specification, where applicable, has a monthly Service Level Measurement Period. The Planned Outage Duration for the Core Services is as follows: 

(i)
Planned Outage Duration—SRS = 8 hours (480 minutes) per month; 

(ii)
Planned Outage Duration—Nameserver = (no planned outages allowed); and 

(iii)
Planned Outage Duration—Whois = 8 hours (480 minutes) per month. 

3.2.2 Planned Outage Timeframe. The Planned Outage Timeframe defines the hours and days in which the Planned Outage can occur. The Planned Outage
Timeframe for the Core Services is as follows: 

(i)
Planned Outage Timeframe—SRS = 0600-1400 UTC Sunday; 

(ii)
Planned Outage Timeframe—Nameserver = (no planned outages allowed); and 

(iii)
Planned Outage Timeframe—Whois = 0600-1400 UTC Sunday. 

3.2.3 Planned Outage Notification. The Registry Operator must notify all of its Registrars of any Planned Outage. The Planned Outage Notification
Performance Specification defines the number of days prior to a Planned Outage that the Registry Operator must notify its Registrars. The Planned Outage Notification for the Core Services is as
follows: 

(i)
Planned Outage Timeframe—SRS = 3 days; 

(ii)
Planned Outage Timeframe—Nameserver = (no planned outages allowed); and 

(iii)
Planned Outage Timeframe—Whois = 3 days. 

3.3 Extended Planned Outage. In some cases such as software upgrades and platform replacements an extended maintenance timeframe is required. Extended
Planned Outages will be less frequent than regular Planned Outages but their duration will be longer. Extended Planned Outage Performance Specifications are a C4 priority level. 

3.3.1 Extended Planned Outage Duration. The Extended Planned Outage Duration defines the maximum allowable time, in hours and minutes, that the Registry
Operator is allowed to take the Registry Services out of service for extended maintenance. Extended Planned Outages are planned in advance and the Registrar Community is provided warning ahead of
time. Extended Planned Outage periods are in addition to any Planned Outages during any Service Level Measurement Period. This Performance Specification, where applicable, has a Service Level
Measurement Period based on a calendar quarter. The Extended Planned Outage Duration for the Core Services is as follows: 

(i)
Extended Planned Outage Duration—SRS = 18 hours (1080 minutes) per calendar quarter; 

(ii)
Extended Planned Outage Duration—Nameserver = (no planned outages allowed); and 

(iii)
Extended Planned Outage Duration—Whois = 18 hours (1080 minutes) per calendar quarter. 

3.3.2 Extended Planned Outage Timeframe. The Extended Planned Outage Timeframe defines the hours and days in which the Extended Planned Outage can
occur. The Extended Planned Outage Timeframe for the Core Services is as follows: 

(i)
Extended Planned Outage Timeframe—SRS = 0600 - 1400 UTC Saturday or Sunday; 

(ii)
Extended Planned Outage Timeframe—Nameserver = (no planned outages allowed); and 

(iii)
Extended Planned Outage Timeframe—Whois = 0600 - 1400 UTC Saturday or Sunday. 

3.3.3 Extended Planned Outage Notification. The Registry Operator must notify all of its Registrars of any Extended Planned Outage. The Extended Planned
Outage Notification Performance Specification defines the number of days prior to an Extended Planned Outage that the Registry Operator must notify its Registrars. The Extended Planned Outage
Notification for the Core Services is as follows: 

(i)
Extended Planned Outage Timeframe—SRS = 4 weeks; 

(ii)
Extended Planned Outage Timeframe—Nameserver =(no planned outages allowed); and 

(iii)
Extended Planned Outage Timeframe—Whois = 4 weeks. 

3.4 Processing Time. Processing Time is an important measurement of transaction-based services like the Registry. The first three Performance
Specifications, Service Availability, Planned Outages and Extended Planned Outages, measure the amount of time that the service is available to its users. Processing Time measures the quality of that
service. 

Processing
Time refers to the time that the Registry Operator receives a request and sends a response to that request. Since each of the Registry Services has a unique function the Performance
Specifications for Processing Time are unique to each of the Registry Services. For example, a Performance Specification for the Nameserver is not applicable to the SRS and Whois, etc. Processing Time
Performance Specifications are a C2 priority level. 

Processing
Time Performance Specifications have a monthly Service Level Measurement Period and will be reported on a monthly basis. The Registry Operator will log the processing time for all of the
related transactions, measured from the time it receives the request to the time that it returns a response. 

3.4.1 Processing Time—Add, Modify, Delete = 3 seconds for 95%.

(i)
Processing Time—Add, Modify, and Delete is applicable to the SRS as accessed through the XRP protocol defined in Appendix C. It measures the processing time for add, modify, and
delete transactions associated with domain names, nameservers, contacts, and registrar profile information. 

(ii)
The Performance Specification is 3 seconds for 95% of the transactions processed. That is, 95% of the transactions will take 3 seconds or less from the time the Registry Operator receives the
request to the time it provides a response. 

3.4.2 Processing Time—Query Domain = 1.5 seconds for 95%.

(i)
Processing Time—Query Domain is applicable to the SRS as accessed through the XRP protocol defined in Appendix C. It measures the processing time for an availability query of a
specific domain name. 

(ii)
The performance specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time the Registry Operator receives the query to
the time it provides a response as to the domain name's availability. 

3.4.3 Processing Time—Whois Query = 1.5 seconds for 95%.

(i)
Processing Time—Whois Query is only applicable to the Whois. It measures the processing time for a Whois Query. 

(ii)
The Performance Specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time the Whois receives a query to the time it
responds. 

3.4.4 Processing Time—Nameserver Resolution = 1.5 seconds for 95%.

(i)
Processing Time—Nameserver Resolution is only applicable to the Nameserver. It measures the processing time for a DNS query. 

(ii)
The Performance Specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time Nameserver receives the DNS query to the
time it provides a response. 

3.5 Update Frequency. There are two important elements of the Registry that are updated frequently and are used by the general public; Nameserver and
Whois. Registrars generate these 

updates
through the SRS. The SRS then updates the Nameserver and the Whois. These will be done on a batch basis. Update Frequency Performance Specifications are a C3 priority level. 

The
committed Performance Specification with regard to Update Frequency for both the Nameserver and the Whois is 15 minutes for 95% of the transactions. That is, 95% of the updates to the Nameserver
and Whois will be effectuated within 15 minutes. This is measured from the time that the registry confirms the update to the registrar to the time the update appears in the Nameserver and Whois.
Update Frequency Performance Specifications have a monthly Service Level Measurement Period and will be reported on a monthly basis. 

3.5.1 Update Frequency—Nameserver = 15 minutes for 95%.

3.5.2 Update Frequency—Whois = 15 minutes for 95%.

3.6 Cross-Network Nameserver Performance Requirements. Nameserver round-trip-time and packet loss from the Internet are
important elements
of the quality of service provided by the Registry Operator. These characteristics, however, are affected by Internet performance and therefore cannot be closely controlled by Registry Operator.
Accordingly, these requirements are not matters subject to Service Level Exceptions and credits under the Service Level Agreement (Appendix E), but they are Registry Operator obligations under
Section 3.3 of the Registry Agreement. 

The
committed Performance Specification for cross-network nameserver performance is a measured round-trip time of under 300 ms and measured packet loss of under 10%. Cross-network
nameserver performance measurements will be conducted by ICANN at times of its choosing, in the following manner: 

3.6.1
The measurements will be conducted by sending strings of DNS request packets from each of four measuring locations to each of the.biz nameservers and observing the responses from the.biz
nameservers. (These strings of requests and responses are referred to as a "CNNP Test".) The measuring locations will be four root nameserver locations (on the US East Coast, US West Coast, Asia, and
Europe). 

3.6.2
Each string of request packets will consist of 100 UDP packets at 10 second intervals requesting ns records for arbitrarily selected.biz second-level domains, preselected to ensure that the
names exist in the Registry TLD and are resolvable. The packet loss (i.e. the percentage of response packets not received) and the average round-trip time for response packets received
will be noted. 

3.6.3
To meet the packet loss and round-trip-time requirements for a particular CNNP Test, all three of the following must be true: 

3.6.3.1
The round-trip time and packet loss from each measurement location to at least one.biz nameserver must not exceed the required values. 

3.6.3.2
The round-trip time to each of 75% of the.biz nameservers from at least one of the measurement locations must not exceed the required value. 

3.6.3.3
The packet loss to each of the.biz nameservers from at least one of the measurement locations must not exceed the required value. 

3.6.4
Any failing CNNP Test result obtained during an identified Core Internet Service Failure shall not be considered. 

3.6.5
To ensure a properly diverse testing sample, ICANN will conduct the CNNP Tests at varying times (i.e. at different times of the day, as well as on different days of the week). Registry Operator
will be deemed to have failed to meet the cross-network nameserver performance requirement only if the.biz nameservers persistently fail (see Section 3.6.3 above) the CNNP Tests with no less
than three consecutive failed CNNP Tests to be considered to have persistently failed. 

3.6.6
In the event of persistent failure of the CNNP Tests, ICANN will give Registry Operator written notice of the failures (with backup data) and Registry Operator will have sixty days to cure the
failure. 

3.6.7
If, following that opportunity to cure, the.biz nameservers continue to persistently fail CNNP Tests and Registry Operator fails to resolve the problem after thirty days notice of the continuing
failures, Registry Operator will be deemed not to have met its obligations under Subsection 3.3 of the Registry Agreement. 

3.6.8
Sixty days prior to the commencement of testing under this provision, ICANN will provide Registry Operator with the opportunity to evaluate the testing tools and procedures to be used by ICANN.
In the event that Registry Operator does not approve of such tools and procedures, ICANN will work directly with Registry Operator to make necessary modifications. 

4. Responsibilities of the Parties.

4.1
Except in the case of nameserver performance measurements, Registry Operator will perform monitoring from internally located systems as a means to verify that the availability and performance
measurements in this document are being met. 

4.2
Beginning no later than 120 days post Commencement-of-Service Date, the Registry Operator will publish preliminary weekly system performance and availability
reports. Registry Operator will use best efforts to finalize these reports no later than 30 days after the preliminary reports are provided. 

4.3
The Registry Operator will provide the Whois Service as specified in Appendices C and O. 

4.4
The Registry Operator will use commercially reasonable efforts to restore the critical systems of the Core Services within 24 hours after the termination of a force majeure event and
restore full system functionality within 48 hours after the termination of a force majeure event. Outages due to a force majeure will not be considered Service Unavailability. 

5. Miscellaneous.

5.1
This Appendix is not intended to replace any term or condition in the Registry Agreement. 

5.2
Dispute Resolution will be handled pursuant to the terms of Subsection 5.9 of the Registry Agreement. 

 
 

PERFORMANCE SPECIFICATION MATRIX    
    

	 
	 	Performance

Specification Description
	 	SRS
	 	Nameserver
	 	Whois

	1	 	Service Availability	 	99.9% per calendar month	 	99.999% per calendar year	 	99.95% per calendar month
	2	 	Processing Time—Add, Modify, Delete	 	3 sec for 95%	 	NA	 	NA
	3	 	Processing Time—Query Domain	 	1.5 sec for 95%	 	NA	 	NA
	4	 	Processing Time—Whois	 	NA	 	NA	 	1.5 sec for 95%
	5	 	Processing Time—Nameserver Resolution	 	NA	 	1.5 sec for 95%	 	NA
	6	 	Update Frequency	 	NA	 	15 min for 95%	 	15 min for 95%
	7	 	Planned Outage—Duration	 	8 hrs per calendar month	 	not allowed	 	8 hrs per calendar month
	8	 	Planned Outage—Timeframe	 	0600—1400 UTC Sun	 	not allowed	 	0600—1400 UTC Sun
	9	 	Planned Outage—Notification	 	3 days	 	not allowed	 	3 days
	10	 	Extended Planned Outage—Duration	 	18 hrs per calendar quarter	 	not allowed	 	18 hrs per calendar quarter
	11	 	Extended Planned Outage—Timeframe	 	0600—1400 UTC Sat or Sun	 	not allowed	 	0600—1400 UTC Sat or Sun
	12	 	Extended Planned Outage—Notification	 	28 days	 	not allowed	 	28 days
	13	 	Cross-Network Nameserver Performance	 	NA	 	300 ms RTT and 10% packet loss	 	NA

APPENDIX E  

 
 

Service Level Agreement  
  

1.  Definitions. Capitalized terms used herein and not otherwise defined shall have the definitions ascribed to them in Appendix D to
the Registry Agreement or the Registry-Registrar Agreement. 

2.  Credits. If Registry Operator fails to meet the Performance Specifications defined in Appendix D to the Registry Agreement
("Service Level Exception" or "SLE"), Registry Operator shall pay in the aggregate to the Registrar Community a credit according to the tables provided below ("Applicable Credit"). Each Registrar
shall only be entitled to a fraction of the Applicable Credit. Such fractions of the credit specified in the tables to be paid to any individual Registrar will be calculated based upon the number of
domain names that such Registrar added to the Registry during the Service Level Measurement Period compared to the total number of domain names added to the Registry by all Registrars during the
Service Level Measurement Period in which the SLE occurred. The credit due to Registrar may be paid as an offset to registrations and other fees owed to Registry Operator by Registrar. All credits
shall be paid in U.S. Dollars. The following Credit Lookup Matrix indicates the corresponding credit table for which the credits defined in this Appendix will be levied. 

 
 

CREDIT LOOKUP MATRIX    
    

	 
	 	Performance Specification

Description
	 	SRS
	 	Nameserver
	 	Whois

	1	 	Service Availability	 	Table C1a	 	Table C1b	 	Table C1a
	2	 	Processing Time—Add, Modify, Delete	 	Table C2	 	NA	 	NA
	3	 	Processing Time—Query Domain	 	Table C2	 	NA	 	NA
	4	 	Processing Time—Whois	 	NA	 	NA	 	Table C2
	5	 	Processing Time—Nameserver Resolution	 	NA	 	Table C2	 	NA
	6	 	Update Frequency	 	NA	 	Table C3	 	Table C3
	7	 	Planned Outage—Duration	 	Table C4b	 	NA	 	Table C4b
	8	 	Planned Outage—Timeframe	 	Table C4a	 	NA	 	Table C4a
	9	 	Planned Outage—Notification	 	Table C4a	 	NA	 	Table C4a
	10	 	Extended Planned Outage—Duration	 	Table C4b	 	NA	 	Table C4b
	11	 	Extended Planned Outage—Timeframe	 	Table C4a	 	NA	 	Table C4a
	12	 	Extended Planned Outage—Notification	 	Table C4a	 	NA	 	Table C4a
	13	 	Cross-Network Nameserver Performance	 	NA	 	See note.	 	NA

Note:
The cross-network nameserver performance requirement is a subject of Registry Operator's obligations under Subsection 3.3 of the Registry Agreement but is not a subject of this Service Level
Agreement (Appendix E). 

If
one or more SLEs occurs as the direct result of a failure to meet a Performance Specification in a single credit class, Registry Operator shall be responsible only for the credit assessed for the
credit class which is the proximate cause for all directly related failures. 

The
following tables identify total Registrar Community credits due for SLEs in the four credit classes C1—C4. Notwithstanding the credit levels contained in these tables, the total
credits owed by Registry Operator under this Agreement shall not exceed $30,000 USD monthly and $360,000 USD annually. 

The
credits contained in Tables C1a-C4 represent the total credits that may be assessed in a given SLR category in one Service Level Measurement Period. 

2.1 C1 Credit Class—If availability of C1 Credit Class components or systems does not meet C1 Performance Specifications in any given
Service Level Measurement Period described in the
Performance Specification Matrix in Appendix D of the Registry Agreement, Registry Operator will credit the Registrar Community according to the tables (which amount will be credited to the
Registrar on a proportional basis as set forth above). 

 
 

Table C1a    
    

	SLE
 
	 	< 30

sec.'s
	 	30-60

sec.'s
	 	1-2

min.'s
	 	2-10

min.'s
	 	10-30

min.'s
	 	over 30

min.'s

	Monthly Credit to Registrar Community	 	$	750	 	$	1,500	 	$	2,500	 	$	3,750	 	$	5,000	 	$	6,000

C1a Availability Example: In a given measurement period, the SRS Availability is 99.87%, which equates to 52 minutes of unplanned downtime. The Registry
Operator's Performance Specification for SRS Availability is 99.9%, or 43 minutes of downtime. The Service Level Exception, therefore, is 9 minutes (52-43 minutes), the difference between
the Performance Specification and the actual measured performance. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C1a. In Table C1a, the time interval (2-10
minutes) has a corresponding credit of $3,750 USD to be paid to the Registrar Community. 

 
 

Table C1b    
    

	SLE
 
	 	< 10

min.'s
	 	10-30

min.'s
	 	30-60

min.'s
	 	1-2

hours
	 	2-4

hours
	 	over 4

hours

	Annual Credit to Registrar Community	 	$	7,500	 	$	15,000	 	$	25,000	 	$	35,000	 	$	50,000	 	$	75,000

C1b Availability Example: In a given Service Level Measurement Period, the measured Nameserver Availability is 99.990% over a twelve (12) month
period, which equates to 52 minutes of downtime. The Registry Operator's Performance Specification for Nameserver Availability is 99.999%, or 5minutes of downtime per calendar year. The Service Level
Exception, therefore, is 47 minutes (52-5 minutes), the difference between the Performance Specification and the actual measured performance. From the Credit Lookup Matrix, we see the
relevant SLA is found in Table C1b. In Table C1b, the time interval (30-60 minutes) has a corresponding credit of $25,000 USD to be paid to the Registrar Community. 

2.2 C2 Credit Class—If processing time for C2 Credit Class services does not meet C2 Service Levels in any given Service Level Measurement
Period, Registry Operator will credit the Registrar Community according to the following table (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C2    
    

	SLE
 
	 	< 2 sec.'s
	 	2-5

sec.'s
	 	5-10

sec.'s
	 	10-20

sec.'s
	 	20-30

sec.'s
	 	over 30

sec.'s

	Monthly Credit to Registrar Community	 	$	375	 	$	750	 	$	1,500	 	$	3,500	 	$	4,000	 	$	7,500

C2 Processing Example: The Performance Specification for Processing Time for Add, Modify, and Delete is 3 seconds or less for 95% of the transactions.
In a given Service Level Measurement Period 7% of the transactions are greater than 3 seconds. The 5% of those transactions with the longest processing times are not subject to the SLE calculation (3
seconds for 95%). The SLE is calculated using the average processing time for the 2% of the transactions that are subject to the SLE. If there were 1,000 transactions and they took a total of 4,000
seconds the average is 4 

seconds.
That generates an SLE of 1 second (4 seconds—3 seconds). From the Credit Lookup Matrix, we see the relevant SLA is found in Table C2. In Table C2, the SLE time interval
(< 2 seconds) has a corresponding credit of $375 USD to be paid to the Registrar Community. 

2.3 C3 Credit Class—If update frequency measurements of C3 Credit Class components or systems do not meet C3 Service Levels in any given
Service Level Measurement Period as described in the Performance Specification Matrix in Appendix D of the Registry Agreement, Registry Operator will credit the Registrar Community according to
the following tables (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C3    
    

	SLE
 
	 	< 30

sec.'s
	 	30-60

sec.'s
	 	1-2

min.'s
	 	2-10

min.'s
	 	10-30

min.'s
	 	over 30

min.'s

	Monthly Credit to Registrar Community	 	$	188	 	$	375	 	$	625	 	$	938	 	$	1,250	 	$	1,500

C3 Update Frequency Example: In a given Service Level Measurement Period, 95% of the updates to the Nameserver take 24 minutes or less to complete. The
corresponding Registry Operator's Performance Specification is 15 minutes for 95% of the updates. The SLE, therefore, is 9 minutes. From the Credit Lookup Matrix, we see the relevant SLA is found in
Table C3. The SLE time interval (2-10 minutes) has a corresponding credit of $938 USD to be paid to the Registrar Community. 

2.4 C4 Credit Class—If Registry Operator fails to comply with C4 Credit Class category Performance Specifications, Registry Operator will
credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C4a    
    

	SLE
 
	 	Any

	Monthly Credit to Registrar Community	 	$	500

C4a Planned Outage Notification Example: In each instance the Registry Operator fails to meet the Performance Specifications for Notification and
Timeframe related to Planned Outages and Extended Planned Outages, the Registry Operator is subject to the credit in Table C4a. For example, the Registry Operator informs the Registrar Community that
it will initiate a Planned Outage of the SRS on the next calendar Sunday (five (5) days advance notice). The corresponding Registry Operator's Performance Specification is 28 days
notice. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C4a. This results in a credit of $500 USD to be paid to the Registrar Community. 

 
 

Table C4b    
    

	SLE
 
	 	< 1 hour
	 	1-2 hours
	 	2-4 hours
	 	4-6 hours
	 	6-10 hours
	 	over 10 hours

	Monthly Credit to Registrar Community	 	$	300	 	$	750	 	$	1,200	 	$	2,500	 	$	3,500	 	$	4,000

C4b Planned Outage Example: In a given Service Level Measurement Period, the actual duration of a planned outage is 11 hours and 20 minutes for
the SRS. The corresponding Registry Operator's Performance Specification is 8 hours per month for the SRS. The SLE, therefore, is 3 hours and 20 minutes. From the Credit Lookup Matrix
the relevant SLA is found in Table C4b. The SLE time interval (2-4 hours) has a corresponding credit of $1,200 USD to be paid to the Registrar Community. 

3. Receipt of Credits. In order for Registrars to claim credits, the following procedure must be followed: 

3.1
Registry Operator shall perform the required measurements in order to obtain the total credits associated with the applicable Service Level Measurement Period. Such measurements and associated
documentation shall be delivered by e-mail to each of the Registrars in the Registrar Community. Such notice shall also include the total credit (if any) to be paid to the Registrar
Community as a result of any outages. 

3.2
Receipt of Credit—When the above steps have been completed, the Registry Operator shall enter in each Registrar's account balance the amount of credit (if applicable) that can be used
immediately toward registrations in the Registry. 

4.     Obligations.  

4.1
Except in the case of cross-network nameserver performance (which is not a subject of this Service Level Agreement), Registry Operator will perform monitoring from internally located systems as a
means to verify that the conditions of the SLA are being met. 

4.2
Upon written request, and at the sole expense of the requesting Registrar(s), Registry Operator will retain an independent third party to be selected by Registry Operator with the consent of the
Registrar(s). The Registrar may, under reasonable terms and conditions, audit the reconciliation records for the purposes of verifying measurements of the Performance Specifications. The frequency of
these audits will be no more than once yearly during the term of the agreement between Registry Operator and the Registrar. 

4.3
Registry Operator's obligations under this SLA (Appendix E) are waived during the first 120 days after the Commencement-of-Service Date. 

4.4
A Registrar must report each occurrence of alleged occasion of Unavailability of Core Services to the Registry Operator customer service help desk in the manner required by the Registry Operator
(i.e., e-mail, fax, telephone) in order for an occurrence to be treated as Unavailable for purposes of the SLE. 

4.5
In the event that the Core Services are Unavailable to an individual Registrar, Registry Operator will use commercially reasonable efforts to re-establish the affected Core Services
for such Registrar as soon as reasonably practicable. In the event that the Unavailability of Core Services affects all Registrars, the Registry Operator is responsible for opening a blanket trouble
ticket and immediately notifying all Registrars of the trouble ticket number and details. 

4.6
Both Registrar and the Registry Operator agree to use reasonable commercial good faith efforts to establish the cause of any alleged Core Services Unavailability. If it is mutually determined to
be a Registry Operator problem, the issue will become part of the Unplanned Outage minutes. 

4.7
Beginning no later than 120 days post Commencement-of-Service Date, the Registry Operator will publish preliminary weekly system performance and availability
reports. Registry Operator will use best efforts to finalize these reports no later than 30 days after the preliminary reports are provided. 

4.8
The Registry Operator will use commercially reasonable efforts to restore the critical systems of the Core Services within 24 hours after the termination of a force majeure event and
restore full system functionality within 48 hours after the termination of a force majeure event. Outages due to a force majeure will not be considered Service Unavailability. 

4.9
Incident trouble tickets must be opened within a commercially reasonable period of time. 

5.     Miscellaneous.  

5.1
This Service Level Agreement is independent of any rights, obligations or duties set forth in the Registry Agreement. In the event of any conflict between the terms and conditions of this
Agreement and the Registry Agreement, the Registry Agreement shall control. 

APPENDIX F  

 
 

Registry-Registrar Agreement  
  

This
Registry-Registrar Agreement (the "Agreement") is between NeuLevel, Inc., a Delaware corporation, with its principal place of business located at Loudoun Tech Center, 45980 Center Oak
Plaza, Sterling, VA 20166 ("Registry Operator"), and [Registrar's name], a [jurisdiction and type of organization], with its principal place of business
located at [Registrar's location] ("Registrar"). 

WHEREAS,
Registry Operator has entered a Registry Agreement with the Internet Corporation for Assigned Names and Numbers to operate a shared registration system, TLD nameservers, and other equipment
for the.biz top-level domain; 

WHEREAS,
multiple registrars will provide Internet domain name registration services within the.biz top-level domain; 

WHEREAS,
Registrar wishes to act as a registrar for domain names within the.biz top-level domain. 

NOW,
THEREFORE, for and in consideration of the mutual promises, benefits and covenants contained herein and for other good and valuable consideration, the receipt, adequacy and sufficiency of which
are hereby acknowledged, Registry Operator and Registrar, intending to be legally bound, hereby agree as follows: 

1.     DEFINITIONS  

1.1.  The
"APIs" are the application program interfaces by which Registrar may interact, through the XRP, with the Registry System. 

1.2.  "Confidential
Information" means all information and materials, including, without limitation, computer software, data, information, databases, protocols, reference implementation
and documentation, and functional and interface specifications, provided by the Disclosing Party to the Receiving Party under this Agreement and marked or otherwise identified as Confidential,
provided that if a communication is oral, the Disclosing Party will notify the Receiving Party in writing within 15 days of the disclosure. 

1.3.  "DNS"
means the Internet domain name system. 

1.4.  The
"Effective Date" shall be the date on which it is first executed by both parties. 

1.5.  "ICANN"
means the Internet Corporation for Assigned Names and Numbers. 

1.6.  "Personal
Data" refers to data about any identified or identifiable natural person. 

1.7.  "Registered
Name" refers to a domain name within the domain of the Registry TLD, whether consisting of two or more (e.g., john.smith.name) levels, about which Registry Operator or an
affiliate engaged in providing Registry Services maintains data in a Registry Database, arranges for such maintenance, or derives revenue from such maintenance. A name in a Registry Database may be a
Registered Name even though it does not appear in a TLD zone file (e.g., a registered but inactive name). 

1.8.  "Registered
Name Holder" means the holder of a Registered Name. 

1.9.  The
"Registrar Tool Kits" shall mean the Tool Kits set forth in Exhibit A. The Registrar Tool Kits shall be comprised of the Domain Name Application Service and the Registry
Live Tool Kits. 

1.10.  "Registry
Agreement" means the Registry Agreement between Registry Operator and ICANN dated [date of Registry Agreement] for the operation of the Registry
TLD. 

1.11.  "Registry
TLD" means the.biz TLD. 

1.12.  "Registry
Database" means a database comprised of data about one or more DNS domain names within the domain of the Registry TLD that is used to generate either DNS resource records
that are published authoritatively or responses to domain-name availability lookup requests or Whois queries, for some or all of those names. 

1.13.  "Registry
Services" means services provided as an integral part of the operation of the Registry TLD, including all subdomains in which Registered Names are registered. In
determining whether a service is integral to the operation of the Registry TLD, consideration will be given to the extent to which the Registry Operator has been materially advantaged in providing the
service by its designation as such under this Agreement. The development of technology, expertise, systems, efficient operations, reputation (including identification as Registry Operator), financial
strength, or relationships with registrars and third parties shall not be deemed an advantage arising from the designation. Registry Services include: receipt of data concerning registration of domain
names and nameservers from registrars, provision to registrars of status information relating to the Registry TLD, dissemination of TLD zone files, operation of the Registry TLD zone servers,
dissemination of contact and other information concerning domain-name and nameserver registrations in the Registry TLD. 

1.14.  The
"Registry System" means the registry system operated by Registry Operator for Registered Names in the Registry TLD. 

1.15.  "Term"
means the term of this Agreement, as set forth in Subsection 8.1. 

1.16.  "XRP"
means the extensible registry-registrar protocol used by the Registry System. 

1.17.  A
"TLD" means a top-level domain of the DNS. 

Other
terms used in this Agreement as defined terms shall have the meanings ascribed to them in the context in which they are defined. 

2.     OBLIGATIONS OF REGISTRY OPERATOR  

2.1.  Access to Registry System. Throughout the term of this Agreement, Registry Operator shall provide Registrar with access as a registrar
to the Registry System that Registry Operator operates according to its arrangements with ICANN. Nothing in this Agreement entitles Registrar to enforce any agreement between Registry Operator and
ICANN. 

2.2.  Maintenance of Registrations Sponsored by Registrar. Subject to the provisions of this Agreement, ICANN requirements, and Registry
requirements authorized by ICANN, Registry Operator shall maintain the registrations of Registered Names sponsored by Registrar in the Registry System during the term for which Registrar has paid the
fees required by Subsection 4.1. 

2.3.  Provision of Tool Kits; License.  

2.3.1.  Domain
Name Application Service Tool Kit. Until the expiration of the Domain Name Application Service (as set forth in Appendix J to the Registry Agreement), Registry
Operator shall provide to Registrar a copy of the Domain Name Application Service Tool Kit no later than five business days after the Effective Date. Such Domain Name Application Service Tool Kit
shall provide sufficient technical specifications to allow Registrar to interface with the Domain Name Application Service portion of the Registry System and employ its features that are available to
Registrars; provided that if the Effective Date occurs prior to the date that Registry Operator has made the Domain Name Application Service Tool Kit available to.biz accredited Registrars generally
("DNAS Availability Data"), and such date is prior to the expiration of the Domain Name Application Service, Registry Operator shall provide to Registrar a copy of the Domain Name Application Service
Tool Kit, no later than five (5) business days after the DNAS Availability Date. 

2.3.2.  Registry
Live Tool Kit. No later than five business days after the Effective Date, Registry Operator shall provide to Registrar a copy of the Registry Live Tool Kit, which shall 

provide
sufficient technical specifications to allow Registrar to interface with the Registry Live portion of the Registry System and employ its features that are available to Registrars; provided
that if the Effective Date occurs prior to the date that Registry Operator has made the Registry Live Tool Kit available to.biz accredited Registrars generally ("Live Availability Data"), Registry
Operator shall provide to Registrar a copy of the Registry Live Tool Kit, no later than five (5) business days after the Live Availability Date. 

2.3.3.  License.
Subject to the terms and conditions of this Agreement, Registry Operator hereby grants Registrar and Registrar accepts a non-exclusive,
non-transferable, worldwide limited license to use for the term and purposes of this Agreement the XRP, APIs and any reference client software included in the Registrar Tool Kits, as well
as updates and redesigns thereof, for providing domain name registration services in the Registry TLD only and for no other purpose. 

2.4.  Changes to System. Registry Operator may from time to time make modifications to the XRP, APIs, or other software licensed hereunder
that will revise or augment the features of the Registry System. Registry Operator will provide Registrar with at least ninety days notice prior to the implementation of any material changes to the
XRP, APIs or software licensed hereunder. 

2.5.  Engineering and Customer Service Support. Registry Operator shall provide Registrar with engineering and customer service support as
set forth in Exhibit B. 

2.6.  Handling of Personal Data. Registry Operator shall notify Registrar of the purposes for which Personal Data submitted to Registry
Operator by Registrars is collected, the intended recipients (or categories of recipients) of such Personal Data, the mechanism for access to and correction of such Personal Data, and the retention
policy of Registry Operator for such Personal Data. Registry Operator shall take reasonable steps to protect Personal Data 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. 

2.7.  ICANN Requirements. Registry Operator's obligations hereunder are subject to modification at any time as a result of ICANN-mandated
requirements and consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by
ICANN. 

3.     OBLIGATIONS OF REGISTRAR  

3.1.  Accredited Registrar. During the term of this Agreement, Registrar shall maintain in full force and effect its accreditation by ICANN
as a registrar for the Registry TLD, by either, at the sole discretion of ICANN, amending its existing ICANN Accreditation Agreement with ICANN ("Accreditation Agreement") to apply to Registry
Operator, or by signing a new Accreditation Agreement with ICANN that applies to Registry Operator. 

3.2.  Registrar Responsibility for Customer Support. Registrar shall provide (i) support to accept orders for Registered Names and
(ii) customer service (including domain name record support) and billing and technical support to Registered Name Holders. 

3.3.  Registrar's Registration Agreement. At all times while it is sponsoring the registration of any Registered Name within the Registry
System, Registrar shall have in effect an electronic or paper registration agreement with the Registered Name Holder. The initial form of Registrar's registration agreement is attached as
Exhibit C (which may contain multiple alternative forms of the registration agreement). Registrar may from time to time amend those forms of registration agreement or add alternative forms of
registration agreement, provided a copy of the amended or alternative registration agreement is furnished to the Registry Operator three business days in advance of the use of such amended
registration agreement. Registrar shall include in its registration agreement those terms required by this Agreement and other terms that are consistent with Registrar's obligations to Registry
Operator under this Agreement. 

3.4.  Indemnification Required of Registered Name Holders. In its registration agreement with each Registered Name Holder, Registrar shall
require such Registered Name Holder to indemnify, defend and hold harmless Registry Operator, and its directors, officers, employees and agents from and against any and all claims, damages,
liabilities, costs and expenses, including reasonable legal fees and expenses, arising out of or relating to the Registered Name Holder's domain name registration. The registration agreement shall
further require this indemnification obligation survive the termination or expiration of the registration agreement. 

3.5.  Data Submission Requirements. As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall
submit complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants
Registry Operator a non-exclusive, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as
otherwise required in Registry Operator's operation of the Registry TLD. 

3.6.  Security. Registrar agrees to develop and employ in its domain name registration business all necessary technology and restrictions to
ensure that its connection to the Registry System is secure. All data exchanged between Registrar's system and the Registry System shall be protected to avoid unintended disclosure of information.
Registrar agrees to employ the necessary measures to prevent its access to the Registry System granted hereunder from being used to (1) allow, enable, or otherwise support the transmission by
e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than its own existing customers; or (2) enable high volume, automated,
electronic processes that send queries or data to the systems of Registry Operator, any other registry operated under an agreement with ICANN, or any ICANN-accredited registrar, except as reasonably
necessary to register domain names or modify existing registrations. In addition, Registry Operator may require other reasonable security provisions to ensure that the Registry System is secure. 

3.7.  Resolution of Technical Problems. Registrar agrees to employ necessary employees, contractors, or agents with sufficient technical
training and experience to respond to and fix all technical problems concerning the use of the XRP and the APIs in conjunction with Registrar's systems. Registrar agrees that in the event of
significant degradation of the System or other emergency, Registry Operator may, in its sole discretion, temporarily suspend access to the System. Such temporary suspensions shall be applied in a
non-arbitrary manner and shall apply fairly to any registrar similarly situated, including affiliates of Registry Operator. 

3.8.  Time. Registrar agrees that in the event of any dispute concerning the time of the entry of a domain name registration into the
Registry Database, the time shown in the Registry records shall control. 

3.9.  Change in Registrar Sponsoring Domain Name. Registrar may assume sponsorship of a Registered Name Holder's existing domain name
registration from another registrar by following the policy set forth in Exhibit D. When transferring sponsorship of a Registered Name to or from another registrar, Registrar shall comply with
the requirements of Exhibit D. 

3.10.  Compliance with Terms and Conditions. Registrar shall comply with, and shall include in its registration agreement with each
Registered Name Holder as appropriate, all of the following: 

3.10.1.  ICANN
standards, policies, procedures, and practices for which Registry Operator has monitoring responsibility in accordance with the Registry Agreement or other arrangement with
ICANN. 

3.10.2.  Operational
standards, policies, procedures, and practices for the Registry TLD as set forth in the Registry Agreement and as established from time to time by Registry Operator in
a non-arbitrary manner and applicable to all registrars, including affiliates of Registry Operator, and consistent with ICANN's standards, policies, procedures, and practices and Registry
Operator's Registry Agreement with ICANN. Among Registry Operator's operational standards, policies, procedures, and practices are those set forth in Exhibit E. Additional or 

revised
Registry Operator operational standards, policies, procedures, and practices for the Registry TLD shall be effective upon thirty days notice by Registry Operator to Registrar. 

3.10.3  Operational
standards, policies, procedures, and practices for the IP Claim Service are set forth in Exhibit I. 

3.11.  Restrictions on Registered Names. In addition to complying with ICANN standards, policies, procedures, and practices limiting domain
names that may be registered, Registrar agrees to comply with applicable statutes and regulations limiting the domain names that may be registered. 

4.     FEES  

4.1.  Amount of Registry Operator Fees. Registrar agrees to pay Registry Operator the fees set forth in Exhibit F for initial and
renewal registrations and other services provided by Registry Operator to Registrar (collectively, "Fees"). Registry Operator reserves the right to revise the Fees prospectively upon thirty days
notice to Registrar, provided that such adjustments are consistent with Registry Operator's Registry Agreement with ICANN. As one element of the Fees, Registrar agrees to pay Registry Operator the
applicable variable fees assessed to Registry Operator by ICANN, as permitted by Subsection 3.14.5 of the Registry Agreement. 

4.2.  Payment of Registry Operator Fees. In advance of incurring Fees, Registrar shall establish a letter of credit, deposit account, or
other credit facility accepted by Registry Operator, which acceptance will not be unreasonably withheld so long as payment is assured. All Fees are due immediately upon receipt of applications for
initial and renewal registrations, or upon provision of other services provided by Registry Operator to Registrar. Payment shall be made via debit or draw down of the deposit account, letter of credit
or other credit facility. Registry Operator shall provide monthly invoices to the Registrar. 

4.3.  Non-Payment of Fees. In the event Registrar has insufficient funds deposited or available through the letter of credit or
credit facility with Registry Operator, Registry Operator may do any or all of the following: (a) stop accepting new initial or renewal registrations from Registrar; (b) delete the
domain names associated with any negative balance incurred from the Registry database; and (c) pursue any other remedy under this Agreement. 

4.4.  Parity of ICANN Support Fees. Registry Operator may pay Variable Registry-Level Fees to ICANN under Subsection 3.14.2 of its Registry
Agreement with ICANN. In consideration of Registry-Operator's payment of these fees, Registrar provides the following assurance of parity of support of ICANN among TLDs: For any period in which
(a) Registry Operator pays ICANN Variable Registry-Level Fees for the Registry TLD; (b) Registrar is not required to pay ICANN an on-going component of registrar
accreditation fees for accreditation as a registrar in the Registry TLD; (c) the Registry Operator for the.com,.net, and.org is not obligated by its Registry Agreement with ICANN to pay ICANN
Variable Registry-Level Fees; and (d) Registrar is accredited by ICANN as a registrar in the.com,.net, and.org TLDs, Registrar hereby gives its express approval of an on-going
component of its Registrar accreditation fees for.com,.net, and.org TLDs that is equivalent, on a per-name basis, to the Variable Registry-Level Fee paid by Registry Operator to ICANN with
respect to the Registry TLD. 

5.     CONFIDENTIALITY AND INTELLECTUAL PROPERTY  

5.1.  Use of Confidential Information. During the Term of this Agreement, each party (the "Disclosing Party") may be required to disclose
its Confidential Information to the other Party (the "Receiving Party"). Each party's use and disclosure of the Confidential Information of the other party shall be subject to the following terms and
conditions: 

5.1.1.  The
Receiving Party shall treat as strictly confidential, and use all reasonable efforts to preserve the secrecy and confidentiality of, all Confidential Information of the
Disclosing Party, including implementing reasonable physical security measures and operating procedures. 

5.1.2.  The
Receiving Party agrees that it will use any Confidential Information of the Disclosing Party solely for the purpose of exercising its right or performing its obligations under
this Agreement and for no other purposes whatsoever. 

5.1.3.  The
Receiving Party shall make no disclosures whatsoever of any Confidential Information of the Disclosing Party to others; provided, however, that if the Receiving Party is a
corporation, partnership, or similar entity, disclosure is permitted to the Receiving Party's officers, employees, contractors and agents who have a demonstrable need to know such Confidential
Information, provided the Receiving Party shall advise such personnel of the confidential nature of the Confidential Information and of the procedures required to maintain the confidentiality thereof,
and shall require them to acknowledge in writing that they have read, understand, and agree to be individually bound by the confidentiality terms of this Agreement. 

5.1.4.  The
Receiving Party shall not modify or remove any confidentiality legends and/or copyright notices appearing on any Confidential Information of the Disclosing Party. 

5.1.5.  The
Receiving Party agrees not to prepare any derivative works based on the Confidential Information. 

5.1.6.  Notwithstanding
the foregoing, this Subsection 5.1 imposes no obligation upon the parties with respect to information that (a) is disclosed with the Disclosing Party's prior
written approval; or (b) is or has entered the public domain through no fault of the Receiving Party; or (c) is known by the Receiving Party prior to the time of disclosure; or
(d) is independently developed by the Receiving Party without use of the Confidential Information; or (e) is made generally available by the Disclosing Party without restriction on
disclosure. 

5.1.7.  In
the event the Receiving Party is required by law, regulation or court order to disclose any of Disclosing Party's Confidential Information, Receiving Party will promptly notify
Disclosing Party in writing prior to making any such disclosure in order to facilitate Disclosing Party seeking a protective order or other appropriate remedy from the proper authority, at the
Disclosing Party's expense. Receiving Party agrees to cooperate with Disclosing Party in seeking such order or other remedy. Receiving Party further agrees that if Disclosing Party is not successful
in precluding the requesting legal body from requiring the disclosure of the Confidential Information, it will furnish only that portion of the Confidential Information which is legally required. 

5.1.8.  The
Receiving Party's duties under this Subsection 5.1 shall expire five (5) years after the information is received or earlier, upon written agreement of the parties. 

5.2.  Intellectual Property.  

5.2.1.  Subject
to Subsection 3.5, each party will continue to independently own its intellectual property, including all patents, trademarks, trade names, service marks, copyrights, trade
secrets, proprietary processes and all other forms of intellectual property. In addition, Registry Operator, or its suppliers and/or licensees, shall own all right, title and interest in and to the
XRP, APIs, Registrar Tool Kits, and any software incorporated into the Registry System, as well as all intellectual property appurtenant thereto. 

5.2.2.  Without
limiting the generality of the foregoing, no commercial use rights or any licenses under any patent, patent application, copyright, trademark, know-how, trade
secret, or any other intellectual proprietary rights are granted by the Disclosing Party to the Receiving Party by this Agreement, or by any disclosure of any Confidential Information to the Receiving
Party under this Agreement. 

6.     INDEMNITIES AND LIMITATION OF LIABILITY  

6.1.  Indemnification. Registrar, at its own expense and within thirty days after presentation of a demand by Registry Operator under this
Section, will indemnify, defend and hold harmless Registry Operator and its employees, directors, officers, representatives, agents and affiliates, against any claim, suit, action, or other proceeding
brought against Registry Operator or any affiliate of Registry Operator based on or arising from any claim or alleged claim: (i) relating to any product or service of Registrar;
(ii) relating to any agreement, including Registrar's dispute policy, with any Registered Name Holder of Registrar; or (iii) relating to Registrar's domain name registration business,
including, but not limited to, Registrar's advertising, domain name application process, systems and other processes, fees charged, billing practices and customer service; provided, however, that in
any such case: (a) Registry Operator provides Registrar with prompt notice of any such claim, and (b) upon Registrar's written request, Registry Operator will provide to Registrar all
available information and assistance reasonably necessary for Registrar to defend such claim, provided that Registrar reimburses Registry Operator for its actual and reasonable costs incurred in
connection with providing such information and assistance. Registrar will not enter into any settlement or compromise of any such indemnifiable claim without Registry Operator's prior written consent,
which consent shall not be unreasonably withheld. Registrar will pay any and all costs, damages, and expenses, including, but not limited to, reasonable attorneys' fees and costs awarded against or
otherwise incurred by Registry Operator in connection with or arising from any such indemnifiable claim, suit, action or proceeding. 

6.2.  Limitation of Liability. EXCEPT AS PROVIDED IN SUBSECTION 6.3 BELOW, IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY SPECIAL,
INDIRECT, INCIDENTAL, PUNITIVE, EXEMPLARY OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES FOR ANY VIOLATIONS OF THIS AGREEMENT. 

6.3.  Performance Credits. In the event Registry Operator fails to meet the performance specifications set forth in Exhibit G of this
Agreement, Registry Operator shall provide a credit to Registrar in an amount equal to its proportionate share of applicable performance credits set forth in Exhibit H to this Agreement. Such
performance credits shall constitute the sole and exclusive remedy available to Registrar with regard to Registry Operator's failure to meet the performance specifications. 

7.     DISPUTE RESOLUTION  

7.1.  Dispute Resolution. Disputes arising under or in connection with this Agreement, including requests for specific performance, shall be
resolved through binding arbitration conducted as provided in this Section pursuant to the rules of the International Court of Arbitration of the International Chamber of Commerce ("ICC"). The
arbitration shall be conducted in the English language and shall occur in the Commonwealth of Virginia, USA. There shall be three arbitrators: each party shall choose one arbitrator and, if the two
arbitrators are not able to agree on a third arbitrator, the third shall be chosen by the ICC. The parties shall bear the costs of the arbitration in equal shares, subject to the right of the
arbitrators to reallocate the costs in their award as provided in the ICC rules. The parties shall bear their own attorneys' fees in connection with the arbitration, and the arbitrators may not
reallocate the attorneys' fees in conjunction with their award. The arbitrators shall render their decision within ninety days of the initiation of arbitration. Any litigation brought to enforce an
arbitration award shall be brought in a Commonwealth or federal court in the eastern district of the Commonwealth of Virginia, USA; however, the parties shall also have the right to enforce a judgment
of such a court in any court of competent jurisdiction. For the purpose of aiding the arbitration and/or preserving the rights of a Party during the pendency of an arbitration, each Party shall have
the right to seek temporary or preliminary injunctive relief from the arbitration panel or a court located in the Eastern District of the Commonwealth of Virginia, USA, which shall not be a waiver of
this arbitration agreement. 

8.     TERM AND TERMINATION  

8.1.  Term of the Agreement; Revisions. The Term of this Agreement shall commence on the Effective Date and, unless earlier terminated in
accordance with the provisions of this Agreement, shall expire on the expiration of the Registry Agreement. In the event that revisions to Registry Operator's approved form of Registry-Registrar
Agreement are approved or adopted by ICANN, Registrar will either execute an amendment substituting the revised agreement in place of this Agreement or, at its option exercised within fifteen days
after receiving notice of such amendment, terminate this Agreement immediately by giving written notice to Registry Operator. In the event that Registry Operator does not receive such executed
amendment or notice of termination from Registrar within such fifteen day period, Registrar shall be deemed to have terminated this Agreement effective immediately. 

8.2.  Termination. This Agreement may be terminated as follows: 

8.2.1.  Termination
For Cause. In the event that either party materially breaches any of its obligations under this Agreement and such breach is not substantially cured within thirty
calendar days after written notice thereof is given by the other party, then the non-breaching party may, by giving written notice thereof to the other party, terminate this Agreement as
of the date specified in such notice of termination. 

8.2.2.  Termination
at Option of Registrar. Registrar may terminate this Agreement at any time by giving Registry Operator thirty days notice of termination. 

8.2.3.  Termination
Upon Loss of Registrar's Accreditation. This Agreement shall terminate in the event Registrar's accreditation by ICANN is terminated or expires without renewal. 

8.2.4.  Termination
in the Event of Termination of Registry Agreement. This Agreement shall terminate in the event that Registry Operator's Registry Agreement with ICANN is terminated or
expires without entry of a subsequent Registry Agreement with ICANN and this Agreement is not assigned under Subsection 9.1.1. 

8.2.5.  Termination
in the Event of Insolvency or Bankruptcy. Either party may terminate this Agreement if the other party is adjudged insolvent or bankrupt, or if proceedings are
instituted by or against a party seeking relief, reorganization or arrangement under any laws relating to insolvency, or seeking
any assignment for the benefit of creditors, or seeking the appointment of a receiver, liquidator or trustee of a party's property or assets or the liquidation, dissolution or winding up of a party's
business. 

8.3.  Effect of Termination. Upon the expiration or termination of this Agreement for any reason: 

8.3.1.  Registry
Operator will complete the registration of all domain names processed by Registrar prior to the effective date of such expiration or termination, provided that Registrar's
payments to Registry Operator for Fees are current and timely. 

8.3.2.  Registrar
shall immediately transfer its sponsorship of Registered Names to another ICANN-accredited registrar in compliance with any procedures established or approved by ICANN. 

8.3.3.  All
Confidential Information of the Disclosing Party in the possession of the Receiving Party shall be immediately returned to the Disclosing Party. 

8.3.4.  All
fees owing to Registry Operator shall become immediately due and payable. 

8.4.  Survival. In the event of termination of this Agreement, the following shall survive: (i) Subsections 2.6, 3.5, 5.1, 5.2, 6.1,
6.2, 7.1, 8.3.3, 8.3.4, 8.4, 9.2, 9.3.3, 9.5, 9.6, 9.8, 9.9, 9.10, 9.11 and 9.13 and (ii) the Registered Name Holder's indemnification obligation under Subsection 3.4. Neither party shall be
liable to the other for damages of any sort resulting solely from terminating this Agreement in accordance with its terms. 

9.     MISCELLANEOUS  

9.1.  Assignments.  

9.1.1.  Assignment to Successor Registry Operator. In the event the Registry Operator's Registry Agreement is terminated (and such
termination is deemed final under the Registry Agreement) or expires without entry by Registry Operator and ICANN of a subsequent registry agreement, Registry Operator's rights under this Agreement
may be assigned to a company with a subsequent registry agreement covering the Registry TLD upon ICANN's giving Registrar written notice within sixty days of the termination or expiration, provided
that the subsequent registry operator assumes the duties of Registry Operator under this Agreement. 

9.1.2.  Assignment in Connection with Assignment of Agreement with ICANN. In the event that Registry Operator's Registry Agreement with
ICANN for the Registry TLD is validly assigned, Registry Operator's rights under this Agreement shall be automatically assigned to the assignee of the Registry Agreement, provided that the assignee
assumes the duties of Registry Operator under this Agreement. In the event that Registrar's accreditation agreement with ICANN for the Registry TLD is validly assigned, Registrar's rights under this
Agreement shall be automatically assigned to the assignee of the accreditation agreement, provided that the subsequent registrar assumes the duties of Registrar under this Agreement. 

9.1.3.  Other Assignments. Except as otherwise expressly provided in this Agreement, the provisions of this Agreement shall inure to the
benefit of and be binding upon, the successors and permitted assigns of the parties. Neither party shall assign or transfer its rights or obligations under this Agreement without the prior written
consent of the other party, which shall not be unreasonably withheld. 

9.2.  Notices. Any notice or other communication required or permitted to be delivered to any party under this Agreement shall be in writing
and shall be deemed properly delivered, given and received when delivered (by hand, by registered mail, by courier or express delivery service, by e-mail or by telecopier during business
hours) to the address or telecopier number set forth beneath the name of such party below, unless party has given a notice of a change of address in writing: 

If
to Registrar: 

with
copy to: 

If
to Registry Operator: 

NeuLevel, Inc.

Loundoun Tech Center

45980 Center Oak Plaza

Sterling, VA 20166

Attn: VP of Policy and Industry Relations 

with
a copy to: 

NeuLevel, Inc.

Loundoun Tech Center

45980 Center Oak Plaza

Sterling, VA 20166

Attn: General Counsel 

9.3.  Representations and Warranties.  

9.3.1.  Registrar. Registrar represents and warrants that: (1) it is a corporation duly incorporated, validly existing and in good
standing under the law of the                        , (2) it has all requisite corporate power and authority to execute,
deliver and perform its obligations 

under
this Agreement, (3) it is, and during the Term of this Agreement will continue to be, accredited by ICANN or its successor, (4) the execution, performance and delivery of this
Agreement has been duly authorized by Registrar, (5) no further approval, authorization or consent of any governmental or regulatory authority is required to be obtained or made by Registrar in
order for it to enter into and perform its obligations under this Agreement. 

9.3.2.  Registry Operator. Registry Operator represents and warrants that: (1) it is a corporation duly incorporated, validly
existing and in good standing under the laws of the State of Delaware, (2) it has all requisite corporate power and authority to execute, deliver and perform its obligations under this
Agreement, (3) the execution, performance and delivery of this Agreement has been duly authorized by Registry Operator, and (4) no further approval, authorization or consent of any
governmental or regulatory authority is required to be obtained or made by Registry Operator in order for it to enter into and perform its obligations under this Agreement. 

9.3.3.  Disclaimer of Warranties. THE XRP, APIs, REGISTRAR TOOLKITS, REGISTRY SYSTEM AND ANY COMPONENT THEREOF ARE PROVIDED
"AS-IS" AND WITHOUT ANY WARRANTY OF ANY KIND. REGISTRY OPERATOR EXPRESSLY DISCLAIMS ALL
WARRANTIES AND/OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY OR SATISFACTORY QUALITY AND FITNESS FOR A PARTICULAR PURPOSE
AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. REGISTRY OPERATOR DOES NOT WARRANT THAT THE XRP, APIs, REGISTRAR TOOLKITS, REGISTRY SYSTEM OR ANY COMPONENT THEREOF WILL MEET REGISTRAR'S REQUIREMENTS, OR
THAT THE OPERATION OF XRP, APIs, REGISTRAR TOOLKITS, THE REGISTRY SYSTEM OR ANY COMPONENT THEREOF WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE XRP, APIs, REGISTRAR TOOLKITS,
REGISTRY SYSTEM OR ANY COMPONENT THEREOF WILL BE CORRECTED. FURTHERMORE, REGISTRY OPERATOR DOES NOT WARRANT NOR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE XRP, APIs, REGISTRAR
TOOLKITS, REGISTRY SYSTEM OR ANY COMPONENT THEREOF OR RELATED DOCUMENTATION IN TERMS OF THEIR CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. SHOULD THE XRP, APIs, REGISTRAR TOOLKITS, THE REGISTRY
SYSTEM OR ANY COMPONENT THEREOF PROVE DEFECTIVE, REGISTRAR ASSUMES THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION OF REGISTRAR'S OWN SYSTEMS AND SOFTWARE. 

9.4.  Insurance. During the Term of this Agreement, and any renewal Terms, Registrar shall have in place US $1,000,000 in comprehensive
legal liability insurance from a reputable insurance provider with an A.M. Best rating of "A" or better. Such Insurance shall be used to indemnify and hold harmless Registry Operator and its
employees, directors, officers, representatives, agents and affiliates from all costs and damages (including reasonable attorneys' fees) which it may suffer by reason of Registrar's failure to
indemnify Registry Operator as provided above. Registrar shall provide a copy of the insurance policy to Registry Operator upon Registry Operator's reasonable request. 

9.5.  Third-Party Beneficiaries. The Parties expressly agree that ICANN is an intended third-party beneficiary of this Agreement. Otherwise,
this Agreement shall not be construed to create any obligation by either party to any non-party to this Agreement, including any holder of a Registered Name. Registrar acknowledges that
nothing in this Agreement shall confer upon Registrar the status of an intended third-party beneficiary to the Registry Agreement. 

9.6.  Relationship of the Parties. Nothing in this Agreement shall be construed as creating an employer-employee or agency relationship, a
partnership or a joint venture between the parties. 

9.7.  Force Majeure. Neither party shall be liable to the other for any loss or damage resulting from any cause beyond its reasonable
control (a "Force Majeure Event") including, but not limited to, insurrection or civil disorder, war or military operations, national or local emergency, acts or omissions of government or other
competent authority, compliance with any statutory obligation or executive order, industrial disputes of any kind (whether or not involving either party's employees), fire, lightning, explosion,
flood, subsidence, weather of exceptional severity, equipment or facilities shortages which are
being experienced by providers of telecommunications services generally, or other similar force beyond such Party's reasonable control, and acts or omissions of persons for whom neither party is
responsible. Upon occurrence of a Force Majeure Event and to the extent such occurrence interferes with either party's performance of this Agreement, such party shall be excused from performance of
its obligations (other than payment obligations) during the first six months of such interference, provided that such party uses best efforts to avoid or remove such causes of nonperformance as soon
as possible. 

9.8.  Amendments. Except as otherwise provided herein, no amendment, supplement, or modification of this Agreement or any provision hereof
shall be binding unless executed in writing by both parties. 

9.9.  Waivers. No failure on the part of either party to exercise any power, right, privilege or remedy under this Agreement, and no delay
on the part of either party in exercising any power, right, privilege or remedy under this Agreement, shall operate as a waiver of such power, right, privilege or remedy; and no single or partial
exercise or waiver of any such power, right, privilege or remedy shall preclude any other or further exercise thereof or of any other power, right, privilege or remedy. Neither party shall be deemed
to have waived any claim arising out of this Agreement, or any power, right, privilege or remedy under this Agreement, unless the waiver of such claim, power, right, privilege or remedy is expressly
set forth in a written instrument duly executed and delivered on behalf of such party; and any such waiver shall not be applicable or have any effect except in the specific instance in which it is
given. 

9.10.  Attorneys' Fees. If any legal action or other legal proceeding (including arbitration) relating to the performance under this
Agreement or the enforcement of any provision of this Agreement is brought against either Party hereto, the prevailing Party shall be entitled to recover reasonable attorneys' fees, costs and
disbursements (in addition to any other relief to which the prevailing Party may be entitled). 

9.11.  Construction. The Parties agree that any rule of construction to the effect that ambiguities are to be resolved against the drafting
party shall not be applied in the construction or interpretation of this Agreement. 

9.12.  Further Assurances. Each party hereto shall execute and/or cause to be delivered to each other Party hereto such instruments and
other documents, and shall take such other actions, as such other Party may reasonably request for the purpose of carrying out or evidencing any of the transactions contemplated by this Agreement. 

9.13.  Entire Agreement. This Agreement (including its exhibits, which form a part of it) constitutes the entire agreement between
the parties concerning the subject matter of this Agreement and supersedes any prior agreements, representations, statements, negotiations, understandings, proposals or undertakings, oral or written,
with respect to the subject matter expressly set forth herein. 

9.14.  Counterparts. This Agreement may be executed in one or more counterparts, each of which shall be deemed an original, but all of which
together shall constitute one and the same instrument. 

IN
WITNESS WHEREOF, the parties hereto have executed this Agreement as of the date set forth in the first paragraph hereof. 

	NeuLevel, Inc.	 	[Registrar]
	 	 	 	 	 
	 	 	 	 	 
	By:	 	 	By:	 
	Name:	 	 	Name:	 
	Title:	 	 	Title:	 

 
 

Exhibit A
  Registrar Tool Kits    
    

Registry-Registrar
Software Development Kit includes: 

1.     Software Development Kit for Domain Name Application Service  

	•
	Secure
ftp client

	•
	Reference
client implementation:

	•
	TCL

	•
	Interface
definition:

	•
	ABNF

	•
	XML
schema

	•
	Registry
Operational Profile (our extensions)

	•
	Authentication
and Encryption guidelines 

2.     Software Development Kit for Registry Live  

	•
	Reference
client implementations:

	•
	Java

	•
	Language
bindings

	•
	Interface
Definition Language (IDL)

	•
	Interface
definition:

	•
	ABNF

	•
	XML
schema

	•
	Registry
Operational Profile (our extensions)

	•
	Authentication
and Encryption guidelines

	•
	Epp
"feature freeze" drafts

	•
	Epp
test plan and coverage matrix

	•
	Java,
API documentation 

 
 

Exhibit B
  Engineering and Customer Service Support    
    

During
the Term of this Agreement, Registry Operator will provide reasonable telephone and electronic customer support to Registrar, not Registered Name holders or prospective customers of Registrar,
for non-technical issues solely relating to the Registry System and its operation. Registry Operator will provide Registrar with a telephone number and e-mail address for such
support during implementation of the XRP, APIs and Software. While e-mail and FAQs are the primary method of help, Registry Operator will provide support on a
7-day/24-hour basis. Registry Operator will provide a web-based customer service capability in the future and such web-based support will become the
primary method of customer service support to Registrar at such time. 

The
Registry Operator provides a clear, concise and efficient deliberation of customer support responsibilities. Registrars provide support to registrants and registries provide support for
Registrars. This allows the Registry to focus its support on the highly technical and administratively complex issues that arise between the Registry and the Registrar. 

Technical Help Systems  

NeuLevel
will provide the Registrars with the following types of technical support: 

	•
	Web-based
self-help services, including:

	•
	Knowledge
bases

	•
	Frequently
asked questions

	•
	White
papers

	•
	Downloads
of XRP client software

	•
	Support
for email messaging

	•
	Telephone
support from our central Help Desk

	•
	Fee-based
consulting services. 

Web Portal  

Registry
Operator will implement a secure Web-based multimedia portal to help support registrar operations. To obtain access to our Web-based services, a registrar must
register his registrants with us, and must have implemented our security features, including SSL encryption, log in with user ID and password, and digital certificates for authentication. The home
page of the web portal will include a notice to registrars of planned outages for database maintenance or installation of software upgrades. This notification will be posted 30 days prior to
the event in addition to active notification including phone calls and email. We will also record outage notifications in the help desk database to facilitate compliance with the service-level
agreement. Finally, seven days and again two days prior to the scheduled event, we will use both an email and a Web-based notification to remind registrars of the outage. 

Non-affiliated
registrars and the general Internet community may obtain generic information from NeuLevel's public Web site, which will describe our TLD service offerings and list
ICANN-certified registrars providing domain-name services. 

Central Help Desk  

In
addition to implementing the Web site, we will provide telephone support to our registrars through our central Help Desk. Access to the help desk telephone support is through an automatic call
distributor that routes each call to the next available customer support specialist. We will authenticate callers by using caller ID and by requesting a pre-established pass phrase that is
different for each registrar. Requests for assistance may also come to the Help Desk via email, either directly or via the secure Web site. The Help Desk's three tiers of support are: 

Tier-1
Support. Telephone support to registrars who normally are calling for help with customer domain-name problems and such other issues such as XRP implementation or billing
and collection. Problems that can't be resolved at Tier 1 are escalated to Tier 2. 

Tier-2
Support. Support provided by members of the technical support team, who are functional experts in all aspects of domain-name registration. In addition to resolving
escalated Tier 1 problems with XRP implementation and billing and collection, Tier 2 staff provides technical support in system tuning and workload processing. 

Tier
3 Support. Complex problem resolution provided by on-site maintenance technicians, third party systems and software experts, and vendors, depending on the nature of the problem. 

In
turn, the Help Desk uses an automated software package to collect call statistics and record service requests and trouble tickets in a help desk database. The help desk database documents the
status of requests and tickets, and notifies the Help Desk when an SLA threshold is close to being breached. Each customer-support and technical support specialist uses our problem management process
to respond to trouble tickets with a troubleshooting, diagnosis, and resolution procedure and a root-cause analysis. 

Escalation Policy  

Our
escalation policy defines procedures and timelines for elevating problems either to functional experts or to management for resolution if they not resolved within the escalation-policy time
limits. The following table is an overview of our escalation policy. 

	Level
	 	Description
	 	Escalation Policy
	 	Notification

	I	 	Catastrophic outage affecting overall registry operations	 	Data-center manager escalates to NeuLevel management and Disaster-Recovery Team if not resolved in 15 minutes	 	Web portal and e-mail notifications to all Registrars within 15 minutes; updates every 30 minutes
	

II	
 	

Systems outage affecting one or two registrar sessions but not the entire system	
 	

Systems engineer escalates to data-center manager if not resolved in one hour	
 	

Web-portal notification to all registrars; hourly updates
	

III	
 	

Technical questions	
 	

Help Desk customer-support specialist escalates to the systems engineer if not resolved in two hours	
 	

Hourly updates to registrar via e-mail
	

IV	
 	

Basic questions	
 	

Help Desk customer-support specialist escalates to the systems engineer if not resolved within four hours	
 	

Hourly updates to registrar via e-mail

Staffing  

Initially,
Registry Operator will staff its Help Desk with a complement of customer service specialists. We will add staff as necessary to respond to incoming requests within the service-level
agreement.
Customer-service specialists will obtain assistance from Registry Operator's technical staff for any problems that cannot be resolved in one phone call. 

Test and Evaluation Facility  

Registry
Operator will establish an operational test-and-evaluation facility that will be available for Registrars to test their client XRP system. Our technical-support team,
which consists of functional experts in the processes and technologies for domain-name registration, will support the registrars' testing. 

Once
each new Registrar is satisfied that its system is compatible with the registry system, it will schedule a formal acceptance test that will be monitored by our system engineer. After a
registrar has passed the acceptance test, we will issue its user id, passwords, and digital certificates, and the Registrar can begin operations. 

Customer Satisfaction Survey  

To
determine Registrars' satisfaction with Registry Services, Registry Operator will implement a Web-based customer-satisfaction survey that will consist of a set of survey questions with
responses ranging from one to five on the Likert Scale. We will tabulate the results and publish them on the Web site. 

To
further verify the quality of our customer services, Registry Operator will commission a biannual customer-satisfaction survey by an independent third party. 

 
 

Exhibit C
  Registrar's Registration Agreement
  [To be supplied by Registrar]    

 
 

Exhibit D
  Policy on Transfer of Sponsorship of
  Registrations Between Registrars    
    

A. Holder-Authorized Transfers.  

Registrar Requirements.  

The
registration agreement between each Registrar and its Registered Name Holder shall include a provision explaining that a Registered Name Holder will be prohibited from changing its Registrar
during the first 60 days after initial registration of the domain name with the Registrar. Beginning on the 61st day after the initial registration with the Registrar, the procedures for change
in sponsoring registrar set forth in this policy shall apply. Enforcement shall be the responsibility of the Registrar sponsoring the domain name registration. 

For
each instance where a Registered Name Holder wants to change its Registrar for an existing domain name (i.e., a domain name that appears in a particular top-level domain zone file),
the gaining Registrar shall: 

1)  Obtain
express authorization from an individual who has the apparent authority to legally bind the Registered Name Holder (as reflected in the database of the losing Registrar). 

a)  The
form of the authorization is at the discretion of each gaining Registrar. 

b)  The
gaining Registrar shall retain a record of reliable evidence of the authorization. 

2)  In
those instances when the Registrar of record is being changed simultaneously with a transfer of a domain name from one party to another, the gaining Registrar shall also obtain
appropriate authorization for the transfer. Such authorization shall include, but not be limited to, one of the following: 

a)  A
bilateral agreement between the parties. 

b)  The
final determination of a binding dispute resolution body. 

c)  A
court order. 

3)  Request,
by the transmission of a "transfer" command as specified in the XRP, that the Registry database be changed to reflect the new Registrar. 

a)  Transmission
of a "transfer" command constitutes a representation on the part of the gaining Registrar that: 

(1)  the
requisite authorization has been obtained from the Registered Name Holder listed in the database of the losing Registrar, and 

(2)  the
losing Registrar will be provided with a copy of the authorization if and when requested. 

In
those instances when the Registrar of record denies the requested change of Registrar, the Registrar of record shall notify the prospective gaining Registrar that the request was denied and the
reason for the denial. 

Instances
when the requested change of sponsoring Registrar may be denied include, but are not limited to: 

1)  Situations
described in the Domain Name Dispute Resolution Policy 

2)  A
pending bankruptcy of the Registered Name Holder 

3)  Dispute
over the identity of the Registered Name Holder 

4)  Request
to transfer sponsorship occurs within the first 60 days after the initial registration with the Registrar 

In
all cases, the losing Registrar shall respond to the electronic notice regarding the "transfer" request within five (5) days. Failure to respond will result in a default "approval" of the
"transfer." 

Registry Requirements.  

Upon
receipt of the "transfer" command from the gaining Registrar, Registry Operator will transmit an electronic notification to both Registrars. 

Registry
Operator shall complete the "transfer" if either: 

1)  the
losing Registrar expressly "approves" the request, or 

2)  Registry
Operator does not receive a response from the losing Registrar within five (5) days. 

When
the Registry's database has been updated to reflect the change to the gaining Registrar, Registry Operator will transmit an electronic notification to both Registrars. 

Records of Registration.  

Each
Registered Name Holder shall maintain its own records appropriate to document and prove the initial domain name registration date, regardless of the number of Registrars with which the Registered
Name Holder enters into a contract for registration services. 

Effect
on Term of Registration. 

The
completion by Registry Operator of a holder-authorized transfer under this Part A shall result in a one-year extension of the existing registration, provided that in no event
shall the total unexpired term of a registration exceed ten (10) years. 

B.    ICANN-Approved Transfers.  

Transfer
of the sponsorship of all the registrations sponsored by one registrar as the result of acquisition of that Registrar or its assets by another Registrar may be made according to the following
procedure: 

(a)  The
gaining Registrar must be accredited by ICANN for the Registry TLD and must have in effect a Registry-Registrar Agreement with Registry Operator for the Registry TLD. 

(b)  ICANN
must certify in writing to Registry Operator that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual or
imminent business failure of a Registrar. 

Upon
satisfaction of these two conditions, Registry Operator will make the necessary one-time changes in the registry database for no charge, for transfers involving 50,000 name
registrations or fewer; provided that the data to be transferred to Registry Operator is in the form specified by Registry Operator as may be reasonably approved by ICANN ("Approved Format"). If the
transfer involves registrations of more than 50,000 names, and the data to be transferred to Registry Operator is in the Approved Format, Registry Operator will charge the gaining registrar a
one-time flat fee of US$ 50,000. If the data to be transferred is not in the Approved Format, the Registry Operator may charge a reasonable fee in connection with the costs associated with
reformatting such data. 

 
 

Exhibit E
  Registry Operator's Operational Standards, Policies, Procedures and Practices    
    

I.     Registration Requirements  

Before
the Registry Operator will accept applications for registration from Registrar, all domain name applicants in the.biz TLD ("Applicants") must: 

1.  Enter
into an electronic or paper registration agreement with the Registrar ("Registrar"), in accordance with the ICANN Registrar Accreditation Agreement ("Accreditation Agreement")
and this Agreement. Such electronic or paper registration agreement shall include, at a minimum, the following certifications: 

a)  The
data provided in the domain name registration application is true, correct, up to date and complete; and 

b)  The
registrant will keep the information provided above up to date. 

2.  Certify
in the Registration Agreement that to the best of its knowledge: 

a)  The
registered domain name will be used primarily for bona fide business or commercial purposes and not (i) exclusively for personal use; or (ii) solely for the purposes
of (1) selling, trading or leasing the domain name for compensation, or (2) the unsolicited offering to sell, trade or lease the domain name for compensation. 

b)  The
domain name registrant has the authority to enter into the registration agreement; and 

c)  The
registered domain name is reasonably related to the registrant's business or intended commercial purpose at the time of registration. 

II.    Incorporation of.Biz Dispute Resolution Services  

In
addition, Registrar agrees to incorporate the following text (or translation of such text into relevant language) into their Registration Agreement: 

"The
Registrant acknowledges having read and understood and agrees to be bound by the terms and conditions of the following documents, as they may be amended from time to time, which are hereby
incorporated and made an integral part of this Agreement: 

(i)  The
Uniform Domain Name Dispute Resolution Policy, available at <URL>; 

(ii)  The
Start-up Dispute Resolution Policy ("SUDRP"), available at <URL>; and 

(iii)  The
Restrictions Dispute Resolution Criteria and Rules, available at <URL>." 

The
SUDRP sets forth the terms and conditions in connection with a dispute between a registrant of a.biz domain name ("Registrant") with any third party (other than Registry Operator or Registrar)
over the registration or use of a.biz domain name registered by Registrant that is subject to the Start-up Intellectual Property Notification Service ("SIPNS"). SIPNS is a service
introduced by Registry Operator to notify a trademark or service mark holder ("Claimant") that a second-level domain name has been registered in which that Claimant claims intellectual property
rights. In accordance with the SUDRP and its associated Rules, those Claimants will have the right to challenge registrations through independent ICANN-accredited dispute resolution providers. 

The
UDRP sets forth the terms and conditions in connection with a dispute between a Registrant and any party other than the Registry Operator or Registrar over the registration and use of an Internet
domain name registered by Registrant. 

The
RDRP sets forth the terms under which any allegation that a domain name is not used primarily for business or commercial purposes shall be enforced on a case-by-case, fact
specific basis by an independent ICANN-accredited dispute provider. None of the violations of the Restrictions will be enforced directly by or through Registry Operator. Registry Operator will not
review, monitor, or otherwise verify that any particular domain name is being used primarily for business or commercial purposes or that a domain name is being used in compliance with the SUDRP or
UDRP processes. 

III.  Reservation  

        Registry Operator reserves the right to deny, cancel or transfer any registration 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, in compliance with any dispute resolution process;
(3) to avoid any liability, civil or criminal, on the part of Registry Operator, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) for violations of this
Agreement and its Exhibits; or (5) to correct mistakes made by Registry Operator or any Registrar in connection with a domain name registration. Registry Operator also reserves the right to
freeze a domain name during resolution of a dispute. 

 
 

Exhibit F
  Registration Fees    
    

	•
	Domain
Name Application Fees (Phase 1). Registrar agrees to pay the non-refundable amounts as set forth below: 

US
$2.00 Per Domain Name Application Submission 

	•
	Initial
Registration. Registrar agrees to pay the non-refundable amounts as set forth below: 

	Initial Registration Fee

(Per Domain Name)
	 	Volume Range

(Number of Registered Names)

	US $5.30	 	0 to 4,999,999
	US $5.00	 	5,000,000 to 9,999,999
	US $4.75	 	10,000,000 +

	•
	Renewal
Fees. Registrar agrees to pay the non-refundable amounts as set forth below: 

	Renewal Fee

(Per Domain Name)
	 	Volume Range

(Number of Registered Names)

	US $5.30	 	0 to 4,999,999
	US $5.00	 	5,000,000 to 9,999,999
	US $4.75	 	10,000,000 +

	•
	Secure
Domain Name Registration Service. Registrar agrees to pay the non-refundable amounts as set forth below: 

US
$500.00 Per Secure Domain Name Registration 

	•
	Fees
for Transfers of Sponsorship of Domain-Name Registrations 

Where
the sponsorship of a domain name is transferred from an ICANN-Accredited Registrar to another ICANN-Accredited Registrar, other than an ICANN approved bulk transfer, Registry Operator may
require the registrar receiving the sponsorship to request a renewal of one year for the name. In connection with that extension, Registry Operator may charge a Renewal Fee for the requested extension
as provided in the renewal schedule set forth above. The transfer shall result in an extension according to the renewal request, subject to a ten-year maximum on the future term of any
domain-name registration. The Renewal Fee shall be paid in full at the time of the transfer by the ICANN-Accredited Registrar receiving sponsorship of the domain name. 

For
a bulk transfer approved by ICANN under Part B of Exhibit D to the Registry-Registrar Agreement, Registry Operator will charge the gaining registrar US $0 (for transfers of 50,000
names or fewer) or US$50,000 (for transfers of more than 50,000 names). 

	•
	Enhanced
Whois Service. Registrar agrees to pay the non-refundable amounts as set forth below: 

To
be provided with at least 30 days advance notice: Yearly Subscription Fee Rate, One time Usage Fee 

Registry
Operator reserves the right to revise the Fees prospectively upon thirty days notice to Registrar, provided that such adjustments are consistent with Registry Operator's Registry Agreement
with ICANN. 

 
 

Exhibit G
  Performance Specifications    
    

1.  Introduction. The attached Performance Specification Matrix ("Matrix") provides a list of performance specifications as they apply to
the three Core Services provided by the Registry—SRS, Nameserver, and Whois services. 

2.  Definitions. Capitalized terms used herein and not otherwise defined shall have the meaning ascribed to them in the Registry-Registrar
Agreement. 

2.1  "Core
Services" refers to the three core services provided by the Registry—SRS, Nameserver, and Whois Services. 

2.2  "Performance
Specification" refers to the specific committed performance service levels as specified herein. 

2.3  "Performance
Specification Priority" refers to the Registry's rating system for Performance Specifications. Some Performance Specifications are more critical to the operations of the
Registry than
others. Each of the Performance Specifications is rated as C1-mission critical, C2-mission important, C3-mission beneficial, or C4-mission maintenance. 

2.4  "Registrar
Community" refers to all the ICANN-Accredited Registrars accredited by ICANN who have executed Registry-Registrar Agreements with Registry Operator for the Registry TLD. 

2.5  "SRS"
refers to the Shared Registration System; the service that the Registry provides to the Registrar Community. Specifically, it refers to the ability of Registrars to add, modify,
and delete information associated with domain names, nameserver, contacts, and registrar profile information. This service is provided by systems and software maintained in coactive redundant data
centers. The service is available to approved Registrars via an Internet connection. 

2.6  "Nameserver"
refers to the nameserver function of the Registry and the nameservers that resolve DNS queries from Internet users. This service is performed by multiple nameserver sites
that host DNS resource records. The customers of the nameserver service are users of the Internet. The nameservers receive a DNS query, resolve it to the appropriate address, and provide a response. 

2.7  "Service
Level Measurement Period" refers to the period of time for which a Performance Specification is measured. Monthly periods are based on calendar months, quarterly periods are
based on calendar quarters, and annual periods are based on calendar years. 

2.8  "Whois"
refers to the Registry's Whois service. The Registry will provide contact information related to registered domain names and nameserver through a Whois service. Any person
with access to the Internet can query the Registry's Whois service directly (via the Registry website) or through a Registrar. 

3.  Performance Specifications. Registry Operator shall use commercially reasonable efforts to provide Registry Services for the Registry
TLD. The Performance Specifications defined below establish the basis for the Service Level Exception Credits ("SLE Credits") provided for in Exhibit H to this Registry-Registrar Agreement. 

3.1  Service Availability. Service Availability is defined as the time, in minutes, that the Registry's Core Services are responding to its
users. Service is unavailable when a service listed in the Matrix is unavailable to all users, that is, when no user can initiate a session with or receive a response from the Registry
("Unavailability"). Service Availability is a C1 priority level. 

3.1.1  Service Availability is measured as follows: 

Service
Availability % = {[(TM—POM)—UOM] / (TM—POM)}*100 where: 

TM =
Total Minutes in the Service Level Measurement Period (#days*24 hours*60 minutes). 

POM =
Planned Outage Minutes (sum of (i) Planned Outages and (ii) Extended Planned Outages during the Service Level Measurement Period). 

UOM =
Unplanned Outage Minutes (Difference between the total number of minutes of Unavailability during the Service Level Measurement Period minus POM). 

Upon
written request, and at the sole expense of the requesting Registrar(s), Registry Operator will retain an independent third party (to be selected by Registry Operator with the consent of the
Registrar(s) to perform an independent calculation of the UOM). The frequency of this audit will be no more than once yearly during the term of the agreement between Registry Operator and the
Registrar. 

This
calculation is performed and the results reported for each calendar month for SRS and Whois availability and for each calendar year for Nameserver availability. Results will be reported to the
Registrar Community via e-mail. 

3.1.2  Service Availability—SRS = 99.9% per calendar month. Service
Availability as it applies to the SRS refers to the ability of the SRS to respond to Registrars that access and use the SRS through the XRP protocol defined in Appendix C of the Registry
Agreement. SRS Unavailability will be logged with the Registry Operator as Unplanned Outage Minutes. The committed Service Availability for SRS is 99.9% and the Service Level Measurement Period is
monthly. 

3.1.3  Service Availability—Nameserver = 99.999% per calendar year.
Service Availability as it applies to the Nameserver refers to the ability of the Nameserver to resolve a DNS query from an Internet user. Nameserver Unavailability will be logged with the Registry
Operator as Unplanned
Outage Minutes. The committed Service Availability for Nameserver is 99.999% and the Service Level Measurement Period is annually. 

3.1.4  Service Availability—Whois = 99.95% per calendar month. Service
Availability as it applies to Whois refers to the ability of all users to access and use the Registry's Whois service. Whois Unavailability will be logged with the Registry Operator as Unplanned
Outage Minutes. The committed Service Availability for Whois is 99.95% and the Service Level Measurement Period is monthly. 

3.2  Planned Outage. High volume data centers like the Registry require downtime for regular maintenance. Allowing for regular maintenance
("Planned Outage") ensures a high level of service for the Registry. Planned Outage Performance Specifications are a C4 priority level. 

3.2.1  Planned Outage Duration. The Planned Outage Duration defines the maximum allowable time, in hours and minutes, that the Registry
Operator is allowed to take the Registry Services out of service for regular maintenance. Planned Outages are planned in advance and the Registrar Community is provided warning ahead of time. This
Performance Specification, where applicable, has a monthly Service Level Measurement Period. The Planned Outage Duration for the Core Services is as follows: 

3.2.1.1  Planned
Outage Duration—SRS = 8 hours (480 minutes) per month; 

3.2.1.2  Planned
Outage Duration—Nameserver = (no planned outages allowed); and 

3.2.1.3  Planned
Outage Duration—Whois = 8 hours (480 minutes) per month. 

3.2.2  Planned Outage Timeframe. The Planned Outage Timeframe defines the hours and days in which the Planned Outage can occur. The Planned
Outage Timeframe for the Core Services is as follows: 

3.2.2.1  Planned
Outage Timeframe—SRS = 0600-1400 UTC Sunday; 

3.2.2.2  Planned
Outage Timeframe—Nameserver =(no planned outages allowed); and 

3.2.2.3  Planned
Outage Timeframe—Whois = 0600-1400 UTC Sunday. 

3.2.3  Planned Outage Notification. The Registry Operator must notify all of its Registrars of any Planned Outage. The Planned Outage
Notification Performance Specification defines the number of days prior to a Planned Outage that the Registry Operator must notify its Registrars. The Planned Outage Notification for the Core Services
is as follows: 

3.2.3.1  Planned
Outage Timeframe—SRS = 3 days; 

3.2.3.2  Planned
Outage Timeframe—Nameserver =(no planned outages allowed); and 

3.2.3.3  Planned
Outage Timeframe—Whois = 3 days. 

3.3  Extended Planned Outage. In some cases such as software upgrades and platform replacements an extended maintenance timeframe is
required. Extended Planned Outages will be less frequent than regular Planned Outages but their duration will be longer. Extended Planned Outage Performance Specifications are a C4 priority level. 

3.3.1  Extended Planned Outage Duration. The Extended Planned Outage Duration defines the maximum allowable time, in hours and minutes, that
the Registry is allowed to take the Registry Services out of service for extended maintenance. Extended Planned Outages are planned in advance and the Registrar Community is provided warning ahead of
time. Extended Planned Outage periods are in addition to any Planned Outages during any Service Level Measurement Period. This Performance Specification, where applicable, has a Service Level
Measurement Period based on a calendar quarter. The Extended Planned Outage Duration for the Core Services is as follows: 

3.3.1.1  Extended
Planned Outage Duration—SRS = 18 hours (1080 minutes) per calendar quarter; 

3.3.1.2  Extended
Planned Outage Duration—Nameserver =(no planned outages allowed); and 

3.3.1.3  Extended
Planned Outage Duration—Whois = 18 hours (1080 minutes) per calendar quarter. 

3.3.2  Extended Planned Outage Timeframe. The Extended Planned Outage Timeframe defines the hours and days in which the Extended Planned
Outage can occur. The Extended Planned Outage Timeframe for the Core Services is as follows: 

3.3.2.1  Extended
Planned Outage Timeframe—SRS = 0600-1400 UTC Saturday or Sunday; 

3.3.2.2  Extended
Planned Outage Timeframe—Nameserver =(no planned outages allowed); and 

3.3.2.3  Extended
Planned Outage Timeframe—Whois = 0600-1400 UTC Saturday or Sunday. 

3.3.3  Extended Planned Outage Notification. The Registry must notify all of its Registrars of any Extended Planned Outage. The Extended
Planned Outage Notification Performance Specification defines the number of days prior to an Extended Planned Outage that the Registry Operator must notify its Registrars. The Extended Planned Outage
Notification for the Core Services is as follows: 

3.3.3.1  Extended
Planned Outage Timeframe—SRS = 4 weeks; 

3.3.3.2  Extended
Planned Outage Timeframe—Nameserver =(no planned outages allowed); and 

3.3.3.3  Extended
Planned Outage Timeframe—Whois = 4 weeks. 

3.4  Processing Time. Processing Time is an important measurement of transaction-based services like the Registry. The first three
Performance Specifications, Service Availability, Planned Outages and Extended Planned Outages, measure the amount of time that the service is available to its users. Processing Time measures the
quality of that service. 

Processing
Time refers to the time that the Registry Operator receives a request and sends a response to that request. Since each of the Registry Services has a unique function the Performance
Specifications for Processing Time are unique to each of the Registry Services. For example, a Performance Specification for the Nameserver is not applicable to the SRS and Whois, etc. Processing Time
Performance Specifications are a C2 priority level. 

Processing
Time Performance Specifications have a monthly Service Level Measurement Period and will be reported on a monthly basis. The Registry Operator will log the processing time for all of the
related transactions, measured from the time it receives the request to the time that it returns a response. 

3.4.1  Processing Time—Add, Modify, Delete = 3 seconds for 95% 

3.4.1.1  Processing
Time—Add, Modify, and Delete is applicable to the SRS as accessed through the XRP protocol defined in Appendix C of the Registry Agreement. It
measures the
processing time for add, modify, and delete transactions associated with domain names, nameserver, contacts, and registrar profile information. 

3.4.1.2  The
Performance Specification is 3 seconds for 95% of the transactions processed. That is, 95% of the transactions will take 3 seconds or less from the time the Registry Operator
receives the request to the time it provides a response. 

3.4.2  Processing Time—Query Domain = 1.5 seconds for 95% 

3.4.2.1  Processing
Time—Query Domain is applicable to the SRS as accessed through the XRP protocol defined in Appendix C of the Registry Agreement. It measures the
processing time for an availability query of a specific domain name. 

3.4.2.2  The
performance specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time the Registry Operator
receives the query to the time it provides a response as to the domain name's availability. 

3.4.3  Processing Time—Whois Query = 1.5 seconds for 95% 

3.4.3.1  Processing
Time—Whois Query is only applicable to the Whois. It measures the processing time for a Whois Query. 

3.4.3.2  The
Performance Specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time the Whois receives a query
to the time it responds. 

3.4.4  Processing Time—Nameserver Resolution = 1.5 seconds for 95% 

3.4.4.1  Processing
Time—Nameserver Resolution is only applicable to the Nameserver. It measures the processing time for a DNS query. 

3.4.4.2  The
Performance Specification is 1.5 seconds for 95% of the transactions. That is, 95% of the transactions will take 1.5 seconds or less from the time Nameserver receives the DNS
query to the time it provides a response. 

3.5  Update Frequency. There are two important elements of the Registry that are updated frequently and are used by the general public;
Nameserver and Whois. Registrars generate these updates through the SRS. The SRS then updates the Nameserver and the Whois. These will be done on a batch basis. Update Frequency Performance
Specifications are a C3 priority level. 

The
committed Performance Specification with regard to Update Frequency for both the Nameserver and the Whois is 15 minutes for 95% of the transactions. That is, 95% of the updates to the Nameserver
and Whois will be effectuated within 15 minutes. This is measured from the time that the registry confirms the update to the registrar to the time the update appears in the Nameserver and Whois.
Update Frequency Performance Specifications have a monthly Service Level Measurement Period and will be reported on a monthly basis. 

3.5.1  Update Frequency—Nameserver = 15 minutes for 95%. 

3.5.2  Update Frequency—Whois = 15 minutes for 95%. 

	 
	 	Performance

Specification

Description
	 	SRS
	 	Nameserver
	 	Whois

	1	 	Service Availability	 	99.9% per calendar month	 	99.999% per calendar year	 	99.95% per calendar month
	2	 	Processing Time—Add, Modify, Delete	 	3 sec for 95%	 	NA	 	NA
	3	 	Processing Time—Query Domain	 	1.5 sec for 95%	 	NA	 	NA
	4	 	Processing Time—Whois	 	NA	 	NA	 	1.5 sec for 95%
	5	 	Processing Time—Nameserver Resolution	 	NA	 	1.5 sec for 95%	 	NA
	6	 	Update Frequency	 	NA	 	15 min for 95%	 	15 min for 95%
	7	 	Planned Outage—Duration	 	8 hrs per calendar month	 	not allowed	 	8 hrs per calendar month
	8	 	Planned Outage—Timeframe	 	0600—1400 UTC Sun	 	not allowed	 	0600—1400 UTC Sun
	9	 	Planned Outage—Notification	 	3 days	 	not allowed	 	3 days
	10	 	Extended Planned Outage—Duration	 	18 hrs per calendar quarter	 	not allowed	 	18 hrs per calendar quarter
	11	 	Extended Planned Outage—Timeframe	 	0600—1400 UTC Sat or Sun	 	not allowed	 	0600—1400 UTC Sat or Sun
	12	 	Extended Planned Outage—Notification	 	28 days	 	not allowed	 	28 days

 
 

Exhibit H
  Service Level Agreement    
    

1.  Definitions. Capitalized terms used herein and not otherwise defined shall have the definitions ascribed to them in Exhibit G to
the Registry-Registrar Agreement. 

2.  Credits. If Registry Operator fails to meet the Performance Specifications defined in Exhibit G ("Service Level Exception" or
"SLE"), Registry Operator shall pay in the aggregate to the Registrar Community a credit according to the tables provided below ("Applicable Credit"). Each Registrar shall only be entitled to a
fraction of the Applicable Credit. Such fractions of the credit specified in the tables to be paid to any individual Registrar will be calculated based upon the number of domain names that such
Registrar added to the Registry during the Service Level Measurement Period compared to the total number of domain names added to the Registry by all Registrars during the Service Level Measurement
Period in which the SLE occurred. The credit due to Registrar may be paid as an offset to registrations and other fees owed to Registry Operator by Registrar. All credits shall be paid in U.S.
Dollars. The following Credit Lookup Matrix indicates the corresponding credit table for which the credits defined in this Appendix will be levied. 

 
 

CREDIT LOOKUP MATRIX  
  

	 
	 	Performance

Specification

Description
	 	SRS
	 	Nameserver
	 	Whois

	1	 	Service Availability	 	Table C1a	 	Table C1b	 	Table C1a
	2	 	Processing Time—Add, Modify, Delete	 	Table C2	 	NA	 	NA
	3	 	Processing Time—Query Domain	 	Table C2	 	NA	 	NA
	4	 	Processing Time—Whois	 	NA	 	NA	 	Table C2
	5	 	Processing Time—Nameserver Resolution	 	NA	 	Table C2	 	NA
	6	 	Update Frequency	 	NA	 	Table C3	 	Table C3
	7	 	Planned Outage—Duration	 	Table C4b	 	NA	 	Table C4b
	8	 	Planned Outage—Timeframe	 	Table C4a	 	NA	 	Table C4a
	9	 	Planned Outage—Notification	 	Table C4a	 	NA	 	Table C4a
	10	 	Extended Planned Outage—Duration	 	Table C4b	 	NA	 	Table C4b
	11	 	Extended Planned Outage—Timeframe	 	Table C4a	 	NA	 	Table C4a
	12	 	Extended Planned Outage—Notification	 	Table C4a	 	NA	 	Table C4a

If
one or more SLEs occurs as the direct result of a failure to meet a Performance Specification in a single credit class, Registry Operator shall be responsible only for the credit assessed for the
credit class which is the proximate cause for all directly related failures. 

The
following tables identify total Registrar Community credits due for SLEs in the four credit classes C1—C4. Notwithstanding the credit levels contained in these tables, the total
credits owed by Registry Operator under this Agreement shall not exceed $30,000 USD monthly and $360,000 USD annually. The credits contained in Tables C1a-C4 represent the total credits that may be
assessed in a given SLR category in one Service Level Measurement Period. 

2.1 C1 Credit Class—If availability of C1 Credit Class components or systems does not meet C1 Performance Specifications in any given
Service Level Measurement Period described in the Performance Specification Matrix in Exhibit G, Registry Operator will credit the Registrar Community according to the tables (which amount will
be credited to the Registrar on a proportional basis as set forth above). 

 
 

Table C1a    
    

	SLE
 
	 	< 30

sec.'s
	 	30-60

sec.'s
	 	1-2

min.'s
	 	2-10

min.'s
	 	10-30

min.'s
	 	over 30

min.'s

	Monthly Credit to Registrar Community	 	$	750	 	$	1,500	 	$	2,500	 	$	3,750	 	$	5,000	 	$	6,000

C1a Availability Example: In a given measurement period, the SRS Availability is 99.87%, which equates to 52 minutes of unplanned downtime. The Registry
Operator's Performance Specification for SRS Availability is 99.9%, or 43 minutes of downtime. The Service Level Exception, therefore, is 9 minutes (52-43 minutes), the difference between
the Performance Specification and the actual measured performance. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C1a. In Table C1a, the time interval (2-10
minutes) has a corresponding credit of $3,750 USD to be paid to the Registrar Community. 

 
 

Table C1b    
    

	SLE
 
	 	< 10

min.'s
	 	10-30

min.'s
	 	30-60

min.'s
	 	1-2

hour s
	 	2-4

hours
	 	over 4

hours

	Annual Credit to Registrar Community	 	$	7,500	 	$	15,000	 	$	25,000	 	$	35,000	 	$	50,000	 	$	75,000

C1b Availability Example: In a given Service Level Measurement Period, the measured Nameserver Availability is 99.990% over a twelve (12) month
period, which equates to 52 minutes of downtime. The Registry Operator's Performance Specification for Nameserver Availability is 99.999%, or 5 minutes of downtime per calendar year. The Service Level
Exception, therefore, is 47 minutes (52-5 minutes), the difference between the Performance Specification and the actual measured performance. From the Credit Lookup Matrix, we see the
relevant SLA is found in Table C1b. In Table C1b, the time interval (30-60 minutes) has a corresponding credit of $25,000 USD to be paid to the Registrar Community. 

2.2 C2 Credit Class—If processing time for C2 Credit Class services does not meet C2 Service Levels in any given Service Level Measurement
Period, Registry Operator will credit the Registrar Community according to the following table (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C2    
    

	SLE
 
	 	< 2

sec.'s
	 	2-5

sec.'s
	 	5-10

sec.'s
	 	10-20

sec.'s
	 	20-30

sec.'s
	 	over 30

sec.'s

	Monthly Credit to Registrar Community	 	$	375	 	$	750	 	$	1,500	 	$	3,500	 	$	4,000	 	$	7,500

C2 Processing Example: The Performance Specification for Processing Time for Add, Modify, and Delete is 3 seconds or less for 95% of the transactions.
In a given Service Level Measurement Period 7% of the transactions are greater than 3 seconds. The 5% of those transactions with the longest processing times are not subject to the SLE calculation (3
seconds for 95%). The SLE is calculated using the average processing time for the 2% of the transactions that are subject to the SLE. If there were 1,000 transactions and they took a total of 4,000
seconds the average is 4 seconds. That generates an SLE of 1 second (4 seconds—3 seconds). From the Credit Lookup Matrix, we see the relevant SLA is found in Table C2. In Table C2, the SLE
time interval (< 2 seconds) has a corresponding credit of $375 USD to be paid to the Registrar Community. 

2.3 C3 Credit Class—If update frequency measurements of C3 Credit Class components or systems do not meet C3 Service Levels in any given
Service Level Measurement Period as described in the Performance Specification Matrix in Exhibit G, Registry Operator will credit the Registrar Community according to the following tables
(which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C3    
    

	SLE
 
	 	< 30

sec.'s
	 	30-60

sec.'s
	 	1-2

min.'s
	 	2-10

min.'s
	 	10-30

min.'s
	 	over

30 min.'s

	Monthly Credit to Registrar Community	 	$	188	 	$	375	 	$	625	 	$	938	 	$	1,250	 	$	1,500

C3 Update Frequency Example: In a given Service Level Measurement Period, 95% of the updates to the Nameserver take 24 minutes or less to complete. The
corresponding Registry Operator's Performance Specification is 15 minutes for 95% of the updates. The SLE, therefore, is 9 minutes. From the Credit Lookup Matrix, we see the relevant SLA is found in
Table C3. The SLE time interval (2-10 minutes) has a corresponding credit of $938 USD to be paid to the Registrar Community. 

2.4 C4 Credit Class—If Registry Operator fails to comply with C4 Credit Class category Performance Specifications, Registry Operator will
credit the Registrar Community according to the following tables (C4a and C4b) (which amount will be credited to the Registrars on a proportional basis as set forth above). 

 
 

Table C4a    
    

	SLE
 
	 	Any

	Monthly Credit to Registrar Community	 	$	500

C4a Planned Outage Notification Example: In each instance the Registry Operator fails to meet the Performance Specifications for Notification and
Timeframe related to Planned Outages and Extended Planned Outages, the Registry Operator is subject to the credit in Table C4a. For example, the Registry Operator informs the Registrar Community that
it will initiate a Planned Outage of the SRS on the next calendar Sunday (five (5) days advance notice). The corresponding Registry Operator's Performance Specification is 28 days
notice. From the Credit Lookup Matrix, we see the relevant SLA is found in Table C4a. This results in a credit of $500 USD to be paid to the Registrar Community. 

 
 

Table C4b    
    

	SLE
 
	 	< 1

hour
	 	1-2

hours
	 	2-4

hours
	 	4-6

hours
	 	6-10

hours
	 	over 10

hours

	Monthly Credit to Registrar Community	 	$	300	 	$	750	 	$	1,200	 	$	2,500	 	$	3,500	 	$	4,000

C4b Planned Outage Example: In a given Service Level Measurement Period, the actual duration of a planned outage is 11 hours and 20 minutes for
the SRS. The corresponding Registry Operator's Performance Specification is 8 hours per month for the SRS. The SLE, therefore, is 3 hours and 20 minutes. From the Credit Lookup Matrix
the relevant SLA is found in Table C4b. The SLE time interval (2-4 hours) has a corresponding credit of $1,200 USD to be paid to the Registrar Community. 

3.  Receipt of Credits. In order for Registrars to claim credits, the following procedure must be followed: 

3.1  Registry
Operator shall perform the required measurements in order to obtain the total credits associated with the applicable Service Level Measurement Period. Such measurements and
associated documentation shall be delivered by e-mail to each of the Registrars in the Registrar Community. Such notice shall also include the total credit (if any) to be paid to the
Registrar Community as a result of any outages. 

3.2  Receipt
of Credit—When the above steps have been completed, the Registry Operator shall enter in each Registrar's account balance the amount of credit (if applicable) that
can be used immediately toward registrations in the Registry. 

4.     Obligations.  

4.1  Except
in the case of cross-network nameserver performance (which is not a subject of this Service Level Agreement), Registry Operator will perform monitoring from internally located
systems as a means to verify that the conditions of the SLA are being met. 

4.2  Upon
written request, and at the sole expense of the requesting Registrar(s), Registry Operator will retain an independent third party to be selected by Registry Operator with the
consent of the Registrar(s). The Registrar may, under reasonable terms and conditions, audit the reconciliation records for the purposes of verifying measurements of the Performance Specifications.
The frequency of these audits will be no more than once yearly during the term of the agreement between Registry Operator and the Registrar. 

4.3  Registry
Operator's obligations under this SLA are waived during the first 120 days after the Commencement-of-Service Date. 

4.4  A
Registrar must report each occurrence of alleged occasion of Unavailability of Core Services to the Registry Operator customer service help desk in the manner required by the
Registry Operator (i.e., e-mail, fax, telephone) in order for an occurrence to be treated as Unavailable for purposes of the SLE. 

4.5  In
the event that the Core Services are Unavailable to an individual Registrar, Registry Operator will use commercially reasonable efforts to re-establish the affected
Core Services for such Registrar as soon as reasonably practicable. In the event that the Unavailability of Core Services affects all Registrars, the Registry Operator is responsible for opening a
blanket trouble ticket and immediately notifying all Registrars of the trouble ticket number and details. 

4.6  Both
Registrar and the Registry Operator agree to use reasonable commercial good faith efforts to establish the cause of any alleged Core Services Unavailability. If it is mutually
determined to be a Registry Operator problem, the issue will become part of the Unplanned Outage minutes. 

4.7  Beginning
no later than 120 days post Commencement-of-Service Date, the Registry Operator will publish preliminary weekly system performance and
availability reports. Registry Operator will use best efforts to finalize these reports no later than 30 days after the preliminary reports are provided. 

4.8  The
Registry Operator will use commercially reasonable efforts to restore the critical systems of the Core Services within 24 hours after the termination of a force majeure
event and restore full system functionality within 48 hours after the termination of a force majeure event. Outages due to a force majeure will not be considered Service Unavailability. 

4.9  Incident
trouble tickets must be opened within a commercially reasonable period of time. 

5.     Miscellaneous.  

5.1  This
Service Level Agreement is independent of any rights, obligations or duties set forth in the Registry Agreement. In the event of any conflict between the terms and conditions of
this Agreement and the Registry Agreement, the Registry Agreement shall control. 

 
 

Exhibit I
  Registry/Registrar IP Claim Service Agreement    
    

This
IP Claim Service Agreement ("Agreement") entered into this            day
of                        , 2001 ("Effective Date") is between NeuLevel, Inc., a Delaware corporation having a
principal place of business at Loudoun Tech Center, 45980 Center Oak Plaza, Building VIII, Sterling, VA 20166 ("Registry Operator")
and                        ,
a                        corporation having a
principal place of business at                        ("Registrar"). This Agreement is hereby incorporated as Exhibit I to
Appendix F ("Registry-Registrar Agreement") to the Registry Agreement
by and between the Internet Corporation for Assigned Names and Numbers ("ICANN") and Registry Operator, including all Appendices attached thereto ("Registry Agreement"). Capitalized terms not defined
herein shall have the meaning set forth in the Registry Agreement. 

 
 

Explanatory Statement    
    

Registry
Operator has been authorized by the Internet Corporation for Assigned Names and Numbers ("ICANN") to operate as the.biz top-level domain registry. 

Prior
to Registry Operator's launch of the.biz registry, Registrar desires to offer an Intellectual Property Claim Service to holders of intellectual property rights who desire to obtain a.biz domain
name. 

Registry
Operator is willing to provide such Intellectual Property Claim Service subject to the terms and conditions of this Agreement. 

NOW,
THEREFORE, the parties agree as follows: 

1.     DEFINITIONS  

1.1  "Branded Site" means the Web site that includes Registry Operator branding, which Registry Operator will make available to third
parties to obtain information regarding the IP Claim Service. 

1.2  "Batch Option" means the submission of one hundred (100) or more separate claims in a flat file (e.g., Microsoft Excel "CSV"
format or as otherwise specified by Registry Operator) to Registry Operator for syntax check and batch load for IP Claim Service processing. 

1.3  "Claim" means a claim submitted by an End User through the IP Claim Service with respect to a Trademark (as defined below). 

1.4  "End User" means any individual, company or legal entity that uses the IP Claim Service. 

1.5  "IP Claim Service" means the Intellectual Property Claim Service as described in the Terms of Use in which each domain name application
in the.biz TLD submitted through an ICANN-Accredited Registrar will be compared to a database of registered or common law trademark ("Trademark") claim forms. For each match between the domain name
for an application and a string identified on a Trademark claim form notifications will be provided by Registry Operator to the applicant that other entities have claimed intellectual property rights
over that domain name. 

1.6  "Link" (as a noun or verb) means one or more instances of the following, as the context requires: (i) the hypertext connection
between the Registrar Site and the Branded Site or White Site; or (ii) the text and graphics depicting the hypertext connection. 

1.7  "Marketing Materials" means any advertising, press releases, publicity, marketing collateral or similar materials regarding the IP
Claim Service. 

1.8  "Participating Registrars" means the ICANN-Accredited Registrars offering the IP Claim Service. 

1.9  "Registrar Site" means the Internet URL controlled and/or operated by Registrar for the provision of the IP Claim Service. 

1.10  "Terms of Use" means the terms and conditions to access and use the IP Claim Service, a copy of which is attached as
Schedule A, which Registry Operator may modify from time to time in its sole discretion. 

1.11  "White Site" shall mean the Web site that does not include Registry Operator branding, which Registry Operator will make available to
Participating Registrars. 

2.     SERVICE DESCRIPTION  

2.1  Basic IP Claim Service. Registry Operator will provide the IP Claim Service pursuant to the terms and conditions of this Agreement
during the period beginning approximately May 21, 2001 continuing through approximately July 9, 2001 ("Phase 1"). The exact dates are subject to change at Registry Operator's sole
discretion. Registry Operator will provide advance notice to Registrar in the event that the above dates change. Registry Operator shall provide the IP Claim Service on behalf of Registrar in the
following manner: 

Branded
Site. Registrar will be included on the Branded Site unless Registrar expressly opts out. Registry Operator will make information regarding the IP Claim Service generally available to third
parties through the Branded Site. If an End User desires to submit a Claim through the Branded Site, Registry Operator will provide the End User with a list of all of the Participating Registrars.
Claimant will be required to choose a Participating Registrar as its 

provider
of the IP Claim Service before submitting a Claim through the Branded Site. Upon Registry Operator's receipt of a Claim and payment for such Claim pursuant to Section 7.2 below,
Registry Operator will process such Claim on behalf of Registrar through the IP Claim Service. Registrar acknowledges that Registry Operator does not guarantee that End User(s) will elect to obtain
the IP Claim Service from Registrar. Registry Operator will randomize the order in which each Participating Registrar appears on such list. Registrar further acknowledges that an End User's selection
of a Participating Registrar will not obligate such End User to obtain any other products or services of the Participating Registrar, including the submission of an application for a domain name or
the submission of any additional Claims through the IP Claim Service. 

2.2  Additional Methods. In addition to the Branded Site, Registrar may elect one or both of the following methods, at Registrars sole
discretion: 

(a)  Batch
Option. Registrar may submit Claims to Registry Operator for processing through the Batch Option. Registrar shall be solely responsible for collecting from End Users and
submitting to Registry Operator accurate and complete data for each Claim submitted through the Batch Option. Upon receipt by Registry Operator of properly-formatted Claims submitted through the Batch
Option and payment for such Claims pursuant to Section 7.1 below, Registry Operator will process such Claims through the IP Claim Service. 

(b)  White
Site. Registrar may refer End Users to the IP Claim Service by creating a Link to the White Site or by "framing" the White Site. Upon receipt by Registry Operator of a Claim
submitted by an End User through the White Site and payment for such Claim pursuant to Section 7.2 below, Registry Operator will process such Claim on behalf of Registrar through the IP Claim
Service. Registry Operator will make the White Site available as soon as practicable, but in no event later that five (5) business days from the Effective Date. 

2.3  Terms of Use. Registrar shall execute, and cause each of its End Users to execute the Terms of Use for each Claim submitted through the
Batch Option. For Claims submitted through the White and/or Branded Sites, Registry Operator shall cause each of the End Users to execute the Terms of Use on behalf of Registrar. Registry Operator
will provide Registrar with a copy of any modifications to the Terms of Use and Registrar shall notify all End Users of such modifications. Registrar shall not create terms and conditions with respect
to the IP Claim Service that are inconsistent with the Terms of Use. In the event of any inconsistency, the Terms of Use shall control. Registrar may provide End Users with a foreign translation of
the Terms of Use, but each End User must execute the English version of the Terms of Use provided by Registry Operator, which shall be authoritative. Registrar shall diligently enforce End User
compliance with such Terms of Use. 

2.4  Data Entry Services. If Registrar submits data through the Batch Option, Registrar (i) must provide accurate data for each
Claim, (ii) must ensure that the data conforms to the required field specifications, and (iii) may not create or supply "filler" data to bypass the data field requirements. Registrar
shall not access or modify the text of any data field created or supplied by an End User or its agent during the Claim submission process. In addition, Registrar shall not replace End User or agent
data with its own contact information in a Claim. 

2.5  End User License. By submitting End User data in connection with a Claim, Registrar automatically grants, or warrants that the owner of
such data has expressly granted, Registry Operator the limited, royalty-free, non-exclusive worldwide license to use all of the data contained in a Claim solely for the
purposes of implementing the IP Claim Service, processing the Claim, notifying domain name applicants of Claims, notifying End User of changes to the IP Claim Service, for archival purposes, and
otherwise required by Registry Operator for in Registry Operator's operation of the Registry TLD. 

2.6  Misuse. Registrar shall promptly notify Registry Operator of any suspected or known misuse of the IP Claim Service and provide its best
efforts to assist in verifying the facts surrounding such suspected misuse. 

2.7  Restrictions. Except as may be expressly provided in this Agreement, Registrar may not: (i) rent, lease, lend, directly or
indirectly transfer the IP Claim Service to any third party other than Registrar's authorized resellers of registration services; (ii) create derivative products based on the IP Claim Service
(other than as may be necessary to frame the White Site and bundle the IP Claim Service with Registrar's services); or (iii) remove, modify or obscure any copyright, trademark, patent or mask
work notices that appear on the IP Claim Service, Terms of Use or Marketing Materials or that appear during the use of the IP Claim Service. 

2.8  Reports. Registry Operator may be required to provide certain information and reports to ICANN from time to time. Registrar shall
submit periodic reports to Registry Operator, which shall include such information as may be reasonably requested by Registry Operator. Any failure of Registrar to provide such reports within thirty
(30) days after request by Registry Operator shall be a material breach of this Agreement. 

2.9  Technical Contacts. Upon execution of this Agreement, Registrar shall designate at least two (2) technical contacts that
Registry Operator may contact regarding this Agreement and shall provide Registry Operator with the name, telephone number and email address of such technical contact. Registrar shall promptly notify
Registry Operator of any change of its technical contacts or such contact information. 

2.10  Return of Copy of Registrar End User Data. No later than thirty (30) days after the completion of Phase 1, Registry Operator
shall provide to Registrar a complete copy of all Registrar's End User data submitted through the IP Claim Service. In no event shall Registrar receive any End User data that did not originate from
Registrar. 

3.     MARKETING  

3.1  Promotion. Registrar shall use its commercially reasonable efforts to promote and otherwise solicit prospective End Users to use to the
IP Claim Service. Such efforts shall accurately describe the IP Claim Service as set forth in the Marketing Materials and as otherwise provided by Registry Operator. In addition, such efforts shall be
consistent with good business ethics and reflect favorably upon the IP Claim Service. 

3.2  Marketing Materials. Registry Operator will provide Registrar with Marketing Materials in electronic format or such other format as the
parties may mutually agree. ** 

3.3  Restrictions. Registrar shall refrain from engaging in any illegal, unfair, or deceptive trade practices, unethical business practices
or making any representations or warranties inconsistent with those provided hereunder with respect to the promotion of the IP Claim Service. 

3.4  Logo and Trade Name Use. Registry Operator hereby consents to Registrar's use of Registry Operator's logo and trade name, as provided
by Registry Operator to Registrar, for the limited purpose of Linking to the Branded Site or the White Site and for Marketing Materials. Any and all use of Registry Operator's logo or trade name by
Registrar shall inure to the benefit of Registry Operator. Registrar acknowledges that its utilization of Registry Operator's logo will not create in it, nor will it represent it has any right, title
or interest in or to such logo. Registrar shall not do anything contesting or impairing the trademark rights of Registry Operator. Except as expressly contemplated by this Agreement, Registrar may not
use Registry Operator's name, trademarks, service marks or other identifier in any capacity without Registry Operator's prior written consent. 

3.5  Press Release. Any news release, public announcement, advertisement or publicity proposed to be released by Registrar containing
Registry Operator's logo and/or trademark will be subject to the prior written approval of Registry Operator. 

4.     SUPPORT  

4.1  Branded Site and White Site Options. At no cost to End Users, Registry Operator shall be the exclusive provider of customer support for
the IP Claim Service for Registrars that use the Branded or White Site Options. 

4.2  Batch Option. At no cost to End Users, Registrars shall be the exclusive provider of customer support for the IP Claim Service for
Registrars that elect to use the Batch Option. 

4.3  FAQs. Registrar shall create a Link from the Registrar Site to the Frequently Asked Questions ("FAQs") on the Branded Site, which
Registry Operator may amend from time to time in its sole discretion. Registrar may provide translation(s) of the FAQs into languages other than English but shall modify any translation upon request
by Registry Operator, if Registry Operator determines in its sole discretion that the translation does not accurately convey the intent of the FAQs. Nothing herein shall obligate Registry Operator
from verifying or monitoring in any way Registrar's compliance with the above. Registry Operator may frequently modify the FAQs. It is essential that the End User have access to the most recent
version of the FAQs. Therefore, except as provided above, Registrar may not otherwise copy the Frequently Asked Questions in whole or in part. 

5.  ACCURATE DATA. Registrar shall be responsible for the adequacy and accuracy of all data and information that Registrar and End User
furnish to Registry Operator and the results obtained therefrom. Registrar shall be responsible for maintaining adequate controls over its processing and data transmissions up to but excluding
transmissions within the IP Claim Service, for monitoring the input and output of such processing and transmissions and for notifying Registry Operator of any non-conforming processing
and/or transmissions. Registrar acknowledges and agrees, and shall require End User to acknowledge and agree, that Registry Operator is not responsible for checking, verifying or editing message
content or completeness or for detecting errors or anomalies nor for recreating or re-transmitting data. Although Registrar understands and acknowledges that Registry Operator has no
obligation to check, verify or edit claim content or completeness or for detecting errors, in the event that any errors are discovered, the claims containing such errors may be returned to Registrar
for correction and/or editing prior to Registry Operator processing the claim. 

6.     TERMINATION  

6.1  Term. Unless otherwise terminated in accordance with section 6, this Agreement shall expire 6 months after the
commencement of Phase 1. 

6.2  Termination Under Registry—Registrar Agreement. This Agreement may be terminated pursuant to the terms of the
Registry-Registrar Agreement. 

6.3  Material Breach. Registry Operator may terminate this Agreement upon ten (10) days written notice of a material breach of this
Agreement if such breach is not cured within such ten (10) day period. Notwithstanding the above, Registry Operator may terminate this Agreement immediately, upon written notice, for breach of
Sections 2.3, 2.4, or 4.3. 

6.4  Suspension. Registry Operator may suspend the IP Claim Service for Registrar and/or terminate this Agreement if Registrar breaches this
Agreement, and Registrar fails to cure such breach within five (5) days after receiving notice thereof from Registry Operator; provided, however, that Registry Operator may immediately suspend
the IP Claim Service and/or terminate this Agreement without notice (i) in order to prevent damage to or degradation of its Internet network integrity which may be caused by Registrar or its
End Users, (ii) to comply with any law, regulation, court order, or other governmental request or order which requires immediate action, (iii) for anyone's violation of Registry
Operator's Terms of Use or Privacy Policy, or (iv) for other behavior that in Registry Operator's sole discretion may be deemed to be illegal or otherwise to protect Registry Operator from
legal liability. Registry Operator will endeavor to give Registrar notice regarding the reason(s) for suspension or termination as soon as reasonably practicable after such suspension or termination. 

6.5  Effect of Termination. Within thirty (30) days after the expiration or termination of this Agreement for any reason, Registrar
will destroy the original and all copies (including partial copies) of all Marketing Materials or other materials provided by Registry Operator or used by Registrar in connection with this Agreement,
including copied portions contained in derivative works. Within such time period, Registrar will certify in writing to Registry Operator its compliance with this provision. 

6.6  Survival. The provisions of Articles Section 2.5, 2.8, 8, 9 and 10 shall survive any termination or the expiration of this
Agreement. 

7.     FEES TO REGISTRY OPERATOR  

7.1  Batch Option Fee. Subject to the terms of Appendix G of the Registry Agreement, Registrar shall pay Registry Operator a fixed
fee for each Claim submitted through the Batch Option ("Batch Option Fee"). The Batch Option Fee is provided in Schedule B. Registry Operator may, at its option and within 7 days written
notice, revise the fees in Schedule B. Registrar shall pay Registry Operator the Batch Option Fee by wire transfer concurrently with submission of Claims to Registry Operator. 

7.2  Branded Site and White Site Fees. End Users shall pay Registry Operator an IP Claim Service fee of ninety dollars (US $90) for each
Claim submitted through the White Site or the Branded Site ("IP Claim Service Fee"). IP Claim Service Fees are provided in Schedule B. Registry Operator may, at its option and with
7 days written notice, revise the fees in Schedule B. Registry Operator shall deduct from each IP Claim Service Fee a fixed fee in accordance with the fees set forth below ("Site Fee").
Registry Operator shall pay Registrar the remaining amount within thirty (30) days after the official close of Phase 1. Registry Operator, in accordance with Appendix G, shall determine
the Site Fees for the Branded and White Sites along with the Batch Option Site Fees. 

7.3  Expenses. Each party shall be responsible for its own expenses incurred in connection with performing its obligations hereunder. 

7.4  Taxes. Each party shall be responsible for sales, use, transfer, excise and all other taxes and duties, whether international,
national, state or local, however designated, which are levied or imposed by reason of performance by the other party under this Agreement; excluding, however, income taxes. 

8.     OWNERSHIP/CONFIDENTIALITY  

8.1  Ownership. Registry Operator has and shall retain all right, title and interest, including intellectual property rights, in and to the
IP Claim Service, Branded Site, White Site, and Registry Operator's logos, trademarks, and service marks. 

9.     WARRANTIES; LIMITATION OF LIABILITY; INDEMNIFICATION  

9.1  Accreditation; Terms of Use. Registrar represents and warrants that it has received and will maintain accreditation by ICANN as a
registrar of top-level domains. Registrar will offer the IP Claim Service in a manner that is consistent with this Agreement, the Terms of Use and Marketing Materials provided by Registry
Operator. Registrar shall be solely responsible for any claims, warranties or representations made by Registrar or Registrar's employees or representatives that differ from the Terms of Use provided
by Registry Operator. Registrar has entered a Registry-Registrar Agreement with Registry Operator which shall remain in effect during the term of this Agreement. 

9.2  Disclaimer of Warranties. REGISTRY OPERATOR MAKES NO WARRANTY TO REGISTRAR OR TO ANY OTHER ENTITY, WHETHER EXPRESS, IMPLIED OR 

STATUTORY,
AS TO THE MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE, LACK OF VIRUSES, ACCURACY OR COMPLETENESS OF RESPONSES OR RESULTS, TITLE, NONINFRINGEMENT, QUIET ENJOYMENT OR QUIET
POSSESSION, OR CORRESPONDENCE TO DESCRIPTION WITH RESPECT TO THE IP CLAIM SERVICE, THE WHITE SITE, OR THE BRANDED SITE. THE ENTIRE RISK AS TO THE QUALITY OF OR ARISING OUT OF THE USE OR PERFORMANCE OF
THE IP CLAIM SERVICE, THE WHITE SITE AND THE BRANDED REMAINS WITH THE REGISTRAR AND END USER. 

9.3  Limitation of Liability. IN NO EVENT SHALL EITHER PARTY OR THEIR AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS OR ASSIGNS BE
LIABLE FOR ANY INDIRECT DAMAGES, INCLUDING BUT NOT LIMITED TO, LOST PROFITS, LOSS OF BUSINESS, LOSS OF PRIVACY, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE OR CONSEQUENTIAL DAMAGES THAT RESULT
IN ANY WAY FROM REGISTRAR'S OR ITS END USERS' RELIANCE ON OR USE OF CONTENT, INFORMATION, OR SERVICES PROVIDED ON OR THROUGH THE IP CLAIM SERVICE, THE WHITE SITE, THE BRANDED SITE OR THAT RESULT FROM
OR ARE RELATED TO, MISTAKES, OMISSIONS, INTERRUPTIONS, DELETION OF FILES, ERRORS, DEFECTS, DELAYS IN OPERATION OR TRANSMISSION OR ANY FAILURE OF PERFORMANCE OF ANY KIND, EVEN IF SUCH PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. REGISTRY OPERATOR'S LIABILITY TO THE OTHER WHETHER IN CONTRACT OR IN TORT (INCLUDING BREACH OF WARRANTY, NEGLIGENCE AND STRICT LIABILITY IN TORT) SHALL BE
LIMITED TO THE AMOUNTS ACTUALLY PAID (INCLUDING BOTH PRINCIPAL AND INTEREST) TO REGISTRAR BY REGISTRY OPERATOR AT THE TIME THE EVENT RESULTING IN LIABILITY OCCURS. 

10.   MISCELLANEOUS  

10.1  Governing Law. This Agreement shall be governed by and construed in accordance with the laws of the Commonwealth of Virginia without
regard to its principles of conflicts of laws. 

10.2  Independent Contractors. Except to the extent that Registry Operator processes Claims on behalf of Registrars, nothing contained in
this Agreement shall be construed as creating any agency, partnership, or other form of joint enterprise between the parties. In the course of performing the IP Claim Service, Registry Operator may
retain independent contractors or assign or subcontract to or otherwise have any third party perform any or all of the IP Claim Service at any time, provided that Registry Operator shall continue to
remain responsible for full performance of any such duties to the same extent as if it had performed the IP Claim Service itself. 

10.3  Third-Party Beneficiaries. This Agreement shall not be construed to create any obligation by Registry Operator to any
non-party to this Agreement, including any End User. Notwithstanding the above, Registry Operator shall be a third party beneficiary to the Terms of Use. 

IN
WITNESS WHEREOF, this Agreement has been executed and delivered by the undersigned officers, thereunto, duly authorized, as of the Effective Date. 

	NEULEVEL, INC.	 	REGISTRAR
	 	 	 	 	 
	

By:	

 	
 	

By:	

 
	Name:	 	 	Name:	 
	Title:	 	 	Title:	 
	Date:	 	 	Date:	 

 
 

SCHEDULE A
  IP CLAIM SERVICE
  TERMS OF USE    
    

THIS IS A LEGALLY BINDING AGREEMENT BETWEEN                        - ("REGISTRAR") AND YOU, THE OWNER OF A
REGISTERED OR COMMON LAW TRADEMARK OR SERVICE MARK ("OWNER") OR THE DULY
AUTHORIZED AGENT OF AN OWNER ("AGENT") (COLLECTIVELY, "YOU"). THESE TERMS OF USE ARE THE COMPLETE AND EXCLUSIVE STATEMENT OF THE TERMS OF USE REGARDING USE OF THE REGISTRAR'S INTELLECTUAL PROPERTY
CLAIM SERVICE (THE "SERVICE").

BY SELECTING "I AGREE," BY USING THE SERVICE OR BY SIGNIFYING ACCEPTANCE IN ANY OTHER WAY, YOU AGREE TO BE BOUND BY THESE TERMS OF USE. IF YOU DO NOT AGREE WITH ALL OF THESE
TERMS OF USE, YOU ARE NOT AUTHORIZED TO USE THE SERVICE AND YOU MUST DISCONTINUE ANY FURTHER USE.

1.  The Service. Registrar provides the Service to holders of both registered and common law trademarks or service marks (collectively
"Trademarks"). During the domain name application process, applicants for a.biz domain name ("Applicants") will be notified of an Owner's alleged intellectual property rights in a Trademark if the
domain name contained in the domain name application is an exact match of the Trademark identified in an IP Claim (as defined below) submitted by Owner. You may review frequently asked questions
regarding the Service by reviewing our FAQs. 

2.  Registration, Password and Security. To use the Service, You may be asked to first create an account and obtain a login name and
password. You must provide Registrar with accurate, complete and current registration information and must update this information promptly if it changes. 

You
represent and warrant that You are at least eighteen (18) years of age or older and are either an Owner or an Agent duly authorized to represent an Owner(s) in connection with the Service
and submitting an IP Claim on behalf of an Owner(s). Agent will indemnify and hold harmless Registrar and its officers, directors, employees, agents, affiliates and subcontractors for any claims
brought by Owner or Third Parties relating to the use of the Service. 

You
are solely responsible for maintaining the confidentiality of Your login name and password. You must immediately notify Registrar of any unauthorized use of Your login name and You are responsible
for any unauthorized activities, charges and/or liabilities made on or through Your login name until we receive such notification. You may not transfer or lend login names to any other third party. 

3.  License to Use Data / Privacy. By submitting an IP Claim, You hereby grant Registrar, as well as any of its agents or subcontractors, a
limited, royalty-free, non-exclusive worldwide license to use all of the data contained in the IP Claim solely for the purposes of implementing the Service, processing Your IP
Claim, notifying Applicants of Your IP Claim, and for notifying You of changes to the Service, for archival purposes. 

4.  The IP Claim Process. 

In
order to submit a claim with respect to a Trademark or Trademarks ("IP Claim") through the Service, You must complete an IP Claim form for each Trademark. For each IP Claim, You must submit
complete contact information, representative contact information and notification details, and the details regarding the Trademark. You may specify in the representative field that an Agent may
receive legal correspondence regarding the IP Claim. Once You have submitted an IP Claim, you will receive a confirmation email and a claim number. You must retain the claim number for each IP Claim
You submit. 

Registrar
will accept IP Claims until July 9, 2001, or such later date as it may determine in its sole discretion ("Close of Phase I") and no IP Claims will be accepted after that date. 

From
the Close of Phase I until September 25, 2001 ("Phase 2"), or such other later date as Registrar may choose, in its sole discretion, the domain name applications from ICANN-approved
registrars ("Applications") will be compared with the database of IP Claims processed through the Service ("IP Claim Database"). For each exact match between an IP Claim in the IP Claim Database and a
domain name application, the Registry Operator for.Biz ("Registry Operator") will notify the Applicant that a third party or third parties have submitted an IP Claim for the exact Trademark. The email
notification to the Applicant will include, among other things, the information provided by Owner in the IP Claim, instructions on how to proceed with the registration process, and that if selected
during the randomized name selection phase ("Name Selection Phase"), the domain name will be placed on a temporary thirty (30) day hold when the Registry goes "live." The Applicant will have
the option to proceed with the Application or cancel the Application. If the Applicant does not respond to the email notification, or elects to cancel the Application, Your domain name application
will not be processed during the Name Selection Phase. If the Applicant chooses to proceed with the registration process and the name is selected during the Name Selection Phase, that domain name
automatically will be placed on a thirty (30) day "hold period" when the name is registered. 

After
Name Selection, the Owner will be notified by Registry Operator if an Applicant has successfully registered the domain name. The Owner will then have the option of contacting the Applicant and
finding a solution or using the guidelines set forth by a special dispute resolution process called the Start-up Trademark Opposition Policy ("STOP") ("information available at
[LINK], or the Uniform Domain-Name Dispute Resolution Procedures ("UDRP") (information is available at
http://www.icann.org/udrp/udrp-policy-24oct99.htm). 

You
will not be notified if there are no Applications that exactly match an IP Claim You submitted in the IP Claim Database. 

USE OF THE SERVICE DOES NOT GUARANTEE THAT AN OWNER WILL BE AWARDED THE.BIZ EXTENSION FOR ITS TRADEMARK. AN OWNER THAT WISHES TO OBTAIN A.BIZ EXTENSION FOR ITS TRADEMARK MUST
FILE A DOMAIN NAME APPLICATION.

DOMAIN NAME APPLICANTS WILL ONLY BE NOTIFIED OF APPLICATIONS THAT ARE EXACT MATCHES WITH A TRADEMARK IDENTIFIED IN AN IP CLAIM FORM. REGISTRAR WILL NOT VERIFY WHETHER A
TRADEMARK CLAIMED ON AN IP CLAIM FORM CORRESPONDS WITH AN ACTUAL, LEGAL OR VALID TRADEMARK, NOR WILL REGISTRAR PROVIDE ANY LEGAL OVERSIGHT OR ADJUDICATION FOR ANY DISPUTED INTELLECTUAL PROPERTY
IMPLICATED BY THE SERVICE.

5.  Conduct. 

You
may access and use the Service for lawful purposes only and you are solely responsible for the knowledge and adherence to any and all laws, statutes, rules and regulations pertaining to Your use
of the Service. You agree that You will not (i) use the Service to commit a criminal offense or to encourage conduct that would constitute a criminal offense or give rise to a civil liability,
or otherwise violate any local state, Federal or international law or regulation; (ii) upload or otherwise transmit any content that You do not have a right to transmit under any law or
contractual or fiduciary duty; 

(iii) interfere
or infringe with any trademark or proprietary rights of any other party; (iv) interfere with the ability of other users to access or use the Service; (v) claim a
relationship with or to speak for any individual, business, association, institution or other organization for which You are not authorized to claim such a relationship; (vi) interfere with or
disrupt the Service or servers or networks connected to the Service, or disobey any requirements, procedures, policies or regulations of networks connected to the Service; or (vii) reproduce,
duplicate, copy, use, distribute, sell, resell or otherwise exploit for any commercial purposes any portion of the Service. 

6.  Fees. As consideration for the Service, You agree to pay Registrar, or its agents or subcontractors, as the case may be, an IP Claim fee
for each IP Claim submitted through the Service by credit card through its online payment system. Such fee shall be due immediately and is non-refundable. Registrar, or its agents or
subcontractors, may take all remedies to collect fees owed. Registrar, or its agents or subcontractors may require you to submit and pay for each IP Claim individually or it may allow you store up a
certain number of IP Claims before submitting them for processing. Once you have stored that number of IP Claims, you may not be able to store any additional IP Claims and may need to submit them for
processing and pay the applicable fee before obtaining additional storage space. No refunds are permitted. 

7.  Agents. You agree that, if Your agent (e.g., an attorney, employee, etc.) submits an IP Claim on Your behalf, You are nonetheless bound
as a principal by all Terms of Use herein. Your continued use of the Services shall ratify any unauthorized actions of Your agent. By acting on Your behalf, Your agent certifies that he or she is
authorized to use the Service on Your behalf, that he or she is authorized to bind You to these Terms of Use and that he or she has apprised You of these Terms of Use of this Agreement. In addition,
You are responsible for any errors made by Your agent. Registrar will not refund fees paid by You or Your agent on Your behalf for any reason, including, but not limited to, in the event that Your
agent fails to comply with these Terms of Use, Your agent incorrectly provides information in the IP Claim process or if Your agent changes or otherwise modifies Your IP Claim incorrectly. 

8.  Copyright. You acknowledge that the Service, any underlying technology used in connection with the Service, and all software, material,
information, communications, text, graphics, links, electronic art, animations, audio, video, photos, and other data (collectively, the "Content") available within the Service are provided by
Registrar or third-party providers and are the copyrighted works of Registrar and/or such third parties. Except as expressly authorized by Registrar or such third parties in these Terms of Use or as
may be posted on the Service, You may not copy, reproduce, publish, distribute, modify, create derivative works of, rent, lease, sell, transfer, display, transmit, compile or collect in a database, or
in any manner commercially exploit any part of the Content or the Service, in whole or in part. You may not store any significant portion of any Content or the Service owned by, or licensed to
Registrar in any form, whether archival files, computer-readable files, or any other medium. You also may not "mirror" any Content or the Service on any other server. 

Registrar
encourages you to download and print a reasonable number of copies of an IP Claim for noncommercial, internal use only; provided that (i) any permitted copies contain, in unmodified
form, any copyright or other proprietary rights notices and an original source attribution to the Service; and (ii) no modifications are made except as may be expressly provided by Registrar. 

9.  Links. Some links on the Service lead to sites posted by independent site owners. Because Registrar has no control over these sites, it
cannot be responsible for such sites' accessibility via the Internet and does not endorse products, services, or information provided by such sites. As such, Registrar shall not be responsible or
liable, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with, use or reliance on any content, goods or services available on or through any other
site. Further, the inclusion of these links does not imply that the other sites have given
permission for inclusion of these links, or that there is any relationship between Registrar and the linked sites. 

10.  Disclaimer of Warranty, Limitation of Liability. YOU AGREE THAT YOUR ACCESS TO AND USE OF THE SERVICE IS AT YOUR OWN RISK. NEITHER
REGISTRAR NOR TIS PARENTS, 

SUBSIDIARIES,
SHAREHOLDERS, MEMBERS, OFFICERS, DIRECTORS, EMPLOYEES, AFFILIATES, AGENTS OR SUBCONTRACTORS WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE; NOR DO THEY MAKE ANY
WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM THE USE OF THE SERVICE OR AS TO THE ACCURACY, RELIABILITY, OR CONTENT WITHIN THE SERVICE. THE SERVICE IS PROVIDED ON AN "AS IS, "AS AVAILABLE"
BASIS WITHOUT REPRESENTATIONS OR WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSES AND
NON-INFRINGEMENT. 

IN
NO EVENT WILL REGISTRAR NOR ITS PARENTS, SUBSIDIARIES, SHAREHOLDERS, MEMBERS, OFFICERS, DIRECTORS, EMPLOYEES, AFFILIATES, AGENTS OR SUBCONTRACTORS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY
INCIDENTAL, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES (EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES), ARISING OUT YOUR USE OF OR INABILITY TO ACCESS OR USE THE SERVICE, INCLUDING WITHOUT
LIMITATION, LOSS OF REVENUE OR ANTICIPATED PROFITS, LOSS OF GOODWILL, LOST BUSINESS, LOST DATA, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES THAT RESULT FROM MISTAKES,
INACCURATELY ENTERED DATA, UNAUTHORIZED USE, OMISSIONS, INTERRUPTIONS, ERRORS, DEFECTS, DELAYS IN OPERATION, OR ANY FAILURE OF PERFORMANCE, WHETHER OR NOT LIMITED TO ACTS OF GOD, COMMUNICATIONS
FAILURE, THEFT, DESTRUCTION OR UNAUTHORIZED ACCESS TO INSTITUTIONS RECORDS, PROGRAMS OR SERVICES. YOU AGREE THAT THE FOREGOING LIMITATIONS OF LIABILITY REPRESENT A REASONABLE ALLOCATION OF RISK. 

IN
NO EVENT, SHALL REGISTRAR BE LIABLE TO YOU FOR ANY AMOUNT EXCEEDING THE AMOUNT OF FEES PAID BY YOU FOR THE APPLICABLE IP CLAIM. 

11.  Indemnification. You agree to indemnify and hold harmless Registrar and its parents, subsidiaries, shareholders, members, officers,
directors, employees, affiliates, agents and subcontractors from any claim or demand, including reasonable attorney's fees made by any third party due to or arising out of Your use of the Service,
your breach of these Terms of Use, any Content submitted to the Service, or any disputes involving the intellectual property rights of the Trademarks. 

12.  Modifications to the Service. Registrar reserves the right at any time and from time to time to modify or discontinue, temporarily or
permanently, the Service (or any part thereof) with or without notice. You agree that will not be liable to You or to any third party for any modification, suspension, or discontinuation of the
Services. 

13.  Termination. You may discontinue Your participation in and access to the Service at any time. These Terms of Use will continue to apply
to all past use of the Service by You, even if You are no longer using the Service. You acknowledge and agree that Registrar may terminate or block Your use of all or part of the Service without prior
notice for any reason, including, without limitation, if Registrar believes You have engaged in conduct prohibited by these Terms of Use. You agree that upon termination or discontinuance for any
reason, may delete all information related to You on the Service and may bar Your access to and use of the Service. 

14.  Governing Law. These Terms of Use shall be governed by and construed in accordance with the laws of the
[                        ], without regard to its principles of conflicts of law. 

15.  Changes to the Terms of Use. Registrar reserves the right to modify the Terms of Use at any time and from time to time. Any
modifications shall be effective upon the posting of the modified Terms of Use at www.                        . You agree to
review these Terms of Use periodically so that You are aware of any modifications.
Your continued use of the Service shall be deemed Your acceptance of the modified Terms of Use. 

16.  Severability. In the event that any provision of these Terms of Use shall be unenforceable or invalid under any applicable law or be so
held by applicable court decision, such unenforceability or invalidity shall not render this Agreement unenforceable or invalid as a whole, and, in such event, such provision shall be changed and
interpreted so as to best accomplish the objectives of such provision within the limits of applicable law or applicable court decision. 

17.  Third Party Beneficiary. Registry Operator ("NeuLevel") is an intended third party beneficiary of these Term and Conditions with rights
to enforce these Terms of Use. You will cooperate in good faith with NeuLevel or Registrar in investigating instances of non-compliance with these Terms of Use, if NeuLevel or Registrar
believes in good faith that you are not in compliance with these Terms of Use. 

18.  Subcontractors. In the course of providing the IP Claim Service, Registrar may retain independent contractors or assign or subcontract
to or otherwise have any third party perform any or all of the IP
Claim Service at any time, provided that Registrar shall continue to remain responsible for full performance of any such duties to the same extent as if it had performed the IP Claim Service itself. 

19.  Entire Agreement. These Terms of Use completely and exclusively state the agreement of the parties regarding the subject matter, and
supersede all prior agreements and understandings, whether written or oral, with respect to the subject matter of these Terms of Use. 

I
AGREE                        I DO NOT AGREE 

APPENDIX G  

 
 

Registry Operator Maximum Price Schedule  
  

This
schedule specifies the maximum price NeuLevel may charge for Registry Services under the Registry-Registrar Agreement. In a manner consistent with Section 3.4.3 of the Registry Agreement,
NeuLevel may charge a lower-than-specified rate for services, including not charging for a specified service. NeuLevel shall not be entitled to charge for any Registry Service
not specified in this Appendix G. 

1.     Maximum Domain-Name Initial Registration Fee  

NeuLevel
may charge the maximum fee per year at the time of registration for each domain name registered (the "Initial Registration Fee") in the Registry TLD or for each deferred domain name
registration, during the Term of the Registry Agreement as provided in the table below: 

	Maximum Fee

(Per Domain Name)
	 	Volume Range

(Number of Registered Names)

	US $5.30	 	0 to 4,999,999
	US $5.00	 	5,000,000 to 9,999,999
	US $4.75	 	10,000,000 +

The
Initial Registration Fee shall be paid in full by the ICANN-Accredited Registrar sponsoring the domain name at the time of registration. 

2.     Maximum Domain-Name Renewal Fee  

NeuLevel
may charge the maximum fee per year at the time of registration for each domain name registration renewal (the "Renewal Fee") in the Registry TLD during the Term of the Registry Agreement as
provided below: 

	Maximum Fee

(Per Domain Name)
	 	Volume Range

(Number of Registered Names)

	US $5.30	 	0 to 4,999,999
	US $5.00	 	5,000,000 to 9,999,999
	US $4.75	 	10,000,000 +

The
Renewal Fee shall be paid in full by the ICANN-Accredited Registrar sponsoring the domain name at the time of renewal. 

3.     Fees for Transfers of Sponsorship of Domain-Name Registrations  

During
the Term of the Registry Agreement, where the sponsorship of a domain name is transferred from one ICANN-Accredited Registrar to another ICANN-Accredited Registrar, NeuLevel may require the
registrar receiving the sponsorship to request a renewal of one year for the name. In connection with that extension, NeuLevel may charge a Renewal Fee for the requested extension as provided in item
2 above. The transfer shall result in an extension according to the renewal request, subject to a ten-year maximum on the future term of any domain-name registration. The
Renewal Fee shall be paid in full at the time of the transfer by the ICANN-Accredited Registrar receiving sponsorship of the domain name. 

For
a bulk transfer approved by ICANN under Part B of Exhibit D to the Registry-Registrar Agreement, Registry Operator may charge the gaining registrar US $0 (for transfers of 50,000
names or fewer) or US $50,000 (for transfers of more than 50,000 names). 

4.     Maximum Fee for Enhanced Whois Service  

During
the Term of the Registry Agreement, NeuLevel may introduce extended capabilities to its Whois service, as described in Appendix O to the Registry Agreement. 

These
extended service capabilities shall be made available on a subscription fee basis as follows: 

	To be negotiated with ICANN	 	Yearly Subscription Fee Rate
	To be negotiated with ICANN	 	One Time Usage Fee

5.  Maximum Fee for Start-Up Intellectual Property Notification and Domain Name Application Service

During
the Start-Up phase of the Registry TLD, NeuLevel will provide an Intellectual Property Notification and Domain Name Application service. This service is described in detail in
Appendix J to the Registry Agreement. This service shall be made available on a fee basis with maximum fees as follows: 

	US $90.00	 	Per Trademark Claim Form
	US $2.00	 	Per Domain Name Application Submission

6.     Maximum Fee for Secure Domain Name Registration Service  

During
the Term of the Registry Agreement, NeuLevel contemplates the introduction of an enhanced registration service, offered through ICANN-Accredited Registrars, utilizing secure processing
mechanisms for mission critical registrations to provide additional security measures with respect to modifications to domain name information and/or transfers of a domain name. This service is
described
in Appendix J to the Registry Agreement. This service will be offered as early as during the Start-Up phase of the Registry TLD with initial payments billed and due after the
Commencement-of-Service Date. The maximum fee charged will be as follows: 

	US $500.00	 	Per Secure Domain Name Registration

7.     Maximum Fee for Multi-Lingual Domain Registration Service  

During
the Term of the Registry Agreement, NeuLevel contemplates the introduction of a multi-lingual registration service, offered through ICANN-Accredited Registrars, allowing registrants to register
domain names in their native languages. This service will be introduced consistent with ICANN's plan on internationalized domains. The maximum fee charged will be as follows: 

	Maximum Fee

(Per Domain Name)
	 	Volume Range

(Number of Registered Names)

	To be negotiated with ICANN	 	0 to 4,999,999
	To be negotiated with ICANN	 	5,000,000 to 9,999,999
	To be negotiated with ICANN	 	10,000,000 +

The
Initial Registration Fee shall be paid in full by the ICANN-Accredited Registrar sponsoring the multi-lingual domain name at the time of registration. 

NeuLevel
may charge the maximum fee per year at the time of registration for each multi-lingual domain name registration renewal (the "Renewal Fee") in the Registry TLD during the Term of the Registry
Agreement as provided below: 

	Maximum Fee

(Per Domain Name)
	 	Volume Range

(Number of Registered Names)

	To be negotiated with ICANN	 	0 to 4,999,999
	To be negotiated with ICANN	 	5,000,000 to 9,999,999
	To be negotiated with ICANN	 	10,000,000 +

The
Renewal Fee shall be paid in full by the ICANN-Accredited Registrar sponsoring the multi-lingual domain name at the time of renewal. 

8.     Fee for Restoring Deleted Domain Name Registrations  

NeuLevel
may charge registrars the following maximum prices for each Registered Name that is restored pursuant to the Redemption Grace Period Policy set forth in Appendix C to the Registry
Agreement: 

	•
	The
cost of restoring an unintentionally deleted domain name in the Redemption Grace Period must not exceed US $40.00. 

NeuLevel
will waive the fee for restoring any Registered Name that was deleted, contrary to the wishes of the Registered Name Holder, as the result of a mistake of the Registry Operator. 

Note:
the fee for restoring deleted names is separate from, and in addition to, any Renewal Fees that may be charged pursuant to Section 2 of this appendix. 

9.     Fee Adjustments  

The
fees listed below are subject to adjustment according to the terms of Sections 3.14.5 and 4.4 of the Registry Agreement. 

 
 

FEE TABLE    
    

	Fee Type
	 	Maximum Amounts
	 	Fee Subject to Adjustment

	Registration Fee	 	US $5.30, $5.00, $4.75	 	Yes, §§ 3.14.5, 4.4
	

Renewal Fee	
 	

US $5.30, $5.00, $4.75	
 	

Yes, §§ 3.14.5, 4.4
	

Multi-Lingual Registration Fee	
 	

To be negotiated with ICANN	
 	

Yes, §§ 3.14.5, 4.4
	

Multi-Lingual Renewal Fee	
 	

To be negotiated with ICANN	
 	

Yes, §§ 3.14.5, 4.4
	

Enhanced Whois Fee	
 	

To be negotiated with ICANN	
 	

Yes, §§ 3.14.5, 4.4
	

Secure Domain Name Registration Fee	
 	

US $500	
 	

Yes, §§ 3.14.5, 4.4
	

Redemption Grace Period Restore Fee	
 	

US $40	
 	

Yes, §§ 3.14.5, 4.4

APPENDIX H  

 
 

NeuLevel Equal Access and Nondiscrimination Practice  
  

I. Equal Access and Nondiscriminatory Practice  

NeuLevel
shall provide registrars with the opportunity to register domain names in the.biz TLD pursuant to the terms and conditions of a Registry-Registrar Agreement ("RRA") to be executed between
NeuLevel and any such registrars accredited by ICANN to act as a registrar for domain names within the domain of the.biz TLD (hereinafter referred to as "ICANN-Accredited Registrars"). NeuLevel shall
provide all ICANN-Accredited Registrars (including individual NeuLevel members acting as a registrar) with equivalent access to the Registry-Registrar Protocol. NeuLevel will also make a certification
to ICANN at the end of the six month period immediately following the Effective Date of the Registry Agreement and at the end of each subsequent six month period for the Term of the Registry
Agreement, using the objective criteria set forth in the NeuLevel Equivalent Access Certification below, that NeuLevel, in its capacity as Registry Operator is providing all ICANN-Accredited
Registrars with such equivalent access. 

NeuLevel
will ensure, in a form and through ways described in the NeuLevel Equivalent Access Certification below, that the revenues and assets of the Registry Operator are not utilized to advantage
NeuLevel, its affiliates, any contractor to NeuLevel, or any owner of such contractor, to the detriment of other ICANN-Accredited Registrars. 

All
capitalized terms not otherwise defined herein shall have the meaning ascribed to them in the Registry Agreement. 

 
 

NEULEVEL EQUIVALENT ACCESS CERTIFICATION  
  

NeuLevel,
in its capacity as the Registry Operator, and on behalf of its contractors, makes the following certifications: 

1.  All
ICANN-Accredited Registrars (including NeuLevel affiliates acting as Registrars) connect to the Registry Shared Registration System using the same means available on the same terms
and conditions to any other ICANN-Accredited Registrar. 

2.  The
Registry Operator has made all registrar access software and any updates to that software available to all ICANN-Accredited Registrars at the same time and under the same term and
conditions. 

3.  All
ICANN-Accredited Registrars have the same level and means of access to Registry customer support personnel. 

4.  All
ICANN-Accredited Registrars have the same level and means of access to the NeuLevel Registry resources to resolve Registry/Registrar or Registrar/Registrar disputes and technical
and/or administrative customer service issues. 

5.  All
ICANN-Accredited Registrars have the same level and means of access to Registry Data to reconcile their registration activities. 

6.  All
ICANN-Accredited Registrars may perform basic automated registrar account management functions using the same registrar access software made available to all ICANN-Accredited
Registrars by the Registry Operator. 

7.  The
Registry Operator's Shared Registration System does not include any algorithms or protocols that differentiate among ICANN-Accredited Registrars with respect to functionality,
including database access, system priorities and overall performance. 

8.  All
Registry Operator officers, directors, shareholders, employees, agents, consultants, and contractors have been directed not to give preferential treatment to any individual
ICANN-Accredited Registrar. 

9.  The
Registry Operator has not provided preferential pricing structures, promotions or other economic terms to any individual ICANN-Accredited Registrar which are not available to all
ICANN-Accredited Registrars. 

10.  Registry
Operator has complied with the terms of the Registry Operator Code of Conduct and the Equal Access and Nondiscrimination Practice Plan. 

11.  I,
the undersigned, have taken reasonable steps to verify that the foregoing representations are true and correct. 

This
Certification is dated this the    day of                        ,
            . 

NeuLevel 

	By:	 	

	Name:	 	

	Title:	 	

II.    NeuLevel Equal Access and Nondiscriminatory Practice  

NeuLevel
and its contractors will comply with the following policies relating to Equal Access and Nondiscrimination Practice Plan (the "Plan"). 

	1.
	Section A—Equivalent Access Policy

It
is the goal of this policy to ensure that: 

1.1  All
ICANN-Accredited Registrars connect to the System using the same protocols and with the same limitations and security measures. 

1.2  All
ICANN-Accredited Registrars have the same access to customer support, administrative and business services. 

1.3  All
ICANN-Accredited Registrars have the same access to the tools required to access their data through the System including billing, account management and other similar services. 

1.4  With
the exception of systems designed to enforce NeuLevel's or ICANN's terms of service, contract or policy, the System does not include any features or systems designed to perform
prejudicially or favorably towards any specific ICANN-Accredited Registrar[s]. 

	2.
	Section B—Organizational Conflict of Interest Compliance Plan for NeuLevel

NeuLevel
has created the following processes and policies in order to achieve the goals outlined above. 

2.1  Organization Structure

NeuLevel
will comply with its Code of Conduct contained in Appendix I with respect to its organizational structure. NeuLevel will ensure it maintains the appropriate protections from
organizational conflicts of interest. Currently, Jeff Ganek is a member of the Board of Directors of Neustar and NeuLevel. NeuLevel will ensure that its directors, officers, employees, agents and
consultants are independent and derive their mandate and directions from NeuLevel Board of Directors. 

2.2  Financial Separation

NeuLevel
will ensure that separate financial statements for NeuLevel are prepared using United States GAAP accounting standards. NeuLevel's financial statements will account for its own costs,
revenues, cash flow, etc. as a separate entity, using distinct systems and accounting functions. Reasonable and independently auditable internal accounting controls will be in place to ensure the
adequacy of these systems and functions. The accounting and operational 

procedures
will be established in such a fashion that no detailed customer account information relating to any ICANN-Accredited Registrar will be available to any other ICANN-Accredited Registrar. 

2.3  Different Locations/Office Premises

NeuLevel
will conduct its business and technical operations from different premises than any ICANN-Accredited Registrar. There may be situations where technical systems might reside within the same
physical premises as an ICANN-Accredited Registrar, however these premises will not be owned by an ICANN-Accredited Registrar, will be operated by an entity not affiliated with any of them, and will
be physically and distinctly separated from each other. Any instance where NeuLevel has located or will locate technical systems in the same third party premises as an ICANN-Accredited Registrar will
be disclosed to ICANN within a commercially reasonable time period after NeuLevel is made aware of the situation. Only upon the written consent of ICANN, which shall not be unreasonably withheld or
delayed, may NeuLevel technical systems reside in any datacenter or network facility owned or controlled, in whole or in part, by an ICANN-Accredited Registrar. 

2.4  Physical Barriers

At
NeuLevel's facilities, only assigned personnel employed or contracted by NeuLevel will have regular badge access to the premises and any other person will be treated as a visitor to the facility
and will gain access only through established visitor sign-in and identification badge procedures. NeuLevel will create and maintain an entry/exit log for all persons who enter the
facility. 

2.5  Registry
Access 

NeuLevel
will provide access to all Registry customers through the mechanisms described above. 

	3.
	Section C—Information Control

NeuLevel
has in place various procedural safeguards to ensure that data and information of the registry business are not utilized to advantage one ICANN-Accredited Registrar over another. The Access
to Data Policy is attached as Exhibit A. 

3.1  Staff Training

All
NeuLevel Personnel and other employees who have a need to know NeuLevel business will undergo a formal Training Program, providing the staff members with a clear understanding of this Plan with
special attention paid to the Equivalent Access Policy and the staff members' responsibility under the plan. Formal training will be required before any potential staff member is given an assignment
or access to NeuLevel material. Formal refresher training will be given on an annual basis. 

3.2  Treatment of Information

Upon
completion of the training program, all NeuLevel Personnel and other employees who have a need to know NeuLevel business will be required to sign a non-disclosure agreement
(Exhibit B) and a NeuLevel Business Avoidance Certification (Exhibit C) acknowledging, among other things, his/her understanding of the requirements, and certifying that he/she will
strictly comply with the provisions of the Plan. The signed agreements will be maintained in the program files and the individual's personnel file. Each staff member acknowledges verification of the
annual refresher training required by this Plan. 

The
Compliance Officer (CO) will, in all cases, endeavor to ensure that NeuLevel and its employees do not release any information to any ICANN-Accredited Registrar, or their respective employees that
could be used by an ICANN-Accredited Registrar to the detriment of any other ICANN-Accredited Registrar regardless of the official stated sensitivity of the 

information.
Under no circumstances will Registry Sensitive Information be approved by the CO for release to any other ICANN-Accredited Registrar. 

 
 

EXHIBIT A
  ACCESS TO DATA POLICY    
    

1.  Purpose: To establish policies (i) for the protection of Proprietary Information developed by and/or in the possession of
NeuLevel, and (ii) for the protection of Registry Sensitive Information to ensure that the revenue and assets of NeuLevel are not unfairly utilized to advantage another ICANN-Accredited
Registrar to the detriment of other competing ICANN-Accredited Registrars. 

2.  Scope: This policy is applicable to all officers, directors, members, shareholders, employees, agents, consultants, and subcontractors
of NeuLevel. 

3.  Definitions:

3.1  Proprietary Information.  Financial, personnel, technical, or business information owned or possessed by NeuLevel which has
not been authorized for public release. Such information is frequently referred to as "Proprietary Information," "Confidential Information" or "Privileged Information." 

3.2  Registry Sensitive Information.  Any information, including Proprietary Information or other financial, personnel,
technical, or business information owned or possessed by NeuLevel relating to its business which could be utilized to advantage ICANN-Accredited Registrar to the detriment of other competing
ICANN-Accredited Registrars. Examples of Registry Sensitive Information are contained in Attachment 1 hereto. 

3.3  Computer Software.  Computer programs and computer databases. 

3.4  Computer Software Documentation.  Technical data, including computer listing and printouts, in human-readable form which
(i) document the design or details of computer software, (ii) explain the capabilities of the software, or (iii) provide instructions for using the software to obtain desired
results from a computer. 

4.     Procedures for Protection of Proprietary Information:  

4.1  Responsibility.  Managers are responsible for identifying Registry Sensitive Information developed, produced or possessed
by NeuLevel and for instructing employees reporting to them regarding the proper handling and safeguarding of such information. Each NeuLevel employee will exercise reasonable care to protect Registry
Sensitive Information from unauthorized or inadvertent disclosure. 

4.2  Disclosure.  It is recognized that there are occasions where it is necessary to disclose Proprietary Information to
outsiders. Such disclosure should not be made without the prior written approval of an authorized Corporate officer of NeuLevel. Advice from Corporate counsel should be obtained on all questions
relating to the identification or releasing of Proprietary Information or Registry Sensitive Information. 

4.3  Marking of Documents.  Documents containing Proprietary Information or Registry Sensitive Information will be marked with
one of the markings described below at the time the document(s) is produced. Computer tapes and other recorded material should be identified by proper labeling which is visible to the ordinary person
while the material is being stored. In addition, all such material should have a warning notice at the beginning of the material to ensure the user is forewarned about the proprietary or sensitive
nature of its contents (as soon as access is afforded to a computer tape or at the beginning of a sound recording, etc.). 

4.3.1  Internal Documents.  On internal documents (reports, memoranda, drawings, etc.) the applicable following legend shall be
put at the top or bottom of the first page or, in the case 

of
drawings, in the space provided for such legends. The "need to know" principle shall be the guideline when divulging Proprietary Information or Registry Sensitive Information internally. 

 
 

NeuLevel Proprietary Information    
    

The information on this document is proprietary to NeuLevel. It may not be used, reproduced or disclosed without the written approval of NeuLevel.

 
 

NeuLevel Registry Sensitive Information    
    

The information on this document is proprietary to NeuLevel. It may not be used, reproduced or disclosed without the written approval of the Compliance Officer of
NeuLevel.

4.3.2  Documents for External Distribution

	A.
	Reports and Similar Documents

The
following legend shall be typed or stamped on the cover and/or title page of reports or on the face of other documentation provided to others: 

 
 

NeuLevel Proprietary Information    
    

This document is the property of NeuLevel. It may be used by recipient only for the purpose for which it was transmitted and shall be returned upon request or when no longer
needed by recipient. It may not be copied or communicated without the prior written consent of NeuLevel.

	B.
	Letters

On
letters to third parties or outsiders which will contain Proprietary Information, the following statement or equivalent shall appear in the text: 

Information contained herein is NeuLevel Proprietary Information and is made available to you because of your interest in our company (or program, etc.). This information is
submitted in confidence and its disclosure to you is not intended to constitute public disclosure or authorization for disclosure to other parties.

	C.
	Proposals to Commercial Companies

1.  A
restrictive legend such as the following shall be placed on the title page of each volume of the proposal: 

NeuLevel's proposal, which follows, contains information and data that are privileged and/or confidential to NeuLevel. This information and data are not made available for
public review and are submitted voluntarily to XYZ COMPANY NAME only for purposes of review and evaluation in connection with this proposal. No other use of the information and data contained herein
is permitted without the express written permission of NeuLevel. Information and data contained herein is protected by the Uniform Trade Secrets Act, as codified, and any improper use, distribution,
or reproduction is specifically prohibited. No license of any kind whatsoever is granted to any third party to use the information and data contained herein unless a written agreement exists between
NeuLevel and the third party which desires access to the information and data. Under no condition should the information and data contained herein be provided in any manner whatsoever to any third
party without the prior written permission of NeuLevel. The data subject to this restriction is contained in pages            .

2.  Each
page of the proposal which contains Proprietary Information shall be marked as follows: 

Use or disclosure of proposal information is subject to the restriction on the title page of this proposal.

	D.
	Proprietary Information Released Pursuant to Contract

When
Proprietary Information is exchanged between NeuLevel and another company, a Confidentiality Agreement or Non-Disclosure Agreement shall be executed by the parties concerned. 

1.  The
parties will designate in writing one or more individuals within their own organization as the only person(s) authorized to receive Proprietary Information exchanged between the
parties pursuant to this Agreement (see Attachment 2 for sample agreement.). 

2.  All
information which the disclosing party claims as proprietary shall be received in writing, clearly identified as proprietary, and delivered personally or by mail addressed to
individuals designated above to receive the Proprietary Information. 

5.     Safekeeping  

When
not in use, Proprietary Information or Registry Sensitive Information will be stored in a locked desk, cabinet or file. Such material will not be left unattended during the workday and should be
turned face down in the presence of visitors or employees who have no need to know. 

6.     Destruction  

Burning,
shredding or comparable methods will be used for the destruction of Proprietary Information or Registry Sensitive Information. 

7.     Terminating Employees  

Terminating
employees will be reminded of their responsibilities and obligations in protecting Proprietary Information. All employees will execute a non-disclosure agreement specifying
that they may not retain or otherwise use such information after termination. Any deviation from this policy must be approved in writing by NeuLevel counsel and NeuLevel. 

8.     Third-Party Proprietary Information  

Proprietary
Information received from other companies through contractual or pre-contractual relationships will be afforded the same level of protection given to NeuLevel's Proprietary
Information. 

9.     Questions  

Questions
concerning implementation or interpretation of this policy will be referred to the appropriate General Manager or the General Counsel. 

 
 

ATTACHMENT 1
  Examples of Proprietary & Registry Sensitive Information    
    

Engineering Information  

Engineering
information, including schematics, code, and engineering notes will be considered Proprietary Information. 

Statistical Information  

Some
statistical information will be available for public consumption. Such information does not require any special treatment, so long as neither NeuLevel nor any ICANN-Accredited Registrar, receives
any preferential treatment (e.g., early access to such information). Other statistics, such as numbers of registrations, transfers, etc., performed by each registrar, as well as processing times,
numbers of failures or any information that is trending negative or contains negative performance factors not generally available to the public should be considered Registry Sensitive Information. 

One
area of statistical data that is deserving of special attention is Registry Information pertaining to the numbers of registrations, transfers, etc., performed by each registrar. All such
information is Registry Sensitive Information and will be treated accordingly. Unless otherwise approved, registration activity information must be protected from disclosure to any registrar other
than the registrar to which the information refers. 

Financial Information  

Financial
data related to NeuLevel is Registry Sensitive Information and will not be released without the express consent of the General Manager of NeuLevel. Monthly expenses and income shall be kept
sensitive and restricted from disclosure to any party other than the appropriate NeuLevel staff. 

 
 

ATTACHMENT 2
  NON-DISCLOSURE AGREEMENT
  Proprietary Information    
    

This
is an Agreement, effective                            , 2000 between NeuLevel, Inc., (hereinafter
referred to as "NeuLevel") and                        (hereinafter referred to as
"                        "). It is recognized that it may be necessary or desirable to exchange information between NEULEVEL
and                        for the purpose
of                                         
       . With respect
to the information exchanged between the parties subsequent to this date, the parties agree as follows: 

(1)  "Proprietary
Information" shall include, but not be limited to, performance, sales, financial, contractual and special marketing information, ideas, technical data and concepts
originated by the disclosing party, not previously published or otherwise disclosed to the general public, not previously available without restriction to the receiving party or others, nor normally
furnished to others without compensation, and which the disclosing party desires to protect against unrestricted disclosure or competitive use, and which is furnished pursuant to this Agreement and
appropriately identified as being proprietary when furnished. 

(2)  In
order for proprietary information disclosed by one party to the other to be protected in accordance with this Agreement, it must be: (a) in writing or in electronic form;
(b) clearly identified as proprietary information at the time of its disclosure by each page thereof being marked with an appropriate legend indicating that the information is deemed
proprietary by the disclosing party; and (c) delivered by letter of transmittal, hand delivery, or electronically transmitted to the individual designated in Paragraph 3 below, or his
designee. Where the proprietary information has not been or cannot be reduced to written or electronic form at the time of disclosure and such disclosure is made orally and with prior assertion of
proprietary rights therein, such orally disclosed proprietary information shall only be protected in accordance with this Non-Disclosure Agreement provided that complete written summaries
of all proprietary aspects of any such oral disclosures shall have been delivered to the individual identified in 

Paragraph 3
below, within 20 calendar days of said oral disclosures. Neither party shall identify information as proprietary which is not in good faith believed to be confidential, privileged,
a trade secret, or otherwise entitled to such markings or proprietary claims. 

(3)  In
order for either party's proprietary information to be protected as described herein, it must be submitted in written or electronic form as discussed in Paragraph 2 above
to: 

	NeuLevel, Inc.	 	

	

Name: Jeffrey J. Neuman, Esq.	
 	

Name:
	 	 	

	

Title: Director, Law & Policy	
 	

Title:
	 	 	

	

Address: 1120 Vermont Ave., NW Fourth Floor, Washington, D.C. 20005	
 	

Address:
	 	 	

	

Telephone No: (202) 533-2733	
 	

Telephone No:
	 	 	

	

FAX No: (202) 533-2970	
 	

FAX No:
	 	 	

(4)  Each
party covenants and agrees that it will keep in confidence, and prevent the disclosure to any person or persons outside its organization or to any unauthorized person or persons,
any and all information which is received from the other under this Non-Disclosure Agreement and has been protected in accordance with paragraphs 2 and 3 hereof; provided however, that a
receiving party shall not be liable for disclosure of any such information if the same: 

A.  Was
in the public domain at the time it was disclosed, 

B.  Becomes
part of the public domain without breach of this Agreement, 

C.  Is
disclosed with the written approval of the other party, 

D.  Is
disclosed after three years from receipt of the information, 

E.  Was
independently developed by the receiving party, 

F.  Is
or was disclosed by the disclosing party to a third party without restriction, or 

G.  Is
disclosed pursuant to the provisions of a court order. 

As
between the parties hereto, the provisions of this Paragraph 4 shall supersede the provisions of any inconsistent legend that may be affixed to said data by the disclosing party, and the
inconsistent provisions of any such legend shall be without any force or effect. 

Any
protected information provided by one party to the other shall be used only in furtherance of the purposes described in this Agreement, and shall be, upon request at any time, returned to the
disclosing party. If either party loses or makes unauthorized disclosure of the other party's protected information, it shall notify such other party immediately and take all steps reasonable and
necessary to retrieve the lost or improperly disclosed information. 

5)  The
standard of care for protecting Proprietary Information imposed on the party receiving such information, will be that degree of care the receiving party uses to prevent disclosure,
publication or dissemination of its own proprietary information, but in no event less than reasonable care. 

(6)  Neither
party shall be liable for the inadvertent or accidental disclosure of Proprietary Information if such disclosure occurs despite the exercise of the same degree of care as such
party normally takes to preserve its own such data or information. 

(7)  In
providing any information hereunder, each disclosing party makes no representations, either express or implied, as to the information's adequacy, sufficiency, or freedom from
defect of any kind, including freedom from any patent infringement that may result from the use of such 

information,
nor shall either party incur any liability or obligation whatsoever by reason of such information, except as provided under Paragraph 4, hereof. 

(8)  This
Non-Disclosure Agreement contains the entire agreement relative to the protection of information to be exchanged hereunder, and supersedes all prior or
contemporaneous oral or written understandings or agreements regarding this issue. This Non-Disclosure Agreement shall not be modified or amended, except in a written instrument executed
by the parties. 

(9)  Nothing
contained in this Non-Disclosure Agreement shall, by express grant, implication, estoppel or otherwise, create in either party any right, title, interest, or
license in or to the inventions, patents, technical data, computer software, or software documentation of the other party. 

(10)  Nothing
contained in this Non-Disclosure Agreement shall grant to either party the right to make commitments of any kind for or on behalf of any other party without the
prior written consent of that other party. 

(11)  The
effective date of this Non-Disclosure Agreement shall be the date upon which the last signatory below executes this Agreement. 

(12)  This
Non-Disclosure Agreement shall be governed and construed in accordance with the laws of the Commonwealth of Virginia. 

(13)  This
Non-Disclosure Agreement may not be assigned or otherwise transferred by either party in whole or in part without the express prior written consent of the other
party, which consent shall not unreasonably be withheld. This consent requirement shall not apply in the event either party shall change its corporate name or merge with another corporation. This
Non-Disclosure Agreement shall benefit and be binding upon the successors and assigns of the parties hereto. 

(14)  It
is further understood and agreed that money damages would not be a sufficient remedy for any breach of this agreement by either party or any of its representatives and that the
non-breaching party shall be entitled to equitable relief, including injunction and specific performance, as a remedy for any such breach. Such remedies shall not be deemed to be the
exclusive remedies for a breach of this agreement but shall be in addition to all other remedies available at law or equity. In the event of litigation relating to this agreement, if a court of
competent jurisdiction determines that either party or any of its representatives have breached this agreement, then the breaching party shall be liable and pay to the non-breaching party
the reasonable legal fees incurred in connection with such litigation, including an appeal therefrom. 

	NeuLevel, Inc.	 	

	

By:	
 	

	
 	

By:	
 	

	

Name:	
 	

	
 	

Name:	
 	

	

Title:	
 	

	
 	

Title:	
 	

	

Date:	
 	

	
 	

Date:	
 	

 
 

EXHIBIT B
  NON-DISCLOSURE AGREEMENT    
    

I
understand I am an employee of NeuLevel, Inc. ("NeuLevel") or another employee who has a need to know information related to NeuLevel which is proprietary, confidential or business sensitive,
belonging to NeuLevel, other companies or customers of NeuLevel. I agree not to disclose or otherwise disseminate such information to anyone other than Need to Know Employees, except as directed, in
writing, by                        of NeuLevel or his/her designee ("Compliance Officer"). I understand
that disclosure of such information to anyone other than a Need to Know
Employee or use of such information could result in personal liability for such unauthorized use or disclosure.

I
agree to use such proprietary, confidential and/or business sensitive information only in the performance of requirements necessary to carry out my duties as a Need to Know Employee, and I agree to
take suitable precautions to prevent the use or disclosure of such information to any party, other than Need to Know Employees. I will report to the Compliance Officer any potential violation of this
agreement. I further agree to surrender any and all data and information, of any type whatsoever,
to the Compliance Officer upon the termination of my employment as an employee of NeuLevel, or my assignment with NeuLevel. 

I
certify that I have read and fully understand this Non-Disclosure Agreement and agree to abide by all requirements contained herein. I understand that my strict compliance is essential
to NeuLevel, and any violation of these requirements may result in termination of my employment. 

	Agreed to:	 	Verified:
	

 Employee	
 	

 General Manager, Registry
	

Date	
 	

Date

 
 

EXHIBIT C
  REGISTRY BUSINESS ORGANIZATIONAL CONFLICT OF INTEREST AVOIDANCE CERTIFICATION    
    

I
hereby certify that I have received training in and understand the requirements of conflict of interest issues and the requirements of the Organizational Conflict of Interest Compliance Plan of the
Registry Business of NeuLevel, LLC. I certify that I will strictly comply with the provisions of this Plan. I understand my obligation to (i) refrain from any activities which could pose a
personal conflict of interest and (ii) report to the General Manager of the Registry Business, any conflict, whether personal or organizational, which is perceived or identified during the
course of my employment with the Registry Business. 

	CERTIFIED	 	 
	

 signature date	
 	

 
	

 name	
 	

 

APPENDIX I  

 
  REGISTRY CODE OF CONDUCT  
  

NeuLevel
will at all times operate as a trusted neutral third-party provider of Registry Services. NeuLevel recognizes that domain names are the means by which businesses, consumers, and individuals
gain access to, navigate, and reap the benefits of the global Internet. These benefits cannot be fully realized, however, unless DNS resources are administered in a fair, efficient, and neutral manner
that makes them available to all parties desiring to provide DNS services. Therefore, in its provision of neutral Registry Services, NeuLevel will comply with the following Registry Code of Conduct. 

1.  Other
than in connection with the distribution of dividends or other profits to NeuLevel's members and shareholders, NeuLevel will not, and will require that its subcontractors do not,
directly or indirectly, show any preference or provide any special consideration to any DNS registry operator or ICANN-Accredited Registrars in the.biz Registry versus any other DNS registry operator
or ICANN-Accredited Registrars in the.biz Registry, as those terms are defined by ICANN, including the registry or registrar owned by a member of NeuLevel. 

2.  All
ICANN-Accredited Registrars in the.biz Registry shall have equal access to Registry Services provided by NeuLevel as set forth in Appendix H. 

3.  NeuLevel
and its owners shall not in any way attempt to warehouse domain names. In addition, Registry Operator shall not attempt to register domain names in its own right, except for
names designated for operational purposes in compliance with Subsection 3.6 of the Registry Agreement. In its Monthly Report to ICANN, NeuLevel shall include a list of all names designated for
operational purposes. 

4.  Any
shareholder, subsidiary, affiliate, or other related entity of NeuLevel that also operates as a provider of registrar services shall maintain separate books of account with respect
to its registrar operations separate from those of NeuLevel. 

5.  Neither
NeuLevel, nor its shareholders, subsidiaries, affiliates, or other related entities shall have access to user data or proprietary information of an ICANN-Accredited Registrar,
except as necessary for registry management and operations. 

6.  NeuLevel
will ensure that no user data or proprietary information from any ICANN-Accredited Registrar is disclosed to its affiliates, subsidiaries, or other related entities, except as
necessary for registry management and operations. 

7.  Confidential
information about NeuLevel's business services will not be shared with employees of any DNS registry operator or ICANN-Accredited Registrars, except (i) as
necessary for registry management and operations or (ii) if such information is made available to all DNS registry operator employees and ICANN-Accredited Registrars on the same terms and
conditions. 

8.  No
member of NeuLevel's Board of Directors will simultaneously serve on the Board of Directors of an ICANN-Accredited Registrar that obtains Registry Services from NeuLevel. 

9.  No
employee of NeuLevel will hold a greater than 5% interest, financial or otherwise in a company that obtains Registry Services from NeuLevel. 

10.  No
employee of NeuLevel will also be an employee of any NeuLevel subsidiary, affiliate or other related entity that also operates as an ICANN-Accredited Registrar. 

11.  NeuLevel
will ensure that no user data from or proprietary information of any registry operated or controlled by NeuLevel is disclosed to any other registry operated or controlled by
NeuLevel. 

12.  NeuLevel
will conduct internal neutrality reviews on a regular basis. In addition, NeuLevel and ICANN may mutually agree on an independent party ("Neutrality Analyst") that ICANN may
hire, at ICANN's expense, to conduct a neutrality review of NeuLevel, ensuring that NeuLevel and its owners comply with all the provisions of this Registry Operator Code of Conduct. The neutrality
review may be conducted as often as once per year. NeuLevel will provide the Neutrality Analyst with reasonable access to information and records appropriate to complete the review. The results of the
review of the Neutrality Analyist will be provided to ICANN and shall be deemed to be confidential and proprietary information of NeuLevel and its owners. 

APPENDIX J  

 
  Registry TLD Start-Up Plan  
  

Registry
Operator will follow a multi-phased start-up procedure for.biz. These phases have been designed to ensure fairness and equity to all ICANN-Accredited Registrars, resellers,
potential registrants and registrants, and to reflect the diverse needs of these constituencies and the Internet Community. The approximate commencement date of the phases are set forth below: 

	

	PHASE
 
	 	ESTIMATED AVAILABILITY TO CUSTOMERS
 

	

	Phase 1: Start-Up Intellectual Property Notification and Domain Name Application	 	•	 	Acceptance of Trademark Claim Forms: 150 days prior to Commencement-of-Service Date.
	Service	 	•	 	Last Day to Submit Trademark Claim Forms: 110 days prior to Commencement-of-Service Date
	 	 	•	 	Acceptance of Domain Name Application submissions: 110 days prior to Commencement-of-Service Date
	 	 	•	 	Last day to submit Domain Name Applications before Landrush: 15-30 days prior to Commencement-of-Service Date
	

	Phase 2: Landrush	 	•	 	15-30 days prior to Commencement-of-Service Date
	

	Phase 3: Registry Live	 	Occurs on Commencement-of-Service Date:
	 	 	•	 	WHOIS service available
	 	 	•	 	DNS service available
	 	 	•	 	Registration of domain names on first-come, first-served basis begins
	 	 	•	 	Commencement of 30 day "Hold Period" for domain names that are subject to SIPN
	

This
Appendix describes the Start-Up Intellectual Property Notification and Domain Name Application Service, and the Landrush process. The Registry Live phase is described more fully in
Appendix C. NeuLevel will develop proprietary systems to support the first two phases of operation of the Registry. The systems for these phases are being developed specifically for the
purposes described below and are not intended to be supported after the Commencement-of-Service Date. The time frames contemplated herein are approximate and subject to change
with advance notice to ICANN and the Internet community. All final dates will be published on our website. 

Phase 1: Intellectual Property Notification and Domain Name Application Service  

The
Start-Up Intellectual Property Notification and Domain Name Application Service is designed to assist entities with intellectual property rights in trademarks and service marks
("Trademarks") in protecting their rights in the context of new TLDs and expected significant number of applications for new second level domain names. As more fully described below, each domain name
application in the.biz TLD submitted through an ICANN-Accredited Registrar will be compared to a database of Trademark claim forms operated by the Registry Operator. For each match between the domain
name for an application and a string identified on a Trademark Claim Form (as defined below) notifications will be provided that entities have claimed intellectual property rights over that domain
name. 

	A.
	Trademark Claim Form Submission

The
Start-up Intellectual Property Notification service ("SIPN") will begin approximately 150 days prior to the Commencement-of-Service Date, Registry
Operator will advise the public about the SIPN service by publishing detailed information for the general public that describes the SIPN process on its own website as well as make available to ICANN
to publish on its website. For a period of approximately thirty (30) to forty-five (45) days beginning approximately 110 days prior to the 

Commencement-of-Service
Date ("Claim Period"), Trademark owners ("Claimants") will be afforded the opportunity to fill out and submit "Trademark Claim Forms" which will set out
the following information: 

(i)  The.biz
domain name in which the Trademark owner is claiming intellectual property rights. This domain name must be identical to the alphanumeric string contained in the mark; 

(ii)  Exact
alphanumeric string contained in the trademark in which rights are claimed; 

(iii)  Trademark
holder entity contact information; 

(iv)  Trademark
holder representative's contact information and relationship to trademark holder entity (i.e., General Counsel, President, CEO, etc.); 

(v)  Description
of goods and services for which the exact Trademark is being used; 

(vi)  Date
of first use of the Trademark in commerce; and 

(vii)  If
the mark is registered with any national Trademark office, registration number, and country where registration was obtained (optional). 

There
shall be no restriction on the number of intellectual property owners that may file Trademark Claim Forms for a given domain name. Trademark owners may not submit a Trademark Claim Form after
the Claim Period. 

The
Registry Operator will not, however: 

	•
	Verify
whether a claim corresponds with an actual Trademark.

	•
	Provide
legal oversight or adjudication.

	•
	Guarantee
or represent that a Trademark owner who enrolls in the SIPN ("Claimant") will receive the actual domain name. 

Due
to the administrative requirements associated with comparing Trademark Claim Forms with domain name applications, and the limited duration of the SIPN process, the Registry Operator, and not
ICANN-Accredited Registrars will be responsible for managing and administering the SIPN service. In conjunction with the various marketing channels of Registry Operator, ICANN-Accredited Registrars
may also be afforded the opportunity to participate in the marketing of the SIPN service in accordance with Registry Operator's Equal Access Requirements and Code of Conduct, as set forth in
Appendices H and I respectively. The SIPN service will be offered on a fixed fee per Trademark Claim Form basis. The amount of the SIPN fee will be published by Registry Operator prior to the
commencement of the SIPN service, but in no event will the fee exceed the maximum amount set forth in Section 6 of Appendix G. This fee will be collected by the Registry Operator, or its
designee at the time that the Trademark Claim Form is submitted. 

Claimants
will submit a Trademark Claim Form for each separate Trademark for which they are claiming intellectual property rights via a website. This website will be accessible 24 hours per day
and will provide information about the SIPN, the Pre-registration, Landrush and SRS live phases, and a link to any relevant dispute resolution services. Claimants will receive
e-mail notification acknowledging receipt of the Trademark Claim Form. 

Submission
of a Trademark Claim Form does not create any special rights with respect to registering a particular domain name. Any Claimant wishing to register a domain name must also submit a separate
domain name application as described below. In addition to the Trademark Claim Form, the Claimant must also submit an Application (as described below) in order to be eligible to have a chance at
receiving the actual domain name. The submission of a Trademark Claim Form does not guarantee that the Claimant will receive the actual domain name. 

	B.
	Domain Name Application Submission

After
the end of the Claim period set forth above, and for a period of approximately ninety days thereafter, ICANN-Accredited Registrars will collect from those individuals or entities applying for
a.biz domain name ("Applicants") and provide to the Registry Operator the applications for domain name registrations in the Registry TLD ("Applications"). 

	•
	Prior
to the commencement of the submission of domain name Applications, the Registry Operator will have:

	•
	Agreements
with ICANN-Accredited Registrars;

	•
	Completed
testing with these ICANN-Accredited Registrars as set forth below;

	•
	Established
Customer Support processes and procedures for ICANN-Accredited Registrars as set forth in Appendix C;

	•
	Established
processes and procedures for billing, order entry, reporting and operations support;

	•
	A
website that will support secure transactions from Registrars, including posting of reports for ICANN-Accredited Registrars;

	•
	A
website that provides information to potential domain name Applicants;

	•
	Customer
Care support;

	•
	Escalation
processes and procedures for ICANN-Accredited Registrars; and

	•
	Debit
and billing capabilities. 

ICANN-Accredited
Registrars and Applicants will be advised that a minimum subscription of two (2) years will be required for domain name registrations granted during Landrush, and that a
non-refundable fixed fee for each domain name Application will be assessed. Such application fee shall not exceed the amount set forth in Appendix G. This fee is separate and in
addition to the Domain Name Initial Registration Fee set forth in Section 1 of Appendix G. 

Only
ICANN-Accredited Registrars that have completed testing with the Registry Operator will be permitted to submit Applications. The technical requirements placed on ICANN-Accredited Registrars
during Phases 1 and 2 will be significantly less than that required once the Registry enables the XRP protocol post-Landrush (as set forth below). During this start-up period,
ICANN-accredited Registrars must pass a start-up-phase technical acceptance test provided by the registry. The start-up-phase acceptance test will
involve: 

	•
	Creation
of batch files

	•
	Submission
of batch files

	•
	Validation
of submitted files against format and syntactic rules 

ICANN-Accredited
Registrars will be granted start-up-phase system access after submitting a batch file correctly conforming to the structure and syntax required by the Registry
Operator. ICANN-Accredited Registrars will be responsible for developing the necessary interface with their customers. The Registry Operator will develop an API that the ICANN-Accredited Registrars
will use to interface with the Registry Operator's systems. ICANN-Accredited Registrars will use a batch process to submit domain name applications to the Registry Operator. The file format, transport
method, and processing schedule will be provided in advance to the ICANN-Accredited Registrars. The Registry Operator will check the file format and integrity of each batch file to determine if it is
readable. If the batch file is not readable, the ICANN-Accredited Registrar will be notified and given an opportunity to resubmit the batch file. 

When
submitting its domain name application, the applicant will be given the opportunity to purchase NeuLevel's Secure Domain Name Registration Service. In the event that an applicant obtains the
domain name in question through the Landrush process described below, the service will be activated 

and
the domain name holder billed after the Commencement-of-Service Date. The Secure Domain Name Registration Service will be designed to provide a higher level of domain name
security to businesses with a mission critical domain name. Although domain names enrolled in the service will be subject to the restrictions and requirements of the.biz TLD, a secure registration
will be maintained in a "locked" status so that no changes to the information about the name may be modified absent affirmative approval obtained from the registrant by the Registry Operator. This
service will minimize the likelihood that a domain name will be hijacked or otherwise made unavailable either intentionally or through administrative error. The Secure Domain Name Service will be
offered on a 5-year term subject to the maximum fee set forth in Appendix G. 

Prior
to Landrush, each Application received by the Registry Operator will be compared to the Trademark Claim Form database. For each match between an Application and a Trademark Claim Form, the
Registry Operator will notify the applicant and the ICANN-Accredited Registrar through which the applicant filed an Application, that a third party, or parties, has submitted a claim for the exact
string requested. The notification to the Applicant will include, among other things, the information provided by Claimant in the Trademark Claim Form, instructions on how to proceed with the
registration process, notification that the domain name will automatically placed "On Hold" (as described below) if the name is registered. This notification is provided to all Applicants that apply
for the same string in the Application and does not guarantee ultimate registration by that Applicant of the domain name during Landrush. 

The
e-mail notification to the Applicant will provide a link to a secure site where the Applicant will go to confirm whether it wishes to proceed with the domain name application. The
Applicant will have the option to proceed with the application or cancel. If the Applicant does not respond to the e-mail notification from the Registry Operator, or elects to cancel the
Application, the Application will not be processed during Landrush, thus making the Applicant ineligible to register the actual domain name. If the Applicant affirmatively elects to continue the
application process after being notified of the Claimant(s) alleged trademark rights in the desired domain name, Registry Operator will provide confirmation to the Applicant as well as the ICANN-
Accredited Registrar through which the Applicant filed the Application, confirming the decision to pursue the domain name during Landrush. 

Phase 2: Landrush  

The
Landrush phase will begin approximately fifteen (15) to thirty (30) days prior to the Commencement-of-Service Date, depending on the number of Applications
received by the Registry Operator. The final date will be published on Registry Operator's website. All of the Applications from all ICANN-Accredited Registrars received by the Registry Operator will
be combined and randomized in a single batch for Landrush processing. This process will ensure fairness for each ICANN-Accredited Registrar and Applicant. In order to assure the ICANN-Accredited
Registrar community and the public that the results will be truly random, NeuLevel will apply a randomization algorithm to the batch. The requirement of the randomization algorithm is to ensure that
submitted domain names are completely randomized, without bias to any ICANN-Accredited Registrar. 

The
duration of processing during the Landrush phase will depend on the number of Applications received and placed in the processing queue. Domain name requests will be processed in the order in which
they appear in the randomized batch. After the processing of all Applications, each ICANN-Accredited Registrar will be notified of the domain names granted for that ICANN-Accredited Registrar's
customers. It will be the responsibility of the ICANN-Accredited Registrar to notify its customers whether they received the name(s) for which they submitted Applications. 

Registry
Operator will not guarantee that any individual Applicant or ICANN-Accredited Registrar will obtain a given name, nor will it accept any liability for errors, mistakes, omissions or technical
problems that arise with the Start-up Process. 

ICANN-Accredited
Registrars will be responsible for payment for each domain name that is successfully registered. This registration fee will be separate from the non-refundable fixed
application fee submitted during Phase 1 above. The Registry Operator will deduct payment from a debit account 

pre-funded
by each ICANN-Accredited Registrar. Domain names registered during the Landrush period will be registered for two (2) years. 

Phase 3: Registry Live  

Registry
Live begins on the Commencement-of-Service Date and will include the services and functionality described in Appendix C. 

	A.
	ICANN-Accredited Registrar Testing for Registry Live. 

Before
being granted access to the Registry-Live system, ICANN-Accredited Registrars will be required to pass a more extensive acceptance test than for Phases 1 and 2 described above. It
will require that ICANN-Accredited Registrars pass an XRP acceptance test which will involve: 

	•
	Connecting
to the registry and establishing a session

	•
	Passing
the authentication/authorization process

	•
	Executing
a script testing each XRP function at least once

	•
	Disconnecting
from the system 

The
Registry Operator will record a transaction log documenting the ICANN-Accredited Registrar's interaction with the Registry Operator. The ICANN-Accredited Registrar will be granted full access to
the system after successfully passing this test. 

	B.
	Commencement of Service. 

As
of the Commencement of Service Date, all domain names granted during the Landrush phase will be activated in the DNS unless such names are subject to the Hold Period described below. 

	C.
	Registration Hold Period. 

The
registration in the live registry of a domain name that is the subject of a complete Trademark Claims Form will not be immediate, but rather the subject domain name registration will automatically
enter a thirty (30) day Hold Period during which all Claimants will be advised by e-mail of the identity of the person or entity that has registered the exact Trademark claimed. The
notification e-mail will include the full WHOIS information of the registrant. In addition, the e-mail will provide a hyperlink to the Start-Up Uniform Dispute
Resolution Process ("SUDRP") as described in Appendix M to the Registry Agreement. 

During
this Hold Period, the domain name will not be activated in the DNS. Should a notified party file a contest to the registration in the formal SUDRP process, the domain name would be
"locked" until the dispute is decided. During such "locked" period, in accordance with the current Uniform Dispute Resolution Policy, modification by the registrant of the domain name information
(i.e. holder, contact information, etc.) will not be permitted, however, the domain name will resolve to the DNS after the Hold Period set forth above. 

Disclaimer of Warranties  

REGISTRY
OPERATOR DOES NOT MAKE ANY WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE SERVICES RENDERED BY ITSELF, ITS SERVANTS, OR ITS AGENTS OR THE RESULTS OBTAINED FROM THEIR WORK, INCLUDING,
WITHOUT LIMITATION, ANY IMPLIED WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. 

APPENDIX K  

 
  Schedule of Reserved Names  
  

Except
to the extent that ICANN otherwise expressly authorizes in writing, the Registry Operator shall reserve names formed with the following labels from initial (i.e. other than renewal)
registration within the TLD: 

A. Labels Reserved at All Levels. The following names shall be reserved at the second level and at all other levels within the TLD at which Registry
Operator makes registrations: 

ICANN: 

	•
	aso

	•
	dnso

	•
	icann

	•
	internic

	•
	pso

IANA-related
names: 

	•
	afrinic

	•
	apnic

	•
	arin

	•
	example

	•
	gtld-servers

	•
	iab

	•
	iana

	•
	iana-servers

	•
	iesg

	•
	ietf

	•
	irtf

	•
	istf

	•
	lacnic

	•
	latnic

	•
	rfc-editor

	•
	ripe

	•
	root-servers 

B. Additional Second-Level Reservations. In addition, the following names shall be reserved at the second level: 

	•
	All
single-character labels.

	•
	All
two-character labels shall be initially reserved. The reservation of a two-character label string shall be released to the extent that the
Registry Operator reaches agreement with the government and country-code manager, or the ISO 3166 maintenance agency, whichever appropriate.The Registry Operator may also propose release
of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes. 

	•
	aero

	•
	arpa

	•
	biz

	•
	com

	•
	coop

	•
	edu

	•
	gov

	•
	info

	•
	int

	•
	mil

	•
	museum

	•
	name

	•
	net

	•
	org

	•
	pro

C. Tagged Domain Names. All labels with hyphens in the third and fourth character positions (e.g., "bq—1k2n4h4b") 

D. Second-Level Reservations for Registry Operations. The following names are reserved for use in connection with the operation of the registry for the
Registry TLD. They may be used by Registry Operator under Subsection 3.6.1, but upon conclusion of Registry Operator's designation as operator of the registry for the Registry TLD they shall be
transferred as specified by ICANN: 

	•
	nic

	•
	whois

	•
	www

APPENDIX L  

 
  .biz Registration Restrictions  
  

Restrictions  

Registrations
in the.biz TLD will be subject to the following restrictions: 

1.  Registrations
in the.biz TLD must be used or intended to be used primarily for bona fide business or commercial purposes; and 

2.  Registrations
in the.biz TLD must comply with the Uniform Dispute Resolution Policy ("UDRP"), as adopted and as may be amended by the Internet Corporation of Assigned Names and
Numbers. For proceedings intitiated before the Commencement-of-Service Date, a modified version of the UDRP, known as the Start-Up Uniform Dispute Resolution Policy
("SUDRP") (which also includes corresponding modifications to the Rules for Uniform Domain Name Resolution Policy) will apply. 

For
purposes of the.biz Registration Restrictions ("Restrictions"), "bona fide business or commercial use" shall mean the bona fide use or bona fide intent to use the domain name or any content,
software, materials, graphics or other information thereon, to permit Internet users to access one or more host computers through the DNS: 

1.  To
exchange goods, services, or property of any kind; 

2.  In
the ordinary course of trade or business; or 

3.  To
facilitate (i) the exchange of goods, services, information, or property of any kind; or, (ii) the ordinary course of trade or business. 

Registering
a domain name solely for the purposes of (1) selling, trading or leasing the domain name for compensation, or (2) the unsolicited offering to sell, trade or lease the domain
name for compensation shall not constitute a "bona fide business or commercial use" of that domain name. 

For
illustration purposes, the following shall not constitute a "bona fide business or commercial use" of a domain name: 

1.  Using
or intending to use the domain name exclusively for personal, noncommercial purposes; or 

2.  Using
or intending to use the domain name exclusively for the expression of noncommercial ideas (i.e., registering abcsucks.biz exclusively to criticize or otherwise express an opinion
on the products or services of ABC company, with no other intended business or commercial purpose). 

Violations  

It
will be a violation of the Restrictions for an Applicant to: 

1.  register
or use a domain name contrary to the SUDRP; 

2.  register
and use a domain name contrary to the UDRP; or 

3.  use
the registered domain name in a manner inconsistent with the definition of "business or commercial use" contained herein. 

Violations
of the Restrictions may be grounds for cancellation of a registered.biz domain name, pursuant to the enforcement mechanism discussed below. 

Enforcement  

A
violation of the Restrictions will be enforced on a case-by-case, fact specific basis under the processes set forth below: 

1.  Any
allegation that a domain name is not used primarily for business or commercial purposes shall be enforced under the provisions of the Restrictions Dispute Resolution Process
("RDRP") as set forth in Appendix M. 

2.  Any
alleged violation of the UDRP shall be enforced under the provisions contained therein, as modified by the SUDRP for proceedings initiated no later than sixty days after the
Commencement-of-Service Date. 

None
of the violations of the Restrictions will be enforced directly by or through Registry Operator. The RDRP, UDRP, and SUDRP will be made applicable by the ICANN-Accredited Registrars' registration
agreements with registrants. Proceedings under the RDRP, UDRP, and SUDRP must be brought by interested third parties in accordance with the policies and procedures set forth in Appendix M.
Registry Operator will not review, monitor, or otherwise verify that any particular domain name is being used primarily for business or commercial purposes or that a domain name is being used in
compliance with the SUDRP or UDRP processes. 

Registration Requirements  

Before
the Registry Operator will accept applications for registration, all domain name applicants in the.biz TLD ("Applicants") must: 

1.  Enter
into an electronic or paper registration agreement with an ICANN-Accredited Registrar ("Registrar"), in accordance with the ICANN Registrar Accreditation Agreement
("Accreditation Agreement") and the Registry-Registrar Agreement. Such electronic or paper registration agreement shall include the following certifications: 

a)  The
data provided in the domain name registration application is true, correct, up to date and complete; and 

b)  The
registrant will keep the information provided above up to date. 

2.  As
part of a domain name registration application, the Applicant must certify that to the best of its knowledge: 

a)  The
registered domain name will be used in a manner consistent with the Restrictions above; 

b)  The
domain name registrant has the authority to enter into the registration agreement; and 

c)  The
registered domain name is reasonably related to the registrant's business or intended commercial purpose at the time of registration. 

Failure
to comply with the above will result in failure of the Registry Operator to process an Applicant's domain name application. 

Reservation  

Registry
Operator reserves the right to deny, cancel or transfer any registration that it deems necessary, in its discretion, to protect the integrity and stability of the registry, to comply with any
applicable laws,
government rules or requirements, requests of law enforcement, in compliance with any dispute resolution process, or to avoid any liability, civil or criminal, on the part of Registry Operator, as
well as its affiliates, subsidiaries, officers, directors and employees. Registry Operator also reserves the right to freeze a domain name during resolution of a dispute. 

APPENDIX M  

 
  Start-Up Enforcement and Enforcement of the
  Restrictions Document  
  

I. Uniform Dispute Resolution Policy  

A. General Information  

All
ICANN-Accredited Registrars in the.biz top-level domain shall follow the Uniform Domain-Name Dispute-Resolution Policy (often referred to as the "UDRP"). Under the policy,
most types of trademark-based domain-name disputes must be resolved by agreement, court action, or arbitration before a registrar will cancel, suspend, or transfer a domain name. Disputes
alleged to arise from abusive registrations of domain names (for example, cybersquatting) may be addressed by expedited administrative proceedings that the holder of trademark rights initiates by
filing a complaint with an approved dispute-resolution service provider. 

To
invoke the policy, a trademark owner should either (a) file a complaint in a court of proper jurisdiction against the domain-name holder (or where appropriate an
in-rem action concerning the domain name) or (b) in cases of abusive registration submit a complaint to an approved dispute-resolution service provider (see below for a list and
links). 

B. Principal Documents  

The
following documents provide relevant details: 

1.
Uniform Domain Name Dispute Resolution Policy—This policy is followed by all ICANN-Accredited Registrars. It can be found at:
http://www.icann.org/udrp/udrp-policy-24oct99.htm 

2.
Rules for Uniform Domain Name Dispute Resolution Policy—These rules are followed by all dispute-resolution service providers, with supplementation by each provider's supplemental rules.
This can be found at: <http://www.icann.org/udrp/udrp-rules-24oct99.htm>. 

3.
List of Approved Dispute-Resolution Service Providers. This list can be found at: <http://www.icann.org/udrp/approved-providers.htm>. 

4.
Information Concerning Approval Process for Dispute-Resolution Service Providers. This information can be found at:
<http://www.icann.org/udrp/udrp-provider-approval-process.htm>. 

II.    Start-Up Dispute Resolution Policy  

A. General Information  

All
disputes between a third party and a domain name registrant regarding the registration of an Internet domain name that is subject to the Start-Up Intellectual Property Notification
Service ("SIPNS"), set forth in Appendix J, shall be decided under the Start-Up Dispute Resolution Policy ("SUDRP"). 

To
invoke the policy, a third party may submit a complaint to an approved dispute-resolution service provider. 

B. Principal Documents  

The
following documents provide details: 

1.
Start-up Dispute Resolution Policy—This policy is followed by all ICANN-Accredited Registrars. The Policy, is attached as Exhibit 1 to this Appendix, and is made a
part of the ICANN-Accredited Registrar-registrant agreement. Registry Operator has begun the process of contacting potential dispute providers and is finalizing the procedures outlined below. 

2.
Rules for Start-Up Dispute Resolution Policy—These rules are followed by all dispute-resolution service providers, with supplementation by each provider's supplemental
rules. A preliminary draft 

of
the Rules are attached as Exhibit 2 to this Appendix. Registry Operator has begun the process of contacting potential dispute providers and is finalizing the procedures outlined below. 

3.
List of Approved Dispute-Resolution Service Providers. The then current list of approved dispute-resolution service providers will be identified on ICANN's web site at
http://www.icann.org/udrp/<FILE TO BE INSERTED>. 

4.
Information Concerning Approval Process for Dispute-Resolution Service Providers. The then current approval process will be identified on ICANN's web site at
http://www.icann.org/udrp/<FILE TO BE INSERTED>. 

III.  Restrictions Dispute Resolution Policy  

A. General Information  

All
ICANN-Accredited Registrars in the.biz top-level domain shall follow the Restrictions Dispute Resolution Policy (referred to as the "RDRP"). Under the policy, several types of disputes
alleged from a violation of the Restrictions Document (for example, from a.biz domain name used exclusively for personal noncommercial use), as set forth in Appendix L, may be addressed by
expedited administrative proceedings. These may be initiated by any party filing a complaint with an approved dispute-resolution service provider. To invoke the policy, a third party may submit a
complaint to an approved dispute-resolution service provider. 

B. Principal Documents  

The
following documents provide details: 

1.
Restrictions Dispute Resolution Policy—This policy is followed by all ICANN-Accredited Registrars. A preliminary draft of the Policy, is attached as Exhibit 3 to this Appendix,
and is made a part of the ICANN-Accredited Registrar-registrant agreement. Registry Operator has begun the process of contacting potential dispute providers and is finalizing the procedures outlined
below. 

2.
Rules for Restrictions Domain Name Dispute Resolution Policy—These rules are followed by all dispute-resolution service providers, with supplementation by each provider's supplemental
rules. A preliminary draft of the Rules are attached as Exhibit 4 to this Appendix. Registry Operator has begun the process of contacting potential dispute providers and is finalizing the
procedures outlined below. Registry Operator will coordinate with ICANN to publish the final Rules prior to the beginning of the.biz start-up procedures described in Appendix J. 

3.
List of Approved Dispute-Resolution Service Providers. The then current list of approved dispute-resolution service providers will be identified on ICANN's web site at
http://www.icann.org/udrp/<FILE TO BE INSERTED>. 

4.
Information Concerning Approval Process for Dispute-Resolution Service Providers. The then current approval process will be identified on ICANN's web site at
http://www.icann.org/udrp/<FILE TO BE INSERTED>. 

Exhibit 1

Start-up Dispute Resolution Policy for <.biz>  

1. Purpose. This Start-up Dispute Resolution Policy (the "Policy") is incorporated by reference into the <.biz>Registration
Agreement. It sets forth the terms and conditions in connection with a dispute between you (as the registrant) and any party other than us (as the registrar) or the registry administrator for the
<.biz> top-level domain (the "Registry Operator") over the registration or use of an Internet domain name registered by you that is subject to the Start-Up
Intellectual Notification Service ("SIPNS"; <URL>). 

The
SIPNS is a service introduced by the Registry Operator to notify a trademark or service mark holder ("Claimant") that a second-level domain name has been registered in which that Claimant 

claims
intellectual property rights. In order to benefit from the SIPNS, a Claimant was required to submit a Trademark Claim Form ("TCF") for the <.biz> domain name matching the exact
alphanumeric string contained in the trade or service mark in which that Claimant has rights. Neither the Registry Operator nor we verified whether the TCF information provided by a Claimant is
accurate. Neither the Registry Operator nor we provide any warranties or guarantees in respect of that information. No restriction was placed on the number of Claimants that could file a TCF
for a given domain name. Accordingly, in some cases, there are multiple Claimants for a single domain name. If your domain name identically matches a trade or service mark string specified in a TCF,
any Claimant that filed such a TCF will be notified of this fact. The notification will provide the relevant details of your registration, including your contact details. In accordance with this
Policy and the Rules, those Claimants will have the right to challenge your domain name registration, subject to the challenge priority established by the Registry Operator. 

Proceedings
under Paragraph 4 of this Policy will be conducted according to the Rules for Start-up Dispute Resolution Policy (the "Rules"), which are available at
<URL>, and the selected administrative dispute resolution service provider's supplemental rules. 

2. Your Representations. By applying to register a domain name in the start-up period, you hereby represent and warrant to us that
(a) the statements that you made in your <.biz> Registration Agreement are complete and accurate; (b) to your knowledge, the domain name will not infringe upon or otherwise
violate the rights of any third party; (c) you are not registering the domain name for an unlawful purpose; and (d) you will not knowingly use the domain name in violation of any
applicable laws or regulations. It is your responsibility to determine whether your domain name registration infringes or violates someone else's rights. 

3. Cancellations, Transfers, and Changes. We will cancel, transfer or otherwise make changes to a domain name registration that is subject to this
Policy under the following circumstances: 

a.
subject to the provisions of Paragraph 8, our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action; and/or 

b.
our receipt of an order from a court or arbitral tribunal, in each case of competent jurisdiction, requiring such action; and/or 

c.
our receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party and which was conducted under this Policy or a later version of
this Policy adopted by ICANN. 

We
may also cancel, transfer or otherwise make changes to a domain name registration in accordance with the terms of the <.biz> Registration Agreement, ICANN Policy, or other legal
requirements. 

4.     Mandatory Administrative Proceeding.  

This
Paragraph sets forth the type of disputes for which you are required to submit to a mandatory administrative proceeding. These proceedings will be conducted before one of the administrative
dispute resolution service providers listed at www.icann.org/udrp/approved-providers.htm (each, a "Provider"). 

a. Applicable Disputes. You are required to submit to a mandatory administrative proceeding in the event that a Claimant asserts to the applicable
Provider, in compliance with the Rules, that: 

(i)
your domain name is identical to a trademark or service mark in which the Claimant has rights; and 

(ii)
you have no rights or legitimate interests in respect of the domain name; and 

(iii)
your domain name has been registered or is being used in bad faith. 

In
the administrative proceeding, the Claimant must prove that each of these three elements is present. 

b. Evidence of Registration or Use in Bad Faith. For the purposes of Paragraph 4(a)(iii), the following circumstances, in particular but without
limitation, if found by the Panel to be present, shall be considered evidence of the registration or use of a domain name in bad faith: 

(i)
circumstances indicating that you have registered the domain name primarily for the purpose of selling, renting, or otherwise transferring the domain name registration to the Claimant or to a
competitor of the Claimant, for valuable consideration in excess of your documented out-of-pocket costs directly related to the domain name; or 

(ii)
you have registered the domain name in order to prevent the Claimant from reflecting the mark in a corresponding domain name; or 

(iii)
you have registered the domain name primarily for the purpose of disrupting the business of a competitor; or 

(iv)
by using the domain name, you have intentionally attempted to attract, for commercial gain, Internet users to your web site or other on-line location, by creating a likelihood of
confusion with the Claimant's mark as to the source, sponsorship, affiliation, or endorsement of your web site or location or of a product or service on your web site or location. 

c. How to Demonstrate Your Rights to and Legitimate Interests in the Domain Name in Responding to a Complaint. When you receive a complaint, you should
refer to the Rules to determine how your response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be proved based on its
evaluation of all evidence presented, shall demonstrate your rights or legitimate interests to the domain name for purposes of Paragraph 4(a)(ii): 

(i)
You are the owner or beneficiary of a trade or service mark that is identical to the domain name; or 

(ii)
Before any notice to you of the dispute, your use of, or demonstrable preparations to use, the domain name or a name corresponding to the domain name in connection with a bona fide offering of
goods or services; or 

(iii)
you (as an individual, business, or other organization) have been commonly known by the domain name, even if you have acquired no trademark or service mark rights. 

d. Selection of Provider. The Claimant shall select the Provider from among those approved by ICANN by submitting the complaint to that Provider. The
selected Provider will administer the proceeding, except in cases of consolidation as described in Paragraph 4(f). 

e. Initiation of Proceeding and Process and Appointment of Administrative Panel. All disputes will be decided by a single Panelist, who shall be
appointed by the Provider. The Rules state the process for initiating and conducting a proceeding and for appointing the Sole Panelist that will decide the dispute (the "Administrative Panel"). 

f. Consolidation. In the event of multiple disputes between you and a Claimant, either you or the Claimant may petition to consolidate the disputes
before a single Administrative Panel. This petition shall be made to the first Administrative Panel appointed to hear a pending dispute between the parties. This Administrative Panel may consolidate
before it any or all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy or another dispute resolution policy adopted by ICANN. 

g. Fees. All fees charged by a Provider in connection with any dispute before an Administrative Panel pursuant to this Policy shall be paid by the
Claimant. 

h. Our Involvement in Administrative Proceedings. We do not, and will not, participate in the administration or conduct of any proceeding before an
Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by an Administrative Panel. 

i. Remedies. The remedies available to a Claimant pursuant to any proceeding before an Administrative Panel shall be limited to requiring the transfer
of your domain name registration to the Claimant. 

j. Notification and Publication. The Provider shall notify us and the Registry Operator of any decision made by an Administrative Panel with respect to
a domain name you have registered with us. All decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact
portions of its decision. 

k. Implementation of the Administrative Panel's Decision. If an Administrative Panel decides that your domain name registration should be transferred,
we will wait ten (10) business days (as observed in the location of our principal office) after we are informed by the applicable Provider of the Administrative Panel's decision before
implementing that decision. We will then implement the decision unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint,
file-stamped by the clerk of the court) that you have commenced a lawsuit against the Claimant in a jurisdiction to which the Claimant has submitted under Paragraph 3 of the Rules.
(In general, that jurisdiction is either the location of our principal office or of your address as shown in our Whois database.) If we receive such documentation within the ten (10) business
day period, we will not implement the Administrative Panel's decision, and we will take no further action, until we receive (i) evidence satisfactory to us of a resolution between the parties;
(ii) evidence satisfactory to us that your lawsuit has been dismissed or withdrawn; or (iii) a copy of an order from such court dismissing your lawsuit or ordering that you do not have
the right to continue to use your domain name. 

l. Multiple Challenges.

(i)
Your domain name may be the subject of multiple challenges by Claimants. In such event, the Registry Operator will be responsible for establishing the challenge priority among multiple claimants
on a randomized basis. 

(ii)
In the event that there is more than one challenger, the Administrative Panel shall decide, in light of its findings in respect of each of the elements identified in Paragraph 4(a),
whether any further challenges shall be permitted in respect of your domain name under this Policy. 

5. All Other Disputes and Litigation. All other disputes between you and any party other than us or the Registry Operator regarding your domain name
registration that are not brought pursuant to the mandatory administrative proceeding provisions of Paragraph 4 shall be resolved between you and such other party through any court, arbitration
or other proceeding that may be available, or the Uniform Domain Name Dispute Resolution Policy, as supplemented by the Registration Restrictions Dispute Resolution Criteria. 

6. Our Involvement in Disputes. We will not participate in any way in any dispute between you and any party other than us regarding the registration and
use of your domain name. You shall not name us as a party or otherwise include us in any such proceeding. In the event that we are named as a party in any such proceeding, we reserve the right to
raise any and all defenses deemed appropriate, and to take any other action necessary to defend ourselves. 

7. Maintaining the Status Quo. We will not cancel, transfer, activate, disactivate, or otherwise change the status of any domain name registration
subject to this Policy, except as provided in Paragraph 3 above. 

8. Transfers During a Dispute.

a. Transfers of a Domain Name to a New Holder. You may not transfer a domain name registration that is subject to this Policy to another holder until
all pending or prospective challenges pursuant to this Policy have been resolved, except that a transfer may be made to the Claimant in a pending administrative proceeding (e.g., in the event of a
settlement of the dispute). 

b. Changing Registrars. You may not transfer a domain name registration that is subject to this Policy to another registrar until all pending or
prospective challenges pursuant to this Policy have been resolved. 

9.     Policy Modifications.  

The
Registry Operator reserves the right to modify this Policy at any time with the permission of ICANN. We will post the revised Policy at <URL> at least fifteen (15) calendar days
before it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in which event the version of the Policy in effect at the time it was invoked
will apply to you until the dispute is over, all such changes will be binding upon you with respect to any domain name registration dispute, whether the dispute arose before, on or after the effective
date of the change. In the event that you object to a change in this Policy, your sole remedy is to cancel your domain name registration with us, provided that you will not be entitled to a refund of
any fees you paid to us. The revised Policy will apply to you until you cancel your domain name registration. 

 
 

Exhibit 2
  Rules for Start-up Dispute Resolution Policy
  (the "Rules")

Administrative
proceedings for the resolution of disputes pursuant to the Start-up Dispute Resolution Policy (<URL>) shall be governed by these Rules and any Supplemental Rules
of the dispute resolution service provider administering the proceedings, as posted at its web site. 

1.     Definitions  

In
these Rules: 

Complainant
means a party or the parties that submitted a Trademark Claim Form and which is/are challenging a domain name registration that is subject to the Start-up Intellectual Property
Notification Service. 

ICANN
refers to the Internet Corporation for Assigned Names and Numbers. 

Mutual
Jurisdiction means a court jurisdiction at the location of either (a) the principal office of the Registrar of the domain name in question, or (b) the domain name holder's
address, as shown for the registration of the domain name in the Registrar's Whois database at the time a complaint is submitted to a Provider. 

Panel
means the sole panelist appointed by a Provider to decide a complaint pursuant to the Policy. 

Party
means a Complainant or a Respondent. 

Policy
means the Start-up Dispute Resolution Policy that is incorporated by reference and made a part of the Registration Agreement. 

Provider
means a dispute resolution service provider approved by ICANN. A list of such Providers appears at http://www.icann.org/udrp/approved-providers.htm. 

Registrar
means the entity with which the Respondent has registered a domain name that is the subject of a complaint. 

Registration
Agreement means the agreement between a Registrar and a domain name holder. 

Registry
Operator means the registry operator for the <.biz> top-level domain. 

Respondent
means the holder of a domain name registration against which a complaint is initiated. 

Reverse
Domain Name Hijacking means using the Policy in bad faith to attempt to deprive a registered domain name holder of a domain name. 

Supplemental
Rules means the rules adopted by the Provider administering a proceeding to supplement these Rules. Supplemental Rules shall not be inconsistent with the Policy or these Rules. 

2.     Communications  

(a)
Any written communication to the Complainant or the Respondent required under these Rules shall be made by the means specified by the Complainant or the Respondent, respectively, or in the absence
of such specification: 

(i)
by facsimile with a confirmation of transmission; or 

(ii)
by postal or courier service, postage pre-paid and return receipt requested; or 

(iii)
electronically via the Internet, provided a record of its transmission is available. 

(b)
Any communication to the Provider or the Panel shall be made in accordance with the Provider's Supplemental Rules. 

(c)
All communications shall be made in the language prescribed in Paragraph 11. 

(d)
Either Party may update its contact details by notifying the other Party, the Provider and the Registrar. 

(e)
Except as otherwise provided in these Rules, or decided by a Panel, all communications provided for under these Rules shall be deemed to have been made: 

(i)
if delivered by facsimile transmission, on the date shown on the confirmation of transmission; or 

(ii)
if by postal or courier service, on the date marked on the receipt; or 

(iii)
if via the Internet, on the date that the communication was transmitted, provided that the date of transmission is verifiable. 

(f)
Except as otherwise provided in these Rules, all time periods calculated under these Rules shall begin to run on the earliest date that the communication is deemed to have been made in accordance
with Paragraph 2(e). 

(g)
Except as otherwise provided in these Rules, any communication by 

(i)
a Panel to any Party shall be copied to the Provider and to the other Party; 

(ii)
the Provider, following the commencement of an administrative proceeding pursuant to Paragraph 4(c), to any Party shall be copied to the other Party; and 

(iii)
a Party shall be copied to the other Party, the Panel and the Provider, as the case may be. 

(h)
It shall be the responsibility of the sender to retain records of the fact and circumstances of sending, which shall be available for inspection by affected parties and for reporting purposes. 

(i)
In the event that a Party sending a communication receives notification of non-delivery of the communication, that Party shall promptly notify the Provider of the circumstances of the
notification. 

3.     The Complaint  

(a)
A Complainant shall initiate an administrative proceeding under this Policy by: 

(i)
submitting its complaint to the Provider of its choice within twenty (20) calendar days of being notified by the Registry Operator of its challenge priority; and 

(ii)
registering the submission of its complaint with the Registry Operator. See instructions posted at (Registry Operator) <URL>. 

If
the Complainant fails to submit its complaint to a Provider or to complete its registration with the Registry Operator by the specified deadline, it shall be deemed to have forfeited its right to
challenge the domain name registration under this Policy. In any event, a Complainant shall as 

soon
as possible after receiving notification of its challenge priority advise the Registry Operator in writing of its election not to challenge the domain name registration under this Policy. 

(b)
The complaint shall be submitted in hard copy (with annexes) and in electronic form (without annexes). 

(c)
The complaint shall: 

(i)
Request that the complaint be submitted for decision in accordance with the Policy and Rules and describe why the domain name registration should be considered subject to the Policy; 

(ii)
Provide the full name, postal and e-mail addresses, and the telephone and telefax numbers of the Complainant and of any representative authorized to act for the Complainant in the
administrative proceeding; 

(iii)
Provide the Registry Account Number, the Registry Claim Number and the Challenge Priority Number provided by the Registry Operator; 

(iv)
Specify a preferred method for communications to the Complainant in the administrative proceeding (including person to be contacted, medium, and address information) for each of
(A) electronic-only material and (B) material including hard copy; 

(v)
Provide the full name of the Respondent and, if different from the contact details available in the Whois database for the domain name, provide all information known to the Complainant regarding
how to contact the Respondent or any representative of the Respondent, including contact information based on pre-complaint dealings; 

(vi)
Specify the domain name(s) that is/are the subject of the complaint; 

(vii)
Identify the Registrar(s) with whom the domain name(s) is/are registered at the time the complaint is filed; 

(viii)
Specify the trademark(s) or service mark(s) on which the complaint is based and, for each mark, describe the goods or services, if any, with which the mark is used (the Complainant may also
separately describe other goods and services for which it intends, at the time the complaint is submitted, to use the mark in the future); 

(ix)
Describe, in accordance with the Policy, the grounds on which the complaint is made including, in particular, 

(1)
the extent to which the domain name(s) is/are identical to a trademark or service mark in which the Complainant has rights; and 

(2)
why the Respondent should be considered as having no rights or legitimate interests in respect of the domain name(s) that is/are the subject of the complaint; and 

(3)
why the domain name(s) should be considered as having been registered or used in bad faith. 

(x)
Identify any other proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that is/are the subject of the complaint, including any such
proceedings under this Policy; 

(xi)
Identify the Mutual Jurisdiction to which the Complainant(s) will submit, with respect to any challenges to a decision in the administrative proceeding to transfer the domain name, as follows: 

"The
Complainant hereby designates [identify precisely the court jurisdiction] as the Mutual Jurisdiction, for the purposes of any challenges to a decision in the
administrative proceeding to cancel or transfer the domain name." 

(xii)
Conclude with the following statement followed by the signature of the Complainant or its authorized representative: 

"Complainant
agrees that its claims and remedies concerning the registration of the domain name, the dispute, or the dispute's resolution shall be solely against the domain name holder and waives all
such claims and remedies against (a) the dispute resolution service provider and the Administrative Panelist, except in the case of deliberate wrongdoing, (b) the registrar,
(c) the Registry Operator, and (d) the Internet Corporation for Assigned Names and Numbers, as well as their directors, officers, employees, and agents." 

"Complainant
certifies that the information contained in this Complaint is to the best of Complainant's knowledge complete and accurate, that this Complaint is not being presented for any improper
purpose, such as to harass, and that the assertions in this Complaint are warranted under the Start-up Dispute Resolution Policy, the Rules for Start-up Dispute Resolution
Policy and under applicable law, as it now exists or as it may be extended by a good-faith and reasonable argument."; and 

(xiii)
Annex any documentary or other evidence, including any trademark or service mark registration upon which the complaint relies and a schedule indexing such evidence. 

(d)
The complaint may relate to more than one domain name, provided that the domain names are registered by the same domain name holder and the Complainant has an equal challenge priority in respect
of each domain name that is the subject of the complaint. 

4.     Notification of Complaint  

(a)
The Provider shall review the complaint for formal compliance with the Policy and the Rules. If the complaint is found to be in compliance, the Provider shall notify it to the Respondent, in the
manner prescribed in Paragraph 2(a). For the purposes of notifying the complaint, the Provider shall not be required to use any contact details other than those available in the Whois database
for the domain name(s) in dispute. 

(b)
If the Provider finds the complaint to be formally deficient, it shall promptly notify the Complainant of the nature of the deficiencies identified. The Complainant shall have five
(5) calendar days within which to correct any such deficiencies, after which the administrative proceeding will be deemed terminated and the Complainant shall be deemed to have forfeited its
right to challenge the domain name registration under this Policy. 

(c)
The date of commencement of the administrative proceeding shall be the date the complaint is notified by the Provider to the Respondent. 

(d)
The Provider shall immediately notify the Complainant, the Respondent, the Registry Operator and ICANN of the date of commencement of the administrative proceeding. 

5.     The Response  

(a)
Within twenty (20) calendar days of the date of commencement of the administrative proceeding the Respondent shall submit a response to the Provider. 

(b)
The response shall be submitted in hard copy (with annexes) and in electronic form (without annexes). 

(c)
The response shall: 

(i)
Specifically respond to the statements and allegations contained in the complaint and include any and all bases for the Respondent to retain registration and use of the disputed domain name(s); 

(ii)
Provide the name, postal and e-mail addresses, and the telephone and telefax numbers of the Respondent and of any representative authorized to act for the Respondent in the
administrative proceeding; 

(iii)
Specify a preferred method for communications directed to the Respondent in the administrative proceeding (including person to be contacted, medium, and address information) for each of
(A) electronic-only material and (B) material including hard copy; 

(vi)
Identify any other proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that is/are the subject of the complaint, including any such
proceedings under the Policy; 

(vii)
Conclude with the following statement followed by the signature of the Respondent or its authorized representative: 

"Respondent
certifies that the information contained in this Response is to the best of Respondent's knowledge complete and accurate, that this Response is not being presented for any improper purpose
and that the assertions in this Response are warranted under the Start-up Dispute Resolution Policy, the Rules for Start-up Dispute Resolution Policy and under applicable law,
as it now exists or as it may be extended by a good-faith and reasonable argument."; and 

(viii)
Annex any documentary or other evidence upon which the Respondent relies, together with a schedule indexing such documents. 

(d)
At the request of the Respondent, the Provider may, in exceptional cases, extend the period of time for the filing of the response. The period may also be extended by written stipulation between
the Parties, provided the stipulation is approved by the Provider. 

(e)
If a Respondent does not submit a response, in the absence of exceptional circumstances, the Panel shall decide the dispute based upon the complaint. 

(f)
Where there are multiple Claimants in respect of a domain name registration, a Respondent that has already submitted a response, shall be entitled to rely on such response and, subject to the time
limits specified in Paragraph 5(a), to supplement any previously submitted response. 

6.     Appointment of the Panel and Timing of Decision  

(a)
Each Provider shall maintain and publish a publicly available list of panelists and their qualifications. 

(b)
The Provider shall appoint a single Panelist from its published list, taking into consideration such factors as the nationalities of the parties and the circumstances of the dispute. 

(c)
Once the Panel is appointed, the Provider shall notify the Parties of the Panelist appointed and the date by which, absent exceptional circumstances, the Panel shall forward its decision on the
complaint to the Provider. 

7.     Impartiality and Independence  

The
Panelist shall be impartial and independent and shall have, before accepting appointment, disclosed to the Provider any circumstances giving rise to justifiable doubt as to the Panelist's
impartiality or independence. If, at any stage during the administrative proceeding, new circumstances arise that could give rise to justifiable doubt as to the impartiality or independence of the
Panelist, that Panelist shall promptly disclose such circumstances to the Provider. In such event, the Provider shall have the discretion to appoint a substitute Panelist in accordance with
Paragraph 6. 

8.     Communication Between Parties and the Panel  

No
Party or anyone acting on its behalf may have any unilateral communication with the Panel. 

9.     Transmission of the File to the Panel  

The
Provider shall forward the case file as soon as the Administrative Panel is appointed. 

10.   General Powers of the Panel  

(a)
The Panel shall conduct the administrative proceeding in such manner as it considers appropriate in accordance with the Policy and the Rules. 

(b)
In all cases, the Panel shall ensure that the Parties are treated with equality and that each Party is given a fair opportunity to present its case. 

(c)
The Panel shall ensure that the administrative proceeding takes place with due expedition. It may, at the request of a Party or on its own motion, extend, in exceptional cases, a period of time
fixed by the Rules or by the Panel. 

(d)
The Panel shall determine the admissibility, relevance, materiality and weight of the evidence. 

(e)
A Panel shall decide a request by a Party to consolidate multiple domain name disputes in accordance with the Policy and the Rules. 

11.   Language of Proceedings  

(a)
Unless otherwise agreed by the Parties, or specified otherwise in the Registration Agreement, the language of the administrative proceeding shall be the language of the Registration Agreement,
subject to the authority of the Provider or the Panel, as the case may be, to determine otherwise, having regard to the circumstances of the administrative proceeding. 

(b)
The Panel may order that any documents submitted in languages other than the language of the administrative proceeding be accompanied by a translation in whole or in part into the language of the
administrative proceeding. 

12.   Further Statements  

In
addition to the complaint and the response, the Panel may request, in its sole discretion, further statements or documents from either of the Parties. 

13.   In-Person Hearings  

There
shall be no in-person hearings (including hearings by teleconference, videoconference, and web conference), unless the Panel determines, in its sole discretion and as an exceptional
matter, that such a hearing is necessary for deciding the complaint. 

14.   Default  

(a)
In the event that a Party, in the absence of exceptional circumstances, does not comply with any of the time periods established by the Rules or the Panel, the Panel shall proceed to a decision on
the complaint. 

(b)
If a Party, in the absence of exceptional circumstances, does not comply with any provision of, or requirement under, the Rules or any request from the Panel, the Panel shall draw such inferences
therefrom as it considers appropriate. 

15.   Panel Decisions  

(a)
A Panel shall decide a complaint on the basis of the statements and documents submitted and in accordance with the Policy, these Rules and any rules and principles of law that it deems applicable. 

(b)
In the absence of exceptional circumstances, the Panel shall forward its decision on the complaint to the Provider within fourteen (14) calendar days of its appointment. 

(c)
The Panel's decision shall be in writing, provide the reasons on which it is based, indicate the date on which it was rendered and identify the name of the Panelist. 

(d)
If the Panel concludes that the dispute is not within the scope of Paragraph 4(a) of the Rules, it shall so state. If after considering the submissions the Panel finds that the complaint
was brought in an attempt at Reverse Domain Name Hijacking the Panel shall state its findings to this effect in its decision. 

(e)
In the event that there are multiple Complainants, each Panel shall specify in its decision whether any subsequent challenges against the domain name(s) that is/are the subject of the Panel's
decision shall be permitted. 

16.   Communication of Decision to Parties  

(a)
Within three (3) business days (as observed at the Provider's principal place of business) after receiving the decision from the Panel, the Provider shall endeavor to communicate the full
text of the decision to each Party, the Registry Operator and ICANN. 

(b)
In the event of a determination in favor of the Complainant, the Registry Operator shall immediately communicate to each Party the date for the implementation of the decision in accordance with
the Policy and any action required by the Parties in connection therewith. 

(c)
Except if the Panel determines otherwise, the Provider shall publish the full decision and the date of its implementation on a publicly accessible web site. In any event, the portion of any
decision determining a complaint to have been brought in bad faith shall be published. 

(d)
In the event of multiple Complainants, the Registry Operator shall be responsible for communicating the Panel's decision to all Complainants, including specifying whether a further challenge has
been authorized by the Panel. 

17.   Settlement or Other Grounds for Termination  

(a)
If, the Complainant notifies the Provider or the Panel that the Parties have agreed on a settlement, the Provider or the Panel, as the case may be, shall suspend or terminate the administrative
proceeding. 

(b)
If, it becomes unnecessary or impossible to continue the administrative proceeding for any other reason, the Provider or Panel, as the case may be, shall terminate the administrative proceeding,
unless a Party raises justifiable grounds for objection within a period of time to be determined by the Provider or Panel. 

18.   Fees  

(a)
The Complainant shall pay to the Provider an initial fixed fee, in accordance with the Provider's Supplemental Rules, within the time and in the amount required. 

(b)
The Provider shall be under no obligation to take any action on a complaint until it has received from the Complainant the initial fee in accordance with Paragraph 18(a). 

(c)
If the Provider has not received the fee within ten (10) calendar days of receiving the complaint, the Provider shall have the discretion to terminate the administrative proceeding and the
Complainant shall be deemed to have forfeited its right to challenge the domain name registration pursuant to the Policy. 

(d)
In exceptional circumstances, the Provider shall be entitled to request payment of additional fees. 

19.   Exclusion of Liability  

Except
in the case of deliberate wrongdoing, neither the Provider nor a Panelist shall be liable to a Party for any act or omission in connection with any administrative proceeding under the Policy
and the Rules. 

20.   Amendments  

The
version of these Rules in effect at the time of the submission of the complaint to the Provider shall apply to the administrative proceeding commenced thereby. These Rules may not be amended
without the express written approval of ICANN. 

 
 

Exhibit 3
  Restrictions Dispute Resolution Policy    
    

1. Purpose. This Restrictions Dispute Resolution Policy (the "RDRP") is incorporated by reference into your <.biz>Registration Agreement. It
sets out the terms and conditions that will apply in the event of a dispute between you (as the registrant) and a third party other than us (as the registrar) or the registry administrator for the
<.biz> top-level domain over the registration or use of your domain name in violation of the <.biz> Registration Restrictions (available at http://<URL>).
Proceedings under Paragraph 4 of the RDRP will be conducted according to the Supplemental Rules for Restrictions Dispute Resolution Policy (the "Supplemental RDRP Rules"), which are available
at <http://www.icann.org/{filename}>, and the selected administrative dispute resolution service provider's supplemental rules. 

2. Your Representations. By applying to register a domain name, or by asking us to maintain or renew a domain name registration, you hereby represent
and warrant to us that (a) the statements that you made in your Registration Agreement are complete and accurate; (b) to your knowledge, the registration of the domain name will not
infringe upon or otherwise violate the rights of any third party; (c) you are not registering the domain name for an unlawful purpose; (d) you will not knowingly use the domain name in
violation of any applicable laws or regulations; (e) your domain name registration does not and will not violate the terms and conditions of the <.biz> Registration Restrictions. It
is your responsibility to determine whether your domain name registration infringes or violates someone else's rights. It is also your responsibility to determine whether your domain name registration
violates the <.biz> Registration Restrictions. 

3. Cancellations, Transfers and Changes. We will cancel, transfer or otherwise make changes to domain name registrations under the following
circumstances: 

(a)
subject to the provisions of Paragraph 8, our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action; 

(b)
our receipt of an order from a court or arbitral tribunal, in each case of competent jurisdiction, requiring such action; and/or 

(c)
our receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party and which was conducted under the RDRP or a later version of
the RDRP adopted by ICANN. 

We
may also cancel, transfer or otherwise make changes to a domain name registration in accordance with the terms of your <.biz> Registration Agreement, ICANN policy, or other legal
requirements. 

4.     Mandatory Administrative Proceeding.  

This
Paragraph sets forth the type of disputes for which you are required to submit to a mandatory administrative proceeding. These proceedings will be conducted before one of the administrative
dispute resolution service providers listed at www.icann.org/udrp/approved-providers.htm (each, a "Provider"). 

a. Applicable Disputes. In addition to the grounds set out in Paragraph 4(a) of the UDRP, you will also be required to submit to a mandatory
administrative proceeding in the event that a complainant asserts to a Provider that your domain is not being or will not be used primarily for a bona fide business or commercial purpose. In the
administrative proceeding, the complainant will bear the burden of proving that the above element is present. A complaint under the RDRP will not be considered valid if based exclusively on the
alleged non-use of your domain name. 

b. Bona Fide Business or Commercial Use. "Bona fide business or commercial use" shall mean the bona fide use or bona fide intent to use the domain name
or any content software, materials, graphics or other information thereon, to permit Internet users to access one or more host computers through the DNS: 

(i)
to exchange goods, services, or property of any kind; or 

(ii)
in the ordinary course of trade or business; or 

(iii)
to facilitate the exchange of goods, services, information, or property of any kind or the ordinary course of trade or business. 

c. Not a Bona Fide Business or Commercial Use. Registering a domain name solely for the purposes identified below shall not constitute a "bona fide
business or commercial use" of that domain name: 

(i)
selling, trading or leasing the domain name for compensation, or 

(ii)
the unsolicited offering to sell, trade or lease the domain name for compensation. 

(iii)
For illustration purposes, the following shall not constitute a "bona fide business or commercial use" of a domain name: 

(1)
Using or intending to use the domain name exclusively for personal, noncommercial purposes; or 

(2)
Using or intending to use the domain name exclusively for the expression of noncommercial ideas (e.g., registering <abcsucks.biz>exclusively to criticize or otherwise express an opinion
on the products or services of ABC company, with no other intended business or commercial purpose). 

d. Selection of Provider. The complainant shall select the Provider from among those approved by ICANN by submitting the complaint to that Provider. The
selected Provider will administer the proceeding, except in cases of consolidation as described in Paragraph 4(f). 

e. Initiation of Proceeding and Process and Appointment of Administrative Panel. The Supplemental RDRP Rules state the process for initiating and
conducting a proceeding and for appointing the panel that will decide the dispute (the "Administrative Panel"). 

f. Consolidation. In the event of multiple disputes between you and a complainant, either you or the complainant may petition to consolidate the
disputes before a single Administrative Panel. This petition shall be made to the first Administrative Panel appointed to hear a pending dispute between the parties. This Administrative Panel may
consolidate before it any or all such disputes in 

its
sole discretion, provided that the disputes being consolidated are governed by the RDRP or another dispute resolution policy adopted by ICANN. 

g. Fees. All fees charged by a Provider in connection with any dispute before an Administrative Panel pursuant to the RDRP shall be paid by the
complainant, except in cases where you elect to expand the Administrative Panel from one to three panelists as provided in the Supplemental RDRP Rules, in which case all fees will be split evenly by
you and the complainant. 

h. Our Involvement in Administrative Proceedings. We do not, and will not, participate in the administration or conduct of any proceeding before an
Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel. 

i. Remedies. The remedies available to a complainant pursuant to any proceeding before an Administrative Panel shall be limited to requiring the
cancellation of your domain name or the transfer of your domain name registration to the complainant. 

j. Notification and Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domain name you have
registered with us. All decisions under the RDRP will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact portions of its decision. 

k. Availability of Court Proceedings. The mandatory administrative proceeding requirements set forth in Paragraph 4 shall not prevent either you
or the complainant from submitting the dispute to a court of competent jurisdiction for independent resolution before such mandatory administrative proceeding is commenced or after such proceeding is
concluded. If an Administrative Panel decides that your domain name registration should be canceled or transferred, we will wait ten (10) business days (as observed in the location of our
principal office) after we are informed by the applicable Provider of the Administrative Panel's decision before implementing that decision. We will then implement the decision unless we have received
from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you have commenced a lawsuit
against the complainant in a jurisdiction to which the complainant has submitted under the Supplemental RDRP Rules. (In general, that jurisdiction is either the location of our principal office or of
your address as shown in our Whois database.) If we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, and we will
take no further action, until we receive (i) evidence satisfactory to us of a resolution between
the parties; (ii) evidence satisfactory to us that your lawsuit has been dismissed or withdrawn; or (iii) a copy of an order from such court dismissing your lawsuit or ordering that you
do not have the right to continue to use your domain name. 

5. All Other Disputes and Litigation. All other disputes between you and any party other than us regarding your domain name registration that are not
brought pursuant to the mandatory administrative proceeding provisions of Paragraph 4 shall be resolved between you and such other party through any court, arbitration or other proceeding that
may be available. 

6. Our Involvement in Disputes. We will not participate in any way in any dispute between you and any party other than us regarding the registration and
use of your domain name. You shall not name us as a party or otherwise include us in any such proceeding. In the event that we are named as a party in any such proceeding, we reserve the right to
raise any and all defenses deemed appropriate, and to take any other action necessary to defend ourselves. 

7. Maintaining the Status Quo. We will not cancel, transfer, activate, deactivate, or otherwise change the status of any domain name registration under
the RDRP except as provided in Paragraph 3 above. 

8.     Transfers During a Dispute.  

a. Transfers of a Domain Name to a New Holder. You may not transfer your domain name registration to another holder (i) during a pending
administrative proceeding brought pursuant to 

Paragraph 4
or for a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; or (ii) during a
pending court proceeding or arbitration commenced regarding your domain name unless the party to whom the domain name registration is being transferred agrees, in writing, to be bound by the decision
of the court or arbitrator. We reserve the right to cancel any transfer of a domain name registration to another holder that is made in violation of this subparagraph. 

b. Changing Registrars. You may not transfer your domain name registration to another registrar during a pending administrative proceeding brought
pursuant to Paragraph 4 or for a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding
is concluded. You may transfer administration of your domain name registration to another registrar during a pending court action or arbitration, provided that the domain name you have registered with
us shall continue to be subject to the proceedings commenced against you in accordance with the terms of the RDRP. In the event that you transfer a domain name registration to us during the pendency
of a court action or arbitration, such dispute shall remain subject to the domain name dispute policy of the registrar from which the domain name registration was transferred. 

9. Policy Modifications. We reserve the right to modify the RDRP at any time with the permission of ICANN. We will post the revised RDRP at
<URL> at least thirty (30) calendar days before it becomes effective. Unless this version of the RDRP has already been invoked by the submission of a complaint to a Provider, in
which event the version of the RDRP in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any domain name
registration dispute, whether the dispute arose before, on or after the effective date of our change. In the event that you object to a change in this version of the RDRP, your sole remedy is to
cancel your domain name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised RDRP will apply to you until you cancel your domain name
registration. 

 
 

Exhibit 4
  Supplemental Rules for
  Restrictions Dispute Resolution Policy    
    

1. Purpose. Administrative proceedings for the resolution of disputes under the Restrictions Dispute Resolution Policy ("RDRP"; <URL>) shall
be governed by the Rules for Uniform Domain Name Dispute Resolution Policy ("UDRP Rules"; <URL>) as supplemented or modified by these Supplemental Rules for Restrictions Dispute Resolution
Policy (the "Supplemental RDRP Rules") and any supplemental rules of the dispute resolution service provider administering the proceedings. 

2. Definitions. Defined terms in the UDRP Rules shall have the same meaning in these Supplemental RDRP Rules, subject to the following: 

(a)
Complaint based on UDRP and RDRP. If a complaint is based on the UDRP and the RDRP, the term "Policy" shall refer to the Uniform Domain Name Dispute Resolution Policy ("UDRP") and the RDRP, and
the term "Rules" shall refer to the UDRP Rules as supplemented or modified by these Supplemental RDRP Rules. 

(b)
Complaint based on the RDRP alone. If a complaint is based on the RDRP alone, the term "Policy" shall refer to the RDRP, and the term "Rules" shall refer to the UDRP Rules as supplemented or
modified by these Supplemental RDRP Rules. 

3. RDRP Grounds. A complaint pursuant to the RDRP (whether or not also based on the UDRP) shall describe, in accordance with Paragraph 4(a)-(c),
the grounds on which the complaint is made including, in particular, the extent to which the domain name is not being or will not be used primarily for a bona fide business or commercial purpose. 

APPENDIX N  

 
 

Zone File Access Agreement  
  

1.     PARTIES  

The
User named in this Agreement hereby contracts with [name of Registry Operator]
("[nickname of Registry Operator]") for a non-exclusive, non-transferable, limited right to access an
Internet host server or servers designated by [nickname of Registry Operator] from time to time, and to transfer a copy of the
described Data to the User's Internet host machine specified below, under the terms of this Agreement. Upon execution of this Agreement by [nickname of Registry
Operator], [nickname of Registry Operator] will return a copy of this Agreement to you for
your records with your UserID and Password entered in the spaces set forth below. 

2.     USER INFORMATION  

	

 	
 	

(a) User:	
 	

	

 	
 	

(b) Contact Person:	
 	

	

 	
 	

(c) Street Address:	
 	

	

 	
 	

(d) City, State or Province:	
 	

	

 	
 	

(e) Country and Postal Code:	
 	

	

 	
 	

(f) Telephone Number:	
 	

	 	 	(including area/country code)

	

 	
 	

(g) Fax Number:	
 	

	 	 	(including area/country code)

	

 	
 	

(h) E-Mail Address:	
 	

	

 	
 	

(i) Specific Internet host machine which will be used to access [nickname of Registry Operator]'s server to transfer copies of the Data:

	

 	
 	

 	
 	

 
	 	 	Name:	 	

	

 	
 	

IP Address:	
 	

	

 	
 	

(j) Purpose(s) for which the Data will be used: During the term of this Agreement, you may use the data for any legal purpose, not prohibited under Section 4 below. You may incorporate some or all of the Data in your own products or services,
and distribute those products or services for a purpose not prohibited under Section 4 below.

3.     TERM  

This
Agreement is effective for a period of three (3) months from the date of execution by [nickname of Registry
Operator] (the "Initial Term"). Upon conclusion of the Initial Term this Agreement will automatically renew for successive three-month renewal terms (each a
"Renewal Term") until terminated by either party as set forth in Section 12 of this Agreement or one party provides the other party with a written notice of termination at least seven
(7) days prior to the end of the Initial Term or the then current Renewal Term. 

NOTICE
TO USER: CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS. YOU MAY USE THE USER ID AND ASSOCIATED PASSWORD PROVIDED IN CONJUNCTION WITH THIS AGREEMENT ONLY TO OBTAIN A COPY OF
[TLD label] TOP-LEVEL DOMAIN ("TLD") ZONE FILES, AND ANY ASSOCIATED ENCRYPTED CHECKSUM FILES (COLLECTIVELY THE
"DATA"), VIA THE FILE TRANSFER PROTOCOL ("FTP") OR HYPERTEXT TRANSFER PROTOCOL ("HTTP") PURSUANT TO THESE TERMS. 

4.     GRANT OF ACCESS  

[Nickname of Registry Operator] grants to you a non-exclusive, non-transferable, limited right to access
an Internet host server or servers designated by [nickname of Registry Operator] from time to time, and to transfer a copy of
the Data to the Internet host machine identified in Section 2 of this Agreement no more than once per 24 hour period using FTP or HTTP for the purposes described in this
Section 4. You agree that you will: 

(a)  use
this Data only for lawful purposes but that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission by
e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than your own existing customers; or (2) enable high volume,
automated, electronic processes that send queries or data to the systems of [nickname of Registry Operator] or any
ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. [Nickname of Registry
Operator] reserves the right, with the approval of the Internet Corporation for Assigned Names and Numbers ("ICANN"), to specify additional specific categories of
prohibited uses by giving you reasonable written notice at any time and upon receiving such notice you shall not make such prohibited use of the Data you obtain under this Agreement. 

(b)  copy
the Data you obtain under this Agreement into a machine-readable or printed form only as necessary to use it in accordance with this Agreement in support of your use of the Data. 

(c)  comply
with all applicable laws and regulations governing the use of the Data. 

(d)  not
distribute the Data you obtained under this Agreement or any copy thereof to any other party without the express prior written consent of
[nickname of Registry Operator], except that you may redistribute the Data insofar as it has been incorporated by you into a
value-added product or service that does not permit the extraction of a substantial portion of the Data from the value-added product or service, provided you prohibit the recipient of the Data from
using the Data in a manner contrary to Section 4(a). 

(e)  take
all reasonable steps to protect against unauthorized access to, use, and disclosure of the Data you obtain under this Agreement. 

5.     FEE  

You
agree to remit in advance to [nickname of Registry Operator] a quarterly fee of $0 (USD) for the right to access the files
during either the Initial Term or Renewal Term of this Agreement. [Nickname of Registry Operator] reserves the right to adjust,
with the approval of ICANN, this fee on thirty days prior notice to reflect a change in the cost of providing access to the files. 

6.     PROPRIETARY RIGHTS  

You
agree that no ownership rights in the Data are transferred to you under this Agreement. You agree that any copies of the Data that you make will contain the same notice that appears on and in the
Data obtained under this Agreement. 

7.     METHOD OF ACCESS  

[Nickname of Registry Operator] reserves the right, with the approval of ICANN, to change the method of access to the Data at
any time. You also agree that, in the event of
significant degradation of system processing or other emergency, [nickname of Registry Operator] may, in its sole discretion,
temporarily suspend access under this Agreement in order to minimize threats to the operational stability and security of the Internet. 

8.     NO WARRANTIES  

The
Data is being provided "as-is." [Nickname of Registry Operator] disclaims all warranties with respect to the Data, either expressed or implied, including but
not limited to the implied warranties of 

merchantability,
fitness for a particular purpose, and non-infringement of third party rights. Some jurisdictions do not allow the exclusion of implied warranties or the exclusion or
limitation of incidental or consequential damages, so the above limitations or exclusions may not apply to you. 

9.     SEVERABILITY  

In
the event of invalidity of any provision of this Agreement, the parties agree that such invalidity shall not affect the validity of the remaining provisions of this Agreement. 

10.   NO CONSEQUENTIAL DAMAGES  

In
no event shall [nickname of Registry Operator] be liable to you for any consequential, special, incidental or indirect
damages of any kind arising out of the use of the Data or the termination of this Agreement, even if [nickname of Registry
Operator] has been advised of the possibility of such damages. 

11.   GOVERNING LAW  

This
Agreement shall be governed and construed in accordance with the laws of [home jurisdiction of Registry Operator]. You
agree that any legal action or other legal proceeding relating to this Agreement or the enforcement of any provision of this Agreement shall be brought or otherwise commenced in the
[specify local court]. You expressly and irrevocably agree and consent to the personal jurisdiction and venue of the federal and
state courts located [home jurisdiction of Registry Operator] (and each appellate court located therein) for matters arising in
connection with this Agreement or your obtaining, use, or distribution of the Data. The United Nations Convention on Contracts for the International Sale of Goods is specifically disclaimed. 

12.   TERMINATION  

You
may terminate this Agreement at any time by erasing the Data you obtained under this Agreement from your Internet host machine together with all copies of the Data and providing written notice of
your termination to [nickname of Registry Operator] at [address of Registry
Operator]. [Nickname of Registry Operator] has the right to terminate this Agreement
immediately if you fail to comply with any term or condition of this Agreement. You agree upon receiving notice of such termination of this Agreement by [nickname
of Registry Operator] or expiration of this Agreement to erase the Data you obtained under this Agreement together with all copies of the Data. 

13.   DEFINITION  

"Data"
means all data contained in a DNS zone file for the Registry TLD as provided to TLD nameservers on the Internet. 

14.   ENTIRE AGREEMENT  

This
is the entire agreement between you and [nickname of Registry Operator] concerning access and use of the Data, and it
supersedes any prior agreements or understandings, whether written or oral, relating to access and use of the Data. 

	[Full name of Registry Operator]	 	User:
	

By:

(sign)	
 	

By:

(sign)
	

Name:

(print)	
 	

Name:

(print)
	

Title:	
 	

Title:
	

Date:	
 	

Date:

ASSIGNED USERID AND PASSWORD  

(To
be assigned by [nickname of Registry Operator] upon execution of this Agreement): 

	USERID:	 	PASSWORD:

APPENDIX O  

 
 

Whois Specification—Public Whois  
  

NeuLevel
will provide RFC954-conformant Whois service. NeuLevel will also provide an enhanced "Whois" service. This Appendix is subject to change by agreement of Registry Operator and
ICANN during the design process as well as during the IETF standards process. However, the following provides the target architecture and initial functionality. 

RFC954-Conformant Whois  

The
standard Whois service is intended as a lookup service for registries, registrars, registrants, as well as for other individuals and businesses that wish to query details of domain names or
nameservers stored in the registry. Being a fat-registry, the standard Whois service will provide a central location for all authoritative.biz TLD data. Registrars will be able to provide
a front-end web interface to the standard Whois service. In addition, the Registry provides its own front-end web interface to allow convenient user access to the Whois
service. 

Due
to the nature of the NeuLevel fat- (thick-)registry model, the RFC954-conformant Whois service will be engineered to handle high transaction load and be integral to the
standard suite of registry services. The service will return a single response per domain name or nameserver query. The RFC954-conformant Whois service will conform to established service
level agreements. 

The
RFC954-conformant service provided by the registry will have the following features: 

	•
	Standard
protocol accessible over port 43. 
	•
	Consistent
format (fields and formatting) for all registrars. 
	•
	Near
real-time updates, eliminating "timing" problems when modifying registry information. 
	•
	Extensible
field capability. 

Whois Service Data Elements  

The
RFC954-conformant service will include the following data elements: 

	•
	The
name of the domain name registered; 
	•
	The
IP addresses of the primary nameserver and secondary nameserver(s) of the name registered; 
	•
	The
corresponding names of those nameservers; 
	•
	The
identity of the registrar; 
	•
	The
original creation date and term of the registration; 
	•
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the domain name registrant; 
	•
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the technical contact for the name registered; and 
	•
	The
name, postal address, e-mail address, voice telephone number, and (where available) fax number of the administrative contact for the name registered. 

Extensible-Field Capability  

NeuLevel
will introduce the ability for registrars to use XRP to add customized fields to a record in the registry database. These fields will appear in an "additional information" section of the
Whois data. The maximum number of custom fields allowed per record is yet to be determined. 

The
extensible-field capability will eliminate the need for registrars to store additional information in their own local database, then combine it with the registry Whois information when they
present it to end users. The proposed capability will also ensure that end users will view the same information no matter which registrar they use to retrieve Whois data. 

Privacy Capability  

NeuLevel
may introduce the optional ability for registrars to use XRP to associate privacy labels to a record in the registry database. These fields would appear in an "additional information" section
of the Whois data. The maximum number of custom fields allowed per record is yet to be determined. 

The
privacy label capability allows registrars to transmit data with an associated indication of any special disclosure or handling restrictions. This can allow exchange of data among entities
involved in the domain-name registration system in a manner that permits consistent adherence to applicable restrictions. 

Query Control—Object Type Control  

The
following keywords restrict a search to specific object type: 

Domain:  Search only by domain objects. The input string is searched in the Name field. 

Contact:  Search only contact objects. The input string is searched in the ID field. 

Nameserver:  Search only by nameserver objects. The input string is searched in the nameserver field or the IP address field. 

Registrar:  Search only registrar objects. The input string is searched in the Name field. 

By
default, if no object type control is specified, then the Name field of the Domain object is searched. 

Whois Output Fields  

Domain Record:  

A
Whois query that results in domain information will return the following fields from the Domain object and the associated data from host and contact objects. This set of data is also referred to as
the Domain Record. 

Domain
ID

Domain Name

Sponsoring Registrar

Domain Status

Registrant, Administrative, Technical and Billing Contact

Information including

        Contact ID

        Contact Name

        Contact Organization

        Contact Address, City, State/Province, Country

        Contact Postal Code

        Contact Phone, Fax, E-mail

Name Servers associated with this domain

Created by Registrar

Last Updated by Registrar

Last Transferred Date

Additional fields (registrar specified)

Domain Registration Date

Domain Expiration Date

Domain Last Updated Date 

Note:
For domains on PendingDelete Status, the Registry's front-end web interface will provide an additional explanation of the status as follows: 

	Up to 30 days after deletion:	 	Pending Delete (Restorable)
	

More than 30 days after deletion:	
 	

Pending Delete (Scheduled for release)

Nameserver
Record: 

Nameserver
ID

Nameserver name

Currently Associated (true/false)

Nameserver status

IP addresses associated

Sponsoring Registrar

Created by Registrar

Last Updated by Registrar

Last Transferred Date

Additional fields (registrar specified) 

Contact Record:  

A
Whois query that results in contact information will return the following. This set of information is referred to as the Contact Record. 

Contact
ID

Contact Registrar

Contact Name

Contact Organization

Contact Address, City, State/Province, Country + 3 street fields

Contact Postal Code

Contact Phone, Fax, E-mail

Contact Registration Date

Contact Last Updated Date

Currently Associated

Contact Status

Sponsoring Registrar

Created Registrar

Last Transferred Date 

Registrar Record:  

A
Whois query that results in Registrar information will return the following. This set of information is referred to as the Registrar Record. 

Registrar
ID (conforming to the IANA registrar-ids registry)

Registrar Name

Registrar Status

Registrar Address, City, State/Province, Country

Registrar Postal Code

Registrar Phone, Fax, E-mail

Registrar Administrative Contacts

Registrar Billing Contacts 

Sample Whois Output  

This
section provides sample output from the Whois server for each type of Registry Object: Domain, Contact, Nameserver, and Registrar. The output is structured as key/value pairs, which simplifies
machine-readability. 

Domain Record:  

	 	 	Input:	 	whois "domain = neulevel.biz"
	 	 	Output:	 	Domain ID: DOM-1012
	 	 	 	 	Domain Name: NEULEVEL.BIZ
	 	 	 	 	Sponsoring Registrar: SAMPLE
	 	 	 	 	Domain Status: ACTIVE
	 	 	 	 	Registrant Name: JEFFREY J. NEUMAN
	 	 	 	 	Registrant Organization: NEULEVEL, INC.
	 	 	 	 	Registrant Address: 1120 VERMONT AVE., NW
	 	 	 	 	Registrant City: WASHINGTON
	 	 	 	 	Registrant State/Province: DC
	 	 	 	 	Registrant Country: USA
	 	 	 	 	Registrant Postal Code: 20005
	 	 	 	 	Registrant Phone Number: (202) 533-2600
	 	 	 	 	Registrant Facsimile Number: (202) 533-2970
	 	 	 	 	Registrant Email: JEFF.NEUMAN@NEULEVEL.BIZ
	 	 	 	 	Admin ID: CNT-1012
	 	 	 	 	Admin Name: JEFFREY J. NEUMAN
	 	 	 	 	Admin Organization: NEULEVEL, INC.
	 	 	 	 	Admin Address: 1120 VERMONT AVE., NW
	 	 	 	 	Admin City: WASHINGTON
	 	 	 	 	Admin State/Province: DC
	 	 	 	 	Admin Country: USA
	 	 	 	 	Admin Postal Code: 20005
	 	 	 	 	Admin Phone Number: (202) 533-2600
	 	 	 	 	Admin Facsimile Number: (202) 533-2970
	 	 	 	 	Admin Email: JEFF.NEUMAN@NEULEVEL.BIZ
	 	 	 	 	Tech ID: CNT-1012
	 	 	 	 	Tech Name: JEFFREY J. NEUMAN
	 	 	 	 	Tech Organization: NEULEVEL, INC.
	 	 	 	 	Tech Address: 1120 VERMONT AVE., NW
	 	 	 	 	Tech City: WASHINGTON
	 	 	 	 	Tech State/Province: DC
	 	 	 	 	Tech Country: USA
	 	 	 	 	Tech Postal Code: 20005
	 	 	 	 	Tech Phone Number: (202) 533-2600
	 	 	 	 	Tech Facsimile Number: (202) 533-2970
	 	 	 	 	Tech Email: JEFF.NEUMAN@NEULEVEL.BIZ
	 	 	 	 	Billing ID: CNT-1012
	 	 	 	 	Billing Name: JEFFREY J. NEUMAN
	 	 	 	 	Billing Organization: NEULEVEL, INC.
	 	 	 	 	Billing Address: 1120 VERMONT AVE., NW
	 	 	 	 	Billing City: WASHINGTON
	 	 	 	 	Billing State/Province: DC
	 	 	 	 	Billing Country: USA
	 	 	 	 	Billing Postal Code: 20005
	 	 	 	 	Billing Phone Number: (202) 533-2600
	 	 	 	 	 

	 	 	 	 	Billing Facsimile Number: (202) 533-2970
	 	 	 	 	Billing Email: JEFF.NEUMAN@NEULEVEL.BIZ
	 	 	 	 	Name Server: ENTERPRISE.MELBOURNEIT.COM.AU
	 	 	 	 	Name Server: DEFIANT.MELBOURNEIT.COM.AU
	 	 	 	 	Created On: May 5, 2001
	 	 	 	 	Expires On: May 5, 2003
	 	 	 	 	Updated On: May 5, 2001

Contact Record: 

	 	 	Input:	 	whois "contact = Jeff Neuman"
	 	 	Output:	 	Contact ID: CNT-1012
	 	 	 	 	Registrar: SAMPLE
	 	 	 	 	Name: JEFFREY J. NEUMAN
	 	 	 	 	Organization: NEULEVEL, INC.
	 	 	 	 	Address: 1120 VERMONT AVE, NW
	 	 	 	 	City: WASHINGTON
	 	 	 	 	State: DC
	 	 	 	 	Country: USA
	 	 	 	 	Postal Code: 20005
	 	 	 	 	Phone Number: (202) 533-2600
	 	 	 	 	Facsimile Number (202) 533-2970
	 	 	 	 	E-mail: JEFF.NEUMAN@NEULEVEL.BIZ
	 	 	 	 	Created On: MAY 5, 2001
	 	 	 	 	Updated On: MAY 5, 2001

Nameserver Record: 

	 	 	Input:	 	whois "nameserver dns1.neulevel.biz"
	 	 	Output:	 	Nameserver ID: HST-9
	 	 	 	 	Nameserver name: dns1.NEULEVEL.BIZ
	 	 	 	 	Currently Associated (true/false):T
	 	 	 	 	Nameserver status: ACTIVE
	 	 	 	 	IP addresses associated: 24.6.0.1
	 	 	 	 	Sponsoring Registrar: SAMPLE
	 	 	 	 	Created by Registrar: SAMPLE
	 	 	 	 	Last Updated by Registrar: May 5, 2001
	 	 	 	 	Last Transferred Date: May 5, 2001
	 	 	 	 	Additional fields (registrar specified)

Registrar Record: 

	 	 	Input:	 	whois "registrar SAMPLE"
	 	 	Output:	 	Registrar ID: REG-42
	 	 	 	 	Registrar Name: SAMPLE
	 	 	 	 	Registrar Status: ACTIVE
	 	 	 	 	Registrar Address 1: 424 Fifth Street
	 	 	 	 	Registrar Address 2:
	 	 	 	 	Registrar City: FARGO
	 	 	 	 	Registrar State/Province: ND
	 	 	 	 	Registrar Country: USA
	 	 	 	 	Registrar Postal Code: 12345
	 	 	 	 	Registrar Phone: (888) 555-1212
	 	 	 	 	Registrar E-mail: jn24601@sample.biz
	 	 	 	 	Admin Contact Name: Jean Valjean
	 	 	 	 	 

	 	 	 	 	Admin Contact Phone: (888) 555-1212
	 	 	 	 	Admin Contact E-mail: jn24601@sample.biz
	 	 	 	 	Billing Contact Name: Jean Valjean
	 	 	 	 	Billing Contact Phone: (888) 555-1212
	 	 	 	 	Billing Contact E-mail: jn24601@sample.biz

Enhanced Whois Service  

NeuLevel
will also provide a Whois-like directory service intended for intellectual property owners. This service will provide multiple responses to queries and allow
sub-string and boolean searches. The registry will provide access to a subset of the enhanced Whois functionality fee exempt, and additional functionality will be provided on a for fee
basis. 

This
service is intentionally separated from the standard Whois service due to the high transaction loads that will be placed on the standard service due to the fat-registry model, and
requirement to meet service level agreements. While the RFC954-conformant Whois service will be updated in near real-time, there is no need for the enhanced service to have
this requirement due to the nature of it's users. The enhanced service will not be required to conform to service level agreements, so the registry can be more liberal enabling enhanced functionality
that places additional load on the enhanced services infrastructure. The maximum update latency of the enhanced service will be 24 hours after updates to the core registry database are
received. 

The
registry will continue consultation with the Intellectual Property Constituency of the DNSO in ICANN and similar interested groups to maximize the utility of the enhanced Whois service. However at
a minimum the enhanced service will provide the following functionality: 

Functionality exempt from fee:  

	•
	Exact-match
search on registrant name, returning first 75 matching records. 

Functionality incurring fee:  

	•
	Exact-match
search on domain name. 
	•
	Exact-match
search on registrant name. 
	•
	Sub-string
search on domain name. 
	•
	Multi-field
search involving sub-string searches on both domain name and registrant name fields. 
	•
	Boolean
searches. For example: ((xxx AND yyy) OR zzz). 

APPENDIX P  

 
 

Whois Provider Data Specification  
  

Registry
Operator will provide bulk access to up-to-date data concerning domain name and nameserver registrations maintained by Registry Operator in connection with the
Registry TLD on a daily schedule, only for purposes of providing free public query-based access to up-to-date data concerning domain name and nameserver registrations in
multiple TLDs, to a party designated from time to time in writing by ICANN (the "Designated Recipient"). 

The
procedures for providing access, and the specification of the content and format of this data, will be as stated below, until changed according to the Registry Agreement. This Appendix is subject
to change by agreement of Registry Operator and ICANN during the design process as well as during the IETF standards process. In addition, Registry Operator agrees to implement changes to this
Appendix sepcified by ICANN to conform to the IETF provreg working group's protocol specification no later than 135 days after the IETF specification is adopted as a Proposed Standard
[RFC 2026, section 4.1.1]. Accordingly, the following provides the target architecture and initial functionality. 

A.  Procedures for Providing Access  

The
Registry Operator will prepare (i) full data sets for one day of each week (the day to be designated by ICANN) and (ii) incremental data sets for all seven days of each week. Full
and incremental data sets shall be up-to-date and coherent as of 1200 UTC on the day to which they relate. Until a different day is designated by ICANN, the full data sets will
be prepared for Sundays. (Note that on the ICANN-designated day both an incremental and a full data set are prepared.) 

1.  Preparation of Files Containing Data Sets. Each full and incremental data set consists of an XML document meeting the content and format
requirements of Parts B and C of this document. Once the XML document is generated, the following preparation steps will be performed: 

a.  The
XML document will be placed in a file named according to the following convention: 

For
full data sets: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single-digit number should be left-padded
with a zero). 

For
incremental data sets: "wiYYMMDD" where "YYMMDD" follows the same format. 

b.  The
Registry Operator may optionally split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split,
an MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors in case of transfer fault. The Registry Operator may optionally compress the document using
the Unix GZIP command (or equivalent) to reduce the filesize. 

c.  The
file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow
file in addition to encrypting it.) The Data Recipient's public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be
exchanged between the Registry Operator and the Designated Recipient by e-mail, physical delivery of floppy diskettes, or other agreed means. 

2.  Transmission of Full Data Sets. Once prepared, full data sets will be provided either by the procedures for incremental data sets
described in item A(3) below or, at the option of either the Registry Operator or the Designated Recipient, by writing the full data set to DAT tape (or other media mutually agreed by Registry
Operator and the Designated Recipient) and sending it to the Designated Recipient by expedited delivery service (such as FedEx or DHL). If sent by expedited delivery service, the full data set will be
scheduled for arrival no later than the second calendar day following the day to which the full backup relates. 

3.  Transmission of Incremental Data Sets. To permit the transmission of incremental data sets, the Registry Operator will make them
available for download by the Designated Recipient by Internet File Transfer Protocol. Incremental data sets will be made available for download no later than 20:00 UTC on the day to which they
relate. 

B.  Content  

The
data sets (whether full or incremental) will consist of four types of objects: 

1.  Domain objects. One type of object is the domain object, which corresponds to a single Registered Name. Each domain object includes the
following data: 

Domain
ID

Domain Name

Sponsoring Registrar (IANA-assigned identifier)

Domain Status

Registrant, Administrative, Technical and Billing

Contact Information including

        Contact ID

        Contact Name

        Contact Organization

        Contact Address, City, State/Province, Country

        Contact Postal Code

        Contact Phone, Fax, E-mail

Name Servers associated with this domain

Created by Registrar (IANA-assigned identifier)

Last Updated by Registrar (IANA-assigned identifier)

Last Transferred Date

Additional fields (registrar specified)

Domain Registration Date

Domain Expiration Date

Domain Last Updated Date 

2.  Nameserver objects. A second type of object is the nameserver object, which corresponds to a single registered nameserver. The
nameserver object includes the following data: 

Nameserver
ID

Nameserver Name

IP Addresses associated

Sponsoring Registrar(IANA-assigned identifier)

Created by Registrar (IANA-assigned identifier)

Name Server Last Updated by Registrar (IANA-assigned identifier)

Last Transferred Date 

3.  Contact objects. A third type of object is the contact object, which corresponds to a single contact (whether registrant,
administrative, technical or billing contact). The contact object includes the following data: 

Contact
ID

Contact Name

Contact Organization

Contact Address, City, State/Province, Country

Contact Postal Code

Contact Phone, Fax, E-mail

Contact Registration Date

Contact Last Updated Date

Currently Associated

Contact
Status

Sponsoring Registrar (IANA-assigned identifier)

Created Registrar (IANA-assigned identifier)

Last Transferred Date 

4.  Registrar object. The final type of object corresponds to a single registrar. It includes the following data: 

Registrar
ID (conforming to the IANA registrar-ids registry)

Registrar Name

Registrar Status

Registrar Address, City, State/Province, Country

Registrar Postal Code

Registrar Phone, Fax, E-mail

Registrar Administrative Contacts

Registrar Billing Contacts 

5.  Objects Contained in Full and Incremental Data Sets. Full data sets include one domain object for each Registered Name within the
Registry TLD; and nameserver, contact, and registrar objects for each nameserver, contact, and registrar referred to in any domain object. Incremental data sets consist of (a) those of the
objects constituting a full data set that have been added or updated since the last incremental data set and (b) notations of deletion of any objects since the last incremental data set. 

C.  Format  

Full
and incremental data sets will be XML version 1.0, UTF-8 encoded documents conforming to the following document type definition: 

<?xml
version="1.0"?> 

<schema
targetNamespace="urn:neulevel:whoisdb"

    xmlns="http://www.w3.org/2000/10/XMLSchema"

    xmlns:whoisdb="urn:neulevel:whoisdb"

    xmlns:eppcom="urn:iana:xml:ns:eppcom"

    xmlns:epp="urn:iana:xml:ns:epp"

    xmlns:contact="urn:iana:xml:ns:contact"

    xmlns:domain="urn:iana:xml:ns:domain"

    xmlns:host="urn:iana:xml:ns:host"

    elementFormDefault="qualified"> 

<!—Import
EPP Element Types—>

<import namespace="urn:iana:xml:ns:eppcom" schemaLocation="eppcom.xsd"/>

<import namespace="urn:iana:xml:ns:epp" schemaLocation="epp.xsd"/>

<import namespace="urn:iana:xml:ns:contact" schemaLocation="contact.xsd"/>

<import namespace="urn:iana:xml:ns:domain" schemaLocation="domain.xsd"/>

<import namespace="urn:iana:xml:ns:host" schemaLocation="host.xsd"/> 

<annotation>

    <documentation>XML Schema for Whois Data Escrow From NeuLevel

    </documentation>

</annotation> 

<!—Child
Element—>

<element name="whois-data" type="whoisdb:whoisDbType"/> 

<complexType
name="whoisDbType">

    <choice>

        <element name="full" type="whoisdb:fullsetType"/>

        <element name="incremental" type="whoisdb:partialType"/>

    </choice>

    <attribute name="tld" type="whoisdb:tldType" use="required"/>

    <attribute name="date" type="timeInstant" use="required"/>

</complexType> 

<simpleType
name="tldType">

    <restriction base="string">

        <enumeration value="biz"/>

    </restriction>

</simpleType> 

<complexType
name="fullsetType">

    <sequence>

        <element name="contact" type="contact:infDataType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="domain" type="domain:infDataType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="host" type="host:infDataType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="registrar" type="whoisdb:registrarType" minOccurs="0" maxOccurs="unbounded"/>

    </sequence>

</complexType> 

<complexType
name="partialType">

    <sequence>

        <element name="contact" type="contact:infDataType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="domain" type="domain:infDataType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="host" type="host:infDataType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="registrar" type="whoisdb:registrarType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="del-contact" type="contact:sIDType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="del-domain" type="domain:sNameType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="del-host" type="host:sNameType" minOccurs="0" maxOccurs="unbounded"/>

        <element name="del-registrar" type="whoisdb:registrarIDType" minOccurs="0" maxOccurs="unbounded"/>

    </sequence>

</complexType> 

<complexType
name="registrarIDType">

    <sequence>

        <element name="registrar-id" type="eppcom:clIDType"/>

    </sequence>

</complexType> 

<!—Registrar
Type derived from XRP Specification—>

<complexType name="registrarType">

    <sequence>

        <element name="roid" type="eppcom:roidType"/>

        <element
name="registrar-id" type="eppcom:clIDType"/>

        <element name="name" type="whoisdb:registrarNameType"/>

        <element name="address" type="contact:addrType"/>

        <element name="web-url" type="whoisdb:registrarWebUrlType"/>

        <element name="iana-id" type="whoisdb:registrarIanaIDType"/>

        <element name="contact" type="whoisdb:registrarContactType" maxOccurs="5"/>

        <element name="status" type="whoisdb:registrarStatusType"/>

        <element name="crDate" type="timeInstant"/>

        <element name="upDate" type="timeInstant" minOccurs="0"/>

    </sequence>

</complexType> 

<simpleType
name="registrarNameType">

    <restriction base="string">

        <minLength value="1"/>

        <maxLength value="128"/>

    </restriction>

</simpleType> 

<simpleType
name="registrarWebUrlType">

    <restriction base="string"/>

</simpleType> 

<simpleType
name="registrarIanaIDType">

    <restriction base="string"/>

</simpleType> 

<complexType
name="registrarContactType">

    <simpleContent>

        <extension base="eppcom:roidType">

            <attribute name="type" use="required">

                <simpleType>

                    <restriction base="string">

                        <enumeration value="administrative"/>

                        <enumeration value="billing"/>

                        <enumeration value="technical"/>

                    </restriction>

                </simpleType>

            </attribute>

        </extension>

    </simpleContent>

</complexType> 

<simpleType
name="registrarStatusType">

    <restriction base="string">

        <enumeration value="active"/>

        <enumeration value="suspended"/>

        <enumeration value="defunct"/>

    </restriction>

</simpleType> 

</schema>

APPENDIX Q  

 
  Whois Specification—ICANN  
  

Registry
Operator will provide bulk access by ICANN to up-to-date data concerning domain name and nameserver registrations maintained by Registry Operator in connection with
the Registry TLD on a daily schedule, only for purposes of verifying and ensuring the operational stability of Registry Services, the DNS, and the Internet. 

The
procedures for providing access, and the specification of the content and format of this data, will be as stated below, until changed according to the Registry Agreement. This Appendix is subject
to change by agreement of Registry Operator and ICANN during the design process as well as during the IETF standards process. In addition, Registry Operator agrees to implement changes to this
Appendix specified by ICANN to conform to the IETF provreg working group's protocol specification no later than 135 days after the IETF specification is adopted as a Proposed Standard
[RFC 2026, section 4.1.1]. Accordingly, the following represents the target architecture and initial functionality. 

A. Procedures for Providing Access  

The
Registry Operator will prepare a full data set once each week (the day to be designated by ICANN). Full data sets shall be up-to-date and coherent as of 1200 UTC on the day
to which they relate. Until a different day is designated by ICANN, the full data sets will be prepared for Sundays. 

1. Preparation of Files Containing Data Sets. Each full data set consists of an XML document meeting the content and format requirements of Parts B and
C of this document. Once the XML document is generated, the following preparation steps will be performed: 

a.
The XML document will be placed in a file names according to the following convention: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day;
in all cases a single-digit number should be left-padded with a zero). 

b.
Registry Operator may optionally split the document using the Unix SPLIT command (or equivalent) to produce files no less than 1GB each (except the final file). If files are split, an MD5 file
(produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors. The Registry Operator may optionally compress the document using the Unix GZIP command (or equivalent)
to reduce the filesize. 

c.
The file(s) will then be encrypted and signed using PGP, version 6.5.1 or above, with a key of DH/DSS type and 2048/1024-byte length. (Note that PGP compresses the escrow file in
addition to encrypting it.) An ICANN public key will be used for the encryption and the Registry Operator's private key will be used for the signature. Public keys will be exchanged between the
Registry Operator and ICANN by e-mail, physical delivery of floppy diskettes, or other agreed means. 

2. Transmission of Full Data Sets. Once prepared, full data sets will be provided according to paragraph a below or, at Registry Operator's
option, according to paragraph b below: 

a.
Registry Operator will make full data sets available for download by ICANN by Internet File Transfer Protocol (FTP). (FTP access will be password protected and limited to prespecified IP ranges.)
The data sets will be made available for download beginning no later than 2000 UTC on the day to which they relate and until the next full data set becomes available for download. 

b.
Registry Operator will write the full data set to DAT (DDS-4) tape (or other media specified by ICANN) and send it to ICANN by expedited delivery service (such as FedEx or DHL). The
full data set will be scheduled for arrival at ICANN no later than the fourth calendar day following the day to which the data set relates. 

B. Content  

The
full data sets will consist of the objects and contents described for full data sets in Part B of Appendix P. 

C. Format  

Full
data sets will be XML version 1.0, UTF-8 encoded documents conforming to the schema/document type declaration set forth in Part C of Appendix P. 

APPENDIX R  

 
  Data Escrow Schedule, Content, Format, and Procedure  
  

This
Appendix R to the Registry Agreement consists of four of the five exhibits to the Service Level Agreement that constitutes Appendix S to the Registry Agreement: 

Exhibit A—Schedule
for Escrow Deposits 

Exhibit B—Escrow
Deposit Format Specification 

Exhibit C—Escrow
Transfer Process 

Exhibit D—Escrow
Verification Procedures 

The
fifth exhibit (Exhibit E) to Appendix S, which sets forth the escrow agent's fees, is subject to negotiation between Registry Operator and the escrow agent. 

 
 

Exhibit A—Schedule for Escrow Deposits

1. Procedures for Providing Access. The Registry Operator will prepare (i) full data sets for one day of each week (the day to be designated by
ICANN) and (ii) incremental data sets for all seven days of each week. Full and incremental data sets shall be up-to-date and coherent as of 1200 UTC on the day to which
they relate. Until a different day is designated by ICANN, the full data sets will be prepared for Sundays. 

2. Preparation of Files Containing Data Sets. Each full and incremental data set consists of an XML document meeting the content and format requirements
of Exhibit B of this document. Once the XML document is generated, the following preparation steps will be performed: 

The
XML document will be placed in a file named according to the following convention: 

For
full data sets: "wfYYMMDD" where "YYMMDD" is replaced with the date (YY=last two digits of year; MM=number of month; DD=day; in all cases a single-digit number should be left-padded
with a zero). 

For
incremental data sets: "wiYYMMDD" where "YYMMDD" follows the same format. 

3. Start Date for Escrow Procedures. Registry Operator and ICANN shall cooperate in resolving implementation issues, an escrow agent shall be selected,
and an escrow agreement shall be entered in time for escrow deposits to begin within ninety days after the Commencement-of-Service Date. 

 
 

Exhibit B—Escrow Deposit Format Specification

This
Appendix is subject to change by agreement of Registry Operator and ICANN during the design process as well as during the IETF standards process. In addition, Registry Operator agrees to
implement changes to this Appendix sepcified by ICANN to conform to the IETF provreg working group's protocol specification no later than 135 days after the IETF specification is adopted as a
Proposed Standard [RFC 2026, section 4.1.1]. Accordingly, the following provides the target architecture and initial functionality. 

The
escrow data sets (whether full or incremental) will consist of four types of objects: 

	•
	Domain
object

	•
	Nameserver
object

	•
	Contact
object

	•
	Registrar
object 

Additionally,
incremental data sets will contain notations of deletion of objects since the last incremental data set. 

1. The Domain Object. The domain object which corresponds to a single registered name consists of the following elements: 

Domain
ID

Domain Name

Sponsoring Registrar

Domain Status

Registrant Identifier

Contact Identifiers for Administrative, Technical and Billing

Contacts

Name Servers associated with this domain

Child Name Servers registered in this domain

Domain Created by Registrar

Domain Last Updated by Registrar

Domain Registration Date

Domain Expiration Date

Domain Last updated

Date Domain Last TransferDate

Domain Authorization Information

Additional Fields (Registrar Specified) 

2. The Name Server Object. The nameserver object which corresponds to a single registered nameserver consists of the following elements: 

Name
Server ID

Name Server Name

Name Server Status

Name Server Association Status

Name Server IP Addresses if applicable

Sponsoring Registrar

Created by Registrar

Name Server Creation Date

Name Server Last Updated Date

Name Server Last Transfer Date

Additional fields (Registrar Specified)

Name Server Authorization Information 

3. The Contact Object. The contact object, which corresponds to a single contact (whether registrant, administrative, technical or billing contact)
consists of the following elements: 

Contact
ID

Contact Name

Contact Status

Contact Association Status

Contact Organization

Contact Address, City, State/Province, Country

Contact Postal Code

Contact Phone, Fax, E-mail

Sponsoring Registrar

Created by Registrar

Contact Creation Date

Contact Last Updated Date

Contact Last Transfer Date

Contact Authorization Information

Additional fields (Registrar Specified) 

4. The Registrar Object. The registrar object, which corresponds to a single registrar consists of the following elements: 

Registrar
ID (registry specific)

Registrar Object Identifier (Unique object Identifier)

Registrar ID (conforming to the IANA registrar-ids registry)

Contact ID of Registrar

Registrar Name

Registrar Address, City, State/Province, Country

Registrar Administrative Contacts

Registrar Technical Contacts

Registrar Billing Contacts

Registrar URL

Registrar Creation Date

Registrar Last Updated Date

Registrar Authorization Information

Registrar Account Information 

Additionally,
incremental data sets will contain notations of deletion of objects since the last incremental data set. These notations of object deletion are defined as follows: 

	Name of element
 
	 	Type of element

	Del-domain	 	domain:sNameType
	Del-nameserver	 	host:sNameType
	Del-contact	 	contact:sIDType
	Del-registrar	 	whoisdb:registrarIDType

Objects Contained in Full and Incremental Data Sets. Full data sets include one domain object for each Registered Name within the Registry TLD; and
nameserver, contact, and registrar objects for each nameserver, contact, and registrar referred to in any domain object. Incremental data sets consist of:(a) those of the objects constituting a full
data set that have been added or updated since the last incremental data set and (b)notations of deletion of any objects since the last incremental data set. 

Format. Full and incremental data sets will be XML version 1.0, UTF-8 encoded documents. The XML Schema definition for the objects and their
notations of deletion will be specified after discussions between ICANN and Registry Operator. The format will be based on the Whois provider format specified in Appendix P, Section C
"Format", but will be augmented to include all data elements reasonably necessary to permit operation of the Registry Services for the Registry TLD in the event the escrow data is released. In the
event that ICANN and Registry Operator do not agree on the escrow format, ICANN shall reasonably specify that format. 

 
 

Exhibit C—Escrow Transfer Process

Deposit Transfer Process. Registry Operator shall prepare and transfer the Deposit file by the following steps, in sequence: 

1.
The file(s) making up the Deposit will first be created according to the format specification. (See Exhibit B above, "Escrow Deposit Format Specification"). The resulting file shall be named
according to the following format: "bizSEQN", where "SEQN" is a four digit decimal number that is incremented as each report is prepared. 

2.
Next, the Deposit file will be processed by a program (provided by ICANN) that will verify that it complies with the format specification and contains reports of the same date/time (for a Full
Deposit), count the number of objects of the various types in the Deposit, and append to the file a report of the program's results. 

3.
Registry Operator may optionally split the resulting file using the Unix SPLIT command (or equivalent) to produce files no less than 1 GB each (except the final file). If Deposit files are split, 

an
MD5 file (produced with MD5SUM or equivalent) must be included with the resulting files to isolate errors. 

4.
The file(s) will then be encrypted and signed using a method mutually agreed by the Registry Operator and the Designated Data Recipient. 

5.
Transmission of Full Data Sets. Once prepared, full data sets will be provided either by the procedures for incremental data sets described in item C(6) below or, at the option of either the
Registry Operator or the Designated Recipient, by writing the full data set to DAT tape (or other media mutually agreed by Registry Operator and the Designated Recipient) and sending it to the
Designated Recipient by expedited delivery service (such as FedEx or DHL). If sent by expedited delivery service, the full data set will be scheduled for arrival no later than the second calendar day
following the day to which the full backup relates. 

6.
Transmission of Incremental Data Sets. To permit the transmission of incremental data sets, the Registry Operator will make them available for download by the Designated Recipient by Internet file
transfer protocol. Incremental data sets will be made available for download no later than 2000 UTC on the day to which they relate. 

 
 

Exhibit D—Escrow Verification Procedures

Verification Procedures. Escrow Agent will verify the format and completeness of each Deposit by the following steps: 

1.
At the conclusion of the deposit window, all Deposit files will be moved to a not-publicly-accessible directory and the existence and size of each will be noted. 

2.
The file(s) will then be decrypted using a method mutually agreed by the Registry Operator and the Escrow agent. 

3.
If there are multiple files, they will be concatenated in sequence. 

4.
Escrow Agent will run a program on the Deposit file (without report) that will split it in to its constituent reports (including the format report prepared by the Registry Operator and appended to
the Deposit) check its format, count the number of objects of each type, and verify that the data set is
internally consistent. This program will compare its results with the results of the Registry-generated format report, and will generate a Deposit format and completeness report. 

5.
The decrypted Deposit file will be encrypted by the program using a method mutually agreed by the Registry Operator and the Escrow agent. 

6.
The decrypted Deposit file will be destroyed to reduce likelihood of data loss to intruders in case of partial security failure. 

Distribution Of Public Keys. Each of Registry Operator and Escrow Agent will distribute its public key to the other party (Registry Operator or Escrow
Agent, as the case may be), confirm receipt by a method mutually agreed by both the parties. 

APPENDIX S  

 
  Registry Data Escrow Agreement  
  

This
Registrar Data Escrow Agreement ("Agreement") is made as of this [enter date] (the "Beginning Date"), by and between
[name of Registry Operator] ("Registry Operator"), [name of Escrow
Agent] ("Escrow Agent"), and the Internet Corporation for Assigned Names and Numbers ("ICANN"). All capitalized terms not defined herein shall have the meaning set
forth in the Registry Agreement. All capitalized terms not defined in this Agreement have the meanings set forth in the Registry Agreement. 

 
 

RECITALS    
    

A.
Registry Operator and ICANN have entered into a Registry Agreement dated [insert date of Registry Agreement] ("Registry
Agreement"), which requires Registry Operator, during the term of the Registry Agreement, to submit certain domain name registration data to a reputable escrow agent to be held in escrow. 

B.
Pursuant to the Registry Agreement, Registry Operator intends to deliver periodically to Escrow Agent an electronic copy of the Registry Database, as detailed in Subsection 3.11 of the Registry
Agreement (each such delivery referred to as a "Deposit"). 

C.
Registry Operator desires Escrow Agent to hold each Deposit, and, upon certain events, release any retained Deposits (or a copy of the Deposits) to ICANN, in accordance with the terms of this
Agreement or as ordered by a court of competent jurisdiction. 

Now,
therefore, in consideration of the premises and mutual obligations contained herein and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged,
the parties agree as follows: 

 
 

AGREEMENT    
    

1.
Content of Deposits. Deposits will be of two kinds: Full Deposits and Incremental Deposits. Each Full Deposit will consist of Registry Data that
reflects the current and complete Registry Database. Incremental Deposits will consist of data that reflects all transactions involving the database that are not reflected in the last previous Full
Deposit or Incremental Deposit, as the case may be. 

2.
Schedule for Deposits. Registry Operator must create and deliver to Escrow Agent a Full Deposit once each week, according to the schedule specified
in Exhibit A of Appendix R. Registry Operator must create and deliver to Escrow Agent an Incremental Deposit once each day during which a Full Deposit is not made, according to the
schedule specified in Exhibit A of Appendix R. 

3.  Format of Deposits. The data in each Full Deposit and in each Incremental Deposit shall follow the data format specified in the TLD Registry Data
Escrow: Format Specification (the "Format Specification"), attached as Exhibit B of Appendix R. 

4.
Procedure for Deposits. Each properly formatted Full Deposit and Incremental Deposit shall be processed and electronically delivered in encrypted
form to Escrow Agent according to the transfer process described in Exhibit C of Appendix R. 

5.
Notification of Deposits. Simultaneous with the delivery to Escrow Agent of any Full or Incremental Deposit, Registry Operator shall deliver to
Escrow Agent and to ICANN a written statement (which may be by authenticated e-mail) that includes a copy of the report generated upon creation of the Full or Incremental Deposit by the
ICANN-provided software (as described in Exhibit A) and states that the Full or Incremental Deposit (as the case may be) has been inspected by Registry Operator according to the procedures
described in Exhibit C of Appendix R and is complete and accurate. Escrow Agent shall notify ICANN of all Deposits received, within two business days of receipt. 

6.
Verification. Within two business days after receiving each Full or Incremental Deposit, Escrow Agent shall verify the format and completeness of
each Deposit by performing the verification procedures 

specified
in Exhibit D of Appendix R and shall deliver to ICANN a copy of the verification report generated for each Deposit (which may be by authenticated e-mail). If Escrow
Agent discovers that any Deposit fails the verification procedures, Escrow Agent shall notify, including by email, fax and phone, Registry Operator and ICANN of such nonconformity within forty-eight
hours of discovery. Upon notification of such verification failure, Registry Operator shall begin developing modifications, updates, corrections, and other fixes of the Full or Incremental Deposit
necessary for the Deposit to pass the verification procedures and shall deliver such fixes to Escrow Agent as promptly as possible. Escrow Agent shall verify the accuracy or completeness of any such
corrected Deposit pursuant to the procedures in this Section 6 and shall give ICANN notice of successful verification within twenty-four hours. The failure of any Full or
Incremental Deposit to meet verification procedures and any efforts by Registry Operator to remedy such failure shall not delay the delivery of any subsequent scheduled Full or Incremental Deposits
pursuant to the schedule in Exhibit A of Appendix R. Escrow Agent shall deliver, on the first business day of each month, (i) a written certification to ICANN that Escrow Agent
has performed such verification procedures on each Deposit received during the last month, and (ii) copies of the verification reports generated for each Deposit received during the last month. 

7.  Retention and Confidentiality. 

7.1  Retention. Escrow Agent shall hold and maintain the Deposits in a secure, locked, and environmentally safe facility which is accessible only to
authorized representatives of Escrow Agent. Escrow Agent shall use commercially reasonable efforts to protect the integrity of the Deposits. Each of ICANN and Registry Operator shall have the right to
inspect Escrow Agent's written records with respect to this Agreement upon reasonable prior notice and during normal business hours. 

7.2
Destruction of Deposits. At all times, Escrow Agent shall retain the four most recent Full Deposits and all Incremental Deposits after the earliest
of those four Full Deposits, all of which must have passed the verification procedures specified in Exhibit D of Appendix R. Registry Operator may destroy any Deposits prior to these
four most recent Full Deposits. 

7.3
Confidentiality. Escrow Agent shall use commercially reasonable efforts to protect the confidentiality of the Deposits. Except as provided in this
Agreement, Escrow Agent shall not disclose, transfer, make available, or use any Deposit (or any copies of any Deposit). Should Escrow Agent be put on notice that it is required to disclose any
Deposits by statute, rule, regulation, order, or other requirement of a governmental agency, legislative body, court of competent jurisdiction, or binding arbitral body (other than any requirement
pursuant to Sections 9.6, 11, and 13 of this Agreement), Escrow Agent shall notify ICANN and Registry Operator within seven days or as soon as practicable and reasonably cooperate with Registry
Operator and/or ICANN in any contest of the disclosure. Should any contest
prove unsuccessful, Escrow Agent shall not be held liable for any disclosure pursuant to such governmental, legislative, judicial, or arbitral order, statute, rule, regulation, or other requirement. 

8.
Duplication. Escrow Agent may duplicate any Deposit by any commercially reasonable means in order to comply with the terms and provisions of this
Agreement, provided that Registry Operator shall bear the expense of such duplication. Alternatively, Escrow Agent, by notice to Registry Operator, may reasonably require Registry Operator to promptly
duplicate any Deposit. 

9.  Release of Deposit to ICANN. Within five business days after receipt of any required documents and/or notices specified in this Section 9,
Escrow Agent shall deliver to ICANN all Deposits in Escrow Agent's possession, in the event that the Escrow Agent receives all of the following: 

9.1
One of the following notices: 

9.1.1
A written notice by the Registry Operator requesting Escrow Agent to effect such delivery to ICANN; or 

9.1.2
A written notice by ICANN that the Registry Agreement has: (i) expired without renewal, pursuant to Subsection 5.1 of the Registry Agreement, or (ii) been terminated, pursuant to
Subsection 5.4 of the Registry Agreement; or 

9.1.3
A written notice by ICANN that all of the following have occurred: 

9.1.3.1
ICANN failed, with respect to (a) any Full Deposit or (b) five Incremental Deposits within any calendar month, to receive, within five calendar days after the Deposit's scheduled
delivery date, to receive notification of receipt from Escrow Agent; and 

9.1.3.2
ICANN gave notice to Escrow Agent and Registry Operator of that failure; and 

9.1.3.3
ICANN has not, within seven calendar days after the notice under Section 9.2.3.2, received notice from Escrow Agent that the Deposit has been received; or 

9.1.4
A written notice by ICANN that all of the following have occurred: 

9.1.4.1
ICANN has received notification from Escrow Agent of failed verification of a Full Depositor of failed verification of five Incremental Deposits within any calendar month; and 

9.1.4.2
ICANN gave notice to Registry Operator of that receipt; and 

9.1.4.3
ICANN has not, within seven calendar days after the notice under Section 9.1.4.2, received notice from Escrow Agent of verification of a remediated version of the Deposit; or 

9.1.5
A written notice by ICANN that release of the Deposits is mandated by non-payment of any fees due to Escrow Agent, pursuant to Section 15 of this Agreement; or 

9.1.6
A written notice by ICANN that a court, arbitral, legislative, or government agency that ICANN finds to be of competent jurisdiction has issued an order, rule, statute, regulation, or other
requirement (a copy of which ICANN has provided to Registry Operator) that mandates the release of the Deposits to ICANN; and 

9.2
Evidence satisfactory to Escrow Agent that ICANN or Registry Operator (whichever gave the notice under Section 9.1) has previously notified the other party in writing; and 

9.3
Written instructions from ICANN that the Deposits be released and delivered to ICANN; and 

9.4
A written undertaking by ICANN that the Deposits will be used only as permitted under the terms of the Registry Agreement. Upon release of any Deposits to ICANN, Escrow Agent shall at the same
time deliver to Registry Operator a photostatic copy of the notice it received from ICANN under Sections 9.1.2 to 9.1.6, as applicable. 

10.  Release of Deposit to Registry Operator. Escrow Agent shall deliver all Deposits to Registry Operator upon termination of this Agreement in
accordance with Sections 14.1 and 14.2.1 of this Agreement. 

11.
Procedure After Release. 

11.1
Right to Use Deposits. Upon release of any Deposits to ICANN pursuant to Section 9, ICANN shall immediately have the right to exercise or
have exercised all rights in the Deposits necessary to provide registry services, as detailed in Section 3.13 of the Registry Agreement, except that ICANN shall not deliver Deposits released
pursuant to Sections 9.1.3, 9.1.4, or 9.1.5 to a third party for use so long as (a) the Registry Agreement is in effect, (b) Registry Operator is providing Registry Services in
conformity with the requirements of the Registry Agreement, and (c) Registry Operator provides Deposits directly to ICANN according to the Exhibits A, B, and C of Appendix R (modified to
make ICANN rather than Escrow Agent the recipient), and the Deposits pass the verification procedures specified in Exhibit D of Appendix R. 

11.2
Objection Notice. Upon release of any Deposits to ICANN pursuant to Sections 9.1.2 through 9.1.6, Registry Operator shall have thirty calendar days
to notify Escrow Agent and ICANN in writing (the "Objection Notice") of its objection to the release of the Deposits to ICANN and request that the issue of entitlement to the Deposits be resolved
pursuant to the dispute resolution procedures in Subsection 5.9 of the Registry Agreement (the "Dispute Resolution Procedures"). Registry Operator and ICANN agree to resolve any disputes they may have
as between themselves hereunder, including any objections to release of the Deposits pursuant to Sections 9.1.2 thru 9.1.6, solely through the Dispute Resolution Procedures. The parties agree that the
delivery of an Objection Notice and the commencement of Dispute Resolution Procedures shall not delay release of any Deposits to ICANN pursuant to Section 9. 

11.3
Dispute Resolution Procedures. The parties agree that any proceedings brought pursuant to the Dispute Resolution Procedures shall be conducted
consistently and in accordance with any prior arbitration or court orders/decisions involving the Registry Agreement. The parties further agree that any proceedings relating to this Agreement and
brought pursuant to the Dispute Resolution Procedures shall not examine, re-evaluate, reconsider, or otherwise subject to review any issues, causes of action, or other claims which were
decided, or which a party had a reasonable opportunity to raise, in proceedings which involved the Registry Agreement. 

11.4
Withdrawal of Objection Notice. Registry Operator may, at any time, notify Escrow Agent and ICANN that Registry Operator wishes to withdraw its
Objection Notice. Upon receipt of such withdrawal from Registry Operator, Escrow Agent shall promptly deliver to ICANN any Deposits that have not previously been delivered to ICANN. 

11.5  Dispute Resolution Decisions. 

11.5.1
If the release of Deposits to ICANN is determined in Dispute Resolution Procedures to have been proper, Escrow Agent shall promptly deliver to ICANN, in accordance with the instructions
specified in Section 9.3, any Deposits that have not previously been delivered. 

11.5.2
If the release of Deposits to ICANN is determined in Dispute Resolution Procedures to have been improper, ICANN shall promptly return or destroy, at Registry Operator's discretion, the Deposits
received by ICANN under Section 9. 

12.
Indemnity. Registry Operator and ICANN shall, jointly and severally, indemnify and hold harmless Escrow Agent and each of its directors, officers,
agents, employees and stockholders ("Escrow Agent Indemnitees") absolutely and forever, from and against any and all claims, actions, damages, suits, liabilities, obligations, costs, fees, charges,
and any other expenses whatsoever, including reasonable attorneys' fees and costs, that may be asserted by a third party against any Escrow Agent Indemnitees in connection with this Agreement or the
performance of Escrow Agent or any Escrow Agent
Indemnitees hereunder (with the exception of any claims based on the misrepresentation, negligence, or misconduct of Escrow Agent, its directors, officers, agents, employees, contractors, and
stockholders). Escrow Agent shall likewise indemnify and hold harmless Registry Operator and ICANN, and each of their respective directors, officers, agents, employees and stockholders ("Indemnitees")
absolutely and forever, from and against any and all claims, actions, damages, suits, liabilities, obligations, costs, fees, charges, and any other expenses whatsoever, including reasonable attorneys'
fees and costs, that may be asserted by a third party against any Indemnitee in connection with the misrepresentation, negligence, or misconduct of Escrow Agent, its directors, officers, agents,
employees, contractors, and stockholders. 

13.
Interpleader. 

13.1
Escrow Agent may submit any dispute under this Agreement to any court of competent jurisdiction in an interpleader or similar action. Any and all costs incurred by Escrow Agent in connection
therewith, including reasonable attorneys' fees and costs, shall be borne 50% by each of Registry Operator and ICANN. 

13.2
Escrow Agent shall perform any acts ordered by any court of competent jurisdiction, without any liability or obligation to any party hereunder by reason of such act. 

14.
Term and Termination. 

14.1
Term. The initial term of this Agreement shall be one year, commencing on the Beginning Date (the "Initial Term"). This Agreement shall be
automatically renewed for an additional term of one year ("Additional Term") at the end of the Initial Term and each Additional Term hereunder unless, on or before ninety days prior to the end of the
Initial Term or an Additional Term, a party notifies the other parties that it wishes to terminate this Agreement at the end of such term. In the event a party gives the other parties such notice of
termination, and Registry Operator and ICANN cannot agree to resolve, by the end of the then-current term, any disputes regarding the renewal of this Agreement or the establishment of a
replacement escrow agent: (i) Registry Operator and ICANN shall resolve any such disputes through the Dispute Resolution Procedures; (ii) this Agreement shall continue to remain in
effect during the resolution of any such disputes; and (iii) Escrow Agent shall have the right to invoice either Registry Operator or ICANN for the data escrow services provided during this
dispute resolution period at the rates listed in Exhibit E. This paragraph in no way limits the Registry Operator's right under Subsection 3.11 of the Registry Agreement to change to a
different Escrow Agent mutually approved by Registry Operator and ICANN, such approval not to be unreasonably withheld by either of them, provided that such Escrow Agent will agree to substantially
similar terms as in the present document and there is no significant interruption of Deposits. 

14.2
Termination. This Agreement shall terminate the occurrence of any of the following: 

14.2.1
Termination of this Agreement by both Registry Operator and ICANN upon having delivered to Escrow Agent a written notice signed by both Registry Operator and ICANN indicating their mutual
intent to terminate this Agreement upon ninety days' notice; 

14.2.2
Termination of this Agreement by Escrow Agent pursuant to Section 15; or 

14.2.3
Release of the Deposit(s) to ICANN pursuant to Section 9 and, if an Objection Notice is made and not withdrawn, a final decision that the release of materials to ICANN was proper at the
end of the Dispute Resolution Procedures. 

15.
Fees and Payments. Registry Operator shall pay to Escrow Agent the applicable fees and charges listed in Exhibit E as compensation for Escrow
Agent's services under this Agreement. If Registry Operator fails to pay any fees or charges invoiced by Escrow Agent by the due date(s), Escrow Agent shall give written notice to Registry Operator of
non-payment of any such past-due fees hereunder and, in that event, the Registry Operator shall have the right to pay the past-due fee(s) within ten business days
after receipt of the notice from Escrow Agent. If Registry Operator fails to pay in full all such past-due fees during the ten day period, Escrow Agent shall give notice of
non-payment of any past-due fees to ICANN and, in that event, ICANN shall have the option of paying the past-due fee within ten business days of receipt of such
notice from Escrow Agent. Upon payment of the past-due fee by either Registry Operator or ICANN, this Agreement shall continue in full force and effect. If both Registry Operator and ICANN
fail to pay the past-due fee(s) within the applicable periods under this Section 15, Escrow Agent shall have the right to terminate this Agreement immediately by sending notice of
termination to all other parties, and, upon termination, Escrow Agent shall deliver to ICANN all Deposits held by Escrow Agent. 

16.
Ownership of Deposit Materials. Subject to the provisions (including Subsection 3.13) of the Registry Agreement, the parties recognize and
acknowledge that ownership of the Deposit materials during the effective term of this Agreement shall remain with the Registry Operator at all times. 

17.  Miscellaneous. 

17.1
Remedies. For the purposes of fulfilling its obligations under this Agreement, Escrow Agent may act in good faith reliance on, and shall not be
held liable for, any written notice, instruction, instrument, or other writing signed or presented by a person with apparent authority to act on behalf of Registry Operator or ICANN. 

17.2
Dispute Resolution. Registry Operator and ICANN further agree to resolve any disputes they may have as between themselves under this Agreement
pursuant to the Dispute Resolution Procedures. 

17.3  Limitation of Liability. The parties shall not be liable to each other for special, indirect, incidental, or consequential damages hereunder. As
between ICANN and Registry Operator the liability limitations of Subsection 5.10 of the Registry Agreement also apply. 

17.4
Independent Contractor. Escrow Agent is an independent contractor and is not an employee or agent of either Registry Operator or ICANN. 

17.5
No Third-Party Beneficiaries. This Agreement shall not be construed to create any obligation by Registry Operator, ICANN, or Escrow Agent to any
non-party to this Agreement, including but not limited to any domain-name holder or registrar. 

17.6  Amendments. This Agreement shall not be modified or amended except in writing executed by each of the parties. 

17.7
Assignment. Neither Registry Operator nor ICANN may assign or transfer this Agreement (by merger, sale of assets, operation of law, or otherwise),
except that the rights and obligations of Registry Operator or ICANN automatically shall be transferred to the assignee of one of those parties' rights and obligations under the Registry Agreement.
Escrow Agent may not assign or transfer this Agreement without the prior written consent of both Registry Operator and ICANN. 

17.8  Entire Agreement. This Agreement, including all exhibits, supersedes all prior discussions, understandings, and agreements between Escrow Agent and
the other parties with respect to the data escrow services. The parties acknowledge and agree that, as between ICANN and Registry Operator, the Registry Agreement (including all its appendices) is
intended to co-exist with this Agreement, this Agreement is supplementary to the Registry Agreement, and the Registry Agreement shall control in the event of any conflict. 

17.9
Counterparts. This Agreement may be executed in counterparts, each of which when so executed shall be deemed to be an original and all of which
when taken together shall constitute one and the same Agreement. 

17.10  Governing Law. This Agreement shall be construed and enforced in accordance with the laws of the State of California, without regard to its
conflicts-of-laws principles. The parties consent and agree that jurisdiction and venue for any legal proceedings relating to this Agreement shall lie with the state and
federal courts of Los Angeles County in the State of California. 

17.11
Notices. All notices, requests, demands or other communications required or permitted to be given or made under this Agreement shall be in writing
and shall be delivered by hand, by commercial overnight delivery service which provides for evidence of receipt, by certified mail, return receipt requested, postage prepaid, by facsimile, or by
e-mail (e-mail to be followed promptly at receiver's request by a copy delivered by one of the other means of delivery) to the corresponding addresses listed on the signature
page of this Agreement. If delivered personally, by commercial overnight delivery service, by facsimile, or by e-mail, the date on which the notice, request, instruction or document is
delivered shall be the date on which delivery is deemed to be made, and if delivered by mail, the date on which such notice, request, instruction or document is received shall be the date on which
delivery is deemed to 

be
made. Any party may change its address for the purpose of this Agreement by notice in writing to the other parties as provided herein. 

17.12  Survival. The obligation of confidentiality in Section 7, Sections 9, 10, 11, 12, 13, and this Section 17.12 shall survive any
termination of this Agreement. 

17.13
No Waiver. No failure on the part of any party hereto to exercise, and no delay in exercising any right, power or single or partial exercise of
any right, power or remedy by any party will preclude any other or further exercise of that or any other right, power, or remedy. No express waiver or assent by any party to any breach of or default
in any term or condition of this Agreement shall constitute a waiver of or an assent to any succeeding breach of or default in the same or any other term or condition. 

IN
WITNESS WHEREOF each of the parties has caused its duly authorized officer to execute this Agreement as of the date and year first above written. 

Escrow
Agent

[name and address of Escrow Agent] 

	By:	 	
 [name of signer]

[title of signer]	 	 
	

Registry Operator

[name and address of Registry Operator]	
 	

 
	

By:	
 	

 [name of signer]

[title of signer]	
 	

 
	

ICANN

4676 Admiralty Way

Suite 330

Marina del Rey, CA 90292

E-mail:

Phone: 1-310-823-9358

Fax: 1-310-823-8649	
 	

 
	

By:	
 	

 M. Stuart Lynn

President and CEO	
 	

 

APPENDIX T  

 
  Registry Operator's Monthly Report  
  

Registry
Operator shall provide the following information in its monthly reports. Information reported in response to items 5-16 shall be kept confidential by ICANN until three months
after the end of the month to which the report relates. 

ICANN
shall use reasonable commercial efforts to preserve the confidentiality of the information reported in response to items 5-16. 

1. Accredited Registrar Status. State the number of registrars for whom the Registry Operator had received accreditation notification from ICANN at the
end of the reporting month, grouped into the following three status categories: 

1.1.
Operational registrars are those who have authorized access into the System for processing domain name registrations. It should be noted that operational registrars are not listed on the
InterNIC.net web site until they specifically request to be listed. This means that a registrar may be operational from the point of view of the Registry Operator but not listed on the InterNIC site. 

1.2.
Registrars in the ramp-up period represent those who have received a password to access the Registry operational test and evaluation (OT&E) environment. The OT&E environment is
provided to allow registrars to develop and test their systems with the System. 

1.3.
Registrars in the pre-ramp-up period are those who have been sent information regarding the Registry TLD, but have not yet entered the Ramp-up Period. 

2. Service Level Agreement Performance. Compare Service Level Agreement ("SLA") requirements with actual performance measures for the reporting month. 

3. TLD Zone File Access Activity. State the zone file access activity for the current reporting month including: 

3.1.
Total number of zone file access passwords at end of previous month 

3.2.
Number of new zone file access passwords issued during the reporting month 

3.3.
Total number of zone file access approvals at end of reporting month 

4. Completed SRS/System Software Releases. State significant releases that have occurred since the Effective Date, including: 

4.1.
Release Name 

4.2.
Features 

4.3.
Target Date 

4.4.
Complete Date 

5. Domain Names Under Sponsorship—Per Registrar. State the number of domain names sponsored by each live ICANN-Accredited Registrar in the
TLD for the current reporting month. 

6. Nameservers Under Management—Per Registrar. State the number of nameservers registered by each ICANN-Accredited Registrar in the TLD for
the current reporting month. 

7. Domain Names Registered by Registry Operator. Provide a list of all domain names registered by Registry Operator, other than on a request submitted
by a registrar pursuant to that registrar's Registry-Registrar Agreement, in the Registry TLD. The list should be broken down in accordance with Subsections 3.6.1 and 3.6.2 of the Registry Agreement. 

8. Whois Service Activity. State the number of Whois queries during the current reporting month. For registries with fee-based enhanced
Whois Service, state the number of queries for each service (i.e. basic, xWhois, etc.). 

9. Monthly Growth Trends. Tabulate the monthly growth trend in total Registry transactions. Transactions should be divided into three categories: 

9.1.
Write Domain—This category includes the following transactions: add domain, modify domain, delete domain, renew domain (including restore domain), auto-renew domain (if
any) and transfer domain. 

9.2.
Query Domain—This category includes the following transactions: query domain and query domain transfer status. 

9.3.
Check Domain—This category includes the following transaction: check domain. 

9.4.
Write Server—This category includes the following transactions: add name server, modify name server, and delete name server. 

9.5.
Query Server—This category includes the following transaction: query name server. 

9.6.
Check Server—This category includes the following transaction: check name server. 

9.7.
Write Contact (where contact information is maintained under the registry model)—This category includes the following transactions: add contact, modify contact, delete contact,
transfer contact. 

9.8.
Query Contact (where contact information is maintained under the registry model)—This category includes the following transactions: query contact and query contact transfer status. 

9.9.
Check Contact (where contact information is maintained under the registry model)—This category includes the following transaction: check contact. 

10. Total Number of Transactions by Subcategory by Month. Tabulate the monthly growth trend for each transaction in subcategories of the Write Domain,
Write Server, and Write Contact categories described in Subsection 9.1 as follows: 

10.1.
Add Domain 

10.2.
Delete Domain(divided in deletions within the Add Grace Period, and those that are moved to the Redemption Grace Period). 

10.3.
Modify Domain 

10.4.
Check Domain 

10.5.
Renew Domain 

10.6.
Transfer Domain 

10.7.
Restore Domain 

11. Total Number of Failed Transactions by Subcategory by Month. Starting 1 December 2001, tabulate the monthly growth trend for each failed
transaction in subcategories of the Write Domain, Write Server, and Write Contact categories described in Subsection 9.1 as follows: 

11.1.
Add Domain 

11.2.
Delete Domain 

11.3.
Modify Domain 

11.4.
Check Domain 

11.5.
Renew Domain 

11.6.
Transfer Domain 

11.7.
Restore Domain 

12. Daily Transaction Range. Tabulate the number of total daily transactions. The range of transaction volume should be shown for each month along with
the average daily transaction volume. 

13. TLD Geographical Registrations Distribution. Tabulate the number and percent of total and new domain name registrations in the Registry TLD broken
down by geographical location (country code) as of the end of the current reporting month. (Only applies where contact information is maintained under registry model.) 

14. Deleted Names—Per Registrar. State the number of domain names deleted by each registrar during the current reporting month. 

15. Restored Names—Per Registrar. List the number of domain names restored by each registrar during the current reporting month, and state
the total number of domain names restored by each registrar. 

16. Violations of Registrar Restore Report—Per Registrar. List the total number of such domain names for each registrar. 

APPENDIX U  

 
  Evaluation of Concepts  
  

Registry
Operator shall provide the following reports and related data to ICANN for use in its proof of concept evaluation. Such reports shall be provided according to the schedule described herein
during the Term of the Registry Agreement. 

The
reports provided by Registry Operator as described in this Appendix shall be subject to confidentiality restrictions according to categories described in Section 11. 

1. Concept: Procedures for Maintaining Registry Stability and Fairness to Customers in the Launch of a TLD Restricted to Commercial Use

1.1 Phase 1 Period Effectiveness—within 120 days after the end of the Phase 1 Period (as set forth in Appendix J), Registry
Operator shall provide the following information and reports to ICANN. 

1.1.1
Total number of Trademark Claim Form Submissions for the Intellectual Property Notification ("IPN") Service. 

1.1.2
Total number of Trademark Claim Form Submissions for the IPN Service broken down by the following global regions: 

1.1.2.1
Africa; 

1.1.2.2
Asia Pacific; 

1.1.2.3
Europe; 

1.1.2.4
Latin America/Caribbean; and 

1.1.2.5
North America. 

1.1.3
Total fees collected for the IPN Service during the Phase 1 Period. 

1.1.4
Total number "matches" between.biz strings submitted in the.biz domain name Applications and Trademark Claim Forms. 

1.1.5
Total number of domain names placed "on hold" as a result of the IPN Service. 

1.1.6
Total number of domain name requests cancelled by the applicant following IPN Service notice. 

1.1.7
Total Domain Name Application volume by day. 

1.1.8
Total Domain Name Application volume by week. 

1.1.9
Total Domain Name Application volume with holder addresses in the regions described below: 

1.1.9.1
Africa; 

1.1.9.2
Asia Pacific; 

1.1.9.3
Europe; 

1.1.9.4
Latin America/Caribbean; and 

1.1.9.5
North America. 

1.1.10
Total number of ICANN-Accredited Registrars qualified to submit Domain Name Applications on each day of the Phase 1 Period. 

1.1.11
Total number of Domain Names Applications during the Phase 1 Period under the sponsorship of each ICANN-Accredited Registrar. 

1.1.12
Total number of registrants requesting the Secure Domain Name Registration Service. 

1.1.13
Total number of registrants who requested the Secure Domain Name Registration Service and obtained their requested domain name during the Phase 2-Landrush. 

1.1.14
Total number of ICANN-Accredited Registrars permitted to sell the Secure Domain Name Registration Service. 

1.1.15
Total number of Secure Domain Name Registration Service registrations under sponsorship of each ICANN-Accredited Registrar. 

1.1.16
A summary of the complaints received from Registrars during the Phase 1 Period. 

1.1.17
A description of significant technical difficulties encountered in operating during the Phase 1 Period. 

1.2 Phase 2 (Landrush) Period Effectiveness—within 120 days after the end of the Phase 2-Landrush Period (as set forth in
Appendix J), Registry Operator shall provide the following information and reports to ICANN. 

1.2.1
A summary of the complaints received from Registrars during the Phase 2-Landrush Period. 

1.2.2
A description of significant technical difficulties in operating during the Phase 2-Landrush Period. 

1.2.3
A tabulation, by Registrar, of the terms in years of Phase 2-Landrush registration requests submitted to the random selection.biz domain name processing system. 

1.2.4
A tabulation, by registrar, of the terms in years of Phase 2-Landrush registration requests successfully filled by the random selection.biz domain name processing system. 

1.3 Dispute Resolution Mechanism—within 120 days after the last day an initial claimant may make a Start-Up Dispute
Resolution Policy ("SUDRP") challenge, Registry Operator shall provide the following information and reports to ICANN. 

1.3.1
A statement of the total number of challenges submitted under the SUDRP. 

1.3.2
A tabulation of the number of names subject to multiple SUDRP challenges (i.e. × names were subject to exactly two challenges, y names were subject to exactly three
challenges, etc.). 

1.3.3
A statement of how many names sponsored by each Registrar were subject to at least one SUDRP challenge. 

1.3.4
A breakdown by country of the registration offered by the domain-name holder of the number of successful and unsuccessful SUDRP challenges. 

1.3.5
A statement, broken down by sponsoring registrar, of the number of names involved in challenges where the holder failed to submit any materials after receiving notification of the SUDRP
challenge. 

1.3.6
A statement, broken down by the region of the holder's address as described below, of the number of names subject to successful SUDRP challenges: 

1.3.6.1
Africa; 

1.3.6.2
Asia Pacific; 

1.3.6.3
Europe; 

1.3.6.4
Latin America/Caribbean; and 

1.3.6.5
North America. 

1.3.7
A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful SUDRP challenges: 

1.3.7.1
Africa; 

1.3.7.2
Asia Pacific; 

1.3.7.3
Europe; 

1.3.7.4
Latin America/Caribbean; and 

1.3.7.5
North America. 

1.3.8
A statement of the number of successful SUDRP challengers that did not register the challenged name, broken down by priority of the challenger (i.e. × first-priority
challengers chose not to register the challenged name; y second priority challengers were offered the opportunity to, but did not, register the challenged name, etc.). 

1.3.9
A summary of the complaints received from Registrars regarding the SUDRP. 

1.3.10
A description of significant technical difficulties encountered in connection with the SUDRP. 

1.3.11
Registry Operator's evaluation of the overall effectiveness of the SUDRP. 

1.4 Registry Live Effectiveness—within 180 days after the start of the Registry Live Period, Registry Operator shall provide the
following information and reports to ICANN. 

1.4.1
Total number of domain names granted during Registry Live broken down by ICANN-Accredited Registrar. 

1.4.2
Total number of domain names granted during Registry Live broken down by domain name holder having addresses in the regions described below: 

1.4.2.1
Africa; 

1.4.2.2
Asia Pacific; 

1.4.2.3
Europe; 

1.4.2.4
Latin America/Caribbean; and 

1.4.2.5
North America. 

1.4.3
Total number of domain names "on hold" at the Commencement-of-Service Date. 

1.4.4
Total initial domain name registration volume by day during Registry Live. 

1.4.5
Total initial domain name registration volume by week. 

1.4.6
Total initial domain name registration volume during Registry Live with holder addresses in the regions described below: 

1.4.6.1
Africa; 

1.4.6.2
Asia Pacific; 

1.4.6.3
Europe; 

1.4.6.4
Latin America/Caribbean; and 

1.4.6.5
North America. 

1.4.7
Total number of ICANN-Accredited Registrars qualified to submit domain name registrations on day one of the Registry Live Period. 

1.4.8
Total number of domain names registered during each month of the Registry live Period under the sponsorship of each ICANN-Accredited Registrar. 

1.4.9
A summary of the complaints received from Registrars during the Registry Live Period. 

1.4.10
A description of significant technical difficulties encountered in operating during the Registry Live Period. 

1.5 Effectiveness of Batch Processing, Random Selections System—within 90 days after the end of the Phase 2-Landrush
Period, Registry Operator shall provide the following information and reports to ICANN. 

1.5.1
Provide a written report detailing the effectiveness of the batch processing, random selection.biz domain name processing system during the Land Rush Period. Include such items as lessons
learned during the process and methods of improvement. 

1.5.2
For each round of the random selection.biz domain name processing system, as described in Appendix J: 

1.5.2.1
the date on which the merged "qualified".biz domain name list was created; 

1.5.2.2
processing time required to process the "random" domain name list and register the.biz domain name selected during Phase 2-Landrush in the Registry Database; 

1.5.2.3
the names of the Registrars from which domain name applications were received; 

1.5.2.4
the number of domain name requests received from each registrar; 

1.5.2.5
the number of domain names granted for each Registrar during Phase 2-Landrush; 

1.5.2.6
the number of domain name requests submitted by each Registrar that were not granted because the domain name was "unavailable or "reserved"; 

1.5.2.7
a tabulation showing the number of names subject to multiple requests (i.e. × names were subject to exactly two requests, y names were subject to exactly three
requests, etc.); and 

1.5.2.8
a tabulation showing the number of names subject to multiple requests in each submitted by each Registrar queue (i.e. × names were subject to exactly two requests, y
names were subject to exactly three requests, etc.). 

1.6 Miscellaneous.  

1.6.1
Within 30 days after the anniversary of the Commencement-of-Service Date, provide a tabulation of the number of Phase I Period domain name registrations
transferred to another holder during each month after the Commencement-of-Service Date. 

1.6.2
Within 30 days after the anniversary of the Commencement-of-Service Date, provide a tabulation of the number of Landrush domain name registrations transferred to
another holder during each month after the Commencement-of-Service Date. 

1.6.3
Within 30 days of receipt by Registry Operator of any lawsuit concerning the start-up activities in.biz, please identify the lawsuit and provide a copy of the complaint or
describe its allegations. 

1.6.4
Within 30 days after the anniversary of the Commencement-of-Service Date, provided a tabulation of the number of Registry Live domain name registrations
transferred to another holder during each month after the Commencement-of-Service Date. 

2. Concept: Procedures for Minimizing Abusive Domain-Name Registration Practices

No
later than 180 days after the Commencement-of-Service Date, Registry Operator shall provide to ICANN a Proof-of-Concept Report on Minimizing
Abusive Registration Practices, with the following information. 

2.1
Provide a written report detailing the effectiveness of the IPN Service in limiting abusive registration practices. Include such items as lessons learned and methods of improvement. 

2.2
Provide a written report detailing the effectiveness of the Domain Name Application Fee in limiting abusive registration practices. Include such items as lessons learned and methods of
improvement. 

2.3
Provide a written report detailing the effectiveness of the Secure Domain Name Registration Service in limiting abusive registration practices. Include such items as lessons learned and methods of
improvement. 

3. Concept: Introducing a TLD Restricted to Commercial Use as a Means of Effective Competition with a Dominant, Well-Financed TLD Such
as.com

No
later than one month after each anniversary date after the Commencement-of-Service Date, Registry Operator shall provide to ICANN an Annual
Proof-of-Concept Report on Effectiveness of Competition, with the following information: 

3.1 Marketing Efforts.

3.1.1
Total Registry Operator expenditures for marketing the.biz TLD, broken down by calendar quarter ending in the year to which the report relates and by the region where the expenditure was made: 

3.1.1.1
Africa; 

3.1.1.2
Asia Pacific; 

3.1.1.3
Europe; 

3.1.1.4
Latin America/Caribbean; and 

3.1.1.5
North America. 

3.1.2
Types of marketing media utilized by Registry Operator, broken down by calendar quarter ending in the year to which the report relates. 

3.1.3
Total expenditure for each marketing media provided above, broken down by calendar quarter ending in the year to which the report relates. 

3.1.4
(For the first annual report:) Provide a breakdown of marketing expenditures during the Phase 1 Period for the following global regions: 

3.1.4.1
Africa; 

3.1.4.2
Asia Pacific; 

3.1.4.3
Europe; 

3.1.4.4
Latin America/Caribbean; and 

3.1.4.5
North America. 

3.1.5
(For the first annual report:) Provide a breakdown of marketing expenditures during the Phase 2-Landrush Period for the following global regions: 

3.1.5.1
Africa; 

3.1.5.2
Asia Pacific; 

3.1.5.3
Europe; 

3.1.5.4
Latin America/Caribbean; and 

3.1.5.5
North America. 

3.1.6
Total annual marketing expenditure. 

3.2 Quarterly Report—Total number of ICANN-Accredited Registrars registering domain names in the TLD 

3.2.1
Total number of ICANN-Accredited Registrars authorized to register domain names in the.biz TLD broken down on a quarterly basis (include a geographic breakdown by global region). 

3.2.2
Total number of new ICANN-Accredited Registrars authorized to register domain names in the.biz TLD broken down on a quarterly basis (include a geographic breakdown by global region). 

3.2.3
Total number of ICANN-Accredited Registrars authorized to register domain names in the.biz TLD that were terminated broken down on a quarterly basis (include a geographic breakdown by global
region). 

3.2.4
Describe the reason for each termination listed above. 

3.2.5
Total number of registrations under management by each ICANN-Accredited Registrar, broken down on a quarterly basis. 

3.3
Number of initial registrations during each calendar month ending in the year to which the report relates. 

3.4
Number of renewals during each calendar month ending in the year to which the report relates. 

3.5
Number of registration transfers during each calendar month ending in the year to which the report relates. 

3.6
Provide the Geographic breakdown of registrants by global region: 

3.6.1
Africa; 

3.6.2
Asia Pacific; 

3.6.3
Europe; 

3.6.4
Latin America/Caribbean; and 

3.6.5
North America. 

3.7
Total domain name registrations expiring and not renewed during each calendar month ending in the year to which the report relates. 

3.8
Average term of new registrations during each calendar month ending in the year to which the report relates. 

3.9
Average term of renewals during each calendar month ending in the year to which the report relates. 

4. Concept: Adding a TLD Restricted to Commercial Use Will Result in an Expansion and Globalization of the Effective Namespace, Rather than Wasteful Duplication of
Registrations

Landrush Report—within 90 days after the end of the Phase 2—Landrush Period, Registry Operator shall provide to ICANN an
"Expansion of the DNS" report with the following elements: 

4.1
Total number of duplicate registrations (i.e. same name) with each of the following TLDs during Landrush Period: 

4.1.1
..com; 

4.1.2
..net; 

4.1.3
..org; 

4.1.4
..de; and 

4.1.5
..co.uk. 

4.2
An estimate of the percentage of such duplicate registrations registered to the same holder. (e.g., example.biz and example.com registered to the same holder). 

4.3
The estimated percentage of such duplicate registrations sharing at least one nameserver with respect to each of the five domains listed in 3.1.1 to 3.1.5. 

4.4
Total number of domain names under management during the Phase 2—Landrush Period with holder addresses in the regions described below: 

4.4.1
Africa; 

4.4.2
Asia Pacific; 

4.4.3
Europe; 

4.4.4
Latin America/Caribbean; and 

4.4.5
North America. 

4.5
Number of ICANN-Accredited Registrars, broken down by global region, registering domain names during the Phase 2—Landrush Period: 

4.5.1
Africa; 

4.5.2
Asia Pacific; 

4.5.3
Europe; 

4.5.4
Latin America/Caribbean; and 

4.5.5
North America. 

Annual Reports—No later than one month after each anniversary date after the Commencement-of-Service Date, Registry
Operator shall provide to ICANN an "Expansion of the DNS" report with the following elements: 

4.6
Total number of duplicate registrations (i.e. same name) with each of the following TLDs at the end of each calendar month ending in the year to which the report relates. 

4.6.1
..com; 

4.6.2
..net; 

4.6.3
..org; 

4.6.4
..de; and 

4.6.5
..co.uk. 

4.7
An estimate of the percentage of such duplicate registrations registered to the same holder. 

4.8
The percentage of such duplicate registrations sharing at least one nameserver with respect to each of the five domains listed in 3.6.1 to 3.6.5. 

4.9
Total number of domain names under management Post Landrush Period on a quarterly basis with holder addresses in the regions described below: 

4.9.1
Africa; 

4.9.2
Asia Pacific; 

4.9.3
Europe; 

4.9.4
Latin America/Caribbean; and 

4.9.5
North America. 

4.10
Number of ICANN-Accredited Registrars, broken down by global region, registering domain names during the Post Landrush Period: 

4.10.1
Africa; 

4.10.2
Asia Pacific; 

4.10.3
Europe; 

4.10.4
Latin America/Caribbean; and 

4.10.5
North America. 

5. Concept: Registry Services Can Effectively Be Provided by a Jointly Managed Registry Operator

5.1
Ability to Effectively Operate the Registry. Annual Report—No later than one month after each anniversary date after the
Commencement-of-Service Date, Registry Operator shall provide to ICANN a Joint Management Registry Report with the following elements: 

5.1.1
Total number of registrations under management during each calendar month ending in the year to which the report relates. 

5.1.2
Total number of ICANN-Accredited Registrars registering domain-names in the Registry TLD during each calendar month ending in the year to which the report relates. 

5.1.3
Total amount of SLE Credits to ICANN-Accredited Registrars during each calendar month ending in the year to which the report relates. 

5.1.4
Total SLE Credits awarded to each ICANN-Accredited during each calendar month ending in the year to which the report relates. 

5.1.5
Provide a breakdown of the SLE Credits awarded to ICANN-Accredited Registrars for the following Credit Classes: 

5.1.5.1
C1a Credit Class; 

5.1.5.2
C1b Credit Class; 

5.1.5.3
C2 Credit Class; 

5.1.5.4
C3 Credit Class; and 

5.1.5.5
C4 Credit Class. 

5.2
Ability to Attract and Maintain Registrars—within 180 days after the Commencement-of-Service Date,
Registry Operator shall provide the following information and reports to ICANN. 

5.2.1
Total number of ICANN-Accredited Registrars who participated in the Registry start-up-phase technical acceptance test. 

5.2.2
Total number of ICANN-Accredited Registrars who failed the start-up-phase technical acceptance test. 

5.2.3
Total number of ICANN-Accredited Registrars re-tested in the start-up-phase technical acceptance test. 

5.2.4
A summary of complaints received from ICANN-Accredited Registrars regarding the start-up-phase technical acceptance test. 

5.2.5
Provide a written report detailing the effectiveness of the start-up-phase technical acceptance test. Include such items as lessons learned and methods of improvement. 

5.2.6
Total number of ICANN-Accredited Registrars who participated in the XRP Acceptance Test. 

5.2.7
Total number of ICANN-Accredited Registrars who failed the XRP Acceptance Test. 

5.2.8
Total number of ICANN-Accredited Registrars re-tested for the XRP Acceptance Test. 

5.2.9
A summary of complaints received from Registrars regarding the XRP Acceptance Test. 

5.2.10
Provide a written report detailing the effectiveness of the XRP acceptance test. Include such items as lessons learned and methods of improvement. 

6. Concept: Mechanisms for Ensuring that all Registrars Are Treated Fairly

Annual Reports—No later than one month after each anniversary date after the Commencement-of-Service Date, Registry
Operator shall provide to ICANN a Fair-Treatment Report with the following elements: 

6.1
A description of every known violation or alleged violation of the Code of Conduct during each calendar month ending in the year to which the report relates. 

6.2
Total number of complaints received by Registry Operator from registrars regarding services provided by Registry Operator. 

6.2.1
Identify and categorize the types of complaints received from registrars. 

6.2.2
List corrective actions, if any, in response to the categorized complaints. 

6.3
Total number of ICANN-Accredited Registrars restricted from further registrations for non-payment of registration fees. 

7. Concept: Use of Centralized Registry-Level Whois to Enhance Transparency and Accountability in Domain-Name Registrations

Annual Reports—No later than three months after each anniversary date after the Commencement-of-Service Date,
Registry Operator shall provide to ICANN a Whois Report with the following elements: 

7.1
Total number of complaints received from registrants regarding Whois information during each calendar month ending in the year to which the report relates. 

7.2
Total number of complaints received from ICANN-Accredited Registrars regarding Whois service during each calendar month ending in the year to which the report relates. 

7.3
Total number of complaints received from third parties regarding Whois information during each calendar month ending in the year to which the report relates. 

7.4
(For the first annual report:) Total initial query volume during the Phase 2—Landrush Period. 

7.5
Total number of queries during each calendar month ending in the year to which the report relates. 

7.6
Enhanced Whois Services: 

7.6.1
Total number of subscribers (include a geographic breakdown by country and global region). 

7.6.2
Total number of queries during each calendar month ending in the year to which the report relates. 

7.6.3
Total number of queries broken down by subscriber during each calendar month ending in the year to which the report relates. 

7.7
Privacy Complaints: 

7.7.1
Total number of complaints relating to privacy issues during each calendar month ending in the year to which the report relates. 

7.7.2
Identify and categorize types of privacy complaints. 

8. Concept: Capital Requirements in Operating a TLD Restricted to Commercial Use

Annual Reports—No later than one month after each anniversary date after the Commencement-of-Service Date, Registry
Operator shall provide to ICANN a Funding Requirements Report with the following elements: 

8.1
Total expenditures during the Phase 1. 

8.2
Total expenditures during Phase 2 Land Rush Period. 

8.3
Total expenditures during Phase 3 Registry Live on a quarterly basis. 

8.4
Breakdown of expenditures for the following categories: 

8.4.1
Marketing; 

8.4.2
Software; and 

8.4.3
Hardware. 

8.5
Provide a list of the employee positions hired during the following periods: 

8.5.1
Pre-Phase 1 Period; 

8.5.2
Phase 1 Period; 

8.5.3
Phase 2 Landrush Period; and 

8.5.4
Phase 3 Registry Live on a quarterly basis. 

9. Concept: Registration Restrictions Can Be Implemented by a Registry Operator in a Cost Effective and Timely Manner

9.1
SUDRP/UDRP Proceedings—within 165 days after the Commencement-of-Service Date, Registry Operator shall
provide an initial report with the following information and reports to ICANN. Thereafter, no later than one year after the anniversary date of the initial report, Registry Operator shall provide the
following information and reports to ICANN. 

9.1.1
A statement of the total number of Start-Up Dispute Resolution Policy ("SUDRP") and/or UDRP challenges filed. 

9.1.2
A tabulation of the number of names subject to multiple SUDRP and/or UDRP challenges (i.e., × names were subject to exactly two challenges, y names were subject to
exactly three challenges, etc.). 

9.1.3
A statement of how many names sponsored by each Registrar were subject to at least one SUDRP and/or UDRP challenge. 

9.1.4
A breakdown by country of the registration offered by the domain-name holder of the number of successful and unsuccessful SUDRP and/or UDRP challenges. 

9.1.5
A statement, broken down by sponsoring Registrar, of the number of names involved in SUDRP and/or UDRP challenges where the holder failed to submit any materials after notification of challenge. 

9.1.6
A statement, broken down by the region of the holder's address as described below, of the number of names subject to successful SUDRP and/or UDRP challenges: 

9.1.6.1
Africa; 

9.1.6.2
Asia Pacific; 

9.1.6.3
Europe; 

9.1.6.4
Latin America/Caribbean; and 

9.1.6.5
North America. 

9.1.7
A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful SUDRP and/or UDRP challenges: 

9.1.7.1
Africa; 

9.1.7.2
Asia Pacific; 

9.1.7.3
Europe; 

9.1.7.4
Latin America/Caribbean; and 

9.1.7.5
North America. 

9.1.8
A statement of the number of successful SUDRP and/or UDRP challengers that did not register the challenged name, broken down by priority of the challenger
(i.e. × first-priority challengers chose not to register the challenged name; y second priority challengers were offered the opportunity to, but did not, register the
challenged name, etc.). 

9.1.9
A summary of the complaints received from Registrars regarding the SUDRP. 

9.2
Registrations Restrictions—within 165 days after the Commencement-of-Service Date, Registry Operator
shall provide the following information and reports to ICANN. Thereafter, no later than one year after the anniversary date of the initial report, Registry Operator shall provide the following
information and reports to ICANN. 

9.2.1
A statement of the total number of Restriction Dispute Resolution Policy ("RDRP") Challenges filed. 

9.2.2
A tabulation of the number of names subject to multiple RDRP challenges (i.e., × names were subject to exactly two challenges, y names were subject to exactly three
challenges, etc.). 

9.2.3
A statement of how many names sponsored by each Registrar were subject to at least one RDRP challenge. 

9.2.4
A breakdown by country of the registration offered by the domain-name holder of the number of successful and unsuccessful RDRP challenges. 

9.2.5
A statement, broken down by sponsoring Registrar, of the number of names involved in RDRP challenges where the holder failed to submit any materials after notification of challenge. 

9.2.6
A statement, broken down by the region of the holder's address as described below, of the number of names subject to successful RDRP challenges: 

9.2.6.1
Africa; 

9.2.6.2
Asia Pacific; 

9.2.6.3
Europe; 

9.2.6.4
Latin America/Caribbean; and 

9.2.6.5
North America. 

9.2.7
A statement, broken down by the region of the successful challenger's address as described below, of the number of names subject to successful RDRP challenges: 

9.2.7.1
Africa; 

9.2.7.2
Asia Pacific; 

9.2.7.3
Europe; 

9.2.7.4
Latin America/Caribbean; and 

9.2.7.5
North America. 

9.2.8
A statement of the number of successful RDRP challengers that did not register the challenged name, broken down by priority of the challenger (i.e. × first-priority
challengers chose not to register the challenged name; y second priority challengers were offered the opportunity to, but did not, register the challenged name, etc.). 

9.2.9
A statement, broken down by sponsoring Registrar, of the number of names forfeited on the basis that the name was registered solely for the purpose of (1) selling, trading or leasing the
domain name for compensation, or (2) the unsolicited offering to sell, trade or lease the domain name for compensation. 

9.2.10
A summary of the complaints received from Registrars regarding the RDRP. 

9.2.11
A description of significant technical difficulties encountered in connection with the RDRP resolution. 

9.2.12
Registry Operator's evaluation of the overall effectiveness of the RDRP adopted for the Registry TLD. 

9.2.13
Registry Operator's evaluation of the overall effectiveness of each dispute resolution policy adopted by the Registry TLD described below: 

9.2.13.1
SUDRP; 

9.2.13.2
RDRP; and 

9.2.13.3
UDRP. 

10. Commercially Reasonable Efforts and Review

Many
of the reports to be provided by Registry Operator require access to data to which Registry Operator may not be privy or which may not be reasonably available to Registry Operator. Recognizing
the importance of the proof of concept: 

10.1
Registry Operator shall use commercially reasonable efforts to obtain all necessary data and complete the required reports as set forth in this Appendix; and 

10.2
In the event Registry Operator is unable through commercially reasonable efforts to obtain the requisite data to complete the required reports or the compilation of a specific report proves
unreasonably costly, ICANN shall, to the fullest extent possible, assist Registry Operator and/or the Registry community in obtaining or coordinating efforts to obtain the data, or alternative data 

(including
as appropriate data of reduced scope) useful in connection with the proof of concept, in a less costly way. 

11. Confidentiality

The
reports provided by Registry Operator as described in this Appendix shall be subject to confidentiality restrictions according to categories described in the following table: 

	Category

	 	Restrictions

	1	 	May be publicly disclosed by ICANN 18 months after the information is reported to ICANN.
	

2	
 	

May be publicly disclosed by ICANN 6 months after the information is reported to ICANN.
	

3	
 	

May be publicly disclosed by ICANN 90 days after the last date to which the information relates.
	

4	
 	

No confidentiality restrictions.

ICANN
will use commercially reasonable efforts to prevent public disclosure prior to the times described in the table above. 

Registry
Operator shall clearly label all reports and information provided pursuant to this Appendix with the appropriate confidentiality category prior to submission to ICANN. 

The
following table sets forth, for each item in each report, the confidentiality category (CC) that applies to it: 

	Report

ID
 
	 	CC
	 	Report

ID
	 	CC
	 	Report

ID
	 	CC
	 	Report

ID
	 	CC

	1.1.1	 	2	 	1.4.1	 	4	 	3.8	 	3	 	7.5	 	3
	1.1.2.1-1.1.2.5	 	2	 	1.4.2.1-1.4.2.5	 	4	 	3.9	 	3	 	7.6.1	 	2
	1.1.3	 	2	 	1.4.3	 	3	 	4.1.1-4.1.5	 	4	 	7.6.2	 	2
	1.1.4	 	4	 	1.4.4	 	4	 	4.2	 	4	 	7.6.3	 	2
	1.1.5	 	4	 	1.4.5	 	4	 	4.3	 	4	 	7.7.1	 	2
	1.1.6	 	4	 	1.4.6.1-1.4.6.5	 	4	 	4.4.1-4.4.5	 	4	 	7.7.2	 	2
	1.1.7	 	4	 	1.4.7	 	4	 	4.5.1-4.5.5	 	4	 	8.1	 	3
	1.1.8	 	4	 	1.4.8	 	2	 	4.6.1-4.6.5	 	4	 	8.2	 	3
	1.1.9	 	4	 	1.4.9	 	2	 	4.7	 	4	 	8.3	 	2
	1.1.10.1-1.1.10.5	 	4	 	1.4.10	 	2	 	4.8	 	4	 	8.4.1-8.4.5	 	2
	1.1.11	 	4	 	1.5.1	 	4	 	4.9.1-4.9.5	 	4	 	8.5.1-8.5.5	 	2
	1.1.12	 	2	 	1.5.2.1-1.5.2.4	 	3	 	4.10.1-4.10.5	 	4	 	9.1.1	 	4
	1.1.13	 	4	 	1.5.2.5-1.5.2.9	 	2	 	5.1.1	 	2	 	9.1.2	 	4
	1.1.14	 	3	 	1.6.1	 	3	 	5.1.2	 	2	 	9.1.3	 	2
	1.1.15	 	4	 	1.6.2	 	4	 	5.1.3	 	2	 	9.1.4	 	4
	1.1.16	 	2	 	2.1	 	3	 	5.1.4	 	2	 	9.1.5	 	4
	1.1.17	 	2	 	2.2	 	3	 	5.2.1	 	3	 	9.1.6.1-9.1.6.5	 	4
	1.1.18	 	2	 	2.3	 	3	 	5.2.2	 	3	 	9.1.7.1-9.1.7.5	 	4
	1.2.1	 	2	 	3.1.1.1-3.1.1.5	 	1	 	5.2.3	 	3	 	9.1.8	 	4
	1.2.2	 	2	 	3.1.2	 	1	 	5.2.4	 	3	 	9.1.9	 	4
	1.2.3	 	4	 	3.1.3	 	1	 	5.2.5	 	3	 	9.2.1	 	4
	1.2.4	 	3	 	3.1.4.1-3.1.4.5	 	1	 	5.2.6	 	3	 	9.2.2	 	4
	1.2.5	 	3	 	3.1.5.1-3.1.5.5	 	1	 	5.2.7	 	3	 	9.2.3	 	2
	1.3.1	 	4	 	3.1.6	 	2	 	5.2.8	 	3	 	9.2.4	 	4
	1.3.2	 	4	 	3.2.1	 	4	 	5.2.9	 	3	 	9.2.5	 	4
	1.3.3	 	2	 	3.2.2	 	4	 	5.2.10	 	3	 	9.2.6	 	4
	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 

	1.3.4	 	4	 	3.2.3	 	4	 	6.1	 	2	 	9.2.7	 	4
	1.3.5	 	4	 	3.2.4	 	2	 	6.2.1	 	2	 	9.2.8	 	4
	1.3.6.1-1.3.6.5	 	4	 	3.2.5	 	2	 	6.2.2	 	2	 	9.2.9	 	3
	1.3.7.1-1.3.7.5	 	4	 	3.3	 	3	 	6.3	 	4	 	9.2.10	 	2
	1.3.8	 	4	 	3.4	 	3	 	7.1	 	2	 	9.2.11	 	2
	1.3.9	 	2	 	3.5	 	3	 	7.2	 	2	 	9.2.12	 	3
	1.3.10	 	2	 	3.6.1-3.6.5	 	3	 	7.3	 	2	 	9.2.13.1-9.2.13.5	 	3
	1.3.11	 	4	 	3.7	 	3	 	7.4	 	3	 	 	 	 

APPENDIX V  

Consensus Policies  

The
Registry Agreement requires Registry Operators to abide by various specifically stated procedures and also Consensus Policies. Policies adopted before the date of the Registry Agreement are deemed
to be Consensus Policies. Policies adopted after the date of the Registry Agreement are applicable to Registry Operator if those policies meet certain requirements regarding the demonstration of
consensus. 

The
following policies are specifically identified as having been adopted by the ICANN Board of Directors as of the dates shown below. As such, they are deemed Consensus Policies: 

	•
	Uniform
Domain Name Dispute Resolution Policy—adopted August 26, 1999; form of implementation documents approved October 24, 1999. 

APPENDIX W  

 
  Additional Covenants of NeuLevel  
  

1.     Ownership Structure  

As
of April 23, 2001, Registry Operator is a Delaware corporation. The ownership of the LLC is divided between NeuStar, Inc., a Delaware corporation (55%) and Melbourne IT Ltd.,
an Australian company (45%). The corporate structure and ownership levels of Registry Operator are subject to change in the normal course of Registry Operator's business. Any change of the ownership
structure shall be in conformance with Section 3 below. 

2.     Insurance  

Registry
Operator, or parent of Registry Operator on behalf of Registry Operator, shall acquire, prior to the Effective Date, at least US $10,000,000 in comprehensive general liability insurance from
a reputable insurance provider with an A.M. Best rating of "A" or better and shall maintain insurance meeting these requirements throughout the Term of this Agreement. 

3.     Limitation on Merger, Consolidation or Reorganization  

During
the Term of this Agreement, Registry Operator shall not: (1) merge, consolidate or otherwise reorganize into or with a Registry Operator for a TLD which has more than 10,000,000
Registered Names under management, or any of its affiliates; or (2) sell or otherwise transfer all of its assets or stock to a Registry Operator for a TLD which has more than 10,000,000
Registered Names under management, or any of its affiliates. Registry Operator may merge, consolidate or otherwise reorganize into or with a (1) Registry Operator which has less than 10,000,000
Registered Names under management, or (2) a domain name registrar, only upon the express written consent of ICANN, which consent may not be unreasonably withheld or delayed. In considering
whether to give consent, ICANN may consider Concepts 3, 5 and 6 stated in Appendix U to this Agreement. 

4.     Funding Commitment  

Registry
Operator shall have available from either internal or external sources a minimum of US $34,000,000 in funding solely for Registry Operator's activities in establishing and operating the
Registry TLD through the date that is one year following the Commencement-of-Service Date. 

5.     Marketing Commitment  

Registry
Operator shall have available from either internal or external sources a minimum of US $15,000,000 for marketing Registry Services in the Registry TLD. Registry Operator shall use reasonable
commercial efforts to effectively market.biz Registry Services during the Term of the Agreement. 

APPENDIX X  

 
  Names Registered to Registry Operator  
  

The
domains to be reserved by NeuLevel are as follows: 

Part A: Names staying with the Registry in the event of reassignment  

	1.	advisory.biz
	2.	api.biz
	3.	autorenew.biz
	4.	billing.biz
	5.	bizdomain.biz
	6.	bizinfo.biz
	7.	bizlogin.biz
	8.	bizlock.biz
	9.	bizname.biz
	10.	bizness.biz
	11.	biznotification.biz
	12.	bizregistrar.biz
	13.	bizregistrars.biz
	14.	bizwebaddress.biz
	15.	bulkrenew.biz
	16.	business.biz
	17.	callcenter.biz
	18.	cctld.biz
	19.	claims.biz
	20.	customercare.biz
	21.	customersupport.biz
	22.	digitalcertificates.biz
	23.	directory.biz
	24.	dns.biz
	25.	domain.biz
	26.	domainname.biz
	27.	domainnames.biz
	28.	domains.biz
	29.	dotbizpromotions.biz
	30.	dotbiz.biz
	31.	dotbizaccounting.biz
	32.	dotbizbilling.biz
	33.	dotbizcallcenter.biz
	34.	dotbizcards.biz
	35.	dotbizcustomercare.biz
	36.	dotbizcustomersupport.biz
	37.	dotbizhelp.biz
	38.	dotbizhelpdesk.biz
	39.	dotbizinfo.biz
	40.	dotbizmail.biz
	41.	dotbizorder.biz
	42.	dotbizregistrar.biz
	43.	dotbizregistrarsupport.biz
	44.	dotbizsecurity.biz
	45.	dotbizsite.biz
	46.	dotbiztechnicalsupport.biz
	 	 

	47.	dotbiztroubledesk.biz
	48.	dotbizwebmaster.biz
	49.	ebiz.biz
	50.	ebizness.biz
	51.	findyour.biz
	52.	ftp.biz
	53.	getyour.biz
	54.	gopher.biz
	55.	gtld.biz
	56.	helpdesk.biz
	57.	hostmaster.biz
	58.	identify.biz
	59.	imap.biz
	60.	info.biz
	61.	ldap.biz
	62.	multilingual.biz
	63.	mybiz.biz
	64.	network.biz
	65.	nntp.biz
	66.	ntp.biz
	67.	order.biz
	68.	pop.biz
	69.	pop3.biz
	70.	questions.biz
	71.	questionsdotbiz.biz
	72.	register.biz
	73.	registry.biz
	74.	registeryour.biz
	75.	registeryourbiz.biz
	76.	registrant.biz
	77.	registrar.biz
	78.	registrarreports.biz
	79.	registrars.biz
	80.	registrarsupport.biz
	81.	registrylock.biz
	82.	renew.biz
	83.	renewnames.biz
	84.	root.biz
	85.	rootserver.biz
	86.	securedomain.biz
	87.	securename.biz
	88.	security.biz
	89.	servicemark.biz
	90.	services.biz
	91.	smtp.biz
	92.	snmp.biz
	93.	technicalsupport.biz
	94.	telnet.biz
	95.	thebizdomain.biz
	96.	thebizregistry.biz
	97.	theregistry.biz
	98.	troubledesk.biz
	99.	usergroup.biz
	100.	webmaster.biz
	 	 

	101.	whatbiz.biz
	102.	whois.biz
	103.	whoisbiz.biz
	104.	www.biz
	105.	xrp.biz
	106.	yourbiz.biz
	107.	zone.biz
	108.	zonefile.biz

Part B: Names staying with NeuLevel in the event of reassignment:  

	1.	melbourneit.biz
	2.	neulevel.biz
	3.	neu-level.biz
	4.	neulevelinc.biz
	5.	neulevelbiz.biz
	6.	neulevelllc.biz
	7.	neulevelregistrar.biz
	8.	neulevelregistrars.biz
	9.	neulevelregistry.biz
	10.	neulevel-inc.biz
	11.	neulevel-llc.biz
	12.	neulevel-biz.biz
	13.	neustar.biz
	14.	newlevel.biz
	15.	new-level.biz

If
the corporate identity of NeuLevel is changed, Appendix X will be amended to incorporate 2nd level domain variations on the new identity. 

APPENDIX Y  

 
  Sanctions Program  
  

This
document describes a program (the "Sanctions Program") under which violations of Subsections 3.5.1 through 3.5.5 and Appendix H (certification and separation requirements) and
Appendix I (Registry Operator's Code of Conduct) of the Registry Agreement may be addressed, at ICANN's option, by a separate and additional set of specific monetary sanctions. The Sanctions
Program is intended to allow ICANN flexibility to address violations of those Subsections and Appendices by means less extreme than proceedings to terminate the Registry Agreement. Registry Operator
agrees that the Sanctions Program is a non-exclusive and additional option for promoting compliance with Appendices H and I, and does not (except as stated below) limit or affect in any
way ICANN's ability to employ any other compliance measures or remedies available under the Registry Agreement. 

Registry
Operator agrees to participate in and comply with the Sanctions Program described in this document, provided that all other registry operators having registry agreements with ICANN for the
operation of unsponsored top-level domains (i.e., top-level domains, other than country-code and infrastructure domains, not having a sponsoring organization) are
obligated to participate in and comply with a sanctions program with substantially the same provisions. Failure by Registry Operator to participate in and comply with this sanctions program according
to the terms of this document constitutes a ground for ICANN to terminate the Registry Agreement. 

ICANN
and Registry Operator agree that, should the gTLD Constituency of the Domain Name Supporting Organization propose a substitute Appendix Y at any time prior to 1 May 2002, and ICANN
determines (following an appropriate process of public notice and comment) that substitution by that Appendix Y would serve the interests of the Internet community, the substitution will be
made. 

Investigation:  

ICANN
may elect to employ the Sanctions Program by sending Registry Operator a Confidential Notice of Investigation. Should ICANN choose to initiate an investigation with regard to any particular
activity or conduct, it must do so (a) within 90 days of the time that such activity or conduct is brought to the attention of the appropriate ICANN employee, and (b) in any event
no later than one year after the episode in question. The Confidential Notice of Investigation must be given in the manner described by the Registry Agreement, but shall not be publicly disclosed or
commented upon by ICANN unless Registry Operator has previously disclosed or confirmed its existence. The Confidential Notice of Investigation must include all of the following: 

1.
A statement that an investigation under the Sanctions Program is being initiated; 

2.
A statement of the possible violation of Subsections 3.5.1 through 3.5.5 and Appendices H and I being investigated and the reasons for believing such violation may have occurred; 

3.
A request to Registry Operator to provide to ICANN the information, including copies of any documentation, that ICANN believes is necessary for it to conduct the investigation, which information
must be reasonably related to the alleged violation; and 

4.
A specification of the ICANN investigator to whom a response should be made and the form in which the response should be transmitted. 

Registry
Operator shall have thirty days (or such larger period as ICANN may allow) after the date of the Confidential Notice of Investigation to send a response to the specified ICANN investigator.
The response, which shall be transmitted to the ICANN investigator in the manner stated in the Confidential Notice of Investigation, shall include: 

1.
An acknowledgement that an investigation has been initiated; 

2.
Any of the information requested in the Confidential Notice of Investigation that Registry Operator chooses to provide in accordance with clause 3 above; 

3.
If Registry Operator does not provide any or all of the information sought by the Confidential Notice of Investigation, the Registry Operator may state its reason(s) for not providing the
information, and ICANN is free to draw any reasonable inferences from the failure to provide such information; 

4.
Any request by the Registry Operator for confidential treatment of any of the information supplied, and the reason for such confidential treatment; and 

5.
A specification of the name and address of the person appointed by the Registry Operator to receive communications concerning the investigation ("Authorized Representative"). 

Any
such response shall be treated as confidential by ICANN unless disclosed or confirmed by Registry Operator. Within thirty days after transmission of the Registry Operator's response to the Notice
of Investigation, ICANN shall do one of the following: 

1.
If ICANN chooses to commence a sanctions proceeding based on the information it has received from the Registry Operator and otherwise, send the Authorized Representative a Statement of Evidence of
Violation meeting the requirements stated below; 

2.
If ICANN chooses not to proceed with the sanctions proceeding or a renewed investigation, send the Authorized Representative a notice that the Investigation is closed without further action; or 

3.
If ICANN chooses to seek additional information, send an additional Confidential Notice of Investigation to the Registry Operator meeting the requirements stated above. 

Statement of Evidence of Violation  

If
ICANN has reason to believe that a violation has occurred, it shall send the Authorized Representative a Statement of Evidence of Violation. The Statement of Evidence of Violation shall not be
publicly disclosed or commented on by ICANN unless Registry Operator has previously disclosed or confirmed its existence. The Statement of Evidence of Violation shall: 

1.
Specify the provision(s) of Subsections 3.5.1 through 3.5.5 and Appendices H and I of the Registry Agreement that ICANN has reason to believe Registry Operator has violated; 

2.
Provide a reasonably specific statement of the factual basis of the apparent violation; 

3.
Include all evidence on which ICANN has relied in concluding it has reason to believe that a violation has occurred; 

4.
Give the legal and factual basis for ICANN's conclusion that it has reason to believe that a violation has occurred, based on a discussion of the provisions of the Registry Agreement, the included
evidence, and any reasonable inferences drawn therefrom; and 

5.
State whether the alleged violation would, if established, be a major violation or a minor violation (see below) and why. 

Within
thirty days (or such longer period as ICANN may allow) after the Statement of Evidence of Violation is sent, the Registry Operator shall send a response to the ICANN investigator. 

Finding of Violation  

At
least thirty days after the Statement of Evidence of Violation is sent, and after considering any Registry Operator's response to the Statement of Evidence of Violation, ICANN may issue a Finding
of Violation. A Finding of Violation must be sent to the person appointed by the Registry Operator to receive communications concerning the investigation, and shall be posted on ICANN's website, with
appropriate redactions for material that ICANN and Registry Operator agree is confidential. If no Finding of Violation is sent within ninety days after the Registry Operator's response to the
Statement of Evidence of Violation, the sanctions proceeding shall be deemed closed without action. 

Any
Finding of Violation must: 

1.
Specify the provision(s) of Subsections 3.5.1 through 3.5.5 and Appendices H and I of the Registry Agreement that ICANN finds Registry Operator has violated; 

2.
Provide a specific detailed description of the evidence upon which ICANN relies in making the finding; 

3.
Specifically state any inferences that ICANN draws based on the evidence, upon Registry Operator's failure to provide information requested in the investigation, or otherwise; 

4.
Provide a specific detailed description of the nature of the violation found, and state whether the violation is found to be major or minor and why; and 

5.
State the amount of monetary sanctions assessed for each distinct violation found and reasons why the amount is deemed reasonable. 

In
finding a violation, ICANN may rely on information provided in response to a Confidential Notice of Investigation, on any evidence included in the Statement of Evidence of Violation, and on any
information provided in response to the Statement of Evidence. ICANN may draw inferences from any failure by the Registry Operator to provide information requested in the investigation, provided those
inferences are reasonable in the circumstances. Only one Finding of Violation may be issued with respect to any particular episode of activity or conduct. 

A
violation shall be classified as major or minor based on (a) the effects of the violation on competition and competitors, (b) the extent to which the violation appears to be
intentional by Registry Operator, considering the level of the employees or agents involved, prior notice to the Registry Operator of the circumstances, and other relevant factors, (c) the
extent to which the Registry Operator has established and effectively enforces policies that prohibit such violations (where the violation involves actions by employees or agents of Registry Operator
that have not been approved by senior management that has authority to change such policies), (d) prior findings of violations by the Registry Operator, and (e) any other relevant
circumstances. 

Sanctions
of up to US$10,000 for each violation may be assessed for each minor violation found and sanctions of up to US$100,000 for each violation may be assessed for each major violation found. The
amount of the financial sanction shall be proportionate to the violation and other relevant facts. 

In
the event ICANN makes a Finding of Violation and seeks to impose a monetary sanction, it may not thereafter issue a cure notice or seek any other remedy on the basis of the assertion that the same
specific episode on which the Finding of Violation is based constitutes a breach of this Agreement, but it may take into account the fact of the Finding and sanction in determining that another
violation should be dealt with in a particular way, including by deeming it a material breach of this Agreement. 

Review of Finding of Violation  

Findings
of Violation may be reviewed only by ICANN's Reconsideration Policy or by arbitration under Subsection 5.9 of the Registry Agreement. 

Registry
Operator may seek review of any aspect of any Finding of Violation by a request for reconsideration under ICANN's Reconsideration Policy (as it may be amended from time to time), provided
that the request is submitted within the time allowed by the policy after the sending of the Finding of Violation. The submission of a request for reconsideration shall not be a prerequisite for
seeking review of the Finding of Violation by arbitration. 

Registry
Operator may also appeal the assessment of sanctions in the Finding of Violation by giving ICANN written notice of its intention to arbitrate (the "Arbitration Notice") under Subsection 5.9
of the Registry Agreement. Registry Operator shall deliver the Arbitration Notice no later than fifteen days after the Finding of Violation is sent, except that if a timely request for reconsideration
is submitted under ICANN's Reconsideration Policy (as it may be amended from time to time) the deadline shall be fifteen calendar days after ICANN has provided contractual notice that the ICANN Board
has voted to act or not to act on the request. If Registry Operator does not deliver an Arbitration Notice within the time described above, or the Registry Operator causes the arbitration to be
discontinued before decision, the amount of the sanctions assessed in the Finding of Violation shall be deemed final. 

If
a timely Arbitration Notice is delivered, the arbitration shall determine, based on the record, whether the Finding of Violation is warranted and the amount of sanctions is reasonable. The amount
of sanctions as determined appropriate according to the arbitration decision shall be deemed final. 

Payment of Sanctions  

Registry
Operator shall pay to ICANN the final amount of sanctions within thirty days after the amount of sanctions is deemed final. Failure to do so shall be a ground for termination under Subsection
5.4.7 of the Registry Agreement. 

APPENDIX F  

 
  Amendment No. 1 to Appendix F  
  

This
Amendment to the Registry-Registrar Agreement ("Amendment") dated as of the            day
of                        , 2002 between NeuLevel, Inc., a Delaware corporation, with offices
located at 46000 Center Oak Plaza, Building X, Sterling, VA 20166 ("Registry Operator") and                        , with its
principal place of business at                        ("Registrar").
 

WHEREAS,
Registry Operator and Registrar entered into that certain Registry-Registrar Agreement ("Agreement") dated as
of                        , 2001 ("Effective Date") and the Exhibits and Schedules
thereto (the Agreement, together with such Exhibits and Schedules are collectively referred to as "Transaction Documents"), concerning the provision of domain name registration services for the.BIZ
top-level domain ("TLD"). 

WHEREAS,
Registry Operator and Registrar now desire to amend certain terms of the Transaction Documents to clarify and supplement the parties' agreement; 

WHEREAS,
Registry Operator wishes to offer new Registry Services on the terms and conditions as approved by the Internet Corporation for Assigned Names and Numbers ("ICANN"). 

NOW,
THEREFORE, in consideration of the mutual covenants contained herein and other good and valuable consideration, receipt of which is hereby acknowledged, the parties agree as follows: 

1.
Capitalized terms used in this Amendment and not otherwise defined shall have the same meaning set forth in the Transaction Documents. 

2.
Registry Services. Registry Operator shall provide Registrar no less than thirty (30) days written notice of any new Registry Service (as defined in the Agreement) that has been approved by
ICANN
according to the procedures set forth in the Registry Agreement by and between ICANN and Registry Operator dated May 11, 2001. Such notice shall include the provision of information on pricing,
starting date and any additional terms and conditions regarding the new Registry Service. Such notice shall not be a substitute for the notice required in Section 2.4 of the Agreement. 

3.
By signing this Amendment, Registrar does not have a binding obligation to provide any or all of the Registry Services offered by Registry Operator. The decision of whether to offer a Registry
Service to its end users shall be made solely by Registrar. 

4.
Except as specifically modified by this Amendment, the terms and conditions of the Transaction Documents shall remain in full force and effect. 

IN
WITNESS WHEREOF, the parties have caused this Amendment to be duly executed as of the date first written above. 

	REGISTRY OPERATOR

NEULEVEL, INC.	 	REGISTRAR
	

By:	

	
 	

By:	

	Name:	 	 	Name:	 
	Title:	 	 	Title:	 

 
 

Amendment No. 1 to Registry Agreement  
  

Amendment
No. 1 effective as of 3 June 2003 ("Amendment") to the Registry Agreement dated 11 May 2001 ("Agreement"), by and between the Internet Corporation for Assigned Names and
Numbers, a not-for-profit California corporation ("ICANN"), and NeuLevel Inc., a Delaware corporation ("Registry Operator"). Capitalized terms used but not defined
herein shall have that meaning ascribed to them in the Agreement. 

Whereas,
on 2 June 2003 the ICANN Board of Directors approved certain revisions to the Agreement to implement a redemption grace period service
in the.biz top level domain operated by Registry Operator, on such terms set forth and described to the ICANN Board of Directors at the 2 June 2003 meeting of the ICANN Board of Directors; 

Whereas,
at such 2 June 2003 meeting of the ICANN Board of Directors, the Board of Directors authorized certain revisions to Appendices C, G, O and T to the Agreement and the preparation of
this Amendment in accordance therewith; 

Now,
Therefore, in consideration of the mutual agreements contained herein and intending to be legally bound hereby, the parties hereto amend the Agreement as follows: 

1.  The
following pages of Appendix C to the Agreement are hereby replaced by the substitute pages attached hereto, as follows: Page 1 (table of contents) is replaced with the
attached page 1; pages 132-135 (C.10 Grace Period) are replaced with the attached pages 132-138 (C.10 Grace Period and  C.11 Additional Services).

2.  Appendix G
to the Agreement is hereby deleted in its entirety and replaced with a new Appendix G, in the form attached
hereto. 

3.  Appendix O
to the Agreement is hereby deleted in its entirety and replaced with a new Appendix O, in the form attached
hereto. 

4.  Appendix T
to the Agreement is hereby deleted in its entirety and replaced with a new Appendix T, in the form attached
hereto. 

5.  Except
as expressly amended hereby, the Agreement and the Appendices thereto shall remain and continue in full force and effect. This Amendment may be executed in any number of
counterparts, all of which together shall constitute one and the same instrument. 

The
parties have duly executed this Amendment as of the date first written above. 

	THE INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS	 	NEULEVEL INC.
	

By:	

	
 	

By:	

	Name:	Richard Tindal	 	Name:	Dr. Paul Twomey
	Title:	President and CEO	 	Title:	Vice President, Registry Services

 
 

Amendment No. 2 to Registry Agreement  
  

Amendment
No. 2 effective as of 30 September 2004 ("Amendment") to the Registry Agreement dated 11 May 2001 ("Agreement"), by and between the Internet Corporation for Assigned
Names and Numbers, a not-for-profit California corporation ("ICANN"), and NeuLevel Inc., a Delaware corporation ("Registry Operator"). Capitalized terms used but not
defined herein shall have that meaning ascribed to them in the Agreement. 

Whereas,
on 30 September 2004 the ICANN Board of Directors approved certain revisions to the Agreement. 

Now,
Therefore, in consideration of the mutual agreements contained herein and intending to be legally bound hereby, the parties hereto amend the Agreement as follows: 

1.  Appendix C,
Section 10, page 133-134, regarding the Auto-Renew Grace Period to the Agreement are hereby replaced by the substitute page attached
hereto 

The
parties have duly executed this Amendment as of the date first written above. 

	THE INTERNET CORPORATION FOR ASSIGNED NAMES AND NUMBERS	 	NEULEVEL INC.
	

By:	

	
 	

By:	

	Name:	Richard Tindal	 	Name:	Dr. Paul Twomey
	Title:	President and CEO	 	Title:	Vice President, Registry Services

QuickLinks

Registry Agreement

Internet Assigned Numbers Authority Format and Technical Requirements for Requests to Change TLD Nameservers in the Root Zone

Internet Assigned Numbers Authority Format, Content, and Technical Requirements for Requests to Change TLD Contact Information

Functional Specifications

Performance Specifications

PERFORMANCE SPECIFICATION MATRIX

Service Level Agreement

CREDIT LOOKUP MATRIX

Table C1a

Table C1b

Table C2

Table C3

Table C4a

Table C4b

Registry-Registrar Agreement

Exhibit A Registrar Tool Kits

Exhibit B Engineering and Customer Service Support

Exhibit C Registrar's Registration Agreement [To be supplied by Registrar]

Exhibit D Policy on Transfer of Sponsorship of Registrations Between Registrars

Exhibit E Registry Operator's Operational Standards, Policies, Procedures and Practices

Exhibit F Registration Fees

Exhibit G Performance Specifications

Exhibit H Service Level Agreement

CREDIT LOOKUP MATRIX

Table C1a

Table C1b

Table C2

Table C3

Table C4a

Table C4b

Exhibit I Registry/Registrar IP Claim Service Agreement

Explanatory Statement

SCHEDULE A IP CLAIM SERVICE TERMS OF USE

Registry Operator Maximum Price Schedule

FEE TABLE

NeuLevel Equal Access and Nondiscrimination Practice

NEULEVEL EQUIVALENT ACCESS CERTIFICATION

EXHIBIT A ACCESS TO DATA POLICY

NeuLevel Proprietary Information

NeuLevel Registry Sensitive Information

NeuLevel Proprietary Information

ATTACHMENT 1 Examples of Proprietary & Registry Sensitive Information

ATTACHMENT 2 NON-DISCLOSURE AGREEMENT Proprietary Information

EXHIBIT B NON-DISCLOSURE AGREEMENT

EXHIBIT C REGISTRY BUSINESS ORGANIZATIONAL CONFLICT OF INTEREST AVOIDANCE CERTIFICATION

REGISTRY CODE OF CONDUCT

Registry TLD Start-Up Plan

Schedule of Reserved Names

.biz Registration Restrictions

Start-Up Enforcement and Enforcement of the Restrictions Document

Exhibit 2 Rules for Start-up Dispute Resolution Policy (the "Rules")

Exhibit 3 Restrictions Dispute Resolution Policy

Exhibit 4 Supplemental Rules for Restrictions Dispute Resolution Policy

Zone File Access Agreement

Whois Specification—Public Whois

Whois Provider Data Specification

Whois Specification—ICANN

Data Escrow Schedule, Content, Format, and Procedure

Exhibit A—Schedule for Escrow Deposits

Exhibit B—Escrow Deposit Format Specification

Exhibit C—Escrow Transfer Process

Exhibit D—Escrow Verification Procedures

Registry Data Escrow Agreement

RECITALS

AGREEMENT

Registry Operator's Monthly Report

Evaluation of Concepts

Additional Covenants of NeuLevel

Names Registered to Registry Operator

Sanctions Program

Amendment No. 1 to Appendix F

Amendment No. 1 to Registry Agreement

Amendment No. 2 to Registry Agreement

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00082-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00082-of-00352.parquet"}]]