[Nfd-dev] Structured names and readable timestamp

[Junxiao Shi]

Hi Adhy

Yes, the NDN packet format does not require the payload to be encrypted, so you can certainly put these information as plaintext in the payload.
It’s a bit worrisome as routers are going to inspect the payload, but it’s too early to conclude that as “evil” yet, as putting them in NDNLP is not necessarily better given these fields are end-to-end.

Yours, Junxiao

> On Jun 22, 2017, at 6:15 AM, Adhy Satya <adhysatya820 at gmail.com> wrote:
> 
> Thank you Junxiao.
> 
> Is there a way to put this information in the payload and not encrypt it? I want the intermediate routers to be able to read it and make forwarding decisions.
> I plan to add more fields in the future, which will create long naming schemes.
> 
> 
> 
> On Wed, Jun 21, 2017 at 8:00 PM, Junxiao Shi <shijunxiao at email.arizona.edu <mailto:shijunxiao at email.arizona.edu>> wrote:
> Hi Adhy
> 
> 
> - Consumer application sends out Interest to the network in the form:
> /my_prefix/c_latitude/c_longitude/SeqNo/Timestamp/Nonce
> 
> - The producer application registers the prefix "/my_prefix" and replies with data in the form:
> /my_prefix/p_latitude/p_longitude/SeqNo/Timestamp
> 
> The Interests currently timeout.
> 
> Interest name must be a prefix of Data name in order to be satisfied by Data.
> This Interest name is not a prefix of Data name, so it times out.
> 
> Generally, producer should respond with Data that has the same name as Interest, and place any additional fields in the Data payload. It is also possible to place additional fields in the Data name, after the original Interest name, i.e. /my_prefix/c_latitude/c_longitude/SeqNo/Timestamp/Nonce/p_latitude/p_longitude
> 
>  Yours, Junxiao
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170622/d38123f4/attachment.html>