From 474521056b5e458500acba4bfa3b901c3886486d Mon Sep 17 00:00:00 2001 From: Mark Qvist Date: Sat, 2 Jul 2022 08:45:57 +0200 Subject: [PATCH] Updated packet sizes in docs --- README.md | 4 ++-- docs/source/understanding.rst | 18 +++++++++--------- docs/source/whatis.rst | 4 ++-- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 9488196..304184d 100755 --- a/README.md +++ b/README.md @@ -42,8 +42,8 @@ For more info, see [unsigned.io/projects/reticulum](https://unsigned.io/projects - The API is very easy to use, and provides transfer progress - Lightweight, flexible and expandable Request/Response mechanism - Efficient link establishment - - Total bandwidth cost of setting up an encrypted link is 3 packets totalling 237 bytes - - Low cost of keeping links open at only 0.62 bits per second + - Total bandwidth cost of setting up an encrypted link is 3 packets totalling 265 bytes + - Low cost of keeping links open at only 0.44 bits per second ## Examples of Reticulum Applications If you want to quickly get an idea of what Reticulum can do, take a look at the following resources. diff --git a/docs/source/understanding.rst b/docs/source/understanding.rst index a3e827a..942bb49 100644 --- a/docs/source/understanding.rst +++ b/docs/source/understanding.rst @@ -493,10 +493,10 @@ terms of bandwidth, so it can be used just for a short exchange, and then recrea also rotate encryption keys. The link can also be kept alive for longer periods of time, if this is more suitable to the application. The procedure also inserts the *link id* , a hash calculated from the link request packet, into the memory of forwarding nodes, which means that the communicating nodes can thereafter reach each other simply by referring to this *link id*. -The combined bandwidth cost of setting up a link is 3 packets totalling 237 bytes (more info in the +The combined bandwidth cost of setting up a link is 3 packets totalling 265 bytes (more info in the :ref:`Binary Packet Format` section). The amount of bandwidth used on keeping -a link open is practically negligible, at 0.62 bits per second. Even on a slow 1200 bits per second packet -radio channel, 100 concurrent links will still leave 95% channel capacity for actual data. +a link open is practically negligible, at 0.45 bits per second. Even on a slow 1200 bits per second packet +radio channel, 100 concurrent links will still leave 96% channel capacity for actual data. Link Establishment in Detail @@ -795,12 +795,12 @@ Wire Format wire size counting all fields including headers, but excluding any interface access codes. - - Path Request : 33 bytes - - Announce : 151 bytes - - Link Request : 77 bytes - - Link Proof : 77 bytes - - Link RTT packet : 83 bytes - - Link keepalive : 14 bytes + - Path Request : 51 bytes + - Announce : 157 bytes + - Link Request : 83 bytes + - Link Proof : 83 bytes + - Link RTT packet : 99 bytes + - Link keepalive : 20 bytes .. _understanding-announcepropagation: diff --git a/docs/source/whatis.rst b/docs/source/whatis.rst index 1ba9475..f726a4f 100644 --- a/docs/source/whatis.rst +++ b/docs/source/whatis.rst @@ -46,9 +46,9 @@ What does Reticulum Offer? * Efficient link establishment - * Total bandwidth cost of setting up a link is only 3 packets, totalling 237 bytes + * Total bandwidth cost of setting up a link is only 3 packets, totalling 265 bytes - * Low cost of keeping links open at only 0.62 bits per second + * Low cost of keeping links open at only 0.44 bits per second * Reliable and efficient transfer of arbitrary amounts of data