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

Alex Afanasyev aa at CS.UCLA.EDU
Thu Jul 21 00:33:32 PDT 2016

Just to be clear.  There is content (payload) and there is a data packet that carries a payload.  A data packet is unique and has a unique name.  The same content can be carried in different data packets that can have different names, meta information, and signatures.

If there are two producers that can serve data packets under the same prefix, then forwarding system can choose either of them.  If data cannot be retrieved from one, the forwarding may try alternative path.

In my opinion, if an application is designed properly, different producers will use different names for their data.  They can use the common prefix and be alternative suppliers of the data with the common prefix, but there has to be a way to retrieve (identify) a specific piece of data from a specific producer.

I'm not sure which nonce you're referring to.  If you're talking about nonce in  interest packets, then it is used for completely different purpose and not related to data packets.


> On Jul 21, 2016, at 9: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?
> Best Regards,
> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
> Syed Hassan Ahmed (하산)
> Kyungpook National University,
> Daegu City, Republic of Korea.
> Cell: +82-10-9883-0786
> https://sites.google.com/site/shahmedknu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160721/47a87abf/attachment.bin>

More information about the Ndn-interest mailing list