Merge branch 'develop' into kano-resource-discovery

Author: MahdiBaghbani

.github/workflows/github-pages.yml

@@ -0,0 +1,57 @@
+name: Deploy GitHub Pages
+on:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      
+      - name: Install pandoc
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y pandoc
+
+      - name: Build site
+        run: |
+          rm -rf dist
+          mkdir -p dist
+
+          pandoc README.md \
+            --from=gfm \
+            --to=html5 \
+            --standalone \
+            --metadata title="README" \
+            -o dist/index.html
+
+          cp ./logo.png ./dist/logo.png
+          cp ./docs.html ./dist/docs.html
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: dist
+
+  deploy:
+    needs: build
+
+    # Grant GITHUB_TOKEN the permissions required to make a Pages deployment
+    permissions:
+      pages: write      # to deploy to Pages
+      id-token: write   # to verify the deployment originates from an appropriate source
+
+    # Deploy to the github-pages environment
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    # Specify runner + deployment step
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4
+
+

.github/workflows/line-length.yml

@@ -0,0 +1,18 @@
+name: Validate I-D line length
+on:
+  push:
+    branches:
+      - "*"
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  validate_line_length:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Validate I-D line length
+        run: if grep -nE '.{73,}' IETF-RFC.md | grep ' '; then echo "Found lines exceeding the limit"; exit -1; else echo "Validation completed successfully"; fi
+

.github/workflows/oas-validation.yml

@@ -1,5 +1,10 @@
 name: Validate OpenAPI Specification
-on: [push]
+on:
+  push:
+    branches:
+      - "*"
+  pull_request:
+  workflow_dispatch:
 
 jobs:
   validate_openapi:

.github/workflows/rfc.yml

@@ -1,10 +1,7 @@
-name: Build RFC XML
+name: Prepare I-D for Datatracker
 
 on:
-  push:
-    branches: [develop]
-    paths: [IETF-RFC.md]
-  workflow_dispatch:         
+  workflow_dispatch:
 
 jobs:
   build:
@@ -13,7 +10,6 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      # Ruby setup
       - uses: ruby/setup-ruby@v1
         with:
           ruby-version: '3.2'
@@ -22,25 +18,47 @@ jobs:
       - name: Install kramdown-rfc
         run: gem install --no-document kramdown-rfc
 
-      - name: Convert Markdown to XML
-        run: kramdown-rfc IETF-RFC.md > IETF-RFC.xml
+      - name: Bump I-D version
+        run: perl -pe 's/open-cloud-mesh-(\d+)/"open-cloud-mesh-" . sprintf("%02d", $1 + 1)/e' -i IETF-RFC.md || exit -1
+
+      - name: Convert Markdown to XML and save output
+        id: convert
+        run: |
+          kramdown-rfc IETF-RFC.md > IETF-RFC.xml 2> /tmp/result || true
+          cat /tmp/result
+          echo "result<<EOF" >> $GITHUB_OUTPUT
+          cat /tmp/result >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: rfc-md
+          path: IETF-RFC.md
 
       - uses: actions/upload-artifact@v4
         with:
           name: rfc-xml
           path: IETF-RFC.xml
 
-      # Commit the result back to the repo
+      # Create a PR to the repo with the results
       - uses: peter-evans/create-pull-request@v6
         with:
           branch: rfc/gen-${{ github.sha }}
           base: develop
           add-paths: |
+            IETF-RFC.md
             IETF-RFC.xml
-          commit-message: 'CI: regenerate IETF-RFC.xml'
+          commit-message: 'CI: regenerate IETF-RFC.xml for Datatracker'
           signoff: true
           title: 'Regenerate IETF-RFC.xml'
-          body: 'Automatic XML regeneration by CI'
+          body: |
+            This autogenerated PR bumps the IETF version of the I-D and prepares the IETF-RFC.xml file for submission to the [IETF Datatracker](https://datatracker.ietf.org/submit).
+
+            The conversion produced the output below:
+            ```
+            ${{ steps.convert.outputs.result }}
+            ```
           reviewers: |
             glpatcern
-            michielbdejong
+            MahdiBaghbani
+            mickenordin

CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## [1.2.1] - 2025-07-17 - Giuseppe Lo Presti <[email protected]>
+
+* Overall review of the spec in the ongoing quest to improve clarity
+  and consistency, without altering the semantic of the API.
+* Introduced concept of a Directory Service with a Where-Are-You-From
+  page capability and an Invite Accept Dialog property to complement
+  the Invite flow. Correspondingly, the Discovery endpoint has been
+  extended and its description improved.
+
 ## [1.2.0] - 2024-11-20 - Michiel B. de Jong <[email protected]>
 
 * Rephrased and improved the whole protocol description text

HISTORY.md

@@ -1,20 +1,21 @@
 History and Previous Meet-ups
 =============================
 
-The Open Cloud Mesh initiative started in 2015 within the [GÉANT Association](https://geant.org). Here follows a brief history of the project, including pointers to all technical presentations held over the years, with their recordings where available.
+The Open Cloud Mesh initiative started in 2015 within the [GÉANT Association](https://geant.org). Here follows a brief history of the project, including pointers to all known technical presentations held over the years, with their recordings where available.
 
 
-### Origins of the project at GÉANT
+### Origins of the project at [GÉANT](https://geant.org)
 * In December 2013, the GÉANT Association (formerly known as TERENA) and ownCloud Inc. made an agreement that serves to facilitate the desire of various National Research and Education Networking organisations (NRENs) to introduce services based on ownCloud technology and/or to offer the technology to their constituencies. Such technology appeared to be the most promising in order to provide on-premise file-based sync&share.
-* As part of this collaboration effort, in January 2015, Christian Schmitz from ownCloud initiated an idea to interconnect the individual on-premise private cloud domains at the server side in order to provide federated sharing and syncing functionality between the different administrative domains.
-* The initiative was presented at the [Cloud Sync&Share Storage (CS3) Workshop 2016](https://cs3.ethz.ch/program.html) to an emerging community of vendors, NRENs and other institutions.
-* Minutes of the early meetings and actions are available at the [GÉANT wiki](https://wiki.geant.org/display/OCM/Open+Cloud+Mesh).
+* As part of this collaboration effort, in January 2015, ownCloud initiated an idea to interconnect the individual on-premise private cloud domains at the server side in order to provide [federated sharing functionalities](https://oc.owncloud.com/opencloudmesh.html) between the different administrative domains.
+* The initiative was presented at the [TF-Storage Meeting 2015](https://wiki.geant.org/display/CISS/17th+TF-Storage+meeting) ([slides available from the web archive](https://web.archive.org/web/20200930061326/https:/www.terena.org/activities/tf-storage/ws19/slides/20151014-ocm.pdf)) and subsequently to the [Cloud Sync&Share Storage (CS3) Workshop 2016](https://cs3.ethz.ch/program.html) to an emerging community of vendors, NRENs and other institutions. A [follow-up presentation](https://indico.cern.ch/event/565381/contributions/2401967) took place at CS3 2017.
 * Following that initial effort, implementations appeared in the market featuring a `1.0-proposal1` OCM API version, prior to official standardization. A Campfire-style discussion about current developments and standardization plans was held at [CS3 2020](https://indico.cern.ch/event/854707/timetable/#20200128.detailed).
+* Minutes of the early meetings and actions are available at the [GÉANT wiki](https://wiki.geant.org/display/OCM/Open+Cloud+Mesh).
 
 
-### The EU-funded CS3MESH4EOSC project
-* In January 2020, a consortium of multiple NRENs and independent actors of the [CS3 community](www.cs3community.org), led by CERN, kick-started the [CS3MESH4EOSC project](https://cs3mesh4eosc.eu).
+### The EU-funded [CS3MESH4EOSC project](https://cs3mesh4eosc.eu)
+* In January 2020, a consortium of multiple NRENs and independent actors of the [CS3 community](www.cs3community.org), led by CERN, kick-started the CS3MESH4EOSC project.
 * [Technical Workshop](https://indico.cern.ch/event/928998) held in June 2020: **the `1.0.0` release of the OCM API was [published](https://github.com/cs3org/OCM-API/blob/develop/CHANGELOG.md#100---2020-07-01---bjoern-schiessle-bjoernschiessleorg)**. On the occasion, the OCM repository was migrated to the [cs3org](https://github.com/cs3org) GitHub Organization. The standard was already implemented by ownCloud, Nextcloud and Seafile, and used in production to federate multiple instances.
+* [Paper presented at CHEP 2021](https://www.epj-conferences.org/articles/epjconf/abs/2021/05/epjconf_chep2021_02041/epjconf_chep2021_02041.html) about the emerging ScienceMesh federation.
 * [Automated tests](https://github.com/pondersource/dev-stock?tab=readme-ov-file#open-cloud-mesh-test-suite-) initiated and hosted by PonderSource.
 * [OCM Workshop held at CS3 2021](https://indico.cern.ch/event/970232/sessions/372052/#20210127).
 * OCM Interoperability Session held at the [CS3 2022](https://indico.cern.ch/event/1075584/timetable/#20220124.detailed).
@@ -23,11 +24,16 @@ The Open Cloud Mesh initiative started in 2015 within the [GÉANT Association](h
 * In June 2023, members of the CS3MESH4EOSC project presented at the [EGI 2023 conference](https://whova.com/web/M8zkrnLo5DUwlnug54VINPkHTdssyl49PHa20jCW2Qg%3D/Agenda/), demonstrating the [ScienceMesh](https://sciencemesh.io) and its OCM-based federation capabilities with live demos.
 
 
-### NL-net funded efforts
+### [NL-net](https://nlnet.nl) funded efforts
 * In October 2023 a [W3C Community Group](https://www.w3.org/community/ocm/) was launched.
 * A Campfire and Panel session about OCM took place at [CS3 2024](https://indico.cern.ch/event/1332413/timetable/#20240312.detailed), held back at CERN on its 10th anniversary. Subsequently, the CS3 community initiated thematic SIGs, including an OCM SIG.
 * The OCM Test Suite was revamped, and the specification underwent a major rewrite in order to improve clarity and adopt the IETF Internet-Draft format.
 * [Technical Workshop](https://indico.cern.ch/event/1451374/) held in November 2024: **a new version was [published](https://github.com/cs3org/OCM-API/blob/develop/CHANGELOG.md#120---2024-11-20---michiel-b-de-jong-michielpondersourcecom) and the Internet-Draft document was presented**.
 * Presentation at [FOSDEM 25](https://ftp.fau.de/fosdem/2025/h1308/fosdem-2025-5094-open-cloud-mesh.av1.webm).
-* In March 2025, the team was invited to present the Internet-Draft document at the IETF Meeting #122. The presentation was postponed to the IETF Meeting #123, as it clashed with the CS3 2025 event.
+* In March 2025, the team was invited to present the Internet-Draft document at the IETF Meeting 122. The presentation was postponed to the next meeting, as it clashed with the CS3 2025 event.
 * At [CS3 2025](https://indico.cern.ch/event/1467643/timetable/#20250319.detailed) the OCM CS3 SIG held a session to report on its activity.
+* The Internet-Draft document was presented at [IETF 123](https://datatracker.ietf.org/meeting/123/agenda), as part of the [Dispatch session](https://datatracker.ietf.org/meeting/123/session/dispatch) ([recording](https://youtu.be/LJMnsFVR3rU?t=452)). **Version 1.2.1 was [published](https://github.com/cs3org/OCM-API/blob/develop/CHANGELOG.md#121---2025-07-17---giuseppe-lo-presti-lopresticernch)** in preparation for that event. Following a successful dispatch, a non-WG [IETF mailing list](https://mailman3.ietf.org/mailman3/lists/ocm.ietf.org) was provided to initiate the standardization process.
+
+
+## The path towards IETF Standardization
+* The [wiki](https://github.com/cs3org/OCM-API/wiki) is launched to collect minutes of the ongoing meetings.