Feature #4518

Wireshark dissector: don't interpret name components as elements denoted by TLV-TYPE

Added by Junxiao Shi over 2 years ago. Updated 2 months ago.

Start date:
Due date:
% Done:


Estimated time:
3.00 h


NDN Packet Format v0.3 permits any TLV-TYPE within 1-65535 range to appear as name component, including those TLV-TYPE numbers that are already defined elsewhere. Wireshark dissector should not interpret a name component TLV-TYPE as its original meaning.
For example, the TLV-TYPE 0x05 normally means "Interest", but it should not decoded as an Interest when 0x05 appears as a name component, but should be interpreted as "name component type 0x05".


Updated by Davide Pesavento almost 2 years ago

  • Tags set to Packet03Transition

Updated by Eric Newberry 3 months ago

  • Assignee set to Eric Newberry

Updated by Eric Newberry 3 months ago

  • Status changed from New to In Progress

Updated by Eric Newberry 3 months ago

  • Assignee deleted (Eric Newberry)

Updated by Davide Pesavento 2 months ago

  • Status changed from In Progress to New

Updated by Eric Newberry 2 months ago

I unclaimed this task because I am completely unfamiliar with Lua and this task requires significant re-engineering of the dissector due to the overlap between the TLV type ranges of name components types and general types.

Also available in: Atom PDF