AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
1. Contract ID Code
Pageof Pages
 
1
4
 
2.Amendment/Modification No.
3.Effective Date
6/14/2002
4.Requisition/Purchase Req. No.
5.Project No. (if applicable)
 
0002
 
6.Issued By
Code 000SB
7.Administered By(If other than Item 6) 
Code 
 
NATIONAL INST OF STDS AND TECHNOLOGY
SEE BLOCK 6
 
100 BUREAU DRIVESTOP 3571
 
BUILDING 301 ROOM B129
 
GAITHERSBURG MD20899-3571
 
WIDDUP, JOSEPH301-975-6324
 
8.Name and Address of Contractor(No., Street, County, and Zip Code)
(X)
9A.Amendment of Solicitation No.
 
 
NEUSTAR
Vendor ID: 00007158
9B.Date (See Item 11)
 
1120 VERMONT AVENUE NW
DUNS: 112403295
 
SUITE 400
10A.Modification of Contract/Order No.
 
WASHINGTON DC 20005
CAGE:
X
SB1335-02-W-0175
 
10B.Date (See Item 13)
 
Oct 26, 2001
 
Code
Facility Code
 
11.THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
 
The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers
isextended
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 items 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 ACKNOWLEDG-
 
MENT 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)
 
610100010204000090919000009000090900000000000000US0.00
 
13.THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED 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 changes(such as changes in paying office, appropriation date, etc.)
Set fourth item 14, pursuant to the authority of FAR 43.103 (b)
 
X
C.This supplemental agreement is entered into pursuant to authority of:
 
FAR Subpart 43.103(a)
 
D.Other (Specify type of modification and authority)
 
 
E.IMPORTANT:Contractor
is not,
X
is required to sign this document and return 1 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
Robert Poulin
Senior Vice President
16.a Name and Title of Contracting Officer
WIDDUP, Joseph    301-975-6324
CONTRACTING OFFICER  jwiddup@nist.gov
15B. Contractor/Offeror
/s/Robert Poulin
16B. Signature of Contracting Officer
/s/ Joseph Widdup
06-14-2002 06-14-2002


 I. 

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.

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 domain burke.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:[2]

.us

<state>.us

<locality> .<state>.us

lib.<state>.us

k12. <state>.us

pvt. k12. <state>.us

cc. <state>.us

tec. <state>.us

isa.us

nsn.us

dni.us

This approach will allow NeuStar to maintain control of the listed zone while permitting additional records to be registered at higher delegation levels.For example, an entity would not be permitted to be the delegated manager of somelocality.<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.

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

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

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

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

 V. Future Policies and Processes

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



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