BIS classifies items to the ECCN paragraph or EAR99 on request (CCATS), but a CCATS is not a determination that an item is subject to the EAR, so requesters must first rule out other agencies' exclusive jurisdiction; classification requests are limited to six items, filed in SNAP-R with technical literature as PDFs, completing the specified blocks with a recommended classification and its basis in Block 24 (or the ambiguities preventing one). Advisory opinions on licence requirements or EAR interpretation are requested in writing (mail, RPD2@bis.doc.gov or the website) with contact details, party, end-use and model information and the ECCN; they do not bind future licensing and are not jurisdiction determinations. Specific routes cover encryption classification (740.17(d), Supplement No. 6 to Part 742), confirmation that a part, component, accessory, attachment or software is not 'specially designed' because form and fit changes are minor (interagency consensus), and confirmation that an AI model is below the 4E091 threshold.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.