Subject: [6lowpan] Multihop DAD message types in 6lowpan-nd

From: Zach Shelby <[email-masked]>
Date: Fri, 22 Oct 2010 00:00:45 +0300

Hi,

Several issues around multihop-DAD messages have been brought up during LC. After discussions between the authors, and with chairs and implementors, we have come to the conclusion that the Multihop-DAD messages need to be assigned their own messages rather than piggybacking on NS/NA and re-using ARO. This will solve some problems already brought up on the list and plenty of confusion. The mechanism would be the same, however new messages would carry the information currently in the multihop-DAD ARO option in their headers. We plan on integrating this change in 6lowpan-nd-14 planned for submission by the Oct 25th cutoff. Any objections? 

Regards,
Zach, Erik and Samita

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297