I support Joseph's proposal and plan to add it to our implementation.
Regards, Daniel. -- __________________________________________________ Daniel Gavelle, Software Team Leader Low Power RF Solutions (formerly Jennic Ltd.) NXP Semiconductors Furnival Street, Sheffield, S1 4QT, UK Tel: +44 114 281 2655 Fax: +44 114 281 2951 Comp Reg No: 3191371 - Registered In England http://www.nxp.com http://www.jennic.com __________________________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Reddy, Joseph Sent: 21 April 2011 17:15 To: '[email protected]' Subject: Comment on rpl-routing-header draft ( resending as original post didn't go through... ) Hi, I have a comment on the rpl-routing-header draft that was noticed during interoperability testing conducted by the zigbee alliance. In the most common usage of this header, the border router inserts a source routing header with the full set of intermediate nodes before forwarding it towards the destination within the RPL network. In case of a forwarding error along the route, the intermediate node sends the icmp error message to the source node, however in this case it actually needs to send to the node that inserted the routing header. To fix this issue, the suggestion is that the node that inserts the soruce routing header should include its own address as the first address in the list. This will allow intermediate nodes to send error to it for forwarding failures. -Regards, Joseph
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
