OCM-API icon indicating copy to clipboard operation
OCM-API copied to clipboard

Milestone 5 "spec text development"

Open michielbdejong opened this issue 1 year ago • 5 comments

Write a proper Internet Draft, submit to IETF

michielbdejong avatar Aug 26 '24 11:08 michielbdejong

I think we should probably write four specs:

  • client instance discovery for GNAP
  • end user discovery for GNAP
  • resource notifications for GNAP
  • Open Cloud Mesh (putting it all together but adding as little as possible original content in itself)

michielbdejong avatar Aug 27 '24 10:08 michielbdejong

We should also research how the fediverse does client instance discovery and end user discovery.

michielbdejong avatar Aug 27 '24 14:08 michielbdejong

Lots of new thoughts since last week. No need to add a dependency on GNAP I think, since OCM is really somewhere between authorization and fediverse. I think we can write a single spec that first describes the strictest version that everyone should support, and then add extensions from there.

Rough idea for sections:

  • creating a share, using httpsig+bearer tokens
  • other / multiple protocols, extra (legacy) fields
  • dynamic client registration, discovery (/.well-known/ocm, /ocm-provider, DNS SRV)
  • recipient user/group discovery, invites
  • flows
  • accept/reject/revoke notifications
  • reshare notifications

michielbdejong avatar Sep 03 '24 09:09 michielbdejong

I did some work on this today in #103. Will continue tomorrow.

michielbdejong avatar Sep 03 '24 14:09 michielbdejong

I'm now trying to split this up into smaller, reviewable PRs - will add to this list as I progress:

  • #109

michielbdejong avatar Sep 04 '24 10:09 michielbdejong

I think this can be closed for good, after having published the IETF draft!

glpatcern avatar Dec 17 '24 10:12 glpatcern