Comment # 39
on bug 8594
from Guy Harris
This has a lot of errors; see bug 11419.
DO NOT EVERY USE ENC_NA FOR A MULTI-BYTE NUMERICAL VALUE. Every such value has
a byte order, so you should use ENC_BIG_ENDIAN if it's big-endian or
ENC_LITTLE_ENDIAN if it's little-endian.
Note also that, according to IEEE Std 802.11-2012 section 8.2.2 "Conventions":
Structures defined in the MAC sublayer are described as a sequence of fields
in specific order. Each figure in Clause 8 depicts the fields/subfields as they
appear in the MAC frame and in the order in which they are passed to the
physical layer convergence procedure (PLCP), from left to right.
In figures, all bits within fields are numbered, from 0 to k, where the
length of the field is k + 1 bits. Bits within numeric fields that are longer
than a single bit are depicted in increasing order of significance, i.e., with
the lowest numbered bit having the least significance. The octet boundaries
within a field can be obtained by taking the bit numbers of the field modulo 8.
Octets within numeric fields that are longer than a single octet are depicted
in increasing order of significance, from lowest numbered bit to highest
numbered bit. The octets in fields longer than a single octet are sent to the
PLCP in order from the octet containing the lowest numbered bits to the octet
containing the highest numbered bits.
so fields are presented to the PLCP in *little-endian* byte order.
You are receiving this mail because:
- You are watching all bug changes.