Annex B: Annex B, Object identifiers

What the clause requires

What the public text does not state

• Every object identifier value
• Whether the amendment adds an identifier

What it means for you

Annex B is the one normative annex in the published contents list. It defines the object identifiers for the five algorithms, and clause 5 says those identifiers are the ones to use. That makes the annex the bridge between the standard and the protocols, certificates and module interfaces that need a number rather than a name.

The record does not state an identifier value. The ISO public preview stops before the annex and the values are not in the catalogue record. Writing a plausible arc would be the worst kind of invention, because an identifier is copied into code and into certificates and is hard to withdraw once it is in the field.

The buyer s evidence is a search, not a guess. Ask the engineering team where the module gets its algorithm identifier, and compare the value with the purchased annex. If the module uses a private or vendor arc, record that as a deviation and ask why. If it uses an identifier from another standard, record the cross-reference. The page gives the question and the evidence, not the number.

Evidence to keep

What an auditor or a customer is likely to ask for

Artefact	Owner	Why it matters
Module or protocol configuration showing the algorithm identifier in use	Engineering	The annex is normative and the value has to come from somewhere.
Comparison of that value with the purchased Annex B	Security architecture	A private arc is a deviation worth recording.
Purchase record for the base standard, so Annex B is available	Standards owner	The identifier values are not in the ISO public preview.

How to verify it

Ask where the identifier comes from. If the answer is a copy from another product or a blog, the trace is not to the normative annex.

Dates

The kit plan for annex B sets the evidence review at 17 June 2027, 90 days before the estimated publication date of 15 September 2027.

Cross references

• 5 Requirements on the usage of tweakable block ciphers
• A Annex A, Numerical examples
• 6 Deoxys-TBC
• 7 Skinny

Where this comes from