https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232019-06-11T10:50:30ZNDN project issue tracking systemNLSR - Task #4910: Suppress sub-prefix of a hub's prefix advertised by NFDhttps://redmine.named-data.net/issues/4910?journal_id=254562019-06-11T10:50:30ZSaurab Dulal
<ul><li><strong>Target version</strong> changed from <i>Minor release v0.5.1</i> to <i>v0.6.0</i></li></ul> NLSR - Task #4910: Suppress sub-prefix of a hub's prefix advertised by NFDhttps://redmine.named-data.net/issues/4910?journal_id=271122020-12-29T19:01:27ZSaurab Dulal
<ul><li><strong>Target version</strong> changed from <i>v0.6.0</i> to <i>Minor Release v0.6.1 </i></li></ul> NLSR - Task #4910: Suppress sub-prefix of a hub's prefix advertised by NFDhttps://redmine.named-data.net/issues/4910?journal_id=275222022-01-14T21:20:13ZJunxiao Shi
<ul></ul><p>Such prefix should not be suppressed/aggregated.</p>
<p>Suppose an end host advertises <code>/ndn/edu/memphis/brock1987</code> at both Memphis and UCLA.<br>
If the Memphis router suppresses this advertisement, all Interests would go to UCLA according to longest prefix match rules.</p>