[Nfd-dev] additional data between ethernet header and ndn header
Junxiao Shi
shijunxiao at email.arizona.edu
Tue Jan 5 08:30:13 PST 2016
Hi Salvatore
Your decoding is wrong. FD indicates the TLV-LENGTH field has 3 octets. See http://named-data.net/doc/ndn-tlv/tlv.html#variable-size-encoding-for-type-t-and-length-l
Yours, Junxiao
From: Salvatore Signorello
Sent: Tuesday, January 5, 2016 09:25
To: Junxiao Shi
Cc: Alex Afanasyev; <nfd-dev at lists.cs.ucla.edu>
Subject: Re: [Nfd-dev] additional data between ethernet header and ndn header
Hi Junxiao,
sorry to come back to you on this thing again, I know that I should simply update my software which is outdated.
Now I see a Data packet generated by ndnpoke (some software versions and OS listed in the previous mail) that contains the following:
50:fd:01:83:51:08:00:00:00:00:00:00:00:00:54:fd:01:75:06:fd:01:71:07:22
which, according to your previous hypothesis, could be decoded like:
50 fd // NdnlpData
01 83 // ????
51 08 // NdnlpSequence
00 00 00 00 00 00 00 00
54 fd // NdnlpPayload
01 75 // again ????
06 fd // Data
01 71 // ibid
07 22 // name
In addition, as you can see the 'fd' length value is never decremented...this sound a bit weird. Any idea?
Best,
Salvatore
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160105/e31685c7/attachment.html>
More information about the Nfd-dev
mailing list