[OCM] Meeting minutes 2026-03-31

[Micke Nordin <[e-mail]>]

    Date: 2026-03-31 11:00 CEST

<https://github.com/cs3org/OCM-API/wiki/Meetings-2026#date-2026-03-31-1100-cest>


      Agenda

<https://github.com/cs3org/OCM-API/wiki/Meetings-2026#agenda>

  * STA work <https://github.com/orgs/cs3org/projects/3> status update
      o M6 was claimed by Mahdi, can be easily integrated in ownCLoud
        and OpenCloud, not only CERNBox reva.
      o Mahdi is working on integrating this into Enriques work on
        Nextcloud, hopefully finalized next week.
  * Spec work - PR:s
      o Clarify code flow sender and receiver semantics
        <https://github.com/cs3org/OCM-API/pull/354> <-
        Cleanup/clarification
          + This is not controversial in anyway and can be merged.
            token-exchange vs exchange-token, should we use
            must-exchange-token as criteria instead? This would align
            with mfa.
      o Journaling <https://github.com/cs3org/OCM-API/pull/353> <- New
        feature
          + To be decided in the next IETF interim meeting, come there
            and discuss.
      o ResourceDiscovery <https://github.com/cs3org/OCM-API/pull/196>
        <- New feature
          + Incorporates FAIR principles that are also machine
            actionable, also provide an alternative to dataspaces. To be
            decided in the next IETF interim meeting, come there and
            discuss.
      o RequestShare <https://github.com/cs3org/OCM-API/pull/194> <- New
        feature
          + To be decided in the next IETF interim meeting, come there
            and discuss. Spamming could be an issue here.
  * Spec work - ISSUES:s
      o WebApp <https://github.com/cs3org/OCM-API/issues/351> - Micke
          + Micke has a similiar report as Mahdi, will send a pr for this.
      o Notifications <https://github.com/cs3org/OCM-API/issues/350> -
        Mahdi
        <https://github.com/cs3org/OCM-API/commit/1722f0fcfc910f7101ee33cb0a45c12f45821754>

      o Federation Sharing <https://github.com/cs3org/OCM-API/issues/270>
          + Maybe leave this quite open in the core specification, and
            leave the possibility to do MLS over OCM in a future I-D,
            possibly needs a recharter of the working group.
  * CS3 workshop / IETF Meeting / ISGC Symposium debrief
      o Digital Sovereignty was a big topic in CS3. Richard met Barend
        Mons
        <https://scholar.google.com/citations?user=KzMiMF4AAAAJ&hl=en>
        who expressed interest in OCM. We should invite him to discuss
        resource discovery. Micke held a Hot-Rfc talk at IETF 125, we
        should also keep an eye on canonical jscontact uri, which could
        be interesting for invitations in OCM.
  * Security review
      o ownCloud has offered to do this. We should probably also as CERN
        security team that has offered also, so maybe do both.
  * OCM hexagon stickers were printed along with CS3 stickers. We should
    give the current logo to IETF protocol badge designers and see what
    the come up with.


      Present

<https://github.com/cs3org/OCM-API/wiki/Meetings-2026#present>

  * Giuseppe Lo Presti <https://github.com/glpatcern>
  * Micke Nordin <https://github.com/mickenordin>
  * Julian Koberg <https://github.com/kobergj>
  * Mahdi Baghbani <https://github.com/MahdiBaghbani> - Offline, but
    report via PR
  * Rasmus Welander <https://github.com/rawe0>
  * Richard Freitag

As usual, minutes are also available online: 
https://github.com/cs3org/OCM-API/wiki/Meetings-2026#date-2026-03-31-1100-cest

All the best,

Micke