Proposed Use Case #2 Sticking with the automobile theme, I am concerned about authorization to access data stored within a vehicles computer systems. As autos become smarter and more of them have built-in navigation and emergency communications systems, the data accumulating in these systems becomes increasingly personal. The data is of value to many parties. At a minimum these include the following: 1. the vehicle "owner" 1. who may need emergency assistance 2. who may want to look up some historical facts of his travel (distance traveled to a client site that may be reimbursable) 3. who may want to update the information when he replaces parts or performs maintenance 4. who may need to prove that he wasn't the driver when the car caused an accident or was used for criminal purposes 5. erase his personal driving data when the car is sold or junked 2. the mechanic 1. who may use the information for diagnostic purposes 2. who may update the information with parts replaced, maintenance performed, or accident information 3. the vehicle lessor (in case the vehicle is leased and not purchased) 1. who may bill by mileage 2. who may charge a premium for driving in certain areas (e.g., foreign countries) 4. the insurance company who may charge lower rates for safe driving behavior 5. a prospective second-hand buyer 1. who want to know both the driving history 2. the maintenance/repair history 3. the accident history 6. law enforcement 1. who may use the information to investigate an accident 2. who may use the information as evidence of negligent driving 3. who may use the information to track a vehicle 7. the auto manufacturer 1. who may use it to detect flaws 2. who may use it to improve future models 8. wrongdoers 1. who may use it to track down their victims. 2. may attempt to falsify the history to avoid insurance liability (e.g., in an accident) 3. may attempt to falsify the history to improve resale value 4. may attempt to falsify various information to disguise auto theft. Unlike Ingo's use case which appears only to require uniquely identifying a vehicle, this scenario requires selectively authorizing read and write access to a large amount of personal data by a variety of parties. Use Case #3 Electric refueling at a friend's house As electric cars become more common, the scenario is likely to evolve where Bob drives Carole's electric car to visit Alice. Once at Alice's house, he wants to recharge his vehicle using Alice's electric hookup. But he wants the bill for the electricity used for charging to go to his account, rather than hers. Currently, to do this would likely require having Alice go online to her account to tell the electricity supplier that all electricity going through the car charge for the next three hours should be charged to Bob. And Bob will have to go into his account to authorize the charges coming from Alice's charger. As we migrate towards IoT, it may be possible to make this transaction more automated. One obvious way is to allow the electric hookup to interrogate each car and change any charging to the registered owner of the vehicle. This would solve many problems. But in this case, it would mean that Carole would be charged for Bob's use of the electricity. Another option would be to use the scenario above, but allow for an override function. The system may default to charging Alice, but by entering a command (through some interface which might be a hardware switch), Bob could authenticate and direct the charges to his account or credit card. I don't consider this as interesting as Use Case #2. But it does involve true authentication, not just identification. Thank you. Jeff -- Jeff Stollman stollman.j@gmail.com 1 202.683.8699 Truth never triumphs — its opponents just die out. Science advances one funeral at a time. Max Planck
It would be interesting to look at the EULA you sign when you get a car.. From: dg-idot-bounces@kantarainitiative.org [mailto:dg-idot-bounces@kantarainitiative.org] On Behalf Of j stollman Sent: Monday, August 19, 2013 9:05 AM Cc: dg-idot@kantarainitiative.org Subject: [DG-IDoT] Proposed IoT Use Cases #2 and #3 Proposed Use Case #2 Sticking with the automobile theme, I am concerned about authorization to access data stored within a vehicles computer systems. As autos become smarter and more of them have built-in navigation and emergency communications systems, the data accumulating in these systems becomes increasingly personal. The data is of value to many parties. At a minimum these include the following: 1. the vehicle "owner" 1. who may need emergency assistance 2. who may want to look up some historical facts of his travel (distance traveled to a client site that may be reimbursable) 3. who may want to update the information when he replaces parts or performs maintenance 4. who may need to prove that he wasn't the driver when the car caused an accident or was used for criminal purposes 5. erase his personal driving data when the car is sold or junked 2. the mechanic 1. who may use the information for diagnostic purposes 2. who may update the information with parts replaced, maintenance performed, or accident information 3. the vehicle lessor (in case the vehicle is leased and not purchased) 1. who may bill by mileage 2. who may charge a premium for driving in certain areas (e.g., foreign countries) 4. the insurance company who may charge lower rates for safe driving behavior 5. a prospective second-hand buyer 1. who want to know both the driving history 2. the maintenance/repair history 3. the accident history 6. law enforcement 1. who may use the information to investigate an accident 2. who may use the information as evidence of negligent driving 3. who may use the information to track a vehicle 7. the auto manufacturer 1. who may use it to detect flaws 2. who may use it to improve future models 8. wrongdoers 1. who may use it to track down their victims. 2. may attempt to falsify the history to avoid insurance liability (e.g., in an accident) 3. may attempt to falsify the history to improve resale value 4. may attempt to falsify various information to disguise auto theft. Unlike Ingo's use case which appears only to require uniquely identifying a vehicle, this scenario requires selectively authorizing read and write access to a large amount of personal data by a variety of parties. Use Case #3 Electric refueling at a friend's house As electric cars become more common, the scenario is likely to evolve where Bob drives Carole's electric car to visit Alice. Once at Alice's house, he wants to recharge his vehicle using Alice's electric hookup. But he wants the bill for the electricity used for charging to go to his account, rather than hers. Currently, to do this would likely require having Alice go online to her account to tell the electricity supplier that all electricity going through the car charge for the next three hours should be charged to Bob. And Bob will have to go into his account to authorize the charges coming from Alice's charger. As we migrate towards IoT, it may be possible to make this transaction more automated. One obvious way is to allow the electric hookup to interrogate each car and change any charging to the registered owner of the vehicle. This would solve many problems. But in this case, it would mean that Carole would be charged for Bob's use of the electricity. Another option would be to use the scenario above, but allow for an override function. The system may default to charging Alice, but by entering a command (through some interface which might be a hardware switch), Bob could authenticate and direct the charges to his account or credit card. I don't consider this as interesting as Use Case #2. But it does involve true authentication, not just identification. Thank you. Jeff -- Jeff Stollman stollman.j@gmail.com 1 202.683.8699 Truth never triumphs - its opponents just die out. Science advances one funeral at a time. Max Planck
Thank you Jeff....I'll put them to the our use-case repository From: dg-idot-bounces@kantarainitiative.org [mailto:dg-idot-bounces@kantarainitiative.org] On Behalf Of j stollman Sent: Montag, 19. August 2013 15:05 Cc: dg-idot@kantarainitiative.org Subject: [DG-IDoT] Proposed IoT Use Cases #2 and #3 Proposed Use Case #2 Sticking with the automobile theme, I am concerned about authorization to access data stored within a vehicles computer systems. As autos become smarter and more of them have built-in navigation and emergency communications systems, the data accumulating in these systems becomes increasingly personal. The data is of value to many parties. At a minimum these include the following: 1. the vehicle "owner" * who may need emergency assistance * who may want to look up some historical facts of his travel (distance traveled to a client site that may be reimbursable) * who may want to update the information when he replaces parts or performs maintenance * who may need to prove that he wasn't the driver when the car caused an accident or was used for criminal purposes * erase his personal driving data when the car is sold or junked 1. the mechanic * who may use the information for diagnostic purposes * who may update the information with parts replaced, maintenance performed, or accident information 1. the vehicle lessor (in case the vehicle is leased and not purchased) * who may bill by mileage * who may charge a premium for driving in certain areas (e.g., foreign countries) 1. the insurance company who may charge lower rates for safe driving behavior 2. a prospective second-hand buyer * who want to know both the driving history * the maintenance/repair history * the accident history 1. law enforcement * who may use the information to investigate an accident * who may use the information as evidence of negligent driving * who may use the information to track a vehicle 1. the auto manufacturer * who may use it to detect flaws * who may use it to improve future models 1. wrongdoers * who may use it to track down their victims. * may attempt to falsify the history to avoid insurance liability (e.g., in an accident) * may attempt to falsify the history to improve resale value * may attempt to falsify various information to disguise auto theft. Unlike Ingo's use case which appears only to require uniquely identifying a vehicle, this scenario requires selectively authorizing read and write access to a large amount of personal data by a variety of parties. Use Case #3 Electric refueling at a friend's house As electric cars become more common, the scenario is likely to evolve where Bob drives Carole's electric car to visit Alice. Once at Alice's house, he wants to recharge his vehicle using Alice's electric hookup. But he wants the bill for the electricity used for charging to go to his account, rather than hers. Currently, to do this would likely require having Alice go online to her account to tell the electricity supplier that all electricity going through the car charge for the next three hours should be charged to Bob. And Bob will have to go into his account to authorize the charges coming from Alice's charger. As we migrate towards IoT, it may be possible to make this transaction more automated. One obvious way is to allow the electric hookup to interrogate each car and change any charging to the registered owner of the vehicle. This would solve many problems. But in this case, it would mean that Carole would be charged for Bob's use of the electricity. Another option would be to use the scenario above, but allow for an override function. The system may default to charging Alice, but by entering a command (through some interface which might be a hardware switch), Bob could authenticate and direct the charges to his account or credit card. I don't consider this as interesting as Use Case #2. But it does involve true authentication, not just identification. Thank you. Jeff -- Jeff Stollman stollman.j@gmail.commailto:stollman.j@gmail.com 1 202.683.8699 Truth never triumphs - its opponents just die out. Science advances one funeral at a time. Max Planck
Nice one Jeff, let me add one more facet into your first use case - the chauffeur, who may or may not be a danger to the owner.
The transfer of ownership is also a key area with lot's of issues in there.
I have first hand experience of having to design a system to underpin marketing, selling and servicing very high end vehicles; many of which required armoured plating….; your use case will test the boundaries of the possible.
Cheers
Iain
On 19 Aug 2013, at 14:04, j stollman
Proposed Use Case #2
Sticking with the automobile theme, I am concerned about authorization to access data stored within a vehicles computer systems.
As autos become smarter and more of them have built-in navigation and emergency communications systems, the data accumulating in these systems becomes increasingly personal. The data is of value to many parties. At a minimum these include the following: • the vehicle "owner" • who may need emergency assistance • who may want to look up some historical facts of his travel (distance traveled to a client site that may be reimbursable) • who may want to update the information when he replaces parts or performs maintenance • who may need to prove that he wasn't the driver when the car caused an accident or was used for criminal purposes • erase his personal driving data when the car is sold or junked • the mechanic • who may use the information for diagnostic purposes • who may update the information with parts replaced, maintenance performed, or accident information • the vehicle lessor (in case the vehicle is leased and not purchased) • who may bill by mileage • who may charge a premium for driving in certain areas (e.g., foreign countries) • the insurance company who may charge lower rates for safe driving behavior • a prospective second-hand buyer • who want to know both the driving history • the maintenance/repair history • the accident history • law enforcement • who may use the information to investigate an accident • who may use the information as evidence of negligent driving • who may use the information to track a vehicle • the auto manufacturer • who may use it to detect flaws • who may use it to improve future models • wrongdoers • who may use it to track down their victims. • may attempt to falsify the history to avoid insurance liability (e.g., in an accident) • may attempt to falsify the history to improve resale value • may attempt to falsify various information to disguise auto theft.
Unlike Ingo's use case which appears only to require uniquely identifying a vehicle, this scenario requires selectively authorizing read and write access to a large amount of personal data by a variety of parties.
Use Case #3 Electric refueling at a friend's house
As electric cars become more common, the scenario is likely to evolve where Bob drives Carole's electric car to visit Alice. Once at Alice's house, he wants to recharge his vehicle using Alice's electric hookup. But he wants the bill for the electricity used for charging to go to his account, rather than hers.
Currently, to do this would likely require having Alice go online to her account to tell the electricity supplier that all electricity going through the car charge for the next three hours should be charged to Bob. And Bob will have to go into his account to authorize the charges coming from Alice's charger.
As we migrate towards IoT, it may be possible to make this transaction more automated. One obvious way is to allow the electric hookup to interrogate each car and change any charging to the registered owner of the vehicle. This would solve many problems. But in this case, it would mean that Carole would be charged for Bob's use of the electricity.
Another option would be to use the scenario above, but allow for an override function. The system may default to charging Alice, but by entering a command (through some interface which might be a hardware switch), Bob could authenticate and direct the charges to his account or credit card.
I don't consider this as interesting as Use Case #2. But it does involve true authentication, not just identification.
Thank you.
Jeff
-- Jeff Stollman stollman.j@gmail.com 1 202.683.8699
Truth never triumphs — its opponents just die out. Science advances one funeral at a time. Max Planck _______________________________________________ DG-IDoT mailing list DG-IDoT@kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/dg-idot
Iain Henderson iain@thecustomersvoice.com e-mail: iainhenderson@mac.com blog: www.iainhenderson.info twitter: @iainh1 This email and any attachment contains information which is private and confidential and is intended for the addressee only. If you are not an addressee, you are not authorised to read, copy or use the e-mail or any attachment. If you have received this e-mail in error, please notify the sender by return e-mail and then destroy it. <a href="http://miicard.me/b0F1Jsy5">Identity assured by miiCard : Click to Verify</a>
participants (4)
-
Iain Henderson -
Ingo.Friese＠telekom.de -
j stollman -
Salvatore D'Agostino