From 05c69cf788765dea670369b06042c4e8c6aad041 Mon Sep 17 00:00:00 2001 From: Stefan Hagen Date: Thu, 4 Jul 2024 21:18:36 +0200 Subject: [PATCH] Timetravel 2024-06-16 snapshot Signed-off-by: Stefan Hagen --- .../content-autobahn.md | 18 +++++++++--------- .../content-autobahn.md.blake3.txt | 2 +- .../content-autobahn.md.sha256.txt | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md b/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md index 1858b20..ff0bb80 100644 --- a/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md +++ b/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md @@ -1270,7 +1270,7 @@ exchanges using the same Packet Identifiers. > It is possible for a Client to send a PUBLISH packet with Packet Identifier 0x1234 and then receive a different PUBLISH packet with Packet > Identifier 0x1234 from its Server before it receives a PUBACK for the PUBLISH packet that it sent. > -> ![](media/image5.png){width="3.5502898075240594in" height="2.7864588801399823in"} +> ![](media/image11.png){width="3.5502898075240594in" height="2.7864588801399823in"} ## 2.3 MQTT-SN Packet Fields @@ -3708,7 +3708,7 @@ The CONNECT packet contains flags to communicate to the gateway that Auth intera Figure 3a: Connect procedure (without Auth flag not Will flag set or no further authentication data required) -![](media/image7.png){width="3.345165135608049in" height="2.963542213473316in"} +![](media/image1.png){width="3.345165135608049in" height="2.963542213473316in"} Figure 3b: Connect procedure (with Auth flag set and additional authentication data required) @@ -4373,7 +4373,7 @@ Although the implementation of the transparent Gateway is simpler when compared support a separate connection for each active client. Some MQTT server implementations might impose a limitation on the number of concurrent connections that they support. -![](media/image2.png){width="3.994792213473316in" height="2.6661472003499562in"} +![](media/image6.png){width="3.994792213473316in" height="2.6661472003499562in"} Figure XX: Transparent Gateway scenario @@ -4384,21 +4384,21 @@ exchanges between a MQTT-SN client and an aggregating Gateway end at the Gateway the Server. Although its implementation is more complex than the one of a transparent Gateway, an aggregating Gateway may be helpful in case of WSNs with a very large number of SAs because it reduces the number of MQTT connections that the Gateway must support concurrently. -![](media/image11.png){width="4.578125546806649in" height="3.0552755905511813in"} +![](media/image10.png){width="4.578125546806649in" height="3.0552755905511813in"} Figure XX: Aggregating Gateway scenario ### 4.11.3 Forwarder encapsulator -![](media/image12.png){width="4.704773622047244in" height="2.7964599737532807in"} +![](media/image2.png){width="4.704773622047244in" height="2.7964599737532807in"} -Figure XX: Forwarder encapsulator with TransparentGateway scenario![](media/image8.png){width="4.9003171478565175in" height="2.8304625984251968in"} +Figure XX: Forwarder encapsulator with TransparentGateway scenario![](media/image12.png){width="4.9003171478565175in" height="2.8304625984251968in"} Figure XX: Forwarder encapsulator with Aggregating Gateway scenario ### 4.12.4 MQTT-SN broker -![](media/image10.png){width="2.8596172353455818in" height="2.983947944006999in"} +![](media/image7.png){width="2.8596172353455818in" height="2.983947944006999in"} Figure XX: MQTT-SN broker scenario @@ -4490,7 +4490,7 @@ the "Sleeping clients" section. | | state. | | +----------------------------+---------------------------------------------------------------------------------------+------------------------------+ -![](media/image13.png){width="6.5in" height="6.944444444444445in"} +![](media/image9.png){width="6.5in" height="6.944444444444445in"} Figure 4: The Server View of the Client State @@ -4769,7 +4769,7 @@ state by sending a CONNECT packet to the server/gateway. > > The gateway should attempt to make the best effort to reuse the same topic alias mappings that existed during any initial associated ACTIVE states. > -> ![](media/image6.png){width="4.615764435695538in" height="7.453125546806649in"} +> ![](media/image13.png){width="4.615764435695538in" height="7.453125546806649in"} Figure 5: Awake ping packet flush diff --git a/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.blake3.txt b/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.blake3.txt index afb0a59..1dbd91f 100644 --- a/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.blake3.txt +++ b/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.blake3.txt @@ -1 +1 @@ -5b394458f4146a5ced3e6449285d4426dc912668cf2bfe1413adc9b23f2df23f content-autobahn.md +6cb2842b17e57121a496672193ae89800b94c7fd559b16311562f32d4fcc46db content-autobahn.md diff --git a/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.sha256.txt b/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.sha256.txt index d6e04b6..63f2776 100644 --- a/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.sha256.txt +++ b/mqtt-sn-2.0/prose/editorial-content-timetravel/content-autobahn.md.sha256.txt @@ -1 +1 @@ -a39f9455bc8384cc7fb6258fee2e6dd06b178558b3e9ec348c8ccc155279430b content-autobahn.md +796d211b19fff829adee2f7bd18e5fa715a7ca2fe5ccc231143de758320ebb6a content-autobahn.md