Files
fips/docs/design
Johnathan Corgan 5a36cbda76 Merge v0.5.0 into next
Carries the release and the four commits beneath it onto the development
line: the fipsctl probe report rework, the native datagram API end-of-file
fix and its client-author documentation, the release content, and the
version bump.

The version conflict resolves to next's 0.6.0-dev, as the forward merge
always does. README keeps next's side throughout: the badge, the two-layer
Noise XX description, and the status paragraph all describe this line, and
taking the release side would have replaced them with the older IK and XK
model that next no longer uses. The CLI reference takes the release side,
whose wording is version-agnostic where next's had hardcoded a version
string in an example.

The changelog needed repair the merge did not flag. Git aligned the
released heading with next's Unreleased heading, which filed 181 lines of
next-only work under a released date, left the block holding the released
content marked unreleased, and produced two headings for one version. It
also dropped the entry describing the lost IPv6 scope on inbound source
addresses, which appeared nowhere on this line afterwards.

All four are corrected, and each correction is checked by diffing against
the side it came from. The Unreleased block is byte-identical to its state
before the merge. The released block differs from the release line's by one
line, the deliberate rewording that drops the handshake pattern name
because this line uses a different one. The Breaking block is untouched.
2026-08-30 15:48:27 +00:00
..
2026-08-30 15:48:27 +00:00
2026-08-30 15:48:27 +00:00
2026-08-30 10:42:59 +00:00
2026-08-30 15:48:27 +00:00
2026-08-30 15:48:27 +00:00
2026-08-30 15:48:27 +00:00

FIPS Design

Architectural and protocol-level explanations for FIPS — the why and the how behind the wire and the system. For wire formats and configuration keys, see reference/. For task recipes, see how-to/. For end-to-end lessons, see tutorials/.

Reading Order

Start with fips-concepts.md for the novice-friendly framing of what FIPS is and why, then move to fips-architecture.md for the protocol stack, identity model, and two-layer encryption walkthrough. From there, follow the protocol stack from bottom to top. After the stack, fips-mesh-operation.md explains how the pieces work together at runtime. Cross-cutting and supporting documents cover specific subsystems in detail.

Foundations

Document Description
fips-concepts.md What FIPS is, why it exists, mental model
fips-architecture.md Protocol stack, identity, two-layer encryption
fips-prior-work.md Designs and protocols FIPS builds on

Protocol Stack

Document Description
fips-transport-layer.md Transport layer: datagram delivery over arbitrary media
fips-mesh-layer.md FIPS Mesh Protocol (FMP): peer authentication, link encryption, forwarding
fips-session-layer.md FIPS Session Protocol (FSP): end-to-end encryption, sessions
fips-ipv6-adapter.md IPv6 adaptation: TUN interface, DNS, MTU enforcement
fips-native-api.md Native datagram API: pubkey-addressed flows over FSP, and what it is instead of the TUN path

Cross-Cutting

Document Description
fips-mmp.md Metrics Measurement Protocol (link + session)
fips-mtu.md Path MTU model, encapsulation overhead, PMTUD
fips-security.md fips0 interface threat model and default-deny baseline

Mesh Behavior

Document Description
fips-mesh-operation.md How the mesh operates: routing, discovery, error recovery
fips-nostr-discovery.md Optional Nostr-mediated peer discovery and UDP NAT hole-punch
port-advertisement-and-nat-traversal.md Nostr-signaled port advertisement and UDP NAT-traversal protocol; generic, with FIPS as an example implementation

Deeper Dives

Document Description
fips-spanning-tree.md Spanning tree algorithms: root discovery, parent selection, coordinates
fips-bloom-filters.md Bloom filter properties: FPR analysis, size classes, split-horizon
spanning-tree-dynamics.md Spanning tree walkthroughs: convergence scenarios, worked examples

Adjacent Components

Document Description
fips-gateway.md fips-gateway service: outbound (LAN-to-mesh) DNS-proxy + virtual-IP NAT and inbound (mesh-to-LAN) port-forwarding, sharing one nftables table