[Ndn-interest] Basic Query about Dual Names for one Content

[Syed Hassan Ahmed]

​Dear Prof. Junxiao,

Thanks for the detailed explanation. I understood the encapsulation idea,
however, your very last comment is basically endorsing my query, where, the
appearance of two prefixes may occur for the same content, the consumer has
to send Interest two times. Because upon the first Interest Type 1
(referring my previous email), the consumer couldn't retrieve the required
content, but it has been informed (redirected) to retransmit Interest with
the valid Name prefix...

1. Now here jumps in the attacker? Or Malicious Node? What is the security
aspect in this case?
2. Why would a consumer believe this publisher's intention? If the
redirecting message is only signed by the vehicle?
3. And through what medium/face this Redirection information will be
passed? I mean, in a pull based manner, the producer only sends Data, if
the prefix matches, otherwise, forwarding Daemon gets active for that
Interest and takes decision depending on the strategy, of course.

Is there any scheme or architectural discussion available, where, two
prefixes are used for same content or chunk level retrieval. ?

Dear Andrew Brown,

Thanks for your response. Tell me if I am wrong, I understand your example,
as we have sensors installed for lets say Temperature Monitoring, and by
sending an Interest, you want to retrieve sensed information from either
specific sensor or generally from any sensor. I think, if the former case,
if some other consumer has already requested the device specific readings
and it is cached in the nearby router, so you will get it retrieved by
sending the first prefix that you mentioned.

Also, I agree that in the latter case, you have to have two prefixes and
even though the reading is identical, but since in the first case, you are
being device specific and in the second, you aren't.. As per current NDN, I
can't find the other solutions for such case other than application
sophistication level.


Best Regards,
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
*Syed Hassan Ahmed *(하산)
Kyungpook National University,
Daegu City, Republic of Korea.
Cell: +82-10-9883-0786
https://sites.google.com/site/shahmedknu/

On Fri, Jul 22, 2016 at 12:56 AM, Brown, Andrew <andrew.brown at intel.com>
wrote:

> All,
>
>
>
> I am very interested in multiple names per data packet: for some time, I
> have wanted to produce one piece of data (e.g. a temperature reading), but
> consume it under multiple namespaces (e.g. /temp/[sensor id]/[timestamp]
> and /temp/[timestamp])—the point is that multiple sensors could produce
> simultaneously but a consumer could choose to retrieve either the latest
> sensor-specific reading (e.g. /temp/[sensor id]?ChildSelector=RightMost) or
> the latest global reading (/temp?ChildSelector=RightMost). I cannot do this
> in the current implementation: I must register both prefixes and generate
> packets for both types of requests. I can think of a couple of mechanisms
> that would be helpful (e.g. a field on the data packet for additional
> names, interest selectors that work on more than the last component) but
> are there architectural reasons that this can’t or shouldn’t be done? I
> originally thought the LINK mechanism would allow this but I don’t think it
> does.
>
>
>
> Sincerely,
>
>
>
> Andrew Brown
>
> IoTG Strategy and Integrated Products
>
> Cell: 360-292-5859
>
>
>
> *From:* Ndn-interest [mailto:ndn-interest-bounces at lists.cs.ucla.edu] *On
> Behalf Of *Lixia Zhang
> *Sent:* Thursday, July 21, 2016 12:35 AM
> *To:* Syed Hassan Ahmed <s.h.ahmed at ieee.org>
> *Cc:* ndn-interest at lists.cs.ucla.edu
> *Subject:* Re: [Ndn-interest] Basic Query about Dual Names for one Content
>
>
>
>
>
> On Jul 21, 2016, at 12:18 AM, Syed Hassan Ahmed <s.h.ahmed at ieee.org>
> wrote:
>
>
>
> Respected NDN Community,
>
>
>
> Can we have two names for one Content? Let's say, we consider
> heterogeneous naming schemes, that have been applied at two different
> locations (X, Y) and the nodes are mobile (lets say Vehicles). Now when a
> node from location X moves into the range of location Y? How the NDN
> router/node resolves this issue? May be my question is a bit ambitious,
> however, I believe that one content can have multiple names. I understand
> the concept of NONCE somehow, but NONCE can be applied to two different
> names for the same content?
>
>
>
> 1/ yes a single piece of content can have multiple names.
>
> However every name should name a unique piece of content.
>
>
>
> 2/ There can be applications that name content based on locations.
>
> generally speaking, content names are not location-specific.
>
>
>
> 3/ in your above example: do vehicles X and Y carry an identical piece of
> content?
>
> If so, that content can have its own name, independent from the locations
> of X or Y, there is no issue whether X and Y are far apart or close to each
> other (this could lead you to a different question: if a name is not
> location-dependent, how NDN forwarders find the content: some discussions
> here: http://named-data.net/publications/survey_mobility_support_ndn/)
>
>
>
> 4/ "nonce" is not relevant to the above discussions; it's used to mitigate
>  interest looping.
>
>
>
> my 2 cents,
>
> Lixia
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160722/852008a6/attachment.html>