[Nfd-dev] Change to segmenting and versioning conventions?

Junxiao Shi shijunxiao at email.arizona.edu
Fri May 23 23:44:54 PDT 2014


Hi Jeff

Applications are allowed to use any number encoding.


NDN-TLV 0.2 spec defines three component
types<http://named-data.net/doc/NDN-TLV/0.2/name.html>:
NameComponent, NumberComponent, ImplicitSha256DigestComponent.

Both version number and segment number should use NumberComponent.
If a Data Name ends with two NumberComponents, it can be assumed versioned
and segmented, unless application protocol defines something else.
If a Data Name ends with one NumberComponent, it can be assumed segmented,
unless application protocol defines something else (eg. in
NotificationStream<http://redmine.named-data.net/projects/nfd/wiki/Notification>,
the NumberComponent is a sequence number).

ndn-cxx 0.1.0 implements NDN-TLV 0.1, so NumberComponent is encoded as
NameComponent.
NumberComponent and ImplicitSha256DigestComponent types will be implemented
in Task 1640 <http://redmine.named-data.net/issues/1640>.

Yours, Junxiao
​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140524/ea94ef91/attachment.html>


More information about the Nfd-dev mailing list