I played with games like that too :)
One option I looked at was to obfuscate the MAC addresses based on ASN
(http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1=HITOFF=PALL=1=/netahtml/srchnum.htm=1=G=50=%279,883,382%27.PN.=PN/9,883,382=PN/9,883,382)
Another was to swap transmissions happening
Hi Jim,
Thanks a million for going through the document. Regarding the problem you
outline where the pledge first joins to JRC1 and then later to JRC2, this
would correspond to the change of ownership of the pledge, without going
through the trouble of re-provisioning the pledge with a new
I think I have found a security problem with the document as it currently
stands. I also have a minor request.
Minor Request:
I think it might be advisable to explicitly state that the derived context,
or at least the last partial IV used is stored in non-volatile storage after
use. (Could just
Hi,
I am very happy to read your draft as I a was recently thinking about
building such a jammer.
Just being a french chauvinist:
randez-vous cells -> rendez-vous cells
Thank you,
On 6/29/18 6:09 PM, Marco Tiloca wrote:
> Hi all,
>
> We have just submitted a new draft proposing a security
Hi all,
We have just submitted a new draft proposing a security solution to
protect 6TiSCH networks from selective jamming.
Feedback and comments are of course very welcome. Thanks a lot!
Best,
/Marco
Forwarded Message
Subject:New Version Notification for
Hi,
I reviewed the ”Minimal Security Framework for 6TiSCH” document.
Here some comments that have not been mentioned by others.
1) I miss some section describing how errors are handled at the cbor level.
This is what if the received Configuration option is wrong, e.g there is an
element in the
