Project

General

Profile

Task #2965

LSAs should be segmented before they are published

Added by Vince Lehman about 4 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
06/26/2015
Due date:
% Done:

100%

Estimated time:

Description

Currently, each LSA is sent in a single Data packet. If the content that needs to be sent is larger than the max packet size, NLSR will crash.

Instead, each LSA type should be segmented before it is sent.

This task should implement LSA segmentation and LSA segment fetching.

LSA Segment Publisher.docx (144 KB) LSA Segment Publisher.docx Muktadir Chowdhury, 07/27/2015 03:41 PM

Related issues

Related to NLSR - Bug #2337: NameLsa should be segmented when "Data size exceeds maximum limit"Closed2015-01-02

Related to ndn-cxx - Feature #3412: SegmentFetcher: onError signal should report more specific failure informationNew

Blocked by ndn-cxx - Feature #2734: SegmentFetcher: asynchronous Data validation with ValidatorClosed

History

#1 Updated by Vince Lehman about 4 years ago

  • Related to Bug #2337: NameLsa should be segmented when "Data size exceeds maximum limit" added

#2 Updated by Lan Wang almost 4 years ago

  • Assignee set to Muktadir Chowdhury

#3 Updated by Muktadir Chowdhury almost 4 years ago

  • File LSA Segment Publisher.docx added
  • Assignee deleted (Muktadir Chowdhury)

Design document for LSA Segment PUblihser has been added.

#4 Updated by Muktadir Chowdhury almost 4 years ago

  • Assignee set to Muktadir Chowdhury

#5 Updated by Muktadir Chowdhury almost 4 years ago

  • File deleted (LSA Segment Publisher.docx)

#6 Updated by Muktadir Chowdhury almost 4 years ago

  • File LSA Segment Publisher.docx added

#8 Updated by Muktadir Chowdhury almost 4 years ago

  • File deleted (LSA Segment Publisher.docx)

#9 Updated by Vince Lehman almost 4 years ago

A few questions about the design docs:

LSA Segment Publisher:

  • Is SegmentPublisher going to be renamed NlsrSegmentPublisher or are you planning on copying the code?
  • Is certName optional in NlsrSegmentPublisher’s constructor?

LSA Segment Fetcher:

  • Can you describe the four methods that will be needed for LSA Segment Fetcher?
  • Why is a method needed to list all of the LSAs?
  • How will validation of the LSA segments work with the SegmentFetcher?

#10 Updated by Muktadir Chowdhury almost 4 years ago

LSA Segment Publisher:

  • Yes It's going to be renamed with some minor changes(the constructor will take certName parameter and publish() method will sign data with NLSR's identity).
  • I think certName parameter should be compulsory, since its not possible to sign with NLSR's identity without this parameter.

LSA Segment Fetcher:

  • I think only one method will suffice. The method will take "prefix" as a parameter and will send interest for the segments.

#11 Updated by Lan Wang almost 4 years ago

  • Status changed from New to In Progress

#12 Updated by Muktadir Chowdhury almost 4 years ago

  • % Done changed from 0 to 80

#13 Updated by Junxiao Shi almost 4 years ago

  • Blocked by Feature #2734: SegmentFetcher: asynchronous Data validation with Validator added

#14 Updated by Vince Lehman over 3 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 80 to 90

#15 Updated by Ashlesh Gawande almost 3 years ago

  • Related to Feature #3412: SegmentFetcher: onError signal should report more specific failure information added

#16 Updated by Ashlesh Gawande almost 3 years ago

  • Status changed from Code review to Closed
  • % Done changed from 90 to 100

Also available in: Atom PDF