Firstly, the secret squirrel is a page that shouldn’t have been in this document
Secondly, agreed, TSCH operation should focus on version 2 only due to the need for IEs. Finally, given your intent to use long addresses with the destination PANID, the PANID compression bit should be set to 0 Pat Pat Kinney Kinney Consulting LLC IEEE 802.15 WG vice chair, TG chair ISA100.11a WG chair O: +1.847.960.3715 [email protected] <mailto:[email protected]> On 22, Jul2015, at 4:27, Xavier Vilajosana <[email protected]> wrote: Hi, Pat, all what is the secret squirrel? :) In minimal we want to enforce a specific header configuration which enables us to use long addresses, keeping the presence of the sequence number and having only destination PANID. With the proposed text we do not specify any specific configuration from any of the tables in 15.4 (any version). Vendors will need to look into the spec they are implementing (either 2012 or 2015) and choose the appropiate configuration. IMHO, this is the most general approach we can take as if the implementations are compliant with our requirements they will be able to interoperate. As for frame version we can enforce version 2 since we need IEs in most of the cases (at least for minimal -- and please take into account the purpose of minimal --). From the attached document what we need is (row 7) Extended Extended Present Not Present 0 regards, Xavi 2015-07-22 8:26 GMT+02:00 Pat Kinney <[email protected] <mailto:[email protected]>>: As per our 6tisch meeting yesterday concerning the PAN ID compression bit table, I have attached an IEEE 802.15 document showing the changes to the latest revision draft. This document will act as guidance to the Technical Editor to modify the revision draft. In summary, it was agreed that frames of version numbers “0” or “1" should revert to the instructions stated in IEEE 802.15.4-2011. For frame version “2", new text will be inserted into the revision declaring the rules in a non-ambiguous fashion. I would ask those interested in setting the header bits to read this document and respond with critiques or questions. Thanks, Pat Pat Kinney Kinney Consulting LLC IEEE 802.15 WG vice chair, TG chair ISA100.11a WG chair O: +1.847.960.3715 <tel:%2B1.847.960.3715> [email protected] <mailto:[email protected]> On 21, Jul2015, at 12:46, Xavier Vilajosana <[email protected] <mailto:[email protected]>> wrote: Hi, From the discussion today, the section mandating the use of certain 2012 specific configuration needs to be changed so we can be independent to the evolution of the 15.4 spec. The current text is: The IEEE802.15.4 header of all frames MUST include the Sequence Number field, the Source Address field and the Destination Address field. In the Frame Control Field, this translates to: the Frame Version field MUST be set to 0b10 (Frame Version 2) the Sequence Number Suppression bit MUST be set to 0b0 the Source Addressing Mode MUST set to 0b11 (long address) the Destination Addressing Mode MUST set to 0b11 (long address) except for the broadcast address for which Destination Addressing Mode SHOULD set to 0b10 (short address). The use of long addresses is a REQUIRED as no association procedure is defined in this document. the PAN ID Compression bit MUST be set to 0b0. According to the Table 2a in IEEE802154-2012 this translates into the Destination PAN ID field being "Present" and the Source PAN ID field being "Not Present". I propose the following text which I think is aligned with what has been commented during the discussion. The IEEE802.15.4 header of all frames MUST include the Sequence Number field, the Source Address field and the Destination Address field and only the Destination PANID. Source and destination address fields MUST be filled with an extended address (64 bit) and this be indicated in the corresponding Frame Control field. In case of a destination broadcast address, the address field MUST be filled by a short addresses (16bit). The Destination PANID MUST be present and the Source PANID MUST be elided. Would that work? regards, Xavi _______________________________________________ 6tisch mailing list [email protected] <mailto:[email protected]> https://www.ietf.org/mailman/listinfo/6tisch <https://www.ietf.org/mailman/listinfo/6tisch> _______________________________________________ 6tisch mailing list [email protected] <mailto:[email protected]> https://www.ietf.org/mailman/listinfo/6tisch <https://www.ietf.org/mailman/listinfo/6tisch>
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
