Project

General

Profile

Feature #4448

Serve other routers' certificates

Added by Muktadir Chowdhury over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
01/09/2018
Due date:
% Done:

100%

Estimated time:

Description

This feature is useful in the case where the certificates required to validate a data packet is not found in the content store. Routers serve other router's LSA, so if the certificate is not present in the server routers content store, the client router will not be able to validate the data. So the server router also need to serve the certificates needed to validate the data packet.
However, when a router is serving other routers' LSA, it needs to send the original data packet that contains the origin router's signature.

So the task can be divided into two parts:
(1) Serving original LSA data packet.
(2) Serving certificates.

Part (1) can be achieved by storing the original LSA data packet when a router gets them from its neighbors. NLSR uses SegmentFetcher to fetch the LSA data, so it needs to connect to the signal emitted by SegmentFetcher when it fetches a data segment. Then NLSR can store the fetched data segment packet whenever there is a signal.

Part (2) can be done by storing the certificate in NLSR's own certificate store.


Related issues

Related to NLSR - Task #4424: Investigate solutions to fetch keys reliably when DirectFetch fails to fetch a key from neighbors' content storeNew12/22/2017

Actions
Related to NLSR - Bug #4430: NLSR does not converge without content storeClosedAshlesh Gawande12/29/2017

Actions
Blocked by ndn-cxx - Feature #4438: Add a signal to SegmentFetcher to notify the reception of a Data segmentClosedMuktadir Chowdhury01/08/2018

Actions
#1

Updated by Muktadir Chowdhury over 2 years ago

  • Related to Task #4424: Investigate solutions to fetch keys reliably when DirectFetch fails to fetch a key from neighbors' content store added
#2

Updated by Muktadir Chowdhury over 2 years ago

  • Related to Feature #4438: Add a signal to SegmentFetcher to notify the reception of a Data segment added
#3

Updated by Muktadir Chowdhury over 2 years ago

  • Related to deleted (Feature #4438: Add a signal to SegmentFetcher to notify the reception of a Data segment)
#4

Updated by Muktadir Chowdhury over 2 years ago

  • Blocked by Feature #4438: Add a signal to SegmentFetcher to notify the reception of a Data segment added
#5

Updated by Ashlesh Gawande over 2 years ago

  • Related to Bug #4430: NLSR does not converge without content store added
#6

Updated by Muktadir Chowdhury over 2 years ago

  • Status changed from New to Closed
#7

Updated by Ashlesh Gawande over 2 years ago

  • Target version set to Minor release 0.4.1
  • % Done changed from 0 to 100

Also available in: Atom PDF