Introduce a device setting controlling allowed connection types for AU.

chrome/browser/policy/proto/chrome_device_policy.proto

Index: chrome/browser/policy/proto/chrome_device_policy.proto
diff --git a/chrome/browser/policy/proto/chrome_device_policy.proto b/chrome/browser/policy/proto/chrome_device_policy.proto
index 17a1743c503794b86e1761f406e60b598d20e558..248fe72557ff7ec86a1640639b618cbef902e6cf 100644
--- a/chrome/browser/policy/proto/chrome_device_policy.proto
+++ b/chrome/browser/policy/proto/chrome_device_policy.proto
@@ -182,6 +182,23 @@ message AutoUpdateSettingsProto {
   // amount of time so that a device does not ever get stuck waiting to download
   // an update forever.
   optional int64 scatter_factor_in_seconds = 4;
+
+  // Enumerates network connection types.
+  enum ConnectionType {
+    CONNECTION_TYPE_ETHERNET = 0;
+    CONNECTION_TYPE_WIFI = 1;
+    CONNECTION_TYPE_WIMAX = 2;
+    CONNECTION_TYPE_BLUETOOTH = 3;
+    CONNECTION_TYPE_CELLULAR = 4;
+    CONNECTION_TYPE_VPN = 5;
+  }
+
+  // The types of connections that are OK to run updates over. OS updates
+  // potentially put heavy strain on the connection due to their size and may
+  // incur additional cost. Therefore, they are by default not enabled for
+  // connection types that are considered expensive, which include WiMax,
+  // Bluetooth and Cellular at the moment.
+  repeated ConnectionType allowed_connection_types = 5;
 }
 
 message StartUpUrlsProto {