[Nfd-dev] NLSR TLV Assignments

[Nick Gordon]

Junxiao,

That seems to contradict the statement "TLV-TYPE SHOULD be unique at all nested levels" found here: http://named-data.net/doc/ndn-tlv/tlv.html

Could you explain why application-level TLV assignments need not be unique?

-Nick


On 08/23/17 12:09, Junxiao Shi wrote:
> Hi Damian
>
> Each application is entitled the entire range of TLV-TYPE numbers less those reserved for the network. NLSR's usage of a TLV-TYPE number 
> within application range does not deny other applications from using the same TLV-TYPE number. Therefore, from NFD's point of view, it is 
> fine for NLSR to use as many numbers as wanted.
>
> Yours, Junxiao
>
> On Wed, Aug 23, 2017 at 09:33 Damian Matthew Coomes (dmcoomes) <dmcoomes at memphis.edu <mailto:dmcoomes at memphis.edu>> wrote:
>
>     All,
>
>
>     I am working on a publisher for the statistics collection in NLSR, but I wanted to clarify something before I moved forward.
>     Currently, NLSR statistics maintains a count for 20 different items (sent name lsa interests, received hello data, etc.). There is
>     some concern about using 20 of the allotted TLV-VALUE numbers set aside for application use, mentioned in the table at the bottom of
>     this page: https://named-data.net/doc/ndn-tlv/types.html. Would it be fine to use those values for statistics, which would be the
>     range 142-161, or would it be preferred that I use just one value (142) for statistics and have some sort of internal management to
>     distinguish specific statistical values?
>
>
>     Thanks,
>
>
>     Damian Coomes
>
>     _______________________________________________
>     Nfd-dev mailing list
>     Nfd-dev at lists.cs.ucla.edu <mailto:Nfd-dev at lists.cs.ucla.edu>
>     http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

-- 
-Nick

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