Project

General

Profile

Task #1326

Delete expired RIB entries

Added by Syed Amin over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
RIB
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

Write a callback that can delete the nexthops of the expired entries.


Related issues

Related to NFD - Task #1717: Route expiration test scenarioClosed

Blocked by NFD - Task #1271: RIB stores as a trieClosed

Blocked by NFD - Task #1727: nfdc: Default value for expirationPeriod should be time::milliseconds::max()Closed2014-07-01

History

#1 Updated by Alex Afanasyev over 5 years ago

  • Category set to RIB
  • Target version set to v0.2

#2 Updated by Junxiao Shi over 5 years ago

  • Subject changed from Deletion of expired entries. to Delete expired RIB entries
  • Start date deleted (03/07/2014)
  • Parent task deleted (#1271)

#3 Updated by Syed Amin over 5 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

#4 Updated by Syed Amin over 5 years ago

  • % Done changed from 20 to 90

#5 Updated by Syed Amin over 5 years ago

  • Status changed from In Progress to Code review

#6 Updated by Syed Amin over 5 years ago

  • Parent task set to #1271

#7 Updated by Syed Amin over 5 years ago

  • Parent task deleted (#1271)

#8 Updated by Syed Amin over 5 years ago

  • Blocked by Task #1271: RIB stores as a trie added

#9 Updated by Junxiao Shi over 5 years ago

A proposal about which component should generate FIB updates is sent to nfd-dev list.

http://www.lists.cs.ucla.edu/mailman/private/nfd-dev/2014-June/000217.html

I invite watchers of this Task to have a look.

#10 Updated by Syed Amin over 5 years ago

The proposed changes should be a separate task and should be targeted for the next version, otherwise it may delay the release of v0.2 further. By that time the relevant fib update task would have been completed as well. For now if we don't have any other issue besides moving rib-expiration logic to the Rib, then I think the code we have currently can be accepted?

#11 Updated by Beichuan Zhang over 5 years ago

the route expiration is actually a small issue. the bigger one is how to handle FIB update failure in general. that part is needed for this version. i summarized my understanding in the email.

#12 Updated by Junxiao Shi over 5 years ago

  • Related to Task #1717: Route expiration test scenario added

#13 Updated by Alex Afanasyev over 5 years ago

While looking into http://gerrit.named-data.net/#/c/911/ I realized a big problem with this commit, unless I'm mistaken.

It will expire all manually created entries using nfdc within 1 hour, as it is for some reason "default" expiration period if not overridden with -e option. This applies to all manually created routes with nfdc.

The protocol itself is also a little ambiguous on the issue: http://redmine.named-data.net/projects/nfd/wiki/RibMgmt#Register-a-route
It only defines that expiration period should be "practically" infinity when FaceId is omitted, otherwise it is still 1 hour. What is "practically" and why it cannot be actually infinity (in a sense that we don't set up timers for such entry)?

Why 1 hour? If we submit this commit, how static routes can work? Why expiration lifetime for statically created routes is not defaulted to infinity?

#14 Updated by Alex Afanasyev over 5 years ago

  • Blocked by Task #1727: nfdc: Default value for expirationPeriod should be time::milliseconds::max() added

#15 Updated by Alex Afanasyev over 5 years ago

  • Status changed from Code review to Closed
  • % Done changed from 90 to 100

Also available in: Atom PDF