> List of Items Controlled
> a. Any type of telecommunications equipment having any of the following characteristics, functions or features
> a.2. Specially hardened to withstand gamma, neutron or ion radiation;
is ECC memory now a controlled item?
What this primarily refers to is hardware which has been fabricated on an exotic semiconductor process (like silicon-on-insulator substrates) to resist radiation-induced upsets or latchup. This hardware is almost exclusively used in military and space applications; it's basically nonexistent in the consumer space.
Why?
No, it is exceedingly unlikely that such a bit flip will have a real world impact beyond an unexpected error that manifests as an application crash or device reboot in the worst scenario, and most likely a temporary failure such as an image not loading or rendering, or a decryption operation that fails because the flipped bit makes is treated as an error.
Is it something to be concerned about? Generally not - if you are in an environment that has sufficient radiation that it has a practical impact on your phone, one would hope that your actual concern is more heavily focused on protecting your physical self, and one would hope that your personal threat model increases in scope to justify spending on electronics that are more resilient if you have budget left over after buying protective gear.
I recall coming across a more detailed write up a long time ago but still found mention of the issue [0]
> our clients rarely have ECC memory. We see a constant rate of memory corruption in the wild and end-to-end integrity verification always pays off.
[0] https://dropbox.tech/infrastructure/-broccoli--syncing-faste...
To detect bitflipping errors? Yes. Use cryptographically secure algorithms and protocols that ensure that messages have integrity checks in transit and in memory.
To detect crashes? Probably not - if a bit flips in memory without hardware level error correction that reports the error, there isn't really a way to detect what caused the error.
What you meant to ask is, "Is telecommunications equipment using ECC memory controlled under 5A001?", and the answer is no, a.2 refers to rad-hard components.
The key words are "specifically hardened to ..." instead of something like "using any technology that might help with ...". Generally the CCLs never use vague wording like this.
There are specific definitions for those terms with technical specifications. Then there are licenses/exemptions that mean you don't have to seek a license if you are selling to nongovernment customers in certain (friendlier) countries. There's also larger exemptions in export controls related to commercial off the shelf equipment and fundamental research that would apply as well.
Generally the take away is that if you're selling malware, exploits, or network surveillance equipment, you might want to talk to an export control lawyer first.
I don't deal with legal documents enough (luckily) to have ever really needed this, but it would be a nice thing to know how to use if needed, or on creative document sets. Essentially I'm asking for something where I can import a set of machine readable text (or OCR'd) set a grammar for references in context and then easily click through. If it's easy enough to extend the grammar I could probably link new things up as I go when new kinds of references pop up. Trying to get too smart about things like acronyms might be a step too far though, I want to be able to trust this tool completely.
Not the same XML format (s), but regulatory material (both Federal Register and CFR) is also published in XML.
The Government Printing Office has a Bulk Data Repository with the machine readable (largely XML) forms of legislative, regulatory, and a bunch of other documents: