DDI_Address_Management_-_RFQ.docx

UNITED STATES CENSUS BUREAU

DNS, DHCP, IP ADDRESS MANAGEMENT SERVER PRODUCTS AND MAINTENANCE

· This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-78.

SOLICITATION / REQUEST FOR QUOTE #

DATE

RESPONSE DEADLINE

DELIVERY BY

· CONTRACT LINE ITEMS AND PRICING SCHEDULE

The price of the contract is [to be determined before award]. The prices set forth below shall apply for payment purposes for all items acquired under this contract. The Contractor may not charge the Government for any items acquired under this contract at any prices other than those specified below.

The Government intends to award CLINS identified as HARDWARE (0001, 0002) and SUPPORT (0003) at time of award and may exercise additional CLINS throughout the period of performance identified in 3.0 of this contract.

2.1 PRICING SCHEDULE – FIXED-PRICE PER UNIT

The Government retains the right to exercise optional purchases of each product or maintenance identified in this section during the period of performance of this contract. All optional items shall be purchased on a Fixed Price per unit basis through an issuance of a subsequent modification by the Contracting Officer.

SUPPORT – ONSITE HARDWARE SERVER, SOFTWARE INSTALLATION, DATA CONVERSION

12 Months

EA

· DESCRIPTION OF REQUIREMENTS

PRODUCT #1:

Large DNS/DHCP/IPAM SERVER APPLIANCE

PRODUCT #2:

Medium DNS/DHCP/IPAM SERVER APPLIANCE

PRODUCT #3:

Small DNS/DHCP/IPAM SERVER APPLIANCE

PRODUCT #4:

DNS/DHCP/IPAM SERVER APPLIANCE ON SITE SUPPORT 12 Months

PRODUCT #5:

DNS/DHCP/IPAM SERVER APPLIANCE AND SUPPORT DEVICES 24/7/365

Required Features:

The U.S. Census Bureau, TCO (Telecommunications Office) seeks to determine if any DDI (DNS, DHCP, IP Address Management) vendors are capable of providing a DDI solution in support of the infrastructure services in the Bureau of the Census with the following functionalities:

Past Performance:

Past performance should be demonstrated and will be evaluated during the selection process.

Platform:

PHYSICAL:

Physical 1. Product shall be in appliance form, i.e. rack-mountable Physical 2. Product shall have/support redundant power supply Physical 3: Cloud component must be in virtual server form.

GENERAL OPERATING SYSTEM:

(OS, GUI, account management, configuration management, fault tolerance, backups) OS 1. Operating system shall be locked-down and not allow other compiled executable software to be installed (will not allow the installation of *.EXE or BIN files)

a. Not a general-purpose operating system that allows the installation of software OS 2. Operating system shall have an available graphical user interface OS 3. Operating system shall have an available command line interface OS 4. Product shall support customizable/configurable administrative/user roles/rights OS 5. Product shall support role-based management

a. Roles apply per server

b. Roles apply per view

c. Roles apply per zone

d. Different roles such admin, update, read-only OS 6. Product shall support remote access via https OS 7. Product shall support remote access via SSHv2 OS 8. During login, the product authentication screen shall not display the password characters in cleartext. Dots or asterisks are preferred.

OS 9. Product shall support redundancy and fault-tolerant configuration.

a. Assuming that more than one appliance will be in place OS 10. Product shall support data redundancy of its databases

a. Product shall support bulk import of database data

b. Product shall support bulk export of database data

OS 11. Product shall provide robust reporting and viewing capability

vi. Auto-discovery

vii. Network Topology OS 12. Product shall keep track of changes made to its configuration (continuous monitoring)

a. Shall track changes made to DNS settings (who made what change at what time)

b. Shall track changes made to DHCP settings

c. Product shall provide reporting of changes made

d. Sending out an e-mail alert is one acceptable method

e. Change log shall be viewable and exportable upon demand

f. Product should have revision control (SVN, git, etc.)

OS 13. Product shall be able to rollback its configuration upon (authorized) command

a. Shall support rollback of DNS settings

b. Shall support rollback of DHCP settings

c. Product shall be able to report a DIFF between any two snapshots OS 14. Product shall support integration with an external directory via LDAP to standard LDAPv3 directories

a. LDAPv3

b. Including Active Directory OS 15. Product shall support update, data retrieval, and manipulation via API OS 16. API should preferably be WSDL: (web services definition language) OS 17. Product shall be compatible with HP (Hewlett-Packard) software “Operations Orchestration” OS 18. Product shall be compatible with HP software “UCMDB” (Universal configuration management database from HP)

a. Product shall allow Operations Orchestration and UCMDB to request, obtain, and apply new IP addresses automatically to new virtual machines (VMs).

b. Product shall be able to map information (DNS names, IP addresses) within HP UCMDB

c. HP UCMDB shall be able to obtain real-time information via the API:

SECURITY FEATURES AND FUNCTIONS:

(encryption, auditing, etc.)

Security 1. Has your product been validated to meet

a. FIPS 140-2 ?

b. FIPS 140-3 ?

Security 2. Product shall support SSL or TLS or similar

a. Product shall support the installation of certificates to enable encryption

b. Product supports custom or 3rd-party certification authority for all SSL Security 3. Product shall support audit logging, both local and remote

a. Log format shall be either audit.D or syslog

b. Audit logs shall be able to be exported with some frequency (e.g. daily)

i. Either Push or Pull mechanism is acceptable

c. Audit log export should be encrypted

d. Product shall perform query logging

e. Product shall support archive of all logs

IP ADDRESS MANAGEMENT:

IPAM 1. Product shall provide IP address reports based on several different selectable criteria (rows, headers)

a. By subnet, by host, by address range, etc.

b. By static, by dynamic, etc.

c. Product shall detect and report IP address conflicts IPAM 2. Product shall be able to discover hosts on the network IPAM 3. Product shall provide graphical representation on demand IPAM 4. Product shall support IPv6 address management IPAM 5. Automatic IP address allocation shall support Virtual desktop automatic provisioning

DNS:

DNS1. Product shall provide DNS services for 15,000 hosts (fifteen thousand) minimum DNS2. Product shall support zone signing DNS3. Product shall support secure zone transfers (such as via encryption) DNS4. Product shall authenticate zone transfers before transfer DNS5. Product shall support dynamically allocated zones DNS6. Product shall support zone delegation DNS7. Product shall support zone transfers for different views to the same IP addresses on different ports DNS8. Automatic IP address allocation shall support Virtual Machine automatic provisioning: the ability to specify the name for a host to be used without a manual process DNS 9. Product shall support a manual process to register DNS names.

DNS 10. Product shall be able to register the host name and IP address in DNS without a manual process (when desired); ie. shall be able to register and obtain DNS name automatically. In particular, the automatic process shall be compatible with Operations Orchestration.

DNS12. Product shall either support or provide all the security features of BIND Version 9.6 and higher DNS 13. Product shall support (be compatible with) BIND 9.7 and higher versions DNS14. Product shall support BIND 9 “views” feature DNS 15. Product shall provide DNS dependency mapping.

DNS16. Product shall be compatible with Linux and Windows servers DNS17. Product shall be able to provide DNS services to Windows Active Directory servers DNS18. Product shall be able to write from Active Directory hosts DNS19. Product shall be able to perform dynamic DNS updates DNS20. Product shall support multi-master dynamic DNS DNS21. Product shall support DNS updates and config changes via command line DNS22. Product shall support update, data retrieval, and manipulation via API DNS23. Product shall support annotation and adding text comments to entries DNS 24. Product shall support DNSSEC

a. Product shall support automatic DNSSEC signing for all zones

b. Product should have automatic ZSK and KSK rollover

c. Product should have HSM storage of DNSSEC keys DNS 25. Product shall support IPv6: DNS IPv6, DHCPv6, IPv6 address management

a. Product shall support DNS6to4 translation

b. Product shall support IPv6 and IPv4 dual-stacking DNS26. Would your product be compatible with an automated IP-address request from the REMEDY™ ticketing process? Would this be available through API, or other means?

DHCP:

DHCP 1. Product shall provide DHCP service for 15,000 hosts DHCP 2. Product shall provide features of ISC DHCP 3.x and better

a. Custom DHCP configurations

b. Option types DHCP 3. Product shall support dynamic DHCP (dynamic allocation) DHCP 4. Product shall support multi-master DHCP DHCP 5. Dynamic DHCP shall support 0.99 second response time

a. To go through the broadcast, request, allocation cycle DHCP 6. Product shall support static reservations (static allocation) DHCP 7. Product shall support automatic allocation: the ability to build a host without requesting an IP address through a manual process DHCP 8. Product shall support automated software calls via APIs to perform IP address requests, name requests, etc.

DHCP 9. Product shall have the ability to share information on DHCP IP lease ranges via the API DHCP 10. Product shall provide DHCP dependency mapping.

GENERAL SUPPORT:

Support 1.Product shall support NTP, either by connecting to NTP service as a client or by acting as an NTP server

a. If acting as an NTP server, what is its level of accuracy?

i. What is the maximum drift allowed, and what is the frequency of re-calibration?

b. If acting as an NTP server, does it support GPS input?

c. Shall support RFC 1305

d. Should support NTPv4, RFC 5905 Support 2. Product shall have user guides and administration manuals available Support 3. Company shall have service support contracts available

a. 24/7/365 support shall be available (assuming the support contract is current)

b. Service support shall respond within 2 hours (assuming the response contract is current)

Device support

q. 24/7/365 support shall be available through phone and email (assuming the support contract is current)

b. Service support shall respond within 2 hours (assuming the response contract is current)