Open Cloud Mesh
draft-lopresti-open-cloud-mesh-08
| Document | Type |
Replaced Internet-Draft
(ocm WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Giuseppe Lo Presti , Michiel B. de Jong , Mahdi Baghbani , Micke Nordin | ||
| Last updated | 2025-11-25 (Latest revision 2025-11-11) | ||
| Replaced by | draft-ietf-ocm-open-cloud-mesh | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ocm-open-cloud-mesh | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Open Cloud Mesh (OCM) is a server federation protocol that is used to notify a Receiving Party that they have been granted access to some Resource. It has similarities with authorization flows such as OAuth, as well as with social internet protocols such as ActivityPub and email. A core use case of OCM is when a user (e.g., Alice on System A) wishes to share a resource (e.g., a file) with another user (e.g., Bob on System B) without transferring the resource itself or requiring Bob to log in to System A. While this scenario is illustrative, OCM is designed to support a broader range of interactions, including but not limited to file transfers. Open Cloud Mesh handles interactions only up to the point where the Receiving Party is informed of their access to the Resource. Actual Resource access is subsequently managed by other protocols, such as WebDAV.
Authors
Giuseppe Lo Presti
Michiel B. de Jong
Mahdi Baghbani
Micke Nordin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)