vacp2p/rfc
1
0
Fork 0
mirror of https://github.com/vacp2p/rfc.git synced 2025-01-11 15:24:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

review tweaks

Browse Source
This commit is contained in:
Oskar Thoren 2019-10-02 14:07:31 +08:00
parent 5fcb995738
commit 5740e95234
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
remote-log.md
View File

@ -38,7 +38,7 @@ This specification is complemented by a proof of concept implementation <sup>1</
### Secure Transport, storage, and name system
This specification does not define anything related to to: secure transport,
This specification does not define anything related to: secure transport,
content addressed storage, or the name system. It is assumed these capabilities
are abstracted away in such a way that any such protocol can easily be
implemented.
@ -141,7 +141,7 @@ There are four fundamental roles:
2. Name system (NS)
3. Content-addressed storage (CAS)
The *remote log* protobuf is what is stored at the Name system.
The *remote log* protobuf is what is stored in the name system.
"Bob" can represent anything from 0 to N participants. Unlike Alice, Bob only needs read-only access to NS and CAS.
@ -213,7 +213,7 @@ in time.
### Interaction with MVDS
`vac.mvds.Message` payloads are the only payloads that MUST be uploaded. Other messages types MAY be uploaded, depending on the implementation.
[`vac.mvds.Message`](./mvds.md#payloads) payloads are the only payloads that MUST be uploaded. Other messages types MAY be uploaded, depending on the implementation.
## Footnotes