[Privacy] Clarify steps to generate callbackId about remote-playback

[avayvod]

I'm not even sure what a "callback device" is in the question.

A callback is basically a Javascript function that can be called by the user agent. A numeric identifier is needed to be able to unregister the callback for cleanup. In Chrome we just find the next integer that's not assigned to any previously registered callback that hasn't been cancelled yet. I'd be wary putting this into an algorithm as it may restrict other user agents in their implementation and worse make web pages depend on the order of ids or something.

We can add a note that the identifier MUST not leak any privacy information, however I doubt that's very helpful.

[mfoltzgoogle]

My reading was that "Callback device" is the device triggering the callback, e.g. a newly discovered remote playback device.

[mfoltzgoogle]

I think a note clarifying the id generation mechanism would address this concern. I can propose a PR.

[avayvod]

The id is returned way before any device is found (at least in the simple use case when availability starts as a result of watchAvailability). When the device is found, the callback is fired with a single boolean argument and its id doesn't change.
Clarifying the id generation would probably help eliminate confusion though I agree.

[avayvod]

As a follow up on the PR #83, we might want to spec the uniqueness of the id (e.g. within a frame) so that web authors could rely on the behavior suggested by the example.

[mfoltzgoogle]

Closing as I believe this is addressed by the PR.