vacp2p
/
rfc
mirror of https://github.com/vacp2p/rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Modular p2p messaging stack, with a focus on secure messaging. https://rfc.vac.dev/
41 Commits 45 Branches 11 Tags 32 MiB
HTML 77.9%
Dockerfile 22.1%
Go to file
Oskar Thoren ccb9ae7f44
Add 0.1.0 remote log initial spec 		2019-09-30 13:08:04 +08:00
.github/ISSUE_TEMPLATE Create research-issue.md 2019-09-20 20:26:10 +02:00
assets Create interactive.msc 2019-08-04 14:47:25 +02:00
404.html Create 404.html 2019-09-22 20:39:34 +02:00
CNAME Create CNAME 2019-08-04 15:25:11 +02:00
README.md Add style guide on sequence diagrams 2019-09-24 13:29:48 +08:00
_config.yml Update _config.yml 2019-08-02 18:20:01 +02:00
mvds.md Revert "Add vac.mvds package" 2019-09-24 12:57:56 +08:00
remote-log.md Add 0.1.0 remote log initial spec 2019-09-30 13:08:04 +08:00

README.md

Specifications

This repository contains the specs for vac, a modular peer-to-peer messaging stack, with a focus on secure messaging. A detailed explanation of the vac and its design goals can be found here.

Status

The entire vac protocol is under active development, each specification has its own status which is reflected through the version number at the top of every document. We use semver to version these specifications.

Protocols

These protocols define various components of the vac stack.

  • mvds - Ensure reliable messaging between peers across an unreliable peer-to-peer (P2P) network where they may be unreachable or unresponsive.

Style guide

All specs follow RFC-2119.

Sequence diagrams are generated using Mscgen like this: mscgen -T png -i input.msc -o output.png. Both the source and generated image should be in source control. For ease of readability, the generated image is embedded inside the main spec document.