Erik,
The ttl check is on the receiver. All of RFC 4861 says that a ND message (NS, NA, RS, RA, redirect) with ttl != 255 must be discarded by the receiver. The multi-hop DAD use of NS/NA in 6lowpan-nd is an exception to that.
Some stacks have the rule that any message with a TTL of 255 should never be forwarded on transmit. Also a TTL of 255 will remain in the network for a long time if there is a loop. I think it would be better if the multi-hop messages were sent with a smaller TTL (e.g. 64) rather than 255. The exception on receive you mention would still be required. Daniel. -- __________________________________________________ Daniel Gavelle, Software Engineer Tel: +44 114 281 2655 Fax: +44 114 281 2951 Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK Comp Reg No: 3191371 Registered In England http://www.jennic.com __________________________________________________ _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
