F35-CJ: Yes
Archived previous-definition assessment — revision 5.73. Retired in 5.82; excluded from the active matrix and counts. This historical verdict is not a current assessment.
Rationale
The selected cjdns deployment permits administrators to add a UDP/CryptoAuth peering between intermediate nodes. The pinned InterfaceController attaches peers to SwitchCore and reports compatible peer paths to the pathfinder. Ordinary application traffic uses paths supplied through the existing SessionManager, so additional inter-region connectivity does not require new endpoint applications or custom route-label code.
Assessment method
Primary specification review; no runtime experiment
Source context
Pinned Yggdrasil/Ironwood and cjdns peering/forwarding sources
Outstanding qualification
Before/after witness: join two compatible cjdns regions through a new transit-node peering. Provision numeric IPv4 contacts, keys and private peering credentials; retain the configured route-server/pathfinder infrastructure and ensure it learns and distributes the new reachable paths. Endpoint identities and local attachments remain unchanged. This is a conditional routing-deployment capability, not proof that every peering becomes preferred or that discovery and active sessions recover without interruption. No DNS seed, public beacon, IP tunnel endpoint or replacement routing service is added. Exact deployment execution and convergence timing remain unqualified.
Public sources
- https://github.com/cjdelisle/cjdns/blob/f5902acab6dd2f1a68bf6e4c89e352ed71f93698/doc/peering.md
- https://raw.githubusercontent.com/cjdelisle/cjdns/f5902acab6dd2f1a68bf6e4c89e352ed71f93698/net/InterfaceController.c
- https://raw.githubusercontent.com/cjdelisle/cjdns/f5902acab6dd2f1a68bf6e4c89e352ed71f93698/net/SessionManager.c
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round523.html
- round523-sources.json