From fa2993b427f12796356a232c54be75814fac5d98 Mon Sep 17 00:00:00 2001 From: pablo Date: Tue, 21 Oct 2025 18:01:57 +0300 Subject: [PATCH] fix: pr feedback --- standards/application/segmentation.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/standards/application/segmentation.md b/standards/application/segmentation.md index af1adc2..a7b4c91 100644 --- a/standards/application/segmentation.md +++ b/standards/application/segmentation.md @@ -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