Standards and conformance#

Appendix C.1. The cipher itself is the RustCrypto `aes` crate; the vector is asserted through this crate's wrapper.

All four worked examples in section 4, including the 40 and 64 byte cases.

Both Appendix B worked examples, against the hand-written implementation the browser uses.

Pinned through RFC 4231, which publishes the SHA-256 vectors RFC 2104 does not.

Cases 1 and 2 in Rust, cases 1, 2 and 6 in the browser implementation.

The basic vector in Appendix A.1.

The Alice and Bob example in section 6.1, both public keys and the shared secret.

The worked example in section 2.8.2, sealed and opened.

Each named threat is answered by a test named after it. The SUIT CBOR serialization is a deliberate deviation: draft-ietf-suit-manifest is still a draft.

TEST 2 in section 7.1, asserting the full 64-byte signature.

The Appendix A vectors, plus the shortest-form rule in 4.2.1 and the refusal of indefinite-length items.

The published signed-integer mapping, asserted value by value.

All seven vectors in section 10, encoded and decoded, plus the unpadded form.

The octal constants and the stuffing rule, asserted as the RFC prints them.

COBS has no published standard; the paper is the authority. All eleven of its example encodings are asserted.

Check value 0x4B37 over the ASCII digits, plus a real six-byte request frame.

The worked request and reply of each of the eight functions in section 6, the exception example in section 7, and the register-count example given for exception 0x02.

The 3.5-character gap and its fixed 1.75 ms above 19200 baud from section 2.5.1.1; a broadcast carried out and not answered, and a frame that fails its CRC left unanswered, from sections 2.2 and 2.6.

Edition 3 supersedes the 2015 edition and the 1991 Bosch CAN 2.0 document.

Real published PGNs, including EEC1 at 61444 and the request PGN at 59904.

Run in CI against the kernel's own virtual CAN interface: classic, extended, remote, and CAN FD frames, a filter by J1939 parameter group, and no echo of a node's own frames.

The manual's own ten-bit worked example, 0x2A5 framing as 0xF4 0xA5.

The datasheets' own worked examples, including every CRC in the SCD4x command tables.

Each driver asserts its datasheet's own worked compensation example. Every document is linked from the hardware page, part by part.

Figure 1 of the A4988 datasheet and the DRV8825's timing requirements: 200 ns and 650 ns of setup before the rising edge, 1 and 1.9 microseconds high. The driver holds each for its pulse width, 10 microseconds unless told otherwise.

The text is the one w1_slave_show prints in the kernel's drivers/w1/slaves/w1_therm.c, and its millidegrees are the datasheet's temperature rows.

The join accept field positions in tables 44 and 55.

Each test is named after the table it checks: data rates, maximum payloads, the RX1 offset matrix.

Appendix 1's worked synchronization example, with WOR frames checked against Semtech LoRa Basics Modem and the root key against The Things Stack.

Every command checked against the size the specification gives it, cross-read with Semtech LoRa Basics Modem's own size constants.

ChirpStack's own command bytes, and the parity matrix against an independent rendering. The coded fragments are seeded by the index among the coded fragments, which is what Semtech's Basics Modem and ChirpStack both do; the appendix reads as though the session index were the seed.

ChirpStack's own command bytes, with the key chain of section 4.3 checked step by step.

Every command checked against the size the specification gives it, including the version that rides only with an installable image.

Equations 5 and 6, reproduced and checked.

Equations 2 and 3.

The protocol's own printed example datagrams, and every TX_ACK error value.

The three ID6 identifier examples the protocol glossary prints.

Check value 0x29B1. Also listed as CRC-16/CCITT-FALSE; the bare name CRC-16/CCITT means a different algorithm, KERMIT, which checks 0x2189.

Revised often; the link resolves to the current edition rather than a dated one.

With IEC 62305-2 for the risk assessment and IEC 62305-3 for the protection system itself.

Check value 0x6F91, with a second test asserting it is not the X-25 value 0x906E.

Every enumeration value as the dialect files define them at that commit, whose names every binding reads back identically.

Every twist, pose, and chassis model uses its body frame: x forward, y left, and a positive yaw turning left.

The published hash for std_msgs/msg/String.

Plain CDR is the CORBA transfer syntax; DDS and ROS 2 use the extended form.

Every intersection and inclusion vector from zenoh-keyexpr's own tests, the RFC's canonical-form statements, and a test that asks Zenoh's implementation the same questions.

Sections 4.7.1 and 4.7.2. The client itself speaks 3.1.1, whose topic rules are the same.

The valid and invalid filters of sections 4.7.1.2 and 4.7.1.3, and the remaining-length boundaries of Table 2.4. Acknowledged delivery at each level (4.3), a retained message and its clearing (3.3.1.3), the will a dropped client leaves and the DISCONNECT that discards it (3.1.2.5, 3.14.4), and the password rule of 3.1.2.9 are tested against an in-process broker in crates/pamoja-mqtt/tests/delivery.rs and were checked against Mosquitto 2.1.2.

Sections 4.2 to 4.5 and 5.3.1, and table 6. Beside it, a Reset and a 4.04 fail a confirmable send, and a ping is answered with a Reset.

The freshness conditions of section 3.4, including the 24-bit wrap and the 128-second rule.