Task #4424
open
Investigate solutions to fetch keys reliably when DirectFetch fails to fetch a key from neighbors' content store
0%
Description
When a router receives an LSA, it sends an interest for the signing key back to the face from which the LSA is received. Since the neighbor that sent the LSA has verified the data, it must have retrieved the key and a copy of the key should be in its content store which can satisfy the router’s interest.
However, content store is opportunistic and cannot guarantee this (content could be replaced).
Currently we also use /localhop prefix for LSA - but it is under multicast strategy so situation is a little better.
We can restore the broadcast key prefix as earlier.
Long term solution is to have insert the keys and LSA into a local repo so other router's can retrieve independent of cache or nlsr.
Updated by
Updated by Lan Wang almost 7 years ago
- Subject changed from Investigate alternatives to DirectFetch to Investigate solutions to fetch keys reliably when DirectFetch fails to fetch a key from content store
Updated by Lan Wang almost 7 years ago
- Subject changed from Investigate solutions to fetch keys reliably when DirectFetch fails to fetch a key from content store to Investigate solutions to fetch keys reliably when DirectFetch fails to fetch a key from neighbors' content store
Updated by Muktadir Chowdhury almost 7 years ago
We agreed on the solution where whenever a router receives a LSA data from its neighbors, it will store the certificates needed to validate that data packet. So, a router can serve other routers' LSA data along with the certificates needed to validate it.
Updated by Muktadir Chowdhury almost 7 years ago
- Related to Feature #4448: Serve other routers' certificates added
Updated by Saurab Dulal over 5 years ago
- Related to Feature #4868: Insert the keys and LSA into a local repo so other router's can retrieve independent of cache or nlsr added
Updated by Saurab Dulal almost 4 years ago
- Target version changed from v0.6.0 to 0.7.0