We exchange many Id strings between the browser process and the renderer process e.g. device id, service id, characteristic id, etc.

Introducing a new BluetoothId type would allow us to validate these strings when receiving them in the browser process.

Using a BluetoothId for service id, characteristic id, etc. in device/bluetooth might not be the right thing to do since the id format varies per platform but it would add another layer of security for the generated device ids in content/browser/bluetooth.