Project

General

Profile

Actions

Task #4925

closed

Possible Bug in jNDN's interest

Added by Edward Lu almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
04/27/2019
Due date:
% Done:

0%

Estimated time:

Description

I've found that the interest generated by jNDN has a TLV block with TLV type 0x09; according to the NDN TLV-TYPE number assignment page (https://named-data.net/doc/NDN-packet-spec/current/types.html), this was formerly for selectors but is now reserved.

Is this an actual bug in jNDN, or am I doing something incorrectly? I have double checked that I am using the latest version of jNDN in my project (version 0.21).

I have attached a screenshot of my code.


Files

jndn-interest.png (23.4 KB) jndn-interest.png Edward Lu, 04/27/2019 02:50 PM
Actions #1

Updated by Edward Lu almost 5 years ago

Ah, I found that this isn't a bug and is actually just a problem with the ndn-lite library's implementation. As I understand it, the flag day for adding the NDN packet v3 support hasn't come yet, so it is okay for the jndn library to still have the old packet format.

Actions #2

Updated by Anonymous almost 5 years ago

  • Status changed from New to Closed

That's right. Thanks for figuring it out. jNDN still emits v02 encoding. However, if you set the Interest application parameters field (which is only in v03), then it will emit v03 encoding.

https://github.com/named-data/jndn/blob/60095efe4929b439ec3dbfc91b9eb24ccbff027c/src/net/named_data/jndn/encoding/Tlv0_2WireFormat.java#L115

Actions

Also available in: Atom PDF