-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Carsten" == Carsten Bormann <caboc...@gmail.com> writes:
>> 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)
Carsten> OK, I'm not talking of "host" as in originates or
Carsten> terminates traffic, but "host" in the sense of "does not
Carsten> participate in routing".
Carsten> It appears there is no such thing inside a RPL world then.
Yes, by that definition that's perhaps a fair statement!
I prefer to think of each device as being a router, which an attached host.
(the ip_output()/ip_input() parts... are the host, the ip_forward() is
the router...)
>> 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.
Carsten> Hosts (as in "don't participate in routing") would have
Carsten> little idea of such concepts.
Yes, but the *applications* do know about such things.
Carsten> In IP, hosts send packets to an IP address.
You can do that. Your packet might not get there in time. It might
take a much longer route than necessary. It might not get there at all,
if whatever default RPLinstance that exists does not include your destination.
Carsten> Sometimes there are additional considerations, which we so
Carsten> far have been addressing [sic] with the TOS byte, i.e., the
Carsten> DSCP today.
If you prefer, you may think of the RPLinstance as naming something akin
to an MPLS or ATM "circuit", except that it's NBMA-ish tree rather than P2P.
- --
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] m...@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Finger me for keys
iQEVAwUBTGGzfYCLcPvd0N1lAQKcmAf8DlywBcc1Hq3p8WCos9Oj3srsXnfFuEJb
xjWSF7OCbTeAHmP6VYnlNl0BIQCFYonwMFuab4qfdBecbCRcSmegrOWt+SdTAvCJ
CCzhc+8afOaFf5Wp5nf1o2l0JmCjHA8Mvmjb7a95O3ZGSnyxOD53Bzo+I2MQTp5Z
cdo5O8x6RViuxPFKejsLOn8k5PMP+DMjuTXvuGv31x0+q/KaSs34USXyGLiW5s5i
PR827FfSd78pt4V1NzbT55Xrs8ZVAinqNpuLFNbRPWuN60Hymx2Mcr7kLNDW31XW
oUji2nvTeCszohWnDJ8nvLv/G1DU1oTAafxZwCpNnebMxupQjBfGkg==
=c8iq
-----END PGP SIGNATURE-----
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
