RE: OpenThread CoAP Multicast Message ID

Edvin — Wed, 05 Aug 2020 11:39:39 GMT

Hello,

Following is the reply from our Thread Team:
--

The OpenThread CoAP implementation does not provide a reliable way of fetching the CoAP Message ID after it is sent.

With this PR:

https://github.com/openthread/openthread/pull/3419

the way of handling extra CoAP information such as Message ID was changed. Previously such information was kept in the CoAP Header structure, but right now it is kept in unused space in the Message Buffer itself.

To give you a better understanding, the Message Buffer may contain a few headers i.e:

| IPv6 Header | MPL Header | UDP Header | CoAP Header | Payload |

When a CoAP message is created, it allocates only space for CoAP and UDP Headers, and reserves space to prepend lower-layer headers:

| Reserved                 | UDP Header | CoAP Header | Payload |

(Reserved takes up the space of IPv6 Header and MPL Header)

The current CoAP implementation takes advantage of that, and puts temporarily needed information in the reserved space, because those are needed only to construct the CoAP message):

| CoAP Helper Data         | UCP Header | CoAP Header | Payload |

After the packet is sent to the IP layer, the Reserved space is filled with the IPv6 (and for FF03::1 also MPL Header).

This effectively overwrites the CoAP Helper data (which includes the Message ID).

Luckily (but not on purpose), the Message ID is at the top of the CoAP Helper Data, and if the MPL Header is not used, then the CoAP Message ID information persists.

In case the MPL Header is inserted it fully overwrites the CoAP Message ID as well.

Why do you need to know what the Message ID of the CoAP message is? In the CoAP implementations I know this is always handled internally.

If you need a workaround, you can increase the reserved space allocated by the IP layer to prevent the CoAP Helper Data (Message ID) being overwritten. For example:

diff --git a/src/core/net/ip6.cpp b/src/core/net/ip6.cpp
index d85dfb13e..0a1a72756 100644
--- a/src/core/net/ip6.cpp
+++ b/src/core/net/ip6.cpp
@@ -70,7 +70,7 @@ Ip6::Ip6(Instance &aInstance)
 Message *Ip6::NewMessage(uint16_t aReserved, const Message::Settings &aSettings)
 {
     return Get<MessagePool>().New(Message::kTypeIp6,
-                                  sizeof(Header) + sizeof(HopByHopHeader) + sizeof(OptionMpl) + aReserved, aSettings);
+                                  sizeof(Header) + sizeof(HopByHopHeader) + sizeof(OptionMpl) + aReserved + sizeof(uint32_t), aSettings);
 }

Best regards,

Edvin

RE: OpenThread CoAP Multicast Message ID

Edvin — Tue, 04 Aug 2020 12:50:53 GMT

Hello,

Sorry for the late reply. I was on vacation the last 14 days.

I have not received a reply on my internal ticket, unfortunately. I will ping it.

Did you try to debug into getMessageID() to see why the returned ID was wrong?

BR,

Edvin

RE: OpenThread CoAP Multicast Message ID

Rouben — Thu, 30 Jul 2020 09:00:13 GMT

Hello Edvin

Thank you for your support.

I was not able to find a solution. Do you have any news regarding this issue?

Best regards,

Rouben

RE: OpenThread CoAP Multicast Message ID

Edvin — Mon, 13 Jul 2020 14:57:36 GMT

Hello Roiben,

This looks a bit like a bug. I can see the message ID on the sniffer trace, so there is no reason why the client shouldn't already have this ID at the time when it transmit it. I will have to double check this with our Thread team. I will let you know when I hear something from them. Please note that some additional delay may be expected due to summer holidays.

You can of course look at the implementation of this message, since you have already built the latest version, you have access to the source code.

Best regards,

Edvin