https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232017-08-14T14:27:34ZNDN project issue tracking systemrepo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=203142017-08-14T14:27:34ZAlex Afanasyev
<ul><li><strong>Assignee</strong> set to <i>Muktadir Chowdhury</i></li></ul> repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=205162017-09-11T23:11:02ZMuktadir Chowdhurymrchwdhr@memphis.edu
<ul></ul><p>I need some help regarding the task. The description is not very clear to me. I will try to break it down according to my understanding:<br>
First, Repo will serve certificate to the other nodes. For that repo will store the certificates some where (CertificateCache?) and set interest filter on the certificate's common prefix.<br>
Second, Repo needs to register prefix for the data prefixes here : <a href="https://github.com/named-data/repo-ng/blob/master/src/repo.cpp#L148">https://github.com/named-data/repo-ng/blob/master/src/repo.cpp#L148</a>. </p>
<p>I am not aware of the discussion related to PIB service. So can't relate.</p>
repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=205222017-09-13T10:01:27ZAlex Afanasyev
<ul></ul><p>I think you're over-thought the issue. Right now repo registers with local NFD a set of prefixes specified in the configuration file. With this issue (which should be an option to enable), the repo should register prefixes that correspond to all data packets stored in repo (could be many prefixes, but it's ok). So, you don't need to use any new data structures, rather differently handle the startup and add additional logic on when data packet is added to the storage and removed from the storage.</p>
repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=205242017-09-14T11:11:50ZJunxiao Shi
<ul></ul><p>Registering the exact name of each stored Data packet would not supoort the certificate use case, because the Interest to retrieve a certificate is usually a true prefix of the Data name.<br>
Without loss of generality, I would envision:</p>
<ul>
<li>a configuration option that determines the granularity of prefix registration, ie "register Data name minus last <em>k</em> components"</li>
<li>alternatively, a parameter in repo insertion command that determines the granularity, along with a database field storing this parameter</li>
</ul>
<p>The program logic needs to ensure the prefix registration is not withdrawn until the last Data requiring such registration is deleted.</p>
repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=205252017-09-14T11:24:21ZJunxiao Shi
<ul></ul><blockquote>
<p>add additional logic on when data packet is added to the storage and removed from the storage.</p>
</blockquote>
<p>Hint: given <code>ReadHandle</code> is reponsible for data prefix registration, <code>RepoStorage</code> needs to emit signals upon Data insertion and deletion, and <code>ReadHandle</code> shall react to such signals.</p>
<p>Caution:</p>
<ul>
<li>If a Data is inserted and quickly deleted, <a class="issue tracker-1 status-1 priority-2 priority-default" title="Bug: Face::unsetInterestFilter is ineffective before registration completes (New)" href="https://redmine.named-data.net/issues/2720">#2720</a> may affect the unregistration.</li>
<li>If there are many registrations upon startup, <a class="issue tracker-1 status-6 priority-2 priority-default closed" title="Bug: KeyChain::sign is slow with tpm=osx-keychain (Rejected)" href="https://redmine.named-data.net/issues/1589">#1589</a> and <a class="issue tracker-1 status-1 priority-2 priority-default" title="Bug: Multiple register prefix gives NFD error "request timed out (code: 10060)" (New)" href="https://redmine.named-data.net/issues/2174">#2174</a> may cause registration failures until <a class="issue tracker-2 status-1 priority-2 priority-default" title="Feature: Controller: stop-and-wait (New)" href="https://redmine.named-data.net/issues/2293">#2293</a> is implemented.</li>
</ul>
repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=207372017-10-03T15:05:56ZMuktadir Chowdhurymrchwdhr@memphis.edu
<ul><li><strong>Assignee</strong> changed from <i>Muktadir Chowdhury</i> to <i>Nicholas Gordon</i></li></ul> repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=207502017-10-05T09:07:23ZNicholas Gordonnmgordon@memphis.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>80</i></li></ul><p>I've implemented the feature, and am finishing up on the tests. Provided everything goes smoothly, this should be finished promptly.</p>
repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=207542017-10-05T11:16:09ZNicholas Gordonnmgordon@memphis.edu
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Code review</i></li></ul> repo-ng - Feature #4247: Automatic per-data-packet (per-group) prefix registrationshttps://redmine.named-data.net/issues/4247?journal_id=209102017-10-23T08:53:44ZNicholas Gordonnmgordon@memphis.edu
<ul><li><strong>Status</strong> changed from <i>Code review</i> to <i>Closed</i></li></ul>