- From: Jordan, John CITZ:EX <John.Jordan@gov.bc.ca>
- Date: Thu, 19 Sep 2019 12:24:44 +0000
- To: sethi shivam <sethishivam27@gmail.com>
- CC: "Bill Claxton, Founder & Operations Director of NextID" <williamc@nextid.com>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Devices would likely be authorized using verifiable credentials issued by their owner. DIDs aren’t the right tool for that job. On Sep 19, 2019, at 5:07 AM, sethi shivam <sethishivam27@gmail.com<mailto:sethishivam27@gmail.com>> wrote: Hi Bill , Thanks for quick response. I saw a video under SSi channel that was related to IOT devices . WHere they gave example of how ASUS laptops came under control of the hacker because the public keys were hard coded .and suggested how DID can help in preventing such scenarios. I think our mindset is oriented towards human only. that is my personal opinion . now lets come to the ownership example. Say A corporate account is there which is currently under the control of SHIVAM ,SHIVAM Left job and transfer that ownership to BILL so how will this work .Does shivam needs to use ke rotation to rotate the key pair or just forward the keys to BIll. Because if we check the uport example. they have done something like this publicKey: [ { id: 'did:bdid:0xa036ca2be3d7e406688efbfb9a86c661fb36a3d3#owner', type: 'Ed25519VerificationKey2018', owner: 'did:bdid:0xa036ca2be3d7e406688efbfb9a86c661fb36a3d3', ethereumAddress: '0xbe4acbc70e6c6fbfda6a8b19a5ca4beff909cb69' }, { id: 'did:bdid:0xa036ca2be3d7e406688efbfb9a86c661fb36a3d3#designate-1', type: 'Ed25519VerificationKey2018', owner: 'did:bdid:0xa036ca2be3d7e406688efbfb9a86c661fb36a3d3', ethereumAddress: '0xbccf8ac82a46aa317409bf302686738d7e50d903' } ], Here owner is the very first owner and ethereum address is refereing to current owner. How they are changing key ownership Regards Sethi Shivam On Thu, 19 Sep 2019 at 16:58, Bill Claxton, Founder & Operations Director of NextID <williamc@nextid.com<mailto:williamc@nextid.com>> wrote: Sethi, Technically I suppose a DID may be assigned to a laptop, but you made me go back and read the spec. "In a decentralized identity system, entities (in the sense of discrete identifiable units such as — but not limited to — people, organizations, and things) are free to use any shared root of trust." To me it seems weird that a laptop can be a DID subject, as it is not free to do anything much less share a root of trust. I don't believe DIDs are intended to capture ownership information. Regards, Bill Claxton (williamc@nextid.com<mailto:williamc@nextid.com>) LinkedIn, Facebook, Telegram, Slack, Skype, Twitter or Gmail: wmclaxton SG Voice, Text or Whatsapp: +65-9012-4327 US Voice, Text or Voicemail: +1-415-797-7348 On 9/19/2019 6:45 PM, sethi shivam wrote: I have a query. Suppose I have a laptop with DID "did:laptp:12345" and I sold it to someone. Now ownership changed to my friend.
Received on Thursday, 19 September 2019 12:25:12 UTC