Bug #4511
closed
Failure of RIB register commands within short period of time
Added by Alex Afanasyev about 6 years ago.
Updated almost 3 years ago.
Description
When several applications attempt to register prefixes at the same time, some registration command fails.
- Related to Bug #2174: Multiple register prefix gives NFD error "request timed out (code: 10060)" added
- 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.
So should we reject this issue?
- Assignee deleted (
Muktadir Chowdhury)
- Target version deleted (
Unsupported)
- Related to Feature #5169: nfdc: execute a batch of commands defined in a separate file added
- Category changed from RIB to Management
- Status changed from New to Rejected
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by