F39-RI: No
Rationale
The selected RPL/IPv6/UDP/DTLS composition uses numeric peer addresses and transport ports. RPL computes network routes; DTLS protects the exchange. Neither adds location-independent process naming and local-versus-remote IPC selection.
Assessment method
Primary specifications and retained implementation-source review; no runtime test
Source context
Native IPC naming, local dispatch and selected service boundary
Outstanding qualification
The same UDP API can carry local or remote traffic, but the caller still supplies a host-addressed endpoint. This is not a denial of loopback. No CoAP naming, broker or extra IPC wrapper is selected.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round691.html