logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-05-25 22:39:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: pr feedback

Browse Source
This commit is contained in:
pablo 2025-10-21 18:01:57 +03:00 committed by Igor Sirotin
parent 7346d36ccb
commit e706dcb6f7
No known key found for this signature in database
GPG Key ID: 0EABBCB40CB9AD4A
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
standards/application/segmentation.md
View File

@ -12,7 +12,7 @@ This specification defines an application-layer protocol for **segmentation** an
## Motivation
Waku Relay deployments typically propagate envelopes up to **150 KB** as per [64/WAKU2-NETWORK - Message Size](https://rfc.vac.dev/waku/standards/core/64/network#message-size). To support larger application payloads, a segmentation layer is required. This specification enables larger messages by partitioning them into multiple envelopes and reconstructing them at the receiver. Erasure-coded parity segments provide resilience against partial loss or reordering.
Waku Relay deployments typically propagate envelopes up to **150 KB** as per [64/WAKU2-NETWORK - Message](https://rfc.vac.dev/waku/standards/core/64/network#message-size). To support larger application payloads, a segmentation layer is required. This specification enables larger messages by partitioning them into multiple envelopes and reconstructing them at the receiver. Erasure-coded parity segments provide resilience against partial loss or reordering.
## Terminology
@ -137,7 +137,6 @@ Implementations **SHOULD** support:
### Privacy
`entire_message_hash` enables correlation of segments that belong to the same original message but does not reveal content.
Applications **SHOULD** encrypt payloads before segmentation.
Traffic analysis may still identify segmented flows.
### Integrity