> RPL networks consists of leafs and routers. Both typically act as hosts. > Routers are just hosts that happen to be between other nodes. > (Although, some hosts are too weak to be routers)
OK, I'm not talking of "host" as in originates or terminates traffic, but "host" in the sense of "does not participate in routing". It appears there is no such thing inside a RPL world then. (Note that the traditional usage I'm using here is slightly different from the definition used in RFC2460, which says "does not forward" -- the old 1980's "hosts with RIP routing" would be hosts in RFC2460, but we have learned not to like these monsters. That's why IPv6 has a separate ES-IS protocol called ND.) > Little to no traffic on the RPL is unaware of which RPLinstanceID to > use, because the applications there needs to send using a specific set > of constraints, which is encapsulated into the RPLinstanceID. Hosts (as in "don't participate in routing") would have little idea of such concepts. What you are describing is somehow surprisingly remote from IP. In IP, hosts send packets to an IP address. Sometimes there are additional considerations, which we so far have been addressing [sic] with the TOS byte, i.e., the DSCP today. I don't understand yet why RPL needs a different concept. (Note that Phil's point is also valid, but mostly orthogonal to mine.) Gruesse, Carsten -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
