NDN project issue tracking system: Issueshttps://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232022-05-04T13:59:45ZNDN project issue tracking system
Redmine ndns - Feature #5203 (New): Accommodate certificate name in KeyLocatorhttps://redmine.named-data.net/issues/52032022-05-04T13:59:45ZJunxiao Shi
<p>NDNS protocol so far inherently assumes that KeyLocator is key name.<br>
It does not work if KeyLocator is certificate name.<br>
This issue is finding a resolution to this problem.</p>
NLSR - Task #4803 (New): Abstract segment fetcher functionality in separate LSA fetcher classhttps://redmine.named-data.net/issues/48032019-01-11T11:34:35ZSaurab Dulal
<p>Currently, segment fetcher is directly used in LSDB class, this patch is to separate LSA fetcher from LSDB. </p>
NFD - Feature #4781 (New): Add Adaptive Replacement Cache (ARC) algorithmhttps://redmine.named-data.net/issues/47812018-11-29T19:25:09ZThiago Teixeira
<p>I would like to suggest the implementation of the <strong>Adaptive Replacement Cache</strong> (ARC) in NFD.<br>
Paper: <a href="https://www.usenix.org/conference/fast-03/arc-self-tuning-low-overhead-replacement-cache">https://www.usenix.org/conference/fast-03/arc-self-tuning-low-overhead-replacement-cache</a></p>
<p>ARC was developed by IBM in 2006 and keeps track of both frequently and recently used. It has shown better performance than LRU.<br>
There are C++ implementations available.</p>
NFD - Feature #4762 (New): Add a new UnsolicitedDataPolicy that admits unsolicited data by prefixhttps://redmine.named-data.net/issues/47622018-10-23T20:59:55ZErnest McCrackenemccrckn@memphis.edu
<p>We would like to add an unsolicited data policy that allows applications to specify which prefixes they would like to cache unsolicited data for.</p>
<p>The proposed design is as follows:<br>
Create a new UnsolicityDataPolcy called AdmitPrefixesUnsolicitedDataPolicy that defines two additional methods register(name) and unregister(name).<br>
Prefixes are stored in a table which is looked up in the decide method.</p>
<p>Create a new manager class to allow applications to use the Interest based API to add/remove prefixes as needed.</p>
NFD - Feature #4650 (Feedback): Accept and store PrefixAnnouncement in rib/announce commandhttps://redmine.named-data.net/issues/46502018-07-05T08:45:20ZJunxiao Shi
<p>Including PrefixAnnouncement in <a class="wiki-page" href="https://redmine.named-data.net/projects/nfd/wiki/RibMgmt">RibMgmt</a> <code>rib/announce</code> command enables prefix propagation without NFD having to access the prefix owner's signing key.<br>
This issue changes <code>RibManager</code> to accept the alternate command format, and also stores the PrefixAnnouncement element in the RIB entry so that readvertise component can retrieve it.</p>
ndns - Task #4344 (New): NsCache in IterativeQueryController Need to check FreshnessPeriod befor...https://redmine.named-data.net/issues/43442017-10-16T20:19:14ZYumin Xiame@yumin-xia.com
<p>Currently, NsCache does not check TTL/FreshnessPeriod, when retrieving data from cache. </p>
<p>Solution:<br>
If data is in the cache:</p>
<ol>
<li>check TTL.</li>
<li>if valid, return data.</li>
<li>if not, remove data from cache, fetch record from network.</li>
</ol>
named-data.net - Bug #4061 (New): 500 error when pasting "Beer Mug Emoji"https://redmine.named-data.net/issues/40612017-04-20T10:59:46ZJunxiao Shi
<p>Steps to reproduce:</p>
<ol>
<li>In "new issue" page, paste <a href="http://emojipedia.org/beer-mug/" class="external">Beer Mug Emoji</a> in any text box.</li>
<li>Tap "Create" button.</li>
</ol>
<p>Expected: issue created successfully.<br>
Actual: "internal server error".</p>
<p>This character appears in <a href="http://jenkins.named-data.net/job/NLSR/1071/label=OSX-10.11/consoleText" class="external">HomeBrew output from Jenkins</a>. This bug makes it difficult to paste HomeBrew output without editing.</p>
ndn-cxx - Feature #4020 (In Progress): "ad hoc" detection on Linuxhttps://redmine.named-data.net/issues/40202017-03-27T21:56:21ZJunxiao Shi
<p>When creating a multicast Ethernet or UDP face, use Linux-specific API to detect whether the underlying network interface is ad hoc.</p>
ndn-cxx - Feature #4019 (New): "ad hoc" detection on macOShttps://redmine.named-data.net/issues/40192017-03-27T21:55:20ZJunxiao Shi
<p>When creating a multicast Ethernet or UDP face, use macOS-specific API to detect whether the underlying network interface is ad hoc.</p>
ndn-cxx - Task #3561 (New): Add a FOO_MAX enumerator to all public enumerationshttps://redmine.named-data.net/issues/35612016-03-22T17:02:39ZDavide Pesavento
<p>It is not currently possible to know if an arbitrary integer number is a valid value for a given enumeration. In some cases, even a simple <code>static_cast</code> of the integer to the enumeration type can invoke undefined behavior, so the "upper bound" of the enum must be known in advance. Having a <code>_MAX</code> enumerator also helps in validating user input.</p>
NFD - Bug #3219 (New): AccessStrategy measurements ineffective for NDN-RTC traffichttps://redmine.named-data.net/issues/32192015-09-21T18:10:34ZJunxiao Shi
<p><strong>AccessStrategy</strong> v1 stores last working nexthop in measurements table.<br><br>
An measurements entry is created for one-shorter-prefix of Data Name: for example, when Data <code>/arizona/cs/www/index.html/v3/s0</code> arrives, its incoming face is recorded as last working nexthop of <code>/arizona/cs/www/index.html/v3</code> prefix.<br><br>
To forward a subsequent Interest, a longest prefix match is performed on the measurements table, and if an entry is found, the recorded last working nexthop is considered; otherwise, the Interest would be multicast to all nexthops in FIB entry.<br><br>
There is no attempt to aggregate measurements onto a shorter prefix.</p>
<p><strong>NDN-RTC</strong> is a realtime conference library.<br><br>
The bulk of Data packets generated by NDN-RTC have Names similar to<br>
<code>/ndn/edu/ucla/remap/ndnrtc/user/remap/streams/camera_1469c/mid/key/2991/data/%00%00/23/89730/86739/5/27576</code>.<br><br>
In this name structure, the component before <code>data</code> is the frame number which changes more than 50 times per second,<br>
and the component after <code>data</code> is the segment number within a frame which is usually no more than 25.<br><br>
Interest Names end with the segment number (<code>/ndn/edu/ucla/remap/ndnrtc/user/remap/streams/camera_1469c/mid/key/2991/data/%00%00</code>).</p>
<p><strong>AccessStrategy measurements are ineffective for NDN-RTC traffic</strong>.<br><br>
With NDN-RTC namespace design, AccessStrategy's one-shorter-prefix measurements entry is created beyond the segment number (<code>/ndn/edu/ucla/remap/ndnrtc/user/remap/streams/camera_1469c/mid/key/2991/data/%00%00/23/89730/86739/5</code>), so it's worthless for subsequent Interests.<br><br>
AccessStrategy creates one measurements entry per Data and retain it for 8 seconds; under high traffic, these measurements entries can consume considerable memory and degrade forwarder performance.</p>
ndn-sci - Task #3193 (New): Add a metadata field in the Databasehttps://redmine.named-data.net/issues/31932015-09-09T18:45:57Zsusmit shannigrahisusmit.shannigrahi@gmail.com
<p>We should have a metadata field in the database. This need changes to translator, catalog and UI.<br>
When clicked on a name on UI, it should bring up the metadata.</p>
ndn-sci - Bug #3187 (New): /ndn/broadcast strategy renamed to /ndn/multicast in NFD-0.3.4https://redmine.named-data.net/issues/31872015-09-08T10:41:21ZAnonymous
<p>Please update the catalog configuration appropriately.</p>
mini-ndn - Task #3056 (New): Add ability to specify name prefixes announced by NLSR on a nodehttps://redmine.named-data.net/issues/30562015-07-17T13:17:46ZVince Lehmanvslehman@memphis.edu
<p>Currently, Mini-NDN automatically generates a name prefix to announce based on the node's name.</p>
<p>Instead, the user should be able to specify the names advertised by NLSR for each node.</p>
mini-ndn - Task #2947 (New): Add ability to save statistics to file after an experiment has runhttps://redmine.named-data.net/issues/29472015-06-24T09:37:03ZVince Lehmanvslehman@memphis.edu
<p>After statistics are collected during an experiment, a user should be able to save the collected statistics to file through a save prompt.</p>