Participant Relationship Protocol

Back to matrix

D01-BL: Yes

Rationale

The selected IPv6/Babel composition already includes provisioned leaf LANs. An ordinary leaf endpoint uses the stock IPv6 data plane; Babel speakers maintain routes on the routers, rather than requiring every consuming application to administer routing. The retained Debian 13.6 / Linux 6.12.101 experiment in round 2.34 demonstrates native IPv6 protocol-253 request/reply through pre-opened raw sockets after both endpoints permanently dropped UID/GID to 65534 and cleared effective, permitted, inherited and ambient capabilities. Combining that endpoint witness with the documented separation of routing and forwarding supports unprivileged routine leaf operation.

Assessment method

Documentary role/composition analysis with reused bounded runtime evidence; no new runtime execution

Source context

RFC 8966, babeld maintainer documentation and retained Linux IPv6 endpoint experiment

Outstanding qualification

This is a documentary composition finding, not a newly executed Babel network test. The reused experiment was loopback-only and did not run Babel, a routed multi-host topology or an external NIC. Initial raw-socket creation and interface/address/route provisioning require privileges. Routers may continue to require privileged route installation; no claim is made that babeld itself runs without elevated capabilities. The Yes applies to the ordinary provisioned leaf endpoint allowed by D01, not to a node simultaneously acting as a router. No UDP/TCP application transport or new profile is added.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.