On Sun, Mar 13, 2011 at 8:11 PM, Guy Harris <[email protected]> wrote: > > On Feb 17, 2011, at 11:41 PM, M.Baris Demiray wrote: > >>> Do they begin with the 16-bit synchronization sequence, or is that stripped >>> off, so that they begin with the header field? Do data PDUs include the >>> CRC at the end, or is that stripped off? >> >> 16-bit synchronization sequence is sent over-the-air for all the types >> of DPDUs so it's not stripped off. And for data PDUs, yes, they >> include CRC at the end. So it's like below for data PDUs, >> >> | SYNC | HEADER | HEADER_CRC | DATA | DATA_CRC | >> >> And like below for control frames (namely DPDU types 1, 3, 5, 6, and 15), >> >> | SYNC | HEADER | HEADER_CRC | > > OK, so would a complete and accurate description be > > D_PDUs as described by NATO standard STANAG 5066, starting > with the synchronization sequence, and including both header and data CRCs. > > and leave it up to those who can access STANAG 5066 to read it (and possibly > provide a link to the old unclassified version)?
Indeed, may be you could also add (along with the link to the old unclassified version) that new versions of STANAG 5066 haven't introduced any alterations to D_PDU headers and the last edition, Edition 3, is totally backward compatible with this old 1.0.2 version; since this would help to encourage those who want to contribute and/or debug without a STANAG 5066 specification at hand. But, with or without this notification, I agree on the definition you wrote. Thanks, > - > This is the tcpdump-workers list. > Visit https://cod.sandelman.ca/ to unsubscribe. -- M. Baris Demiray - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
