SEC Info  
    Home      Search      My Interests      Help      Sign In      Please Sign In

Neustar Inc – IPO: ‘S-1/A’ on 6/28/05 – EX-10.5

On:  Tuesday, 6/28/05, at 5:00pm ET   ·   Accession #:  1047469-5-18239   ·   File #:  333-123635

Previous ‘S-1’:  ‘S-1/A’ on 6/10/05   ·   Next:  ‘S-1/A’ on 6/28/05   ·   Latest:  ‘S-1/A’ on 12/6/05

  in    Show  and    Hints

  As Of                Filer                Filing    For·On·As Docs:Size              Issuer               Agent

 6/28/05  Neustar Inc                       S-1/A                 14:31M                                    Merrill Corp/New/FA

Initial Public Offering (IPO):  Pre-Effective Amendment to Registration Statement (General Form)   —   Form S-1
Filing Table of Contents

Document/Exhibit                   Description                      Pages   Size 

 1: S-1/A       Pre-Effective Amendment to Registration Statement   HTML   1.47M 
                          (General Form)                                         
 2: EX-1.1      Underwriting Agreement                              HTML    163K 
 3: EX-3.1      Articles of Incorporation/Organization or By-Laws   HTML     92K 
 4: EX-3.2      Articles of Incorporation/Organization or By-Laws   HTML     70K 
 5: EX-4.1      Instrument Defining the Rights of Security Holders  HTML     15K 
 6: EX-4.2      Instrument Defining the Rights of Security Holders  HTML     15K 
 7: EX-5.1      Opinion re: Legality                                HTML     13K 
 8: EX-9.1      Voting Trust Agreement                              HTML    110K 
 9: EX-10.1     Material Contract                                   HTML  12.06M 
10: EX-10.4     Material Contract                                   HTML   4.97M 
11: EX-10.5     Material Contract                                   HTML   2.37M 
12: EX-10.7     Material Contract                                   HTML    260K 
13: EX-21.1     Subsidiaries of the Registrant                      HTML      9K 
14: EX-23.1     Consent of Experts or Counsel                       HTML     10K 


EX-10.5   —   Material Contract
Exhibit Table of Contents

Page (sequential) | (alphabetic) Top
 
11st Page   -   Filing Submission
"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
"UsTLD Undelegated Name Policy (Interim)
"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
"UsTLD Federal, State and Local Name Request Registration Process
"SF 30 Continuation of Block Narrative
"Schedule
"UsTLD ADMINISTRATOR CODE OF CONDUCT
"UsTLD Dispute-Resolution Policies
"UsTLD Dispute Resolution Policy
"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 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
"QuickLinks

This exhibit is an HTML Document rendered as filed.  [ Alternative Formats ]




QuickLinks -- Click here to rapidly navigate through this document

Exhibit 10.5

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:

        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 Ken Hansen at 202.533.2685, via fax at 202.533.2975, or via e-mail at Ken.hansen@neustar.com.

        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:

7


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:

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:

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:

10


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:

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.

        "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:

        "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.

14


15


        (c)   Disclosure.

16


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

        (e)   Penalties.

        (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:

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

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:

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

18


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

        (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—

19


        (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.

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

        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:

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—

        (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:

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

28


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

29


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 (s
pecify 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 (s
pecify 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:

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 (s
pecify 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:

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

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 (s
pecify 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:

43


        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
2.
Process Flow Description
3.
Business Case & Price By Option:

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

54


Step Two

Step Three

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.

60


        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 (s
pecify 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.

65


        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 (s
pecify 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 (s
pecify 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 (s
pecify 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 (s
pecify 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 (s
pecify 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.

78


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:

        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.

        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:

        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

October 15, 2004

November 1, 2004

November 15, 2004

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

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:

93


        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.

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.

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.

96


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—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:

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.

        IdentiBaseSMA 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

        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. NeuStar's Executive Oversight Committee will ensure the requisite resources are provided for successful service delivery. Graphic Omitted: Organization chart for NeuStar Executive Oversight Committee.]

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. NeuStar's Implementation Team is comprised of dedicated subject matter experts with a depth of experience successfully meeting program objectives. Graphic Omitted: Organization chart for usTLD Implementation Team.]

        [Exhibit A-3. NeuStar's usTLD Ongoing Operations Team will ensure all DOC program objectives are met. Graphic Omitted: Organization chart for usTLD Ongoing Operations Team.]

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.

A-9


 
   
    Ken Hansen, Director, usTLD Administration

Qualifications

 

More that 18 years of management experience in information technology for the Internet, IT and telecommunications industries. His expertise includes managing global operations for a multi-nations telecommunications company; supporting multiple call centers; managing and supporting large data centers; and customer and data center migrations. Accomplishments include managing and staffing network and infrastructure development and support organizations; meeting and exceeding Service Level Requirements (SLRs) for availability in order provisioning environments; and working with IXCs and LECs to automate electronic information exchange to support service provisioning.

Experience

 

Director, Corporate Development, NeuStar, Inc. (2000-Present)
    I.Responsibilities include the development of corporate strategy; growing NeuStar's service portfolio of communications infrastructure services; and identification and pursuit of new business opportunities including partnerships, joint ventures, mergers and acquisitions. Led the business development effort associated with ".BIZ".

 

 

Director, Marketing, Net2000 Communications (1999-2000)
    II.Led a team responsible for all aspects of the Net2000 product portfolio including Internet, e-commerce, Frame Relay, Private Line, Access, Local Service, Long Distance and vertical markets. Responsible for product strategy, product definition, pricing, development, launch, and ongoing product management.

 

 

Senior Manager, Local Service Product Management, Business Markets, MCI Communications Corporation (1989-1999)
    III.Complete product life cycle responsibility for the services associated with MCI's Local Service initiative. Areas of responsibility included product strategy, identification of product requirements, oversight of development, product launch, and ongoing product related activities.

 

 

Senior Manager, Access & Advanced Product Development, MCImetro (1995-1996)
    IV.Led the development of Carrier Access and Advanced Services for MCI's Local Service subsidiary. Primary responsibility included capability development, assessment of proposed services, and program management of new service implementation. Products included SONET based Dedicated Access, Switched Access, ISDN, AIN, and Voice.

 

 

Senior Manager, Global Accounts, Complex Bids / Customer Network Design (1992-1995)
    V.Directed an organization that developed network based solutions and provided third level technical support in pursuit of large complex revenue opportunities. This included; direct interface with customers, Global Account teams, Engineering, Operations, Finance, and Product Marketing.

 

 

Senior Manager Product Development, Global Communication Service (1991-1992)
    VI.Manage the development of MCI's global outsourcing offering targeted at U.S. based multinationals. This required development of short and long-term strategy; and interface with PTTs, Corporate Development and overseas offices. Successfully completed large outsourcing contracts with several large Fortune 500 companies.
     

A-10



Education

 

New York Institute of Technology, Islip, NY

 

 

B.S. Program, Telecommunications Management

 

 

Dianne Black, Program Manager

Qualifications

 

More than 12 years experience in Program Management, Product Management, Software Engineering Management and Telecommunications. Have successfully managed the implementation of over 50 large cross-functional programs with costs over 150 million.

Experience

 

Director, Program Management Office, NeuStar, Inc. (1999-Present)
    VII.Implemented and manage the Program Management Office at NeuStar. The PMO serves as an enterprise cross-functional program management team responsible for implementation of all corporate strategic projects including.biz systems, CARE OSS Clearinghouse, Code Administration System, NPAC Releases 1 through 4, and 10 other systems worth approx. 50 million in revenue within 2 years. Manage a staff of 15 people.

 

 

VIII.Implemented and manage the Project Support Office, part of the Program Management Office responsible for definition and implementation of the Project Management methodology. Created the NeuStar Project Management Handbook and created a library of processes to include software development processes. Also responsible for defining and delivering monthly project management training to all employees, coaching and mentoring. Produces a monthly project management newsletter to entire company, which highlights major project milestones, project successes, processes, best practices, and lessons learned. Participates in monthly operations reviews presented to executives. Program Management team participates in the PMI (Project Management Institute) approved Project Management Certification program.

 

 

Senior Manager, Local Systems Operations, MCI Communications, Inc. (1997-1999)
    IX.Managed 5 functions: Local Systems Project Management, Local Systems Training, Process Improvement (Business Process Reengineering), User Communications, and Web Development.

 

 

X.Responsible for end-to-end project management of 60+ Local systems development projects. Served as interface between Local Systems Development and Local User groups (Product Marketing, Provisioning, OE, Customer Service, Sales, etc.). Project Management including prioritization, budgeting, scheduling, requirements definition, life-cycle development coordination including integration and UAT testing. Matrix management of approx. 50 Local Systems Organizations and 30 Systems User Groups. Systems included Order Entry, Order Processing, Provisioning, Translations, Work Flow Manager, Traffic, Access and Subscriber Billing, Customer Service.

 

 

XI.Managed the Local Systems Training group. Train on approx. 30 Local Systems for approx. 1500 users. Training was mostly hands on technical training, but also support web-based training, web-based self-paced courses (CBT), and interactive video training.
     

A-11



 

 

XII.Managed a Process Improvement group (or Business Process Reengineering group). Projects included revamping systems audit processes, systems Help Desk processes, Billing Systems Operational Support Plan, Mass Markets Systems End User Support Plan and others. Group will assess, recommend, and assist with implementation for each project. Appropriate process standards and methodology are applied for each project.

 

 

XIII.Provided all user communications on all Local Systems Releases. Work with development to package release contents into user friendly material to be presented to the user community.

 

 

XIV.Managed web development group responsible for design, creation, and maintenance of internal Local Systems Operations web pages.

 

 

Senior Manager, Wireless Program Management, MCI Communications, Inc. (1995-1997)
    XV.Responsible for end-to-end project management of new city implementation. Successfully implemented 60+ wireless cities in approx. 1 year. Responsibilities include matrix management of approx 50 organizations including Legal/Regulatory, Carrier Relations, Marketing, Engineering, Fulfillment, Customer Service, Systems Development, and Sales. Developed and managed new city project plan containing approximately 150 tasks.

 

 

XVI.Responsible for Customer Care and Billing software selection. Included managing software vendor RFP and selection process. Through in depth analysis and due-diligence, developed "buy vs. build" business case and presented to Wireless Executives.

 

 

XVII.Responsible for systems requirements and implementation for the integration of Nationwide Cellular, a national cellular reseller acquired by MCI.

 

 

XVIII.Project Managed successful implementation of cellular fulfillment systems and operations. Tasks included review of external vendor candidates. Managed RFP process and vendor selection.

 

 

XIX.Project Managed successful implementation of Wireless Customer Service Systems and Operations. Tasks included operations planning, staffing, selecting and installing ACD, service processes/procedures, and system requirements and systems implementation.

 

 

XX.Successfully planned and implemented National Technical Service Vendor program to support cellular customer on-site servicing needs. Established program processes and procedures and system requirements.

 

 

XXI.Member of Wireless Strategy Team focused on Digital, PCS Resale, and Interconnect strategies. Included thorough research and analysis of CDMA, TDMA, and GSM technologies.

 

 

XXII.Managed a staff of 3 Managers and 18 staff.

 

 

Manager, New Technologies Marketing, MCI Communications, Inc. (1993-1995)
    XXIII.Responsible for project management of systems development, provisioning, order entry, customer service, fulfillment, and all operations for analog video phone product.
     

A-12



 

 

XXIV.Responsible for selection and then implementation of a product fulfillment vendor. Included developing all systems requirements and then managing development project through implementation. Entailed heavy vendor coordination.

 

 

XXV.Member of a team responsible for product management of set-top-box video phone, including product design, technology definition, manufacturing. Entailed heavy vendor management for both technology and manufacturing.

 

 

XXVI.Responsible for multimedia services development accessed via set-top-box video product.

 

 

Project Manager, MCI Communications, Corp. (1992-1993)
    XXVII.Responsible for successful implementation of Customer Marketing Database, a national marketing and lead generation system. Managed Consumer Exception Processing projects.

 

 

XXVIII.Responsible for Business Markets Customer Service Automation.

 

 

XXIX.Developed and facilitated Business Markets Systems Training.

 

 

Systems Analyst, MCI Communications, Corp. (1990-1992)
    XXX.Full life-cycle development of National LEC Interface System.

 

 

XXXI.Served as primary user interface contact.

 

 

XXXII.Represented MCI on OBF Subscription Committee to define order processing standards. Also stood on committee to define cellular interface standards.

Education

 

B.S., Industrial Engineering and Operations Research (IEOR) (1989)
    Virginia Tech, Blacksburg, VA

 

 

M.S., Telecommunications (1995)
    University of Denver, Denver, CO

 

 

M.S., Information Systems Management
    George Washington University, Washington, DC, 75% complete

 

 

Barbara Blackwell, Media Relations

Qualifications

 

Seasoned communications professional with over 10 years of experience in the Internet domain registry, telecommunications, government relations and legal arenas. Skilled in media relations; corporate positioning; brand building; crisis communications; event planning; issues management; public affairs and grassroots lobbying efforts.

Experience

 

Manager, Public Relations, NeuStar, Inc. (2000-Present)
    XXXIII.Creates and manages overall communications strategy and corporate positioning.

 

 

XXXIV.Managed nationwide outreach during spin off of parent company and initial launch and implementation phases of registry services.

 

 

XXXV.Responsible for the planning, coordination, and execution of all national and international media relations efforts.

 

 

XXXVI.Write and distribute press releases and develop tactical strategies for driving all existing and new business agendas.
     

A-13



 

 

XXXVII.Provide public relations counsel to executive management and other senior staff.

 

 

Sr. Public Relations Specialist, NeuStar, Inc. (1999-2000)
    XXXVIII.Serve as a central point of contact for local, national and international media. Research and develop responses on a broad range of issues, arrange interviews, and pitch global and targeted issue-oriented stories to reporters and producers.

 

 

XXXIX.Manage and coordinate registry/registrar public relations efforts with marketing team.

 

 

Sr. Public Affairs Specialist, American Bar Assoc. (1994-1999)
    XL.Plan and oversee media projects relating to program activities covering a wide range of legal issues, including international law, legal problems of the elderly, taxation, administrative law and regulatory practice.

 

 

XLI.Write and edit press releases, news advisories, pitch letters, op-eds.

 

 

XLII.Develop and implement public relations strategies to increase association visibility in targeted media markets.

 

 

XLIII.Formulate opportunities for press conferences and media events surrounding issues, meetings and product and service launches.

 

 

XLIV.Managed public relations budget operations for the Public Affairs Office.

 

 

Legislative Assistant, Senator Charles S. Robb (1992-1994)
    XLV.Drafted legislation and constituency responses for Senator approval.

 

 

XLVI.Tracked legislation and in the areas of housing, banking, telecommunications and gun control; coordinated legislative efforts with other congressional offices.

 

 

XLVII.Served as liaison to state constituency on behalf of Senator; monitored statewide issues and activity.

 

 

XLVIII.During successful re-election year, served around the state as press assistant.

Education

 

M.A. Candidate, Public Communication, George Mason University

 

 

B.A., Pre-Legal Studies, Virginia Commonwealth University

 

 

Member, Public Relations Society of America; Association of Black Women in Journalism. As active member of National Press Club, participate in regular Club activities and events.
     

A-14



 

 

James A. Casey, usTLD Policy

Qualifications

 

Mr. Casey has over seven years of experience with legal and policy matters relating to the Internet, advanced technologies and telecommunications. In this capacity Mr. Casey has assisted numerous companies in the identification and development of new technology business ventures and the development and execution of strategic policy initiatives supporting business activities. Mr. Casey's legal practice has focused on telecommunications and technology law, telecommunications ventures, energy projects, regulatory and transactional matters. And native American tribal affairs. Mr. Casey also has been involved with ongoing tribal telecommunications legislative and administrative efforts and has assisted the Federal Communications Commission as an expert on tribal telecommunications matters. In addition, Mr. Casey participates in international proceedings at the ITU and in other standards bodies, as well as on indigenous knowledge rights and biodiversity and has served as an expert witness with regard to indigenous treaty rights.

Experience

 

Director, Policy and Business Development, NeuStar, Inc. (2000-Present)
    XLIX.Develop and implement strategic policy initiatives.

 

 

L.Monitor policy activities for consistency with NeuStar neutrality principles.

 

 

LI.Monitor international standards and treaty body activities.

 

 

LII.Assess and develop new business opportunities.

 

 

LIII.Conduct governmental relations activities.

 

 

Associate, Greenberg Traurig (2000-2001)
    LIV.Assist in the development of a tribal telecommunications, technology and economic development practice.

 

 

Associate, Morrison & Foerster (1995-2000)
    LV.Practice focused on representation of common carrier clients (wireline and wireless) before the Federal Communications Commission

 

 

LVI.Assisted tribal governments in telecommunications, utility, legislative and other matters, including development of tribal telephone and communications companies.

 

 

LVII.Mass media (radio, television), contract negotiation and drafting, rulemaking proceedings, administrative and federal litigation, satellite, common carrier matters, personal communications services, emergent technologies, and infrastructure issues. Practice also included representation of Internet access companies on matters relating to computer, intellectual property and Internet law.

 

 

Associate, Fletcher, Heald & Hildreth, P.L.C. (1994-1995)
     

A-15


    LVIII.Represented communications clients before the Federal Communications Commission. Experience includes mass media (radio, television), contract negotiation and drafting, rulemaking proceedings, administrative and federal litigation, satellite, common carrier matters, personal communications services, and infrastructure issues. Assisted Native tribal governments in the development of telecommunications infrastructure and provide guidance in regulatory matters and the intersection of Federal Indian Law and Telecommunications law. Other practice areas included intellectual property, computer law, and entertainment law.

 

 

Summer Associate, Birch, Horton, Bittner & Cherot (1993)
    LIX.Conducted legal research in various areas including federal and state litigation and administrative law. Prepared legal memoranda, briefs, executive employment contracts, comments on proposed rule-makings and administrative action response letters and assisted in lobbying efforts. Experience includes: tax status of non-profit organizations, sovereign immunity, FCC comparative hearings, intellectual property liability of spin-off companies, executive contract preparation, good faith appeal to the Mineral Management Service (Department of the Interior).

 

 

Research Assistant, Cornell Law School (1992-1992)
    LX.Researched and wrote on the historical development of the Fourth Amendment to the United States Constitution and the United States Supreme court's use of that history in search and seizure cases. Assisted in other research and materials collection as needed.

 

 

Litigation Assistant, Brown and Bain (1989-1991)
    LXI.Researched and organized case materials for high technology litigation. Experience includes: video game and video special effects patents, trade secret theft, unfair competition, antitrust and class action litigation. Duties included discovery, and factual research and analysis. Assisted in the preparation of summary judgment motions, pre-trial briefs and other filings.

Education

 

J.D., Cornell Law School (1994), specialization in international legal affairs

 

 

B.A., History (1988), extensive coursework in electrical engineering and computer science

 

 

David H. Crocker, Technical Industry Liaison

Qualifications

 

Management, design and development for all aspects of Internet and distributed systems, emphasizing innovate opportunities and aggressive delivery schedules.

Experience

 

Principal, Brandenburg InternetWorking (1991-Present)
    LXII.Consultancy with focus on use of intranets and the Internet. Participate in startup business planning and funding

 

 

LXIII.Assist in development of intellectual property, founded trade associations

 

 

LXIV.Recent projects included standard for facsimile over the Internet; specifications of extensions to Internet email and information services; design of transport-independent deferred-attachment API; and IP network design for contention-access ATM-based interactive cable television service.

 

 

Manager (Internet tech transfer), Net Systems Lab, DEC (1989-1991)
     

A-16


    LXV.Created TCP/IP technology-transfer corporate resource. Delivered early firewall and router products and network management administration tool.

 

 

VP Engineer, The Wollongong Group (1987-1989)
    LXVI.Led product development, guiding end-user and OEM open systems software products, including TCP/IP and ISO-OSI stacks, SNMP-based network management station and TCP/OSI transition products along 9 separate sets of product lines.

 

 

LXVII.Responsible for staff of 50, providing software engineering, configuration management and project support, and corporate network and computing services.

 

 

Development Manager, Undermann-Bass (1985-1987)
    LXVIII.Delivered company's initial suite of TCP/IP software products, for PCs, terminal concentrators and internetwork routers.

 

 

Director, Sys. Development, MCI Digital Info Svcs Corp. (1983-1985)
    LXIX.Met aggressive development schedule, creating application, directory and data processing components for MCI Mail, a unique, $50 million, distributed national electronic mail service.

 

 

LXX.Developed interactive and remove batch access for 140,000 users, including delivery for Telex inbound and outbound, as well as hardcopy with letterhead and signature graphics, and access for communicating word processors.

 

 

Principal Investigator, Electrical Engineering, University of Delaware (1978-1982)
    LXXI.Developed Unix-based email relay for heterogeneous networks. System was an exemplar for "UA/MTA" architecture of CCITT X.400 email standards.

 

 

LXXII.Operated national mail relay service for the Army and for NSF's CSNet, precursor to NSFNet.

 

 

LXXIII.Authored various Internet protocol specifications, especially for electronic mail.

Education

 

Doctoral Program, Computer Science, University of Delaware (1992)

 

 

M.A., Communication, Annenberg School, USC (1977)

 

 

B.A., Psychology, UCLA (1975)

 

 

Thomas G. McGarry, Transition Team

Qualifications

 

Eighteen years experience in network engineering, network and technology planning, and telecommunications management. Significant experience in the internet and registry related technology. Represent NeuStar as SME on internet and domain name space.

Experience

 

Chief Technical Strategic Technical Initiatives, NeuStar, (1998-Present)
    LXXIV.Manage a group of subject matter experts (SME) who provide technical representation for NeuStar at various industry meetings and forums.

 

 

LXXV.Drive the development of industry standards for voice over IP technologies. This work is primarily performed at the Internet Engineering Task Force (IETF) and European Telecommunication Standards Institute (ETSI).
     

A-17



 

 

LXXVI.Interface directly with the federal and state regulators in North America as well as international regulators regarding numbering policy decisions. This is NeuStar's responsibility as the North American Numbering Plan Administrator (NANPA).

 

 

LXXVII.Provide technical support with regard to telecommunications numbering issues for the North American and international communications industry.

 

 

LXXVIII.Support the development and advancement of DNS, BIND, and registry related technologies at the IETF.

 

 

LXXIX.Manage the process of developing new requirements in an open forum for future software releases to NeuStar's Number Portability Administration Center (NPAC). The NPAC is a registry service for ported telephone number information NeuStar has been contracted to provide to the North American communications industry.

 

 

LXXX.Evaluate new business opportunities through representation at industry meetings and forums.

 

 

LXXXI.Manage the introduction of new business opportunities into NeuStar business development processes.

 

 

LXXXII.Acted as Director of Network Engineering for two data centers and six office locations for eight months prior to filling the vacancy.

 

 

Director-Network Engineering, Geotek, Inc. (1997-1998)
    LXXXIII.Manage a group of engineers and administrators in the deployment of network and switching equipment and software, and communications facilities.

 

 

LXXXIV.Interface with facility providers for timely deployment of cell site T1s.

 

 

LXXXV.Plan and deploy interconnection with the public switched telecom network.

 

 

LXXXVI.Manage the deployment and selection of a Frame Relay network for internal communications.

 

 

LXXXVII.Develop hardware and software requirements and configurations for network equipment; DACS, router, alarm, modem, terminal server, synchronization.

 

 

LXXXVIII.Coordinate the purchase and deployment of network and switching equipment.

 

 

LXXXIX.Provide network equipment documentation and support to Geotek field technicians.

 

 

Staff Director—Number Portability Project Management 7, NYNEX Corp. (1996-1999)
    XC.Provide company wide project management for the implementation of number portability capabilities in the NYNEX network.

 

 

XCI.Provide a requirements document to address number portability's impact on NYNEX's signaling and switching network, and related systems.

 

 

XCII.Develop and gain approval for three-year funding requirements for number portability.
     

A-18



 

 

XCIII.Determine 5ESS, 4ESS, DMS10, DMS100, DMS200 TOPS and remote switch software requirements.

 

 

XCIV.Participated in the selection of hardware and software for the deployment of an overlaid intelligent network to provide number portability.

 

 

XCV.Participated in the network design and routing for the overlaid intelligent network.

 

 

XCVI.Represent NYNEX to state and federal regulators, industry committees, and competitors with regard to network and systems requirements for number portability.

 

 

Staff Director—Network & Technology Planning (1995-1996)
    XCVII.Act as Subject Matter Expert with regard to numbering related issues for NYNEX.

 

 

XCVIII.Evaluate the impact to NYNEX of numbering related issues. Develop the NYNEX position, and drive industry direction towards that position at the Industry Numbering Committee (INC).

 

 

XCIX.Provide the NYNEX interface to the North American Numbering Plan Administrator for multiple issues including NPA exhaust planning and reservations.

 

 

C.Successfully lead an effort within the INC to reserve 200 carrier identification codes (CIC) for intranetwork use, available to all carriers.

 

 

CI.Solely responsible for network related number portability issues within NYNEX.

 

 

CII.Lead NYNEX's participation in the NY number portability trial, an effort driven by the NY State Public Service Commission (PSC). Successfully drove decisions involving cost and network reliability to NYNEX's favor.

 

 

CIII.Actively participate in NY PSC effort with regard to deploying number portability. Participate on multiple subcommittees responsible for planning the deployment of new AIN technology and number portability databases.

 

 

CIV.Provide input to Lucent and Nortel with regard to their methods of deploying number portability solutions in end office switches, operator service switches, tandem switches, STPs, SCPs, and operations support systems.

 

 

Manager Strategic Planning—Switch and Network Technology, NYNEX Mobile Communications Company (1993-1995)

 

 

CV.Provide evaluation, recommendation, and development of new products, services, and technologies on a company wide basis.

 

 

CVI.Provided network requirements to equipment vendors and interconnected carriers for new products and services based on Marketing's product definition.

 

 

CVII.Project managed the implementation of new products and service with the line engineering organizations, equipment vendors, and interconnected carriers across multiple markets.

 

 

CVIII.Researched and evaluated new hardware and software developments and designs for cellular applications.
     

A-19



 

 

CIX.Participated on digital deployment core team, which developed NMCC's digital deployment strategy.

 

 

CX.Analyzed and evaluated AT&T digital hardware developments.

 

 

Network Services Director, MobiLink (1992-1993)
    CXI.Chosen by NMCC upper management for a temporary assignment on a multifunctional task force (7 members) responsible for starting-up MobiLink, an international brand name for cellular service supported by 17 major cellular carriers.

 

 

CXII.Developed network requirements; including performance engineering, automatic roaming, roamer validation, and dialing plans; for member companies.

 

 

CXIII.Participated in Board of Directors Meetings (consisting of 7 cellular carrier Presidents) providing definitions of requirements and status of member company's progress.

 

 

CXIV.Worked individually with member companies to advise on methods in which to meet network requirements.

 

 

Manager, Network Engineer (1989-1992)
    CXV.Provide traffic engineering, equipment engineering, and implementation engineering for switch, cell, and network equipment and trunks for the NY Metro cellular network.

 

 

CXVI.Developed and managed the organizational structure to provide equipment engineering, traffic engineering, and network planning for NY Metro cellular network.

 

 

CXVII.Supervised four Engineers and three support personnel.

 

 

CXVIII.Planned, engineered, and procured all switch, cell site, and network equipment utilized in the NY Metro cellular network.

 

 

CXIX.Planned, engineered, and procured the NY Metro voice and data facilities network.

 

 

CXX.Coordinated the implementation of equipment with various internal organizations and vendors.

 

 

CXXI.Responsible for the implementation of proper contract approval, accounting, and purchasing processes and procedures.

 

 

Manager, Network Planning (1987-1989)
    CXXII.Plan and implement network interconnection facilities and equipment for NY Metro cellular network.

 

 

CXXIII.Defined and developed the Network Planning role in the NY Metro cellular network.

 

 

CXXIV.Instituted cost savings methods and procedures for network interconnection and growth.

 

 

CXXV.Planned and implemented the first cutover of a cellular switch to a remote location in the NY Metro cellular network.

 

 

CXXVI.Supervised one Engineer.
     

A-20



 

 

CXXVII.Total responsibility for planning voice network for the NY Metro cellular network.

 

 

CXXVIII.Solely responsible for equal access implementation and coordination from the 1988 to 1992 in the NY Metro cellular network.

Education

 

1983-Present, Advanced Technical Training; Numerous advanced engineering courses in communication system design, digital, communications systems, cellular systems, telephone technology, spread spectrum theory and design, Motorola and AT&T cellular systems, and advanced intelligent network technology.

 

 

May 1983, B.S., Business Administration, University of Buffalo, Buffalo, NY

 

 

Jeffrey J. Neuman, ICANN Relations

Qualifications

 

Mr. Neuman is the Director of Law and Policy at NeuStar, Inc. He is responsible for the oversight of intellectual property law and policy matters, as well as information technology licensing. He is the external liaison for both NeuStar and NeuLevel, Inc. with the Internet Corporation of Assigned Names and Numbers (ICANN) and the Domain Name Supporting Organization.

 

 

He has testified before the Subcommittee on Courts, the Internet and Intellectual Property of the Committee on the Judiciary, U.S. House of Representatives Oversight committee regarding "ICANN, New gTLDs and the Protection of Intellectual Property."

 

 

Prior to joining NeuStar, his practice focused on representing telecommunication providers and e-commerce companies in matters involving technology licensing, intellectual property, and domain name disputes. Mr. Neuman is a frequent speaker on issues involving intellectual property, domain names, online dispute resolution and the introduction of new generic top-level domain names. He has been featured in articles all over the globe, including the New York Times, Wired Magazine, and the June edition of IP Asia, one of the leading intellectual property trade magazines for intellectual property practitioners in Asia, discussing the introduction of the new dot-biz top-level domain.

Experience

 

Director, Law and Policy NeuStar, Inc. (2001-Present)
    CXXIX.Serves as Director of Policy and Intellectual Property and is responsible for policy development for dot-biz.

 

 

CXXX.Performs public relations functions for dot-biz registry and the introduction of top-level domains.

 

 

CXXXI.External liaison with the Internet Corporation for Assigned Names and Numbers (ICANN), the Domain Name Supporting Organization of ICANN, the gTLD Registry Constituency of ICANN and the Intellectual Property Constituency.

 

 

CXXXII.Responsible for the protection of NeuStar's intellectual property assets, domain name disputes, and Internet-related matters.

 

 

CXXXIII.Preparation and negotiation of agreements for technology and software licensing, hardware and software system development, and joint venture/marketing relationships.

 

 

Information Technology Associate, Greenberg Traurig, LLP/Akn, Gump, Strauss, Hauer & Feld, LLP (1999-2001)
     

A-21


    CXXXIV.Representation of domain name registry in intellectual property and policy-related matters before the Internet Corporation for Assigned Names and Numbers (ICANN), the United States House of Representatives and the European Commission.

 

 

CXXXV.Counsel and representation of clients in the protection of intellectual property assets, trademark infringement, copyright infringement, unfair competition, domain name disputes, and Internet-related matters; Representation of clients in trademark matters before the United States Patent and Trademark Office and domain name disputes before the World Intellectual Property Organization (WIPO).

 

 

CXXXVI.Preparation of agreements for technology and software licensing, hardware and software system development, telecommunication system acquisitions, and joint marketing and value added reseller relationships.

 

 

CXXXVII.Preparation of Internet agreements for web site development and hosting, electronic commerce, terms of service, spamming and privacy policies.

 

 

CXXXVIII.Advice and counseling of clients in the export of encryption technology; Representation of clients before the United States Department of Commerce's Bureau of Export Administration.

 

 

CXXXIX.Participation in the formation of ICANN as well as WIPO's hearings on alternative dispute resolution mechanisms for domain name disputes.

 

 

Associate, Arter & Hadden, LLP (1997-1999)

 

 

Representation of clients in trademark infringement, copyright infringement, and unfair competition, as well as in Internet law issues. Published several articles on the creation, development and new management of the domain name system. Participated in the formation process of ICANN as well as WIPO's hearings on alternative dispute resolution mechanisms for domain name disputes. Advice and counseling in matters involving Internet issues including the protection of clients' intellectual property rights on the Internet, domain name registration, dispute resolution mechanisms, spamming, website development agreements, Internet privacy policies, and web hosting agreements.

Education

 

J.D., The George Washington University Law School, Washington, DC, 1997,
cum laude

 

 

B.A., Political Science, Pennsylvania State University, University Park, PA, 1994

 

 

B.A., Labor and Industrial Relations, 1994,
summa cum laude

 

 

Phi Beta Kappa

 

 

Robert S. Nichols, Product Development

Qualifications

 

More than 14 years of experience in telecommunications and high-tech industries where he has played significant roles in launching new products and businesses.

Experience

 

Director, IP Services Business Development, NeuStar, Inc. (2000-Present)
    CXL.Manages marketing and product related activities in pursuit of commercializing a suite of Global Directory Services, which includes national and international ENUM administration as well as next generation signaling services that bring intelligent network capabilities to IP based networks.
     

A-22



 

 

Director, Product Management, USinternetworking, (1999-2000)
    CXLI.USi's Product Management lead for the Enterprise Messaging and Collaboration Business Unit. Primary responsibilities include strategic development of the product roadmap, product and system development, marketing rollout and ongoing product management.

 

 

CXLII.Developed market rollout strategy and launched the Enterprise Messaging and Collaboration Business Unit in September 1999. Product introduction responsibilities included press and analyst briefings, product packaging, positioning, pricing and promotion.

 

 

CXLIII.Managed a team of product managers and developers for ongoing management of the core messaging service based on Microsoft Exchange, as well as enhanced features including document management, unified messaging, real time voice and data collaboration, and wireless access integration.

 

 

CXLIV.Directed a team of developers in defining, building and launching a Customer Extranet, designed to allow USi Clients online access to performance and billing reports, implementation tracking, contracts, as well as initiate service changes.

 

 

CXLV.Directed corporate marketing teams in development of marketing collateral, press releases, sales training documents, advertising, direct mail, case studies and white papers, TCO tools, and the corporate web site.

 

 

CXLVI.Led business development activities with Microsoft Independent Software Vendors (ISVs), including evaluation, negotiation, service development and implementation of advanced service features that integrate with the Microsoft Exchange platform.

 

 

Sr. Manager, New Business Development, Iridium LLC (1997-1999)
    CXLVII.Iridium's Service Development lead regarding new business initiatives involving external network integration and commercial reselling opportunities. Primary activities included initial development, product and market rollout, as well as the ongoing product management and evolution of the Iridium World Calling Card Service, and the Iridium High Speed Data Service.

 

 

CXLVIII.Launch and ongoing service management responsibilities for the Iridium World Calling Card Service. Responsibilities included evaluating global business partners, negotiating partner agreements, developing global distribution and marketing rollout, as well as pricing, positioning and worldwide promotion.

 

 

CXLIX.Service development of the Iridium High Speed Data Service (Integrated Inmarsat High Speed Data). Responsibilities included business plan development, external network integration, operation and customer service development, billing integration, global product distribution and market launch.

 

 

CL.Service development of the Iridium/(Inmarsat) Aeronautical Service. Responsibilities included business plan development, external network and billing integration, global card distribution, and market launch.

 

 

Manager, Satellite Telephone Products, Motient, Inc. (Formerly American Mobile Satellite Corp.(AMSC) (1994-1997)
    CLI.AMSC's product management lead and among the principal architects for marketing and operational related issues, including all SKYCELL service and product development projects.
     

A-23



 

 

CLII.Managed a team of product managers with responsibility for development, implementation and ongoing support of AMSC's SKYCELL services, including voice, data and fax.

 

 

CLIII.Managed systemic and configuration specific development programs to ensure system level functional performance, including network enhancements, subscriber equipment and ancillary switching platforms.

 

 

CLIV.Managed product development life cycles for SKYCELL product lines including vendor management, operational and customer service support, pricing and market launch.

 

 

Business Analyst, Dun & Bradstreet (1987-1993)
    CLV.Developed comprehensive marketing and credit reports, resulting in the assignment of composite credit appraisals. Assigned ratings based upon financial strength, industry norms, management experience, tend of entity, and payment record.

Education

 

B.S. in Business Administration, concentration in Marketing Management; Minor degree in philosophy, University of Delaware, Newark, DE. June 1987

 

 

M.B.A. University of Colorado, Colorado Springs, CO. July 1999

 

 

John Spengler, Customer Service

Qualifications

 

Twenty-five years management responsibility in the areas of communications, information systems and customer service.

Experience

 

Director Business Operations, NeuStar, Inc. (2001-present)
    CLVI.Directs and Operates the Customer Support Center for the.biz Registry. Responsible for developing new service processes and procedures. Responsible for delivery of service within Service Level Objectives.

 

 

Project Manager, Integrion Financial Network (1997-2000)
    CLVII.Overall project management responsibility for the transition of all the Visa Interactive systems to the Interactive Financial Services platform for Integrion. The transition of all back office services to CheckFree platforms. Primary vendor coordination responsibility for IBM, an annual contract of $9.0 million.

 

 

Manager Global Operations Support, Visa Interactive Inc. (1994-1997)
    CLVIII.Management responsible for a software maintenance team of nine programmers. Team was responsible for the quick resolution of system problems and changes. Managed assigned projects, controlled ad hoc system reports and their distribution. Negotiated maintenance contract with Logica, a software house, for the CSMS system and managed the resulting team of eight consultants.

 

 

International Project Manager, Visa Interactive Inc.
    CLIX.Responsible for coordination and implementation of Visa Interactive Electronic Home Banking Services in the European Market. Implemented the first international electronic home banking for Barclays Bank in the UK. The pilot was a significant success and the service went into full production in April,1997.

 

 

Administrative Manager,Visa International Inc. (1981-1994)
     

A-24


    CLX.Prepare and track the Business Resumption and Administration departmental budget. On-site representative for Business Resumption and Site Emergency requirements. Provide support to the Department Senior Vice President by preparing internal management presentations, analyzing and writing reports. Project manage the establishment of physical security standards for the worldwide data centers, completed site evaluations, recommend improvements and track each center for completion.

 

 

Senior Project Manager
    CLXI.Responsible for the construction of a fully redundant 65,000 sq. ft. data center and ancillary structures, from the design phase through operational occupancy. The $32.6 million dollar budget included a negotiated ten-year lease. The project completed on time and under budget, with less than 4% in change orders. The environmental systems included three 1250 KVA generators, two 600 Ton cooling towers.

 

 

Supervisor, Project Implementation and Facilities
    CLXII.Responsible for coordinating new services to be implemented at the McLean Computer Operations Center. Participate in the projects at an early stage and function as central coordinator during implementation. Supervised four hourly employees in the day-to-day activities of maintaining and servicing of office facility.

 

 

Department Head Technical Support
    CLXIII.Administrative responsibility for six senior technical support analysts. Assigned personnel to hardware and software projects and directed their activities. Prepared operational cost estimates for current and proposed projects; evaluated vendor proposals for purchase of hardware. Coordinated the Operations Center Budget for three years.

 

 

Department Head Customer Service
    CLXIV.Directed personnel and resources to provide, maintain, and operate a $3.2 million international credit authorization center. Responsible for productivity, growth, morale and job satisfaction for 70 employees. Established programs, plans and budgets for an efficiently run center. Results: A 100% improvement in morale with a 50% improvement in productivity and a substantial reduction of overtime expenses.

 

 

Head Telecommunication/Data Processing Analyst
    CLXV.Supervised four senior analysts in the design, implementation and maintenance of a $15. million worldwide data network. Monitored and analyzed the performance of a 100 line WATS network on an Automatic Call Distributor.

Education

 

Center for Creative Leadership

 

 

Electronic Computer Programming Institute

 

 

Certificate computer programming.
     

A-25



 

 

Frankie Russell, Product Marketing

Qualifications

 

More than 16 years experience in telecommunications, including business development, strategic planning, quality assurance, product management, brand management, and life cycle management for products and services in telecommunications industry. Expertise includes working with IXCs, ILECs, and CLECs to launch new products and services; media and public relations; and marketing communications.

Experience

 

Director, Product Marketing, NeuStar, Inc. (2001-Present)
    CLXVI.Directs and coordinates activities concerned with research and development of new concepts, ideas, basic data on and applications for, organization's products and services.

 

 

CLXVII.Reviews and analyzes proposals submitted to determine if benefits derived and possible applications justify expenditures.

 

 

CLXVIII.Develops plan for Industry outreach for OSS services.

 

 

CLXIX.Develops and review marketing materials for new and existing products and services.

 

 

Group Manager, Identity Services, Network Solutions, Inc. (1999-2000)
    CLXX.Launched five enhanced services resulting in over $10 million in new revenues.

 

 

CLXXI.Negotiated deals with vendor companies to secure technology for enhanced services; programs included multiple-year registrations which established the company's renewal processes; dot com essentials, the company's first bundled product; Expedited Transfer Service, resulting in over $4 million in its first year; Internet Keywords, a partnership with Real Names Corporation; and 800 number domain names, a "Call or Click" program concept that promotes purchasing a domain name to match an existing 800 number.

 

 

Independent Consultant, McKinley Marketing Partners (1998-1999)
    CLXXII.Senior-level Independent Consultant leading strategic product development projects for Bell Atlantic (now Verizon), Network Solutions, and Cable and Wireless.

 

 

CLXXIII.Founder of consulting firm, Out-of-the-Box Marketing, Inc. Executed consulting contracts with WinStar Communications, Inc., City First Bank, and Kalidescope Kollections. First year billings exceeded $250,000.

 

 

CLXXIV.Group Manager, Quality Assurance, TELE-TV Systems (joint venture between Bell Atlantic, NYNEX and Pacific Telesis) (1995-1997)

 

 

CLXXV.38% improvement in productivity achieved in first six months. Led six QA analysts in support of software metrics, defect tracking/resolution, and documentation for video services product being developed for the company and a major international client. Recruited to this position by exemplifying senior and technical team leadership abilities necessary to represent the company internationally.

 

 

Marketing & Communications Manager (1995-1996)
     

A-26


    CLXXVI.Selected for this high-profile PR position to work closely with executive team in launching the company's introduction into highly competitive digital TV market. Served as spokesperson interfacing with TV, computer, and telecommunications media and the company's key international partners.

 

 

Marketing and Media Relations Manager, Video Services, Bell Atlantic (1995)
    CLXXVII.Chosen as spokesperson for leader in video services. Conceptualized first health and fitness channel for TELE-TV.

 

 

Marketing Manager, FeatureFAX (1991-1994)
    CLXXVIII.Spearheaded primary and secondary research for first-of-its-kind enhanced facsimile product. Developed specialized marketing concepts to direct initial marketing strategies. Resolved regulatory constraints through partnership with Cable & Wireless.

 

 

Marketing Manager, Thinx Software—Information Services (1990-1991)
    CLXXIX.Conducted initial market analysis for company's first venture into computer software. Served as primary Microsoft contact as Independent Software Vendor representative. Interpreted market readings and recommended product withdraw strategy. Successfully identified buyer and sold product.

 

 

Product Manager, Operator Transfer Service, Carrier Marketing and Operator Services (1987-1990)
    CLXXX.Added $4 million to the bottom line by launching innovative operator transfer service; significantly improved relations with top long-distance carrier customers, including AT&T, MCI, and Sprint.

 

 

Assistant Product Manager, Bell Atlantic Calling Card (1984-1987)
    CLXXXI.Championed proactive sales/marketing cultures (100 reps with Fortune 500 clients) to support initial launch of company's first calling card. Developed marketing campaigns targeting strategic market segments.

Education

 

MS Candidate, Engineering Management, George Washington University

 

 

BA, Business Management & Marketing, National Louis University

 

 

Member, Association of Business and Professional Women; Association of Black Women Entrepreneurs. Serves as Vice Chairman, College Partnership Program, Fairfax County, Virginia.

 

 

Spencer Stefansic, Systems Engineering

Qualifications

 

Over nine years of experience in the telecommunications and technology industries developing client/server database systems; Internet/intranet/extranet applications and managing project implementations and large systems/IT organizations. His expertise includes implementation and management of middleware billing systems; program management of disaster recovery operations for a national wireless operator's data warehouse environments. As a manager, his responsibilities include staffing and managing over 75 employees located in four different regions; contract negotiations and vendor management; and process control.

Experience

 

Director, Systems Engineering, NeuStar, Inc. (2001-Present)
     

A-27


    CLXXXII.Director of a 45-person group responsible for implementing cutting edge systems at the enterprise level. Systems include the.BIZ Top Level Domain registry system; and systems providing telco-specific services such as the CARE Clearinghouse, Code Administration System.

 

 

CLXXXIII.Management responsibilities include contract negotiation/vendor management, budget management and process control, invoice reconciliation, and monthly expense/capital report reconciliation

 

 

Director, Billing/Middleware Development, Nextel Communications (2000-2001)
    CLXXXIV.Responsible for the middleware development group, and after internal reorganizations, management and support of the Nextel billing systems group, to include production support, and reporting development organizations. This expanded group has also been tasked with design and implementation of an Enterprise Application Integration system, based on IBM's MQSeries products, with a goal of replacing the current "spider web" of point-to-point system interfaces.

 

 

CLXXXV.Management/budgetary responsibilities expanded to include responsibility of a 75-person group in four cities, with a $25 million+ budget.

 

 

Director, Advanced Communications, Nextel Communications (1999-2000)
    CLXXXVI.Director of a 40-person group (with locations in Atlanta, Denver and Reston) responsible for implementing cutting edge middleware systems at the enterprise level. Systems include an EDI/XML based B to B infrastructure for transmitting bills to large corporate customers electronically; architecture and implementation of an enterprise wide database replication backbone; call detail Traffic Management systems; and development of an EJB-based API platform/system to the NEXTEL billing system, a proprietary product with no native API access.

 

 

CLXXXVII.

 

 

CLXXXVIII.Management responsibilities include contract negotiation/vendor management, budget management ($12 million budget) and process control (assurance and adherence to Nextel policies), invoice reconciliation, and monthly expense/capital report reconciliation.

 

 

Senior Manager, Web Architecture and Infrastructure, Nextel Communications (1997-1999)
    CLXXXIX.Responsible for program management of the design, development and deployment of Nextel intranet and Internet applications, using Netscape web and Oracle web/database technology. Systems include an Oracle Application Server based rate plan workflow application, MapInfo-MapXtreme web based Internet cellular coverage application, and the Nextel Online Web Sales systems.

 

 

CXC.Additional responsibilities included the program management of the National Activity Report (NAR) disaster recovery operation. Coordinated all system stabilization, data and software recovery/repair operations. Responsible for complete project management of all technical resources needed to stabilize the data warehouse environment, establish process control, develop/implement disaster recovery plans and create a 7x24 rapid response process.
     

A-28



 

 

CXCI.Operated in a dual capacity providing special assistance to executive leadership (CIO, VP Development) by leading/supporting special projects research (Electronic billing payment/presentment), application gateway architecture development, and business systems integration support.

 

 

Senior Systems Manager, OAO Corporation (1997-1997)
    CXCII.Technical Manager, providing technical expertise and program management in the architecture, development and deployment of intranet applications, using Netscape web and Oracle database technology. Projects include a classified scientific data warehouse (the Virtual Data Center, or VDC) for the Ballistic Missile Defense Organization (BMDO), accessed via a geographically distributed intranet web infrastructure, utilizing Java and CORBA technologies. Responsible for coordinating the development efforts of four separate BMDO technical groups, each group with a different mission and location within the organization.

 

 

Principal Consultant, Netscape Communications (1996-1997)
    CXCIII.Technical/Project Manager, providing consulting expertise in the development, installation and deployment of intranet/Internet applications, using Netscape web technology. Projects include an electronic document management system, messaging solutions, Internet content publishing systems, and web based executive information systems, in the healthcare and telecommunications verticals. Responsible for engagement management, as well as exploiting new consulting opportunities in conjunction with the product sales force.

 

 

Senior Principal Consultant, Oracle Corporation (1993-1996)

 

 

CXCIV.Technical Manager, providing consulting expertise in the installation and deployment of the Oracle Transparent Gateway for M. Applications developed include an interactive voice response system, accessing legacy data through the gateway. Management responsibilities include engagement and project management of on-site consultants; placement of consultants at customer sites; and customer relations.

 

 

CXCV.Technical Team Leader, provided database/application design review and CASE expertise, using Designer/2000, for a data warehouse environment consisting of an Oracle7 v7.2 database, storing 300 million records and requiring 500 Gigabytes of storage.

 

 

Project Manager, Suncoast Scientific, Inc. (1991-1993)
    CXCVI.Lead eight programmers/analysts through analysis, logical and physical database design activities, using Oracle™ CASE, for a state government agency client/server application. Provided development expertise building eight applications of over 130 forms using Oracle Forms and Reports applications, with an Oracle v6.0 database.

 

 

U.S. Air Force (1983-1991)
    CXCVII.Aircrew member, operations and systems design.

Education

 

B.S., Physics, University of West Florida

 

 

Richard J. Tindal, Channel Management

Qualifications

 

Over 15 years experience in business development and sales with a recent focus on domain names and internet identity products. Responsible for operations management of the gTLD product suite.
     

A-29



Experience

 

Vice President, Sales and Business Development NeuStar, Inc. (1999-Present)

 

 

Establish strong technical, operational, contractual, and billing relationships with all ICANN accredited Registrars to promote, sell and support.BIZ domain names. Work with strategic partners to enhance the functionality and utility of the.BIZ space.

 

 

Vice President, International Operations Melbourne IT. (1999-2001)

 

 

Manage Melbourne IT registrar operations in North America, Europe, Asia and Latin America. Plan and execute the functions of business development, sales, marketing and account management. Oversee all technical, operational, financial and marketing issues associated with major distribution channels. Grow revenues through these wholesale channels. Identify and introduce new product offerings to complement the existing, gTLD product suite. Ensure channel retention and sales growth by maintaining strong relationships with distribution channels. Identify and respond to market trends and emerging technologies that impact the product line.

 

 

Director of Business Development, Network Solutions (1998-1999)

 

 

Developed and executed a global marketing strategy for domain names and associated internet identity products. Performed competitive analysis, forecast demand, identified distribution channels, established alliances, programmed and managed a marketing budget, created promotional materials, mounted product presentations, prepared proposals and negotiated sales closings. Established distribution relationships with major hosting, design, access and portal companies. Substantially grew business with these companies and solidified business relationships through co-marketing programs and the establishment of high quality account management.

 

 

Manager, International Sales, Texas Instruments (1996-1998)

 

 

Managed the worldwide sales of wireless communications products (systems comprising TV, digital and thermal cameras, handheld computers, data compression and transmission software, radios and data link modems). Introduced the product line to government and commercial customers in the international market. Established long-term business relationships throughout Asia-Pacific, Europe and the Middle East. Trained and led a network of sales agents in 19 countries. Fostered key teaming relationships with manufacturers of complementary technology to sell joint applications. Identified and exploited synergies in distribution channels and promotional activities with these technology partners. Designed and produced audio-visual and interactive CD presentations. Trained foreign customers in proper operation and maintenance of systems they had purchased.

 

 

Contract Negotiator, Marine Spill Response Corp. (1994-1995)

 

 

Negotiated high cost/high complexity contracts with vendors in the US, Norway and the UK. The contracts were typically for system integration services, equipment test and evaluation, software/technology licensing, equipment purchase, and training services. Secured improvements in price, terms and conditions while retaining positive, long-term relationships with these business partners. Settled disputes over technical, contractual or financial matters. Redefined Statements of Work (SOW) and managed Change Order Processes.
     

A-30



 

 

Deputy Director: International Programs, Australian Defense Force, Systems Command, Melbourne, Australia (1990-1993)

 

 

Led a team of 36 persons responsible for cooperation programs with government agencies in Malaysia, Singapore, Japan, Israel, New Zealand, Italy, the UK, France, Canada and the USA. These programs involved logistics and engineering services, acquisition support services, training, technology sharing and equipment sales. Planned, organized and managed the performance of this team. Cultivated excellent relationships with counterparts in foreign countries, and used these personal relationships to maximum effect —accelerating agreements and innovating beneficial provisions. Developed an outstanding team spirit and productivity within the department, and mentored high performers into management positions.

 

 

Defense Attaché Staff, Embassy of Australia (1986-1990)

 

 

Responsible for financial, contractual and technical management of major equipment and technology acquisition programs. Liaised with multiple government departments in the US and in other countries.

Education

 

Honors Degree in Business Administration, University of Southern Queensland, Australia

 

 

Spanish Language Certification-in progress.

 

 

Ahita Vessali, Billing & Collections

Qualifications

 

Senior Professional with over 16 years of experience in increasingly responsible positions in the field of Accounting/Finance (eleven of those years being in the telecommunications industry). She has experience in several financial systems including G/L, A/P, A/R, Billing and Inventory with broad experience in banking operations, business acquisitions/mergers and systems integration. She exhibits outstanding organizational and management skills, as well as, extensive financial analysis expertise.

Experience

 

Director, Billing & Collections, NeuStar, Inc. (2000-Present)
    CXCVIII.Responsible for the accuracy and timeliness of all invoices, as well as, cash applications for all lines of businesses at NeuStar.

 

 

CXCIX.Responsible for cash management support, billing system implementation and revenue to A/R cycle reconciliation.

 

 

Controller, Program Control Operations, Spacenet, Inc. (1998-2000)
    CC.Directed accounting staff of 10 in Program Control Operations including billing and collections, capital lease accounting and program profitability analysis.

 

 

CCI.Provided support for cash management, risk management and budget functions.

 

 

CCII.Improved accuracy and timeliness of invoices, as a result of SAP invoicing and Order-To-Cash processes.

 

 

CCIII.Reconciled revenue to A/R cycle and coordinated internal and external audits.

 

 

Manager, Financial Analysis & Contract Revenue, GE Capital Spacenet Services, Inc. (1994-1998)
    CCIV.Managed a group of six billing and collections accountants.
     

A-31



 

 

CCV.Ensured accuracy of monthly customer invoices and provided high quality customer service for key accounts including MCI/USPS, Hollywood Video, Shell Oil, Rite Aid, JC Penney, and Kmart.

 

 

CCVI.Monitored A/R effectively and pursued aggressive collections on aged receivables.

 

 

CCVII.Automated and streamlined billing processes (annual labor savings-2000 hours).

 

 

CCVIII.Coordinated systems integration of the new subsidiaries that included 24% international and domestic travel (completed Germany's systems integration in April 1997 and achieved a Recognition of Excellence award).

 

 

Senior Cost Accountant, GTE Spacenet Corporation (1989-1994)
    CCIX.Performed profitability analysis for both domestic and international contracts.

 

 

CCX.Evaluated risk of carrying inventory to forecast and developed a new cost-of-goods sold recognition process by enhancing our inventory system to provide accurate equipment cost (cost accuracy-100%).

 

 

CCXI.Approved domestic A/P invoices and improved A/P processes to alleviate possible duplication of payments to vendors (1996 savings-$200 thousand).

 

 

CCXII.Audited and reconciled various physical inventories including our Manassas warehouse, which consisted of equipment in excess of $30 million and ensured existence of tight inventory controls.

 

 

CCXIII.Coordinated the development of a new enhanced fixed asset system (annual labor savings-500 hours).

 

 

Branch Manager/Assistant Vice President, Trustbank Savings & Loan Association (1983-1989)
    CCXIV.Increased growth of accounts and deposits by 15% on an annual basis by cross-selling new accounts and developing clientele through telemarketing, mail contacts and Chamber of Commerce.

 

 

CCXV.Supervised the operations of a full service branch and ensured compliance with regulatory policies.

 

 

CCXVI.Recruited, motivated, trained and supervised staff of 20 employees.

Education

 

Certified Public Accountant, 1997

 

 

MBA, Finance, George Mason University

 

 

BBA, Accounting, Marymount University
     

A-32



 

 

Peggy Wenneman, Information Technology and Services

Qualifications

 

More that 18 years of management experience in information technology for the Internet, IT and telecommunications industries. Her expertise includes managing global operations for a multi-nations telecommunications company; supporting multiple call centers; managing and supporting large data centers; and customer and data center migrations. Accomplishments include managing and staffing network and infrastructure development and support organizations; meeting and exceeding Service Level Requirements (SLRs) for availability in order provisioning environments; and working with IXCs and LECs to automate electronic information exchange to support service provisioning.

Experience

 

Director, Information Technology and Services, NeuStar, Inc. (2001-Present)
    CCXVII.Manages the technical operations group and the network support group in a 7x24 real-time mission critical production environment.

 

 

CCXVIII.Responsible for supporting, monitoring, testing and troubleshooting hardware and software problems.

 

 

CCXIX.Manages all Tier 2 support for all LAN/WAN based applications.

 

 

CCXX.Participates in database architecture strategy development, database design and engineering, and reliability and performance enhancements.

 

 

Vice President, Global Standards, Cable & Wireless Global (2000-2001)
    CCXXI.Created a multi-cultural organization to establish standards across 15 business units spanning the United States, Europe, and Japan.

 

 

CCXXII.Directed organization to define, communicate, integrate and enforce standards globally.

 

 

CCXXIII.Participated on Executive eGO Board (e Buisness initiatives) and Global Information Management Steering Board.

 

 

CCXXIV.Saved over $2M in operating costs within first five months

 

 

CCXXV.Developed fast-path (1-4 week) business process to select standard technology utilizing key stakeholder participation, and supporting 90-day product launch life cycle.

 

 

CCXXVI.Implemented Web-based knowledge management system reducing e-mail congestion and dependency on subject-matter experts.

 

 

CCXXVII.Improved knowledge transfer and project startup efficiency.

 

 

CCXXVIII.Initiated development of enterprise interface architecture enabling faster product launch.

 

 

Senior Director, Internet IT (1998-2000)
    CCXXIX.Directed all activities to support C&W Internet network and IT systems, including migration of Internet network and customer base to C&W purchased from MCI, customization and support of Internet Operational Support Systems, support of multiple customer call centers, and transition of Internet customer base upon sale to Prodigy.

 

 

CCXXX.Enabled C&W to launch first Internet business by migrating consumer base of 350,000+ dial customers within a four-month window.

 

 

CCXXXI.Migrated live network with no customer down time.
     

A-33



 

 

CCXXXII.Implemented Customer Care, Order Entry, Security, Provisioning, and Financial systems within four months for Internet dial business.

 

 

CCXXXIII.Reduced operating cost structure from $350,000 per month to $90,000 within six months.

 

 

Senior Director, IT Systems (1996-1998)
    CCXXXIV.Directed all IT development and maintenance activities for Sales, Marketing, Commissions, and Network Provisioning systems with a staff of up to 100 employees.

 

 

CCXXXV.Implemented flow-through Circuit Order through Circuit Completion system and established automation agreements with 28 LECs, to fully automate electronic information exchange.

 

 

CCXXXVI.Improved Service Delivery intervals by 10 to 12 days by identifying and implementing performance enhancements to the Switched Network Provisioning system.

 

 

CCXXXVII.Provided 99.95% system availability of Circuit Order Provisioning, up from less than 80%, in six months during a 400% circuit transaction increase.

 

 

CCXXXVIII.Provided C&W with positive ROI within three months through consolidation of five legacy systems into a single Network Trouble Management system.

 

 

CCXXXIX.Developed a Consolidated Commissions System that enabled flexible changes to compensation plans and delivered company's first on time compensation program.

 

 

Senior Manager, IT, MCI (1983-1996)
    CCXL.Managed all life-cycle system development and implementation activities and utilized "bleeding-edge" technologies.

 

 

CCXLI.Managed development and delivery of client-server rate quotation system.

 

 

CCXLII.Enabled product launch (1-800-COLLECT) within eight-week period.

 

 

CCXLIII.Implemented first production DB2 application within Baltimore/Washington region in 1987; supported traffic alarming system that ran 24x7; and received 1987 Achievement & Commitment to Excellence (ACE) Award.

 

 

CCXLIV.Managed software migration of all mainframe software across four data centers, supporting over 200 application groups; received Flexible Flier Award (Manager of Year) 1986.

 

 

CCXLV.Managed the migration of two data centers over a weekend, including all operational systems and data; closed one data center; and realized significant reduction in operating costs.

 

 

CCXLVI.Implemented various technical improvements to Accounts Receivable System which reduced batch processing from 48 hours to 8 hours, while increasing volume of throughput by 250%.

Education

 

MBA, George Mason University

 

 

International Economy, Technology & Industry studies, Oxford University

 

 

Beta Gamma Sigma National Honor Society

 

 

Board Member and Secretary of George Mason Alumni, 1997-1998

A-34


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

        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

        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:

        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:

        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

        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 AdministrationNeuStar 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. NeuStar will provide usTLD services with the best value and highest degree of quality and responsiveness. Graphic Omitted: highlight of various categories of usTLD services.]

        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 SiteNeuStar 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 ReportingAs 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:

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: Redundant network connectivity, high availability clusters, redundant, and replication to a second data center provide 99.9% availability and scalability. Graphic Omitted: diagram of Enhanced SRS Data Center architecture.]

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: Redundant network components and high availability nameserver cluster provide scalable high availability. Graphic Omitted: diagram of Nameserver Data Center architecture.]

        The following function table lists the nameserver 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:

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

B.2-5



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 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:

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:

B.2-6


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).

        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:

B.2-7


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:

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.

B.2-8



        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 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.

B.2-9



        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:

        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:

        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:

B.2-10


        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.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:

        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:

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-11



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.

        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.

B.2-12



        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. 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: NeuStar's process for near real-time updating of the nameserver zone file databases ensures that consistent and timely data are always available. Graphic Omitted: flow diagram depicting zone file distribution flow.]

        [Exhibit B.2-5: Maintaining a zone file database at each nameserver data center allows zone file servers to respond to DNS inquiries by accessing their own local zone file database. This maximizes efficiency and increases redundancy. Graphic Omitted: diagram depicting nameserver update process.]

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.

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:

        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:

        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."

B.2-18


        NeuStar is confident that this phased approach will succeed for the following reasons:

        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:

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:

        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:

        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
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
 
  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:

Methodology

B.2-24


Research Participants

Target Audience

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

Consumer Research Findings

B.2-25


Business Research Findings

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

 
  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


 
  Percentage
  Pop. Projection
Business   4 % 1.6 M
Consumer   23 % 31.5 M
Total     33.1 M
 
  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:

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:

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:

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: There are numerous markets and positioning options for the usTLD as demonstrated in this illustrative sample of logos. Graphic Omitted: sample usTLD logos.]

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:

 
   
   
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


 
   
   
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.

        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:

        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:

        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:

B.2-33



        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

Domain Name Registration Purchasing Habits   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.

 

 

However, latent interest in purchasing a domain name exists, with more than one-quarter 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.

 

 

Online consumers who access the Web from school are the population subgroup most likely to say they don't currently own a domain name but they plan to purchase one in the next year.

 

 

Not surprisingly, current domain name owners tend to be early adopters, while those planning future purchases self identify as less savvy in their use of the Internet.

 

 

Consumers say they primarily want a domain name to start/maintain home-based businesses and/or for a hobby.

 

 

A clear majority of consumer domain name owners say their personal Web site is very important to them.

Awareness and Purchasing Likelihood of usTLDs

 

In an unaided test, very few consumers were able to recall that dot-us exists. In fact, general awareness of country code TLDs is low.

 

 

In an aided test, approximately three-quarters report that they know that dot-us exists. This aided figure is very close to TLDs other than dot-com and dot-net (such as dot-biz 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.
       

B.2-34



 

 

Our initial estimates are that approximately one-quarter of online consumers state an initial interest in purchasing a usTLD. This is an elastic figure, however, as many more are willing to consider a usTLD if a dot-com option is taken and/or dot-us can compete with dot-com on price.

Size and Demographics of Likely Purchasers

 

Slightly less than one-quarter of online consumers state any interest in one day purchasing a domain name with a dot-us extension, and 5% say they are "very likely" to one day purchase a domain name with a dot-us extension. In round numbers, this 5% roughly equates to 6.2 million Americans.

 

 

The target market is made up of a disproportionate number of people in upper socioeconomic groups.

 

 

Target purchasers have been online for over 5 years, read technology-oriented magazines, and self-identify as "Internet experts."

 

 

A disproportionate number of target users currently own a domain name.

 

 

The self-employed and those who are in technical fields also make strong targets.

 

 

Finally, online consumers who have a family member with a domain name are strongly interested in purchasing a domain name.

Attitudes About Existing TLD Options

 

Slightly more than three-quarters of consumers want to use the same domain name extension that they have used in the past when they make their next purchase. Given that the overwhelming majority used dot-com in the past, we can assume that this is the preferred choice going forward.

 

 

dot-com remains the most universal TLD—many other TLDs have specifically assigned categories in the minds of consumers.

 

 

However, domain name extensions appear to be less important to consumers than choosing a descriptive name for a Web site (e.g., 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.

Assess branding and product benefits for the usTLD

 

A key differentiator for dot-us (like most non-dot-com suffixes) is that consumers can receive the name that they want.

 

 

Other branding efforts should focus on the patriotic aspects of the usTLD. This focus particularly resonates with older online consumers.

 

 

Consumers assume that a dot-us Web site would be more trustworthy than a dot-web or dot-biz. site.
       

B.2-35



 

 

Finally, while many feel that a usTLD is easy to remember, there is some concern that a person using a dot-us extension would be difficult to locate on a search engine.

Receptivity for locality and hierarchical based structures

 

About 4 in 10 consumers are generally receptive to locality-based name structures.

 

 

However, when we ask consumers if they would personally prefer a long locality-based name (such as yourname.dallas.tx.us) or a shorter structure (yourname.us), the overwhelming preference is for the shorter name.

 

 

Consumers overwhelmingly believe that public service second-level domains (i.e., parks.us) are a good idea.

Preferred strings for different types of Web sites

 

dot-com tested most favorably among all the options presented.

 

 

dot-us tested very favorably versus the options presented, particularly when the sought-after name in dot-com was unavailable.

 

 

dot-us is seen as most relevant for government, education, political, and military Web sites. Users were also receptive toward personal, business, family, and community Web sites with usTLDs.

 

 

dot-net is seen as primarily for networks and alliances. Other potential uses are for any corporate Web site and, to a lesser extent, for personal Web sites.

 

 

dot-name is seen as relevant only for personal or family Web sites.

 

 

dot-biz is seen as strictly a corporate Web site TLD.

 

 

Consumers believe dot-org has multiple applications outside personal use.

 

 

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

Price elasticity and channel strategies

 

dot-us needs to be priced competitively in the marketplace. While most expect dot-com and dot-us to be priced equally, a plurality of consumers expects dot-us to be cheaper than dot-com.

 

 

For likely domain name purchasers, dot-us purchase intent remains low until the $15 per year price point; at $15 per year, 64% say they would be "very likely" to purchase a usTLD.

 

 

Not surprisingly, online is the preferred channel for TLDs. Among other avenues tested, about 1 in 10 are very interested in a tele-channel and 1 in 7 are very interested in purchasing domain names at retail outlets.

Barriers to TLD Purchases

 

Three in five online consumers do not know how to purchase a domain name.
       

B.2-36



 

 

Two-thirds of online consumers believe that they do not need their own domain name right now.

 

 

Approximately 1 in 4 survey respondents believe that owning a Web site is too expensive and 1 in 5 believe the creation and maintenance of a Web site is too difficult.

Summary of Results and Conclusions—Businesses

Domain Name Registration Purchasing Habits   Domain name penetration (in percentage terms) is relatively high in the business Internet population, with 55% currently owning a domain name.

 

 

However, 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.

 

 

Small businesses are more likely than large businesses to say they plan to purchase a domain name in the next year.

 

 

A majority of online businesses say their Web site is important to them.

 

 

Approximately 2 in 5 businesses say customers purchase goods or services through their current Web site.

Awareness and Purchasing Likelihood of usTLDs

 

In an unaided test, very few businesses were able to recall that dot-us exists. In fact, general awareness of ccTLDs is low.

 

 

One in twenty business survey respondents work for a company that currently has a country code associated with its domain name. Virtually all of these businesses have more than 1,000 employees.

 

 

In an aided test, approximately 7 in 10 report that they know that dot-us exists. This aided figure is very close to TLDs other than dot-com and dot-net (such as 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 businesses state some interest in eventually purchasing a usTLD. 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.

Size and Demographics of Likely Purchasers

 

Slightly more than one-fifth of online businesses state an interest in one day purchasing a domain name with a dot-us extension. This means that approximately 1.5 million businesses are potential purchasers of the usTLD.
       

B.2-37



 

 

While small and large businesses demonstrate strong interest in purchasing domain names going forward, midsize businesses appear less interested.

 

 

SOHO is an excellent target.

 

 

Target business purchasers have been online for over 5 years, and self-identify as "Internet experts."

 

 

Most business purchasers currently own a domain name.

 

 

Very few target business purchasers are over the age of 55.

 

 

Businesses that do not currently own a domain name or know how to purchase a domain name, and whose employees do not use the Internet on a daily basis are disinclined to purchase a domain name.

Attitudes about existing TLD options

 

Slightly more than 3 in 5 businesses want to use the same domain name extension that they have used in the past when they make their next purchase. Given that the overwhelming majority used dot-com in the past, we can assume that this is the preferred choice going forward.

 

 

dot-com remains the most universal TLD—many other TLDs have specifically assigned categories in the minds of businesses.

 

 

However, domain name extensions appear to be slightly less important to businesses than choosing a descriptive name for a Web site. For example, by a six-point margin, businesses would rather select a first choice name with a dot-us extension than a less desirable name with a dot-com extension.

 

 

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.

Assess branding and product benefits for the usTLD

 

A key differentiator for dot-us (like most non-dot-com suffixes) is that businesses can receive the name that they want.

 

 

Seven in ten businesses believe the dot-us extension means that the company is based in the United States.

 

 

While many businesses feel that a usTLD is easy to remember, there is some concern that a company using a dot-us extension could be difficult to locate on a search engine.

 

 

About one-third of businesses feel that dot-us connotes that a Web site is secure and trustworthy.

 

 

Businesses say that just because a Web site has a dot-us extension, this does not necessarily mean that it is new.

 

 

Among the businesses interested in purchasing a usTLD, one-third cited the prevention of cybersquatting and one-third believes that usTLD adds value; the remainder were unsure.

Receptivity for locality and hierarchical based structures

 

About 4 in 10 online businesses are generally receptive to locality-based name structures.
       

B.2-38



 

 

However, when we ask businesses if they would personally prefer a long locality-based name (such as your.company.dallas.tx.us) or a shorter structure (your.company.us), the overwhelming preference is for the shorter name.

Preferred strings for different types of Web sites

 

dot-com tested most favorably among all the options presented.

 

 

dot-us tested very favorably versus the options presented, particularly when the sought-after name in dot-com was unavailable.

 

 

dot-us is seen as most relevant for government, education, political, and military Web sites. Businesses were also receptive toward personal, business, family, and community Web sites with usTLDs.

 

 

dot-net is seen as primarily for networks and alliances. Other potential uses are for any corporate Web site and, to a lesser extent, for personal Web sites.

 

 

dot-biz is seen as strictly a corporate Web site TLD.

 

 

Businesses believe dot-org has multiple applications outside personal use.

 

 

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

Price elasticity and channel strategies

 

dot-us needs to be priced competitively in the marketplace. While most expect dot-com and dot-us to be priced equally, a plurality of businesses expect dot-us to be cheaper than dot-com.

 

 

For likely domain name purchasers, dot-us purchase intent remains low until the $15 per year price point; at $15 per year, 63% of business say they would be very likely to purchase a usTLD.

 

 

Businesses prefer purchasing domain names in longer intervals (well over 50% would like the intervals to be three years or more) without having to renew.

 

 

Not surprisingly, online is the preferred channel for TLDs. Among other avenues tested, 15% are very interested in a tele-channel and 1 in 10 are very interested in purchasing domain names at retail outlets.

Barriers to TLD Purchases

 

Slightly less than 1 in 5 businesses say that they do not know how to purchase a domain name and that this has been a very important barrier that has stopped them from creating a Web site.

 

 

One-third of businesses believe that they do not need their own domain name right now.

 

 

About 1 in 4 business respondents believe purchasing a domain name is too expensive and 13% believe the creation and maintenance of a Web site is too difficult.

B.2-39


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.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.

B.2-40



        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:

        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.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:

B.2-41


        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:

        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

B.2-42



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:

        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:

        All M&P documentation will also include contact information for escalation of issues.

B.2-43


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:

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-44



        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:

        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:

        These reports will be developed on an ongoing basis in consultation with registrars and the DOC.

B.2-45



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:


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:

B.2-46


        The IP Customer Service Center's phone system will use an Interactive Voice Response (IVR) system and