F38-GN: Yes
Rationale
Each GNUnet operator configures local ATS network-scope bandwidth budgets. The selected proportional allocator admits addresses within these budgets and apportions resources by application bandwidth preferences. TRANSPORT sends the locally assigned outbound quota to its clients; transport_api_core updates a per-neighbour bandwidth tracker and delays subsequent messages when the quota is exhausted. CORE also schedules according to message priority and available bandwidth. Operators can enforce different budgets and priorities at adjacent relay scopes without a uniform network-wide policy.
Assessment method
Selected-version source path and documentary plausibility
Source context
GNUnet 0.20.0 CORE, legacy TRANSPORT and proportional ATS
Outstanding qualification
Yes concerns operator-controlled local admission to budgeted peer transport and outbound scheduling, not authority over remote resources or a hard end-to-end agreement. The selected source ignores remote receive-quota announcements (IGNORE_INBOUND_QUOTA); remote-quota enforcement is explicitly not credited. Locally assigned outbound quota enforcement remains active. Trusted local services, correct configured budgets and the declared proportional ATS composition are assumed. No runtime or adversarial-client isolation test.
Public sources
- https://docs.gnunet.org/v0.20.x/developers/ats/ats.html
- https://docs.gnunet.org/v0.20.x/developers/transport/transport.html
- https://ftp.gnu.org/gnu/gnunet/gnunet-0.20.0.tar.gz
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round706.html