- DG-BSC - mailman.kantarainitiative.org

Fwd: Questionnaire for the Sovrin Foundation for the BSC report
by Eve Maler 25 Oct '16

25 Oct '16

Hi folks-- Following is the material I was supplied by the Sovrin Foundation folks in answer to the questionnaire. Hopefully we can use this as a discussion topic on the next call (unless there's a more pressing set of material ahead of it). *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *The ForgeRock Identity Summit* is coming to <http://summits.forgerock.com/> *Paris in November!* ---------- Forwarded message ---------- From: Eve Maler <eve.maler(a)forgerock.com> Date: Sun, Oct 23, 2016 at 4:42 PM Subject: Re: Questionnaire for the Sovrin Foundation for the BSC report To: Phil Windley <phil(a)windley.org> Belated ack/thanks for this! I'm going to send it to our DG for question and comment as we work through it. What we publish may be a combination of quoted sections, paraphrases, commentary, and so on, and since we do our work in the open anyway, of course we'll invite and welcome comment back on the draft. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *The ForgeRock Identity Summit* is coming to <http://summits.forgerock.com/> *Paris in November!* On Fri, Oct 14, 2016 at 8:30 AM, Phil Windley <phil(a)windley.org> wrote: > Here’s some answers to the questionnaire. Let me know if something doesn’t > make sense or needs more explanation. > > *Deficits and benefits of how the problem space was/is being solved* > > The Internet was built without a standard, explicit way of identifying > people or organisations. So websites simply began offering their own local > accounts with usernames and passwords, and this has been the predominant > solution ever since. > > But the Internet has expanded hugely, and people use more and more > services daily. This silo-based approach, where users must maintain > identities for every site they interact with, has become untenable. It is > not just a usability disaster for individuals, it also creates a multitude > of data honeypots for hackers—the breach of which compromises trust in all > Internet services. > > To solve this problem we have tried to connect different identity silos > together in various federated models. However these have produced > inadvertent side effects such as concentrating control around a small > number of providers, correlation of personal data through multiple > seemingly unrelated transactions, increasing data leakage through > inadvertent sharing, and raising privacy concerns, all while not actually > giving the individual real control. At the same time, there is a growing > economic inefficiency when organisations all around the world have to > collect, store and protect the same sort of personal data in their own > silos. It is reaching a tipping point. > > The next evolution of the Internet will be the creation of a common > identity layer that allows people, organisations and things to have their > own self-sovereign identity—a digital identity they own and control, and > which cannot be taken away from them. Self-sovereign identity is the > natural evolution of an ecosystem which has moved faster than its > supporting capabilities. > > *Proposed benefits of the new solution space* > > To create the long-missing identity layer of the Internet, a new, trusted > infrastructure is required which enables identity owners to share not only > identity, but also verified attributes about people, organizations and > things, with full permission and consent. > > For identities to be truly self-sovereign, this infrastructure needs to > reside in an environment of diffuse trust, not belonging to or controlled > by any single organisation or even a small group of organisations. Nobody > can “turn the lights out”. Distributed ledger technology (DLT) is the > breakthrough that makes this possible. It enables multiple institutions, > organisations and governments to work together for the first time by > forming a decentralised network much like the Internet itself, where data > is replicated in multiple locations to be resistant to faults and tampering. > > When combined with distributed key management and peer-to-peer sharing of > encrypted claims, DLT is what finally makes self-sovereign identity > possible. Within this identity layer, mechanisms for discovery, routing of > requests, secure exchange of information and management of consent, under > the full control of the identity owner, finally becomes possible. > > The Sovrin Identity Network has been design specifically to deliver a > globally scalable self-sovereign identity solution. But to be truly > self-sovereign, it cannot be owned by anyone. Similarly, to be fully > trusted, and to avoid the pitfalls of other initiatives in the distributed > ledger space, Sovrin needs a lightweight governance layer. To achieve this, > the developers of Sovrin have given away the source code to the Sovrin > Foundation, a not-for-profit organisation whose role is to provide a thin > layer of governance to Sovrin while not owning or managing any > infrastructure. The Sovrin Foundation ensures the effective distribution of > the decentralised network and ensures that the network itself functions in > the best interest of its users. > > *Different approaches being taken in the new solution space, e.g. if other > approaches are being taken outside of Sovrin* > > Early examples of identity solutions using distributed ledger technology > used ledgers built for other purposes such as the Bitcoin ledger, or > general purpose ledgers such as Ethereum. While these capabilities are able > to provide fairly simple proofs that something took place on a certain date > & time, they are not dedicated to the particular nuances of the identity > ecosystem such as non-correlation, revocation and anonymous zero-knowledge > proofs. > > They also lack governance. For example, the need to secure the network by > using hashing power has resulted in a concentration of Bitcoin mining in > China. Who are these miners, do we trust them, do they jointly exert too > much influence. What governance is in place? The recent forking of Ethereum > has also shown the consequences of a lack of governance and direction. > > Sovrin is the first public-permissioned distributed ledger. It is publicly > accessible by anyone, but in order to run one of the nodes which validates > the integrity of the network, you need to be permitted to and you must > abide by certain rules which include the Sovrin Trust Framework. > > Non-distributed ledger solutions are attempting to paper over the problems > with silo-based identity. Examples are federated identity models such as > the gov.ukVerify system, which uses attribute sharing hubs and identity > providers to move information from one silo to another, but without giving > the identity owner real control. Personal information management solutions > are going a step further, in enabling identity owner control of their data, > but are still somewhat lacking in portability and therefore remain as silos. > > *Strengths, weaknesses, risks, and open issues being seen in practice* > > The ability for an identity owner to assert multiple verifiable claims > about their identity, anonymously if required, and without possibility of > correlation, is central to the architecture of Sovrin. With discovery > capabilities to ensure that party A can confirm the identity of party B, > and vice versa, direct party-to-party data sharing can take place with no > need for intermediaries and with full evidence of consent. > > By replacing intermediaries with protocols, immediate digital identity > verification can take place with no 3rd party involvement. There are too > many benefits to list, bur here are a few that we are working on: instant > employment screening; frictionless bank KYC, identity for the stateless, > fast online checkout, globally portable digital identity for travellers, > and vaccination recording for developing countries. > > Challenges to adoption of Sovrin are those typical of a two-sided market. > Both identity issuers and relying parties need to come on board. Sovrin > partners are taking a simple approach to this – the initial partners will > be both issuers and relying parties. They will provide new identity > services for their users to be utilised within their own ecosystem. These > islands of functionality will expand and intersect with other islands, and > individuals will find that they can use their identity information from one > issuer with a completely different relying party. In other cases, > coalitions of organisations which are all trying to solve the same problem > are coming together to create an ecosystem where they can all use Sovrin to > their mutual benefit. > > The other major challenge is an educational one. Trying to explain > self-sovereign identity to a layman is difficult. Because people have been > brought up to understand that the only way the internet works is to give > their details to many different organisations repeatedly, they cannot > conceive of a better way. Being able to get across the power of every > individual having their own digital identity which they control and own and > which cannot be taken away, is a new concept which needs to be communicated > effectively. > > *Whether other technologies and techniques are being brought to bear (you > can see a list of technologies and techniques we are analyzing in > our report > <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> TOC)* > > Sovrin enables/uses the following > - Public-permissioned distributed ledger technology based on the > Plenum Consensus Protocol, involving multiple specialised legers (identity > ledger, config ledger etc) > - Verifiable claims > - Anonymous credentials > - Revocation, anonymous if required > - Distributed and cryptographic identifiers > - Link contracts & consent receipting > - Persistent P2P messaging endpoints > - Key discovery, management recovery & rotation > - Portable off-ledger private data storage e.g. IPFS/BigChainDB > etc. > - Identity, relationship and reputation graphs > - 3rd party attested and self-attested claims > > > On Oct 11, 2016, at 9:41 AM, Eve Maler <eve.maler(a)forgerock.com> wrote: > > Hi Phil-- Thanks for being willing to help the Blockchain and Smart > Contracts group understand what Sovrin is doing in the context of our > analysis efforts! > > If you look at the first paragraph of our draft report's introduction > <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…>, > you'll see a statement of our scope: > > - Solving use cases for *empowering traditionally disempowered parties* > (such as individuals) > - taking part in *transactions* (such as entering into contracts and > information-sharing agreements) > - with *parties that traditionally hold greater power* (such as > companies and large countries) > - in the context of *decentralization technologies and techniques* > (such as blockchain and smart contracts) > - and their mixture with *identity* (both in the course of conducting > business/legal transactions and to solve digital identity use cases). > > Our Discussion Group is time-boxed to six months, and so we plan to go > into only as much depth as can be covered in this time frame. (We started > in July!) > > With all of this in mind, could you please comment on the following > aspects of Sovin? > > - Deficits and benefits of how the problem space was/is being solved > - Proposed benefits of the new solution space > - Different approaches being taken in the new solution space, e.g. if > other approaches are being taken outside of Sovrin > - Strengths, weaknesses, risks, and open issues being seen in practice > - Whether other technologies and techniques are being brought to bear > (you can see a list of technologies and techniques we are analyzing in our > report > <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> > TOC) > > Many thanks! If you have any questions, or would like to discuss responses > in a phone call, don't hesitate to let me know. > > > *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging > Technology > Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl > *ForgeRock Summits* are coming to <http://summits.forgerock.com/> *London > and Paris!* > > >

2 2

Meeting only on Tuesday Oct 25 during this week
by Eve Maler 23 Oct '16

23 Oct '16

Hi folks-- I'm sorry about any confusion around meeting times during my lengthy absence. Thomas and I have coordinated for this new week, and we're both available on Tuesday and not available on Thursday, so we've decided the best thing to do is *meeting for an hour on Tuesday Oct 25 only* (asking Kantara staff by bcc to please remove the calendar entry for the 27th). I've just sent the Sovrin questionnaire answers to the list, so that's one possible agenda item, and I saw that Jim sent his answers (possibly already discussed?). I'm still tardy on my UMA section content, but at least we won't be hung up for discussion topics. Thanks again for your forbearance. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *The ForgeRock Identity Summit* is coming to <http://summits.forgerock.com/> *Paris in November!*

1 0

Another indicator of peak blockchain
by John Wunderlich 20 Oct '16

20 Oct '16

The title alone is sufficient: Walmart and IBM Are Partnering to Put Chinese Pork on a Blockchain <http://fortune.com/2016/10/19/walmart-ibm-blockchain-china-pork/> Sincerely, John Wunderlich @PrivacyCDN <https://twitter.com/PrivacyCDN> Call: +1 (647) 669-4749 eMail: john(a)wunderlich.ca -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

NIST / ONC workshop on blockchain in healthcare
by Scott Shorter 14 Oct '16

14 Oct '16

Hi all, Here is the agenda with links to the presentation, from the NIST/ONC workshop on blockchain in healthcare. As Ross mentioned Drummon Reed gave a good presentation on decentralized identity. https://oncprojectracking.healthit.gov/wiki/display/TechLabI/Use+of+Blockch… Regards, Scott

1 1

Kathleen's report text
by Scott Shorter 13 Oct '16

13 Oct '16

Hi all, I just reviewed the notes from today’s call and I noticed that Kathleen sent some text to Eve and myself for review - I have not received that so please resend. I don’t have Kathleen’s email so I’m sending to the list generally. Thanks! - Scott

1 0

Thursday call
by Scott Shorter 13 Oct '16

13 Oct '16

Apologies folks but I need to take care of a family medical issue and will be unable to chair the call today. - Scott

2 1

Draft template to use for case study participants
by Eve Maler 11 Oct '16

11 Oct '16

I just sent this to Phil W. for Sovrin. Here is a generic version for others assigned to case studies to use, if they like... ==== Hi [*name*]-- Thanks for being willing to help the Blockchain and Smart Contracts group understand what [*name of group/effort/company*] is doing in the context of our analysis efforts! If you look at the first paragraph of our draft report's introduction <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…>, you'll see a statement of our scope: - Solving use cases for *empowering traditionally disempowered parties* (such as individuals) - taking part in *transactions* (such as entering into contracts and information-sharing agreements) - with *parties that traditionally hold greater power* (such as companies and large countries) - in the context of *decentralization technologies and techniques* (such as blockchain and smart contracts) - and their mixture with *identity* (both in the course of conducting business/legal transactions and to solve digital identity use cases). Our Discussion Group is time-boxed to six months, and so we plan to go into only as much depth as can be covered in this time frame. (We started in July!) With all of this in mind, could you please comment on the following aspects of [*name of group/effort/company*]? - Deficits and benefits of how the problem space was/is being solved - Proposed benefits of the new solution space - Different approaches being taken in the new solution space, e.g. if other approaches are being taken outside of [*name of group/effort/company*] - Strengths, weaknesses, risks, and open issues being seen in practice - Whether other technologies and techniques are being brought to bear (you can see a list of technologies and techniques we are analyzing in our report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> TOC) Many thanks! If you have any questions, or would like to discuss responses in a phone call, don't hesitate to let me know. ==== *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits* are coming to <http://summits.forgerock.com/> *London and Paris!*

2 1

Please read and respond ASAP if you're mentioned: Meetings and section assignments this week, and how to fill in sections
by Eve Maler 10 Oct '16

10 Oct '16

Both Thomas and I are *unable to attend/run* the meetings this week. We have a couple of options: a) If there is new section content to review, we could seek a chair pro tem (*Scott S?*) for that purpose, or b) if there isn't, we probably shouldn't meet. The current assignments are as follows. You can find most of them in the Report <http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch…> itself. *Can people please speak up TODAY about when they can complete first drafts*, and we'll make a judgment call ASAP about tomorrow's call? - IPFS: *Thomas* - Certificate Transparency: *Scott S* (already some content there) - CommonAccord: *Jim H* - Protocol-Specific Contract Provisions: - *Kathleen* for HL7 piece - *Eve* for UMA model text piece - Legal contracts: *Scott D* - Digital Identity: *Andrew* - UMA: *Eve* - Consent Receipts: *John W* - User-Submitted Terms: *John W* or designee - Case Study: MedRec: *Kathleen* - Case Study: Blood Diamond: *Matisse+Scott S* - Case Study: Sovrin: *Eve* For case studies, we said we'd use a questionnaire approach something like this: - Deficits and benefits of how the problem space was/is being solved - Proposed benefits of the new solution space – crystalize this (e.g., fraud, not "user empowerment"?) - Different approaches being taken (e.g., whitelist? blacklist? other?) in the new solution space - Strengths, weaknesses, risks, and open issues being seen in practice - Cross-references to the appropriate other technology, case study, and use case sections - Since our Report process is time-boxed, go into only as much depth as you can in a short period of time For *use cases*, we already have a template <http://kantarainitiative.org/confluence/display/BSC/Use+Case+Template> in use; I feel it may benefit from *enhancement* with points from the above. For *technology/technique sections*, we said we'd like to see this information: - A definition - A short discussion of strengths and weakness of the current way of doing things - A short comparative discussion of strengths and weakness of the new way of doing things (if the technology/technique is "new") - Pointers to the other technology and technique sections as appropriate (so that we have cross-references among the sections) *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits* are coming to <http://summits.forgerock.com/> *London and Paris!*

3 4

IIW and this DG (please respond by Friday morning!)
by Eve Maler 07 Oct '16

07 Oct '16

Hi folks-- If you are thinking of attending IIW and don't have your ticket yet: I've just been speaking to Phil Windley, and he was really interested to learn of our work. *He's able to offer us a special discount registration code for use by TOMORROW if you act quickly and let me know of your interest by tomorrow morning.* Also, since the Sovrin Foundation (which he writes about in detail on his blog <http://www.windley.com>) has a "self-sovereign (no IdP) identity using distributed ledger" approach, I suggested that we try out our case study questionnaire technique on him, and he's totally game to respond. I will take that action item when we have a draft questionnaire. :-) *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits* are coming to <http://summits.forgerock.com/> *London and Paris!*

3 3

FYI: Blockchain Healthcare 2016 Report
by John Wunderlich 06 Oct '16

06 Oct '16

FYI https://tierion.com/blog/blockchain-healthcare-2016-report/ John Wunderlich, Sent frum a mobile device, Pleez 4give speling erurz "...a world of near-total surveillance and endless record-keeping is likely to be one with less liberty, less experimentation, and certainly far less joy..." A. Michael Froomkin -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0