Archived criterion

C08-BL: Yes

Archived previous-definition assessment — revision 4.72. Retired in 5.73; excluded from the active matrix and counts. This historical verdict is not a current assessment.

Rationale

RFC 8966 requires neighbor, source and route state, not a persistent archive of final communicating pairs. The selected IPv6/Babel service can operate without flow export or packet-history logging. Current route entries can still reveal topology; no forensic invisibility is claimed.

Assessment method

Primary-document analysis and selected-profile inference; no execution

Source context

Babel routing protocol, RFC 8966

Outstanding qualification

Pin the Babel daemon and IPv6 host configuration; disable optional flow/packet-history export. Inspect memory, journals and backups after traffic and route expiry, including daemon-specific default logging. Architectural capability does not certify a particular deployment.

Public sources