ObliviOS Developer portal Project site

Home / Decisions / ADR-107

Amend ADR-106: correct design §6.2's Device-ID.

Accepted, recorded 28 September 2026.

Decision
ADR-107
Date
2026-09-28
Status
AcceptedAccepted
Mentions
ADR-106
Mentioned by
ADR-108, ADR-109

1Decision

Amend ADR-106: correct design §6.2's Device-ID (SDP) scoping mechanism from BTA_DmSetLocalDiRecord to system/stack/sdp/sdp_server.cc's process_service_search_attr_req per-connection attribute-response path.

2Why and evidence

Task 1 of docs/superpowers/plans/2026-09-28-airpods-platform-integration.md, executed against the real pinned Bluetooth stack source on the build server (idle at the time; no writes made — pure grep/sed -n reads), found BTA_DmSetLocalDiRecord (and the SDP_SetLocalDiRecord it calls) takes no peer/BD_ADDR parameter at all: it is called once at Bluetooth-enable time and writes a single global local SDP record answered identically to every peer's SDP query.

Design §6.2's bonded-BD_ADDR scoping condition cannot be applied at that function as originally written.

The real, per-connection hook point with the peer's BD_ADDR available is process_service_search_attr_req in sdp_server.cc (p_ccb->device_address), which already contains a working precedent for exactly this shape of peer-scoped, in-place SDP attribute override: sdp_dynamic_change_hfp_version, which checks an interop allowlist against the requesting peer's BD_ADDR before mutating an outgoing attribute.

The L2CAP half of §6.2's mechanism (l2c_fcr_chk_chan_modes) was independently confirmed exactly as originally designed, with its own existing per-BD_ADDR precedent (l2c_should_skip_ertm) — no change needed there. Full evidence: docs/research/airpods-bluetooth-stack-investigation.md.

3Consequences

Design doc §6.2 is amended in place with a dated amendment note citing this ADR; the original approved text is kept, not deleted, for the audit trail. No change to the mechanism's intent, threat model (§9/§10), or AIR-021's validation criteria — only the named source location of the Device-ID patch. Task 3 of the platform-integration plan may now proceed against the corrected hook point.

4Review when

If a future AOSP/Bluetooth-stack rebase restructures sdp_server.cc's attribute-response path or removes the sdp_dynamic_change_hfp_version-style per-peer override pattern this amendment relies on, Task 3's patch location needs re-verification against the new pinned revision before reuse.

Read from docs/governance/decision-log.md, entry ADR-107.