%% You should probably cite draft-ietf-ocm-open-cloud-mesh instead of this I-D.
@techreport{lopresti-open-cloud-mesh-08,
    number =    {draft-lopresti-open-cloud-mesh-08},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-lopresti-open-cloud-mesh/08/},
    author =    {Giuseppe Lo Presti and Michiel B. de Jong and Mahdi Baghbani and Micke Nordin},
    title =     {{Open Cloud Mesh}},
    pagetotal = 34,
    year =      2025,
    month =     nov,
    day =       11,
    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.},
}