remoteStorage
draft-dejong-remotestorage-16
INTERNET DRAFT Michiel B. de Jong
Document: draft-dejong-remotestorage-16 (independent)
F. Kooman
(independent)
S. Kippe
Intended Status: Proposed Standard (independent)
Expires: 1 June 2021 11 December 2020
remoteStorage
Abstract
This draft describes a protocol by which client-side applications,
running inside a web browser, can communicate with a data storage
server that is hosted on a different domain name. This way, the
provider of a web application need not also play the role of data
storage provider. The protocol supports storing, retrieving, and
removing individual documents, as well as listing the contents of an
individual folder, and access control is based on bearer tokens.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 1 June 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
de Jong [Page 1]
Internet-Draft remoteStorage December 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction...................................................2
2. Terminology....................................................3
3. Storage model..................................................3
4. Requests.......................................................4
5. Response codes.................................................7
6. Versioning.....................................................8
7. CORS headers...................................................8
8. Session description............................................9
9. Bearer tokens and access control...............................9
10. Application-first bearer token issuance.......................10
11. Storage-first bearer token issuance...........................12
12. Example wire transcripts......................................12
12.1. WebFinger................................................12
12.2. OAuth dialog form........................................13
12.3. OAuth dialog form submission.............................14
12.4. OPTIONS preflight........................................14
12.5. Initial PUT..............................................15
12.6. Subsequent PUT...........................................15
12.7. GET......................................................16
12.8. DELETE...................................................17
13. Distributed versioning........................................18
14. Security Considerations.......................................19
15. IANA Considerations...........................................20
16. Acknowledgments...............................................20
17. References....................................................20
17.1. Normative References.....................................20
17.2. Informative References...................................21
18. Authors' addresses............................................22
1. Introduction
Many services for data storage are available over the Internet. This
specification describes a vendor-independent interface for such
services. It is based on HTTPS, CORS and bearer tokens. The
metaphor for addressing data on the storage is that of folders
containing documents and subfolders. The actions the interface
exposes are:
de Jong [Page 2]
Show full document text