Project

General

Profile

Actions
Copy link

Feature #4518

open

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

Added by Junxiao Shi over 6 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
3.00 h
Tags:
Packet03Transition

Description

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".

Actions
Copy link
 #1

Updated by Davide Pesavento about 6 years ago

  • Tags set to Packet03Transition
Actions
Copy link
 #2

Updated by Eric Newberry over 4 years ago

  • Assignee set to Eric Newberry
Actions
Copy link
 #3

Updated by Eric Newberry over 4 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #4

Updated by Eric Newberry over 4 years ago

  • Assignee deleted (Eric Newberry)
Actions
Copy link
 #5

Updated by Davide Pesavento over 4 years ago

  • Status changed from In Progress to New
Actions
Copy link
 #6

Updated by Eric Newberry over 4 years 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.

Actions
Copy link

Also available in: Atom PDF