diff options
| author | Magnus Feuer <mfeuer@jaguarlandrover.com> | 2015-06-26 16:09:44 -0700 |
|---|---|---|
| committer | Magnus Feuer <mfeuer@jaguarlandrover.com> | 2015-06-26 16:16:14 -0700 |
| commit | 5a5e97bca23fbc3066b2b65e635b17f5c77a9ccd (patch) | |
| tree | f84bcb7c2a6459ae0458d3c4b0412dc60d0aa45e | |
| parent | 6e18cfe2c5ea35ce87b756d1f5718d7cddb8d019 (diff) | |
| download | rvi_core-5a5e97bca23fbc3066b2b65e635b17f5c77a9ccd.tar.gz | |
Fixed formatting
| -rw-r--r-- | doc/rvi_services.md | 23 |
1 files changed, 13 insertions, 10 deletions
diff --git a/doc/rvi_services.md b/doc/rvi_services.md index 0292c09..f7e43ac 100644 --- a/doc/rvi_services.md +++ b/doc/rvi_services.md @@ -6,12 +6,12 @@ Attribution-ShareAlike 4.0 International. # REVIEW NOTES BY MAGNUS: 1. Shall "internal" services be specially marked?<br> How about ```jlr.com/vin/123456/dm/cert_provision``` is renamed -```jlr.com/vin/123456/dm/$cert_provision```.<br> + ```jlr.com/vin/123456/dm/$cert_provision``` .<br> All services starting with ```$``` are routed to RVI-internal code. 2. Per-service configuration? Current setup: - +``` "jsonrpc": "2.0", "id": 1, "method": "message", @@ -20,8 +20,11 @@ Current setup: "params": { "variable" : ["varname1","varname2"] } +``` + Suggested change: +``` "jsonrpc": "2.0", "id": 1, "method": "message", @@ -31,6 +34,8 @@ Suggested change: "service" : "jlr.com/vin/123456/body/lock", "variable" : ["varname1","varname2"] } +``` + Similar setup for setting configuration. @@ -133,8 +138,7 @@ The app is started for the first time and connects to the provisioning server. 2. Device sends authenticate to server<br> The command contains the auth cert (device public key) and the single, -pre-provisioned node certificate giving the device the right to invoke -```jlr.com/provisioning/setup``` +pre-provisioned node certificate giving the device the right to invoke ```jlr.com/provisioning/setup``` 3. Server sends authenticate to device<br> The server's auth cert (server public key) is sent, but no node @@ -173,16 +177,16 @@ Connection is done over bluetooth, with no Internet connection. 2. Device sends authenticate to vehicle<br> The command contains the auth cert together with the received node certificate, proving that it has the right to invoke -```jlr.com/vin/ABCD/unlock```.<br> + ```jlr.com/vin/ABCD/unlock```.<br> It also proves that the device has the right to register -```jlr.com/mobile/1234/status```. + ```jlr.com/mobile/1234/status```. 3. Vehicle sends authenticate to device<br> The server's auth cert (server public key) is sent, together with a pre-provisioned node certificate giving it the rights to register -```jlr.com/vin/ABCD/unlock```.<br> + ```jlr.com/vin/ABCD/unlock```.<br> The certificate also gives the vehicle the right to invoke -```jlr.com/mobile/*/status```. + ```jlr.com/mobile/*/status```. 4. Device sends service announce to vehicle<br> The command contains ```jlr.com/mobile/1234/status```.<br> @@ -213,8 +217,7 @@ step 2. 2. Device sends authenticate command to server<br> The command contains the auth cert together with a node cert showing -that the device has the right to register register -```jlr.com/mobile/1234/receive_bitcoin```. +that the device has the right to register register ```jlr.com/mobile/1234/receive_bitcoin```. 3. [server responds with its own authenticate] |