<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>All,<o:p></o:p></span></a></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>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</span> <span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Sincerely,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:black'>Andrew Brown<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#595959'>IoTG Strategy and Integrated Products<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#595959'>Cell: 360-292-5859</span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#7F7F7F'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Ndn-interest [mailto:ndn-interest-bounces@lists.cs.ucla.edu] <b>On Behalf Of </b>Lixia Zhang<br><b>Sent:</b> Thursday, July 21, 2016 12:35 AM<br><b>To:</b> Syed Hassan Ahmed <s.h.ahmed@ieee.org><br><b>Cc:</b> ndn-interest@lists.cs.ucla.edu<br><b>Subject:</b> Re: [Ndn-interest] Basic Query about Dual Names for one Content<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Jul 21, 2016, at 12:18 AM, Syed Hassan Ahmed <<a href="mailto:s.h.ahmed@ieee.org">s.h.ahmed@ieee.org</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>Respected NDN Community,<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>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? <o:p></o:p></span></p></div></div></div></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>1/ yes a single piece of content can have multiple names.<o:p></o:p></p></div><div><p class=MsoNormal>However every name should name a unique piece of content.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>2/ There can be applications that name content based on locations.<o:p></o:p></p></div><div><p class=MsoNormal>generally speaking, content names are not location-specific.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>3/ in your above example: do vehicles X and Y carry an identical piece of content?<o:p></o:p></p></div><div><p class=MsoNormal>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: <a href="http://named-data.net/publications/survey_mobility_support_ndn/">http://named-data.net/publications/survey_mobility_support_ndn/</a>)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>4/ "nonce" is not relevant to the above discussions; it's used to mitigate interest looping.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>my 2 cents,<o:p></o:p></p></div><div><p class=MsoNormal>Lixia<o:p></o:p></p></div></div></body></html>