Comment # 11
on bug 9217
from Guy Harris
(In reply to comment #10)
> By the way, how does this differ from what's dissected by
> epan/dissectors/packet-s5066.c? That seems to handle a TCP encapsulation
> different from the one your dissector handles; for example, it has a length
> field and a version field, neither of which are mentioned in the STANAG 5066
> 1.0.2 spec that I have.
OK, those are in Annex A of the 5066 spec I have:
As shown in Figure A-1(a), all primitives shall begin with the 16-bit
Maury-Styles sequence shown below, with the least significant bit (LSB)
transmitted first:
(MSB) 1110101110010000(LSB)
Following the Maury-Styles sequence, the next 8 bits shall carry the 5066
version number. For this version of 5066, the version number shall be all
zeros.
The next 16 bits shall carry the size in bytes of the S_primitive to
follow, exclusive of the Maury-Styles sequence, version field, and this size
field. The LSB of the of the size value shall be mapped into the low order bit
of the field.
It appears that the dissector introduced by this patch handles what's described
in Annex C of that spec.
You are receiving this mail because:
- You are watching all bug changes.
