Xavier Vilajosana writes:
> We wanted to make a document which is self-contained as now to
> implement 15.4e TSCH you need 15.4 and the 15.4e TSCH amendment
> documents + minimal draft, going back and forth to them (too much
> paper on the table does not leave space for the keyboard).

The current document is nowhere near to be self-contained. You still
need to read 15.4 and 15.4e etc to be able to implement anything. 

> I've seen some emails in the ML of people that is worried about how
> security Keys can be *interpreted* if we allow for example
> well-known keys.

For security keys, the minimal draft does not specify anything how
they are identified in the 802.15.4 level. For the MAC MLME or MCPS
calls you need to give KeyIdMode, KeySource and KeyIndex.

How do you map K1 to those 3 values?

The text does not include anything about how the IEs are actually
formatted inside the MLME nested IE. Or how the IE lists are
terminated. Or it also does not mention that IEEE numbers are in LSB
order etc.

> Well I agree partially, it helps when implementing, which is one of our goals
> (promote adoption of standardized technologies) right? Do you think that there
> is a risk that those IEs change along time?

Most likely no, even when there was some people who complained that
802.15.4 IEs are in LTV format not in TLV format, and they wanted to
ues the last frame version to fix that (i.e. the IE formats for 0b10
DATA etc frame types would not have changed, but we would have added
new frame version 0b11 for DATA etc frame types whcih would use
different IE format).

This was discussed in during the maintenance work, and it was decided
that we do not do this change. If we ever end up changing the frame
format again and need to use the last frame version, then this might
be discussion whether we should fix that at that point, but I
personally do not think there is so much difference whether it is LTV
or TLV to make such change.
-- 
[email protected]

_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to