vacp2p/rfc
1
0
Fork 0
mirror of https://github.com/vacp2p/rfc.git synced 2025-01-23 13:19:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

update(lightpush): dandelion (#549)

Browse Source
This commit is contained in:
kaiserd 2022-12-13 11:45:58 +01:00 committed by GitHub
parent 5684d26461
commit 127f5bd2c7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
content/docs/rfcs/19/README.md
View File

@ -4,17 +4,16 @@ title: 19/WAKU2-LIGHTPUSH
name: Waku v2 Light Push
status: draft
editor: Oskar Thorén <oskar@status.im>
contributors:
contributors: Daniel Kaiser <danielkaiser@status.im>
---
**Protocol identifier**: `/vac/waku/lightpush/2.0.0-beta1`
# Motivation and goals
# Motivation and Goals
Light nodes with short connection windows and limited bandwidth wish to publish
messages into the Waku network. Additionally, there is sometimes a need for
confirmation that a message has been received "by the network" (here, at least
one node).
Light nodes with short connection windows and limited bandwidth wish to publish messages into the Waku network.
Additionally, there is sometimes a need for confirmation that a message has been received "by the network"
(here, at least one node).
`19/WAKU2-LIGHTPUSH` is a request/response protocol for this.
@ -41,17 +40,26 @@ message PushRPC {
}
```
## Message relaying
## Message Relaying
Nodes that respond to `PushRequests` MUST relay this via [11/WAKU2-RELAY](/spec/11) protocol on the specified `pubsub_topic`.
Nodes that respond to `PushRequests` MUST either
relay the encapsulated message via [11/WAKU2-RELAY](/spec/11) protocol on the specified `pubsub_topic`,
or forward the `PushRequest` via 19/LIGHTPUSH on a [44/WAKU2-DANDELION](https://rfc.vac.dev/spec/44/) stem.
If they are unable to do so for some reason, they SHOULD return an error code in `PushResponse`.
## Security considerations
## Security Considerations
Since this can introduce amplification factor, it is RECOMMENDED for the node relaying to the rest of the network to extra precaution. This can be done by various forms of rate limiting, or by using [18/WAKU2-SWAP](/spec/18) to account for the service provided.
Since this can introduce an amplification factor, it is RECOMMENDED for the node relaying to the rest of the network to take extra precautions.
This can be done by rate limiting via [17/WAKU2-RLN-RELAY](https://rfc.vac.dev/spec/17/).
Note that the above is currently not fully implemented.
# Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
# References
* [11/WAKU2-RELAY](/spec/11)
* [44/WAKU2-DANDELION](https://rfc.vac.dev/spec/44/)