Last edited · 3 revisions   

 


Secure Data Storage WG Agenda - Thu Oct 1, 2020

Current Spec

Issues

Agenda

1. IPR Reminder

2. Introductions and Re-Introductions

3. Special Guest: Eve Maler presenting UMA User Managed Access 15+ min presentation and then Q&A 

4. Last 15 mins: WG and Spec Naming Discussion!

    * Goal: Finalize names by IIW

    * 3 week process: Week 1) Generate list of names, 

        Week 2) Debating "hard no"s/deal breaker names,

        Week 3) Community ranked-choice voting

    * To start us off: see the last several comments on issue #35

Attendees:

  • Michael Shea
  • Dave Longley
  • Dmitri Zagidulin
  • Robbie Jones
  • Orie Steele
  • Kaliya Young
  • Juan Caballero
  • David Mason
  • Daniel Buchner
  • Andreas Freund
  • Adrian Gropper
  • Dmitri Zagidulin
  • David Mason
  • Manu Sporny
  • Jonathan Holt
  • Benjamin Goering

Exploratory Names

Exploratory properties of good name choices:

* Short

* No collisions

* Should not snark/pun on existing similar solutions (like Solid Pods, for example)

* Should not make people think "This already exists; Google Drive / Dropbox"

  * bengo: e.g. "encrypted"? +1 -- manu

* Should not suggest that this is more secure or decentralized than it really is.

    * bengo: As CCG has discussed, there are many definitions of 'decentralized', and there is usually a better choice of words.

    * bengo: Im new to the spec, but I was under the impression it would be possible to implement SDS in a very traditional/centralized architecture, while also enabling some new ones.

Exploratory properties of names that may not be important:

* globally unique

* resolvable

* works with posix tools for resolving names. A valid name could be 'enrypted.data', `whois encrypted.data`

* name is syntax-compatible with other standards

* decision reached via [Formal Consensus](https://en.wikipedia.org/wiki/Formal_consensus)

  * bengo: I believe it's probably possible to make this decision via [this protocol][1], but not desirable if fielding concerns takes more than x weeks (x=4?). Mitigation: if consensus takes longer than y weeks, group could vote on a resolution to bound the debate to z weeks.

[1]: https://theanarchistlibrary.org/library/c-t-butler-and-amy-rothstein-on-conflict-and-consensus-a-handbook-on-formal-consensus-decisionm "Formal Consensus"

 

Lower-level, storage-focused names:

* Decentralized Encrypted Storage

* Decentralized Encrypted Vault

* Secure Data Vault

* Encrypted Storage Vault

* Vault Data Store

* Decentralized Data Vault

* Decentralized Vault Store

* Secure Data Share

* Encrypted Data Vault

* Secure Resource Server

* Ookie Pookie- 

* Pubsubhubbub hubs (for Michael Shea :D )

* Encrypted fiefdoms

 

All-inclusive, app-focused names:

* Dapp Hub

* App Mesh

* Dapp Mesh

* Decentralize App Hub

* Distributed Data Hub

* Encrypted Data Mesh

* Encrypted Storage Mesh

* User Space

* Encrypted fiefdoms

 

Links

* https://kantarainitiative.org/download/uma-21st-century-health-information-interoperability-user-control

Recording (Zoom)

Transcript (Otter AI)