SPECIAL NOTICE
A -- Common Cryptographic Management Information Base
- Notice Date
- 7/25/2012
- Notice Type
- Special Notice
- NAICS
- 541330
— Engineering Services
- Contracting Office
- Department of the Air Force, Air Force Materiel Command, ESC - Electronic Systems Center, 9 Eglin Street, Hanscom AFB, Massachusetts, 01731, United States
- ZIP Code
- 01731
- Solicitation Number
- RFI_CCMIB0725
- Archive Date
- 9/8/2012
- Point of Contact
- LaToya Siples, , Mark R. De La Rosa,
- E-Mail Address
-
latoya.siples.1@us.af.mil, mark.delarosa@us.af.mil
(latoya.siples.1@us.af.mil, mark.delarosa@us.af.mil)
- Small Business Set-Aside
- N/A
- Description
- Request for Information (RFI) About Common Cryptographic Management Information Base RFI#: RFI_CCMIB0725 This Request for Information (RFI) is in accordance with the Federal Acquisition Regulation (FAR) clause 52.215-3 (Request for Information or Solicitation for Planning Purposes - Oct 1997) and is published only to obtain information for use by the United States Air Force Electronic Systems Center Cryptologic Systems Division, Cryptographic Modernization Program Office (AF CMPO), Lackland Air Force Base, Texas, for market research and planning purposes only. This RFI is NOT a Request for Proposal, Invitation for Bid, or an announcement of a solicitation, it is intended for information or planning purposes only. There is no bid package or solicitation document associated with this announcement. Response to this RFI is strictly voluntary and will not affect any potential offeror's ability to submit an offer if a solicitation is released. Any requests for a solicitation package will be disregarded. The Government does not intend to award a contract on the basis of this RFI or otherwise pay for the information solicited. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of preparing submissions in response to this RFI and the Government's use of such information. Submittals will not be returned to the sender. Respondents of this RFI may be requested to provide additional information/details based on their initial submittals. The AF CMPO is in the process of designing and specifying a Simple Network Management Protocol version 3 (SNMPv3)-based common management technology suite suitable for managing End Cryptographic Units, (ECUs). This effort is related to the development and final release of IETF RFC 6353 - Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP), an alternative to SNMP's User-Based Security Model (USM). It also includes ongoing discussions about Management Information Base (MIB) modules for SNMP, and refining some preliminary development activities with regard to unifying a common architecture for MIB modules for managing cryptographic functions. This RFI is a successor to RFI Solicitation Number: RFI_CCMIB. AF CMPO analyzed, vetted, and incorporated into the CC MIB pertinent responses from this RFI. The Common Cryptographic Management Information Base (CC MIB) precept is a refined architectural concept for the development and standardization of a set of MIB modules which encapsulate and typify the management objects necessary to manage a cryptographic appliance through the full product lifecycle (initialization, use, and retirement). The CC MIB enables a 3-tiered, extensible construct to manage all cryptographic devices. The top tier is labeled the CC MIB Core. The CC MIB Core contains a set of cryptographic capabilities common to all cryptographic devices. The second tier (middle tier) is labeled the CC MIB Family Extension. The CC MIB Family Extension contains a set of cryptographic capabilities common to a specific ECU device family (e.g. HAIPE, LEF). The CC MIB Core and CC MIB Family Extension are designed to be extensible for the inclusion of future management functionalities. The final tier (lower tier) is the CC MIB Vendor Extension. The CC MIB Vendor Extension allows a vendor to include any additional cryptographic capability outside of what is defined in the previous two tiers. The AF envisions the CC MIB Family Extension and Vendor Extension MIBs as a means for industry to innovate and differentiate their products in the market place. The CMPO is seeking industry comments to the current draft of the CC MIB Core, CC MIB HAIPE and LEF family extensions, and CC MIB CONOPS, as well as answers to the questions below. For access to the draft CC MIB artifacts, please send an email digitally signed by a valid DoD External Certificate Authority issued certificate to latoya.siples.1@us.af.mil and mark.delarosa@us.af.mil. 1. What problems, if any, do you see with the encoding, format, or overall structure of the CC MIB? 2. Do you agree with the functionality of the CC MIB Core and CC MIB Family Extensions as currently architected? If not, what changes do you propose? 3. What design improvements would you recommend for the CC MIB? 4. Current efforts for the CC MIB (not included in this RFI release) include updating the CC MIB to be in compliance with RFC 5934 - Trust Anchor Management Protocol (TAMP) and draft-turner-sodp-02.txt (or successor) - Secure Object Delivery Protocol (SODP). What functionality do you see as missing and/or extraneous in the CC MIB? 5. Besides the LEF and HAIPE family extensions, what additional family specific extensions do you think should be added to the CC MIB? 6. What additional documentation is desirable in order to implement the CC MIB in an existing product line? 7. What management capabilities do your products currently have? 8. Would the incorporation of the CC MIB, a Family Extension MIB, and, if necessary, a Vendor Extension MIB into your cryptologic devices and systems reduce your effort to provide remote management capabilities for your systems? 9. Would the uniform adoption of the secure network protocols, TLS and DTLS, of IETF RFC 6353 in your cryptologic devices and systems facilitate the remote management of your systems? Why or why not? 10. In addition to CC MIB and IETF RFC 6353 technologies, what additional standards-based technologies would you suggest that would ease the training and operations burdens of AF Servicemen who must manage diverse types of remotely located cryptologic systems from multiple vendors? In addition to the above listed questions, please provide the following business information: 11. Please provide your cage code and business size. a. If you are a Small Business, do you also qualify under any of the sub-categories: 8(a), Small Disadvantaged Business, HUBZone, etc) 12. For small business consideration, would your firm be able to compete under NAICS 334111, 334119, 334210, 334220, 334290, 334419, 517919, or 541330? If not, why? 13. Are you on one or more GSA schedules? If so, which one(s)? Submissions shall not exceed thirty (30) 8.5 X 11 inch, single-sided pages. Vendors who submit information for review do so with the understanding that U.S. Government personnel as well as their support contractors will review their material and data. Respondents will not be contacted regarding their submission or information gathered as a result of this notice nor the outcome of the Government's review of the solicited information unless the Government desires further information. Submitted information packages will be retained by the Government and not returned to the contractor. All interested, capable and responsible sources that wish to respond to this RFI are required to electronically supply their responses (.doc or.pdf format) in the order and format in which they are presented, to latoya.siples.1@us.af.mil and mark.delarosa@us.af.mil no later than 1600 hrs CT, 24 August 2012. Telephonic responses will not be accepted. Electronic media can be mailed to: Cryptologic Systems Division Contracting Division/ESC/HNCKA (Attn: Mr. Mark Delarosa) 230 Hall Blvd. Suite 114 San Antonio, Texas 78243-7007
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AFMC/ESC/RFI_CCMIB0725/listing.html)
- Place of Performance
- Address: N/A, United States
- Record
- SN02814671-W 20120727/120725235637-1840b001ac7271a8953fc26399d51557 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |