FIXME 13 : Integer truncation warning

[eerpini]

Sudhir, check for FIXME 13 on line 77 in rpl/rpldag.c

You will have to pull to get the last two commits.

[kylasa]

Satish,

We can change the RPL_INF_DIST to 255, to get rid of this warning.

I may not be able to meet with you today. I have to meet with a tax consultant reg. my tax returns for this year, this afternoon .

Will call you when I am done with it.

---

I have figured that we can use Path sequence number in the Target Information Option in the DAO message. This path sequence number should be incremented once the lifetime of the path expires. The path lifetime is set by the ROOT, effectively every RPL node should send a DAO message to the ROOT after this interval.

So ROOT node, can monitor the sequence numbers from all the nodes in the RPL Domain. After every expiry of the Path Lifetime interval, it must receive an updated/latest DAO message from every RPL node. If it does not then we can remove that node from the adjacency matrix on the ROOT node.

We need to work on this timer, this is the only thing left out for implementation.

---

Sudhir Kylasa @Purdue

On Apr 8, 2012, at 1:38 PM, satish wrote:

Sudhir, check for FIXME 13 on line 77 in rpl/rpldag.c

---

Reply to this email directly or view it on GitHub: https://github.com/eerpini/Xinu-RPL/issues/1

[kylasa]

Satish,

We can change the RPL_INF_DIST to 255, to get rid of this warning.

Sure, I thought of the same thing, but was not sure if the spec enforced a particular value for INF_DIST or not. I may not be able to meet with you today. I have to meet with a tax consultant reg. my tax returns for this year, this afternoon .

Will call you when I am done with it.

Thats fine.

I have figured that we can use Path sequence number in the Target Information Option in the DAO message. This path sequence number should be incremented once the lifetime of the path expires. The path lifetime is set by the ROOT, effectively every RPL node should send a DAO message to the ROOT after this interval.

So ROOT node, can monitor the sequence numbers from all the nodes in the RPL Domain. After every expiry of the Path Lifetime interval, it must receive an updated/latest DAO message from every RPL node. If it does not then we can remove that node from the adjacency matrix on the ROOT node.

We need to work on this timer, this is the only thing left out for

implementation.

Cool, we can work on this once we meet.

Sudhir Kylasa @Purdue

Cheers Satish

[kylasa]

Sudhir,

I was talking to Bala and the other IPv6 team guys, they have apparently chalked out an api, they said they can meet tomorrow after the CS636 class to discuss it with us. Would be great if you can stop by for a short while.

Satish

Satish,

We can change the RPL_INF_DIST to 255, to get rid of this warning.

I may not be able to meet with you today. I have to meet with a tax consultant reg. my tax returns for this year, this afternoon .

Will call you when I am done with it.

---

I have figured that we can use Path sequence number in the Target Information Option in the DAO message. This path sequence number should be incremented once the lifetime of the path expires. The path lifetime is set by the ROOT, effectively every RPL node should send a DAO message to the ROOT after this interval.

So ROOT node, can monitor the sequence numbers from all the nodes in the RPL Domain. After every expiry of the Path Lifetime interval, it must receive an updated/latest DAO message from every RPL node. If it does not then we can remove that node from the adjacency matrix on the ROOT node.

We need to work on this timer, this is the only thing left out for

implementation.

---

Sudhir Kylasa @Purdue

On Apr 8, 2012, at 1:38 PM, satish wrote:

Sudhir, check for FIXME 13 on line 77 in rpl/rpldag.c

---

Reply to this email directly or view it on GitHub: https://github.com/eerpini/Xinu-RPL/issues/1