José Ángel Miranda writes: > >5.2.4.22 IE List Termination IE > > The Header IE list is terminated with an IE List Termination > IE (ID = 0x7e or 0x7f) that has a content length of zero.
The first sentence says that Header IE list is terminated. That does not list any exceptions. > Explicit termination is required after a Header IE if there is > one or more Payload IEs (0x7e), or MAC payload (0x7f), > following the Header IE list. If an unformatted payload This second sentence gives enforces the first rule, i.e. explicit termination is required if there is anything after the Header IE list, i.e. either payload IEs, or MAC payloads. > follows the Payload IE list, then the payload IE list is > terminated with a list termination IE (ID = 0xf) that has a > content length of zero. Otherwise the terminator may be > omitted. So that otherwise only covers the case where there is nothing after the header IE (i.e. no payload IEs, and no MAC pyload), or nothing after payload IE (i.e. no MAC payload). This text does not give any exception that Header IE termination could be omitted if you do not have any header IEs, or if the payload is unencrypted. > Once more, taking the Beacon which is showed in the minimal > document, there you have a beacon which contains: > - Header IEs not present. > - Payload IEs present and not encrypted ( In the current standard > the IEs Payload within the beacon are not encrypted, please see > table 53 from the standard where it is specified that the private > payload is the Beacon payload and not the entire MAC payload ). Table 53 was not updated in the 4e even when it should have been. This was one of the issues we found while making the 802.15.4rev, and this was fixed there following the instructions from implementors and people who wrote the 4e. Also the section 5.2.1.7a clearly states that payload IEs are part of MAC payload, and they may be encrypted (i.e. if security level is >= 4). > - Beacon payload not present. > So, what is the need to add a Header IE termination list? There is > not. It needs to be added as 5.2.4.22 says that Header IE list is terminated when there is payload IEs after it. Yes, some other protocol defining IEs, could have defined IEs in such way that some of those termination IEs can be left out, but 802.15.4e did not do that. -- [email protected] _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
