September 2016 - DG-BSC - mailman.kantarainitiative.org

Notes from special BSC telecon 2016-09-09
by Eve Maler 09 Sep '16

09 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… http://kantarainitiative.org/confluence/display/BSC/Report+from+the+Blockch… Agenda: - Informal report writing Attending: Eve, Andrew, Thomas, Domenico, Luk?, Kathleen Thoughts for the report: If some topics aren't "use cases" because they assume technologies/techniques, could we still include them as "tests" (e.g. real-world case studies that use blockchain)? MedRec is one such case study. That would allow us to include a lot of up-to-the-minute information. Also, we would like to include some thread of blockchain vs. smart contracts. We already have this covered in the report outline. We're thinking that maxing out on the number of use cases and case studies (five each, or even less) will be fine; that will elicit the analysis we need. We could easily analyze up to five actual real projects/pilots/POCs ("case studies") out there; there are so many. The distinction in the name is "theoretical vs. actual". Hmm, we might not want to put a limit on case studies as long as we keep illustrating real technologies/techniques. Let's limit theoretical use cases, though. In which case we've probably hit our limit among those submitted. We'd like to propose that our meetings use a pattern in our meetings of using the half-hour for use case work, and a second half-hour for deep-dive report writing (that is to say, doing this *twice* a week). Next week Eve can't attend due to being awesomely in Barcelona. *Can Thomas run the meetings next week? Please confirm to the list.* Kathleen took an action to flesh out some MedRec case study text for next week. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Re: [DG-BSC] User-Managed Identities for Blockchains (using UMA for user-centric control over blockchain identities)
by Adrian Gropper 08 Sep '16

08 Sep '16

Luk, I understand "persistent pairwise pseudonyms" (PPP, for short) because that's what FIDO seems to do. I don't understand what you mean by adding "/persona" to the mix. Thomas seems to be drawing - in the diagram on his blog - a distinction where multiple PPPs are derived in a hierarchical deterministic way from a single persona. The persona could be a way to link verifiable claims to the PPP but it's not clear to me how that would work or be standardized. I think W3C Verifiable Claims takes a decent shot at that. I also note that no blockchain is involved yet. Adrian On Thursday, September 8, 2016, Luk Vervenne <luk.vervenne(a)synergetics.be> wrote: > My vote is for different but persistent pairwise pseudonyms/persona (so > per service provider / per web service). > I that sense it is a “fully" persistent pairwise *pseudonymisation / > persona* that can dive into the "deep web serivce call chains" needed to > preform an business service. > > luk > > On 8 Sep 2016, at 14:22, Adrian Gropper <agropper(a)healthurl.com > <javascript:_e(%7B%7D,'cvml','agropper(a)healthurl.com');>> wrote: > > Thomas, > > There are many ways to get where we're headed with personas, verifiable > claims, and non-correlatable transaction identifiers and you are > contributing to a valuable conversation. I love that you are bringing UMA > into the conversation because I tend to consider the authorization server > as a key component of identity and tightly coupled to persona. > > Privacy engineering identity can build on standards (and would-be > standards) including: > > - FIDO (for non-correlatable yet persistent identifiers) > - W3C Verifiable Claims (for a triple blind attribute verification > architecture) > - Hierarchical Deterministic keys in blockchain > - Decentralized UMA authorization servers as online agents and > self-sovereign support technology > - TOR and other anonymization protocols for an UMA authorization server > > The more I learn about decentralized ID (in the Rebooting Web of Trust > context) and blockchains, the harder it is to map this work into > traditional standards and governance like OpenID Connect and IDESG. > > The tools for privacy engineering identity are out there but the > governance model that will put them together in a sustainable decentralized > way remains elusive. > > Adrian > > On Thu, Sep 8, 2016 at 8:18 AM, John Moehrke <johnmoehrke(a)gmail.com > <javascript:_e(%7B%7D,'cvml','johnmoehrke(a)gmail.com');>> wrote: > >> Thomas, >> >> That functionality - usecase - is critical to the use-case I presented on >> "Evidence Notebook". In that case the a human may need many identities, for >> the various things he is working on in his virtual notebooks. These >> identities need to be opaque at times, and later exposed for who they >> represent. I explain this in my use-case, but would very much rather it be >> a common building block concept that could be leveraged rather than >> re-explained. >> >> In my case these 'transaction identities' would be used for years before >> being exposed and retired. Is that timeframe acceptable in your use-case? >> The term 'transaction' tends to lead me to very short term use. >> >> John >> >> John Moehrke >> Principal Engineering Architect: Standards - Interoperability, Privacy, >> and Security >> CyberPrivacy – Enabling authorized communications while respecting Privacy >> M +1 920-564-2067 >> JohnMoehrke(a)gmail.com >> <javascript:_e(%7B%7D,'cvml','JohnMoehrke(a)gmail.com');> >> https://www.linkedin.com/in/johnmoehrke >> https://healthcaresecprivacy.blogspot.com >> "Quis custodiet ipsos custodes?" ("Who watches the watchers?") >> >> On Thu, Sep 8, 2016 at 6:18 AM, John Wunderlich <john(a)wunderlich.ca >> <javascript:_e(%7B%7D,'cvml','john(a)wunderlich.ca');>> wrote: >> >>> Thomas; >>> >>> This aligns well with Canadian privacy views of a 'biographical core' >>> and the social reality that we all have many identities that we present to >>> the world. When I read this and note the piece that I just posted about the >>> potential conflict between the GDPR 'right to erasure' and Blockchain, I >>> think you have correctly identified a normative inverse relationship >>> between "Core Identity" attributes what should be written openly to a >>> blockchain. Exciting work. >>> >>> 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 >>> >>> >>> >>> >>> On Thu, Sep 8, 2016 at 12:23 AM -0400, "Thomas Hardjono" < >>> hardjono(a)mit.edu <javascript:_e(%7B%7D,'cvml','hardjono(a)mit.edu');>> >>> wrote: >>> >>> Folks, >>>> >>>> This may or may not be a use-case proper for BSC-DG, but I thought I'd mention it here because its an "infrastructure" technology that supports scaling of blockchains. (analogy: DNS is not part of Internet routing in TCP/IP, but it sure does help us use the Internet). >>>> >>>> One of the key concepts we (at MIT) are trying to develop further in CoreID (diagram is here http://www.findthomas.net/blog/) Part of it is the idea of a new kind of identity provider called the "persona provider" (PP) >>>> >>>> The Persona Provider could be implemented as a combination of an UMA Authorization Server combined with an UMA Resource Server. (PP = AS + RS). >>>> >>>> When Alice creates an account at the Persona Provider (PP), she convinces the PP initially that she is legit by supplying the PP with signed assertions (blinded assertion) which the Core Identity Issuer (upstream) has created. >>>> >>>> When Alice needs to transact on the blockchain using an anonymous-verifiable identity, she goes to her account at the PP and self-generates a transaction-identity (transaction-identifier) to be used on the blockchain or within a smart contract. She can self-generate as many transaction-identifiers as she needs -- no limit. The PP provides the crypto-tools to do this (just like bitcoin-wallets / client softwares or PGP). >>>> >>>> At the same time, she could optionally set policy on the account, treating the the blinded assertions (from the Core Identity Issuer) as resources. The transaction identities (which are anonymous-verifiable strings) can also be treated as resources sitting on the PP. >>>> >>>> The PP keeps these transaction-identifiers as long as she needs, and may even archive them. >>>> >>>> The PP also makes available a Identity Verification end-point (API) that allows the counter-party (RP) -- or anyone for that matter -- to verify a transaction-identifier found on a blockchain or in a smart-contract. >>>> >>>> >>>> If this is useful, I can write it up for the use-cases page. >>>> >>>> /thomas/ >>>> _______________________________________________ >>>> DG-BSC mailing listDG-BSC(a)kantarainitiative.org <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');>http://kantarainitiative.org/mailman/listinfo/dg-bsc >>>> >>>> >>> >>> 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. >>> >>> _______________________________________________ >>> DG-BSC mailing list >>> DG-BSC(a)kantarainitiative.org >>> <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');> >>> http://kantarainitiative.org/mailman/listinfo/dg-bsc >>> >>> >> >> _______________________________________________ >> DG-BSC mailing list >> DG-BSC(a)kantarainitiative.org >> <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');> >> http://kantarainitiative.org/mailman/listinfo/dg-bsc >> >> > > > -- > > Adrian Gropper MD > > PROTECT YOUR FUTURE - RESTORE Health Privacy! > HELP us fight for the right to control personal health data. > DONATE: http://patientprivacyrights.org/donate-2/ > _______________________________________________ > DG-BSC mailing list > DG-BSC(a)kantarainitiative.org > <javascript:_e(%7B%7D,'cvml','DG-BSC(a)kantarainitiative.org');> > http://kantarainitiative.org/mailman/listinfo/dg-bsc > > > -- Adrian Gropper MD PROTECT YOUR FUTURE - RESTORE Health Privacy! HELP us fight for the right to control personal health data. DONATE: http://patientprivacyrights.org/donate-2/

1 0

Re: [DG-BSC] Blockchain Technologies and EU 'right to be forgot...
by John Wunderlich 08 Sep '16

08 Sep '16

Luk; The FYI was a flag that I was passing it on for information, not endorsing. That being said, and to your point, transaction audit logs may not be OK if the logs themselves reveal or contain personal information. It is often the case that privacy issues arise with edge cases. Most of the time, for most users, in most circumstances a system will be OK and the edge case will not arise. Developers, especially at startups or with new products, therefore leave edge cases for downstream fixes and consciously accept privacy and security risk to get to version 1.0 release and start generating cash flow. When this logic is applied to blockchain developments you end up with unrecoverable errors. 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 _____________________________ From: Luk Vervenne <luk.vervenne(a)synergetics.be> Sent: Thursday, September 8, 2016 7:13 AM Subject: Re: [DG-BSC] Blockchain Technologies and EU 'right to be forgot... To: John Wunderlich <john(a)wunderlich.ca> Cc: <dg-bsc(a)kantarainitiative.org> John, No so fast. Storing personal data with a right to be forgotten policy at hand, might not be.But transaction audit summary logs in blockchain within an ecosystem are ok luk On 8 Sep 2016, at 13:06, John Wunderlich <john(a)wunderlich.ca> wrote: FYI http://www.ibtimes.co.uk/blockchain-technologies-eu-right-be-forgotten-insu… 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._______________________________________________ DG-BSC mailing list DG-BSC(a)kantarainitiative.org http://kantarainitiative.org/mailman/listinfo/dg-bsc -- 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

Blockchain Technologies and EU 'right to be forgot...
by John Wunderlich 08 Sep '16

08 Sep '16

FYI http://www.ibtimes.co.uk/blockchain-technologies-eu-right-be-forgotten-insu… 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

No call Thursday; editorial call Friday
by Eve Maler 07 Sep '16

07 Sep '16

A reminder that we're not meeting on Thursday (tomorrow). However, the core team interested to work on a key report section has identified Friday 11am PT/2pm ET/7pm UK/8pm CET as a 60-minute slot during which we can make progress; others are welcome to join if they remember and stick to our meeting goal. ;-) Dial-in details are the same as usual and are on the BSC calendar: http://kantarainitiative.org/confluence/display/BSC/Calendar Eve (sent from my iPhone, possibly with Siri's "help": +1-425-345-6756)

1 0

Notes from BSC telecon Tuesday, September 6 (NOTE: no meeting this Thursday)
by Eve Maler 06 Sep '16

06 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Pick a time for an ad hoc report working session - Work on use cases on the call (finally!) Attending: Eve, Kathleen, Jeff S, Adam M, John M, Scott S, Domenico, Adrian, Jim, John W *NOTE:* No BSC telecon this Thursday because we couldn't find a chair pro tem. Eve, Thomas, Kathleen, and Scott D had expressed particular interest in an editing session. We'll work out a time for that and advertise the time. (John W and Domenico have some interest.) Regarding the Stellar Consensus Protocol-involving use case: John W notes: "Disclaimer re: Stellar Consensus Protocol. I work with JLINC Labs which uses the Stellar blockchain for our open source JLINC protocol." John M describes his new "Evidence Notebook" use case <https://healthcaresecprivacy.blogspot.com/2016/08/blockchain-and-smart-cont…>: It's trying to achieve what Jim describes as proof-of-existence in a way that can be private at first. He provides three variations, e.g. to provide signatures. Community peers could even provide counter-signatures even if they can't see the content. He's prepared for lots of discussion over all of this. Adrian ties these ideas to his for doctors signing patient-centric prescriptions, noting that no smart contract is needed in his scenario; for John's use case, the signature is independent and doesn't need smart contracts while the escrow does. Observing commonalities in use cases: John W sees that there are attributes (facts??) that are frozen and verifiable. In the identity space, these might be identity attributes. *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Agenda for BSC telecon 2016-08-06
by Eve Maler 06 Sep '16

06 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… We meet *Tuesdays* for 30 minutes at 7:30am PT / 10:30am ET / 3:30pm UK / 4:30pm CET. We use Kantara Line A (US +1-805-309-2350, Skype +99051000000481, international options <https://www.turbobridge.com/international.html>, web interface <https://panel.turbobridge.com/webcall/>, more info <https://www.turbobridge.com/join.html>, code 4022737) and http://join.me/findthomas for screen sharing. See the DG calendar <http://kantarainitiative.org/confluence/display/BSC/Calendar> for our full meeting schedule. Previous meeting minutes are here: July <http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29…>, August <http://kantarainitiative.org/confluence/display/BSC/2016-08+%28August+2016%…> . Agenda: - Pick a time for an ad hoc report working session - Work on use cases on the call (finally!) *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

2 1

From John Moehrke
by John Wunderlich 01 Sep '16

01 Sep '16

John got this bounced on the list, so I'm posting on his behalf: ---- I have a potential new use of Blockchain and Smart-Contracts. I have written it up using the template, but don't yet have rights on the Kantara system. I have published what I have developed with a friend of mine (Health Informaticist and Researcher) onto my Blog. I am happy to submit it fully to the Kantara DG-BSC efforts if the community is interested. The use-case is Evidence Notebooks (aka Lab Notebooks, or Patent Notebooks). https://healthcaresecprivacy.blogspot.com/2016/08/blockchain -and-smart-contracts-applied.html John Moehrke ---- Sincerely, John Wunderlich @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.

2 1

Notes from BSC telecon Thursday, September 1
by Eve Maler 01 Sep '16

01 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… Agenda: - Working session on report text to capture sentiment around "central tension" (vs. cooperative "outlet") and action items for fleshing it out - Could result in text in use case(s) and technology/technique description/analysis too Attending: Eve, Thomas, Matisse, Jim, John W, Adrian, Scott D, Kathleen We'd really like to delve into all the use cases being contributed. But it seems we need to deal with this elephant in the room; then we can make quicker progress on the use cases and the technologies/techniques! How to address the tensions and mitigations in our deliverables? There's a kind of recursion we can see in how reliability of interactions is increased (Scott D's traffic lights example). Or is it commoditization? Race to the top? Standardization? All of the above? Almost any use case could do, he thinks, as long as they capture the same pattern. Merkel turtles! Scott suggests that channel integrity be applied along with reliability here. Financial products are commoditized though intangible. A blockchain is a time machine. Jim adds: Each event is a record, linking to the prior state and to any code or prose needed to execute or understand. John asks: Is model-view-controller an apt design pattern to apply here? Jim notes: parameters-prose-code seems awfully close. Applying security and privacy, Kathleen adds the concept of dynamism. Capturing someone's consent requires capturing their parameters. The forthcoming paper on computational sovereignty is about "Who do you put in the 'turtle' position?" (Turtles all the way down...) Identity comes in because you need to test "halt, who goes there" and "state your business" (authentication and authorization) and your purpose of use. But then you're right back to the "poison of centralization"! PKI, DNS, third-party asserted identity, IdPs, cross-domain SSO, and all the rest. Unless you're doing "decentralization" in a single-domain sandbox, which is less interesting (discussed on Tuesday), or doing ZKP tricks that are (Eve's position) too technically tricky and expensive for users' desires, IAM today is a centralization play. Can we call it the "drug of centralization" instead, to be more philosophically neutral? Yes. Or even the "siren song". Who's interested to put together the awesome 1-2 page summary of this? Eve, Thomas, Kathleen, Scott D. Scott D points to Cope's Rule <https://en.wikipedia.org/wiki/Cope%27s_rule> in biology as gainsaying Eve's belief that decentralization as inherently unstable in most circumstances. Scott: Rule-making, operations, and enforcement can be separated so that not all need to be centralization. (Also see the network effect <https://en.wikipedia.org/wiki/Network_effect>.) Eve's version says that "No committee ever recommends its own demise." This is why she hopes that we stick to our six-month plan! Can we find a chair pro tem for next Thursday? *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0

Agenda for BSC telecon Tuesday, September 1
by Eve Maler 01 Sep '16

01 Sep '16

http://kantarainitiative.org/confluence/display/BSC/2016-09+%28September+20… We meet *Thursdays* for 30 minutes at 11am PT / 2pm ET / 7pm UK / 8pm CET. We use Kantara Line A (US +1-805-309-2350, Skype +99051000000481, international options <https://www.turbobridge.com/international.html>, web interface <https://panel.turbobridge.com/webcall/>, more info <https://www.turbobridge.com/join.html>, code 4022737) and http://join.me/findthomas for screen sharing. See the DG calendar <http://kantarainitiative.org/confluence/display/BSC/Calendar> for our full meeting schedule. Previous meeting minutes are here: July <http://kantarainitiative.org/confluence/display/BSC/2016-07+%28July+2016%29…>, August <http://kantarainitiative.org/confluence/display/BSC/2016-08+%28August+2016%…> . Agenda: - Working session on report text to capture sentiment around "central tension" (vs. cooperative "outlet") and action items for fleshing it out - Could result in text in use case(s) and technology/technique description/analysis too *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging Technology Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl *ForgeRock Summits and UnSummits* are coming to <http://summits.forgerock.com/> *London and Paris!*

1 0