User Tools

Site Tools


groups:identity:identity-wg-potential-substreams

The following are raw notes from a part of the Identity Management Working Group meeting that was held at a session hosted by the DTCC on May 5, 2016 on potential sub-streams within the working group.

I - Commons and Principles

  1. Self-Sovereign Identity
    1. ID 2020 Summit on Digital Identity at United Nations May 20th http://id2020summit.org
    2. #RebootingWebOfTrust Design Workshop after UN Summit May 21st & 22nd http://www.WebOfTrust.info
  2. Ostrom's work - Where tragedy of the commons didn't happen
    1. A Revised “Ostrom’s Design Principles for Collective Governance of the Commons”: http://www.lifewithalacrity.com/2015/11/a-revised-ostroms-design-principles-for-collective-governance-of-the-commons-.html
  3. Taxonomy
    1. What are the different terms of art in the existing communities of practice, and which more accurately represent our vision?
    2. Subject / issuer
    3. Entitlements
    4. Credential / assertion
  4. Boaty mcboatface
  5. Non-repudiation of transaction / event
  6. Onboarding / Bootstraping Process
  7. Life cycle of identity
  8. HLTP - What's most useful leanest

II - Federation - Permission-less, Permissioned or Mix

  1. Layerings
  2. Permissioned networks
  3. Peer question
  4. Additive homomorphic
  5. Boot strapping
  6. Liquid - bitcoin exchanges - very fast transfers among exchanges
  7. Permissioned blockchain
  8. Create keys together for exchanges
  9. No one can cheat for keys in trust zone
  10. Shared key generation
  11. Zcash
  12. Selective encryption
  13. Parameter for a curve
  14. Snhore
  15. Maxwell's tree of ?
  16. Multi-sigs
  17. Voting
  18. Multi-sig versus threshold sigs
  19. Design constraints on federation participant
  20. Abstractions
  21. Paxos
  22. When add or change members
  23. Nature of the consensus mechanism may change
  24. Bootstrapping a permissioned network
  25. Consensus federation changes

III - Fiduciary Code and Signing

  1. Permissions
  2. Approved by
  3. Successful validation
  4. How prove fiduciary met
  5. How prove transparency met
  6. Implementation code failures
  7. How to attest to the hardware
  8. Consensus for integrity of the ledger
  9. VM
  10. Multi-factor authentication
  11. Software-defined networking example vs. juniper networks
  12. Delegation

IV - Failure

  1. Individual key loss
  2. China shuts down great firewall for 3 days
  3. Hierarchical Deterministic Keys
  4. Bitcoin uses 3 of 6 variants
  5. Powerful/mature technology
  6. Audit every child of that key
  7. Master key offline and can be revoked
  8. Hyperledger currently
  9. CA authority generates
  10. To handle auditability for b2b case
  11. Every transaction has unique public key
  12. Social network reboot
  13. Proof of existence
  14. Reboot of identity
  15. Multi-sig network recovery
  16. Consumer with list of friends - backup buddies if I lose my phone
  17. If I lose my Yubi key, 2 people from IT can recovery
  18. Smart contracts level of indirection from crypto identifier and private keys that control the system
  19. Replace/rotate keys without changing identifier
  20. Pluggable element for control of identity
  21. Three days of inactivity then go to recovery procedure
  22. Trusted computational fabric enabled by
  23. Nonrepudiation if can't recreate keys
  24. New key versus re-generating old key
  25. Core ideas for how identities interact then works for use cases (e.g., consumer/retail, business-to-business)

V - Confidentiality, Privacy

  1. Selective disclosure, blinding, uprove, identity mixer, zero-knowledge proofs / homomorphic proofs
  2. Confidential transactions
  3. Front running

VI - Legacy

  • Existing identity systems

VII - Visioning the Future

  • N/A
groups/identity/identity-wg-potential-substreams.txt · Last modified: 2016/11/02 17:41 by Jeremy Sevareid