CrOS policies: Store device ID with device token

chrome/browser/policy/proto/device_management_local.proto

Index: chrome/browser/policy/proto/device_management_local.proto
diff --git a/chrome/browser/policy/proto/device_management_local.proto b/chrome/browser/policy/proto/device_management_local.proto
index cd5a93abeb02b462f7ebc0d6edfbdc031925d49a..269b00d384dfa5a06a1853498131e1f36ae3168e 100644
--- a/chrome/browser/policy/proto/device_management_local.proto
+++ b/chrome/browser/policy/proto/device_management_local.proto
@@ -18,3 +18,9 @@ message CachedDevicePolicyResponse {
   optional uint64 timestamp = 2;
 }
 
+// Encapsulates a device token and the associated device ID.

[Mattias Nissler (ping if slow), 2010/11/15 18:02:51]

The comment suggests you generate a device ID for a token, but actually it's the
other way round.

[Jakob Kummerow (corp), 2010/11/16 09:37:02]

Done.

+message DeviceToken {

[Mattias Nissler (ping if slow), 2010/11/15 18:02:51]

Same for the message name here. Can we make it something more generic, maybe
DeviceMetaData? Or DeviceIdentity? Not sure these are good choices, but
DeviceToken is actually missing the ID part.

[Jakob Kummerow (corp), 2010/11/16 09:37:02]

Done.

+  required string device_token = 1;
+  required string device_id = 2;

[Mattias Nissler (ping if slow), 2010/11/15 18:02:51]

Can we make these optional?

[Jakob Kummerow (corp), 2010/11/16 09:37:02]

Done.

+}
+