DARPA-BAA-11-01_QAs_-_12-7-10.docx
DOCX document 18 KB Posted
- Attached to
- System F6 Federal contract opportunity
- Solicitation number
- DARPA-BAA-11-01
About this file
Attached is a second round of Questions and Answers (12-7-10)
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| DARPA-BAA-11-01 Q As - 11-12-10.docx | DOCX document | |
| DARPA-BAA-11-01 System F6.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
System F6, DARPA-BAA-11-01 Questions & Answers 11/6/10 - 11/19/10
Question 111:
Is it correct to assume that the open source FDK supplied for Technical Area 3 does not have to include the full-up middleware developed for the Technical Area 3, as long as it (1) accurately represents the external interfaces and behaviors of the Technical Area 3 middleware, (2) includes full source for an API and reference implementation (e.g. code examples using the API) meeting the open source release requirements, and (3) includes the Technical Area 3 FDK documentation and interface specification?
Answer 111:
The BAA states that the FDK includes, “interface standards, protocols, software, behaviors, and reference implementations thereof.” So software including the middleware should be included.
Question 112:
Are we correct in assuming that the full Technical Area 3 technology packages can be ITAR controlled (in contrast to the FDK which must be open source)?
Answer 112:
No. Technical Area 3 does not specify the development of a space-qualified technology package as referenced in the question. Technical Area 3 only specifies the development of standards, software, and reference implementations. Additionally refer to Question 116.
Question 113:
Historically, restrictions in TAAs have precluded the export of key technologies like encryption and data guard technologies that enable MLS (i.e. cannot be offered or discussed). Should bidders assume that these limitations will be worked within the Government by the time discussions with international participants are conducted?
Answer 113:
As the BAA states, “A cryptographic solution that meets defense standards for space systems communications, while remaining unclassified and shareable in an open-source and internationally collaborative environment, is desired.” Additionally refer to Question 116.
Question 114:
How much do the modules move relative to each other? Can we expect major changes in the topology of the network in which we are routing?
Answer 114:
Relative velocities between modules will depend on the selected cluster flight solution in Technical Area 4. Offerors should detail any assumptions made or limitations on their proposed approach in their technical proposal.
Question 115:
What is the base station that the data would be routed to? Is it another satellite? Is it an earthbound station?
Answer 115:
As the BAA states, “The third technical area seeks the development of an information architecture to function at Layers 3 through 7 across the space-based wireless links and extending to the ground segment via a variety of downlink paths.”
Question 116:
Have there been any new developments regarding the designation of technologies developed under this BAA with respect to export control regulations.
Answer 116:
As the cognizant U.S. government agency and pursuant to the authority of 22 CFR §120.11(a)(7), DARPA has determined that the architectures, standards, reference implementations thereof, and any discussions and working documents in pursuance thereof, developed under this BAA contract shall be published and made generally accessible and available to the public without export control restrictions. Specially excluded from the scope of this determination are designs of physical hardware and the hardware itself in Technical Area 2. Notwithstanding this determination, the DARPA Program Manager shall review information for compliance and scope with respect to the applicable Statement of Work and Security Classification Guide to ensure its appropriateness for release into the public domain.
File details come from the government source that posted it. Updated .