New thoughts for the report: add IAM as a technology
I'm thinking we should add "Identity and access management" as a technology in the report, and then discuss taxonomies a bit within that subsection (and maybe more extensively elsewhere, if they play an extensive role in our recommendations). I have in mind a description of the blockchain technology that differentiates between the (potential) need for identification/authentication/authorization of those who *interact with* it and the use case of putting identity-related information *on* it. (*Jeff S:* If I were to draft V1 of this, would you be willing to review it? I already have some candidate text that's short and hopefully pithy.) And wherever we have a section/subsection that analyzes connections between technologies/techniques, we can perhaps touch on the "self-sovereign identity" solutions that are coming out that use blockchain technology to address user-centric types of identity use cases. If non objections, I can add outline stubs as above so we don't lose the ideas. *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/> *Sydney, London, and Paris!*
Hi Eve, This is a good idea as there is much hype around identity/blockchains right now (same as in early 1990s when there was excitement about PGP public-keys being identities).
I have in mind a description of the blockchain technology that differentiates between the (potential) need for identification/authentication/authorization of those who interact with it and the use case of putting identity-related information on it. (Jeff S: If I were to draft V1 of this, would you be willing to review it? I already have some candidate text that's short and hopefully pithy.)
(1) Identity information required to access a given blockchain (where the Identity info is sourced from outside the blockchain). (2) Reputation-related information "lying around" inside a blockchain. Maybe it's just a set of transaction pubkeys, transaction identifiers, or maybe more, recorded on the "blocks" on a blockchain. (3) Identity information gleaned from smart-contracts sitting at nodes of a blockchain. (4) Identity information (perhaps PII) gleaned from objects (e.g. land titles) that has been hashed and stored on a notary-blockchain. /thomas/ ------------------------------------------ From: dg-bsc-bounces@kantarainitiative.org [mailto:dg-bsc-bounces@kantarainitiative.org] On Behalf Of Eve Maler Sent: Tuesday, July 26, 2016 3:53 PM To: dg-bsc@kantarainitiative.org Subject: [DG-BSC] New thoughts for the report: add IAM as a technology I'm thinking we should add "Identity and access management" as a technology in the report, and then discuss taxonomies a bit within that subsection (and maybe more extensively elsewhere, if they play an extensive role in our recommendations). I have in mind a description of the blockchain technology that differentiates between the (potential) need for identification/authentication/authorization of those who interact with it and the use case of putting identity-related information on it. (Jeff S: If I were to draft V1 of this, would you be willing to review it? I already have some candidate text that's short and hopefully pithy.) And wherever we have a section/subsection that analyzes connections between technologies/techniques, we can perhaps touch on the "self-sovereign identity" solutions that are coming out that use blockchain technology to address user-centric types of identity use cases. If non objections, I can add outline stubs as above so we don't lose the ideas. 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 Sydney, London, and Paris!
participants (2)
-
Eve Maler -
Thomas Hardjono