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

[Burke, Jeff]

Hi Junxiao,

Thanks for the explanation.   Both the change to implicit (rather than explicit) segments and versioning and the addition of type tags for name components are significant conceptual changes.  It seems like these should be discussed further before they are implemented; I'll ask Lixia and Beichuan.   Is there some type of design documentation that explains the motivation for the changes?

Thanks,
Jeff

From: Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>>
Date: Sat, 24 May 2014 14:44:54 +0800
To: Jeff Burke <jburke at remap.ucla.edu<mailto:jburke at remap.ucla.edu>>
Cc: "nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>" <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>
Subject: Re: [Nfd-dev] Change to segmenting and versioning conventions?

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/886ca9fe/attachment.html>