>I *think* we're repeating each other. From my post: Sorry, if I am repeating myself. I agree with you on the following item. All I said, that there's no need to add extra field for originator address and we can change the source MAC address at each lowpan-hop as well. > > > But of course, routing protocols like AODV or LOAD don't use the M bit, > > they have > > originator and destination address fields within the RREQ. > > So we don't even have to require "the routing protocol to provide information > on originator address so that the intermediate node can setup reverse route." > The required info is already in the RREQ, right?
Sure, the required info is within the RREQ. But that assumes we use AODV, LOAD, DYMO etc. which already use RREQ. Since Lowpan layer is not tying up with any particular routing protocol, hence someone in future can try to develop a new routing protocol that might be different than what we expect today at RREQ. Thus, clarifying that requirement will help the implementors today as to how to setup the reverse lowpan-route and lowpan-routing protocol developers in the future. That's all. Thanks, -Samita _______________________________________________ 6lowpan mailing list [email protected] https://www1.ietf.org/mailman/listinfo/6lowpan
