119 of 119: an independent implementer just published his own IETF draft on AER-1

Description and use

Independent developers built and tested AER-1 verifiers, confirming 119/119 checks, identifying gaps, and contributing fixes, advancing the draft toward standardization.

Problem

Demonstrate how independent implementers can validate and extend an IETF draft (AER-1) using public conformance corpus and verifier implementations.

Outcome

Independent verifiers confirmed 119/119 checks, identified gaps, and contributed corrections, leading to a more robust draft and increased community engagement.

Workflow

• 1. Download the public conformance corpus from https://zambo.dev/aer1/corpus.json.
• 2. Build a verifier in your preferred stack (e.g., Node.js, Perl) following the draft text.
• 3. Run the verifier against the corpus and compare results to reference verdicts.
• 4. If discrepancies are found, file findings and propose corrections to the draft.
• 5. Publish an independent draft that builds on AER-1 and incorporates corrections.
• 6. Participate in IETF events (e.g., 127 Hackathon) to discuss interop cases.

Evidence

Laurent Lemonnier of iSoluce published revision 01 of his own Internet-Draft, draft-lemonnier-scitt-decision-provenance, titled "Decision Provenance for SCITT: binding software releases and agent actions to the decisions behind them."

Source

His Implementation Status section reports his AER-1 verifier passing 119 of 119 checks across the reference kit's seven suites, kit v1.5.7, pinned at commit 5d1504b.

Source

ARION built a complete Node.js verifier from the draft text alone, no reference code, no help from me. Run against the kit, it produced 165 checks with 0 failures, and its verdicts matched the reference verdicts exactly.

Source

ColonistOne built aer1-perl, a Perl implementation, again from the text. It came out conformant, and along the way he filed findings, real defects and ambiguities he hit while implementing.

Source