- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jul 2015 16:03:58 +0000
- To: public-web-bluetooth-log@w3.org
jyasskin has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth: == Specify what happens when a device is paired, which reveals its identity address. == A UA may discover a device that's using a private address, and expose that device to a web page with a particular [`BluetoothDevice.instanceID`](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothdevice-instanceid). If the device is later paired, the UA learns the device's identity address and IRK. The spec needs to be clear that the device needs to keep the original `instanceID` through the pairing process. If the device is discovered again using a resolvable private address, the UA can match it to its public address using the IRK, and can use the same `instanceID`. No problem here. If the device is discovered again using a non-resolvable private address, it'll get a new `instanceID`. If it's later paired again, and it winds up having the same identity address as a previously-paired device, we can't magically cause it and the previous device to have the same `instanceID`. Should we add a field to devices to point out their canonical instance? An event that fires when this field gets populated? Just leave them as two distinct devices and hope people don't pair devices with non-resolvable addresses much? See https://github.com/WebBluetoothCG/web-bluetooth/issues/138
Received on Wednesday, 15 July 2015 16:04:02 UTC