Feature #3592
Updated by Junxiao Shi about 8 years ago
A forwarding strategy often needs to store measurement-entries *per content object*. Currently object* (currently only the access strategy Access Strategy does, but there might be more use cases, as it is quite common in the literature such as [Flow-aware traffic control for a content-centric network](http://netlab.pkusz.edu.cn/wordpress/wp-content/uploads/2011/10/Flow-aware-traffic-control-for-a-content-centric-network.pdf)) literature, e.g. http://netlab.pkusz.edu.cn/wordpress/wp-content/uploads/2011/10/Flow-aware-traffic-control-for-a-content-centric-network.pdf) However, currently there is no reliable mechanism to identify the object name. We cannot assume that every application will use the naming scheme of "/.../.../version/segment" "/.../.../version/sequence" where everything other than the last component (segment) octet ("sequence") is part of the object name. The access strategy assumes this naming scheme and saves measurement entries "one level up the interest name" which lead to Bug #3219, as NDN-RTC uses a different naming scheme. The I think the problem is more general and stems from the inability to identify the object name.