Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • U upsycle-router-design
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • DREAM
  • UPSYCLE
  • upsycle-router-design
  • Issues
  • #1
Closed
Open
Created Jan 20, 2021 by Allen Haim@allen-alleycatOwner8 of 8 tasks completed8/8 tasks

D1.2 UPSYCLE specification

Complete UPSYCLE specification that should include:

  • overall overview of pub/sub and routing system.
  • serialisation (CBOR), transport (DTLS)
  • description of public key-based routing.
  • authentication & encryption, cryptographic properties (e.g. forward secrecy).
  • event model & dissemination, how to determine causality of events & messages.
  • core & edge network topology, role of relay nodes.
  • description of protocol flows, e.g. how a node joins/leaves a group, creates/deletes a topic.
  • how to interface to the back-end P2P system.
    • @tg-x's NGI0 work on P2Pcollab (ideal)
    • or an existing or simplified system (as a backup in order to avoid this external dependency)

Design document (WIP)

Edited Mar 31, 2021 by TG × ⊙
Assignee
Assign to
Time tracking