Conformance
Every normative statement of RFC 9946, and of the RFC 9097 sections it uses, is a Requirement with a stable ID: 420 in all. A Requirement counts as met when a test that runs on Linux proves it, unless it is recorded otherwise. These pages are generated by cargo xtask req’s checks when the site is built.
348 of 420 Requirements are proven by tests. Of the rest, 24 are Deviations, each recorded with its reason, 33 are operational (they concern how udpstp is deployed or used rather than its code), and 15 don’t apply to udpstp.
Coverage by section
Conformance Records
Where udpstp departs from a Requirement, reads an ambiguous one, or differs from OB-UDPST, a Conformance Record says what it does, why, and which tests prove it.
| Kind | Records |
|---|---|
| Deviations | 17 |
| Interpretations | 117 |
| OB-UDPST Differences | 31 |
How the records work describes the files these pages come from.
States
- Tested: a test that runs on Linux, in CI and before every push, proves it.
- Tested nightly: only tests in the nightly workflow prove it.
- Pending: no test proves it yet.
- Deviation: udpstp departs from it, as a Deviation records.
- Interpretation: udpstp meets it as an Interpretation reads it.
- Operational: it concerns deployment or use, not udpstp’s code.
- Not applicable: it doesn’t apply to udpstp.