Would you please publish to the MANET list? Unless, of course, there's a
lack of consensus as to the milestones (or the dates) from amongst the
author team.
Regards,
Stan
On Tue, Apr 14, 2015 at 1:19 PM, Victoria Mercieca <vmercieca0@xxxxxxxxx>
wrote:
I dont think it went out to MANET...
Regards,
Vicky.
On Tue, Apr 14, 2015 at 6:02 PM, Stan Ratliff <ratliffstan@xxxxxxxxx>
wrote:
Sorry, but this is off-topic.
Did we ever publish interim goals (with dates) to the MANET mailing list?
Regards,
Stan
On Mon, Apr 13, 2015 at 5:37 PM, Lotte Steenbrink <
lotte.steenbrink@xxxxxxxxxxxx> wrote:
Hi folks,
I'm revisiting my code that checks whether a route update offers
improvement right now, and imho the “To briefly summarize, ..” Part of
section 8.1. is a bit misleading, since it doesn't cover all the cases
clearly (and being lazy, I used it as my only reference first). Therefore,
I'd propose to remove the following paragraphs:
To briefly summarize, AdvRte must satisfy the following conditions
compared to the existing route table entry before it can be used:
o AdvRte is more recent, (i.e., AdvRte.SeqNum > Route.SeqNum) OR
o AdvRte is not stale and can safely restore an invalid route (i.e.
LoopFree (AdvRte, Route) == TRUE), OR
o AdvRte is not stale and is less costly.
Regards,
Lotte