REQUEST FOR INFORMATION (RFI) SPAWAR, Atlantic RFI Announcement # N65236-17-RFI-0001_fbo Topic: Alternative Technologies to Traditional Cryptographic-based Communication Security (COMSEC) Systems 1.0 DISCLAIMER: THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Navy is not at this time seeking proposals and will not accept unsolicited proposals. Respondees are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested partys expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it will be synopsized on the Federal Business Opportunities (FedBizOpps) website and the SPAWAR E-Commerce Central website at https://e-commerce.spawar.navy.mil. It is the responsibility of the potential offerors to monitor these sites for additional information pertaining to this requirement. 2.0 BACKGROUND: Space and Naval Warfare Systems Center (SPAWAR) Atlantic is seeking information on the following topic by an interested contractor. 2.1 An architectural design and a possible prototype that uses information-theoretic, physical-layer security as an alternative to traditional cryptographic-based communication security (COMSEC) systems, involving a key management infrastructure (KMI). With advances in information theory and implementation of software defined radios in the Fleet, application of keyless COMSEC has numerous benefits. Technical requirements include the following: a. Reduce or eliminate the need for key exchange and management b. Reduce man-in-the middle attack impact c. Add geolocation privacy d. Supplement or replace traditional cryptographic algorithm-based COMSEC devices e. Software deployable. 2.2 Potential applications of the proposed design are intra-platform secure intercom, secure wireless networking, authenticating squad meshed network radios, and flight deck radio transmission security (TRANSEC) to mask operations tempo. Intra-platform primarily includes ship, shore, air, and ground interactive communications as well as other military departments (MILDEPS) or DoD agencies. 2.3 The technology should: a. Allow for serial, other legacy, and non-traditional device interface requirements to share data with the NetOps Manager of Manager (MoM) capability and provide critical NetOps and Cyber Situational Awareness data to enable proactive monitoring and management of crypto and other communications devices. b. Allow inputs to monitor the web based configuration tool of a large number of crypto devices and displays status changes and alarms on a single screen. c. Provide, at a glance, status updates and indication of each individual device and allow operators to access the configuration of the device. d. Provide innovative solutions to enhance crypto, network and communication devices to be accessible to monitoring and management. 2.4 Delivery Period: Proposals are due 30 days after RFI posting. 2.5 Limitations: Proposals must be at a Technology Readiness Level (TRL) of TRL-5 or higher. 2.6 Security Requirements: Proposals are to be submitted at the UNCLASSIFIED level. 4.0 SUBMISSION INSTRUCTIONS and FORMATTING REQUIREMENTS 4.1 Interested parties are requested to respond to this RFI with a white paper. 4.2 White papers must be in Microsoft Word or PDF format, and shall be typed in 12- point Times New Roman font, single spaced, with 1-inch margins. 4.3 White papers are due 30 days after RFI posting. Responses shall be limited to 5-pages for Section 2 and submitted via e-mail only to Jo Ann Lawless,
contact@example.gov . Subject line should be title White- paper_RFI_N65236_17_RFI_0001_fbo_ALPHA_contractor name. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. 4.4 Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum: 4.4.1 Name, mailing address, phone number, and e-mail of designated point of contact. 4.4.2 Data handling (Identify which approach is most applicable) a. A statement that the respondee will not allow the Government to release its proprietary data to Government support contractors. b. In the absence of either of the foregoing, the Government will assume that the respondee does NOT agree to the release of its submission to Government support contractors. 4.4.3 Business type (large business, small business, small disadvantaged business, 8(a)-certified small disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business). Small business concern means a concern, including any affiliates that are 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 and size standards in 13 CFR Part 121. Please refer to Federal Acquisition Regulation FAR 19 for additional detailed information on Small Business Size Standards. The FAR is available at http://www.arnet.gov. 4.4.4 The facility security clearance of the offeror. 4.4.5 The number of pages in Section 1 of the white paper shall not be included in the 5-page limitation, i.e., the 5-page limitation applies only to Section 2 of the white paper. 4.4 Section 2 of the white paper shall answer the issues addressed in this RFI. a. Responses shall not exceed 5 pages b. A suggested submission organization: 1. Cover Sheet [Section 1] 2. Abstract [Section 2] 3. Technical Description and Approach [Section 2] 4. Findings and Research Applications [Section 2] 5. Prototyping and Experimentation [Section 2] No cost or pricing information should be provided. Any received will be deleted and destroyed. 5.0 Industry Discussions SPAWAR, Atlantic representatives may or may not choose to meet with potential offerors. Such discussions would only be intended to get further clarification of potential capability to meet the requirements, especially any development and certification risks. 6.0 QUESTIONS AND POINT OF CONTACT Questions of a technical nature regarding this RFI may be sent to the following Point of Contact via email at
contact@example.gov. Jo Ann Lawless Code 22230, SPAWAR, Atlantic The subject line of the email shall read as follows : Question_ RFI_N65236_17_RFI_0001_fbo_ALPHA 7.0 Summary THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. The information provided in the RFI is subject to change and is not binding on the Government. The Navy has not made a commitment to procure any of the items discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned. This RFI is issued solely for information and program planning purposes; it does not constitute a formal solicitation for proposals. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Submission is voluntary and is not required to respond to a subsequent Broad Agency Announcement (BAA) (if any) or other research solicitation (if any) on this topic.
