RFC conformance: review against the code, the verify budget, newer RFCs
Finals within a budget, packets no faster than the peer may send RFC conformance names the Poll budget as deviation 4 and the spacing as a note; Monitoring lists too-fast and changes-lost; the security model adds the churning-timer flood; Limitations has the engine at 2% for 1024.
RFC conformance: the fast path demuxes on Your Discriminator and keeps one source port Deviation 4 is gone: a packet naming one of our discriminators reaches userspace when the address pair misses. The fallback socket is bound within 49152-65535, and both planes send from the port the session bound.
RFC conformance: name the remaining deviations; fix the deployment example The fast path now keeps to our transmit rate, which the page explains. Echo sourcing and the fast path's address-pair demux are listed as deviations. The engine.conf example drops --dp-peer, which a TCP port ignores, and --stats-dump, now the default.
Seed the wiki: deployment, limitations, conformance, kernels, security, testing The README was cut back to what a reader needs first. This is the rest of it: the deployment notes and the reserved-port trap, the deviations from stock bfdd and from the RFC, the kernels the object is known to load on, the threat model and the flood measurements, and what each test suite covers and needs.