ARIN Issues RFP for IN-ADDR Services

[Member Services]

July 7, 2000

ARIN is seeking Professional Services Support in the area of Internet
Domain Name System (DNS) Inverse Address Resolution (IN-ADDR). One of
ARIN's responsibilities is to maintain IN-ADDR.ARPA, a domain whereby IP
numbers are translated to domain names. ARIN is increasing its level of
IN-ADDR responsibilities and is issuing the Request for Proposal (RFP)*
presented below to accomplish that goal. The RFP is to be used as a guide
in formatting your response, and its schedule must be strictly adhered to.
All responses meeting the stated criteria therein will be considered. ARIN
invites all interested parties to submit a proposal, and looks forward to
your suggested technical solutions. As mentioned in the RFP, questions 
and comments should be submitted to rfp at arin.net.

*Publication of this RFP does not constitute a promise or an obligation on
ARIN's part to enter into a contractual arrangement with any vendor,
however, it is our intent to enter into a Service Level Agreement (SLA)
with one or more qualified vendor(s).	

The RFP can be found on the ARIN website at the following url:

http://www.arin.net/announcements/rfp.html

Regards,

Susan Hamlin
ARIN Member Services

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
American Registry For Internet Numbers (ARIN)
Professional Services Host Site
Request for Proposal (RFP)


I. Introduction
ARIN maintains the authoritative IN-ADDR.ARPA zone files for networks
within its region.  It is ARIN's responsibility to ensure that Domain Name
System (DNS) services reflect the correct zone file information. The
primary function of the DNS is to map a domain name to its corresponding
IP address; however, DNS also provides a variety of other services to
include the ability to perform reverse operations.  This reverse operation
maps the IP address to the domain name and is called IN-ADDR.  This
operation is currently being performed by the "Root Servers."   

The purpose of this Request for Proposal (RFP) is to identify world-class
Vendors that can provide IN-ADDR service for network delegations in ARIN's
region. The successful Vendor will take over the responsibility of the
second level address-to-name "PTR" queries.  First level queries will be
performed by the "Root Servers". 

This RFP is requesting responses for a full service offering that will
meet the high-level requirements as described herein.  ARIN will also
entertain responses for co-hosting facilities in the event no single
Vendor is identified that can provide the full service.

II. Schedule
A proposed Schedule for the RFP is provided below.  Please refer to this
schedule for the required timeframes for submitting questions and for
responding to this RFP.


RFP Schedule

Item	Description						Due Date
1	RFP Posted and Announced				07/07/00
2	Questions Submitted (no later than)			07/28/00
3	Answers Provided					08/09/00
4	Proposals Due						08/28/00
5	Top Candidates Selected and Contacted			09/08/00
6	Site Surveys Conducted (week of 9/11 - 9/15)		09/15/00
7	Final Candidate Selected				09/18/00
8	Finalize Service Level Agreement (SLA) and Contract 	10/16/00
9	Phase One Fully Operational				11/13/00


III. Full Service Requirements
The IN-ADDR DNS service shall provide responses to DNS "PTR" queries.
ARIN will provide the IN-ADDR.ARPA zone files and the Vendor shall provide
all functionality for performing the IN-ADDR service.  The Vendor shall
provide an interface to ARIN for access to this file.  The following
sections describe the requirements for providing high-level IN-ADDR
service.

A. Server Software and Network Connectivity 
The Vendor shall provide adequate means to accommodate zone files;
transfer data from ARIN in Chantilly, VA, to the servers; and accommodate
anticipated traffic based on the following:

1. Server Software. Server software shall correctly implement the
following:
a. IETF standards for DNS currently in [RFC1035] and [RFC2181]
b. Dynamic updates [RFC2136] 
c. Transaction signatures [RFC2845]  
d. Key management

2. Zone Transfer. The network infrastructure shall support an average
download transfer time of zone files of approximately 10 minutes
(assumption: zone file of 30MB in size).  The zone file will be available
approximately every 2 hours.  

3. Load. The network infrastructure shall support a sustained average load
of 2500 queries per second and a peak load of 5,000 queries per second
with a maximum expected packet size of 512 bytes. 

B. Network Availability
The Vendor shall provide a minimum network availability of 99.7% uptime as
reported on a 24 x 7 basis, averaged over 30 days, inclusive of scheduled
outages and maintenance windows.

IV. Vendor Response to RFP
The Vendor shall respond to this RFP in accordance with the schedule
provided in Section II of this RFP.  Responses will be accepted in the
form of e-mail or hard copy.  Questions and responses to this RFP should
be submitted to rfp at arin.net.  Hard copies should be mailed to ARIN at
4506 Daly Dr., Suite 200, Chantilly, VA  20151, Attention:  IN-ADDR RFP
Submittal.

Vendors will be evaluated on their technical approach, cost, and
demonstrated ability to meet the specified schedule.  Vendors offering a
proprietary solution shall provide a mechanism for ARIN to access the
information for validation and verification.  

Vendors shall provide responses in the following format:  

A.  Server Platform
1. Server Hardware.  Describe the server hardware solution to include
platform type, RAM, hard drive size, network I/O, operating system
version, and backup architecture to meet IN-ADDR server requirements
specified in Section III.

2. Server Software.  Describe software implementation of IETF standards
for DNS currently in [RFC1035] and [RFC2181]; [RFC2136] to accommodate
dynamic updates; [RFC2845] for transaction signatures; and key management.

B.  Network (WAN/LAN)
1. Network Connectivity.  Describe current WAN/LAN bandwidth capabilities
and ability to accommodate sustained and peak loads specified in
Section III.   Specify upgrade/growth capacity. 

2. Network Availability.  Describe current network architecture in place
to meet network availability and peering relationships that will be used
to meet requirements. Describe network redundancy, diverse routing, dual
physical connections, multiple ISPs, etc. 

3. Network Management Capabilities.  Provide information on current
enterprise management tools; capacity and performance management and
planning; network monitoring; utilization and trend analysis; fault
management; configuration and change management; and security.

4. Misc.  Describe existing modem and voice lines for trouble-shooting and
remote maintenance for ARIN personnel.

C.  Facility Description
1. Site.  Describe geographic and site location(s); room where equipment
will be installed; environmental conditions to include heating,
ventilation, and air conditioning (HVAC); lighting; and static-free
conditions. 

2. Power and Grounding.  Describe power and grounding specifications, and
backup power accommodations to meet availability requirements.

3. Natural and Man-Made Disaster Impact and Fire Suppression.  Describe
how facility is configured to minimize impacts due to natural and man-made
disasters and describe how equipment will be protected from fire.

4. Physical Security.  Describe the physical security of the facility to
include times when on-site security is in attendance; restricted and
access controlled areas; access policies; and record of access.

D.  Personnel and Support
1. Skill Set.  Describe skill sets for each of the administrative
personnel that will be supporting the ARIN equipment to include operating
system, hardware, software, and network familiarity. 

2. On-site Support Activities.  Describe level of support provided by
on-site personnel to include staff coverage, trouble-shooting, toggling
switches, reporting displays, and access to equipment vendor maintenance
personnel.

3. Trouble Reporting.  Describe trouble reporting for server, network or
circuit fault detection to include internal trouble ticket assignment
process; timeframes, levels and criteria for escalation procedures; ARIN
notification method to include automated notifications (i.e. pager,
e-mail, telephone call); and operations support criteria and priority
levels for outages.

E. Billing
1. Billing Cycle.  Describe information pertaining to and a description of
charges for the billing cycle and frequency.  The details in the bill
shall include the regular monthly charges for the Vendor's services.

2. Terms and Conditions for Payment.  Describe the process for ARIN to
receive a monthly bill due and payable based on terms of net 30.  The bill
should include a "remit to" address along with a payment coupon to ensure
proper crediting of payments.  ARIN requires a 30-day notice from vendors
of any changes in the billing terms or amounts.

F. Schedule
Describe how the Vendor will be positioned to meet operational
requirements, specifically items 8 and 9 of the schedule provided in
Section II.

V. Cost 
The Vendor shall provide all Non-Recurring Charges (NRC) and Monthly
Recurring Charges (MRC) for a full service solution.  Please provide a
list with the cost for each item broken out separately.

VI. References
The Vendor shall provide three references.  The following information is
required for each reference provided:

	Corporate Name
	Individual point of contact (POC)
	Email address of the designated POC
	Phone number of the designated POC