https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232015-04-21T12:47:24ZNDN project issue tracking systemNFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=96702015-04-21T12:47:24ZJunxiao Shi
<ul><li><strong>File</strong> <a href="/attachments/301">NDNLPv2_20150417.pptx</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/301/NDNLPv2_20150417.pptx">NDNLPv2_20150417.pptx</a> added</li></ul><p>20150420 conference call approved the design of listed features in NDNLPv2_20150417.pptx.<br><br>
Other features are not yet approved, and are not part of this Task.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=96752015-04-21T17:34:35ZDavide Pesavento
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-3 priority-high3 closed" href="/issues/2520">Feature #2520</a>: NDNLPv2 high-level design</i> added</li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=98762015-05-09T09:42:44ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=98772015-05-09T10:17:46ZJunxiao Shi
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>Wiki page is created: <a class="wiki-page" href="https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2">NDNLPv2</a></p>
<p>The content is currently embedded from <a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93" class="external">Gist</a> for better version control during initial writing.<br>
It will be copied to Redmine wiki when final version (including all NDNLPv2 features) are complete.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=98952015-05-11T15:42:09ZJunxiao Shi
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>60</i></li></ul><p>Fragmentation is written.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=99062015-05-12T11:51:04ZJunxiao Shi
<ul><li><strong>Category</strong> changed from <i>Docs</i> to <i>Protocol</i></li><li><strong>% Done</strong> changed from <i>60</i> to <i>70</i></li></ul><p>NACK is written.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=99532015-05-15T13:44:05ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>70</i> to <i>100</i></li></ul><p><a class="wiki-page" href="https://redmine.named-data.net/projects/nfd/wiki/LocalControlHeader">LocalControlHeader</a>-equivalent field (NextHopFaceId CachingPolicy IncomingFaceId) are complete.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=100562015-05-24T10:23:11ZJunxiao Shi
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-2 status-5 priority-2 priority-default closed" href="/issues/2531">Feature #2531</a>: LocalControlHeader</i> added</li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=101542015-05-28T04:58:49ZJunxiao Shi
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-3 status-5 priority-3 priority-high3 closed" href="/issues/2841">Task #2841</a>: NDNLPv2 design: packet format API for NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceId</i> added</li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=103532015-06-08T10:27:04ZJunxiao Shi
<ul></ul><p>Answer to <a class="issue tracker-3 status-5 priority-3 priority-high3 closed" title="Task: NDNLPv2 design: packet format API for NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFa... (Closed)" href="https://redmine.named-data.net/issues/2841">#2841</a> note-13:</p>
<blockquote>
<p>Can we call "NdnlpHeaderExtension" a "Feature"?</p>
</blockquote>
<p>No, they are distinct concepts.<br><br>
A <strong>feature</strong> can have zero or more header extensions (and trailer extensions).<br><br>
For example, indexed fragmentation feature defines two HeaderExtensions: <code>NdnlpFragIndex</code> and <code>NdnlpFragCount</code>.</p>
<blockquote>
<p>Why don't we call "Nack" as "NackReason" or just "Reason". The description already calls it this way. For "DuplicataNack" and "GiveUpNack" I would lose "Nack" suffix. Why NACK reason should have "Nack" in it's name?</p>
</blockquote>
<p>Agreed.</p>
<blockquote>
<p>Why NdnlpPacket is assigned code 100 (0x64)?</p>
</blockquote>
<p>This is to avoid clashing with <a class="wiki-page" href="https://redmine.named-data.net/projects/nfd/wiki/NDNLP-TLV">NDNLP-TLV</a> and <a class="wiki-page" href="https://redmine.named-data.net/projects/nfd/wiki/LocalControlHeader">LocalControlHeader</a>, both of which use <code>80</code> as TLV-TYPE code for top-level element.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=103922015-06-09T14:10:50ZJunxiao Shi
<ul></ul><p>20150608 conference call reviewed <a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93/" class="external">revision 213b5818fefc773902728e66d5685cebf883f106</a>.<br><br>
Some comments are:</p>
<ul>
<li>The <code>Ndnlp</code> prefix on all types are unnecessary, because the design is in NDN context.
However, <code>Lp</code> prefix should appear on some types, because the "namespace" of TLV-TYPE declarations is flat, and <code>Lp</code> is necessary to distinguish the type as part of NDNLPv2.</li>
<li>Currently there are only 21 TLV-TYPEs reserved for link protocols, which would be insufficient according to the roadmap of NDNLPv2.
We decide to reserve a block of TLV-TYPEs in 3-octet range for link protocols, and assign 3-octet codes to less common fields.</li>
<li>The concept of <code>HeaderExtension</code> is confusing.
It shall be renamed as <code>HeaderField</code>.</li>
<li>It's unnecessary to let <code>Sequence</code> stand out.
Instead, it could be one choice of HeaderField.</li>
<li><code>HeaderField</code>s under a header should be sorted in increasing TLV-TYPE order, so that there's only one way to encode a packet.</li>
<li><code>NdnlpHeader</code> and <code>NdnlpTrailer</code> wrappers are wasting octets.
Those wrappers should be dropped, in favor of letting header and trailer fields appear directly under <code>LpPacket</code> struct.</li>
</ul>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=103942015-06-09T14:12:08ZJunxiao Shi
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-3 status-5 priority-2 priority-default closed" href="/issues/2866">Task #2866</a>: Reserve TLV-TYPE codes for NDNLPv2</i> added</li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=104002015-06-09T16:26:31ZJunxiao Shi
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/10400/diff?detail_id=9394">diff</a>)</li></ul><p>Document is updated according to note-11.</p>
<p><a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93/0f51ccaf533e23f645f87893dfada67eb63d0274">https://gist.github.com/yoursunny/92d8c3514476be6a7b93/0f51ccaf533e23f645f87893dfada67eb63d0274</a></p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=104462015-06-10T20:41:44ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>20150610 conference call approved this portion of the design.</p>
<p><a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93/ffc631fd6397840adda1b6f3a74b38f431116fea">https://gist.github.com/yoursunny/92d8c3514476be6a7b93/ffc631fd6397840adda1b6f3a74b38f431116fea</a></p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=105562015-06-12T13:44:56ZJunxiao Shi
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-2 priority-default closed" href="/issues/2222">Feature #2222</a>: NDNLPv2 design: link service</i> added</li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=105612015-06-12T13:53:03ZJunxiao Shi
<ul><li><strong>Subject</strong> changed from <i>NDNLPv2: NACK, Fragmentation, LocalControlHeader</i> to <i>NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachingPolicy, IncomingFaceId</i></li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=105632015-06-12T13:53:16ZJunxiao Shi
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-5 priority-2 priority-default closed" href="/issues/2883">Task #2883</a>: NDNLPv2 design: NACK in client Face</i> added</li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=107842015-06-21T21:17:33ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>100</i> to <i>80</i></li></ul><p><a href="http://redmine.named-data.net/issues/2877#note-29">http://redmine.named-data.net/issues/2877#note-29</a></p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=107872015-06-21T21:38:57ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p><a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93/c2213a318211cf0980b19bb174c7a835ac51d186">https://gist.github.com/yoursunny/92d8c3514476be6a7b93/c2213a318211cf0980b19bb174c7a835ac51d186</a></p>
<p>This revision takes some design from <a href="https://gist.github.com/cawka/f8bb5f558568f06c78ca/f552c86630eb07579b85849f3108d32bfa2340e6">https://gist.github.com/cawka/f8bb5f558568f06c78ca/f552c86630eb07579b85849f3108d32bfa2340e6</a>, with the following differences:</p>
<ul>
<li>"NackReason-specific TLVs" is not defined, because <em>Duplicate</em> and <em>GiveUp</em> don't need this.</li>
<li>TLV-TYPE code assignments are updated with <em>NackReason</em> element.</li>
</ul>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=107882015-06-21T21:40:01ZJunxiao Shi
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/10788/diff?detail_id=9736">diff</a>)</li></ul><p>Question: should I change <strong>CachingPolicy</strong> header field to use a structure similar to Nack?</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=107892015-06-21T21:42:40ZEric Newberryenewberry@cs.ucla.edu
<ul></ul><p>Junxiao Shi wrote:</p>
<blockquote>
<p>Question: should I change <strong>CachingPolicy</strong> header field to use a structure similar to Nack?</p>
</blockquote>
<p>It would create consistency within the API. Does CachingPolicy need anything besides a non-negative integer to indicate the policy?</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=108482015-06-23T17:11:16ZJunxiao Shi
<ul></ul><p>Answer to <a class="issue tracker-3 status-5 priority-3 priority-high3 closed" title="Task: NDNLPv2 design: packet format API for NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFa... (Closed)" href="https://redmine.named-data.net/issues/2841">#2841</a> note-33:</p>
<blockquote>
<p>I don't really like that you completely removed NackReason-specific elements in the spec. Why do you want to modify core parts of the specification (i.e., suddenly adding rules that Nack can actually contain multiple elements and define rules how to process those elements) instead of defining it just once upfront? </p>
</blockquote>
<p>It's pointless to define something that won't be used.</p>
<p>We have decided not to define <code>LpTrailerField</code> until it's first used.<br>
For the same reason, NackReason-specific elements won't be defined until it's first used.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=109322015-06-25T17:28:02ZAlex Afanasyev
<ul></ul><p>Junxiao Shi wrote:</p>
<blockquote>
<p>Question: should I change <strong>CachingPolicy</strong> header field to use a structure similar to Nack?</p>
</blockquote>
<p>I don't have a strong preference, but leaning towards consistency (so, towards the change).</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=109332015-06-25T17:35:07ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>100</i> to <i>90</i></li></ul><p>I also prefer to make the note-20 change.<br>
Based on votes in note-21 and note-23, the change will be made, although this means implementation needs reworking.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=109412015-06-25T19:11:40ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p><a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93/f5fd5211a0dff7d33c8ad8e44dad9971dcfcaeea">https://gist.github.com/yoursunny/92d8c3514476be6a7b93/f5fd5211a0dff7d33c8ad8e44dad9971dcfcaeea</a></p>
<p>note-20 is fulfilled.</p>
<p>I also renamed <strong>CachingPolicy</strong> to <strong>CachePolicy</strong> to reduce the length.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=109582015-06-26T05:35:33ZDavide Pesavento
<ul><li><strong>Subject</strong> changed from <i>NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachingPolicy, IncomingFaceId</i> to <i>NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceId</i></li></ul> NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=119152015-08-06T16:36:58ZJunxiao Shi
<ul></ul><p>Spec is updated to <a href="https://gist.github.com/yoursunny/92d8c3514476be6a7b93/4893b3a6183b2751755cc2e9ee208c0c0bbfb8bc" class="external">revision 4893b3a6183b2751755cc2e9ee208c0c0bbfb8bc</a> with NackReasons defined in <a class="issue tracker-3 status-5 priority-2 priority-default closed" title="Task: Determine rules to combine NackReasons (Closed)" href="https://redmine.named-data.net/issues/3032">#3032</a> note-2.</p>
NFD - Task #2763: NDNLPv2: NACK, Fragmentation, NextHopFaceId, CachePolicy, IncomingFaceIdhttps://redmine.named-data.net/issues/2763?journal_id=119162015-08-06T16:37:21ZJunxiao Shi
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11916/diff?detail_id=10590">diff</a>)</li></ul>