[Nfd-dev] NFD RIB Daemon - trigger FIB updates from RIB

[Junxiao Shi]

Dear folks

The only reasons for FIB update failures are: (a) authentication error; (b)
face is closed; (c) timeouts.

   - Authentication error (RIB Daemon's certificate is not trusted by NFD)
   is not recoverable, so RIB Daemon should crash.
   - If face is closed, the whole batch is abandoned because all RIB
   updates in the batch are referring to a non-existent face; FIB reversing is
   unnecessary, because FIB will independently delete all NextHop records
   using the closing face.
   - In case of a timeout, the FIB update should be retried until it
   succeeds or has an unrecoverable failure, or until the face is closed.

In any of the above reasons, FIB reversing is unnecessary.

Yours, Junxiao

On Wed, Jun 25, 2014 at 11:25 AM, Lan Wang (lanwang) <lanwang at memphis.edu>
wrote:

>  Just realized one issue: if we really want to be consistent,  then we
> also need to reverse all fib updates that belong to the same rib update if
> any of them fails.  This would require keeping state of the original fib.
>  Also batching rib updates may make this reversal difficult if the fib
> updates for several rib updates to one optimal set.  There may be other
> complexities related to this. Just want to raise awareness.
>
>  Lan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140625/5d12bbb3/attachment.html>