Reference to SDP in BluetoothScanFilter.

[armansito]

The documentation for BluetoothScanFilter says the following:

When determining the list of Service UUIDs a device supports, the UA must include Services advertised by the device, and may include Services previously discovered through the Bluetooth Service Discovery Protocol (SDP).

This should probably be clarified a bit. SDP is used for discovering services over BR/EDR and, while GATT over BR/EDR is possible, these are not limited to GATT services. This should really read something like "..., and may include GATT services previously discovered through the Attribute Protocol (ATT) and/or Service Discovery Protocol (SDP)"

[jyasskin]

If SDP isn't used for LE at all, I probably shouldn't mention SDP in the spec. (This wasn't clear when reading the Bluetooth spec, so thanks for pointing it out.) I'll change this to just mention ATT.

[armansito]

Low-energy devices will exclusively use ATT. But it IS possible for a classic device to support GATT over a BR/EDR link. I guess it should be clarified whether this API is meant strictly for low-energy devices or for anything that supports GATT.

[jyasskin]

3.C.15.4 says, "If a BR/EDR or BR/EDR/LE device supports a GATT-based service on the BR/
EDR transport, the service shall exist in the SDP server and the GATT server.", so you're right that a GATT service could be discovered via either.

I'm not sure if we want the spec to support BR/EDR. At the moment, I'm only making sure that my terminology supports LE, and it looks like the scanning part of this definition would also need to change to explicitly support BR/EDR. However, if it's easy to generalize the wording without sacrificing privacy or security properties, it'd be nice to include BR/EDR.