The message from Joseph Reddy is important and makes sense.

I have a remark to that message as well: when the RH is built as you suggest (BR inserts is own address in the RH (the one on which interface? an ll address?)) it may be questionable about how the AH authentication header is applied to it.

BEcause - we do not have a specification about how to apply AH on RH5 (although we do know how to apply AH on other RHs).

But we do have example text suggesting how to apply AH on RH5.

The RH5 is currently specified at:
http://www.ietf.org/id/draft-ietf-6man-rpl-routing-header-03.txt

The example text suggesting applying AH on RH5, in the RoLL WG email archives, somewhere sept or october 2010.

Alex

Le 21/04/2011 18:15, Reddy, Joseph a écrit :
( 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
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to