to reply to myself Michael Richardson <[email protected]> wrote: > This will contain a copy of the 16-byte DODAGID so that a very sleepy > node returning to operation would be able to identify which beacon > belongs to which network. A joining node will have no idea which > DODAGID it wants, and a maliciously sent beacon could have any manner > is superfuge here. Nodes which have already joined the network SHOULD > be able to authenticate the beacons. However, this is one of the > larger objects in the 56 bytes that I describe, and maybe it is > excessive to store so many bytes here.
I realized today that the RA probably also needs to carry the ABRO to be
useful to secured hosts. Such hosts will still have to unicast as RS to get
the PIO from a router. I'm sure that we don't want to put the PIO into an
unencrypted EB/RA.
The ARBO has the 6LBR address which is often, but not always the same as the
DODAGID. It can equally well be used to identify the network.
> I want to attempt to apply RFC7400 (GHC) to this, the savings will be
> probably on the order of ten bytes of zeroes.
So far, the savings I got with GHC was 4 bytes. I posted an update to the
git repo. ( https://github.com/ietf-roll/6lo-ra-in-ie )
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
