When inspecting the network transactions between the Agent controller
and the client over a network I noticed that the DIME headers appears to
not be properly formed at all. For example, many of the initial 2 bytes
of the DIME headers would be {0x54, 0xb6} but the DIME specifications
require the first 5 bits to be the version and the last three bits to be
the mb/me/cf flags. Now, if you look at the code in dime.c and dime.h in
the Agent Controller code base, its states that the dime version being
used is 1 (line 22 dime.h), how is 0x54 the first byte of the dime
header if the version of 1 is being used? 0x54 = 1010100b where the it
should look like 00001100b or 00001110b depending if its the first and
last or only the first message in the dime message.
Secondly,
When looking at the data channel of a profile, the first DIME header is
{ 0x51, 0xB6, 0x74, 0xDE ... } where as the subsequent dime headers are
{ 0x01, 0x04, 0x0, 0x0....}. 0x1 doesn't make any sense either as the
first byte in the DIME header. 0x1 = 00000001b, where one would expect
something more like 00001001b where again the version is the first 5
bits and the cf flag is set.
Is this a bug with the TPTP agent controller or am I misunderstanding
something?
Thanks
dimeCapture.pcap <http://www.nabble.com/file/p25722073/dimeCapture.pcap>
attached is a packet capture with the transaction
Ardavon Falls
Lead Software Engineer | MobiTV. TV Anywhere. Anytime.
afa...@mobitv.com | W: +1.510.450.5118
dimeCapture.pcap
Description: dimeCapture.pcap
_______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
