[Nfd-dev] Vanet in NFD

[Adhy Satya]

Hi Professor Zhang,

Thank you. If I understood correctly, I should use structured names (i.e.,
/domain/user/info_1/info_2/... for Interest and Data packets).

If so, should I accomplish this by using the "ndn::Name::append" method
from the ndn-cxx library? I'm still not familiar with NFD, so it would help
if the team has a sample implementation.

Same goes to the second point. Are there any tutorials on how to chunk and
encapsulate a file?


Thank you


On Tue, Jun 20, 2017 at 12:25 AM, Lixia Zhang <lixia at cs.ucla.edu> wrote:

>
> On Jun 19, 2017, at 11:54 AM, Adhy Satya <adhysatya820 at gmail.com> wrote:
>
> Hi,
>
> I have NFD 0.5 and ndn-cxx-0.5.0 installed on my machine.I am developing a
> consumer/producer application using the ndn-cxx templates.
>
> My application scenario is a VANET, whereas the consumer and producer
> exchange location information and transfer files between them. Also, the
> cars along the way must be able to read the consumer and producer location.
>
> So,
>
> 1. How can I exchange location information between the end-hosts so that
> information is also available to the intermediate ndn routers?
>
>
> encode all the info you want the the intermediate nodes to see in the name
> one old example of doing this:
> http://named-data.net/publications/jacobsonvoccn/
>
> 2. The sample producer application only creates a data packet based on the
> Interest name and send it back. How can I send an actual file?
>
>
> encapsulate the file data
>
>
>
> Thank you
> Adhy
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170620/0d66dd14/attachment.html>