UPDATE ......From Tuesday 8 April 2025 we have changed the way that Single Sign-on works on this wiki. Please see here for more information:
Update
...
The bottom line of the consultation process is the preliminary TCD service architecture depicted below. You might also want to read the paper submitted to the SUCRE CloudSource Magazine for more background information.
The strategic direction to be taken by TERENA is gradually shaping as follows:
- TCD should focus on its main asset; maintaining trust and privacy of the client domain by separating metadata and encryption keys (to be kept in a trusted place) from the storage data (to be exported to back-end storage) at the domains' boundary.
- TCD should not compete with the feature-rich front-end sync&share applications available on the market (such as PowerFolder or OwnCloud platforms) instead, broker them to various public and/or NREN-provided storage back-ends in a trusted way.
- TCD should be a lightweight, thin layer (preferably controlled and operated by NRENs) separating/interfacing end-user application domains and cloud service provider domains; considered to be a "storage middleware".
- TCD should ensure the interoperability with some selected private storage service platforms (throughout strategic partnership) at the front-end as well as aggregating demands and relaying storage data to public cloud storage offerings (procured by TERENA under framework agreements) at the back-end.
Consultation participants
...