<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div>Hi Junxiao,</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Jeff</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>><br>
<span style="font-weight:bold">Date: </span>Sat, 24 May 2014 14:44:54 +0800<br>
<span style="font-weight:bold">To: </span>Jeff Burke <<a href="mailto:jburke@remap.ucla.edu">jburke@remap.ucla.edu</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>" <<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Nfd-dev] Change to segmenting and versioning conventions?<br>
</div>
<div><br>
</div>
<div dir="ltr">Hi Jeff
<div><br>
</div>
<div>Applications are allowed to use any number encoding.</div>
<div><br>
</div>
<div><br>
</div>
<div>NDN-TLV 0.2 spec defines <a href="http://named-data.net/doc/NDN-TLV/0.2/name.html" target="_blank">
three component types</a>: NameComponent, NumberComponent, ImplicitSha256DigestComponent.</div>
<div><br>
</div>
<div>Both version number and segment number should use NumberComponent.<br>
</div>
<div>If a Data Name ends with two NumberComponents, it can be assumed versioned and segmented, unless application protocol defines something else.<br>
</div>
<div>If a Data Name ends with one NumberComponent, it can be assumed segmented, unless application protocol defines something else (eg. in
<a href="http://redmine.named-data.net/projects/nfd/wiki/Notification" target="_blank">
NotificationStream</a>, the NumberComponent is a sequence number).</div>
<div><br>
</div>
<div>
<div>ndn-cxx 0.1.0 implements NDN-TLV 0.1, so NumberComponent is encoded as NameComponent.<br>
</div>
</div>
<div>NumberComponent and ImplicitSha256DigestComponent types will be implemented in
<a href="http://redmine.named-data.net/issues/1640">Task 1640</a>.</div>
<div><br>
</div>
<div>Yours, Junxiao</div>
</div>
</span>
</body>
</html>