Pascal Thubert (pthubert) <[email protected]> wrote: > The non RPL source leaf sends a packet IPHC source = self dest = other leaf.
> The 6LR adds the RPI but the IPHC and whatever comes after it stay
untouched
> and the packet flies to the root.
I think that we went through this in useofrpi....
I read the above sentence to say that the packet format is supposed to be:
IP2 RPI IP1 ULP
which means that the the IP2 must say "6LR" to "Root", which implies that the
6LR knows what the root is. That's an unavoidable interaction between RPL
and the IPv6 forwarding stack, and this is where I claim it's now about
6lowpan, but rather about mesh-over.
I think that for a locally generated packet, a
smart stack doesn't build those headers, but rather speaks directly to the
6LoRH part of the 6lowpan stack, and says:
IPsrc=ME, IPdst=THEM, RPLroot=him
> The root adds IP in IP 6LoRH, the updated RPI and the RH3 6LoRH(s) but
still
> the IPHC and whatever comes after it stay untouched.
The root removes the IP/RPI, and adds IP3/RH3. (We agreed that the RPI is
perhaps unnecessary). IP3 = RPL hop before "THEM", which root knows.
I will read the rest of the text.
--
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
