On 10/13/10 05:30 AM, Daniel Gavelle wrote:
When the multi-hop NS is sent from the LR to the LBR, its hop limit is
set to 255 and then decremented on each hop. When it arrives at the LBR,
the hop limit=255 check is ignored. There are a couple of problems with
this mechanism:-
(1) If the packet enters a routing loop, it will take a long time to die.
(2) Some stacks have a rule that packets with a hop limit of 255 should
never be forwarded by the routing layer or a hop limit of 254 should
never be transmitted.
These problems could be addressed by setting the hop limit to a more
typical value, e.g. 64, for the multi-hop messages.
I don't have a problem suggesting a value like 64.
But the implementations in (2) seems to be utterly broken because there
isn't any RFC that says that packets with 255 or 254 should be treated
differently when transmitting or forwarding.
Erik
_______________________________________________
6lowpan mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lowpan
