From 681bcafea7dec6458aeec3e13316f3819be7a1d1 Mon Sep 17 00:00:00 2001 From: Jimmy Debe <91767824+jimstir@users.noreply.github.com> Date: Tue, 9 Jul 2024 06:03:39 -0400 Subject: [PATCH] Update noise-sessions.md --- standards/application/noise-sessions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/standards/application/noise-sessions.md b/standards/application/noise-sessions.md index 3207fb9..adb5dd1 100644 --- a/standards/application/noise-sessions.md +++ b/standards/application/noise-sessions.md @@ -60,7 +60,7 @@ The above mechanism allows a Noise session to be marked as stale either privatel depending if `Hash(session-id)` is sent on `/{application-name}/{application-version}/wakunoise/1/sessions/{ct-id}/proto` to the other party in encrypted form or not, respectively. When a Noise session is publicly marked as stale, -network peers MAY discard all [stored](https://rfc.vac.dev/waku/standards/core/13/store) messages addressed to the content topic `/{application-name}/{application-version}/wakunoise/1/sessions/{ct-id}/proto`. +network peers MAY discard all [stored](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/13/store.md) messages addressed to the content topic `/{application-name}/{application-version}/wakunoise/1/sessions/{ct-id}/proto`. In this the case and in order for parties to retrieve any eventually delayed message, peers SHOULD wait a fixed amount of time before discarding stored messages corresponding to a stale Noise session. @@ -150,7 +150,7 @@ This session management mechanism is loosely based on [Signal's Sesame Algorithm # References -- [13/WAKU2-STORE](https://rfc.vac.dev/waku/standards/core/13/store) +- [13/WAKU2-STORE](https://github.com/vacp2p/rfc-index/blob/main/waku/standards/core/13/store.md) - [WAKU2-NOISE](./noise.md) - [The Noise Protocol Framework](http://www.noiseprotocol.org/noise.html) - [The Sesame Algorithm: Session Management for Asynchronous Message Encryption](https://signal.org/docs/specifications/sesame/)