From dfe7bc1217a00c23eecb9dfcf1d56fe95ebddc3b Mon Sep 17 00:00:00 2001 From: Kevin Hester Date: Wed, 30 Dec 2020 12:24:39 +0800 Subject: [PATCH] doc updates --- docs/docs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs.md b/docs/docs.md index afd80f7a..6df00a3e 100644 --- a/docs/docs.md +++ b/docs/docs.md @@ -63,7 +63,7 @@ This message wraps a MeshPacket with extra metadata about the sender and how it | ----- | ---- | ----- | ----------- | | packet | [MeshPacket](#MeshPacket) | | The (probably encrypted) packet | | channel_id | [string](#string) | | The global channel ID it was sent on | -| mesh_id | [string](#string) | | The sending mesh. FIXME, is this necessary? can we use this to authenticate/prevent fake nodeid impersonation for senders - i.e. use mesh id (which is authenticated) + local node id as the globally trusted nodenum | +| gateway_id | [string](#string) | | The sending gateway. Can we use this to authenticate/prevent fake nodeid impersonation for senders? - i.e. use gateway/mesh id (which is authenticated) + local node id as the globally trusted nodenum |