GUARDAID Annex 1: Technical specification

GUARDAID Annex 1 says what each party to an encounter between software agents does, and why. This specification says the bytes. It carries three things. The complete CDDL, in one place, of everything the annex defines, including two extension fields of its own: presence (1003) and distress (1004). The test vectors: 52 cases — 21 that verify and 31 that stop, each with its real bytes and the code it must stop with. And the conformance list: what an implementation has to pass to say that it implements Annex 1, component by component. No byte of the document was written by hand. The generator that produces the vectors is published in this record together with them, so that anyone can regenerate a case and check that it is what it says it is. It adds no mechanism. Where something the annex does not decide comes up, it is a defect of the annex and is corrected there. Open, free of charge, with nothing to sign. Files. The specification in English, which is the normative language, and a Spanish translation as an informative version; where the two differ, the English governs. The generator (generate.py, requires cbor2) and the vectors it produces (vectors.json). Feedback. Corrections, implementation reports and findings of an error are welcome at [email protected]. A difference between two of these documents is a defect in one of them, and reporting it is the fastest way it gets fixed.