F24-YG: No
Rationale
The selected Yggdrasil composition uses ordinary TCP/TLS peerings and pinned Ironwood routing. Ironwood peer monitoring uses keepalive acknowledgements and read deadlines; routing/path timers refresh reachability. Neither service negotiates when a sleeping receiver will be listening or queues delivery against that schedule.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
Reticulum Link, Ironwood peers and Linux NET/ROM
Outstanding qualification
Idle peerings, adjustable timeout values and reconnection after waking are distinct from coordinated reception. The selected composition includes neither a scheduled MAC nor an application delivery scheduler. This does not deny that Yggdrasil could run over a separate sleep-aware link service; that service is absent from this column. Source-qualified architectural verdict, not a runtime test.
Public sources
- https://raw.githubusercontent.com/Arceliar/ironwood/d50055b11f5ec5b56ee4e56ba9a75261461821dc/network/peers.go
- https://raw.githubusercontent.com/Arceliar/ironwood/d50055b11f5ec5b56ee4e56ba9a75261461821dc/network/config.go
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round505.html
- round505-sources.json