Bug #4511

Failure of RIB register commands within short period of time

Added by Alex Afanasyev over 2 years ago. Updated over 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


When several applications attempt to register prefixes at the same time, some registration command fails.

Related issues

Related to NFD - Bug #2174: Multiple register prefix gives NFD error "request timed out (code: 10060)"New11/13/2014


Updated by Alex Afanasyev over 2 years ago

  • Related to Bug #2174: Multiple register prefix gives NFD error "request timed out (code: 10060)" added

Updated by Junxiao Shi over 2 years ago

  • Tracker changed from Task to Bug
  • Description updated (diff)
  • Category set to RIB
  • Target version set to Unsupported
  • Start date deleted (02/19/2018)

I entered the issue description according to 20180219 NFD call. Please update if it's inaccurate.

As I heard from the conference call, these applications are using the same signing key to register prefixes. If they use the same timestamp or the timestamped Interests are received out of order, the validator will reject them. This is explicitly an unsupported scenario as indicated in CommandInterest:

Since public key cryptography is used, sharing private keys is not recommended. If private key sharing is inevitable, it is the key owner's responsibility to keep clock synchronized.

The solution is to use a distinct key for each application.


Updated by Davide Pesavento over 2 years ago

So should we reject this issue?

Also available in: Atom PDF