# 6.12.5.7 Why the new clause sits after SM2

The amendment inserts the new clause after the last verification subclause of the SM2 mechanism. The position is not cosmetic: it keeps the certificate-based mechanisms in Clause 6 and leaves the identity-based mechanisms in Clause 7 untouched, which tells a reader that EdDSA is certificate-based.

## What it asks

Place EdDSA in the certificate-based part of your own documentation and inventory, and confirm that an identity-based deployment is out of scope for this amendment. A reader who files EdDSA with the identity-based mechanisms will look for the wrong key management.

## What the amendment does

Inserts the new clause after 6.12.5.7.

## Who it binds

The author of the internal standard and the inventory owner.

## Evidence an auditor samples

- The internal standard structure, with EdDSA among the certificate-based mechanisms (cryptography standard)
- The inventory view that separates certificate-based and identity-based rows (configuration management database)
- The scope note that records the identity-based mechanisms as untouched (design note)

## The test you can run

Ask where EdDSA sits in the internal standard. If it is filed with the identity-based mechanisms, the key management section above it will be wrong.

## Common failures

- The mechanism is filed by product rather than by the clause structure.
- The scope note claims the whole standard changed.

## How to close it

Structure is a claim about scope. File the new mechanism where the clause puts it, and write one line that says the identity-based mechanisms were not amended, so that a reader knows what not to re-open.

## Source

ISO/IEC 14888-3:2018/FDAM 1:2026(en), draft, 6.12.5.7. Read on 21 October 2026. Our wording, not the instrument's.
https://www.iso.org/standard/89517.html

Not legal advice; does not certify.