[CrOS Tether] Add tether network properties (battery percentage, carrier, and signal strength) to t…

components/onc/docs/onc_spec.md

 # Open Network Configuration
 
 [TOC]
 
 ## Objective
 
 We would like to create a simple, open, but complete format to describe
 multiple network configurations for WiFi, Ethernet, Cellular,
 Bluetooth/WiFi-Direct, and VPN connections in a single file format, in order
 to simplify and automate network configuration for users.
@@ skipping 212 matching lines @@
 * **WiMAX**
     * (required if **Type** is *WiMAX*, otherwise ignored) -
       [WiMAX](#WiMAX-type)
     * WiMAX settings.
 
 * **Cellular**
     * (required if **Type** is *Cellular*, otherwise ignored) -
       [Cellular](#Cellular-type)
     * Cellular settings.
 
+* **Tether**
+    * (required if **Type** is *Tether*, otherwise ignored) -
+      [Tether](#Tether-type)
+    * Tether settings.
+
 * **Type**
     * (required if **Remove** is *false*, otherwise ignored) - **string**
     * `Allowed values are` *Cellular*,
         *Ethernet*, *WiFi*,
         *WiMAX* and *VPN*.
     * Indicates which kind of connection this is.
 
 * **ConnectionState**
     * (optional, read-only) - **string**
     * The current connection state for this network, provided by the system.
@@ skipping 1176 matching lines @@
 * **RetriesLeft**
     * (optional) - **integer**
     * If **LockType** is empty
       or *sim-pin*, then this property represents
       the number of attempts remaining to supply a correct PIN before the
       PIN becomes blocked, at which point a PUK provided by the carrier would
       be necessary to unlock the SIM (and **LockType**
       changes to *sim-puk*).
 
 
+## Tether Networks
+
+For Tether connections, **Type** must be set to *Tether* and the
+field **Tether** must be set to an object of type [Tether](#Tether-type).
+
+Used for representing a tether hotspot produced by a device with a cellular

[stevenjb, 2017/04/18 23:34:14]

s/produced by a device with a cellular chip/provided by an external device, e.g.
a phone/ ?

I don't think the technology used to provide the hotspot matters from an API
perspective.

[Kyle Horimoto, 2017/04/18 23:41:13]

Done.

+chip.
+
+### Tether type
+
+* **BatteryPercentage**
+    * (optional, read-only) - **integer**
+    * The battery percentage of the device providing the tether hotspot in the
+      range [0, 100].
+
+* **Carrier**
+    * (optional, read-only) - **string**
+    * The name of the cellular provider through which the hotspot is providing
+      an Internet connection.

[stevenjb, 2017/04/18 23:34:14]

'The name of the cellular carrier when the hotspot is provided by a cellular
connection'?

[Kyle Horimoto, 2017/04/18 23:41:13]

Done.

+
+* **SignalStrength**
+    * (optional, read-only) - **integer**
+    * The current signal strength for this network in the range [0, 100].

[stevenjb, 2017/04/18 23:34:15]

s/for this network/for the connection to the hotspot/? Or is it the hotspot's
signal strength? We should be clear either way.

[Kyle Horimoto, 2017/04/18 23:41:13]

Done, and added some extra clarification.

+
+
 ## Bluetooth / WiFi Direct Networks
 
 This format will eventually also cover configuration of Bluetooth and WiFi
 Direct network technologies, however they are currently not supported.
 
 
 ## Certificates
 
 Certificate data is stored in a separate section. Each certificate may be
 referenced from within the NetworkConfigurations array using a certificate
@@ skipping 329 matching lines @@
 is transmitted or saved to disk should be secure. On client device, when
 user names for connections that are user-specific are persisted to disk,
 they should be stored in a location that is encrypted. Users can also opt in
 these cases to not save their user credentials in the config file and will
 instead be prompted when they are needed.
 
 ## Authors
 
 * pneubeck@chromium.org
 * stevenjb@chromium.org