Yes. I worked on some of what is being discussed (main thread), and there were many extra pieces of documentation that I had to prepare declaring ITAR concerns.
If it's open source then necessarily it's been approved by export control. Anything open-sourced obviously can't contain ballistic information which would violate ITAR. But by default, all internal software and documents/documentation related to spacecraft/aircraft are assumed to be sensitive until they've gone through the export control process.
Yes, ITAR also relates to plans, schematics, software, data, all sorts of things. If anything, the ITAR language itself is very vague.
But usually the science type or payload data is one thing, and then the lower level hardware telemetry is done in a different way.
I've used GovCloud to store ITAR data. It's cool. If you encrypt your ITAR data, you can also store it in a public cloud like S3, but just for storage, you shouldn't decrypt it there or have the keys there.
(ex-Boeing, OS+support code for embedded LRUs)
reply