Project

General

Profile

Actions
Copy link

Bug #2461

closed

FinalBlockId contradictions

Added by Junxiao Shi about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Minsheng Zhang
Start date:
Due date:
% Done:

100%

Estimated time:
1.50 h

Description

In http://named-data.net/doc/ndn-tlv/data.html#metainfo,
FinalBlockId is an optional field of MetaInfo in the definition, but the following two statements suggest otherwise:

If both ContentType and FreshnessPeriod are optional, one may consider Metainfo itself should be optional. But would have all 4 parts of Data packet help simplify implementation? We leave this question to people who are more familiar with high speed implementations.

add FinalBlockId after FreshnessPeriod?

Timestamp and FinalBlockID can be useful meta information for applications, but do not need to be processed at the network layer. Therefore, if desired, applications should encode such meta information as part of the content.

This is a remnant of previous version of the specification that argues why FinalBlockID should not be part of MetaInfo. Remove FinalBlockID from this statement?

Actions
Copy link

Also available in: Atom PDF