Feature #3773
open
Inform applications when auto prefix propagation fails because no signing identity is available
Added by Jeff Burke about 8 years ago.
Updated over 6 years ago.
Description
It appears that auto prefix propagation fails silently from an application perspective if, for example, the appropriate signing identity isn't available for the prefix. Is there / can there be feedback to the application?
Related issues
1 (1 open — 0 closed)
- Tracker changed from Task to Feature
- Subject changed from Inform applications with auto preix propagation fails because no signing identity is available to Inform applications when auto prefix propagation fails because no signing identity is available
- Category set to RIB
After #3145, an application should be able to request a routable prefixes dataset from local NFD-RIB.
Prefixes in this dataset are assured that (1) there is a signing identity for auto prefix propagation (2) it falls under a prefix advertised via routing protocol on the connected router.
Through this dataset, an application can know in advance whether a prefix registration would be propagated, and notifications are unnecessary.
#3145 does not cover situations when the signing identity exists but is rejected by the connected router, for example when the certificate is invalid, expired, or otherwise not trusted by the router.
Those situations are not covered by the requested feature of "inform applications when .. no signing identity is available".
#3144-4 has a proposal to provide feedback to application on whether a prefix propagation is in progress, successful, or failed.
However, that proposal has been rejected in #3144-5.
- Related to Feature #3145: Collect and publish routable-prefixes added
- Start date deleted (
09/11/2016)
Also available in: Atom
PDF
Updated by 
Updated by