- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Mon, 18 Nov 2019 09:44:49 -0500
- To: public-credentials@w3.org
On 11/17/19 9:54 PM, Daniel Hardman wrote: > A more insightful contrast would be DIDComm vs. RESTful web services > secured by certificates + user login. Both run over HTTP, and both > are a "whole extra layer over simple HTTP." Huh, interesting. This is a take on DIDComm that I haven't heard before, but then again, I haven't been deeply involved in the DIDComm work. I thought DIDComm was purely a transport agnostic protocol. It could run over HTTP, but I didn't see HTTP as a target transport protocol due to concerns over the existing CA system. I thought the focus was on something more low level than HTTP, something akin to Mutually Authenticated TLS (but using DIDs instead of CAs). In any case, I'm certainly no DIDComm expert and am happy to use whatever contrast you feel will maximize insight. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) Founder/CEO - Digital Bazaar, Inc. blog: Veres One Decentralized Identifier Blockchain Launches https://tinyurl.com/veres-one-launches
Received on Monday, 18 November 2019 14:44:52 UTC