Task #2965
closed
LSAs should be segmented before they are published
Added by Vince Lehman almost 9 years ago.
Updated almost 8 years ago.
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.
Files
- Related to Bug #2337: NameLsa should be segmented when "Data size exceeds maximum limit" added
- Assignee set to Muktadir Chowdhury
- File LSA Segment Publisher.docx added
- Assignee deleted (
Muktadir Chowdhury)
Design document for LSA Segment PUblihser has been added.
- Assignee set to Muktadir Chowdhury
- File deleted (
LSA Segment Publisher.docx)
- File LSA Segment Publisher.docx added
- File deleted (
LSA Segment Publisher.docx)
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?
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.
- Status changed from New to In Progress
- % Done changed from 0 to 80
- Blocked by Feature #2734: SegmentFetcher: asynchronous Data validation with Validator added
- Status changed from In Progress to Code review
- % Done changed from 80 to 90
- Related to Feature #3412: SegmentFetcher: onError signal should report more specific failure information added
- Status changed from Code review to Closed
- % Done changed from 90 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by