├── applicability-of-webdav.md └── README.md /applicability-of-webdav.md: -------------------------------------------------------------------------------- 1 | Applicability of WebDAV (RFC 4918) for synchronisation purposes 2 | 3 | This document outlines the applicability of the [WebDAV Protocol](http://www.webdav.org/specs/rfc4918.html) as a base protocol for synchronisation purposes. 4 | 5 | ## To Be Considered 6 | 7 | * [Collection Synchronization for Web Distributed Authoring and Versioning (WebDAV)](https://www.ietf.org/rfc/rfc6578.txt) 8 | * [Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)](http://www.webdav.org/specs/rfc3253.html) 9 | * [ownCloud Sync Protocol](https://github.com/cernbox/smashbox/blob/master/protocol/protocol.md) and [Checksum extension]( 10 | https://github.com/cernbox/smashbox/blob/master/protocol/checksum.md) 11 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Internet Storage Sync ( ISS ) 2 | 3 | **Internet Storage Sync - Mechanisms to synchronize client file systems with Internet-based data storage services** 4 | 5 | This repository contains supporting documents for [ISS](https://tools.ietf.org/html/draft-cui-iss-problem-03) discussion topics that are not suitable to be tracked in the mailing list. 6 | 7 | 8 | [Internet Storage Sync](https://tools.ietf.org/html/draft-cui-iss-problem-03) is an IETF working draft with the following objective: 9 | 10 | ``` 11 | Internet storage services have become more and more popular. They 12 | attract a huge number of users and produce a significant share of 13 | Internet traffic. Most existing Internet storage services make use 14 | of proprietary sync protocols with different capabilities to achieve 15 | the data sync. However, a single Internet storage service using its 16 | proprietary sync protocols has intrinsic limitations on service 17 | usability and network performance. This document outlines the 18 | related problems caused by using proprietary sync protocols and 19 | missing key capabilities. It also shows a demand for designing a 20 | standard sync protocol to achieve better usability and sync 21 | performance. 22 | ``` 23 | 24 | ## Topics of interest 25 | 26 | ``` 27 | 1.The design targets of WebDAV, rsync and other existing approaches? 28 | 2.The potential use cases of ISS, such as client/server, git-like pattern, svn, etc. 29 | 3.The efficiency improvements might be the second goal for standardizing ISS protocol 30 | 4.CORS headers on storage sync APIs 31 | 5.What is needed for the ISS: a sync protocol or a generalized API 32 | 6.remoteStorage draft discussion 33 | a)relationship vs WebDAV 34 | b)MOVE action should be added or not 35 | c)synchronization should be considered or not 36 | d)comics of new standard 37 | 7.GitHub instead of email messages 38 | a)What is the topic? 39 | i.Whether it is suitable to build on WebDAV 40 | ii.WebDAV vs remoteStorage 41 | iii.Advantages vs disadvantages of WebDAV 42 | ``` 43 | 44 | 45 | ## Supporting documents 46 | To contribute to these documents, please read [How To Contribute](#how-to-contribute). 47 | 48 | * [Applicability of WebDAV (RFC 4918) for synchronisation purposes ?](./applicability-of-webdav.md). 49 | 50 | 51 | ## Related projects and organisations 52 | This is a list of projects and organisations which activities are highly "in sync" with the topics covered in the ISS group. 53 | 54 | *List is alphabetically sorted* 55 | 56 | * [ClawIO](http://clawio.github.io) [Project] 57 | * [CrossCloud.me](https://crosscloud.me/) [Product] 58 | * [CrossCloud.org](http://crosscloud.org/jobs/) [Project] 59 | * [CS3: Cloud Services for Synchronisation and Sharing ](http://cs3.ethz.ch/program.html) [Conference] 60 | * [GEANT Community](http://www.geant.org/) [Community] 61 | * [OpenCloudMesh](http://oc.owncloud.com/opencloudmesh.html) [Project] 62 | * [ownCloud](http://owncloud.org) [Product] 63 | * [remoteStorage](https://remotestorage.io/) [Protocol] 64 | 65 | 66 | 67 | ## How To Contribute 68 | New contributions to these documents have to be previously discussed using the [ISS mailing list](https://www.ietf.org/mailman/listinfo/storagesync). 69 | 70 | The contribution flow is the following: 71 | 72 | 1. Open a discussion in the [ISS mailing list](https://www.ietf.org/mailman/listinfo/storagesync). 73 | 2. Other members of the [ISS mailing list](https://www.ietf.org/mailman/listinfo/storagesync) will give their opinion and review the topic presented. 74 | 3. When there is a general agreement on the topic anyone can contribute to these documents using one of the mechanisms outlined below in order to have the information pressented in a more efficient way. 75 | 76 | Contributions to these documents can be made using the following ways: 77 | 78 | * Pull Request (Recommended) 79 | * Issue 80 | --------------------------------------------------------------------------------