[Nfd-dev] packet format specification

Lan Wang (lanwang) lanwang at memphis.edu
Sat Jan 31 18:18:48 PST 2015


Hi all,

There seems to be some inconsistencies in the packet format specification at 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?

Lan





More information about the Nfd-dev mailing list