F20-RI: Yes
Rationale
Selected RPL non-storing routing maintains topology, parent and destination information, with downward source routes generated by the root. DTLS association state terminates only at the final peers. These transit roles need no mandatory entry per end-to-end DTLS connection or application flow.
Assessment method
Documentary role/state inventory; no runtime test
Source context
Primary protocol specifications and unchanged selected compositions
Outstanding qualification
The root still stores destination/topology state, and routers retain neighbor/control state. 6LoWPAN reassembly may buffer fragments per datagram; that is not persistent state for an end-to-end flow. This does not establish memory bounds at global scale.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round260-sources.json