Dear Xavi:

I think that if we indicate a bit setting, it must be against a particular 
version of the IEEE spec where the bits are defined, in this case 4e-2012.

The document would then state that for further versions of the document where 
the formatting is unknown at this time, the natural bit setting to obtain the 
same result is to be used. Unsure how to word that though.

Cheers,

Pascal

From: 6tisch [mailto:[email protected]] On Behalf Of Xavier Vilajosana
Sent: mardi 21 juillet 2015 19:47
To: [email protected]
Subject: [6tisch] comments on 15.4 header fields in minimal

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]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to