Pascal Thubert (pthubert) <[email protected]> wrote: > This is a short draft, but the work is much needed to complete the RPL > story on non-RPL-aware leaves. The draft conforms to the long-standing > expectations from the 6TiSCH architecture.
1) can you add a reference for "Routing Stretch"?
2) Alternatively, the 6LN may rely on its 6LR to perform routing and
forwarding on its behalf. In the context of RPL, such a 6LN is
-> if you want to give an example of such a node, I think that the window
smash sensor (alarm system), or the kinetically powered light switch,
are two good examples.
{I wish I had links to real products that actually ran RPL.}
section 3:
s/ Upon the renewal of a registration, this specification changes the
behavior or the 6LR.
/ Upon the renewal of a 6lowPAN ND registration, this specification
changes the
behavior of the 6LR. /
The rest of that paragraph is ver hard to parse.
section 4:
should:
This document specifies a new flag in the EARO option, the 'R' flag,
used by the registering node to indicate that the 6LN that performs
the registration is a router and that it handles its reachability.
say:
This document specifies a new flag in the EARO option, the 'R' flag,
used by a 6LN, when registering, to indicate that this 6LN
is a router and that it will handles its own reachability.
(...By sending a DAO)
The rest of the document has some difficult sentences too.
--
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
