Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021


Dmitri Zagidulin
 

Dear all,

This is a reminder that the DIF / CCG Secure Data Storage Working group weekly call will be happening on Thursday at 4pm Eastern / 1pm Pacific / 22:00 CEST.

Meeting link: https://us02web.zoom.us/j/84828031746?pwd=V0xGTnJ2Zm15RHlSRFpNTlRPQzdLUT09

Specification: https://identity.foundation/confidential-storage/
Specification repository: https://github.com/decentralized-identity/confidential-storage

Audio recordings and transcripts of previous meetings: https://dif.groups.io/g/sds-wg/wiki/19633

As always, the IPR policy requires that you can only make substantive contributions if you sign the IPR Release Form. Please follow the instructions at https://dif.groups.io/g/sds-wg/wiki/Home

Confidential Storage Spec Call Agenda
1. IPR Reminder
2. Introductions and Re-Introductions
3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion.
PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ
4. Issue review

Thank you,
The Chairs


Michael Herman (Trusted Digital Web)
 

I know this is going to sound repetitive but … at the top of Daniel’s document, can someone add a couple of sentences distinguishing EDVs and Hub?

 

More specifically, based on last week’s discussion, I sense that the EDV/Hub discussion was more about:

  1. what belonged in the EDV/CS Core/”EDV Microkernel” as a (version 1) capability (e.g. Change Detection/Change Notifications) vs.
  2. what was part of a higher level service (e.g. indexing, replication, etc.)?

 

Does this distinction reflect what was at the heart of last week’s discussion (and this week’s)?

 

Rest regards,

Michael Herman

 

From: sds-wg@... <sds-wg@...> On Behalf Of Dmitri Zagidulin
Sent: February 18, 2021 11:02 AM
To: sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Dear all,


This is a reminder that the DIF / CCG Secure Data Storage Working group weekly call will be happening on Thursday at 4pm Eastern / 1pm Pacific / 22:00 CEST.

Meeting link: https://us02web.zoom.us/j/84828031746?pwd=V0xGTnJ2Zm15RHlSRFpNTlRPQzdLUT09

Specification: https://identity.foundation/confidential-storage/
Specification repository: https://github.com/decentralized-identity/confidential-storage

Audio recordings and transcripts of previous meetings: https://dif.groups.io/g/sds-wg/wiki/19633

As always, the IPR policy requires that you can only make substantive contributions if you sign the IPR Release Form. Please follow the instructions at https://dif.groups.io/g/sds-wg/wiki/Home

Confidential Storage Spec Call Agenda

1. IPR Reminder
2. Introductions and Re-Introductions

3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion.

PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

4. Issue review

 

Thank you,

The Chairs


Michael Herman (Trusted Digital Web)
 

RE: 3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion. PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

 

p.s. …that is, visually, how is support for each of Daniel's use cases partitioned between CS Services and CS Core (see below)? 

…and of these, which should be supported in CS Core version 1? …and which should go into the CS Backlog?

 

 

 

Best regards,

Michael Herman

Sovrin Foundation Self-Sovereignist

 

Self-Sovereign Blockchain Architect

Trusted Digital Web

Hyperonomy Digital Identity Lab

Parallelspace Corporation

 

 

 

 

 

From: Michael Herman (Trusted Digital Web)
Sent: February 18, 2021 11:58 AM
To: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: RE: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

I know this is going to sound repetitive but … at the top of Daniel’s document, can someone add a couple of sentences distinguishing EDVs and Hub?

 

More specifically, based on last week’s discussion, I sense that the EDV/Hub discussion was more about:

  1. what belonged in the EDV/CS Core/”EDV Microkernel” as a (version 1) capability (e.g. Change Detection/Change Notifications) vs.
  2. what was part of a higher level service (e.g. indexing, replication, etc.)?

 

Does this distinction reflect what was at the heart of last week’s discussion (and this week’s)?

 

Rest regards,

Michael Herman

 

From: sds-wg@... <sds-wg@...> On Behalf Of Dmitri Zagidulin
Sent: February 18, 2021 11:02 AM
To: sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Dear all,


This is a reminder that the DIF / CCG Secure Data Storage Working group weekly call will be happening on Thursday at 4pm Eastern / 1pm Pacific / 22:00 CEST.

Meeting link: https://us02web.zoom.us/j/84828031746?pwd=V0xGTnJ2Zm15RHlSRFpNTlRPQzdLUT09

Specification: https://identity.foundation/confidential-storage/
Specification repository: https://github.com/decentralized-identity/confidential-storage

Audio recordings and transcripts of previous meetings: https://dif.groups.io/g/sds-wg/wiki/19633

As always, the IPR policy requires that you can only make substantive contributions if you sign the IPR Release Form. Please follow the instructions at https://dif.groups.io/g/sds-wg/wiki/Home

Confidential Storage Spec Call Agenda

1. IPR Reminder
2. Introductions and Re-Introductions

3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion.

PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

4. Issue review

 

Thank you,

The Chairs


Michael Herman (Trusted Digital Web)
 

RE: the EDV spec defines a fully standalone HTTP server with support for authorization, delegation, and replication over HTTP with DIDs...

 

Thank you, Orie, and, in general, I totally agree.

 

But I’m also suggesting the CS specification should go further and define an EDV MIcrokerel layer and interface to make EDVs deployable on local devices like iOS and Android apps.  An HTTP interface isn’t very useful in these scenarios.

 

Also from a security audit and code path traceability perspective, a microkernel architecture and interface will be more secure/securable.

 

Lastly, what is used to implement the EDV HTTP Server? …what underpins the implementation of the HTTP Serice? …how does it take into account different EDV data vaults mounted on the EDV Server?

 

Michael

 

From: Orie Steele <orie@...>
Sent: February 18, 2021 1:13 PM
To: Michael Herman (Trusted Digital Web) <mwherman@...>
Cc: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: Re: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Layer A - EDVs currently assumes ZCAP over HTTP authorization, and can stand alone.... we don't need an authorization server, we have DIDs and capabilities.

Now you can layer other stuff on top, to integrate with legacy systems, but technically, the EDV spec defines a fully standalone HTTP server with support for authorization, delegation and replication over http with DIDs... it's currently checked in to the repo, and I am happy to give another demo of it...

I think Layer B accurately captures the Hubs dream :)

OS

 

On Thu, Feb 18, 2021 at 1:28 PM Michael Herman (Trusted Digital Web) <mwherman@...> wrote:

RE: 3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion. PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

 

p.s. …that is, visually, how is support for each of Daniel's use cases partitioned between CS Services and CS Core (see below)? 

…and of these, which should be supported in CS Core version 1? …and which should go into the CS Backlog?

 

 

 

Best regards,

Michael Herman

Sovrin Foundation Self-Sovereignist

 

Self-Sovereign Blockchain Architect

Trusted Digital Web

Hyperonomy Digital Identity Lab

Parallelspace Corporation

 

 

 

 

 

From: Michael Herman (Trusted Digital Web)
Sent: February 18, 2021 11:58 AM
To: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: RE: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

I know this is going to sound repetitive but … at the top of Daniel’s document, can someone add a couple of sentences distinguishing EDVs and Hub?

 

More specifically, based on last week’s discussion, I sense that the EDV/Hub discussion was more about:

  1. what belonged in the EDV/CS Core/”EDV Microkernel” as a (version 1) capability (e.g. Change Detection/Change Notifications) vs.
  2. what was part of a higher level service (e.g. indexing, replication, etc.)?

 

Does this distinction reflect what was at the heart of last week’s discussion (and this week’s)?

 

Rest regards,

Michael Herman

 

From: sds-wg@... <sds-wg@...> On Behalf Of Dmitri Zagidulin
Sent: February 18, 2021 11:02 AM
To: sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Dear all,


This is a reminder that the DIF / CCG Secure Data Storage Working group weekly call will be happening on Thursday at 4pm Eastern / 1pm Pacific / 22:00 CEST.

Meeting link: https://us02web.zoom.us/j/84828031746?pwd=V0xGTnJ2Zm15RHlSRFpNTlRPQzdLUT09

Specification: https://identity.foundation/confidential-storage/
Specification repository: https://github.com/decentralized-identity/confidential-storage

Audio recordings and transcripts of previous meetings: https://dif.groups.io/g/sds-wg/wiki/19633

As always, the IPR policy requires that you can only make substantive contributions if you sign the IPR Release Form. Please follow the instructions at https://dif.groups.io/g/sds-wg/wiki/Home

Confidential Storage Spec Call Agenda

1. IPR Reminder
2. Introductions and Re-Introductions

3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion.

PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

4. Issue review

 

Thank you,

The Chairs


 

--

ORIE STEELE

Chief Technical Officer

 


Adrian Gropper
 

Orie, please confirm what you mean by "can stand alone"... 
- Alice gets a ZCAP over HTTP form an EDV
- Alice attenuates the ZCAP and
    - hands it to Bob
    - along with a decryption key
    - and an address of the EDV
    - somehow, out-of-band
- Bob goes to the EDV, posts the ZCAP, gets the doc, and decrypts it.

How'm I doing?

Is there any role for DIDs in this?

Adrian

On Thu, Feb 18, 2021 at 3:15 PM Orie Steele <orie@...> wrote:
Layer A - EDVs currently assumes ZCAP over HTTP authorization, and can stand alone.... we don't need an authorization server, we have DIDs and capabilities.

Now you can layer other stuff on top, to integrate with legacy systems, but technically, the EDV spec defines a fully standalone HTTP server with support for authorization, delegation and replication over http with DIDs... it's currently checked in to the repo, and I am happy to give another demo of it...

I think Layer B accurately captures the Hubs dream :)

OS

On Thu, Feb 18, 2021 at 1:28 PM Michael Herman (Trusted Digital Web) <mwherman@...> wrote:

RE: 3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion. PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

 

p.s. …that is, visually, how is support for each of Daniel's use cases partitioned between CS Services and CS Core (see below)? 

…and of these, which should be supported in CS Core version 1? …and which should go into the CS Backlog?

 

 

 

Best regards,

Michael Herman

Sovrin Foundation Self-Sovereignist

 

Self-Sovereign Blockchain Architect

Trusted Digital Web

Hyperonomy Digital Identity Lab

Parallelspace Corporation

 

 

 

 

 

From: Michael Herman (Trusted Digital Web)
Sent: February 18, 2021 11:58 AM
To: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: RE: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

I know this is going to sound repetitive but … at the top of Daniel’s document, can someone add a couple of sentences distinguishing EDVs and Hub?

 

More specifically, based on last week’s discussion, I sense that the EDV/Hub discussion was more about:

  1. what belonged in the EDV/CS Core/”EDV Microkernel” as a (version 1) capability (e.g. Change Detection/Change Notifications) vs.
  2. what was part of a higher level service (e.g. indexing, replication, etc.)?

 

Does this distinction reflect what was at the heart of last week’s discussion (and this week’s)?

 

Rest regards,

Michael Herman

 

From: sds-wg@... <sds-wg@...> On Behalf Of Dmitri Zagidulin
Sent: February 18, 2021 11:02 AM
To: sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Dear all,


This is a reminder that the DIF / CCG Secure Data Storage Working group weekly call will be happening on Thursday at 4pm Eastern / 1pm Pacific / 22:00 CEST.

Meeting link: https://us02web.zoom.us/j/84828031746?pwd=V0xGTnJ2Zm15RHlSRFpNTlRPQzdLUT09

Specification: https://identity.foundation/confidential-storage/
Specification repository: https://github.com/decentralized-identity/confidential-storage

Audio recordings and transcripts of previous meetings: https://dif.groups.io/g/sds-wg/wiki/19633

As always, the IPR policy requires that you can only make substantive contributions if you sign the IPR Release Form. Please follow the instructions at https://dif.groups.io/g/sds-wg/wiki/Home

Confidential Storage Spec Call Agenda

1. IPR Reminder
2. Introductions and Re-Introductions

3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion.

PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

4. Issue review

 

Thank you,

The Chairs



--
ORIE STEELE
Chief Technical Officer
www.transmute.industries



Michael Herman (Trusted Digital Web)
 

RE: I’m also suggesting the CS specification should go further and define an EDV MIcrokerel layer and interface to make EDVs deployable

 

For example. Consider this use case: https://github.com/decentralized-identity/confidential-storage/issues/173

 

From: Michael Herman (Trusted Digital Web) <mwherman@...>
Sent: February 18, 2021 1:25 PM
To: Orie Steele <orie@...>
Cc: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: RE: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

RE: the EDV spec defines a fully standalone HTTP server with support for authorization, delegation, and replication over HTTP with DIDs...

 

Thank you, Orie, and, in general, I totally agree.

 

But I’m also suggesting the CS specification should go further and define an EDV MIcrokerel layer and interface to make EDVs deployable on local devices like iOS and Android apps.  An HTTP interface isn’t very useful in these scenarios.

 

Also from a security audit and code path traceability perspective, a microkernel architecture and interface will be more secure/securable.

 

Lastly, what is used to implement the EDV HTTP Server? …what underpins the implementation of the HTTP Serice? …how does it take into account different EDV data vaults mounted on the EDV Server?

 

Michael

 

From: Orie Steele <orie@...>
Sent: February 18, 2021 1:13 PM
To: Michael Herman (Trusted Digital Web) <mwherman@...>
Cc: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: Re: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Layer A - EDVs currently assumes ZCAP over HTTP authorization, and can stand alone.... we don't need an authorization server, we have DIDs and capabilities.

Now you can layer other stuff on top, to integrate with legacy systems, but technically, the EDV spec defines a fully standalone HTTP server with support for authorization, delegation and replication over http with DIDs... it's currently checked in to the repo, and I am happy to give another demo of it...

I think Layer B accurately captures the Hubs dream :)

OS

 

On Thu, Feb 18, 2021 at 1:28 PM Michael Herman (Trusted Digital Web) <mwherman@...> wrote:

RE: 3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion. PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

 

p.s. …that is, visually, how is support for each of Daniel's use cases partitioned between CS Services and CS Core (see below)? 

…and of these, which should be supported in CS Core version 1? …and which should go into the CS Backlog?

 

 

 

Best regards,

Michael Herman

Sovrin Foundation Self-Sovereignist

 

Self-Sovereign Blockchain Architect

Trusted Digital Web

Hyperonomy Digital Identity Lab

Parallelspace Corporation

 

 

 

 

 

From: Michael Herman (Trusted Digital Web)
Sent: February 18, 2021 11:58 AM
To: sds-wg@...; sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: RE: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

I know this is going to sound repetitive but … at the top of Daniel’s document, can someone add a couple of sentences distinguishing EDVs and Hub?

 

More specifically, based on last week’s discussion, I sense that the EDV/Hub discussion was more about:

  1. what belonged in the EDV/CS Core/”EDV Microkernel” as a (version 1) capability (e.g. Change Detection/Change Notifications) vs.
  2. what was part of a higher level service (e.g. indexing, replication, etc.)?

 

Does this distinction reflect what was at the heart of last week’s discussion (and this week’s)?

 

Rest regards,

Michael Herman

 

From: sds-wg@... <sds-wg@...> On Behalf Of Dmitri Zagidulin
Sent: February 18, 2021 11:02 AM
To: sds-wg@dif.groups.io; Credentials Community Group <public-credentials@...>
Subject: [sds-wg] Reminder and Agenda for Confidential Storage Spec Call - Feb 18 2021

 

Dear all,


This is a reminder that the DIF / CCG Secure Data Storage Working group weekly call will be happening on Thursday at 4pm Eastern / 1pm Pacific / 22:00 CEST.

Meeting link: https://us02web.zoom.us/j/84828031746?pwd=V0xGTnJ2Zm15RHlSRFpNTlRPQzdLUT09

Specification: https://identity.foundation/confidential-storage/
Specification repository: https://github.com/decentralized-identity/confidential-storage

Audio recordings and transcripts of previous meetings: https://dif.groups.io/g/sds-wg/wiki/19633

As always, the IPR policy requires that you can only make substantive contributions if you sign the IPR Release Form. Please follow the instructions at https://dif.groups.io/g/sds-wg/wiki/Home

Confidential Storage Spec Call Agenda

1. IPR Reminder
2. Introductions and Re-Introductions

3. Continuation of the ‘Division of Responsibilities between Hubs and EDVs’ discussion.

PLEASE REVIEW: Daniel Buchner's proposed list https://hackmd.io/qClYLUPkQ7uf0r3_4O7BUQ

4. Issue review

 

Thank you,

The Chairs


 

--

ORIE STEELE

Chief Technical Officer