Project

General

Profile

Actions

Task #4780

closed

Make Interest Parameters TLV non-critical

Added by Davide Pesavento over 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Start date:
Due date:
% Done:

100%

Estimated time:

Description

As discussed on 2018-11-26, the Interest Parameters element should be redefined to use a non-critical TLV-TYPE.


Related issues 1 (0 open1 closed)

Related to NDN Specifications - Feature #4831: Redefine ParametersSha256DigestComponent covered areaClosedJunxiao Shi

Actions
Actions #1

Updated by Davide Pesavento about 5 years ago

  • Status changed from New to In Progress
  • Assignee set to Davide Pesavento
  • % Done changed from 0 to 30
Actions #2

Updated by Junxiao Shi about 5 years ago

As discussed on 20190130 NFD call, a range of TLV-TYPE numbers indicates of the start of digest computation area for ParametersSha256DigestComponent.
I'd suggest renumbering Parameters to 0x30 instead of 0x24, so that bitwise expression (tlvType & 0xF0) == 0x30 identifies this range.

Actions #3

Updated by Davide Pesavento about 5 years ago

Junxiao Shi wrote:

I'd suggest renumbering Parameters to 0x30 instead of 0x24, so that bitwise expression (tlvType & 0xF0) == 0x30 identifies this range.

err... why? [48-63] or [36-51], what's the difference? both intervals are currently unassigned.

Actions #4

Updated by Junxiao Shi about 5 years ago

Bitwise operator is better than inequal comparison operator, at least in hardware implementation (think electric circuits where it needs less gates).
Although the need for hardware implementation at this level may be sparse, there’s no harm in assigning a hardware-friendly number.

Actions #5

Updated by Junxiao Shi about 5 years ago

  • Related to Feature #4831: Redefine ParametersSha256DigestComponent covered area added
Actions #6

Updated by Davide Pesavento about 5 years ago

Shouldn't ParametersSha256DigestComponent also be non-critical? What's the point of having one critical but not the other?

Actions #7

Updated by Junxiao Shi about 5 years ago

Shouldn't ParametersSha256DigestComponent also be non-critical? What's the point of having one critical but not the other?

Evolvability rules do not apply to name component types.

Actions #8

Updated by Davide Pesavento about 5 years ago

And where is that written?

Actions #9

Updated by Davide Pesavento about 5 years ago

  • % Done changed from 30 to 80

ndn-cxx implementation update https://gerrit.named-data.net/c/ndn-cxx/+/5217

Actions #10

Updated by Davide Pesavento about 5 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 80 to 100
Actions #11

Updated by Davide Pesavento about 5 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF