[Ndn-interest] jndn Library

[Junxiao Shi]

Dear folks

It seems that the ControlParameters protobuf definition in
jndn/examples/src/net/named_data/jndn/tests/control-parameters-proto.proto
<https://github.com/named-data/jndn/blob/4f94d928b85ec41c5163a9393e2a8c17a5143b01/examples/src/net/named_data/jndn/tests/control-parameters-proto.proto#L17-L27>
does
not match ControlCommand rev49
<https://redmine.named-data.net/projects/nfd/wiki/ControlCommand/49>.

NFD Management protocol predates TLV evolvability guidelines. See Feature
4221 note-3 <https://redmine.named-data.net/issues/4221#note-4> for current
guidelines on how to process NFD Management protocol messages.
A complete redesign is scheduled in Feature 4600
<https://redmine.named-data.net/issues/4600>, which provides backwards
compatibility in management protocol.

Yours, Junxiao

On Mon, Jul 8, 2019 at 11:54 AM Thompson, Jeff <jefft0 at remap.ucla.edu>
wrote:

> The meaning of “critical type code” is explained here:
>
> https://named-data.net/doc/NDN-packet-spec/current/tlv.html#considerations-for-evolvability-of-tlv-based-encoding
>
> Type code 129 is critical because its least-significant bit is 1. "if the
> least significant bit of element’s TLV-TYPE number is 1, abort decoding
> and report an error.” The enforcement of critical type codes was added
> after jNDN version 0.16.
>
> The application is using the JNDN ProtobufTlv class which uses a protobuf
> description file to decode TLV. It was decoding a TLV that has type code
> 129, but the corresponding Protobuf description does not have an field with
> this “critical" type code, and so the decoding is aborted because the
> application doesn’t know how to handle it.
>
> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of
> Avakash Bhat via Ndn-interest <ndn-interest at lists.cs.ucla.edu>
> Reply-To: Avakash Bhat <bhatavakash at gmail.com>
> Date: Thursday, July 4, 2019 at 2:35:00
> To: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
> Subject: [Ndn-interest] jndn Library
>
>
> ControlParametersResponseMessage.Builder decodedControlResponse
> = ControlParametersResponseMessage.newBuilder();
> ProtobufTlv.decode(decodedControlResponse, encodedControlResponse);
> ControlParametersResponse
> controlResponse= decodedControlResponse.getControlResponse();
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20190708/ff0b39d1/attachment-0001.html>